🔍 Read the full analysis: FAA Orders Hours-Long Flight Pause: What We Know About The Disruption on ThorstenMeyerAI.com
Get business pricing on office and shipping supplies
- 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 reported radar and communications instability at air traffic facilities. The stop lasted about four hours and 23 minutes, and flight cancellations continued into Saturday. Officials said they had seen no evidence of a cyberattack, but a written root-cause report has not been released.
The Federal Aviation Administration halted departures at airports across the United States for about four hours and 23 minutes on Friday, Nov. 13, after communications and radar instability affected air traffic facilities. The disruption stranded travelers, forced airlines to rearrange flights and crews, and prompted officials to investigate what failed.
The FAA Command Center issued its nationwide ground-stop advisory at 3:54 p.m. Eastern Time, directing departing aircraft to remain on the ground. The notice cited “extraordinary circumstances” and safety. The FAA later listed the cancellation time as 8:16 p.m.; Transportation Secretary Sean Duffy said the airspace reopened at 8:15 p.m. The advisory’s event times, from 3:53 to 8:16 p.m., put the stop at roughly four hours and 23 minutes.
Duffy said the problem began at 3:36 p.m. and involved instability in radar and communications at en route centers and approach-control facilities around the country. He attributed the inconsistent data to older analog telecommunications switches and routers becoming overloaded. He said the system did not lose all radar or all communications. The FAA’s initial statement said communication issues affected multiple Air Route Traffic Control Centers and that technicians were investigating; it described the information as preliminary and subject to change.
More than 3,500 aircraft were airborne when the order came, Duffy said, falling to fewer than 400 by 8 p.m. Medevac flights, life-saving cargo and law-enforcement flights were permitted to continue. FAA advisories documented earlier equipment-related trouble at Chicago O’Hare and Midway, followed by nationwide measures including extended flight-plan times and coordinated releases as facilities recovered. The agency cancelled its national stop at 8:16 p.m., but airport- and airline-specific restrictions continued as carriers worked to reposition aircraft and crews.
FlightAware counted 9,159 cancellations within, into or out of the United States on Friday, and 9,896 worldwide for the day. It counted a further 3,515 cancellations by 7:58 a.m. Eastern on Saturday. Those are all-day totals, not counts attributed solely to the FAA order; the available figures do not isolate how many cancellations the ground stop caused.
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 halt affects far more than flights scheduled during the order. Aircraft and crews can end up in the wrong places, and passengers may miss connections even after departures resume. Friday’s continued airport-specific restrictions and Saturday’s cancellations show that the operational effects lasted beyond the period when the national stop was formally in force.
The episode also exposed how much U.S. air travel depends on communications and coordination across air traffic facilities. Duffy warned that similar disruptions could recur without investment in a replacement system and said he wants $50 billion for modernization. That is his argument for funding, not an established estimate of the cost or a guarantee that a new system would prevent future outages.
For travelers, the immediate concern is whether a particular flight is operating, not simply whether the nationwide restriction has ended. The cancellation totals indicate the scale of disruption, but they do not identify each cancellation’s cause. Passengers and businesses should distinguish the confirmed system-wide halt from the broader flight counts reported for the same period.
Popular right now

Dyson V15 Detect Origin Cordless Vacuum

De'Longhi La Specialista Arte Evo Semi-Automatic Espresso Machine with Grinder and Cold Brew

Breville Barista Express Espresso Machine with Grinder, Black Truffle
As an affiliate, we earn on qualifying purchases.
From Chicago Equipment Alerts to a National Halt
FAA advisories trace the first equipment-related warnings that afternoon to Chicago. At 3:21 p.m., the Command Center reported arrival delays and airborne holding at O’Hare of up to 30 minutes because of equipment issues. At 3:28 p.m., it stopped departures to O’Hare from U.S. airports and several Canadian airports, citing equipment and communications problems. Midway followed at 3:31 p.m. The FAA also activated a diversion recovery tool for all airports that afternoon.
The national order came shortly after those local measures. During the stop, advisories warned of holding at any airport and extended the time flight plans could remain active to 240 minutes because of a nationwide communications failure. Later notices said flights could be released in coordination with the Command Center as en route facilities recovered. The sequence describes the FAA’s operational response; it does not, by itself, establish the underlying technical cause.
The disruption also affected international schedules. According to the supplied reporting, European air traffic manager Eurocontrol suspended U.S.-bound departures from its member states from 10 p.m. UTC Friday until 5 a.m. UTC Saturday at the FAA’s request. BBC News reported that Sydney Airport held U.S.-bound flights and that Air Canada cancelled flights between Canada and the United States.
““We didn’t lose all telecom we didn’t lose all radar.””
— Transportation Secretary Sean Duffy
The Cause Is Not Yet Settled
Officials have not released a written root-cause report, and the FAA’s initial account was expressly preliminary and subject to change. Duffy described overloaded analog switches and routers delivering inconsistent data, but the available material does not include a technical investigation showing exactly which equipment failed, why it became overloaded or how the problems spread across facilities.
Mullin said officials had found no evidence of a cyberattack at the time of his remarks, while also saying they would not rule one out. That is not confirmation of a cyber incident. Duffy and the maker of the FAA’s new SMART traffic tool said the tool was not connected to the failed equipment. Officials also said the disruption was mechanically driven, but a final public account has not established the full chain of events.
The precise number of flights and passengers affected by the order is also not established by the supplied figures. FlightAware’s cancellation counts cover all cancellations during each reporting period, including those not necessarily caused by the ground stop. The source material does not give a confirmed passenger total or a definitive breakdown of delays and cancellations directly attributable to the FAA action.
Investigation and System Funding
The FAA said technicians were investigating, but the supplied information gives no publication date for a final report or detailed technical findings. Those findings will be needed to clarify what equipment failed, how the FAA restored service and whether changes are required to reduce the chance of a repeat disruption.
In the meantime, airlines must continue handling the effects on aircraft, crews and passenger itineraries. Travelers should check directly with their carrier for current flight status, since airport-level restrictions and cancellations can continue after a national ground stop ends.
Duffy has urged Congress to provide $50 billion for a new air traffic system, warning that outages could happen again without modernization. The funding request and the warning are his stated position; the supplied material does not establish whether Congress will approve the money, what a replacement program would involve or when any new equipment could be deployed.
Key Questions
How long did the FAA ground stop last?
FAA advisory times indicate the nationwide stop ran from about 3:53 p.m. to 8:16 p.m. Eastern on Nov. 13, or roughly four hours and 23 minutes. Duffy said the airspace reopened at 8:15 p.m.
What did officials say caused the disruption?
Duffy said radar and communications became unstable at air traffic facilities and attributed inconsistent data to overloaded older telecommunications switches and routers. The FAA has not published a written root-cause report, so the full technical explanation remains unconfirmed.
Was the outage caused by a cyberattack?
Homeland Security Secretary Markwayne Mullin said officials had seen no evidence of a cyberattack and that the issue appeared mechanically driven, while saying investigators would not rule out other possibilities. That does not establish that a cyberattack occurred.
How many flights were cancelled?
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 Saturday. These figures cover all cancellations in those periods, not only those caused by the ground stop.
Could the FAA order another ground stop?
Duffy warned that similar disruptions could happen again without investment in a new system. The FAA has not published its final findings, and the source material does not establish whether a repeat is likely or what specific measures would prevent one.
Source: ThorstenMeyerAI.com
