Logan Airport hit by 480-plus delays amid NYC ground stops

Travelers moving through Boston Logan International Airport on Monday, September 21, faced severe disruption as more than 480 flights were delayed and over 70 were canceled, after ground stops at New York City area airports and a regional air traffic control outage rippled across the Northeast.

How a fiber line failure in the New York region stalled Boston

According to published coverage and flight-tracking data, the disruption began with a communications failure tied to damaged fiber-optic lines serving a key air traffic control facility in the New York–Philadelphia corridor. The outage prompted the Federal Aviation Administration to order ground stops at multiple New York City area airports on Monday, abruptly reducing the flow of arrivals and departures through one of the country’s busiest airspace complexes.

Reports indicate that traffic at Newark Liberty International Airport was among the hardest hit, with hundreds of cancellations and long gaps in arriving commercial flights while technicians worked to restore service. The restrictions quickly cascaded into LaGuardia and John F. Kennedy airports, limiting departures there and forcing airlines to hold planes on the ground at origin airports across the Northeast.

With aircraft and crews unable to move through New York as scheduled, Boston’s Logan Airport was pulled into the disruption. Flight-tracking summaries cited by local outlets show that by late Monday, Logan had recorded roughly 480 delayed flights and in the range of 70 to 80 cancellations, as airlines struggled to reposition aircraft and restart normal rotations.

Publicly available national airspace status data show that Logan was placed into a ground delay program for portions of Monday afternoon and evening. That traffic management measure reduced the rate at which flights could depart for Boston, extending delay times while controllers balanced limited arrival slots with heavy demand across the region.

Runway construction and local constraints added to the crunch

While the initial trigger was the New York area communications outage, Boston-area coverage notes that Logan’s own operating environment made the airport particularly sensitive to the disruption. Ongoing runway work has reduced flexibility on the airfield, with one of the primary runways partially unavailable due to an infrastructure project scheduled to last into the autumn.

Massport materials and local reporting describe current work on safety and runway improvements, including installation of an engineered material arresting system at one runway end and broader pavement and taxiway upgrades. Those projects, combined with seasonal traffic levels, have already led to more frequent use of ground delay programs when weather or upstream constraints limit the airspace around Boston.

On Monday, that existing pressure met the New York region outage. With fewer runway configurations available, Logan had less room to absorb diverted aircraft and schedule changes from other Northeast airports. Some flights originally bound for New York were diverted into Boston, while delayed departures from Logan waited for crews or aircraft still tied up in Newark or Philadelphia.

Data from flight-tracking services cited in local coverage show average delays at Logan stretching to around one hour and 45 minutes at the peak of the disruption. Late-evening departures experienced rolling pushbacks as airlines attempted to clear backlogs while staying within crew duty limits and available gate space.

Tuesday operations improve, but residual delays linger

By Tuesday morning, September 22, publicly available information from the air traffic system showed that the underlying communications issue had been repaired and that New York area ground stops had been lifted. Airlines were gradually resuming normal operations, though schedules remained out of position after the previous day’s cancellations.

Local broadcasts from Boston on Tuesday reported that Logan’s situation had improved sharply compared with Monday. Early-morning tracking data showed a few dozen delays and only a small number of cancellations, far below the levels logged during the outage but still elevated compared with a typical weekday.

Travelers passing through the airport were advised in public reports to continue monitoring their flight status closely, especially for connections involving New York City or Philadelphia. Airlines were still working to reassign aircraft and crews, meaning some departures could face last-minute retimings even as overall traffic levels normalized.

FAA airport status summaries on Tuesday indicated that Logan continued to experience modest departure delays, in part due to ongoing runway construction and residual congestion from Monday’s disruptions. However, arrival and departure rates were generally closer to normal, and no broad ground stop was in effect for Boston.

What the disruption means for Northeast travelers

The events at Logan highlight how tightly linked the major airports of the Northeast corridor have become. Published analyses of Monday’s outage note that large numbers of flights into and out of Boston rely on aircraft and crews that also serve Newark, LaGuardia, Kennedy, and Philadelphia, often on rapid-turn schedules that leave little margin for a systemwide shock.

When a ground stop or air traffic control issue slows the New York region, the aircraft scheduled to operate a Boston departure may be delayed or canceled at its origin, even if skies over Logan remain clear. That pattern was visible on Monday, as some Boston passengers reported multiple rolling delays before an eventual cancellation once crews exceeded duty limits or inbound aircraft never arrived.

For travelers planning near-term trips, publicly available tracking data and airline advisories suggest that most of the acute disruption from the outage has passed. Nonetheless, Logan is expected to remain somewhat more delay-prone through the autumn while runway work continues, particularly during peak afternoon and evening periods or when storms, low clouds, or new traffic management initiatives affect the broader Northeast.

Travel experts and airline operations materials emphasize that during episodes involving ground stops or large-scale delays, monitoring the status of the inbound aircraft and using airline mobile apps can offer more timely clues than static departure boards. Rebooking to earlier flights, considering alternate routings that avoid the most constrained hubs, or allowing extra connection time can help reduce the risk of becoming stranded when a regional outage sends ripples across the network.