Flights slowly resume after East Coast air-traffic outage

Flights are gradually resuming at major airports along the US East Coast after a telecommunications failure at an air-traffic facility near Philadelphia triggered ground stops on Monday, snarling thousands of journeys and rippling delays across the country.

Airports move from standstill to slow recovery

Publicly available air-traffic data and news reports indicate that arrivals into Newark Liberty, New York’s John F. Kennedy and LaGuardia, Philadelphia International, Boston Logan and Teterboro largely restarted late Monday afternoon and evening, after hours of severe disruption linked to an equipment outage at the Federal Aviation Administration’s Philadelphia Terminal Radar Approach Control center.

According to flight-tracking figures cited in national coverage, more than 600 flights were delayed at Newark and Philadelphia alone during the height of the outage, with thousands of delays and cancellations recorded nationwide as airlines held or diverted aircraft away from the crowded Northeast corridor.

By early Tuesday, operations at the major East Coast hubs were described in multiple reports as “resuming” or “largely restored,” but schedules remained heavily backlogged, with airlines still repositioning aircraft and crews and many departures showing extended delays.

Travel press and airline advisories emphasized that even with the technical fault resolved, it could take a full day or more for normal operations to return across the network, particularly at slot-constrained hubs where there is little spare capacity to absorb disrupted flights.

What caused the disruption

According to detailed timelines compiled by Reuters and other outlets, the disruption began late Monday morning, September 21, when communications problems emerged at the Philadelphia radar approach facility that manages airspace for parts of New Jersey and Pennsylvania.

Transportation-focused reports state that an Amtrak construction crew working in New Jersey accidentally cut a fiber-optic telecommunications line used by the FAA, severing a primary circuit. When systems attempted to switch to a backup fiber route, technicians discovered that the backup line was also damaged, leaving controllers temporarily without stable radar and radio links.

The failure led the FAA to order ground stops or ground delays for incoming flights to several major airports, including Newark Liberty, Philadelphia, Teterboro, JFK, LaGuardia and Boston Logan, while controllers shifted to degraded procedures and engineers worked to restore full service.

By late afternoon Monday, officials reported that the affected telecom lines had been repaired and that regional airport operations were cleared to resume, although many flights remained out of position and airspace capacity was still constrained as traffic flows were gradually rebuilt.

Scope of impact across the Northeast corridor

Coverage from national newspapers and travel outlets describes the outage as one of the most disruptive air-traffic incidents in the Northeast in recent years, affecting a dense cluster of airports that together handle hundreds of thousands of passengers on a typical weekday.

At Newark Liberty, reports indicate that commercial arrivals were effectively halted for several hours during the middle of the day, with some long-haul flights diverted to alternate airports while short-haul services remained on the ground waiting for clearance.

Philadelphia International experienced repeated ground stops and extended delays as the host air-traffic facility worked through the equipment issues, while nearby Teterboro, a key business-aviation gateway for the New York region, also faced halted arrivals and diversions.

The ripple effects extended to Boston Logan and the New York City airports, where ground delay programs and slot restrictions were used to meter inbound traffic, leading to crowded terminals, missed connections and overnight rebookings for many travelers heading to or transiting through the corridor.

What travelers are seeing today

On Tuesday morning, airline status boards at major East Coast hubs showed a mix of on-time departures alongside clusters of delays and residual cancellations, reflecting what aviation analysts describe in published commentary as a “multi-day recovery” period after a large-scale disruption.

Carriers including United and other major network airlines have issued temporary waivers allowing affected passengers to change flights without standard fees, according to airline statements cited in travel and financial media.

Travel publications recommend that passengers flying into or through the Northeast over the next 24 to 48 hours monitor their airline apps closely, confirm departure times before leaving for the airport, and be prepared for gate changes or aircraft swaps as schedules are rebuilt.

Consumer advocates quoted in recent coverage also advise allowing extra connection time when itineraries route through New York, Newark, Philadelphia or Boston this week, noting that knock-on delays can linger even after official ground stops are lifted.

Questions over resilience of FAA systems

The outage has renewed scrutiny of the resilience of the US air-traffic system, particularly its dependence on critical telecommunications links that can be disrupted by construction accidents or localized equipment failures.

A recent report by a congressional watchdog, highlighted in national media, warned that certain aviation communication systems remain vulnerable to interference or deceptive messages, and urged regulators to accelerate modernization and cybersecurity protections.

Monday’s incident follows earlier communication and radar issues at the same Philadelphia-area facility in 2025, as well as other high-profile outages in recent years that have led to nationwide ground stops and prompted calls for additional investment in air-traffic technology.

Industry commentators note that while redundancy is built into many FAA systems, the combination of a severed primary circuit and a compromised backup fiber line in this case exposed a single point of failure, raising fresh questions about how infrastructure around key facilities is mapped, protected and tested before nearby construction goes ahead.