🔍 Read the full analysis: US Flights Paused For Hours: Inside The FAA’s Unfolding Story 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 problems affected air traffic control facilities, holding departures for about four hours. Transportation Secretary Sean Duffy blamed overloaded legacy equipment, while officials said they had seen no evidence of a cyberattack; the precise cause has not been established in a published report.
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 problems affected multiple air traffic control centers. Transportation Secretary Sean Duffy said the disruption involved unstable radar and communications systems, but the FAA has not released a written report establishing the root cause.
The FAA Command Center’s advisories trace the disruption to equipment problems first reported around Chicago. At 3:21 p.m. ET, the center warned of arrival delays and airborne holding at O’Hare because of equipment issues. It stopped departures to O’Hare at 3:28 p.m., citing “EQUIPMENT / OUTAGE” and “COMMS ISSUES”; Chicago Midway followed at 3:31 p.m. The nationwide order came at 3:54 p.m., with the advisory’s event time listed as 3:53 p.m.
The FAA said communication issues affected multiple Air Route Traffic Control Centers and that technicians were investigating. Its statement described the information as preliminary and subject to change. Later advisories referred to a nationwide communications failure and said flights would be released as en route facilities recovered, in coordination with the Command Center. The FAA cancellation notice lists 8:16 p.m. as the end; Duffy said the airspace reopened at 8:15 p.m.
Duffy said more than 3,500 aircraft were airborne when the stop began and fewer than 400 remained in the air by 8 p.m. Medevac flights, life-saving cargo and law enforcement flights were permitted to continue, according to his account. 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 totals cover all cancellations on those days, not solely those caused by the ground stop.
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 Disruption Affected Air Travel
A nationwide departure hold can affect far more than flights waiting at U.S. gates. Aircraft and crews become displaced from their planned routes, and later airport-specific restrictions can continue as airlines try to restore schedules. The Friday cancellation total includes causes beyond the ground stop, but the scale of the disruption shows how a problem at air traffic control facilities can ripple through airline operations.
The impact also reached flights outside the United States. According to Xinhua, citing a Eurocontrol notice, the European air traffic agency suspended U.S.-bound departures from member states between 22:00 UTC Friday and 05:00 UTC Saturday at the FAA’s request. BBC News reported that Sydney Airport held U.S.-bound flights and Air Canada cancelled flights between Canada and the United States.
For travelers, the immediate effects were delays, cancellations and uncertainty about connections. For airlines and businesses that depend on air freight, a prolonged recovery can disrupt schedules after the ground stop itself ends. The event also focuses attention on the resilience of communications and equipment used to coordinate aircraft across the national airspace.
Products Worth Considering
Bose QuietComfort Wireless Headphones – Twilight Blue (Limited Edition)
Amazon Kindle Paperwhite (12th Generation, 2024), 16GB, 7-Inch Display, Raspberry
Bose Smart Dolby Atmos Soundbar, All-in-One Soundbar for TV, A.I. Dialogue Mode, Voice Control and Amazon Alexa Built-in, Supports Bluetooth
As an affiliate, we earn on qualifying purchases.
From Chicago Equipment Issues to a Nationwide Order
The FAA Command Center’s timeline shows a progression from local disruption to a national restriction. It first cited equipment issues at O’Hare, then stopped departures to O’Hare and Midway. At 3:30 p.m. ET, it activated a diversion recovery tool for all airports. Duffy said the nationwide problem began at 3:36 p.m., before the all-airport ground stop was issued.
The FAA’s advisories document the operational response. At 4:20 p.m., the center warned of possible airborne holding at any airport. A minute later, it extended flight-plan drop times at all en route centers to 240 minutes, allowing filed plans to remain active longer while flights were held. At 5:46 p.m., it said the stop remained in force because of communications failure and that departures would resume as facilities recovered.
The affected en route centers manage aircraft between airports. An FAA-commissioned review published in 2023 identified 21 such centers. The Command Center’s advisories later reported that some coastal facilities had released international departures before the nationwide stop was cancelled.
““We didn’t lose all telecom we didn’t lose all radar.””
— Transportation Secretary Sean Duffy
Root Cause Still Under Investigation
The FAA has not published a written root-cause report, and its initial statement said its information was preliminary. Duffy attributed the instability to older analog telecommunications switches and routers that became overloaded with data and delivered inconsistent information. That explanation is an official account, but the available material does not include a final technical finding detailing which equipment failed, why it failed or how the failure spread.
Mullin said officials had found no evidence of a cyberattack at that point, while cautioning that they would not rule one out. Duffy and the maker of the FAA’s new SMART AI traffic tool said the tool was not connected to the equipment involved. The source material does not provide a published technical investigation substantiating a complete account of the failure or its precise operational cause.
The cancellation totals also require care: FlightAware’s figures include every cancellation on Friday and Saturday, not just those attributable to the FAA order. The number of cancellations directly caused by the ground stop, and the full cost of the disruption, are not established by those daily totals.
FAA Findings and Modernization Debate
The next major step is a fuller account from the FAA of what failed, how facilities recovered and what measures could reduce the chance of a repeat. The agency said technicians were investigating, but the source material gives no publication date for a final report. Until more findings are released, the technical cause should be treated as unresolved.
Duffy said he wants $50 billion for a new system and warned that similar disruptions could happen without congressional funding. That is his assessment of the risk and his stated funding request, not a confirmed forecast that another shutdown will occur. Further congressional action and any FAA modernization plan were not specified in the source material.
Travelers affected by the event should check directly with their airlines for current flight and rebooking information. The FAA’s subsequent airport- and airline-specific restrictions, along with the continuing movement of aircraft and crews, meant that the end of the national ground stop did not itself restore normal schedules immediately.
Key Questions
When did the nationwide ground stop begin and end?
The FAA Command Center issued the order at 3:54 p.m. ET on Nov. 13, with the event time listed as 3:53 p.m. Its cancellation notice lists 8:16 p.m. ET as the end; Transportation Secretary Sean Duffy said the airspace reopened at 8:15 p.m.
What caused the FAA to halt departures?
The FAA initially cited communications issues affecting multiple Air Route Traffic Control Centers. Duffy said unstable radar and communications involved overloaded legacy switches and routers. The FAA had not published a final root-cause report in the source material.
Was the ground stop caused by a cyberattack?
Homeland Security Secretary Markwayne Mullin said officials had seen zero evidence of a cyberattack, while saying they would not rule one out. The cause remained under investigation.
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. ET Saturday. These are all-cause daily totals and are not counts of cancellations attributed solely to the ground stop.
Will another nationwide ground stop happen?
No future event is confirmed. Duffy warned that similar disruptions could occur without funding for a new system and said he wants $50 billion. That warning is his assessment; the source material does not establish a timeline or probability for another shutdown.
Source: ThorstenMeyerAI.com
