UPDATE: Officials Point to Overloaded Routers in Aging FAA Network for Nationwide Ground Stop; Investigation Continues
Officials say overloaded FAA switches and routers caused Friday's nationwide ground stop. No cyberattack evidence so far; the investigation continues.
UPDATE — Transportation Secretary Sean Duffy said Friday evening that overloaded switches and routers in the FAA's aging air traffic control network produced inconsistent radar and communications data, prompting the nationwide ground stop that halted departures from every U.S. airport for more than four hours. Homeland Security Secretary Markwayne Mullin said investigators have found "zero evidence" of a cyberattack so far, though they have not ruled one out.
The FAA lifted the stop at 8:15 p.m. ET, as BizJet Brief reported. For how the outage began Friday afternoon, see our earlier breaking story.
What officials say went wrong
Duffy told reporters at the White House that the trouble started at 3:36 p.m. ET, when air traffic control facilities began seeing instability in radar and communications. "Our switches, our routers actually got overloaded with data and they started to give us inconsistencies in the data from those routers and because of that we shut the system down," he said, according to Reuters.
Duffy said controllers never fully lost radar or communications and were able to land the aircraft already in the air. More than 3,500 aircraft were airborne when the stop was issued, AvWeb reported. He said recently installed digital equipment kept working, while older analog systems did not.
Nextgov reported that those inconsistencies produced intermittent radio and radar coverage, with periods when controllers could not immediately talk to pilots or see where aircraft were.
The investigation
Mullin said the breakdown appeared to happen as the FAA was installing patches and new technology that was "overwhelming the older system," Nextgov reported. "It appears this was mechanically driven. However, we're still looking," he told Reuters.
At a White House briefing with Duffy, Mullin said, "We have seen zero evidence that this is a cyberattack or an SI attack." He also said, "However, we're still looking, so we're not going to rule that out," according to Nextgov. Mullin said the National Security Agency is working with the Department of Homeland Security on the investigation, along with the Defense Department, the Cybersecurity and Infrastructure Security Agency and other agencies.
Officials were also asked whether the FAA's SMART AI tool could have played a role. Duffy said the system offers recommendations to controllers but is not connected to the agency's STARS or ERAM systems. "There's no possible way SMART would have impacted what happened," he said, AvWeb reported. Mullin said investigators had found no evidence of a "rogue AI" system, Reuters reported, though that possibility had also not been ruled out.
How flying restarted
Exceptions were made during the stop for medical flights, critical cargo and law enforcement operations, AvWeb reported. As departures resumed, Duffy said larger general aviation charter flights carrying 60 to 100 passengers would get priority over smaller aircraft.
An ATCSCC advisory cancelled the nationwide stop at 0119Z Saturday (8:19 p.m. ET Friday). Overnight, the Command Center issued several airline-requested, carrier-specific ground stops as carriers reset their networks, including a Delta-only stop at Minneapolis-St. Paul from 0207Z until it was cancelled at 0359Z (9:07 p.m. to 10:59 p.m. ET). Those carrier-specific stops are no longer listed on the FAA's morning status feed.
Saturday morning
Flightradar24 counted nearly 10,000 cancellations by 11:30 p.m. ET Friday, Reuters reported. The Washington Post reported early Saturday that more than 3,200 flights within, into or out of the United States had already been canceled for Saturday, citing FlightAware.
As of 6:43 a.m. ET Saturday, the FAA's National Airspace System Status page listed no ground stops or ground delay programs. It did list overnight airport closures at Aspen and Santa Ana, plus standing prior-permission rules for transient general aviation at Los Angeles, Las Vegas and San Diego.
What crews should do now
- Confirm your release before you launch. Check NAS Status, current NOTAMs and ATCSCC advisories for your departure, destination and alternates, and get your release from ATC.
- Expect slower handling of smaller aircraft. Duffy said larger charter flights with 60 to 100 passengers would be prioritized over smaller general aviation movements as the system recovered.
- Plan for crowded ramps. Airline recovery may tie up gates, FBO parking and fuel at major airports through the weekend.
- Re-check duty and rest. Crews who sat through Friday's stop, or who repositioned overnight, may now be up against rest requirements for Saturday trips.
- Brief passengers with official facts. Officials have blamed overloaded legacy switches and routers, said newer digital equipment kept working, and said there is no evidence so far of a cyberattack. They have not closed the investigation, and they have not promised it cannot happen again.
BizJet Brief will continue to follow the investigation and post updates as officials release more information.
Sources
- Reuters: US to resume flights after air traffic network failure sparks chaos (Nov. 13, 2026)
- AvWeb: FAA Rules Out SMART AI System as Cause of Nationwide Ground Stop (Nov. 13, 2026)
- Nextgov/FCW: Legacy tech issue led to FAA's nationwide ground stop (Nov. 13, 2026)
- DHS: ICYMI: Secretary Mullin and Secretary Duffy Address Nationwide FAA Ground Stop of All Flights (Nov. 13, 2026)
- FAA Statement on Nationwide Ground Stop (Nov. 13, 2026)
- The Washington Post: Travel chaos, flight cancellations continue following nationwide ground stop (Nov. 14, 2026)
- FAA National Airspace System Status (checked 1143Z Nov. 14, 2026)
- FAA ATCSCC Advisory 005: CNX Nationwide Ground Stop (Nov. 14, 2026)
- FAA ATCSCC Advisory 017: CDM Ground Stop, MSP, carrier DAL only (Nov. 14, 2026)
- FAA ATCSCC Advisory 032: MSP ground stop cancelled (Nov. 14, 2026)
- FAA (@FAANews) on X: ground stop lifted, systems tested (Nov. 13, 2026)
