🔍 Read the full analysis: What Remains Unclear After The FAA’s 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 halted departures at U.S. airports for about four hours on Nov. 13 after communications problems affected multiple air traffic control centers. Officials described equipment instability but have not released a written root-cause report; they also said they had seen no evidence of a cyberattack while declining to rule one out.
The Federal Aviation Administration lifted a nationwide ground stop on Friday, Nov. 13, after communications problems affected multiple air traffic control centers and held departures at U.S. airports for about four hours and 23 minutes. Officials have described instability in radar and communications equipment, but the FAA has not published a written account identifying the root cause, leaving open questions about the failure and the risk of a repeat.
The FAA Command Center issued its nationwide order at 3:54 p.m. Eastern time, directing aircraft operators to keep departing flights grounded. The advisory cited “extraordinary circumstances” and safety. The agency’s cancellation notice gives 8:16 p.m. as the end of the stop; Transportation Secretary Sean Duffy said the airspace reopened at 8:15 p.m. The FAA’s advisories mark the event from 3:53 p.m. to 8:16 p.m.
The disruption began before the nationwide order. At 3:21 p.m., an FAA advisory cited equipment issues causing delays and airborne holding at Chicago O’Hare. The Command Center then restricted departures to O’Hare and Chicago Midway. The FAA said communication issues were affecting multiple Air Route Traffic Control Centers, while technicians investigated. The agency labeled its account preliminary and subject to change.
Duffy said the FAA experienced instability in radar and communications at en route centers and approach control facilities. He attributed the problem to older analog telecommunications switches and routers that became overloaded with data, delivering inconsistent information. He said it was not a total loss of radar or communications. The FAA allowed some flights, including medevac, life-saving cargo and law enforcement operations, to continue. Duffy said more than 3,500 aircraft were airborne when the halt began; fewer than 400 remained in the air by 8 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
Disruption Reached Beyond U.S. Airports
The ground stop affected passengers, airlines and flight operations across the country, and its effects continued after the FAA lifted the order. Airlines still had to reposition aircraft and crews, while passengers faced cancellations and delays. FlightAware counted 9,159 cancellations within, into or out of the United States on Friday, out of 9,896 total cancellations across its count. It reported another 3,515 cancellations by 7:58 a.m. Eastern on Saturday. Those figures cover all cancellations in the stated periods, not just those caused by the FAA order.
The disruption also affected international operations. Eurocontrol suspended U.S.-bound departures from its member states between 22:00 UTC on Nov. 13 and 05:00 UTC on Nov. 14, according to a notice cited by Xinhua. BBC News reported that Sydney Airport held U.S.-bound flights and that Air Canada cancelled flights between Canada and the United States. These measures show how a domestic air traffic control problem can disrupt routes well beyond U.S. airports.
For travelers, the event highlights the difference between the end of a ground stop and a return to normal schedules. The FAA’s nationwide restriction ended Friday evening, but individual airports and airlines continued to issue restrictions and cancellations as they managed the backlog. The full passenger impact attributable specifically to the stop has not been established in the supplied figures.
Products Worth Considering
Apple AirPods Pro 3 Wireless Earbuds with Active Noise Cancellation
Bose Smart Dolby Atmos Soundbar, All-in-One Soundbar for TV, A.I. Dialogue Mode, Voice Control and Amazon Alexa Built-in, Supports Bluetooth
Jackery Explorer 2000 v2 Portable Power Station with Two 200W Solar Panels
As an affiliate, we earn on qualifying purchases.
How the Halt Developed
The FAA’s advisories trace the escalation from local problems to a national restriction. Chicago-area equipment warnings appeared first, followed by departure restrictions for O’Hare and Midway. At 3:30 p.m., the Command Center activated a diversion recovery tool for all airports. Duffy placed the onset of the nationwide problem at 3:36 p.m.; the national ground stop followed less than 20 minutes later.
During the halt, FAA notices described airborne holding and extended flight-plan drop times across en route centers. At 5:46 p.m., the Command Center said the stop remained in force because of a communications failure and that flights would be released as facilities recovered, in coordination with the Command Center. A later notice said some coastal facilities had begun releasing international departures. The nationwide order was cancelled at 8:16 p.m., though airport- and airline-specific restrictions continued into the night.
The scale of the disruption has renewed attention on aging aviation infrastructure. Duffy has argued that the system needs replacement and called for $50 billion in congressional funding. The source material identifies 21 en route centers, citing an FAA-commissioned 2023 review, but does not establish which particular component or facility initiated the failure.
“We didn’t lose all telecom we didn’t lose all radar.”
— Transportation Secretary Sean Duffy
The Failure’s Root Cause Is Unknown
The clearest unresolved issue is what specifically failed and why. Duffy described overloaded analog switches and routers, but the FAA has not issued a written root-cause report identifying the equipment, the initiating fault or how the problem spread across facilities. The FAA’s public statement was marked preliminary, so its description may change as the investigation proceeds.
Officials have not ruled out a cyberattack. Mullin said investigators had seen no evidence of one and that the problem appeared mechanical, while explicitly declining to exclude that possibility. Duffy and the maker of the FAA’s new SMART air traffic tool said the tool was not connected to the failed equipment. The available material does not provide a technical investigation establishing the precise failure path or independently documenting those explanations.
It is also unclear whether the problem was confined to particular equipment or reflected a broader weakness in the network, what corrective work has already been completed, and what safeguards would prevent a similar disruption. The cancellation totals do not isolate how many flights were cancelled because of the ground stop, and the eventual total passenger impact is not specified.
Investigators Must Explain the Failure
The next public milestone is a fuller FAA account of the investigation, including the affected equipment, the failure sequence and any repairs or operational changes. The agency had said technicians were investigating, but the supplied source material includes no published root-cause report or date for one. Until those details are released, the immediate cause and the effectiveness of any corrective measures remain unconfirmed.
Congress may also weigh Duffy’s request for $50 billion to replace or upgrade aviation systems. His warning that further disruptions could occur without new funding is a statement about future risk, not a finding that another halt is scheduled or inevitable. Travelers should look to airlines and airports for current flight information, since local restrictions and schedule recovery can continue after a nationwide order ends.
Key Questions
How long did the FAA’s nationwide ground stop last?
The FAA’s advisories place the event from 3:53 p.m. to 8:16 p.m. Eastern on Nov. 13, about four hours and 23 minutes. Duffy said the airspace reopened at 8:15 p.m.
What caused the flight halt?
Officials described instability in radar and communications systems at multiple air traffic control facilities. Duffy attributed it to older analog switches and routers becoming overloaded, but the FAA has not published a written report establishing the root cause.
Was the disruption caused by a cyberattack?
Officials have not confirmed a cyberattack. Homeland Security Secretary Markwayne Mullin said officials had seen no evidence of one and that the failure appeared mechanical, while saying they would not rule it out.
Were all flights grounded?
The FAA ordered departures at U.S. airports to remain grounded, with exceptions and case-by-case handling for some operations. Duffy said medevac, life-saving cargo and law enforcement flights could continue, and inbound international flights were to be managed individually.
How many flights were cancelled because of the halt?
The supplied FlightAware figures count all cancellations in their stated periods, not only those caused by the ground stop. 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; a specific total attributable to the halt is not provided.
Source: ThorstenMeyerAI.com
