🔍 Read the full analysis: What We Still Don’t Know About The FAA’s Nationwide Flight Halt on ThorstenMeyerAI.com
Get the latest gadgets delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
TL;DR
The FAA ordered a nationwide ground stop on Nov. 13 after communication and equipment problems affected air traffic control facilities. Transportation Secretary Sean Duffy blamed overloaded legacy equipment, while officials said they had seen no evidence of a cyberattack; the FAA has not published a written root-cause report.
The FAA lifted a nationwide ground stop at about 8:16 p.m. ET on Friday, Nov. 13, after communications problems affected air traffic control facilities and held departures across the United States for about four hours and 23 minutes. Officials said the disruption involved radar and communications systems, but the agency has not published a written root-cause report, leaving key questions about the failure and its safeguards unanswered.
The FAA Command Center issued its nationwide order at 3:54 p.m. ET, saying all airports were ground-stopped “for reasons of safety.” Its event time began at 3:53 p.m.; the cancellation notice lists 8:16 p.m. as the end. Transportation Secretary Sean Duffy said airspace reopened at 8:15 p.m. The FAA described the initial cause as communication issues affecting multiple Air Route Traffic Control Centers and said technicians were investigating. The agency marked its statement preliminary and subject to change.
Duffy said the trouble began at 3:36 p.m. and affected radar and communications at en route centers and approach control facilities around the country. He attributed the problem to older analog telecommunications switches and routers that became overloaded with data and delivered inconsistent information. He also said it was not a complete loss of radar or telecommunications. These are the secretary’s account of the failure; the FAA has not released a final technical explanation.
FAA advisories show the disruption developing first around Chicago. At 3:21 p.m., the Command Center cited equipment issues in warning of delays at O’Hare. At 3:28 p.m., it stopped departures to O’Hare, citing equipment and communications problems; Midway followed at 3:31 p.m. The nationwide order came less than half an hour later. More than 3,500 aircraft were airborne when the stop began, Duffy said. The FAA allowed some medevac, life-saving cargo and law enforcement flights to continue, and later permitted some international departures as facilities recovered.
FAA ground stop · Nov 13, 2026 · times ET (UTC−5)
Unreliable data, a full stop, a slow restart
What the FAA Command Center’s advisories and Transportation Secretary Sean Duffy describe, step by step.
US airspace (schematic)
plane (schematic)airports
3,500+ planes in the airwhen the stop began, Duffy says Fewer than 400still airborne by 8 p.m. ET, Duffy says Restartground stop cancelled; flights resume slowly
What the FAA and Duffy said
- 3:21 p.m.Chicago O’Hare: arrival delays “due to equipment issues”FAA advisory 106
- 3:36 p.m.Radar and communications unstable at centers and TRACONs nationwideDuffy
- 3:54 p.m.“All airports are ground stopped”; departures heldFAA advisory 111
- 4:20 p.m.Airborne holding expected at “any and all airports”FAA advisory 116
- 8 p.m.Fewer than 400 planes still airborne, down from 3,500+Duffy
- 8:16 p.m.Nationwide ground stop cancelled; Duffy: airspace reopened at 8:15 p.m.FAA advisory 005
Sources: FAA Air Traffic Control System Command Center advisories 106, 111 and 116 (Nov 13) and 005 (Nov 14, 2026, UTC dates); Transportation Secretary Sean Duffy at the White House briefing, Nov 13 (transcript: Roll Call Factba.se) and on X (as quoted by Fox Business); BBC News, Nov 14. Durations: own calculation from advisory event times (2026: 20:53 to 01:16 UTC; 2023: 12:20 to 14:00 UTC). The radar picture is a schematic, not real traffic.
Graphic: Powered by Thorsten Meyer AI
How the Halt Disrupted Air Travel
A nationwide ground stop affects more than flights waiting to depart. Aircraft already in the air may have to hold or divert, while airlines must reposition planes and crews after restrictions lift. The FAA’s advisories called for airborne holding and extended flight-plan drop times at en route centers, showing how controllers and operators managed the disruption while communications problems persisted.
The effects also crossed national borders. According to the supplied reporting, Eurocontrol suspended US-bound departures from member states at the FAA’s request from 10 p.m. UTC on Nov. 13 until 5 a.m. UTC on Nov. 14. BBC News reported that Sydney Airport held US-bound flights and Air Canada cancelled flights between Canada and the United States. FlightAware counted 9,159 cancellations within, into or out of the U.S. on Friday, and 3,515 more by 7:58 a.m. ET Saturday. Those are whole-day totals, not counts attributed solely to the ground stop.
For travelers, the distinction matters: lifting the order did not immediately restore normal schedules. Aircraft and crews were out of position, and the Command Center continued issuing restrictions for individual airports and airlines into the night. For businesses that rely on air cargo or time-sensitive travel, the halt showed how a failure at air traffic control facilities can disrupt operations well beyond the locations where the trouble first appears.
Products Worth Considering

LG 27GR83Q-B 27-inch Ultragear QHD IPS Gaming Monitor

Amazon Kindle Scribe Colorsoft 64GB with Premium Pen

Apple Watch Series 12 GPS 46mm Smartwatch
As an affiliate, we earn on qualifying purchases.
From Chicago Delays to a National Order
The Command Center’s advisories trace a progression from local trouble to a national restriction. Earlier Friday delays cited weather and traffic. The first advisory in the supplied account to name equipment came at 3:21 p.m. for O’Hare. After departure restrictions were imposed for O’Hare and Midway, the FAA activated a diversion recovery tool for all airports at 3:30 p.m. Duffy placed the nationwide problem’s start at 3:36 p.m.; the all-airports ground stop followed at 3:54 p.m.
Later notices described a system being managed as facilities recovered. At 4:20 p.m., the Command Center warned of possible holding at any airport. At 4:21 p.m., it extended flight-plan drop times to 240 minutes, citing a nationwide communications failure. At 5:46 p.m., it said flights could depart as en route facilities recovered, with coordination from the Command Center. The FAA cancelled the national order at 8:16 p.m., though individual airport and airline restrictions continued afterward.
The supplied source says BBC News characterized the event as the longest nationwide ground stop since the Sept. 11, 2001 attacks. An FAA-commissioned 2023 review identified 21 en route centers, which largely guide aircraft between airports. That helps explain why a problem affecting several facilities could require a broad response, though the available information does not identify which specific systems or facilities failed.
““We didn’t lose all telecom we didn’t lose all radar.””
— Transportation Secretary Sean Duffy
The Cause and Safeguards Remain Unclear
The main unresolved issue is the technical cause. Duffy blamed overloaded analog telecommunications equipment, but the FAA has not published a written root-cause report identifying the failed components, the sequence of failures or why problems across facilities required a nationwide stop. The agency’s initial statement was explicitly preliminary.
Cyber involvement also remains unconfirmed. Mullin said officials had seen no evidence of an attack and that the event appeared mechanically driven, while stating they would not rule out a cyberattack. The source material does not provide a final investigative finding or technical evidence that would settle that question.
The FAA has not given a complete account of which centers were affected, how long each remained impaired, or what redundancy systems were available. Nor is there a confirmed count of cancellations caused specifically by the ground stop: FlightAware’s reported figures cover all cancellations on the relevant days. Officials also have not explained whether the newer SMART AI traffic tool played any role. Duffy and the tool’s maker said it was not connected to the equipment that failed.
Awaiting the FAA’s Technical Findings
The next key development is a fuller account from the FAA explaining the failure and its response. The agency said technicians were investigating, but the supplied material gives no publication date for a final report. Until that account is available, explanations about the precise cause, affected equipment and prevention measures should be treated as provisional.
Duffy has said the problem reflects aging infrastructure and warned that similar disruptions could happen without investment in a replacement system. He is seeking $50 billion from Congress, according to the source material. It is not clear from the information provided whether lawmakers will approve that amount, what a replacement would include or how quickly it could be put in place.
Travelers and carriers will also be watching how the FAA and airlines handle the operational aftermath, including continuing airport restrictions, cancellations and schedule recovery. The national order has ended, but the questions about the communications failure—and how the system will be protected from a repeat—remain open.
Key Questions
When did the FAA ground-stop flights nationwide?
The FAA Command Center issued the order at 3:54 p.m. ET on Nov. 13, 2026, with an event start time of 3:53 p.m. The cancellation notice lists 8:16 p.m. ET as the end; Duffy said airspace reopened at 8:15 p.m.
What caused the nationwide flight halt?
The FAA initially cited communications issues affecting multiple air traffic control centers. Duffy blamed older analog telecommunications switches and routers that became overloaded and delivered inconsistent data. The FAA has not published a final root-cause report, so the explanation remains subject to further findings.
Was the halt caused by a cyberattack?
That has not been established. Homeland Security Secretary Markwayne Mullin said officials had seen “zero evidence” of a cyberattack and described the event as apparently mechanical, while saying they would not rule out an attack.
How many flights were cancelled because of the halt?
The supplied figures do not isolate cancellations caused by the ground stop. FlightAware counted 9,159 cancellations within, into or out of the United States on Friday and another 3,515 by 7:58 a.m. ET Saturday; those totals include cancellations for other reasons.
Could another nationwide ground stop happen?
Duffy warned that similar events could occur without investment in a new system and said he wanted $50 billion from Congress. The FAA has not released its final findings or a timetable for any replacement, so the likelihood of another halt is not established.
Source: ThorstenMeyerAI.com
