Previous Elgin, Aurora incidents that shut down air traffic

  • The FAA Chicago Air Route Traffic Control Center in Aurora.

    The FAA Chicago Air Route Traffic Control Center in Aurora. Mark Black/File

  • The Air Route Traffic Control Center in Aurora.

    The Air Route Traffic Control Center in Aurora. Daniel White/File

 
 
Updated 9/26/2014 2:04 PM

Here's a look at incidents at the Air Route Traffic Control Center in Aurora and the Terminal Radar Approach Control center in Elgin that have impacted air traffic.

May 5, 1999

 

Software glitch forces Elgin to shut down. All air traffic was stopped in the Chicago area.

May 10, 1999

Another software glitch in Elgin forces flight cancellations at O'Hare.

July 27, 1999

Fumes in Aurora sickened a dozen of air traffic controllers in Aurora, causing widespread flight delays due to a lack of staff. The fumes were caused by a sealant in an attic over the control room.

July 1, 2013

A fire alarm prompts evacuation in Elgin, diverting airplanes and slowing some flights.

Elgin revue crews and police leave the TRACON facility in May. A ground stop is in effect at O'Hare and Midway airports after smoke was reported in the TRACON facility in Elgin. Around 11:30 a.m. all FAA personnel were evacuated after smoke was seen in the Elgin facility.
Elgin revue crews and police leave the TRACON facility in May. A ground stop is in effect at O'Hare and Midway airports after smoke was reported in the TRACON facility in Elgin. Around 11:30 a.m. all FAA personnel were evacuated after smoke was seen in the Elgin facility. - Brian Hill | Staff Photographer
May 13, 2014

Another fire alarm prompts evacuation in Elgin, grounding all flights in and out of Chicago

0 Comments
 
Article Comments
Guidelines: Keep it civil and on topic; no profanity, vulgarity, slurs or personal attacks. People who harass others or joke about tragedies will be blocked. If a comment violates these standards or our terms of service, click the X in the upper right corner of the comment box. To find our more, read our FAQ.