610SPOR2 35h_CBSSportsRad_Houston


Texas A&M Issues ‘Code Maroon’ After Receiving Bomb Threat

View Comments
Kyle Field (credit: Facebook)

Kyle Field (credit: Facebook)

Featured Items

77820352_8PHOTOS: The Bikini: from the '50s to Now

77820352_8Meet The 6-10s

77820352_8Best 7 Events At The Astrodome

77820352_8World Cup's Hottest Fans

From Our CBS Music Sites

77820352_8Is Chandler Parsons Dating A Kardashian??

77820352_8Nicki Minaj's Booty Takes Over Her Album Cover

77820352_8The Worst Things You Can Do On A First Date

77820352_8Local Gas Station Clerk/MMA Fighter Takes Down Thieves

Get Breaking News First

Receive News, Politics, and Entertainment Headlines Each Morning.
Sign Up

HOUSTON (CBS Houston) Early Wednesday afternoon, Texas A&M University issued a “code maroon” upon receiving a bomb threat.

The campus “Code Maroon” alert system stated that there was a bomb threat investigation at Kyle Field at around 12:25 p.m.

Stadium and adjacent buildings on the school’s campus will be closed for the remainder of Wednesday, according to officials.

Approximately 700 people were evacuated from Kyle Field, Reed Building, G. Rollie White, Neetum Steed, and the Bright Athletics complex.

The following statement was issued on the school’s website: “Kyle Field is currently being searched due to a bomb threat issued against the facility. Kyle Field, Reed Building, G. Rollie White, Neetum Steed, and the Bright Athletics complex have been evacuated and the buildings will be closed for the remainder of the day.”


As of 2:00 p.m., CST, Texas A&M authorities continue to investigate a bomb threat at Kyle Field, resulting in the evacuation of the stadium and adjacent facilities.

Authorities were notified of the threat just before 11 a.m. on Wednesday. The threat was written on a wall of a non-academic facility on campus.

An investigation was launched immediately, and a “Code Maroon” emergency message was subsequently issued on Wednesday.

Federal agencies were contacted to aid in the on-going investigation of the incident.

View Comments
blog comments powered by Disqus