Skip to main content
MANIFOLD
What caused the FAA's nationwide ground stop on November 13, 2026?
54
Ṁ3.5kṀ14k
Jan 1
11%
Cyberattack in which AI materially enabled or carried out the attack
5%
Cyberattack with no AI role established
0.4%
Physical sabotage or physical attack (deliberate, not cyber)
3%
AI system malfunction or AI agent error (no attacker)
62%
Software bug, failed update, configuration or operator error (no attacker, no AI)
7%
Hardware, power or cable failure, or accidental physical damage
0.2%
Natural event (space weather, storm, earthquake)
11%
Other established cause
1.2%
No root cause publicly established by Dec 31, 2026

On Friday, November 13, 2026, the FAA ordered a ground stop for all US airports, citing "extraordinary circumstances". Transportation Secretary Sean Duffy attributed it to "a communication issue impacting all Air Route Traffic Control Centers". When this market opened, officials had given no root cause, and CNN cited two law enforcement officials saying preliminary reports indicated it was not a cyberattack.

Resolution

Resolves to the one answer that best describes the root cause of the communications failure behind the ground stop, as publicly established by December 31, 2026 (Pacific time).

What counts as established: statements or reports from the FAA, DOT, DHS or CISA, the FBI, the NTSB, the White House or the DOT inspector general, or reporting by a major outlet (Reuters, AP, New York Times, Wall Street Journal, Washington Post, Bloomberg or similar) that investigators reached a finding. Speculation, early anonymous impressions and claims of responsibility do not count on their own. If official statements and reporting on investigators' findings conflict, I will go with the better-supported account.

If several things went wrong, the answer is the initiating cause. A cyberattack that knocked out equipment resolves as a cyberattack. A bad software update at a telecom contractor resolves as a software bug.

Answers

  • Cyberattack in which AI materially enabled or carried out the attack. Malicious cyber activity where officials or investigators find that AI did substantial work in the attack, for example finding or exploiting the vulnerability, writing the malware, or running the intrusion autonomously.

  • Cyberattack with no AI role established. Any other malicious cyber activity, including by a malicious insider. This is also the answer when a cyberattack is established and AI involvement is only speculated.

  • Physical sabotage or physical attack. Deliberate damage or interference that is not cyber: cut cables, arson, radio jamming.

  • AI system malfunction or AI agent error (no attacker). For example an AI traffic-management tool misbehaving, or an AI agent making a bad change to production systems. This takes precedence over the software answer.

  • Software bug, failed update, configuration or operator error. Non-malicious, at the FAA or a contractor, with no AI system at fault.

  • Hardware, power or cable failure, or accidental physical damage. Failed equipment, power loss, an accidental fiber cut, a fire.

  • Natural event. Space weather, severe weather, an earthquake.

  • Other established cause. A cause that meets the evidence bar and fits none of the above.

  • No root cause publicly established by Dec 31, 2026. Nothing meets the evidence bar, including when officials say only "technical issue" or "communication issue" without saying what caused it.

If officials rule out an attack but do not say enough to choose between the non-attack answers, I will split the resolution evenly among the non-attack answers that fit their account.

I may resolve before the close date if a final official finding is published and nothing credible disputes it for two weeks.

Related markets: confirmed as an AI hack by Nov 16?, result of a cyberattack?, how long will it last?

Get
Ṁ1,000
to start trading!
Sort by:

I don't see a bucket that covers "AI involved, no attack"

My personal prediction is AI assisted redteaming found something very critical, they've shut it down to fix, ahead of any actual attack.

@robm I would count intentional shut downs like this under "other established cause"