FAA Halted US Departures for Just Over Four Hours After a Network Flood
The nationwide ground stop ran from about 15:30 to 20:15 Eastern Time on 13 November. The FAA said legacy equipment became unstable when data flooded its network, and that it had no indication of a cyberattack. Weekend recovery followed.
WASHINGTON, United States – The US Federal Aviation Administration issued a nationwide ground stop at about 15:30 Eastern Time on 13 November after instability on its telecommunications network, then reopened the airspace at 20:15 the same evening. The disruption, just over four hours, was followed by a weekend of cancelled and delayed flights. The FAA said it had no indication of a cyberattack.
Highlights
- The FAA issued a nationwide ground stop at about 15:30 Eastern Time on 13 November.
- US airspace was reopened at 20:15 the same evening, after just over four hours.
- Seventeen of the FAA’s 22 en-route centers were affected.
- About 3,500 aircraft already in the air landed safely, the FAA said.
- Operators cancelled about 12,462 flights that Friday, not all because of the stop.
In a 15 November questions-and-answers note, the FAA said the stop was issued “out of an abundance of caution” after a technical problem at approximately 15:30 Eastern Time. Transportation Secretary Sean Duffy, briefing reporters at the White House that evening, timed the start of the instability at 15:36. “At 3:36 p.m. we experienced instability for our radar and our communications and our centers and our TRACONs across the country,” he said. “We had over 3,500 airplanes in the air.”
The FAA later said its “legacy equipment became unstable when data began flooding the FAA FTI network, at a rate of 1,000 connection attempts every 4 to 5 seconds.” That disrupted aircraft communications and radar feeds. The initial investigation pointed to two possible sources of the excess data: a radar site in Amarillo, Texas, and a radio communications site in El Dorado, Arkansas, where L3Harris, the FAA’s network service provider, had been doing work that included deploying a new router. L3Harris blocked those two locations, the FAA said, and the network stabilised. The agency said it then disabled the broadcasting function on the new routers and, as a precaution, on more than 60 other Juniper routers, and paused further installations.
Instability began at 17 of the FAA’s 22 Air Route Traffic Control Centers and spread into several Terminal Radar Approach Controls. The agency said it did not lose all radio or radar, that every aircraft landed safely, and that critical medical, law enforcement and military flights continued. “Based on all available evidence, we have no indication that this was a cyberattack or an outside nefarious actor,” the FAA said.

US Department of Homeland Security Secretary Markwayne Mullin, appearing with Duffy, told reporters: “I just can’t say this enough: all of your loved ones are safe. We are working to resolve the issue, and we hope to have operations up and normal at some point.” In a DHS account of the briefing he also said: “We have seen zero evidence that this is a cyberattack or an SI attack.” In the room, asked whether he could be 100% certain, he said: “There’s nothing completely certain right now.” Duffy said the fix gave “a pretty good indication that it was a legacy network problem,” while adding that he did not want to rule out “nefarious activity” while cybersecurity teams were still looking.
The FAA said that on Friday, 13 November, operators cancelled approximately 12,462 flights, including 9,082 by major airlines, and that “not all cancellations were directly caused by the nationwide ground stop.” Reuters, citing Flightradar24, reported that nearly 10,000 flights had been cancelled by 23:30 that night, including more than 2,200 each at Delta Air Lines and American Airlines and 1,800 at United Airlines. Recovery continued through the weekend. A separate United technology issue on 16 November, which the airline said was not an FAA equipment problem, is covered in a companion story.
For a full account of the week’s other outages, and the official assessment that they were not a coordinated cyberattack, see the overview.
More from this series
- US officials say a week of outages was not a coordinated cyberattack
- JPMorgan Chase software bug delayed payments across several US banks
- United Airlines resolved a system outage that delayed departing flights
- Microsoft said a July bug caused a nearly 24-hour Microsoft 365 outage
- Apple blamed an internal update for outages as officials ruled out a cyberattack
Sources
- FAA, 15 November 2026: Nationwide Ground Stop: Questions and Answers
- US Department of Homeland Security, 13 November 2026: Secretary Mullin and Secretary Duffy address nationwide FAA ground stop
- The White House, 13 November 2026: Secretary Mullin and Secretary Duffy brief members of the press on the FAA ground stop
- The White House, 13 November 2026: Secretary Mullin and Secretary Duffy provide an update on the FAA national ground stop
- Associated Press, 14 November 2026: FAA halts installation of routers that led to ground stop
- Reuters, 13 November 2026: US to resume flights after air traffic network failure sparks chaos
Written by
Tumisang Bogwasi
Tumisang Bogwasi, Founder & CEO of Brimco. 2X Award-Winning Entrepreneur. It all started with a popsicle stand.
