Two commercial jets stopped roughly 100 feet apart on crossing runways at Chicago O’Hare International Airport after controllers issued conflicting taxi and takeoff instructions. The March 21, 2006 event involved Lufthansa flight 437, an Airbus A319, and Chautauqua flight 7826, an Embraer E145, both of which halted only after urgent corrections from the tower. Federal investigators later documented at least two more crossing-runway conflicts at the same airport, in 2008 and 2011, raising pointed questions about whether O’Hare’s physical layout and operational tempo produce a recurring collision risk that procedural fixes alone have not eliminated.
Repeated crossing-runway conflicts at O’Hare and why they persist
O’Hare operates one of the most complex runway systems in the United States, with multiple intersecting strips that allow high throughput but also force controllers to sequence arrivals and departures across shared pavement. When sequencing breaks down during peak traffic, two aircraft can occupy the same intersection at the same time. That is exactly what happened on March 21, 2006, when the closest proximity reached 100 feet at the runway intersection, according to the National Transportation Safety Board’s final report on the event. Both aircraft stopped before a collision occurred, but the margin was thin enough to classify the event as a serious incursion.
The 2006 incident was not an isolated failure. On July 22, 2008, a separate crossing-runway conflict at O’Hare brought American Eagle flight 4298 and a Learjet 60 to within about 150 feet laterally, according to the NTSB’s factual report on that event. Three years later, on May 16, 2011, SkyWest flight 6958 and ExpressJet flight 6075 came within about 480 feet of each other while one aircraft landed on runway 9R and the other departed on runway 32L, according to the NTSB’s final report on that case. The probable cause in the 2011 event was the controller’s failure to adhere to runway separation requirements.
Three documented near-conflicts on crossing runways at a single airport within five years suggest a structural problem rather than a string of unrelated human errors. O’Hare’s intersecting runway geometry means that even brief lapses in coordination between ground and local controllers can place two fast-moving aircraft on a collision course. Peak-hour sequencing, when arrivals and departures overlap on shared runway segments, compounds the risk. Procedural changes after each event did not prevent the next one from occurring, which supports the hypothesis that the airport’s physical configuration creates a baseline level of crossing-runway incursion risk that persists regardless of individual corrective actions.
NTSB findings across three O’Hare intersection events
The strongest evidence comes directly from NTSB investigation files covering all three events. In the 2006 case, designated OPS06IA006, the agency’s report identifies the aircraft as DLH437, an Airbus A319 operated by Lufthansa, and CHQ7826, an Embraer E145 operated by Chautauqua Airlines. The report confirms that both aircraft received instructions that placed them on intersecting runways simultaneously and that both stopped at the intersection after controllers recognized the conflict. The 100-foot proximity figure comes from the NTSB’s own measurement of the closest point between the two jets.
The 2008 event, designated OPS08IA011, involved American Eagle flight 4298 and a Learjet 60 on crossing runways. The NTSB factual report recorded the closest proximity at about 150 feet lateral separation and about 325 feet vertical separation. The FAA’s preliminary operational error report also noted the event, giving it an independent paper trail within the agency’s own safety tracking system.
The 2011 case, OPS11IA552, is the most explicitly diagnosed of the three. The NTSB determined the probable cause was the controller’s failure to maintain required separation between SkyWest 6958, which was landing on runway 9R, and ExpressJet 6075, which was departing on runway 32L. The recorded separation was about 480 feet behind and 275 feet above at the closest point. That finding placed responsibility squarely on air traffic control procedures rather than pilot error or equipment malfunction.
Taken together, these three investigations show a consistent pattern: controllers managing crossing-runway operations at O’Hare lost separation between aircraft, and the margins shrank to distances measured in hundreds of feet or less. The aircraft types ranged from regional jets to a larger Airbus narrowbody, and the events occurred across different runway pairs, which indicates the risk is not confined to a single intersection or a single traffic flow. In each case, the immediate technical cause was framed as a controller error, but the repetition across years and traffic configurations points toward deeper systemic vulnerabilities.
What changed at O’Hare after 2011
Public records show that by 2011 O’Hare was already in the midst of a years-long modernization program that aimed, in part, to reduce reliance on intersecting runways by adding more parallel east–west pavement. That longer-term reconfiguration was intended to simplify traffic flows and make it easier for controllers to keep arrivals and departures physically separated. However, the three NTSB cases demonstrate that during the transition period, the airport continued to run complex crossing-runway operations that depended heavily on flawless human coordination.
In response to the 2006, 2008, and 2011 incursions, investigators recommended a series of procedural and training changes. These included clarifying phraseology for taxi and lineup-and-wait clearances, reinforcing readback-hearback discipline, and tightening local rules for using intersecting departure and arrival paths during peak periods. Controllers were reminded to verify that an intersection was clear before issuing takeoff clearance and to avoid compressing sequences to the point where a single misheard instruction could put two aircraft into conflict.
Yet the recurrence of similar events suggests that incremental procedural fixes may have limited effect when layered on top of a runway layout that routinely forces intersecting movements. As long as operations require multiple aircraft to cross or occupy the same intersection within tight time windows, the system remains vulnerable to momentary distractions, radio interference, or misinterpretation. The NTSB’s emphasis on controller error in the 2011 probable-cause statement does not negate the role of geometry and traffic volume in shaping the context in which that error occurred.
Gaps in the public record on O’Hare runway safety after 2011
After the 2011 SkyWest–ExpressJet incident, the publicly accessible record becomes noticeably thinner. The three NTSB files from 2006, 2008, and 2011 provide detailed narratives, diagrams, and timing analyses, but there is no comparable set of intersection-related O’Hare reports in the same database for the years that followed. That absence does not, by itself, prove that crossing-runway conflicts disappeared; it simply means that, if similar events occurred, they either did not meet the NTSB’s threshold for investigation or were handled entirely within internal FAA safety programs that do not routinely publish case-level documents.
The FAA has, over time, expanded its use of non-punitive reporting systems and automated surface surveillance tools to capture runway incursions that stop short of serious incidents. Data from those systems, however, are often summarized in aggregate rather than linked to specific airports and dates in a way that would allow independent reviewers to trace trends at O’Hare. Without that granularity, it is difficult to say whether the combination of runway reconfiguration, procedural changes, and technological aids has materially lowered the risk of crossing-runway conflicts at this specific field.
Another complication is that modernization projects can temporarily increase operational complexity even as they aim to improve safety in the long run. Construction closures, temporary taxi routings, and changing runway availability can all create unfamiliar patterns for controllers and pilots. If any post-2011 incursions at O’Hare were associated with such transitional states, they might be buried in broader statistics rather than documented in stand-alone reports like the 2006, 2008, and 2011 cases.
For local communities, passengers, and aviation workers, the lack of detailed, airport-specific runway safety data after 2011 leaves an important question unanswered: did the pattern of near-collisions on crossing runways at O’Hare truly end, or did it simply fall below the threshold of public visibility? The three NTSB investigations establish that, during a critical five-year window, the combination of intersecting geometry and heavy traffic produced repeated losses of separation measured in mere hundreds of feet. Until more recent, transparent data are available, it remains impossible to determine whether those episodes were the last manifestations of an old layout or early warnings of a risk that still exists whenever O’Hare’s runways cross and the schedule is tight.
More from Morning Overview
*This article was researched with the help of AI, with human editors creating the final content.
