
A nationwide ground stop began during an FAA copper-to-fiber upgrade when a router flooded the network and disrupted aircraft communications, officials said.
Story Snapshot
- Transportation Secretary Sean Duffy tied the outage to L3Harris work swapping copper lines for fiber at an FAA site.
- A router sent more than 1,000 connection attempts every few seconds, disrupting communications and some radar feeds.
- The FAA restored service after isolating the affected work and stabilizing the network.
- Officials are weighing installer error versus defective equipment; L3Harris is supporting the probe.
What Triggered the Ground Stop
Federal officials said the disruption began on November 13 during maintenance to replace an old copper telecommunications line with fiber at a remote Federal Aviation Administration facility. Transportation Secretary Sean Duffy stated that a router tied to the upgrade began pushing abnormal traffic soon after the work began. The device tried to connect more than 1,000 times every four to five seconds, overwhelming parts of the system. The spike hit communications with aircraft and some radar data paths, which forced the agency to halt departures.
L3Harris, the defense and aerospace contractor performing the upgrade, said it is supporting the Federal Aviation Administration investigation to determine what conditions led to the national ground stop. Duffy said investigators are examining whether the cause was user error, an installation mistake, or a faulty router. He emphasized that the agency had not yet picked a single root cause. The Federal Aviation Administration described the event as an “equipment issue” during a telecom network upgrade and ruled out evidence of a cyberattack.
How the FAA Brought Systems Back
Officials said the Federal Aviation Administration restored operations by isolating the work associated with the malfunctioning equipment and stabilizing network traffic. Ground stops were lifted later that day, but disruptions carried into Saturday as airlines worked through cascading delays and cancellations. Airlines needed time to re-crew flights, position aircraft, and re-sequence routes. By the end of Saturday, travelers still faced hours-long waits and many missed connections due to the system-wide backlog.
Agency leaders pointed to the scale of the effects as consistent with a major network instability. The outage led to thousands of affected flights across the country. That pattern matched what would be expected if communications and radar data links at multiple centers were hit at once. The Federal Aviation Administration and the Department of Transportation said they would publish findings after completing a technical review and any needed corrective actions.
Why This Happened During an Upgrade
Investigators are focusing on the interaction between new hardware and legacy aviation networks. Duffy’s account described a router that flooded other devices, which then overloaded and shut down. That is a known risk when old systems lack strong isolation or rate limits. Recent Government Accountability Office work has warned that many Federal Aviation Administration air traffic control systems are unsustainable or at risk and need faster modernization, which raises the odds that local faults spread widely.
Those reports found the agency has dozens of ongoing modernization projects but has moved too slowly on the most critical systems. They also cited weak oversight of contractors and complex change management in older environments. That history helps explain how a maintenance event at one site could ripple nationwide. It also shows why Congress and the Federal Aviation Administration have pushed for better segmentation, failover, and testing before live cutovers.
Accountability and Next Steps
Duffy said the probe will look at three branches: user error, L3Harris installation error, or defective equipment. The language matters because it assigns different responsibility. A user or install error points to human steps and procedures. A defective router points to vendor hardware or firmware. The Federal Aviation Administration said it will base final findings on logs, device diagnostics, and change-control records from the site and network operations centers.
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
For travelers and taxpayers, the stakes are larger than one router. People on the right and the left both worry that powerful contractors and agencies face weak accountability while core services falter. This event fits that concern. A routine upgrade at a critical system plunged a nation into delay. The remedy is clear but hard: modernize faster, isolate faults better, and test changes under load before they touch live traffic. The investigation’s results, and fixes, should be public and specific.
Sources:
washingtontimes.com, l3harris.com, bloomberg.com, gpb.org, cnbc.com, edition.cnn.com, floridatoday.com, foxla.com, nysun.com, gao.gov



