The first warning at Boston Logan on Saturday did not come from the control tower. It came from the cockpit of a Delta Air Lines jet already over the runway threshold, seconds from putting its wheels down, when the crew saw an American Airlines jet accelerating across their path and called their own escape: going around.
That split-second decision is now the centre of a federal inquiry. The Federal Aviation Administration is investigating what it classifies as a runway incursion — its highest-priority category of safety event — after Delta Flight 2351, arriving from Dallas, was forced to abort its landing at Boston Logan International Airport around 11:30 a.m. local time on Saturday, 20 June 2026, to avoid a departing American Airlines aircraft on an intersecting runway.
No one was hurt. The Airbus A319, carrying 129 passengers and six crew, climbed away, circled and landed safely a short time later, deplaning normally. By the cold arithmetic of aviation, it was a non-event: a routine manoeuvre, executed correctly, ending in a delayed arrival and nothing worse. By the standard the FAA actually cares about, it was the opposite — because the manoeuvre should never have been necessary.
In a statement, the agency laid out the bare sequence without assigning blame. The crew of Delta Air Lines Flight 2351 executed a go-around at Boston Logan International Airport because another aircraft was departing from an intersecting runway,
the FAA said, adding that it is investigating the event.
American Airlines and the airport operator both referred questions to the FAA, according to reporting from the Associated Press.
The geometry is what makes the episode unsettling. Logan was landing arrivals on Runway 33L, the airport’s longest strip at just over 10,000 feet, while departures were rolling from Runway 27 — a runway that crosses 33L not far beyond the touchdown zone. Aviation outlets tracking the flights identified the departing aircraft as American Flight 3161, a Boeing 737 bound for Charlotte. As Simple Flying reconstructed it, the Delta crew were essentially on top of the threshold, committed to landing, when they spotted the American jet building speed from their right and broke off the approach themselves.
Aviation reporter JonNYC shares early details of the Boston Logan go-around, 20 June 2026.
Some of the more dramatic figures circulating — that the aircraft closed to within a few hundred feet of altitude, or half a mile laterally — come from flight-tracking data parsed by aviation analysts, not from the FAA, which has not released official separation numbers and likely will not until its review is complete. What is not in dispute is the shape of the error: two aircraft were operating on runways that intersect, and the conflict was caught by pilots looking out the window rather than by the system that is supposed to keep those paths from crossing in the first place.
That distinction matters because a go-around is not a failure. It is the safety net functioning exactly as designed; commercial crews train for it constantly, and the FAA is careful to note that aborted landings are safe, discretionary procedures. The worrying part sits upstream, in the tower, where a takeoff clearance and a landing clearance ended up pointed at the same patch of concrete. Untangling how that happened — controller workload, timing, the sequencing of two intersecting runways during a busy late-morning push — is the actual work of the investigation, and it is where Logan’s specific layout will get scrutiny.
The timing does the story no favours. The near-miss landed in the middle of a grim fortnight for American aviation. A U.S. Air Force B-52 bomber crashed during a test flight in California, killing all eight aboard; twelve people died when a skydiving plane went down in Missouri; a business jet crashed in Laredo, Texas; and, on the same Saturday as the Logan scare, a small plane crash in western France killed Ubisoft co-founder Claude Guillemot. Read together, the run of headlines feels like a system under strain. Read apart, the Logan event belongs to a different category entirely — a save, not a casualty — and conflating the two does a disservice to what each actually shows.
Still, the public does not parse those categories in real time, and a string of close calls at major U.S. airports over the past year — at Newark, at Reagan National, at JFK — has already worn down the assumption that the busiest hours at the busiest fields are comfortably routine. Boston’s case will be measured against that pattern. Whether it reads as a one-off slip or as evidence of something more systemic depends entirely on what the FAA finds in the tower tapes, and that answer, like the separation figures, will take time. For now the most honest summary is also the most reassuring and the most uncomfortable at once: the layers held, and they should not have had to.
