A near-collision at Boston Logan International Airport has intensified concern over airspace safety in the United States, after Delta Air Lines Flight 2351 was forced into a dramatic go-around to avoid an American Airlines jet that had entered an intersecting runway on Saturday morning.

Get the latest news straight to your inbox!

Near-Collision at Boston Logan Sparks FAA Safety Probe

Close Call Over Boston as Aircraft Converge

Publicly available flight-tracking data shows that Delta Flight 2351, an Airbus A319 arriving from Dallas, was on final approach to Boston Logan late Saturday morning when its descent was abruptly discontinued and the aircraft climbed away from the runway. Reports indicate that an American Airlines aircraft was departing from an intersecting runway at the same time, creating a potential conflict in the shared airspace over the airfield.

Analyses of the flight paths by aviation specialists suggest the two jets passed within several hundred feet vertically and a short distance horizontally before the Delta crew initiated the go-around procedure. Some assessments place the vertical separation at roughly 300 feet at the closest point, a margin considered uncomfortably tight for two large commercial airliners operating near the ground.

According to published coverage, the Federal Aviation Administration has opened an investigation into the event, describing it as a “close call” that warrants a detailed review of air traffic control instructions, cockpit decision-making, and runway use at the time. Both aircraft completed their respective flights without physical damage, and no injuries were reported among passengers or crew.

Boston Logan, one of the busiest airports in New England, relies heavily on intersecting runways to manage peak-period traffic. While such configurations are common at older, space-constrained airports, they require precise coordination of arrivals and departures to maintain safe separation margins.

Delta Flight 2351’s Emergency Go-Around

Delta Flight 2351 was carrying 129 passengers and six crew members on the Dallas to Boston route when the pilots elected to abandon their landing and climb away from the runway environment. Publicly available information from the airline indicates that the crew coordinated with air traffic control to execute what is known as a go-around, a maneuver that transitions an aircraft from landing configuration back to a climb.

Tracking data shows the jet descending steadily toward Logan before the flight path suddenly arcs upward, signaling the shift to full power and a return to safer altitude. Aviation reference materials describe go-arounds as standard procedures that pilots train for repeatedly in simulators, designed precisely to handle unexpected runway incursions, unstable approaches, or rapidly changing conditions near the ground.

Despite the routine nature of the maneuver from a technical perspective, the timing and context of this particular go-around have drawn widespread attention. The incident occurred during clear visibility and in a controlled environment, involving two major U.S. carriers operating regularly scheduled flights. Analysts note that this combination places the episode squarely in the broader pattern of high-profile close calls at major American airports in recent years.

Passengers on board the Delta flight ultimately deplaned normally after the crew brought the aircraft back for a subsequent, uneventful landing. While many such events pass with little notice, the proximity of the other jet and the heightened focus on runway safety across the country have turned Flight 2351 into a focal point in the debate over airspace resilience.

FAA Investigation and Runway Safety Concerns

The Federal Aviation Administration has classified the event as a serious incident and is gathering radar records, cockpit voice and flight data recorder information, and controller tapes to reconstruct the sequence of clearances and responses. According to publicly reported summaries of the probe, investigators are expected to examine whether standard separation rules were compromised and how quickly the developing conflict was recognized in the tower and on both flight decks.

Runway incursions and near-miss events have remained a persistent concern in the United States, prompting congressional hearings, internal safety reviews, and new technology trials to reduce the risk of collisions during takeoff and landing. Data highlighted in recent public discussions in Washington points to a pattern of serious close calls at several large airports, with some incidents coming within seconds of disaster.

Boston Logan’s runway layout, which features multiple intersecting runways and complex taxiway geometry, often appears in professional discussions about air traffic workload and situational awareness. While the configuration allows the airport to manage heavy traffic within a constrained footprint, it also demands high levels of vigilance from controllers and crews, particularly during busy late-morning and early-evening banks when arrivals and departures converge.

Safety advocates argue that the Boston incident underscores the need to accelerate deployment of advanced surface surveillance tools, automated conflict alerts, and standardized procedures to reduce the risk of human error. Others note that, viewed from another angle, the safe handling of the event demonstrates that existing training and procedures remain effective when crews and controllers respond promptly.

Go-Arounds: Rarely Dramatic, Routinely Practiced

Although the Logan episode gained attention for the narrow separation involved, aviation safety literature emphasizes that go-arounds are a fundamental part of modern airline operations worldwide. Industry data frequently cited by pilots indicates that a small but steady fraction of approaches each year are discontinued for reasons ranging from changing winds and runway contamination to traffic conflicts and unstable flight paths.

Training curricula at major airlines incorporate repeated practice of go-arounds at various phases of approach, including low-altitude maneuvers close to the ground. The objective is to ensure that crews can shift from landing to climb quickly and without confusion, even when the initial decision to go around comes from air traffic control rather than from the pilots themselves.

For passengers, the sensation of a sudden climb just before touchdown can feel alarming, particularly if there is no immediate announcement explaining the maneuver. Travel forums and prior passenger reports describe surprise and anxiety when engines spool up and the aircraft pitches skyward moments before landing. Safety professionals, however, consistently describe go-arounds as a sign of caution rather than of impending danger.

In the Logan case, publicly available reporting shows that Delta Flight 2351 followed the textbook pattern of a safe go-around. The jet re-entered the traffic pattern, regained stable spacing from other aircraft, and landed without further incident, reinforcing the notion that executing a go-around is often the safest available option when any uncertainty arises on short final.

Implications for Summer Travel Through Boston

The near-miss arrives as U.S. carriers prepare for one of the busiest summer travel seasons on record, with Boston Logan serving as a key gateway for both domestic and transatlantic flights. For travelers connecting through the airport in the coming weeks, the incident may raise fresh questions about congestion, staffing, and the resilience of the systems that keep high-density airspace operating safely.

Industry observers suggest that the Logan event will likely feed into broader national discussions about controller workload, modernization of radar and surface movement technology, and investment in airport infrastructure. Some experts argue that recurring close calls at multiple hubs point to systemic strains in the national airspace system rather than isolated lapses at individual facilities.

For now, public data indicates that operations at Boston Logan have continued largely as normal, with no widespread disruptions attributed to the incident. Travelers are unlikely to notice visible changes beyond the usual patterns of routine delays and weather-related adjustments that mark busy summer days at major airports.

Behind the scenes, however, the investigation into Delta Flight 2351 is expected to generate detailed recommendations on procedures, training, and technology. For frequent flyers and occasional travelers alike, the episode serves as a reminder that, even amid moments of alarming proximity, layers of safety training and standardized responses can turn a potentially catastrophic airspace failure into an unsettling story rather than a tragedy.