Logan Airport hit with 400+ delays as NYC ground stops snarl travel

Boston Logan International Airport was swept into a wider Northeast travel disruption after ground stops in the New York City area slowed traffic flows, sending ripple effects into Boston with more than 400 delays and dozens of cancellations.

What happened at Logan and why New York disruptions mattered

Published flight-tracking data and local coverage on Monday, September 21, 2026 showed Logan surpassing 400 delayed flights and topping 60 cancellations as air traffic constraints around New York throttled the movement of aircraft across one of the country’s busiest corridors. Some flights originally bound for New York-area airports were rerouted to Boston, adding pressure on gates, taxiways, and ramp operations at Logan.

The wave of delays at Logan reflected a network problem rather than a single-airport issue. When the Federal Aviation Administration initiates ground stops or flow restrictions at major hubs such as Newark Liberty, John F. Kennedy, and LaGuardia, airlines often experience cascading disruptions as aircraft and crews fail to arrive on schedule for later departures elsewhere, including Boston.

In Logan’s case, publicly available information also pointed to local operational factors that made the airport more vulnerable to gridlock. Massport has ongoing runway construction, and reduced arrival rates can quickly translate into longer lines for takeoff and fewer available gates, especially when diversions add unexpected aircraft to the airport’s schedule.

Equipment outage and air-traffic constraints across the Northeast

Coverage of the broader event described a technical failure that affected air traffic control operations tied to the New York region. Published reporting indicated damaged communications lines at a key FAA air traffic control facility in the Philadelphia area were repaired later Monday, allowing operations to resume after hours of disruption.

Regional impacts were substantial. Newark in particular faced a long period in which commercial arrivals were severely curtailed, and Philadelphia also logged large numbers of cancellations. While Boston was not the root cause of the outage, it absorbed secondary impacts, including airborne holding, delayed departures waiting for routes to reopen, and diverted aircraft needing parking and passenger processing.

Even after repairs, airlines typically need additional time to reposition aircraft and crews and to work through congested queues. That lag can keep delays elevated into the evening and can affect next-day schedules if flight crews time out or aircraft end the day at the wrong airport.

By the numbers: delays, cancellations, and average wait times

As of Monday evening, FlightAware’s airport summary for Boston Logan listed 455 total delays and 73 total cancellations for the day. Earlier afternoon coverage characterized the disruption as exceeding 400 delays and roughly 65 cancellations, with the totals shifting as airlines adjusted schedules and as traffic management programs changed throughout the day.

FAA delay information referenced in local reporting showed average delays around 105 minutes at Logan during the disruption window, with low cloud ceilings cited as a contributing factor. Weather factors can compound equipment or traffic-flow constraints by reducing the rate at which aircraft can arrive and depart safely, leaving less flexibility when the system is already strained.

Airline impacts were uneven across carriers, but some of Logan’s biggest operators were heavily affected. Local coverage highlighted Delta Air Lines and JetBlue among airlines with significant numbers of delayed departures from Boston as schedules were disrupted up and down the East Coast.

What travelers should do now if flying through BOS or NYC-area airports

For travelers departing Logan, the most practical step is to monitor the specific aircraft scheduled to operate the flight, not only the published departure time. In Northeast disruptions, the inbound plane may be delayed in New York, Philadelphia, or Washington airspace, and the departure at Boston may slide repeatedly even if the gate display initially shows only a short delay.

Passengers connecting through New York should expect irregular operations even after ground stops lift, because missed connections can trigger rebooking surges. Travelers with time-sensitive plans may want to check same-day options that avoid New York-area connections, including nonstop routes from Boston to final destinations when available, or routings through less-congested hubs depending on the airline’s network.

Travelers heading to Logan to meet arriving passengers should also watch for diversions and gate holds. When aircraft are diverted into Boston, ramp congestion can delay arrival-to-gate time even after the plane lands, which can push baggage delivery and curbside pickup well beyond scheduled arrival times.

Publicly available FAA notices and airline status tools can change quickly during rolling disruptions. Travelers are best served by checking flight status repeatedly before leaving for the airport, keeping receipts for eligible expenses, and building extra time into plans for baggage, rebooking lines, and ground transportation during peak congestion.