More news on this day
Hundreds of flights were delayed at Boston Logan International Airport on Monday, September 21, 2026, as a technical failure affecting air traffic control communications in the Northeast triggered ground stops, diverted aircraft into Boston, and rippled through airline schedules into Tuesday.
Get the latest news straight to your inbox!

What triggered the disruption across the Northeast
Published coverage indicates the interruption began when a primary communications circuit at a Federal Aviation Administration facility serving the region failed Monday morning. Reports also describe a backup fiber optic line being severed during railroad-related construction work in New Jersey, compounding the outage and leaving controllers without normal radar and communications links for a period of time.
The resulting loss of key communications capabilities prompted traffic management actions across multiple major airports in the New York and New Jersey corridor, including ground stops that kept aircraft from departing for affected destinations. As those restrictions spread, airports outside the immediate problem area, including Boston, absorbed diversions and dealt with aircraft and crews arriving out of sequence.
Later Monday, reports indicated the damaged communications lines had been repaired and flights began resuming across the region. Even with service restored, air travel systems typically require hours to unwind disruption, as aircraft, crews, gates, and maintenance schedules must be repositioned to rebuild a workable network.
How Boston Logan was affected and why delays piled up
Flight-tracking tallies reported more than 400 delays at Logan at points during Monday afternoon, along with dozens of cancellations. By late evening, published figures indicated delays had climbed further, with additional cancellations recorded as airlines adjusted to aircraft and crew displacement.
Boston’s role as a diversion point added pressure. With New York area arrivals constrained, aircraft headed for airports such as Newark and JFK were rerouted to alternatives including Logan, increasing demand for gates, ramp space, and baggage processing. Local television coverage described aircraft lined up and passengers being transported by bus for terminal processing after unscheduled arrivals.
On top of the regional communications breakdown, Logan’s own operating environment contributed to slower recovery. Reports referenced ongoing runway construction at the airport, which can reduce arrival and departure flexibility during peak disruption, and low cloud ceilings cited in federal airport-status information that can also reduce throughput by increasing spacing requirements between aircraft.
Regional picture: New York and Philadelphia disruptions drove knock-on delays
Airports across the New York City area experienced significant impacts, with Newark among the hardest hit. Published reporting described a lengthy window during which commercial arrivals were effectively paused, contributing to widespread cancellations and a backlog that carried into evening operations.
Philadelphia International Airport was also affected, with cancellations and delays reported as the region’s traffic management actions played out. When key hubs in a dense corridor like the Northeast slow down, airlines often face cascading constraints that extend beyond the immediate geography, because aircraft rotations and crew duty-time rules are planned across multiple cities and time zones.
For travelers, the practical consequence is that a disruption centered in one air traffic facility can show up as missed connections, rebookings, and extended ground holds hundreds of miles away. Boston, while not the epicenter of the outage, became one of the airports where passengers felt the aftershocks as the system tried to rebalance.
What travelers can do next and what to watch Tuesday
With operations reported as resuming Monday evening, the biggest variable for Tuesday is the pace of recovery: how quickly aircraft and crews return to their scheduled positions, and whether weather or runway constraints limit Logan’s ability to clear backlogs. Travelers departing early Tuesday may still encounter aircraft substitution, late inbound planes, and last-minute gate changes tied to Monday’s network disruption.
Publicly available federal flight-status tools can signal whether a ground delay program or other traffic management initiative is in place for Boston or nearby airports, and airline apps typically post rolling updates as flights are reassigned aircraft and crews. When disruptions are driven by air traffic control constraints rather than an airline-specific issue, delays often affect multiple carriers at once, especially on shuttle-style routes linking Boston with New York area airports.
For passengers holding tickets during the recovery window, the most useful steps are often to check flight status before heading to the airport, monitor rebooking options closely, and plan for longer-than-usual processing times if diversions and late arrivals continue. Even after flights restart, the operational reality is that a regionwide pause can take well into the next day to fully normalize.