Two professional crews, doing everything right, came within 300 feet
At one of America's busiest airports on a Saturday afternoon, two commercial aircraft carrying more than a hundred souls came within 300 feet of each other — a margin measured not in miles but in stories of a building. The Delta crew's swift execution of a go-around averted catastrophe, but the incident joins a quiet accumulation of runway close calls that regulators and safety experts have long warned could one day not resolve so cleanly. As federal investigators open their inquiry and a Senate subcommittee prepares to convene, the episode invites a deeper question about whether the systems humanity has built to move millions through the sky are keeping pace with the complexity they were designed to manage.
- Two commercial jets came within 300 feet of each other at Boston Logan when a Delta flight descending from Dallas and an American Airlines plane beginning its takeoff roll converged on intersecting runways simultaneously.
- Aviation safety expert Todd Curtis, analyzing public radar data, called it a significant incident — made more unsettling by the fact that both aircraft were crewed by experienced professionals following standard procedures.
- The FAA launched an immediate investigation, with scrutiny expected to fall on radio communications, aircraft positioning, visibility conditions, and whether any procedural breakdown allowed the conflict to develop.
- All 135 passengers and crew aboard the Delta flight landed safely minutes later, but the closeness of the call has amplified pressure on regulators ahead of a Senate subcommittee hearing on runway incursions scheduled for Tuesday.
On a Saturday afternoon at Boston Logan International Airport, a Delta flight arriving from Dallas was on its final approach when an American Airlines aircraft began its takeoff roll from an intersecting runway. The two jets passed within 300 feet of each other — roughly the height of a nine-story building — before the Delta crew executed a go-around, pulling up and circling back to land safely minutes later. All 129 passengers and six crew members deplaned without injury.
The narrowness of the separation drew immediate attention from aviation safety experts. Todd Curtis, a former Boeing safety engineer, reviewed radar data from the incident and described it as significant — a characterization made more troubling, he noted, by the fact that professional crews operating under standard procedures were involved. Runway incursions, in which aircraft occupy the same runway space without clearance, have been a persistent concern for federal regulators, and this episode at one of the nation's busiest airports exemplifies the kind of close call that could escalate into something catastrophic if its causes go unexamined.
The FAA opened an investigation immediately. Investigators are expected to scrutinize radio communications between pilots and air traffic control, the precise positions of both aircraft, and whether any procedural lapse contributed to the conflict. Go-arounds are considered routine and safe maneuvers — but the fact that one was necessary at all raises questions about communication clarity, radar tracking, and the system's resilience against human error.
The incident arrives at a charged moment. Just three days later, the Senate Commerce Subcommittee on Aviation, Space, and Innovation is scheduled to hold a hearing examining runway incursions and safety protocols across the national airspace system. Whether Saturday's close call represents a near-miss the system successfully caught — or a warning sign that the system itself requires adjustment — is precisely the question that hearing will begin to confront.
On Saturday afternoon at Boston Logan International Airport, two commercial jets passed within 300 feet of each other in an unplanned encounter that forced one aircraft to abandon its landing approach. A Delta flight arriving from Dallas was descending toward the runway when an American Airlines plane began its takeoff roll from an intersecting runway. The Delta crew, working with air traffic control, executed what pilots call a go-around—pulling up and circling back to try again—to avoid a collision.
The Delta aircraft carried 129 passengers and six crew members. All of them landed safely minutes later after the aborted approach, deplaning without incident. But the narrowness of the separation—roughly the height of a nine-story building—caught the attention of aviation safety experts and federal regulators. Todd Curtis, a former Boeing safety engineer who now co-produces a podcast about flight safety, analyzed radar data from the incident using Flightradar24, a public flight-tracking website. His assessment was direct: this was a significant event, made more troubling by the fact that both aircraft were piloted by professional crews operating under standard procedures.
The Federal Aviation Administration opened an investigation immediately. Curtis noted that runway incursions—situations where aircraft or vehicles enter a runway without clearance, or where aircraft occupy the same runway space simultaneously—have been a persistent concern for federal aviation officials. The incident at Boston Logan exemplifies the kind of close call that regulators worry could escalate into something catastrophic if the underlying conditions aren't understood and corrected.
The timing of the near-miss is significant. Just three days after the incident, the Senate Commerce Subcommittee on Aviation, Space, and Innovation scheduled a hearing to examine runway incursions and safety protocols across the nation's airspace system. The Tuesday hearing will focus on strengthening safety measures and understanding why these incidents continue to occur at major airports despite decades of investment in air traffic control technology and training.
According to the FAA, go-arounds are routine procedures. Pilots or air traffic controllers initiate them regularly when conditions warrant—weather changes, traffic conflicts, runway obstructions. They are considered safe maneuvers, built into standard operating procedures. The Delta crew's decision to abort the landing was textbook airmanship. But the fact that such a maneuver was necessary at all, that two professional flight crews operating at one of the nation's busiest airports came so close to occupying the same airspace, raises questions about how clearly instructions are being communicated, how precisely radar and visual systems are tracking aircraft, and whether the current system has adequate safeguards against human error or miscommunication.
The investigation will likely examine radio communications between the pilots and air traffic control, the exact positions of both aircraft at each moment, visibility conditions, and whether any procedural lapses contributed to the conflict. What remains unclear is whether this was a near-miss that the system caught and corrected, or a warning sign that the system itself needs adjustment. The Senate hearing will begin to answer that question.
Citações Notáveis
This is a significant incident, particularly concerning because it involved two professional airline crews— Todd Curtis, former Boeing safety engineer
A Conversa do Hearth Outra perspectiva sobre a história
What made this particular incident significant enough to trigger a Senate hearing?
It wasn't just that two planes came close. It was that they came close while both crews were doing exactly what they were supposed to be doing—following standard procedures and communicating with air traffic control. That suggests the problem isn't pilot error or recklessness. It's something structural.
But go-arounds happen all the time, right? The FAA says they're routine.
They are routine. And that's partly why this matters. If a routine procedure at a major airport can result in a 300-foot separation between two commercial jets, then routine might not be safe enough anymore.
What would have happened if the Delta crew hadn't aborted the landing?
That's the question no one wants to answer. Two aircraft at the same altitude, on intersecting runways, at the same moment. The physics of that collision would be catastrophic for everyone on both planes.
So this is about the system failing, not the people in it.
Exactly. The crews performed correctly. Air traffic control was doing its job. But somewhere in how information flows, how clearances are issued, how runways are managed—something allowed two aircraft to get that close. That's what the Senate wants to understand.
Is Boston Logan uniquely dangerous, or is this happening everywhere?
Boston Logan is busy, but it's not unique. The hearing is about runway incursions across the entire national airspace system. This incident just made the problem visible.