
A single misbehaving router during an FAA copper-to-fiber upgrade triggered a nationwide ground stop that rippled across thousands of flights, exposing fragile federal systems built to keep America moving.
Story Snapshot
- Transportation Secretary Sean Duffy linked the outage to L3Harris work at a remote FAA site.
- A router began blasting abnormal connection attempts, disrupting radios and some radar feeds.
- The FAA restored services after isolating the work tied to the faulty behavior.
- L3Harris said it is supporting the FAA investigation into the ground stop.
What Officials Say Happened During the Upgrade
Transportation Secretary Sean Duffy said the disruption began while a contractor replaced an old copper line with fiber at an FAA facility on November 13. He identified L3Harris as the contractor on site when the problem started. He described a router that began sending more than one thousand connection attempts every few seconds. That traffic interfered with air-to-ground communications and some radar data paths, forcing the FAA to halt departures nationwide.
Reporters and passengers saw the impact within minutes. The Federal Aviation Administration issued a ground stop that lasted hours and led to widespread cancellations and delays into the next day. News outlets counted thousands of disrupted flights across the country. The scale pointed to a core network problem, not a single airline’s systems. Officials stressed there was no sign of a cyberattack or artificial intelligence issue causing the event, only a technology failure.
How Service Came Back and What Remains Under Review
The Federal Aviation Administration restored service after isolating the work associated with the malfunctioning device. Officials described disabling the affected router function and removing it from critical paths. That reduced the network flood and allowed radios and data links to recover. Duffy said investigators are weighing whether human error during installation or a defective router caused the behavior. He said the department had not yet determined the exact fault.
L3Harris said it is helping the Federal Aviation Administration find the cause. The company issued a public statement on November 14 noting its support for the probe into the conditions that led to the nationwide ground stop. The company did not accept blame or describe a confirmed error in its release. That stance matches the government statements that the root cause, whether installer mistake or bad hardware, was still being assessed at the time.
Why One Device Could Snarl a Nation’s Air Travel
The outage highlights risk in the Federal Aviation Administration’s aging communications architecture. Duffy and news accounts described how overloaded switches and routers in legacy networks can cascade under stress. When traffic floods poorly segmented systems, a local fault can ripple across regions. Government Accountability Office reports have warned for years that many air traffic control systems are unsustainable and slow to modernize, raising the odds that small failures have big effects.
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
Both conservatives and liberals will see a familiar pattern here. A major federal system failed ordinary people, and blame bounced between a large contractor and a slow-moving agency. Travelers lost time and money while leaders argued about process and procurement. The facts point to a specific trigger at a work site and a larger weakness in how the network is built and managed. That mix demands transparency, faster upgrades, and real accountability across government and industry.
Sources:
washingtontimes.com, l3harris.com, gpb.org, edition.cnn.com, kbzk.com, nysun.com, galvnews.com, gao.gov
© truthandliberty.com 2026. All rights reserved.












