FAA Ground Stop, 13 November 2026: What Happened
At 3:54pm ET on Friday 13 November 2026, the Federal Aviation Administration ordered a nationwide ground stop — the first since a NOTAM failure in January 2023 and the longest since 11 September 2001. All departing flights in the United States were held. About 3,500 aircraft already in the air landed safely. The stop lasted 4 hours 21 minutes and set off a weekend of cancellations that passed 17,000 by Sunday.
In short
The FAA halted all US departures from 3:54pm to 8:15pm ET on Friday 13 November 2026 — 4 hours 21 minutes — after a communications failure in its air traffic control network. A router deployed at El Dorado, Arkansas, during copper-to-fibre upgrade work, and a router at Amarillo, Texas, flooded the network with about 1,000 connection attempts every 4 to 5 seconds, destabilising 17 of the FAA's 22 Air Route Traffic Control Centers. The FAA says there is no indication of a cyberattack. The root cause is still under investigation.
The afternoon the system failed
The first signs came before the order. At about 3:30pm ET, the FAA's air traffic control communications began to become unstable. Secretary Duffy put the start of unstable radar and communications at about 3:36pm ET. Local stops had already begun: flights bound for Chicago O'Hare were held from about 3:10pm to 3:28pm ET. The instability then spread across the network. At 3:54pm ET, the FAA's Air Traffic Control System Command Center issued Advisory 111, the nationwide ground stop, citing extraordinary circumstances and reasons of safety. Departures stopped at every airport in the country. Airborne aircraft were not ordered down; they continued to their destinations and landed. At 8:15pm ET, air traffic resumed. The advisory itself was formally cancelled at 8:19pm ET under Advisory 005 — the four-minute gap explains why a few outlets reported the stop as 4 hours 25 minutes, or rounded it to almost five hours. The stop, measured from order to resumption, was 4 hours 21 minutes.
Only the third nationwide ground stop in history
A nationwide ground stop is not a routine tool. The FAA had ordered one only twice before. The first was on 11 September 2001, when US airspace was closed after the terrorist attacks. The second was on 11 January 2023, when a failure of the NOTAM system — the system that carries safety notices to pilots — halted departures for about 90 minutes to 1 hour 52 minutes, causing about 1,300 cancellations and 9,500 to 10,000 delays. The 13 November 2026 stop was therefore the third ever, the second since 9/11, and the longest since 9/11. It was also far more disruptive than the 2023 stop: Friday alone saw about 12,462 cancellations by the FAA's count, against about 1,300 in January 2023. A separate comparison is the Southwest Airlines disruption of December 2022, when about 16,900 flights were cancelled over several days after a winter storm overwhelmed the airline's crew scheduling. The November 2026 weekend passed that total by Sunday, according to Flighty figures cited by Bloomberg — making it the worst technology-driven disruption in US aviation history on that measure.
What the FAA says went wrong
The FAA published its fullest account on Sunday 15 November, in a questions-and-answers document. The failure was in the FAA Telecommunications Infrastructure network, FTI, which carries voice and data between air traffic control facilities. Contractor L3Harris had been working at a radio communications site in El Dorado, Arkansas, replacing copper connections with fibre optic cable and deploying a new router. When the new router was switched on, data began flooding the FTI network at about 1,000 connection attempts every 4 to 5 seconds, and legacy equipment became unstable. A second location was involved: a radar site in Amarillo, Texas, where a router installed about three weeks earlier also began flooding the system. The instability reached 17 of the FAA's 22 Air Route Traffic Control Centers and spread into several Terminal Radar Approach Control facilities. Some frequencies and radar feeds remained reliable throughout, the FAA says, and the stop was ordered as a safety measure before the degradation could become a loss of separation between aircraft.
What was not lost
The FAA is emphatic that this was not a complete loss of communications. Some radio frequencies and radar feeds stayed reliable for the whole period. Approximately 3,500 aircraft were in the air when the stop was ordered, and every one of them landed safely, according to the FAA. Critical operations continued: life-saving flights, law-enforcement flights and military flights were not stopped. The agency says it took measures before resuming operations, including disabling the broadcast function on the routers involved — approximately 60 similar routers according to the FAA's written account, or 69 according to Secretary Duffy on Sunday television — and checking the system before traffic was allowed to move again. Both suspect routers were removed and sent for deep diagnostic testing at an L3Harris laboratory in Florida.
The numbers, with their sources
Friday 13 November: the FAA counted approximately 12,462 cancellations, including 9,082 by major airlines. FlightAware counted about 9,200 flights within, into and out of the United States. Saturday 14 November: about 6,400 to 6,700 cancellations and more than 8,000 delays on FlightAware counts, with the exact figure depending on the snapshot time. Sunday 15 November: roughly 1,960 to 2,300 cancellations and more than 10,000 flights cancelled or delayed for a third straight day. Weekend total: more than 17,000 cancellations, with Flighty counting 17,515 from Friday to Sunday. Diversions on Friday: at least 827, of which 670 returned to their departure airport and 157 landed at a different airport, according to Cirium. American Airlines was the most affected by total number, with more than 5,300 flights cancelled since Friday, according to Bloomberg and Cirium. JetBlue was the worst hit by percentage of its schedule: 43 percent of its flights on Saturday and about 27 to 28 percent on Sunday.
The official response
Transportation Secretary Sean Duffy led the public response, with a briefing on Saturday and appearances on five Sunday morning television programmes — ABC's This Week, CBS's Face the Nation, CNN's State of the Union, Fox News Sunday and NBC's Meet the Press. FAA Administrator Bryan Bedford briefed reporters on Saturday. President Trump made his first public comments on Sunday, blaming the previous administration and urging Congress to approve more modernisation funding. New York Governor Kathy Hochul called on Duffy to resign on Saturday; Senator Tammy Duckworth criticised Duffy's comments. Duffy refused to apologise, according to the Washington Post, and blamed decades of underinvestment by both parties. House Democrats on the transportation committee demanded answers about how modernisation money already provided had been spent, and FAA and DOT officials were due to brief committee staff on Monday 16 November. Homeland Security Secretary Mullin was scheduled before a House committee on Wednesday 18 November for a worldwide threats hearing.
What happens next
Three things are pending. First, the investigation: the root cause — faulty equipment, installation error or configuration — has not been decided, and no date has been given for a final report. The routers are under diagnostic testing in Florida with FAA, FBI and vendor engineers involved. Second, the money: Duffy was due to send Congress a detailed request for 50 billion dollars in air traffic control modernisation funding on Monday 16 November, up from the 30.1 billion dollars sent to Congress on Thursday 12 November. Third, the operation itself: airlines spent the weekend repositioning aircraft and crews, and the test of the recovery is Monday's actual cancellation count, which had not been published when this page was last checked at about 05:00 ET on Monday 16 November.
Frequently asked questions
4 hours 21 minutes. The order was issued at 3:54pm ET and traffic resumed at 8:15pm ET. The formal advisory cancellation was signed at 8:19pm ET.
Three in US history: 11 September 2001, 11 January 2023 (NOTAM failure, about 90 minutes), and 13 November 2026. The 2026 stop was the longest since 9/11.
The FAA counted about 12,462, including 9,082 by major airlines. FlightAware counted about 9,200. The FAA counts all operators; FlightAware counts tracked commercial flights within, into and out of the US.
Yes — about 3,500 aircraft were airborne. They were allowed to continue and land, and the FAA says every passenger arrived safely.
A communications failure in the FAA network after router work at El Dorado, Arkansas, and Amarillo, Texas, during a copper-to-fibre upgrade. The routers flooded the network with about 1,000 connection attempts every 4 to 5 seconds. The root cause is still under investigation.
Yes. Traffic resumed at 8:15pm ET on Friday 13 November, and no new ground stop had been imposed as of about 05:00 ET on Monday 16 November.
Figures are given with their snapshot time and source. Developing items are marked as developing. Last checked Monday 16 November 2026, about 05:30 ET.