
America’s air travel stopped for hours after a contractor’s router flooded Federal Aviation Administration systems during a copper-to-fiber upgrade, officials said.
Story Snapshot
- Transportation Secretary Sean Duffy tied the outage to L3Harris work during a telecom upgrade.
- A router sent rapid connection attempts that disrupted FAA communications and radar feeds.
- FAA restored service after isolating the work tied to the faulty behavior.
- Officials are still determining whether it was installer error or bad hardware.
What Triggered The Nationwide Ground Stop
Transportation Secretary Sean Duffy said the outage began as L3Harris replaced an old copper line with fiber at a remote Federal Aviation Administration site on November 13. During the work, a router began firing more than a thousand connection attempts every few seconds, which strained the network and disrupted communications with aircraft. Some radar feeds were also affected, which forced a national halt to departures while controllers stabilized systems.
The Federal Aviation Administration described the root problem as an equipment issue tied to the telecom upgrade. Officials said the agency lifted the ground stop after isolating the affected work and restoring stable communications. The disruption lasted hours, and airlines spent the next day working through thousands of delays and cancellations as planes and crews reset across the country.
How Officials Are Assigning Responsibility
Duffy said investigators are weighing two explanations: installer or user error versus a defective router. He emphasized that the triggering device sat within work linked to L3Harris, a major federal contractor. L3Harris stated it is helping the investigation to understand the conditions that led to the ground stop. That public stance confirms the company’s role in the review but does not concede fault while the technical analysis proceeds.
Reporters at the briefing and later coverage echoed the same framing. They noted that the evidence ties the timing to the upgrade and the router’s abnormal traffic, but stops short of proving a contractor mistake or a confirmed hardware failure. The Federal Aviation Administration returned to service by segmenting the issue, which supports the view that a local fault rippled through a wider system under load.
Why A Local Glitch Became A National Mess
Duffy’s account and independent reporting point to stress in the Federal Aviation Administration’s legacy telecommunications network. When the router flooded connections, switches and routers in older parts of the network became overloaded and went down. That pushed the agency to halt departures until communications with aircraft and key radar feeds were reliable again. The pattern tracks with past warnings about weak isolation and aging infrastructure in air traffic systems.
Transportation Secretary Duffy sharply criticized contractor L3Harris over the FAA outage, saying there could have been mistakes during a router switch. He also said it’s unclear whether the cause was contractor error or faulty equipment.https://t.co/Vs33fKKw4m
— Jonathan Htet (@jonathan_htet) November 14, 2026
Government Accountability Office reviews have flagged many air traffic systems as unsustainable or at risk, and urged faster modernization. Those reports cited slow upgrades, uneven contractor oversight, and technology that vendors no longer support. The November 13 event fits that risk map: a planned upgrade went wrong, and the network design allowed a local failure to cascade. Both parties now face pressure to harden segments, add rate limits, and tighten change controls.
What Matters For Travelers And Taxpayers
Travelers endured cascading delays because planes and crews were out of position nationwide. Airlines restored schedules only after the Federal Aviation Administration stabilized communications and air traffic flow. The fast recovery after isolating the problem shows the core system can rebound, but the scale of the stop shows how fragile key links remain. Clear steps on segmentation, testing, and rollback plans during upgrades could limit future nationwide impacts.
Taxpayers fund both the Federal Aviation Administration’s network and large contractor projects. People on the right and left worry that leaders protect vendors and agencies more than passengers and workers. This case shows why transparency matters. A public root-cause report, with what failed, who signed off, and what will change, would help rebuild trust. L3Harris says it is cooperating, and the Federal Aviation Administration says the probe continues. Results, not talk, will count.
Sources:
washingtontimes.com, l3harris.com, bloomberg.com, gpb.org, edition.cnn.com, foxla.com, gao.gov, galvnews.com



