Delays Linger at Boston Logan After Major Northeast Outage

Some flight delays and schedule disruptions are still affecting Boston Logan International Airport after a major air traffic control telecommunications outage and ongoing runway construction combined to upend travel across the Northeast earlier this week.

Regional outage triggers widespread disruption

Published coverage indicates that the disruption began on Monday, September 21, when a telecommunications line used by the Federal Aviation Administration was severed during construction work in New Jersey. The cut fiber link affected air traffic control communications in the Philadelphia area and forced traffic management measures across several of the busiest airports in the United States.

Ground stops and severe flow restrictions were imposed at major East Coast hubs, including New York’s John F. Kennedy International, LaGuardia, Newark Liberty, Philadelphia International and Boston Logan. Reports from national and local outlets describe hundreds of cancellations and delays as controllers worked with reduced capacity, with ripple effects spreading quickly through the region’s tightly linked airspace.

At Boston Logan, publicly available data and local reporting show that nearly 500 flights were delayed on Monday, with average delays topping 100 minutes at the height of the disruption. Some services were diverted to or from other Northeast airports, while others remained on the ground for extended periods as traffic managers balanced constrained routes and arrival rates.

By Monday evening, transportation officials indicated that the underlying telecom problem had been repaired and that operations across the system were beginning to recover. However, Boston’s particular airfield conditions meant that the airport was slower to return to normal than some of its regional counterparts.

Runway construction amplifies delays at Logan

Separate from the telecom outage, Boston Logan has been operating with reduced runway capacity due to construction work that began earlier in September. Publicly available Federal Aviation Administration construction outlooks and traveler reports indicate that runway 9/27, a key east-west runway used for both arrivals and departures, is currently closed for safety and infrastructure upgrades.

The runway work limits the number of aircraft that can land and depart in a given period, especially during peak traffic times or when weather conditions restrict the use of other configurations. Aviation-focused coverage and online traveler reports ahead of the outage already described more frequent ground delay programs into Boston as air traffic managers worked around the construction schedule.

When Monday’s regional communications failure sent additional diverted flights toward Logan and constrained routes across the Northeast, the runway closure amplified congestion on the ground. With fewer available runways to absorb the extra arrivals and repositioning flights, surface congestion built up quickly, leading to long waits at gates and on taxiways even after the ground stops began to ease.

Massachusetts Port Authority, which operates Logan, had previously warned that travelers should expect longer-than-usual delays during the construction window, which is currently expected to extend into mid-November. The telecom outage effectively stacked an unplanned disruption on top of that planned capacity reduction.

Current status: residual delays but improving operations

As of Tuesday, September 22, real-time Federal Aviation Administration traffic tools and local broadcast coverage indicate that operations at Boston Logan are improving but not fully back to normal. Early-morning data showed a smaller number of delayed departures and arrivals compared with Monday’s peak, but delays were still present across several carriers and terminals.

The FAA’s national air traffic reports continue to list Boston among airports subject to flow management and occasional ground delay programs, reflecting both lingering schedule imbalances from the outage and the ongoing impact of runway work. Airlines are continuing to adjust flight times, swap aircraft and reroute crews to restore their networks, a process that typically takes at least one or two days after a disruption of this scale.

Travelers departing Boston on Tuesday and into Wednesday are being advised in local media coverage to monitor their flight status closely and to arrive at the airport with extra time. While security and check-in operations are reported to be functioning normally, gate changes and rolling delays remain possible as carriers recover their schedules.

Published accounts also note that some flights that were heavily delayed on Monday may be operating with adjusted departure times for several days, as airlines add buffer into schedules serving Boston to account for recurring flow constraints linked to the construction.

What travelers can expect in the coming days

Based on the current construction timeline and traffic management practices, residual delays at Boston Logan are likely to persist on busy travel days even after the immediate effects of the telecom outage subside. FAA construction documentation and industry commentary suggest that reduced runway capacity at Boston will remain a factor through at least mid-November, particularly during adverse weather or peak afternoon and evening banks.

In practical terms, this means that flights into and out of Logan may be more susceptible to ground delay programs, where aircraft are held at their departure airports to avoid overwhelming the limited arrival capacity in Boston. Travelers on routes that are already tightly scheduled, such as shuttle services along the Northeast Corridor, may notice more frequent schedule adjustments or slightly lengthened block times as airlines adapt.

Observers also point out that Boston’s role as both a domestic and transatlantic gateway adds complexity when the airport is operating at reduced capacity. Long-haul departures, which require longer runway occupancy and specific timing to meet curfews and connection banks overseas, must be carefully sequenced with dense short-haul traffic serving other New England and Mid-Atlantic destinations.

For travelers, the combination of factors makes advance planning particularly important over the next several weeks. Public information from airlines and local outlets consistently emphasizes the value of confirming flight status before leaving for the airport, allowing extra connection time when routing through Boston, and being prepared for gate or time changes on short notice.

Boston Logan within the broader Northeast picture

The incident has also drawn attention to the interdependence of major airports across the Northeast corridor. Analysis from aviation news outlets and transportation commentators notes that a single point of failure in air traffic communications infrastructure can affect operations at multiple hubs simultaneously, especially when those hubs are already operating near their capacity limits.

Boston’s experience this week illustrates how a regional disruption can be compounded by local constraints such as runway construction. While the telecom outage originated outside Massachusetts, its effects were magnified at Logan because the airport had less flexibility to absorb diverted and delayed flights.

Industry observers point to the episode as another example of the stresses facing the national airspace system, including aging infrastructure, complex construction programs at large airports and strong demand concentrated in a handful of coastal hubs. The incident is prompting renewed public discussion in transportation circles about redundancy in critical communications links and the pace of airfield modernization projects.

For the immediate future, travelers using Boston Logan can expect a gradual return to more typical operations, but with a higher baseline risk of delays while runway 9/27 remains out of service. The events of the week underline how quickly conditions can change when regional and local disruptions intersect, and why even a partial recovery in air traffic systems can still leave some airports facing persistent knock-on effects.