🔍 Read the full analysis: What We Know About The FAA’s 4-Hour Nationwide Flight Halt on ThorstenMeyerAI.com
Get business pricing on tech for your team
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
TL;DR
The FAA ordered a nationwide ground stop on Nov. 13 after communications and equipment problems affected air traffic facilities. The stop lasted about four hours and 23 minutes, according to FAA advisory times; officials have not published a written root-cause report and say they have seen no evidence of a cyberattack so far.
The Federal Aviation Administration ordered a nationwide ground stop on Friday, Nov. 13, holding departures at U.S. airports for about four hours and 23 minutes after communications and equipment problems affected air traffic facilities. The halt began at 3:53 p.m. ET and was lifted at 8:16 p.m., according to FAA Command Center advisories; officials have not released a written account establishing the problem’s root cause.
FAA advisories show the disruption first appeared in Chicago. At 3:21 p.m. ET, the Command Center warned of arrival delays and airborne holding at O’Hare because of equipment issues. It halted departures to O’Hare at 3:28 p.m., citing an equipment outage and communications problems; Chicago Midway followed at 3:31 p.m. The FAA issued the nationwide order at 3:54 p.m., with an event start time of 3:53 p.m.
Transportation Secretary Sean Duffy said the FAA experienced instability in radar and communications at en route centers and approach control facilities around the country. He described older analog telecommunications switches and routers as overloaded with data, producing inconsistent information. He said it was not a complete loss of radar or telecommunications. The FAA said its technicians were investigating communication issues affecting multiple Air Route Traffic Control Centers, and labeled its statement preliminary.
Duffy said more than 3,500 aircraft were in the air when the order began, with fewer than 400 airborne by 8 p.m. Medevac, life-saving cargo and law enforcement flights were permitted to continue. The FAA’s notices show staff extended flight-plan drop times and coordinated some departures as facilities recovered. The end time in the cancellation notice was 8:16 p.m.; Duffy said airspace reopened at 8:15 p.m.
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
The order stopped most departures across the United States and affected international operations too. Eurocontrol suspended U.S.-bound departures from its member states from 10 p.m. UTC on Nov. 13 to 5 a.m. UTC on Nov. 14 at the FAA’s request, according to a report by Xinhua citing the agency’s notice. BBC News reported that Sydney Airport held U.S.-bound flights and Air Canada cancelled flights between Canada and the United States.
FlightAware counted 9,159 cancellations within, into or out of the United States on Friday, and 3,515 more by 7:58 a.m. ET on Saturday. Those are totals for all cancellations during those periods, not a count of flights caused solely by the ground stop. The disruption also continued after the nationwide order ended, as airlines dealt with aircraft and crew out of position and the FAA issued individual airport and airline ground stops.
The episode matters because air traffic control depends on communications between facilities to manage aircraft and coordinate movement. A disruption can restrict departures well beyond the facility where trouble first appears, and recovery can take longer than the systemwide halt itself. Duffy warned that similar events could happen again without investment in replacement systems, and said he wants $50 billion for modernization.
Products Worth Considering
Bose SoundLink Max Portable Bluetooth Speaker, IP67 Waterproof and Dustproof, Up to 20 Hours of Battery Life, Black
Bose QuietComfort Headphones (2nd Gen), Wireless Over-Ear Noise-Cancelling Headphones, Black
Bose QuietComfort Wireless Noise-Cancelling Headphones, Cypress Green
As an affiliate, we earn on qualifying purchases.
From Chicago Delays to a National Order
The FAA Command Center advisories trace the escalation from local disruption to a nationwide stop. Before the equipment notices, some Friday delays cited weather and traffic volume. The first notice to identify equipment issues came at 3:21 p.m. ET for O’Hare. After the Chicago departure restrictions, the Command Center activated a diversion recovery tool for all airports at 3:30 p.m. The national order followed less than half an hour later.
During the halt, the Command Center said aircraft could face airborne holding at any airport and extended the period that filed flight plans remained active to 240 minutes, citing a nationwide communications failure. At 5:46 p.m., it said the stop remained in effect and that flights would be released through coordination as en route facilities recovered. By 7:37 p.m., some coastal facilities were releasing international departures. The FAA cancelled the nationwide stop at 8:16 p.m.
According to a 2023 FAA-commissioned review, the agency has 21 en route centers, which largely manage aircraft between airports. Their role helps explain why a communications problem affecting multiple centers could prompt restrictions across the national system. The FAA advisories document the operational response; they do not, by themselves, establish a full technical explanation for the failure.
“We didn’t lose all telecom we didn’t lose all radar.”
— Sean Duffy, U.S. transportation secretary
Cause Still Under Investigation
Officials have not published a written root-cause report, and the FAA described its initial statement as preliminary and subject to change. Duffy attributed the disruption to overloaded older telecommunications equipment and inconsistent data, but the available advisories do not explain which components failed, what triggered the overload, or how the effects spread among facilities.
Mullin said officials had seen no evidence of a cyberattack and that the problem appeared mechanical, while adding that investigators were not ruling out cyber involvement. The FAA and the maker of its new SMART air traffic tool said SMART was not connected to the equipment that failed. Those statements address specific possibilities but do not supply a final technical account.
Flight cancellation totals also require care: FlightAware’s counts cover all cancellations in the stated periods, and the figures do not isolate those attributable to the ground stop. The precise number of passengers affected, the full financial cost, and the time required for all airline schedules to normalize were not provided in the source material.
Investigation and System Funding
The FAA said technicians were investigating the communications problem, but no publication date for a final report was given. Further agency findings would be needed to establish the failed components, the initiating event and any changes made to reduce the risk of another disruption.
Congressional funding is also part of the debate. Duffy has called for $50 billion to replace or modernize air traffic control systems and warned of further incidents without investment. The source material does not identify a congressional vote, approved funding package or implementation schedule. Travelers should expect any remaining recovery effects to depend on individual airline schedules and should check directly with their carriers for current flight information.
Key Questions
When did the FAA ground-stop U.S. airports?
The nationwide advisory was issued at 3:54 p.m. ET on Nov. 13, with the event listed as starting at 3:53 p.m. The FAA’s cancellation notice gives 8:16 p.m. ET as the end.
How long did the nationwide flight halt last?
Using the event times in the FAA advisories, the halt lasted about four hours and 23 minutes, from 3:53 p.m. to 8:16 p.m. ET.
What caused the FAA disruption?
Duffy said radar and communications became unstable at air traffic facilities, with older telecommunications equipment overloaded with data and delivering inconsistent information. The FAA has not published a written root-cause report, so the complete technical explanation remains unconfirmed.
Was the ground stop caused by a cyberattack?
Homeland Security Secretary Markwayne Mullin said officials had seen no evidence of a cyberattack and that the event appeared mechanically driven, while saying investigators were not ruling cyber involvement out.
How many flights were cancelled because of the halt?
FlightAware counted 9,159 cancellations within, into or out of the United States on Friday and 3,515 more by 7:58 a.m. ET Saturday. Those figures include all cancellations in those periods and do not identify how many were caused specifically by the ground stop.
Source: ThorstenMeyerAI.com
