🔍 Read the full analysis: A Closer Look At The FAA’s 4-Hour Flight Halt Across The US 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 communications and equipment problems affected air traffic control facilities. The FAA’s advisories show the stop ran about 4 hours and 23 minutes; officials said systems were recovering before departures resumed. Authorities have not published a written root-cause report and said they had seen no evidence of a cyberattack, while not ruling one out.
The Federal Aviation Administration halted departing flights at US airports for about 4 hours and 23 minutes on Friday, Nov. 13, after communications problems affected multiple air traffic control facilities. The stop began at about 3:53 p.m. Eastern Time and was lifted at 8:16 p.m., according to FAA Command Center advisories, disrupting domestic and international travel while the agency worked to restore service.
The FAA’s Command Center first reported equipment-related problems around Chicago. At 3:21 p.m., it warned of arrival delays and airborne holding at O’Hare because of equipment issues. At 3:28 p.m., it stopped departures to O’Hare from across the United States and several Canadian airports, citing an outage and communications problems. Chicago Midway followed with a departure stop at 3:31 p.m. The agency issued the nationwide order at 3:54 p.m., saying all departing traffic should remain on the ground until further notice.
Transportation Secretary Sean Duffy said the FAA began experiencing instability in radar and communications at its en route centers and approach control facilities at about 3:36 p.m. He described overloaded analog telecommunications switches and routers that delivered inconsistent data. Duffy said the system had not lost all radar or telecommunications. The FAA’s public statement said communications issues were affecting multiple Air Route Traffic Control Centers and that technicians were investigating; it described the information as preliminary and subject to change.
Duffy said more than 3,500 aircraft were airborne when the stop began, falling to fewer than 400 by 8 p.m. Medevac flights, life-saving cargo and law enforcement flights were allowed to continue, according to the source account. FAA advisories show the agency extending flight-plan drop times and coordinating departures as facilities recovered. The nationwide stop was cancelled at 8:16 p.m.; individual airport and airline disruptions continued afterward as carriers repositioned aircraft and crews.
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 Stop Disrupted Air Travel
A nationwide departure hold affects more than flights waiting at airport gates. Aircraft already in the air may need to hold or divert, while airlines must adjust crews, aircraft and connecting itineraries as departures pause. Even after a broad restriction is lifted, those operational knock-on effects can continue through the evening and into the next day.
The disruption also crossed national borders. The source account says Eurocontrol suspended US-bound departures from its member states at the FAA’s request between 22:00 UTC on Nov. 13 and 05:00 UTC on Nov. 14. It also cites reports that Sydney Airport held US-bound flights and Air Canada cancelled flights between Canada and the United States. Those measures show how a problem in US air traffic control can affect international schedules.
FlightAware counted 9,159 cancellations within, into or out of the United States on Friday, and 3,515 more by 7:58 a.m. Eastern Time Saturday. These are all cancellations recorded for those periods, not a count attributed solely to the FAA stop. The distinction matters: weather, airline operations and other causes can also contribute, and the source material does not provide a cancellation total caused only by this event.
Products Worth Considering

Apple Watch Series 10 GPS 46mm with Silver Aluminum Case and Blue Cloud Sport Loop

LG UltraGear 45GX950A-B 45-Inch 5K2K Curved OLED Gaming Monitor

Bose TV Speaker Compact Soundbar with Bluetooth and HDMI-ARC, Black
As an affiliate, we earn on qualifying purchases.
From Chicago Delays to a National Hold
The FAA’s advisories indicate the disruption escalated in stages rather than beginning with an immediate national shutdown. Early Friday delays cited weather and traffic conditions. The first cited equipment problems at O’Hare at 3:21 p.m.; departure restrictions for O’Hare and Midway followed. At 3:30 p.m., the Command Center activated a diversion recovery tool for all airports. The nationwide ground stop came shortly afterward.
During the stop, the FAA told operators to expect airborne holding and extended flight-plan drop times for all en route centers to 240 minutes. The advisories said departures would be released as en route facilities recovered and in coordination with the Command Center. Some coastal facilities were releasing international departures by 7:37 p.m., before the nationwide stop was formally cancelled.
The source account says the FAA has 21 en route centers, citing an FAA-commissioned 2023 review. These facilities handle aircraft traveling between airports, while approach control facilities manage traffic near airports. The reported issue involved communications and equipment across facilities, but the available public statements do not identify a specific failed component or give a complete technical account.
““ALL AIRPORTS ARE GROUND STOPPED.””
— FAA Command Center advisory
Cause and Cybersecurity Questions
The precise root cause remains unconfirmed. Duffy attributed the instability to overloaded analog telecommunications switches and routers, but the FAA had not published a written root-cause report in the source material. The agency’s initial statement was marked preliminary and subject to change, and it did not identify a specific component failure or explain why the systems became unstable.
Mullin said officials had seen “zero evidence” of a cyberattack and that the problem appeared mechanically driven, but he also said officials would not rule out that possibility. The source account says Duffy and the maker of the FAA’s new SMART air traffic tool said SMART was not connected to the failed equipment. The available information does not include an independent technical investigation or a final determination that rules out every possible cause.
The full scale of the travel impact is also not isolated in the cancellation figures. The reported FlightAware totals cover all cancellations in the stated periods, rather than only flights cancelled because of the ground stop. The source material does not provide a verified count of passengers affected or a definitive event-specific total of cancelled and delayed flights.
FAA Review and Modernization Plans
The FAA’s next key step is to explain what failed and how the communications problems spread across facilities. Its initial statement said technicians were investigating, but the source material does not give a publication date for a final report or a timetable for releasing technical findings. Until those details are available, officials’ descriptions should be treated as their account of the event rather than a published final determination.
Duffy has argued that the disruption reflects aging FAA technology and said he wants $50 billion for a new system. His warning that similar events could occur without new funding is a prediction, not a finding that another nationwide stop is scheduled or inevitable. Any funding decision would be up to Congress, and the source material does not identify an enacted appropriation or a specific replacement timeline.
For travelers, the immediate follow-up is to check directly with airlines for changes to flights and connections, since local delays and cancellations continued after the nationwide order ended. The next major public milestone will be a fuller FAA account of the failure, including whether the agency confirms Duffy’s explanation and what steps it plans to take to reduce the risk of another disruption.
Key Questions
When did the FAA’s nationwide ground stop begin and end?
FAA Command Center advisories place the event from about 3:53 p.m. to 8:16 p.m. Eastern Time on Nov. 13, 2026, a span of about 4 hours and 23 minutes.
Why did the FAA stop departures?
The FAA said communications issues affected multiple Air Route Traffic Control Centers. Transportation Secretary Sean Duffy described instability in radar and communications and said overloaded analog telecommunications equipment delivered inconsistent data. A written final root-cause report was not available in the source material.
Was the disruption caused by a cyberattack?
Officials had not established that. Homeland Security Secretary Markwayne Mullin said officials had seen “zero evidence” of a cyberattack, but said they were not ruling one out.
How many flights were cancelled because of the stop?
The source material does not give a verified count caused only by the ground stop. FlightAware recorded 9,159 cancellations within, into or out of the United States on Friday, but that figure includes cancellations from all causes.
Did the FAA say this could happen again?
Sean Duffy warned that similar events could occur unless Congress funds a new system and called for $50 billion. That was his assessment; the source material does not report a scheduled repeat disruption or a final FAA risk analysis.
Source: ThorstenMeyerAI.com
