Federal investigators have published a preliminary account of a June 20, 2026 runway incursion at Boston Logan International Airport involving a Delta Air Lines flight and an American Airlines flight. No one was hurt, both jets completed their trips after a go-around, and the National Transportation Safety Board is still working toward a probable cause.
According to the NTSB Aviation Investigation Preliminary Report for incident DCA26LA242, Delta flight 2351, an Airbus A319, and American flight 3161, a Boeing 737-800, came into conflict after clearances on intersecting runways. CNN’s July 23, 2026 report on the same preliminary record adds controller and cockpit detail that travelers should treat as investigation facts, not as a new operational restriction at Logan.
- When and where: June 20, 2026, about 11:34 a.m. local at Boston Logan (BOS).
- Flights: Delta 2351 (A319) and American 3161 (Boeing 737-800), per the NTSB preliminary report.
- What happened: Intersecting runway clearances led to a conflict and a Delta go-around.
- Outcome: No injuries; both flights continued after the go-around sequence.
- Status: Preliminary only; full probable cause still under investigation.
What the preliminary report says happened
The NTSB says Delta 2351 was cleared to land on runway 33L while American 3161 was later cleared to take off on intersecting runway 27. That combination put the two Part 121 airliners on a path that required immediate separation action.
CNN’s account of the report says the American jet began its takeoff roll, stopped briefly after a cockpit error message, determined the alert was a false alarm, then continued. Delta pilots saw the developing conflict and aborted the landing, circling before landing safely.
At the closest point, the jets were about 670 feet apart, with hundreds of people onboard and no injuries reported. That distance is tight in runway geometry terms, which is why the NTSB opened a formal investigation even though the day ended without a collision.
Neither crew reported a cockpit collision-avoidance warning, according to the same reporting drawn from the preliminary file. The event is therefore about procedure, attention, and airport surface cues, not about a midair traffic-alert system failure that travelers can see on an app.
Why the tower sequence matters
CNN reports that the controller told investigators he saw the American flight start rolling, then focused on a smaller aircraft clearing the path for Delta. When a tower anti-collision alarm sounded, Delta pilots had already taken evasive action, and the controller described feeling confused.
Investigators also noted that the controller usually tilted paper flight strips when he cleared aircraft for takeoff, but American’s strip was not tilted. That detail is process evidence for the board, not a public instruction for passengers.
Stoplights that can warn of runway conflict extinguished after the small plane landed and did not light again until Delta was on final approach, according to the report coverage. Surface lighting and strip discipline are the kinds of systemic issues NTSB final reports often examine over many months.
Cockpit voice recorder audio from the relevant window had already been overwritten by the time investigators requested the recorders, because those units retain only about two hours of audio. Flight data recorders capture longer histories and remain part of the ongoing technical analysis.
What Boston travelers should and should not change
There is no passenger checklist that would have prevented this sequence. Seatbelts, early boarding, and app flight status do not control intersecting runway clearances.
The traveler-facing takeaway is residual confidence and itinerary realism, not a new security line or bag rule.
If you fly Logan in the coming weeks, expect normal operations unless the airport or FAA publishes a temporary surface procedure. Do not cancel a ticket solely because a preliminary report exists.
Do build buffer for weather and ATC delays the way you already should at a dense coastal hub. Morning banks, evening thunderstorms, and summer holiday peaks still drive more schedule risk than a single published investigation narrative.
Connecting passengers who rebook after any go-around still need the same tools: airline app messaging, same-day rebooking options, and a hotel plan if the last bank of flights is gone. Deep Arrival’s guide on where to stay in Boston helps when a late arrival turns into an overnight.
Southwest and other terminal choices still matter for walking times and security lines. Use the current Southwest at Logan Airport terminal guide when you plan a tight domestic connection rather than treating this investigation as a terminal move.
Cruise travelers using the Port of Boston should keep sea day and flight day buffers separate. A runway go-around is rare; a missed cruise embarkation is expensive.
Pair airport timing with the Boston cruise port guide when sail dates sit on the same day as a Logan arrival. If your cruise line requires all-aboard several hours before sailing, treat a same-day long-haul arrival as the higher-risk choice.
How to read a preliminary report without overreacting
An NTSB preliminary report is an early factual sketch. It is not a verdict, a fine, or a new airport operating rule for passengers.
Social posts often compress the story into a single scary number. Keep the full sequence: two clearances, a false cockpit alert, a go-around, and an investigation that is still open.
If your airline sends a schedule change, respond to that message. If it does not, keep your boarding pass and bag plan. The report does not invent a new document check at security.
Travel insurance and flexible fares still matter for ordinary Boston weather and ATC volume. Use them for the delays you are more likely to face than for a rare surface conflict already under federal review.
Parents and school-group organizers should keep the same pickup windows they already use at Logan. A go-around can add one circuit of the pattern, which is usually minutes, not an automatic overnight, unless crews or gates then cascade.
| If you are… | Do this next |
|---|---|
| Booked on Delta or American through BOS | Keep the trip unless your airline issues a flight-specific change; monitor the app for ordinary ops messages. |
| Connecting same day at Logan | Preserve at least a standard domestic connection buffer; do not cut it further because of this report alone. |
| Arriving late for a Boston hotel night | Confirm late check-in and backup lodging before you leave the origin city. |
| Sailing from Boston the same day | Avoid same-day morning flights when the embarkation clock is hard; prefer an overnight buffer. |
| Following the investigation | Treat the NTSB file as preliminary until the final probable cause report is issued. |
- No published passenger process change at Logan is required by the preliminary report alone.
- Go-arounds and surface conflicts can still create missed connections even when safety outcomes are good.
- Airline apps and rebooking tools remain the first response if your specific flight is delayed after a rare surface event.
- Boston overnight inventory and cruise embarkation buffers matter more than social media speculation about the report.
- The full NTSB investigation typically runs one to two years, so expect more technical detail later, not a next-day rule rewrite.
Did the planes collide at Boston Logan?
No. The NTSB preliminary report describes a runway incursion and a go-around with no injuries.
Closest approach was about 670 feet, per reporting drawn from the preliminary file.
Which flights were involved?
Delta flight 2351, an Airbus A319, and American flight 3161, a Boeing 737-800, according to the NTSB preliminary report for incident DCA26LA242.
Is Logan Airport closed or restricted because of this?
The preliminary report does not announce a passenger-facing closure or new screening rule. Fly the schedule your airline publishes unless you receive a flight-specific change.
When will the final cause be known?
NTSB probable cause determinations commonly take one to two years after a serious runway event. Treat current documents as preliminary facts only.
What should connecting passengers do differently?
Keep realistic connection buffers and know your rebooking path. This investigation does not replace ordinary weather and ATC delay planning at a busy hub.
