Boston Logan International Airport has recorded hundreds of flight delays and dozens of cancellations after ground stops at New York City area airports and a regional air traffic control outage sent disruption cascading through the busy Northeast travel corridor early this week.

Get the latest news straight to your inbox!

Logan Airport hobbled by NYC ground stops and ATC outage

Ground stops in New York ripple north to Boston

Publicly available flight tracking data and published coverage indicate that the disruption began on Monday, September 21, when a telecommunications failure affecting air traffic control communications in the Northeast forced strict traffic limits into several New York area airports, including John F. Kennedy, LaGuardia and Newark Liberty. National airspace management tools show that regulators responded with a series of ground stops in the New York metropolitan area, temporarily halting many departures bound for the affected airports while the issue was addressed.

The New York restrictions quickly reverberated through the broader network. Reports from aviation data services show that flights operating between Boston and the New York region faced extended delays, diversions and, in some cases, cancellations as airspace capacity tightened along one of the country’s busiest corridors. With a high proportion of Boston’s short haul schedule tied into New York and mid Atlantic routes, even a few hours of reduced flow in the region translated into significant disruption at Logan.

According to regional and national coverage, repairs to the damaged communications lines were completed later on Monday, allowing traffic levels in the New York and Philadelphia airspace complex to begin recovering. However, the backlog of aircraft, crews and passengers built up during the ground stops left airlines working into Tuesday to re position aircraft and restore normal schedules, keeping knock on effects in place at Boston and other Northeast hubs.

Hundreds of delays, dozens of cancellations at Logan

Data summarized by local outlets and flight tracking dashboards indicate that Boston Logan recorded more than 480 delayed flights and upwards of 70 cancellations on Monday alone. Arriving and departing services were affected across all major domestic carriers, with disruption spreading from high frequency Northeast shuttles to longer haul routes as aircraft and crews were held out of position.

Federal flight status summaries cited in local coverage show that average departure delays at Logan peaked at around 105 minutes during the worst of Monday’s congestion, placing the airport among the most affected in the country for much of the day. Travelers reported long queues at check in and security as rolling delay estimates shifted through the afternoon, along with crowded gate areas as passengers waited for updated departure times.

By early Tuesday, September 22, publicly available operations data suggested an improving picture. General departure delays from Logan had eased to around 15 minutes or less for many flights, though residual disruption remained as airlines continued to cycle aircraft and crews back into their usual rotations. Some early morning departures showed knock on delays as aircraft arriving late the previous night were turned around for new flights.

Weather and runway work compound constraints

While the initial trigger for the disruption lay in the New York and Philadelphia airspace, conditions on the ground in Boston amplified the impact. Published coverage from local broadcasters notes that low cloud cover and poor visibility around Logan on Monday contributed to spacing requirements between arriving and departing aircraft, reducing the number of movements air traffic controllers could safely handle each hour.

Airport planning documents and recent traveler advisories referenced in aviation focused reports also point to a significant runway construction project underway at Logan this fall. A key runway that intersects several others is closed for roughly 75 days of safety related work scheduled into mid November 2026, including installation of an engineered materials arresting system designed to slow and stop aircraft that overrun the pavement.

The combination of adverse weather, limited runway capacity and upstream ground stops in New York left Logan particularly exposed to network stress. With fewer runways available and instrument conditions in place, the airport’s overall capacity was constrained at the same time that the wider Northeast system was struggling, increasing the likelihood that flights would be delayed, held on the ground at their origin, or canceled altogether.

What travelers experienced and what to expect next

Accounts shared in regional media describe passengers on some Boston bound flights being held at outstations or diverted as crews waited for new arrival slots into the constrained Northeast airspace. In other cases, travelers already aboard aircraft at Logan reported extended tarmac waits while departure times were repeatedly revised in response to updated flow restrictions related to New York.

Public advisories from the airport operator and airlines urged passengers traveling on Monday and Tuesday to monitor their flight status closely and to allow additional time at the airport. Information available through airline channels and national flight status tools showed that same day rebooking options were limited on some routes, particularly for peak hour services connecting Boston with the New York metropolitan region and major mid Atlantic hubs.

By Tuesday afternoon, published reports and operational dashboards indicated that conditions at both New York area airports and Boston were stabilizing, with significantly fewer new delays and cancellations than on Monday. Nevertheless, aviation analysts quoted in coverage of the outage cautioned that it can take several full schedule cycles for aircraft and crews to return to normal patterns after a major regional disruption, meaning some residual irregularities may persist through midweek.

How to navigate future disruptions on the Northeast corridor

The events of this week underline how closely linked Boston Logan is to the New York airspace complex. Publicly available Federal Aviation Administration tools and airline communications show that when ground stops or ground delay programs are in effect for New York area airports, Boston often experiences secondary impacts as flows along the corridor are reduced to accommodate constrained air traffic control capacity.

For travelers, recent coverage and airline guidance highlight several practical steps to reduce the risk of severe disruption. Morning departures from Logan are often less exposed to cascading delays than late afternoon and evening flights, since aircraft and crews are more likely to be in position at the start of the day. It can also be useful to review airline apps and flight tracking services before leaving for the airport, particularly when news reports point to weather systems, construction issues or technical outages affecting New York or other Northeast hubs.

Industry and government updates in the wake of this week’s outage note ongoing efforts to modernize air traffic control infrastructure and improve resilience in the Northeast corridor. Yet published airline filings and regulatory analyses also acknowledge that staffing challenges, complex airspace and major construction projects will continue to limit slack in the system. For Boston Logan, the runway work scheduled through November means that even routine weather or minor upstream disruptions could translate into elevated delay levels until full capacity is restored.