The FAA ground stop cause is now named: on 14 November 2026, the United States Department of Transportation said a router flood during copper-to-fibre work by contractor L3Harris triggered the nationwide ground stop on Friday 13 November 2026. The Federal Aviation Administration, known as the FAA, said the flood hit 17 of the 22 Air Route Traffic Control Centers that guide aircraft between airports, and about 12,462 flights were cancelled on 13 November, including 9,082 by major airlines. The stop lasted about four and a half to five hours, from around 3:30–3:45pm Eastern Time to 8:15pm Eastern Time, and officials said there was no indication of a cyberattack. That distinction matters, because the first hours of the stop produced speculation about what had failed, and the official account that followed pointed to a telecommunications fault, not a hostile act.

Transportation Secretary Sean Duffy and FAA Administrator Bryan Bedford gave the first official account of the cause at a briefing on Saturday 14 November, according to reports by the Associated Press and NPR. Duffy said L3Harris, a longtime FAA contractor, had been replacing ageing copper telecommunication lines with fibre at a remote FAA location. When a router involved in that switch was turned back on, it began flooding other routers in the air traffic control network with 1,000 connection attempts every four to five seconds, according to the FAA's official question-and-answer account cited in the research for this article. The flood overwhelmed the system that carries radar and communication data between centres, and the FAA ordered a nationwide ground stop out of caution while technicians worked to isolate the fault.

The scale of the disruption grew quickly once the flood spread. Reuters reported that more than 20,000 flights had been disrupted since Friday, a figure that covers cancellations and delays beyond the 13 November cancellation count alone. The Weather Channel reported that the stop was the nation's longest ground stop in 25 years, and that FAA Administrator Bryan Bedford said the United States air travel schedule should be back to normal by the end of Sunday 15 November. That recovery timetable gave airlines and passengers a clear target, even while thousands of travellers still faced delays on Saturday as aircraft and crews were out of position after Friday evening's halt.

What the FAA ground stop cause investigation found so far

The FAA ground stop cause investigation, as described by Duffy and Bedford on 14 November, traced the fault to work at two places. Duffy said the copper-to-fibre replacement was under way at El Dorado, Arkansas, and that a second router, at Amarillo, Texas, was also involved after the first router was turned back on. The Weather Channel reported that Duffy said on Sunday 15 November that L3Harris had secured two routers from FAA facilities in Texas and Arkansas for deep diagnostics. That step is central to the next stage of the inquiry, because the two routers hold the evidence that can separate a faulty piece of equipment from a faulty installation.

Duffy said investigators are determining whether the fault came from incompetence or from a faulty router, using the words reported by the Associated Press: investigators are determining "incompetence… or a faulty router". In plainer terms, the question is whether L3Harris technicians made an error during the work, or whether the router itself was defective when it was installed. FAA acting chief technology officer Rebecca Guy said the FAA disabled both routers right away and was able to stabilise the network, according to TechCrunch, and that a root-cause analysis was under way. Guy added, in remarks reported by NPR, that the FAA believes what occurred with that router has been worked through, while the formal root-cause work continues.

L3Harris is the FAA network contractor, and Duffy said the company has worked for the FAA for more than 20 years and owns the network the agency uses to control the airspace, according to the Associated Press account. The company said it is supporting the FAA investigation and takes the impact on airlines and travellers seriously, NPR reported. That cooperation matters for the inquiry, because the contractor holds the maintenance records, the installation logs and the equipment itself. The FAA has not yet published a final finding on the fault, and the Associated Press reported that the agency's own short statement on 13 November said only that communication issues were affecting multiple Air Route Traffic Control Centers and that technicians were investigating.

How the FAA ground stop cause unfolded on 13 November 2026

The FAA ground stop cause unfolded in less than an hour on Friday afternoon. The FAA said it first noticed instability in its network starting around 3:36pm Eastern Time, according to NPR, while other reports put the first intermittent radar and communication problems at around 3:30pm Eastern Time. By 3:44pm Eastern Time, the FAA had declared a nationwide ground stop. The stop was lifted at 8:15pm Eastern Time, after about four and a half to five hours, according to the research for this article. During that window, no departures were allowed nationwide, and the effect spread through the system as aircraft that should have flown stayed on the ground and later flights lost their slots.

The flood reached 17 of the 22 Air Route Traffic Control Centers, the centres that handle flights between airports rather than arrivals and departures at a single airport. That reach explains why a fault traced to one remote site could halt flights across the country. Duffy and Bedford were asked several times why a single router could lead to telecom outages across such a wide part of the country, and they said that is still under investigation, NPR reported. The same briefing heard questions about why the work was done in the middle of a busy travel day instead of late at night, when fewer aircraft are in the air. Officials said the work was considered routine maintenance, and it is not clear why it broke the national airspace system in the way it did.

Bedford said the line change was routine maintenance on the existing network, which he described as a 1980s TDM system, and not part of the separate 12.5 billion dollar air traffic control modernisation programme run with Peraton, according to the Associated Press account. That point separates two different stories that could easily be confused: the fault happened on the old network during a copper-to-fibre switch, while the larger modernisation programme is a separate effort. Congress approved 12.5 billion dollars for FAA improvements in 2025, according to the research for this article, and that funding forms the background to the political argument that followed the stop.

Why the FAA ground stop cause matters for US air travel

The FAA ground stop cause matters because it shows how a single point of failure in a telecommunications network can halt a national system. The FAA's network carries the data that lets controllers see aircraft on radar and speak to pilots, and when that data floods or falls out of sync, controllers lose the tools they need to keep aircraft safely separated. The FAA chose a nationwide stop rather than a partial one, and that choice, while disruptive, reflects the scale of the fault: with 17 of 22 centres affected, the agency could not be sure which routes were safe to keep open. The stop was the first nationwide stop since January 2023, when a key FAA computer system that sends notices to pilots malfunctioned, and only the second since the attacks of 11 September 2001, according to The Weather Channel.

The human cost of the stop was measured in cancelled flights and stranded passengers. About 12,462 flights were cancelled on 13 November, including 9,082 by major airlines, and Reuters reported that more than 20,000 flights had been disrupted since Friday. TechCrunch, citing aviation data firm Cirium, reported more than 8,200 flights cancelled on Friday evening alone, a figure that covers a narrower window than the full-day total and shows how fast the cancellations piled up once the stop began. Passengers faced rebooking queues, overnight stays and missed connections, and airlines faced the slower work of getting aircraft and crews back to the right airports after the stop was lifted.

The stop also matters because it arrived one day after the FAA announced the rollout of an artificial intelligence tool for air traffic controllers, according to TechCrunch. The air traffic controllers union said it was not consulted in designing the system. When Homeland Security Secretary Markwayne Mullin was asked earlier whether the ground stop was caused by artificial intelligence, he replied, in the TechCrunch account, "We call it SI [super intelligence] around here, remember? SI." Duffy said, "We don't believe so," when asked about a cyberattack, and the White House said there was no indication of a terrorist threat or cyberattack connected to the outage, according to The Weather Channel. Officials also confirmed there was no connection to Microsoft. Those denials were specific, and they were repeated across the weekend briefings.

For readers following wider United States government news, the stop sits alongside other major stories of the month, including Iran's reported drone attacks in the Gulf region and the debate over Ukraine, Donbas and NATO membership. The common thread is not the subject matter but the scale: each story turns on decisions taken in Washington and their effects far beyond the capital. In the FAA case, the decision that mattered most on 13 November was the FAA's own choice to halt departures nationwide until the network could be stabilised.

What happens next after the FAA ground stop cause is named

What happens next after the FAA ground stop cause is named starts with the two routers now held for deep diagnostics. Duffy said on Sunday 15 November that L3Harris had secured the routers from the Texas and Arkansas facilities, and the diagnostics should show whether the fault was in the hardware, in the software that ran on it, or in the way it was installed. The FAA's root-cause analysis runs alongside that work, and its findings will shape any changes to maintenance rules, including when copper-to-fibre work can be done, how it is tested before a router is returned to service, and how quickly a flooding router can be isolated before it spreads to other centres.

The political argument has already begun. President Donald Trump broke 1.5 days of silence on 15 November, blaming the Biden administration and calling for more air traffic control funding, according to the research for this article. That claim is a political attribution, not a technical finding, and the technical inquiry has not blamed any administration for the router flood. Congress approved 12.5 billion dollars for FAA improvements in 2025, and the question now is whether that funding, and the modernisation programme it supports, moves faster or changes direction in response to the stop. Bedford's promise that the schedule should recover by the end of 15 November sets a short-term test for the system, while the funding debate sets a longer one.

For passengers, the practical next step is the recovery of the schedule. Bedford said the schedule should be back to normal by the end of Sunday 15 November, and airlines spent the weekend repositioning aircraft and crews. For the FAA, the next step is the root-cause report and any safety recommendations that follow from it. Until that report is published, the named cause remains the official account given on 14 November: a router flood during copper-to-fibre work by L3Harris, with the choice between equipment fault and installation error still open. That is the fact to hold on to, and the question to watch is which of those two explanations the diagnostics support.