Clearance CLR-8960 · SAF993
SAFCON
Safety & OperationsClearance sheet
Controllers reject FAA router explanation for four-hour ground stop
Four days after a router in Arkansas halted US departures for over four hours, controllers remain unbriefed and investigators cannot explain why 17 of 22 centers were affected.
Read-back
- A November 13, 2026 outage halted US departures for more than four hours and hit 17 of 22 en route centers.
- Four days later, NATCA confirmed controllers had not been briefed on the cause.
- The FAA paused Juniper installations and disabled a broadcasting function on over 60 routers.
- FAA Administrator Bryan Bedford said on November 14 there was 'zero evidence of anything AI-related'.
- HPE said the router operated as configured by installer L3Harris.

A single router installed in El Dorado, Arkansas, has left the FAA unable to explain why 17 of its 22 en route control centers lost communications and radar feeds on November 13, grounding departures nationwide for more than four hours. Four days later, the controllers' union says the workforce has received no briefing on the specific cause.
The Federal Aviation Administration traces the disruption to excessive data flooding its telecommunications network after contractor L3Harris installed a router at the remote radio site. A second router in Amarillo, Texas, contributed to the instability, the agency said. Investigators have not determined why the fault propagated so widely.
Gregory Feith, a former senior air safety investigator at the NTSB, calls the architecture itself into question. "Why is the air traffic control system vulnerable to a single-point failure? That doesn't make any sense," he told Denver television station 9NEWS.
Feith also challenged Transportation Secretary Sean Duffy's framing of aging equipment and the copper-to-fiber transition. Modernization work has run for years, he noted. The existing network had not failed this way before Friday's installation.
"Having one router as a single point failure just is baffling to me, and I think a lot of other people in aviation only because we certify aircraft never to have a single-point failure," Feith said.
What does the timeline tell us?
Doubts surfaced on the night of the outage. Washington Examiner reporter Anna Giaritelli told CNN's Laura Coates she had contacted 60 controllers about Duffy's initial explanation. "None of them are buying what he said," Giaritelli reported. She also questioned why router work ran during a busy Friday afternoon.
The FAA's answer is partial. Maintenance at major facilities generally occurs at night. But routine replacements at remote sites have happened during the day for decades without similar disruption, the agency acknowledged. It now says it will reconsider that practice.
By November 17, the gap between official narrative and workforce knowledge had not closed. A National Air Traffic Controllers Association spokesperson confirmed to Forbes that controllers had not been briefed on the cause. Three controllers at different facilities said they had received nothing from supervisors. One supervisor said he feared being held responsible for equipment whose reliability he could not assess.
Is the router actually at fault?
The manufacturer says no. Hewlett Packard Enterprise, which owns Juniper Networks, said the device operated as configured by the installer. The FAA has paused further Juniper installations and disabled a broadcasting function on more than 60 other routers pending the investigation.
Duffy, asked on ABC on November 15 how one remote site could take down the wider network, conceded the question remains open. "We didn't think that should or would happen," he said. That admission, four days in, defines the scale of what regulators do not yet know.
A week of failures, none of them connected
The FAA outage sits inside a run of unrelated technology failures:
- November 12: a Microsoft global outage disrupted Outlook, Teams and other services.
- November 13: HR and payroll provider Workday went down the same day as the FAA ground stop.
- November 16: JPMorgan Chase and other US banks suffered transaction delays; United Airlines delayed departures after a computer problem blocked pilots from obtaining final aircraft weights.
- November 17: the NSA attributed disruption to scheduled maintenance; Apple blamed an internal update for outages.
On Fox News on November 16, Homeland Security Secretary Markwayne Mullin relayed an unnamed technology contact's theory that AI programs capable of writing and revising code could overwhelm older systems. Mullin said the explanation made sense to him. He offered no findings tying it to any specific incident. He also said cybersecurity officials had found no evidence linking the outages and that he was confident they were unrelated to cyberattacks.
The companies involved have rejected the theory outright. Microsoft said its outage was unrelated to AI agents or a cyberattack. FAA Administrator Bryan Bedford said on November 14 that investigators had found "zero evidence of anything AI-related" in the air traffic control failure.
One documented threat does exist, though it connects to nothing here. A November 13 FBI advisory described hackers using the ARTEX platform to automate intrusions across government, finance and other industries. The advisory covered campaigns underway since at least August 2026. It established no link to the aviation outages.
The open questions are structural, not speculative. Until the FAA explains how one configured router cascaded across 17 centers, and briefs the controllers who worked the outage, the official explanation remains a hypothesis. The agency's own pause on Juniper installations and its review of daytime maintenance windows suggest it agrees.
via 9news.com (Original)
More from James Calloway
Show full bio
Staff writer covering people, launches and day-to-day practice in Commercial aviation industry coverage at Flightdeck Report.
688 articles
Same bay
- FDR172FAA Ground Stop Probe Centers on L3Harris Routers in Texas, Arkansas · November 17, 2026
- FDR141FAA Probes Arkansas Router Swap That Grounded US Flights · November 16, 2026
- FDR711Overloaded routers triggered nationwide US ground stop · November 14, 2026
- FDR221FAA Ground Stop Traced to Fiber Upgrade Error at Remote Facility · November 15, 2026
- FDR239One Telecoms Failure, 7,000 Delayed Flights: Inside the U.S. ATC Ground Stop · November 14, 2026