A Delta Air Lines jet flying from Dallas comes screaming down toward the tarmac, ready to touch down. Suddenly, the pilots throttle the engines, pulling the nose up in a steep, unexpected climb. Just 300 feet below them on an intersecting runway, an American Airlines plane is tearing down the strip, taking off.
This isn't a scene from a movie. It happened at Boston Logan International Airport.
When two commercial airliners packed with hundreds of passengers get within 300 feet of each other on the ground, it's not a routine day at the office. Todd Curtis, a former Boeing safety engineer who tracks these events, analyzed flight logs and data from Flightradar24 to pinpoint that terrifyingly small gap. The Federal Aviation Administration is investigating. Capitol Hill is holding hearings. Honestly, it's about time.
Inside the Anatomy of a Go-Around
What went wrong in Boston? Delta Flight 2351, carrying 129 passengers and six crew members, had to execute a maneuver called a go-around. In plain English, they aborted the landing.
The aviation world likes to reassure the public that go-arounds are normal. The FAA states they are routine procedures performed at the discretion of pilots or controllers. That's technically true. Pilots train for them constantly. But pulling off a go-around because an entire American Airlines jet is occupying your path on an intersecting runway is a different story. That's a runway incursion, a fancy industry term for a near-miss that could have turned catastrophic.
Boston Logan is famous for its footprint of crisscrossing runways. It's a layout that demands absolute perfection from air traffic controllers and flight crews. On this particular Saturday, perfection didn't happen. The Delta crew coordinated quickly with the tower, climbed out of danger, circled back, and landed safely. Nobody was hurt. But relying on last-second pilot reflexes to prevent a mass-casualty event is a terrible strategy.
The Systematic Glitch We Aren't Fixing
This Boston incident is just the latest red flag in a system that feels like it's running on fumes. The Senate Commerce Subcommittee on Aviation, Space, and Innovation is gathering to address these close calls. They want to figure out how to strengthen safety across our national airspace.
We don't need another committee. We need answers to the real problems plaguing US airports.
- The Controller Shortage -> Air traffic control towers across America are severely understaffed. Existing controllers are working mandatory overtime, grinding through six-day weeks. Fatigue kills focus.
- Outdated Tech -> While commercial jets use highly sophisticated guidance systems, many ground radar systems at major hubs are decades old. Airport surface detection equipment needs major updates to keep pace with modern traffic volume.
- Skyrocketing Flight Volumes -> Airlines are pushing more planes into the sky than ever to meet demand. More planes mean narrower margins for error, especially at older legacy airports with tight runway configurations.
When you mix tired controllers, surging flight numbers, and intersecting runways, you get close calls. The fact that both planes involved in Boston had highly professional, experienced mainline crews makes it scarier, not less. If elite crews are getting caught in these traps, the underlying system is the issue.
What Needs to Change Before Our Luck Runs Out
Fixing this requires more than just standard slap-on-the-wrist investigations. If you want to see safer skies when you fly, the aviation industry has to shift its approach immediately.
First, stop normalizing near-misses. Every time a major airline spokesperson labels an emergency go-around as "routine," it minimizes the structural risk. It downplays the terrifying reality of what 300 feet actually looks like at 150 miles per hour.
Second, the FAA needs to accelerate the deployment of next-generation runway status lights. These are automated red warning lights embedded directly into the runway pavement that tell pilots if a runway is unsafe, completely independent of air traffic control communication. If a computer sees a conflict, the lights go red. It adds a crucial layer of safety that doesn't rely on a tired human voice over a static-heavy radio frequency.
Finally, we have to look at capping flight frequencies at airports with intersecting runway structures during peak hours until staffing levels catch up. It's a simple equation of volume versus capacity.
Next time you board a flight and hear the engines roar back to life during a final approach, know that the pilots are doing exactly what they were trained to do. But remember that they shouldn't have to dodge another airliner to get you home. Demand better funding for air traffic control tech and hold the airlines accountable for pushing the system to its absolute limits.
