I had FlightAware open when the map went still. You felt it at the gate: screens that had been updating turned stubborn. By the time officials spoke, the explanation sounded like something you could fix with a screwdriver — and then not.
I’ll keep this tight. I’m here to show you what Transportation Secretary Sean Duffy actually said, what the evidence on the table looks like, and where the gaps remain. You can judge the rest.
At 3 p.m., controllers logged more than 1,000 connection attempts every four to five seconds: what Duffy said and why his phrasing matters
Duffy told reporters the nationwide ground stop on Friday sprang from a communications effort that “didn’t meet the moment.” He named a contractor—L3Harris—and described a routine swap from old copper lines to fiber optics, calling out a router that was being replaced. He said that router began “flooding other routers in our air traffic control system,” producing the repeated connection attempts that degraded communication with aircraft.
That is a narrow account with wide implications: if a single replacement router can emit thousands of bogus connections, the problem could be a misconfigured device, bad firmware, or a botched cutover procedure. Duffy stopped short of assigning blame; he said the government does not believe a foreign actor caused it, but left room for contractor error or faulty equipment.
Why were all flights grounded?
Because air traffic control lost reliable communications. When core routers are overwhelmed, controllers cannot meet regulatory safety standards for separation and clearances, and a national ground stop is the blunt safety hammer. The FAA’s public comments, and contemporaneous reports from NPR and The New York Times, place the trigger at a comms cutover rather than at a runway or airplane system failure.
At least one remote FAA facility showed the initial fault: who runs the wires and why that ownership matters
The FAA relies on a private network for much of the airspace communications stack. Duffy said L3Harris “owns the telecommunications network the FAA uses for flight control,” and that the vendor and its telco partners are migrating legacy copper circuits to fiber and to IP-based equipment. That matters because when public agencies outsource infrastructure, the investigative paper trail and contractual remedies live partly with contractors.
L3Harris issued a formal statement telling the FAA and the public it’s been modernizing the National Airspace System network and has completed “more than 70%” of the planned conversion from copper to fiber. The company said it is cooperating with the FAA’s investigation.
“L3Harris has been modernizing the communications infrastructure supporting the National Airspace System in close coordination with the FAA. With safety and reliability as our highest priorities, L3Harris, together with its telco partners and the FAA, has completed more than 70% of the planned airspace communications conversion from legacy copper wires to a fiber optic system. We are supporting the FAA in its investigation to understand the conditions that led to the Nov. 13 ground stop of our nation’s air travel. L3Harris takes the nationwide ground stop and its impact on travelers, airlines and air traffic operations seriously.”
Was the FAA flight grounding caused by a cyberattack?
Duffy said plainly: “Did some foreign nation attack this network? And the answer to that is we don’t believe so.” That is a denial without forensic specifics. The observable symptom—massive repeated connection attempts—can be produced by misrouting or a misconfigured router, but the same signature can appear in some cyber incidents. Right now, the publicly disclosed evidence points at a cutover or equipment fault, not a confirmed intrusion.
At the same time, FAA work on an AI-based air traffic control system was underway: why timing fuels suspicion
The grounding coincided with the FAA moving to newer systems, including trials of AI tools for traffic flows. Social feeds and analysts immediately asked whether the modernization program and the outage were linked. So far there’s no technical tie shown between the AI effort and the comms failure; the presence of two big changes at once, however, creates a narrative problem for the agency.
When infrastructures are upgraded, a small error can cascade faster than anyone expects—like a single frayed thread that unravels a sweater. Public trust in any modernization program depends on clear root-cause explanations and verifiable logs; the FAA will need both to regain confidence.
At airports and on social media, passengers surveyed the damage in real time: the human fallout and the policy questions
Flights canceled, passengers stranded, and the logistics headache of crew reassignments stretched across carriers and terminals. This was the longest U.S. ground stop since 9/11 and the ripple effects lasted beyond the four-hour window Duffy described. Airlines, TSA, and airfields spent the evening triaging delays and refunds while the FAA started an investigation that will involve vendor logs, router configurations, and carrier reports.
Responsibility will hinge on forensic records: configuration files, firmware versions, cutover change tickets, and who signed off on the switchover. If human error was involved, you’ll see procedural fixes and new checklists. If equipment failed, expect warranty and replacement actions. If contracts were weak, look for procurement hearings and tougher SLAs.
I’ve tracked incidents where a single misapplied patch cascaded across a network; in infrastructure, failures propagate like dominoes falling in a cathedral. The technical story can be boring on paper and devastating in practice, and this one will be dug over by Congress, carriers, and cybersecurity teams.
Read the full statements from the FAA and coverage from NPR, The New York Times, and CBS News if you want the primary source material and timelines.
I don’t have a smoking-gun answer yet, but I do have a clear list of the records I’d demand if I were you: router logs, cutover tickets, firmware hashes, and L3Harris–FAA exchange records. Who will be accountable when those documents meet daylight—and will it be enough to stop the next global grounding?