Logan delays mount as NYC-area ground stops snarl Northeast

Boston Logan International Airport is wrestling with hundreds of flight delays and cancellations after a major air traffic control outage and a series of ground stops at New York City–area airports rippled across one of the country’s busiest travel corridors.

Logan faces long waits as disruptions spread north

Publicly available flight tracking data and local broadcast coverage on Tuesday, September 22, indicate that Logan International Airport saw some of the worst knock-on impacts in New England from the air traffic turmoil centered on the New York and Philadelphia region. A combination of ground stops at New York City–area airports and low clouds over Boston pushed average departure delays at Logan to around 105 minutes at the height of the disruption, according to Federal Aviation Administration operational summaries cited in regional news reports.

CBS Boston reported that by midmorning Tuesday, Logan had logged hundreds of delayed flights and a significant number of cancellations as airlines struggled to reposition aircraft and flight crews after the previous day’s outage. The Federal Aviation Administration’s public dashboard showed a ground stop at Boston attributed to airport volume during portions of the disruption, while a separate advisory pointed to a low cloud ceiling as another constraint on arrivals and departures.

Terminal departure boards and airline apps reflected rolling delays throughout the day, affecting both mainline carriers and regional affiliates serving cities such as New York, Washington, D.C., Chicago and Atlanta. While some flights were able to depart only slightly behind schedule, others faced holds at the gate or on the taxiway as air traffic controllers spaced out departures into already congested Northeast airspace.

Boston 25 News coverage indicated that travelers were urged to check flight status frequently and arrive with extra time, as security checkpoints and gate areas grew crowded during peak bank periods. With many aircraft out of position, airlines consolidated some departures and offered rebooking options for passengers willing to shift travel to later in the week.

Technical failure in Philadelphia triggers NYC ground stops

The disruption originated Monday, September 21, when a critical circuit supporting air traffic control communications in the Philadelphia area experienced a failure, according to regional broadcast and wire service reports. That outage affected the terminal radar approach control facility responsible for sequencing aircraft into several major Northeast airports, including Newark Liberty International, John F. Kennedy International, LaGuardia and Philadelphia International.

Published coverage from Axios and other national outlets describes how the failure prompted the FAA to order ground stops at multiple airports around midday Monday, temporarily halting departing flights destined for the affected fields. The move was designed to prevent additional aircraft from entering already constrained airspace while specialists worked to restore data flows and reroute traffic around the affected circuits.

As operations slowed at those major hubs, the impact quickly radiated outward. Airlines that rely on New York and Philadelphia for connections and crew bases began holding or canceling flights systemwide, including services into and out of Boston. Even aircraft that did not transit the affected airspace sometimes faced disruption because their inbound legs or crews were stuck at grounded airports farther south.

By Monday evening, transportation officials publicly stated that repairs to the damaged communications lines were largely complete and that a return to normal operations was underway. However, the backlog of delayed flights and the complex choreography of aircraft and crew scheduling meant that disruptions continued into Tuesday across the Northeast, including at Logan.

Runway work and weather amplify congestion at Logan

The New York–area ground stops hit Logan at a time when the airport was already more vulnerable to delays due to ongoing runway construction and seasonal weather. Aviation industry analysis in recent weeks has highlighted Boston’s closure of Runway 9/27 for an extended period of safety work beginning at the end of August, temporarily reducing the airport’s capacity during certain wind and traffic conditions.

Specialist aviation outlets note that with one of Logan’s key runways offline, controllers have less flexibility to adjust operations when coastal storm systems or low clouds roll in. A routine weather pattern that might previously have produced moderate delays can now result in far longer waits, as arrivals and departures are consolidated onto fewer runways and spacing between aircraft increases.

The FAA’s public operational summaries on Monday and Tuesday referenced both volume and weather constraints at Boston, reinforcing the picture of an airport operating near its current limits. On some recent days, separate from this week’s outage, data compiled by delay-tracking services has shown average ground delays at Logan exceeding two hours during peak afternoon and evening windows as traffic bottlenecks on remaining runways.

Travel forums and recent passenger accounts also point to a pattern of longer-than-usual taxi times at Logan this month, with some flights waiting on the ground after landing for an available gate, or holding short of the runway for extended periods prior to departure. The combination of construction, fall weather systems and the latest Northeast air traffic control failure has created a challenging environment for on-time operations.

New York airspace pressures are a recurring flash point

The latest disruptions underscore how tightly linked Boston’s air traffic fortunes are to the chronically congested New York City airspace. Federal rulemakings and policy documents over the past several years have repeatedly highlighted staffing constraints at the New York Terminal Radar Approach Control facility, known as N90, and the persistent risk of delays at JFK, LaGuardia and Newark during peak travel periods.

In response to those structural pressures, the FAA has periodically ordered airlines to trim schedules at major New York airports, including an order limiting operations at Newark that has been extended several times. Separate notices have temporarily relaxed minimum slot usage rules at JFK and LaGuardia to give airlines more flexibility to cut flights without losing long-held operating rights. Those measures are aimed at reducing overall volume in one of the nation’s most complex airspace systems.

Despite those efforts, the chain reaction from this week’s circuit failure demonstrates how a single technical problem can still cascade through the network. When departures are paused at multiple New York–area airports, aircraft that would ordinarily cycle quickly between Boston and New York instead remain parked, and crews can reach duty-time limits while waiting out the disruption. The result is a wave of cancellations and missed connections that can take more than a day to unwind.

Regulatory filings and past performance reviews also show that the most delay-prone hours at New York airports overlap closely with Boston’s busiest departure banks. That overlap leaves carriers little slack when conditions deteriorate simultaneously in both markets, a scenario that played out across the Northeast at the start of this week.

What travelers through Boston should expect next

Airline network planners and airport officials across the region are now focused on clearing the backlog of displaced passengers and aircraft. According to local television coverage citing airline statements, carriers at Logan have been adding larger aircraft on some routes where possible, consolidating multiple lightly booked flights into a single departure to move more passengers with limited slots.

Boston 25 News reports that travelers with flights scheduled in the days following the outage are being advised to monitor airline apps and email notifications closely, as schedule adjustments and gate changes continue while operations stabilize. Same-day standby options may be limited on heavily booked routes along the Northeast Corridor, although some airlines are waiving change fees or fare differences for affected customers under temporary travel advisories.

Northeast-focused carriers are also encouraging passengers connecting onward through New York or Philadelphia to build in additional time and to consider earlier flights where practical, given the lingering potential for delays while crews and aircraft rotate back into position. For early morning departures from Logan, airport guidance continues to emphasize arriving at least two hours before domestic flights and three hours before international departures, particularly during school vacation periods and major events in the city.

While operations began trending closer to normal levels by late Tuesday, publicly available flight-status boards still showed clusters of delayed departures on some New York and Mid-Atlantic routes, reflecting the complexity of resetting airline networks after a large-scale disruption. For now, travelers through Boston can expect a somewhat smoother experience than at the peak of the outage, but with a continued risk of knock-on delays whenever the New York airspace system comes under strain.