Yesterday was a really rough day for traveling by air in the United States, after the air traffic control system in the Northeast suffered some outages, which lasted for hours. This all happened because a backup fiber optic line was accidentally cut, though even that involves a lot of finger pointing.
Thousands of flights delayed or canceled due to ATC issues
On Monday, September 21, 2026, thousands of flights in the United States were either canceled or delayed. The issues started at around 9:45AM EDT, when workers accidentally cut a telecommunications line in New Jersey, which is used by the Federal Aviation Administration (FAA).
The FAA then had to suspend arrivals at several airports in the Northeast, including in Boston (BOS), New York (JFK & LGA), Newark (EWR), and Philadelphia (PHL). It took over eight hours for the issues to be completely resolved, with all ground stops being lifted by 6:30PM.
As you’d expect, even when the issues were resolved, it’s not like operations immediately resumed as normal, given the huge domino effect to airline operational issues, due to how many planes and crews were out of place. It’s not like airline operations can just recover from one second to the next.
Looking at FlightAware data, United was hit hardest, with 361 cancelations (11% of flights) and 777 delays (24% of flights). American, meanwhile had 116 cancelations (3% of flights) and 1,301 delays (37% of flights). Delta had 47 cancelations (1% of flights) and 922 delays (25% of flights). None of those numbers include regional subsidiaries. Expect that operations will still potentially be impacted on Tuesday, given how long a recovery can take.
The timing of this was also especially bad when you consider that leaders from around the world were enroute to New York yesterday, for the annual United Nations General Assembly.
Fiber optic line failure becomes a blame game
The entire air traffic control system stopped working because a single fiber optic line in New Jersey was cut. Specifically, work was being performed on a rail car storage project, at a yard near the Northeast Corridor line in New Brunswick.
That severed cable knocked out all communications between New York’s metro area air traffic control and the system in Philadelphia, which controls much of the airspace in the region. That cable had been serving as a backup to the primary circuit system, which failed.
Who was to blame for that? Well, Transportation Secretary Sean Duffy initially claimed that an Amtrak construction crew accidentally cut into a fiber optic line in New Jersey, causing the telecom outage.
However, that didn’t actually appear to be accurate. Instead, it was an NJ Transit contractor who performed the work, and not an Amtrak employee.
But even there, the blame wasn’t necessarily that straightforward. A spokesperson for NJ Transit insists that the contractor had been “approximately 10 feet from the utility markings” when they cut through the cable, so the organization also claims it’s not at fault.
Verizon, which owns the fiber optic line in question, also insists it had no responsibility in any of this:
“We have a fiber cable running adjacent to an Amtrak rail line in New Jersey. Construction contractors working in the area dug up and cut our cable. Verizon’s facilities were fully functional up to that point. Verizon bears no responsibility for this incident. We immediately deployed our technicians to the scene. We and our partners are actively working to repair the damaged cable and restore connectivity as quickly as possible.”
Ironically, this fiber optic cable was supposed to be a solution, given the chaos we saw last year, when the communication lag on outdated copper wire caused momentary outages for air traffic controllers. However, clearly there was a lack of redundancies in place.
Bottom line
Yesterday was a rough day for air travel in the United States, given the meltdown that we saw in the Northeast. A fiber optic line in New Jersey was accidentally severed, and that had been serving as a backup to the primary circuit system, which failed. A ground stop was issued at several major airports a little before 10AM, and the ground stop wasn’t lifted until after 6PM.
What do you make of this ATC meltdown? Were any OMAAT readers caught in this mess?
It's crazy that there wasn't greater redundancy to prevent such a widespread fallout for so many hours. Hardly any planes flying around NYC yesterday.
If we had a rule like EU261, even though statutory compensation would likely not be included here ('extraordinary circumstances'), at least the duty of care would apply (think, meals, hotels, more rebooking options). Instead, these folks get nothing. Kick rocks. Pound sand. Fly kite.