FAA Reviews Delta Go-Around After Boston Runway Close Call

The Federal Aviation Administration is investigating after a Delta Air Lines flight aborted its landing at Boston Logan International Airport to avoid a potential runway conflict with an American Airlines aircraft. The Delta crew performed a go-around and later landed safely.

The aircraft was approaching Boston Logan when an American Airlines plane was taking off from an intersecting runway, prompting the landing to be discontinued. AP reported on June 20, 2026, that the Delta flight had arrived from Dallas with 129 passengers and six crew members.

The Boston Logan go-around did what the safety system is designed to do: stop a landing when spacing, runway use or controller instructions create uncertainty. The fact that the aircraft landed safely does not make the incident irrelevant; it is exactly why investigators review close calls.

Go-Arounds Are Safe, but They Are Signals

The FAA has emphasized that go-arounds are standard aviation procedures. The review is about why this one became necessary, not whether the maneuver itself was unusual. Pilots train for them, controllers expect them and passengers may experience them without ever being in immediate danger.

That said, a go-around caused by a possible runway conflict is different from one caused by weather or an unstable approach. It asks investigators to examine communication, runway assignment, aircraft timing and whether all parties had the same picture of the airport surface. The review may also look at whether controller workload, radio congestion or runway geometry contributed to the moment when the landing crew had to break off.

A safe go-around can still reveal a weak point in how aircraft are being sequenced near the runway.

AP reported that air traffic control coordinated the maneuver and that the Delta flight later landed without incident. That is the operational success. The review now turns to whether the conflict should have been avoided earlier. Investigators can compare radar data, tower communications and runway timelines to see whether the aircraft were separated by procedure or by last-second correction. Boston Logan is a busy airport with intersecting runway operations that require tight coordination. The airport’s layout can make surface sequencing complex during busy periods, which is why investigators will look at timing rather than only at the final safe outcome. The airport’s layout can make surface sequencing complex during busy periods, which is why investigators will look at timing rather than only at the final safe outcome. In that kind of environment, seconds and spacing matter. A departure rolling on one runway can become relevant to an arrival on another before passengers see anything unusual from the cabin. Even when every crew acts correctly in the moment, traffic density can leave little room for misunderstanding.

Runway Incidents Draw Wider Scrutiny

The FAA review comes after several years of heightened attention on runway incursions and near misses at U.S. airports. Aviation safety is strong by historical standards, but the system depends on learning from events that end safely as well as those that end badly. Close-call reviews help regulators identify weak signals before they become accident patterns, especially at airports where traffic volume keeps pressure on controllers and crews.

Runway safety is not only about pilots seeing each other. It also involves controller workload, airport geometry, alerts, phraseology, equipment and the timing of takeoff and landing clearances.

In this case, AP said both American Airlines and the airport directed questions to the FAA. That is normal for an active federal review, but it also means the public account will remain limited until investigators release more detail.

The key factual questions are straightforward: where each aircraft was, what clearances had been issued, when the potential conflict became apparent and whether any automated or procedural safeguard worked as intended. Those answers may not point to one dramatic mistake; they may reveal smaller timing and communication issues that only matter when traffic is dense.

Passenger Confidence Depends on Transparency

For passengers, the distinction between a normal safety maneuver and a near-collision can be hard to parse. A sudden climb after nearly touching down feels alarming even if the cockpit and tower are handling the procedure correctly. Cabin announcements after events like this can help passengers separate a controlled safety maneuver from a more serious emergency. Cabin announcements after events like this can help passengers separate a controlled safety maneuver from a more serious emergency.

That is why clear public language matters. The FAA does not need to overdramatize the event, but it does need to explain the sequence well enough that people understand why the go-around happened and what will be checked. A clear timeline can reassure passengers while still being honest about the operational risk that prompted the maneuver.

The safest aviation systems are not the ones that pretend close calls never happen. They are the ones that treat a safely resolved event as evidence to study before the same pattern appears under worse conditions. That is why the FAA review matters even when the flight ended at the gate rather than in an accident report.