A runway incursion at Boston Logan International Airport on June 20 brought two commercial aircraft within an estimated few hundred feet of each other, triggering an NTSB investigation and renewing scrutiny of controller workload and sequencing errors at complex, intersecting-runway environments. American Airlines flight 3161, a Boeing 737-800, had been cleared for takeoff on runway 27 while Delta Air Lines flight 2351, an Airbus A319, was simultaneously on short final for runway 33 Left — a runway that physically crosses runway 27. The critical error occurred when the same air traffic controller issued the American departure clearance without referencing the Delta aircraft, which at that point was approximately two nautical miles from touchdown. The American crew acknowledged the clearance but did not immediately begin their takeoff roll, a delay of nearly one minute that compressed the already thin margin. The Delta crew, now seconds from the threshold, recognized the developing conflict and executed an immediate go-around, citing the American aircraft as the reason. ADS-B data suggests the two aircraft came within several hundred feet of one another before the A319 climbed away and eventually landed uneventfully approximately ten minutes later.
The sequence of events reveals compounding factors that professional crews and operators should study carefully. The controller initially did the right thing by notifying the Delta crew of crossing traffic on runway 27 at the time of the landing clearance — but then issued the American departure clearance approximately one minute later without reissuing a traffic advisory to either aircraft. The communication gap between the two clearances, combined with the American crew's delayed takeoff roll, created a scenario in which neither aircraft had full situational awareness of the other's energy state and position. For line pilots, this incident underscores the importance of building an independent mental traffic picture even after receiving and reading back a clearance. The Delta crew's timely recognition of the conflict and their immediate go-around decision was the last effective barrier between a near-miss and a catastrophic collision. Controllers, for their part, are required to ensure separation exists before issuing a departure clearance into an active final approach corridor, and any delay in a crew's execution of that clearance demands a reassessment before the clearance remains valid.
Boston Logan presents particular complexity for surface operations. Its runway configuration includes multiple intersecting runways — 27, 33L, 33R, 04R/22L, and 09/27 — and simultaneous operations on crossing runways are routine during peak traffic periods. This environment places a premium on controller vigilance regarding sequence timing and crew execution gaps. The scenario of a crew holding short, receiving a clearance, and then delaying the roll while an aircraft descends through two miles final is one that demands real-time re-evaluation, particularly when the controller is managing multiple frequencies or traffic flows. Corporate and charter operators flying into Logan under Part 91 or Part 135 should ensure their crews are briefed on the airport's runway intersection complexity and the heightened risk of exactly this type of conflict during high-density departure and arrival periods.
The broader context is troubling. As the article notes, runway incursions represent one of the few categories of aviation incidents that have trended statistically worse in recent years, even as overall aviation safety continues to improve. The FAA and NTSB have both flagged this trend, and several high-profile near-collisions at U.S. airports in 2023 and 2024 — including incidents at Austin-Bergstrom, JFK, and Honolulu — have elevated the issue to a systemic concern rather than an isolated anomaly. Contributing factors under investigation across multiple events include staffing shortfalls in ATC facilities, increased traffic demand post-pandemic, and questions about crew complacency following long holds and delayed clearances. The FAA's Runway Safety Program has called for enhanced ASDE-X surface detection capability and improved pilot and controller training on intersection risk awareness, but implementation timelines and facility coverage remain uneven across the national airspace system.
For operators and chief pilots, this incident reinforces several standing best practices. Crews should never assume a departure or crossing clearance remains unconstrained simply because it was issued; if the execution is delayed for any reason, a check-in with the controller is appropriate before beginning a roll. Equally, crews on final should maintain independent awareness of intersecting runway traffic, particularly at airports with complex geometry, and should not defer a go-around decision pending controller instruction once a conflict is visually confirmed. The NTSB's preliminary report, expected within approximately 30 days, will likely clarify the precise lateral and vertical separation at the point of closest approach and may yield additional findings regarding controller task saturation and facility procedures at Logan. Until then, the incident stands as a stark reminder that procedural compliance at the clearance-delivery stage is not a substitute for dynamic situational awareness throughout the operation.