Developing storyHigh severity

FAA nationwide ground stop: officials see no hacking, FBI reportedly probes software update

US officials say the FAA's 13 November nationwide departure halt shows no sign of hacking, while investigators reportedly examine a network software update.

By Mr Elite Published 7 min read

Severity
High
Status
Still developing
Sources
1
Last checked

The short version

  • The FAA halted flight departures nationwide on 13 November after a communications problem hit its air route traffic control centers, SecurityWeek reported.
  • The order was lifted at 8:15 pm ET, more than four hours later, and officials expect delays for several days.
  • Homeland Security Secretary Markwayne Mullin said there were no signs of a cyberattack but did not rule it out.
  • CBS News reported the outage followed an update to a private network operated by L3Harris; no official root cause has been announced.

What happened

The Federal Aviation Administration (FAA) halted flight departures across the United States on Friday 13 November after a communications problem hit its air route traffic control centers, SecurityWeek reported. The ground stop was lifted at 8:15 pm ET, more than four hours after it began, and thousands of flights were disrupted.

Departures have resumed, but officials expect delays to continue for several days, according to SecurityWeek. The FAA described the halt as a precaution.

Homeland Security Secretary Markwayne Mullin told reporters at the White House that the incident did not appear to be a cyberattack and looked mechanical. He said investigators had seen no chatter and no footprints, but added that agencies were still looking and would not rule an attack out. Mullin said the NSA, the Department of Defense, CISA and other agencies were involved.

Bloomberg reported, citing a person familiar with the matter, that the FBI does not believe a cyberattack or criminal activity was behind the outage. The person said investigators were looking at a software update as a possible cause.

Officials also said the incident was unrelated to the Microsoft outage earlier in the week, and that the FAA's recently deployed AI systems played no role, SecurityWeek reported.

Why it happened

No official root cause has been announced. What exists so far is a set of accounts from officials and press reports, and they overlap rather than match exactly.

Transportation Secretary Sean Duffy blamed legacy equipment. He said switches and routers in the FAA's network were flooded with data and began producing inconsistent information, at which point the agency shut the system down. Mullin offered a possible trigger: the FAA appeared to have been applying patches and installing new equipment and technology, which he said was overwhelming the older system.

CBS News, citing multiple sources, reported that the outage followed an update to the private communications network linking the air traffic control system. According to that report, the network rebooted and then crashed, and L3Harris operates it. SecurityWeek did not say whether L3Harris or the FAA has commented.

How this kind of failure works

Large networks fail without any attacker involved more often than many readers expect. A switch is a device that moves data between machines inside a network, and a router sends data between networks. If a change causes them to send out bad or excessive traffic, other devices can receive conflicting information and stop trusting it.

Operators often respond by shutting a system down on purpose. Running on data you cannot trust is riskier than running on no data, particularly in air traffic control, so a controlled stop is a normal safety decision.

Picture a town's road signs being replaced overnight. If the new signs are wired into an old control box that cannot cope, every junction might show a different instruction at once. The sensible response is to turn all the lights to red until the box is fixed. Nobody has to have sabotaged anything for that to happen.

Changes to old systems are risky because nobody may know every dependency. A patch that is sound on its own can interact badly with ageing hardware or with a partner's network. That is why change control, staged rollouts and tested rollback plans matter, and why investigators ask early what changed shortly before an outage.

Who is affected

Air travellers and airlines across the US were hit directly. SecurityWeek reported thousands of flights disrupted, with delays expected to last several days as schedules recover.

For ordinary passengers, the practical effect is knock-on disruption: aircraft and crews out of position, missed connections and rebooking queues. Checking flight status with your airline before travelling is the reliable way to tell whether your journey is affected.

No data exposure has been reported. Nothing in the reporting suggests passenger or FAA data was stolen, and officials say they have found no sign of hacking.

How to defend against it

Tick each step as you check it. Your progress is saved on this device.

What to learn from this

The concept: Change management as a security control

Availability, meaning systems being up when needed, is one of the three core goals of security alongside confidentiality and integrity. Outages caused by routine changes threaten it as much as attacks do, and the early response looks much the same.

Good change management means each change is reviewed, tested, scheduled, staged and reversible. It also leaves a record, which helps investigators answer the first question in any incident: what changed recently.

The same idea appears in cloud misconfigurations, faulty security-software updates and expired certificates, where an internal change rather than an outside attacker triggers the failure.

Treat every update as a possible cause of an outage, and make it staged, tested and reversible.

Quick check

Sign in to earn 10 XP for a right answer

A critical system fails shortly after a patch, and there is no sign of intruders. What is the most useful practice that would have limited the damage?

Timeline

  1. Earlier in the week of 13 November A separate Microsoft outage occurs; officials say it is unrelated to the FAA incident.
  2. 13 November 2026 The FAA issues a nationwide ground stop after a communications problem hits its air route traffic control centers.
  3. 13 November 2026, 8:15 pm ET The ground stop is lifted, more than four hours after it began.
  4. 13-14 November 2026 Mullin says there is no sign of a cyberattack; Duffy blames legacy equipment; Bloomberg and CBS News report on a software update.
  5. 14 November 2026 SecurityWeek reports that departures have resumed and delays are expected for several days.

What is not known yet

  • The official root cause has not been announced.
  • It is not confirmed that a software update to the L3Harris-operated network caused the outage; this rests on CBS News and Bloomberg reporting citing unnamed people.
  • L3Harris's response has not been reported.
  • It is not yet clear how long full schedule recovery will take.
  • Officials have not ruled out a cyberattack, though they say they have seen no evidence of one.

Questions people ask

Was the FAA ground stop caused by a cyberattack?

Officials say there is no evidence of one. Homeland Security Secretary Markwayne Mullin said the failure appeared mechanical, though he said agencies were still looking and would not rule an attack out. Bloomberg reported the FBI does not think a cyberattack or criminal activity was responsible.

How long did the FAA ground stop last?

SecurityWeek reported that the FAA lifted the order at 8:15 pm ET on 13 November, more than four hours after it began. Departures have resumed, but officials expect delays to continue for several days.

What do officials say caused the outage?

No official cause has been announced. Transportation Secretary Sean Duffy blamed legacy equipment that was flooded with data. Mullin said patches and new equipment appeared to be overwhelming the older system, and CBS News reported an update to a private network preceded the failure.

Were the FAA's AI systems or the Microsoft outage involved?

Officials said no to both, according to SecurityWeek. They said the incident had nothing to do with the Microsoft outage earlier in the week, and that the FAA's recently deployed AI systems played no role.

Sources

  • SecurityWeek: No Signs of Hacking in FAA Ground Stop as FBI Reportedly Probes Software Update

Know someone who should see this?

Keep reading