A severed fiber-optic cable in New Jersey triggered a major communications outage for the Federal Aviation Administration this week, prompting ground stops at several of the busiest airports in the U.S. Northeast and unleashing a wave of delays and cancellations for travelers across the region and beyond.

Get the latest news straight to your inbox!

FAA fiber cut in New Jersey snarls Northeast air travel

Fiber cut in New Jersey knocks out key FAA backup line

Publicly available information indicates that the disruption began on Monday, September 21, when a primary communications circuit failed at the FAA’s Philadelphia Terminal Radar Approach Control facility, which manages approach traffic for several major Northeast airports. The system attempted to switch to a backup telecommunications feed designed to provide redundancy, but that backup line was already out of service after being accidentally severed at a construction site in New Jersey.

Transportation reporting and telecom statements describe the damaged infrastructure as a Verizon fiber-optic cable running along an Amtrak rail corridor between New Brunswick and North Brunswick, New Jersey. Construction activity in the area reportedly cut through several hundred feet of the cable, leaving the FAA facility without its intended fallback connection when the primary circuit failed.

Coverage from aviation and travel outlets notes that the combination of the blown circuit and the pre-existing fiber damage left controllers temporarily without the level of communications capacity required to safely handle normal volumes of arrivals and departures into the region’s airspace. As a result, the FAA initiated ground stops and other traffic management measures while technicians worked to stabilize and reroute systems.

Telecom providers have indicated that repairs to the damaged fiber segment were completed later the same day, with service gradually restored as network engineers spliced and tested replacement sections of the cable. However, the temporary loss of both the primary and backup paths had already cascaded through airline schedules, triggering disruptions that continued into the following day.

Ground stops ripple across Newark, New York and Philadelphia

According to flight tracking data and airport status reports, the outage prompted the FAA to halt or sharply restrict inbound traffic to a cluster of key Northeast gateways, including Newark Liberty International Airport, New York’s John F. Kennedy International Airport, LaGuardia Airport, Philadelphia International Airport and Teterboro Airport in New Jersey.

At Newark Liberty, published coverage indicates that commercial arrivals were effectively suspended from around 9:40 a.m. until shortly after 5:20 p.m. local time on Monday, bringing one of United Airlines’ largest hubs close to a standstill. Many departures were also held at gates or on taxiways as air traffic managers throttled flows into the congested New York–New Jersey airspace.

Philadelphia International Airport saw similar disruption. Local reports citing FlightAware data put Monday’s toll at roughly 400 delays and about 200 cancellations at PHL alone, as the FAA ground stop kept arriving flights on hold for much of the day. Airlines diverted some aircraft to other cities, while others waited on the ground at their origin airports for clearance to depart toward Philadelphia.

The disruption extended northward as well. New York–area airports experienced a mix of outright ground stops and ground delay programs, with departing flights required to wait for assigned slots before taking off toward the region. Business aviation hub Teterboro was also affected, limiting private and corporate operations that normally use the smaller airport to avoid congestion at the larger commercial fields.

Thousands of travelers face delays, diversions and missed connections

For passengers, the technical failure translated into hours of uncertainty and a patchwork of delays, diversions and rebookings. Airline status boards across the Northeast filled with red as carriers held aircraft, rerouted crews and reshuffled fleets in response to the evolving traffic limits.

Data from flight tracking services show that several hundred flights were canceled outright across the affected airports on Monday, while many more departed significantly late. Travelers connecting through Newark and Philadelphia, in particular, faced high risks of missed onward connections as inbound aircraft arrived hours behind schedule.

Disruption spread well beyond the immediate region. West Coast and Midwest departures bound for Newark, New York and Philadelphia were subject to extended ground holds while traffic managers worked to meter arrivals into the constrained airspace. Some long-haul flights that had already departed for the Northeast were placed in holding patterns or diverted to alternate airports to wait out the restrictions.

Reports from Boston and other secondary Northeast airports indicate that the outage also contributed to knock-on delays where carriers rely on aircraft that rotate through the New York–Philadelphia system. Even after the FAA lifted formal ground stops late Monday afternoon, residual delays persisted into Tuesday as airlines repositioned aircraft and crews and worked through backlogs of stranded passengers.

Recovery timeline and what travelers should expect next

By Monday evening, the FAA reported that communications capabilities for the affected air traffic control facility had been restored, allowing full operations to resume at Newark, Philadelphia, Teterboro, JFK and LaGuardia. Airlines began operating a recovery schedule, attempting to bring aircraft and crews back into their normal positions and accommodate displaced passengers on remaining seats.

Transportation coverage notes that ground stops at the major hubs were lifted around late afternoon to early evening local time, with some airports transitioning first to ground delay programs before eventually returning to standard flow rates. Nevertheless, airline operations are tightly interlinked, and a full day of schedule disruption in such a dense corridor can take 24 hours or more to unwind.

Travel industry reports advise passengers with flights through the affected airports over the next one to two days to check their flight status frequently and to monitor airline apps or email notifications for involuntary rebookings or gate changes. Same-day schedule changes and rolling delays remain possible as carriers balance crew duty time limits, maintenance requirements and airport slot controls.

Many major airlines have issued limited travel waivers for customers ticketed to, from or through the impacted airports on September 21 and, in some cases, September 22, allowing rebooking without change fees within a specified date window and fare conditions. The precise terms vary by carrier, and travelers are being directed through public advisories and customer service channels to review their options.

Questions raised about redundancy and infrastructure resilience

The incident has already prompted scrutiny of how a combination of a single circuit failure and a construction-related fiber cut could affect operations at such a critical air traffic control facility. Engineering and aviation commentators note that the Philadelphia approach control center manages dense, highly complex airspace serving multiple major hubs, making robust redundancy especially important.

According to technical descriptions included in industry coverage, the facility’s design relied on both a primary circuit and a geographically separate backup fiber route to maintain communications with aircraft and other control centers. The discovery that the backup line had been damaged before it was needed effectively eliminated that redundancy, leaving the system vulnerable when the primary connection failed.

Telecommunications statements describe the damaged segment as several hundred feet of multi-strand fiber cable, which required excavation, replacement and splicing before full capacity could be restored. The incident has drawn attention to coordination practices between infrastructure owners and construction crews working near critical communications corridors, particularly along busy rail and highway rights of way.

Policy and industry discussions are likely to focus on whether additional layers of backup connectivity, more rigorous monitoring of fiber integrity, or stricter construction oversight are warranted to prevent similar events from rippling through the nation’s air transportation network in the future. For travelers and airlines alike, the New Jersey cable cut has underscored how a localized infrastructure failure can quickly translate into a broad disruption across one of the world’s busiest aviation corridors.