FAA nationwide ground stop: Why Mullin says it happened
The FAA nationwide ground stop on Friday stemmed from a telecommunications outage after outdated air traffic control systems overloaded, Homeland Security Secretary Markwayne Mullin and Transportation Secretary Sean Duffy said. Officials stressed the public was never in danger, and the stop has since been lifted.
For only the third time in U.S. history, the Federal Aviation Administration halted flights coast to coast on Friday, Nov. 13, 2026. Massive delays hit thousands of travelers before the order was lifted later that evening. Officials framed the freeze as a safety precaution, not a national security crisis.
Key Takeaways
- The FAA nationwide ground stop followed a temporary telecommunications outage tied to overloaded, outdated network routers.
- Homeland Security Secretary Markwayne Mullin said the public was never in danger and called the event “not another 9/11.”
- Transportation Secretary Sean Duffy blamed ’80s-era “copper lines” colliding with newer technology and urged Congress for $50 billion in emergency funding.
- Air Space Intelligence and Microsoft denied links to the FAA’s new SMART AI tool or a Microsoft outage; the ground stop has been lifted.
- FlightAware’s Misery Map showed about 2,406 delays and 763 cancellations amid the chaos.
Why did the FAA nationwide ground stop happen?
The FAA first said it halted travel “due to extraordinary circumstances and for reasons of safety,” then clarified that a temporary telecommunications outage prompted the order “out of an abundance of caution.” International flights were to be handled case by case, and officials said every flight had been accounted for.
CBS News, citing multiple sources, reported that an update to a private communications network used by air traffic controllers forced a system reboot and impeded communications at the nation’s 22 regional air traffic control centers. That network is operated by Florida-based L3Harris, according to CBS.
Hours later, Duffy and Mullin said outdated air traffic control gear buckled under newer systems’ processing demands. “Our routers got overloaded by the data,” Duffy said, describing affected lines as “’80s copper lines.” The overload caused instability at Terminal Radar Approach Control (TRACON) facilities and Air Route Traffic Control Centers (ARTCCs). Duffy said only older lines were affected, not newly installed ATC tech.
CNN separately reported that the FAA told airlines the problem originated with “network routers.” As of early evening, some insiders said investigators were still piecing together the blackout’s exact circumstances even after the stop was lifted, according to Mashable’s reporting.
Was the FAA nationwide ground stop linked to AI or a cyberattack?
Online speculation flared quickly. Some users tied the freeze to the FAA’s new AI-powered Strategic Management of Airspace, Routes and Trajectories system, known as SMART. Others pointed to a recent Microsoft outage. Both theories met firm pushback from the companies involved.
Air Space Intelligence (ASI), the firm behind SMART, stated the ground stop was “not based on or a result of the SMART system, any product of ASI or our integration with FAA and ATC.” Microsoft said it had “no indication that the FAA’s nationwide ground stop is related to any Microsoft services.”
SMART is a cloud-based tool meant to help controllers evaluate airline schedules, weather, airport capacity, and airspace constraints. Ars Technica reported it had been active in Washington, D.C., airspace since at least Sept. 21, with a Nov. 10 rollout to 22 centers nationwide, and that it had helped reroute 180 flights. Officials have not confirmed any connection between SMART and Friday’s outage.
When asked whether AI played a role, Mullin said officials couldn’t “rule anything out.” He later said there was no indication of a cybersecurity attack, though interference could not be ruled out entirely. “There’s nothing completely certain right now. It does not appear that way,” he said. “The public was never at danger. There was never any lives at risk. There were no flights at risk.” Mullin also reiterated there were “no indications” of foreign interference at the time of the briefing.
How does Friday’s freeze compare with past nationwide stops?
Nationwide ground stops remain rare, which is why Friday’s order stirred memories of darker days. The FAA has grounded all U.S. flights only twice before: on Sept. 11, 2001, and on Jan. 11, 2023, when a Notice to Air Missions (NOTAM) system failure froze traffic for about 90 minutes. In 2024, the CrowdStrike IT outage prompted major airlines to issue a broader global stoppage, but that was not the same coast-to-coast FAA order.
Mullin moved quickly to separate Friday’s tech failure from 9/11-era fear. “This is not another 9/11,” he said, according to KOMO News. “There is no fear to the public. I want to make sure we say this again — there is no reason for the public to be afraid or scared for your loved ones.” That contrast—then a security catastrophe, now an aging network reboot—is the story’s clearest then-and-now lesson for anyone following aviation history in our Nostalgia: Then & Now coverage.
The infrastructure backdrop is familiar to aviation watchers. The FAA is mid-modernization, including plans to phase out floppy disks for weather, airport status, and equipment updates. Duffy used Friday’s episode to press Congress for $50 billion in emergency funding to overhaul the system completely. For travelers, the “now” looked more like cascading delays than a lasting lockdown: airports including JFK and Dulles urged passengers to confirm flight status before heading to the terminal.
What should travelers know after the ground stop was lifted?
By Friday evening, airline sources said the ground stop had been lifted. Residual delays and cancellations still rippled through the system. FlightAware’s Misery Map logged 2,406 delays and 763 cancellations that day, versus 410 delays and six cancellations at the same time the day before.
Secretary Duffy confirmed the stoppage earlier on X, saying the FAA acted after a communication issue impacting all Air Route Traffic Control Centers and that technicians were investigating. Even after flights resumed, the Department of Transportation and Department of Homeland Security continued briefing on cause and next steps.
The takeaway for the traveling public is practical: Friday’s FAA nationwide ground stop was a communications and legacy-systems failure handled as a precaution, not an attack. Mullin’s message stayed consistent—no public danger, no flights at risk—and the stop itself ended the same day, even as delays lingered and the modernization debate grew louder.