Blog

The FAA Ground Stop

Written by Bola Ogbara | Nov 20, 2026, 2:32:19 PM

The FAA ground stop, which cancelled over 12,000 flights and left over a million Americans stranded, triggered fears about a possible cyberattack. 

On November 13th, 2026, the Federal Aviation Administration (FAA) issued a nationwide ground stop, a four-hour pause that prevented planes from taking off in what has been the longest airplane shutdown since the terrorist attacks on September 11th, 2001. The ground stop affected the millions of Americans taking flights on Friday, and resulted in delays and cancellations that poured into the weekend. The outage, which started at 3:36 pm, cancelled over 12,000 flights across the country, leaving many travelers stranded and frustrated with the delays, especially as the reason for the stoppage was unclear at first. The widespread impact of a ground stop also inflamed concern about a possible cyberattack and general security as flyers wondered when it would be safe to travel by plane again.

 

At the time of the outage, the cause was attributed to telecommunications issues. Secretary of the Department of Homeland Security (DHS), Markwayne Mullin, explained that a cyberattack was likely not to blame shortly after the ground stop, saying: “There was no indication as of yet that this was a nefarious attack against us. It’s just a telecommunication outage as of right now”. Though a congressional official around the time shared that their correspondence with the White House indicated that they were still unclear about the cause, Mullin maintained that the incident was “not another 9/11”, but simply “a telecommunications outage.”

 

Besides an intrusion, another theory for the pause gained traction as news swirled about the FAA’s decision. Only a couple of days before the ground stop, on November 10th, the FAA rolled out a new artificial intelligence (AI) tool, the Strategic Management of Airspace, Routes and Trajectories system (SMART) at all 22 air traffic control centers. SMART, which was first implemented in a few traffic control centers on September 21st, 2026, is meant to synthesize “200 data streams - including weather patterns, flight paths, traffic flow, and controller staffing metrics - into one platform… to provide a comprehensive visualization of where planes are going, how much traffic the system can handle, and where congestion or weather could cause challenges.”

 

The program’s original launch in Washington D.C. received some pushback by Democratic Representatives who asked for SMART to be paused “as we have not seen any safety evaluation and testing reports, nor have we ​been made aware of any efforts to train aviation safety personnel on how best ⁠to use the tool…We are deeply concerned about the integration of any AI-enabled system into air traffic control systems, where decisions are literally a matter of life or death”. Still, the system was integrated in D.C., and at least some with FAA experience supported the change. Dave Riley, a former FAA air traffic controller, called SMART “a step in the right direction”, explaining that “those specialists, those very, very well-trained operators that make really critical operations when they’re on shift” should “have world-class software.” The producers of the software, Air Space Intelligence (ASI) also denied any connection to the FAA ground stop on November 13th. “The current ground stop is not based on or a result of the SMART system, any product of ASI or our integration with FAA and ATC.”

 

DHS Secretary Mullin has also entertained the idea that AI (also called ‘super intelligence’, or SI, by the White House) could have played a role in the disruptions, tying the upgrade to the mismatch between the new tool and aging infrastructure. On November 16th, 2026, Mullin recounted a conversation with a tech expert who shared the same sentiment on Fox News: “He said, because these programs aren’t designed to work as fast as SI is. And so when they put in a program that’s able to write codes, and it goes in and it self-fixes itself, as it starts self-fixing itself, it’s like doing a change order on a house. When you change one thing in a house, everything else starts changing. That’s a ripple effect. It causes these systems to be overrun that weren’t designed to run as fast as the SI technology is today”.

 

Despite Mullin’s hypothesis, the FAA’s statement on the ground stop, released on Sunday November 15th, outright refuted the idea that the SMART system could have been to blame: “The two systems are not related. SMART is a data aggregator, and it does not feed information into the air traffic control system.” In their own words, the cause for the outage was a technical issue, as their “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. This disrupted the system and created instability with aircraft communications and radar feeds.” The FAA identified two possible sources for the data overload, a radar site based in Amarillo, Texas and a radio communications site in El Dorado, Arkansas. The latter of the two sites was actually receiving a new router when the instabilities started. The data flooding was stopped when the FAA’s network service provider blocked the two sites, and all new routers were blocked from broadcasting as a precaution.

 

Like Mullin, and Secretary of the Department of Transportation, Sean Duffy, the FAA stated that “we have no indication that this was a cyberattack or an outside nefarious actor.” While officials maintain no proof of a malicious intrusion, the overload has been compared to one, with the CNN correspondent calling the incident “a DDOS [Distributed Denial of Service] attack that the FAA did on itself” due to the onslaught of data overwhelming systems. What’s more, the Federal Bureau of Investigation (FBI) announced that their cyber teams were providing “technical assistance following Friday’s air traffic communications outage”, leading to more speculation by commenters about a possible cyberattack.

 

The main culprits being investigated by the FBI are the routers that were the sources of the data overload. The routers were being changed by government contractor L3Harris, which was scrutinized by Duffy after the ground stop: “Was it the router or were they not doing great work for us at L3Harris, either through contractor error or a faulty piece of equipment?” L3Harris explained that the router conversion was not unprecedented, as they had “completed more than 70% of the planned airspace communications conversion from legacy copper wires to a fiber optic system”. The contractor has been working with the FAA to examine the situation with “deep diagnostics testing”. CNN reported on the FBI’s plan to try to replicate the incident “to see if they can essentially have the same thing happen, and watch what it does, and maybe get to the bottom of what went wrong on Friday.”

 

As the investigation continues, other seriously impactful cyber incidents occurring around the same time have only added to anxieties about cyberattacks. The day before the FAA outage, tech giant Microsoft experienced server issues that stopped Teams, Copilot, and their email service, utilized by more than 400 million active users worldwide, from working in 74 countries and territories. On X, the company shared that they “determined a portion of infrastructure is experiencing elevated load across multiple regions, which is likely contributing to the connectivity errors”, forcing the group to start “redistributing connection traffic across our broader worldwide infrastructure to help balance the load.” Like the FAA, Microsoft expressed that it was “not aware of any malicious activity” related to the outage.

 

These outages have only continued into this week - at the commercial and federal level. On Monday, November 16th, several US financial institutions, including JPMorgan Chase, U.S. Bank, Capital One, Wells Fargo, and Bank of America, experienced technical issues that prevented customers from accessing their accounts and sending money through Zelle. The following day, the National Security Agency (NSA) also addressed an outage with NSANet, their internal communications network used with classified information. The NSA described the event as “temporary degradation during scheduled routing maintenance” and also noted there was no evidence of a cyberattack. Jay Clayton, the Director of National Intelligence, attributed the NSA disturbance to software updates related to the PHP vulnerability in a conversation with Fox Business: “The patching that has gone on following that has caused some of these systems to not come back up when you patch them as expected”.

 

Curiously, these service interruptions have not been completely universal, even while being deeply impactful. The FAA said that during the stop, “frequencies remained available to safely land commercial aircraft and ensure that critical life-saving, law enforcement and military flights continued.” The NSA also shared that “mission-critical capabilities remain fully operational and our ability to defend national security continues.” The alarm caused by these disruptions has not been assuaged by these statements or the current hardware and software modernization efforts, especially as some of the disruptions were seemingly caused by updates, and more updates (like the $50.1 billion requested by Duffy for FAA renovations) may be underway.

 

As investigations into the events continue, cybersecurity experts have found at least one thread linking the outages. An IT analytics and operations expert at the University of Notre Dame, Mike Chapple, commented that “they all point to a common theme: the complexity and fragility of the systems that we depend on every day.” Just one technical problem could easily cascade into critical systems losing functionality, causing interruptions that many Americans are now very familiar with. Addressing this risk will be necessary to preserve stability in the networks and systems that keep the country running.