WatchfulEye

Why the FAA halted all US departures on Nov. 13

Controllers at consoles in the Washington Air Route Traffic Control Center in Leesburg, Virginia.
Undated FAA file photo (published by 2007): controllers at the Washington Air Route Traffic Control Center in Leesburg, Virginia. It does not show the Nov. 13, 2026 ground stop. Photo: Federal Aviation Administration via Wikimedia Commons, public domain. Cropped.

Updated Nov. 14, 2026: The FAA cancelled the nationwide ground stop at 8:16 p.m. ET on Nov. 13, its Command Center advisories show, and Transportation Secretary Sean Duffy blamed overloaded routers in old air traffic control equipment.

The Federal Aviation Administration halted departures from every U.S. airport on Friday, Nov. 13, at 3:54 p.m. ET because of what Transportation Secretary Sean Duffy called "a communication issue impacting all Air Route Traffic Control Centers," the facilities that guide planes at high altitude. The FAA later said "a temporary telecommunications outage" was behind the stop and that flights were halted "out of an abundance of caution."

The FAA's Command Center cancelled the nationwide ground stop effective 8:16 p.m. ET, more than four hours after it began. Duffy later blamed routers in old equipment that were overloaded with data and asked Congress for $50 billion for upgrades, CNBC, Al Jazeera and the BBC reported.

Key facts

What happened?

Departures stopped at airports across the country on Friday afternoon. Planes already in the air were allowed to continue and land. Flight-tracking site Flightradar24 said about 3,100 airborne aircraft were bound for U.S. airports when the stop began, the BBC reported. Some passengers who had just landed at Los Angeles International Airport were held on the tarmac because departing planes could not leave their gates, CBS News reported, according to the BBC.

FlightAware counted about 9,000 U.S. flight cancellations and more than 7,000 delays on Friday, some of them caused by bad weather, CNBC reported. For Saturday, FlightAware counted more than 3,000 cancellations and close to 1,000 delays as of 5:45 a.m. ET, according to CNBC. Flightradar24 put cancellations of flights to and from U.S. airports at nearly 10,000 through early Saturday, the BBC reported. An earlier figure of about 11,000 flights delayed or canceled came from FlightAware data the Guardian cited on Friday evening, before the stop ended. Separately, flight-data firm Cirium said about 11,000 flights had been scheduled to leave U.S. airports after 4 p.m. ET Friday and that at least 827 had been diverted by 7:05 p.m. ET, Al Jazeera reported.

What caused the FAA ground stop?

The FAA and Duffy have described the cause as a communications failure. Duffy said the problem hit all Air Route Traffic Control Centers. The FAA said it was "a temporary telecommunications outage." An earlier Command Center notice for Chicago listed the condition as an equipment outage.

At a news conference Friday night, Duffy said routers were overloaded with data and started giving air traffic control centers inconsistent information, CNBC reported. "This is analogue telecom. Our switches, our routers actually got overloaded with data and they went down," Duffy said, the BBC reported. He said controllers did not lose all communications or radar, according to Al Jazeera. Duffy blamed an "incredibly old air traffic control system," the BBC reported. He also said the equipment that had already been replaced was not affected, Engadget reported.

Mullin said there was no evidence the ground stop was caused by a cyberattack or linked to a separate Microsoft outage, the BBC reported. He said his department was still looking, according to Engadget. The FAA said that before clearing flights to resume, "we thoroughly tested our systems to confirm they were stable and that operations remain reliable," CNBC reported.

How long did the ground stop last?

The national order took effect at 3:54 p.m. ET. At 5:46 p.m. ET the Command Center said it remained in effect, with flights to be released as en route facilities recovered. At 7:37 p.m. ET it said some coastal facilities had been able to release some international departures. The Command Center cancelled the stop at 8:16 p.m. ET, more than four hours after it began. An earlier version of this article said departures restarted at about 6 p.m. ET, based on CNBC and the FAA's airport status page. The Command Center advisories show the nationwide stop stayed in place until 8:16 p.m. ET.

Nationwide stops are rare. The Guardian reports this is the third time all U.S. departures have been grounded, after the Sept. 11, 2001, attacks and a January 2023 failure of the pilot notification system that paused departures for less than two hours. CNBC and the BBC reported it was the longest nationwide stop since the one after the Sept. 11 attacks.

What does the ground stop mean for travelers?

Disruption carried into Saturday. Duffy said on X that operations were "slowly returning to normal" but that travelers would "continue to see some delays and cancellations," the BBC reported. CNBC reported that disruptions could extend through the weekend as airlines move spare planes and crews into place. Airports and airlines told passengers to check flight status before heading out.

What does the outage mean for FAA funding?

Last year Congress approved $12.5 billion to fix the FAA's aging communications system, the Guardian reported. On Friday the FAA and the White House asked Congress for another $30.1 billion for other needs, according to the Guardian. The BBC also cited the $12.5 billion figure.

After the stop, Duffy blamed the outage on old air traffic control equipment and called for $50 billion in upgrades, the BBC and Al Jazeera reported. The reports did not say how the $50 billion relates to the $30.1 billion request.

Sources

Download on the App StoreGet it on Google Play