One severed fiber line stalled flights at five Northeast airports for hours

A single severed fiber-optic line in New Jersey knocked out the primary and backup communications systems at the Federal Aviation Administration’s Philadelphia radar approach control facility on Monday, forcing ground stops that stalled flights at five Northeast airports for hours. Newark Liberty International Airport bore the worst of it, with the FAA reporting average delays of 306 minutes as of roughly 6:40 p.m. ET, while Philadelphia International Airport reported 212 minutes, Teterboro Airport 159 minutes, John F. Kennedy International Airport 72 minutes, and LaGuardia Airport 67 minutes.

Transportation Secretary Sean Duffy said Monday evening that the telecom lines had been repaired and that airport operations across the region were resuming, though residual delays would take time to clear.

A backup system that turned out to have its own single point of failure

FAA Administrator Bryan Bedford said the Philadelphia Terminal Radar Approach Control facility, known as Philadelphia TRACON, lost its primary communications circuit first. Controllers switched to the backup system as designed, only to discover that it, too, had failed — a backup Verizon fiber cable running through New Jersey had also been severed, leaving the facility with no working circuit at all rather than a degraded one. That is a materially different failure than a single line going down: redundancy exists specifically so one cut cable does not take out an entire region’s air traffic communications, and on Monday it did anyway.

The FAA told Fox Business it had paused flights into Philadelphia, Teterboro, and Newark because of “issues with some frequencies at Philadelphia TRACON,” a description that undersold, in the moment, just how far the disruption would spread once JFK and LaGuardia began absorbing delays too.

Newark’s 306 minutes topped a list of five affected airports

The gap between Newark’s average delay and LaGuardia’s was more than four hours. That spread reflects both flight volume and how each airport’s air traffic feeds through the Philadelphia TRACON system, with Newark and Teterboro sitting closer to the epicenter of the New Jersey cable cut than JFK or LaGuardia, which draw on a wider mix of overlapping control facilities. Newark and Philadelphia absorbed the heaviest disruption of the five, consistent with their position closest to where the fiber line was cut.

Amtrak and New Jersey Transit disagree about whose contractor did it

Duffy’s initial account named a specific culprit: “An Amtrak construction crew accidentally cut into a fiber line in New Jersey which caused a telecom outage and forced FAA to pause flights in the Northeast,” he wrote earlier Monday. Amtrak disputed that account within hours. A spokesperson told Fox Business that the incident “occurred on New Jersey Transit property and involved a New Jersey Transit contractor,” directing further questions about the outage and the related work to New Jersey Transit directly. Neither the FAA nor New Jersey Transit had responded to requests for comment by the time reporting closed Monday evening.

Duffy calls it unsurprising, and says the fix costs money the department does not yet have

Speaking to reporters, Duffy did not treat the outage as a fluke. “But this is not shocking,” he said, framing it as a symptom of aging telecom architecture rather than a one-off accident. He added that the episode strengthens the case for additional funding to modernize aging infrastructure and prevent disruptions like this in the future, tying Monday’s ground stops to a broader push to rebuild the FAA’s communications backbone. He said the department is working through the upgrade regardless of funding status, but acknowledged the pace depends on money Congress has not yet appropriated.

That funding gap is not a new complaint from Duffy’s department, and Monday’s outage will likely be cited as the latest evidence for it rather than a one-time embarrassment. Aging circuits and single points of failure of exactly this kind have been flagged in prior FAA infrastructure reviews, and the Philadelphia TRACON failure gives the argument a fresh, dated example: a facility whose backup system failed for the same reason as its primary one, on the same day, in the same state.

With the ground stops lifted, the practical advice from Duffy’s own statement was for travelers to check directly with their carriers rather than assume normal schedules had resumed. Delays of the length recorded at Newark and Philadelphia do not clear the moment a circuit comes back online; aircraft and crews are typically out of position across an entire network by the time a multi-hour ground stop ends, and airlines spend the following hours, sometimes longer, working connections back into place. LaGuardia’s inclusion on the affected list came on top of an unrelated pavement issue that had already forced a runway closure there earlier in the month, adding a second, independent source of delay at one of the five airports during the same general stretch of days — a detail that leaves open how much of Monday’s disruption gets fixed by a repaired cable, and how much of it was already baked into an aging system before the fiber line was ever cut.

More from Morning Overview

This article was produced with the assistance of AI and reviewed by Morning Overview editors prior to publication.