FAA Blames L3Harris Router Fault for Nationwide Ground Stop as 4,000 More Flights Canceled Saturday
By Saturday morning, the question hanging over every crowded American airport had a partial answer. The nationwide ground stop that froze US air travel on Friday was set off by a router fault during routine telecom work by contractor L3Harris, Transportation Secretary Sean Duffy said at a briefing on Saturday — the first time federal officials have pointed to a specific cause.
The stop itself lasted more than four hours on Friday, from just before 4 p.m. Eastern until about 8:15 p.m. But the damage kept spreading long after planes were allowed to move again. FlightAware counted more than 9,100 cancellations and more than 24,500 delays on Friday, and by Saturday afternoon more than 4,000 additional flights had been canceled as airlines tried to untangle planes and crews that were in the wrong cities.
FAA Administrator Bryan Bedford said at the same briefing that he expects a full recovery by Sunday evening. For passengers still sleeping on airport floors and rebooking for the third time, that promise is the only number that matters.
What Duffy said on Saturday
Duffy said the trouble began at 3:36 p.m. on Friday, when radar and communications data at air traffic facilities across the country started producing inconsistent readings. Shortly before 4 p.m., the FAA ordered every departing flight in the country to stay on the ground. About 3,500 flights were already in the air; those were allowed to land, and more than 3,000 did so safely on Friday, according to Homeland Security Secretary Markwayne Mullin.
The work at the centre of the investigation was unglamorous: L3Harris, a longtime FAA contractor that runs the communications network air traffic control depends on, was switching old copper wiring to fiber-optic lines at a remote FAA location. Duffy said a router involved in that work began flooding the network, sending more than 1,000 connection attempts every four to five seconds to other equipment, according to an account reported by Reuters. The flood overwhelmed the aging system and knocked out communications and some radar feeds between control centres.
Officials have not yet settled whether the router was installed incorrectly, configured wrong, or was simply defective. Duffy said the investigation is still running, and L3Harris said in a statement that it is "supporting the FAA in its investigation to understand the conditions that led to the Nov. 13 ground stop." The company did not address Duffy's account directly.
The numbers: Friday and Saturday
Friday's totals were the worst for a single day of flight disruption in years. FlightAware recorded 7,468 delays and 9,201 cancellations within, into or out of the United States on Friday, and the FAA said about 12,000 flights were not completed at all, including roughly 9,000 commercial flights.
The four largest airlines took the heaviest hits. Delta canceled about 1,001 flights on Friday, American 821, United 770 and Southwest 637, according to FlightAware figures reported late Friday. JetBlue canceled its remaining flights for Friday night, and Air Canada canceled all of its flights to and from the United States for the rest of the evening. Only 387 commercial flights took off after the stop was lifted at 8 p.m.
Saturday brought no quick relief. FlightAware showed more than 4,000 US cancellations by late morning — about 18 percent of flights departing the country, according to aviation analytics firm Cirium — and Bedford said he expected between 4,000 and 5,000 flights to be canceled over the full day, out of about 41,000 scheduled. Delta issued a waiver letting passengers change Friday and Saturday flights at no extra cost.
Not a cyberattack, but questions remain
What officials were quick to rule out was foul play. The Department of Homeland Security said there was no evidence the incident involved a cyberattack or deliberate sabotage, and Bloomberg reported that the FBI does not believe a foreign attacker was involved. President Donald Trump said the failure appeared unrelated to cyberattacks or artificial intelligence and was more likely caused by aging, damaged infrastructure.
Duffy was blunter about the state of the system: the country is running its air traffic network on equipment he described as incredibly old. The stop was only the second nationwide ground stop since the September 11, 2001, attacks — the other came in January 2023, when a system that sends safety notices to pilots malfunctioned — and the Associated Press described Friday's as the longest nationwide ground stop in 25 years.
There is an awkward detail in the official account that investigators still have to explain. The failure was not one system breaking, but the links between the centres that guide planes between airports. Controllers in one part of the country could not reliably reach the centres next door, and radar data was dropping out. With aircraft moving at hundreds of miles an hour, that is not a gap the system can work around — which is why Bedford said he stood behind the decision to order the stop even before anyone knew what had caused it.
The National Weather Service reported its own nationwide internet and communications problems on Friday, a separate headache that added to the sense of a system under strain.
Why it matters, and what happens next
For the passengers still stuck this weekend, the practical question is how fast the backlog clears. Airlines warned the effects could be felt for days, as planes and crews are out of position. Officials said the system should be operating normally in time for the Thanksgiving travel rush, which begins in less than two weeks and is one of the busiest periods of the year.
The bigger question is the one Duffy raised at the White House: how long the country keeps flying on equipment that can be knocked out by a routine update. Air traffic control modernisation has been promised for years, and Friday's failure will put fresh pressure on the administration and Congress to show the upgrades are actually happening — and that adding new technology does not break the old system it is supposed to replace.
The FAA has not said when its investigation will be complete. For now, the advice for anyone flying this weekend is the same advice that applied on Friday night: check your flight before leaving for the airport, and expect the schedule to keep shifting.
For the full account of Friday evening, read our earlier report: FAA Lifts Nationwide Ground Stop After Four Hours as 9,100 Flights Canceled. And with Thanksgiving travel approaching, read our explainer on what really sets the price at the pump: Why Gas Prices Go Up and Down: The Real Reasons Explained.
Sources
- Associated Press (via WHCP) — FAA blames Friday's ground stop on 'equipment issue' during telecoms network upgrade
- Fox Weather — FAA expects 'full recovery' by Sunday as thousands of flights feel impact of historic ground stop
- Real NW Times — Duffy Links Nationwide FAA Ground Stop to Telecom Upgrade Work
- Consensus Daily — What Caused the FAA Ground Stop? L3Harris Router Fault
Published November 15, 2026. The nationwide ground stop began on Friday, November 13, 2026, at about 4 p.m. Eastern time and was lifted at about 8:15 p.m. Eastern time. Cause details and Saturday cancellation figures are from federal briefings and FlightAware data reported on Saturday, November 14, 2026.

Comments