If you were stuck at an airport on 13 November, you want to know who caused it. New reporting points to the FAA itself. An FAA official supervised the repair work, tested it and signed off on it. Eight minutes later, the radio network began to fail. The FAA ground stop cause is now partly a question about the agency’s own role.
The Washington Post reported on 17 November 2026 that the official oversaw a contractor in El Dorado, Arkansas. The contractor was switching air traffic communications lines from an old copper network to fibre optics. The official tested the finished work and signed off on it. Just eight minutes later, the radio network serving much of the US air traffic control system began to falter.
The FAA then ordered a nationwide ground stop. It ran from 3:54 p.m. to about 8:15 p.m. ET, about 4.5 hours. It affected 17 of the FAA’s 22 en route centres. The contractor was L3Harris Technologies, which is modernising the FAA’s communications backbone. This update follows the original ground stop report.
For travellers, the cause matters because it decides what gets fixed. A faulty router points to a hardware problem. A problem with testing and sign-off points to how upgrades are checked. The investigation is not finished, so no single answer is confirmed. Another outage like this one would again leave flights on the ground across much of the country.
Transportation Secretary Sean Duffy has blamed L3Harris and a faulty router. He said the router flooded the network with more than 1,000 connection attempts every few seconds. He also said the FAA was working out whether it was “incompetence” or a faulty router.
A person close to the investigation disagrees with that tone. That person called Duffy’s characterisations “inflammatory” and “insulting”. They said his comments overlooked the FAA’s prominent role in the work. The FAA and L3Harris are examining the router at a lab in Florida.
The two accounts do not have to cancel each other out. A router can be faulty, and an FAA official can still have tested and approved the work. The facts reported so far do not rule out either one. The eight-minute gap between sign-off and failure is the detail both sides will need to explain. An earlier FAA ground stop also disrupted flights, so the stakes for passengers are not new.
Who was responsible for the FAA ground stop? Transportation Secretary Sean Duffy blames contractor L3Harris and a faulty router. The Washington Post reported that an FAA official supervised, tested and signed off the work minutes before the network failed. No final finding has been published.
In short, the FAA communications outage began eight minutes after an FAA official approved the Arkansas work. Duffy blames L3Harris and a faulty router. A person close to the investigation says the FAA’s own role is being left out. The router is under examination in Florida, and the answer is still open.