On November 13, 2026, the FAA ordered a nationwide ground stop on US departures. Within hours, SMART, an AI tool used for en-route airspace routing, became the focus of speculation. No official attribution has been made, and prediction markets lean heavily toward No.
🔑 Key takeaways
- A rushed nationwide ground stop on November 13, 2026, with nearly 7,000 flights delayed or cancelled according to FlightAware.
- The SMART system, tied to an $875 million 12-year contract, is at the center of speculation, with no established link.
- Officials point to a communications problem, rule nothing out, and report no sign of malicious attack.
- Polymarket prices ‘Yes’ between 2.8% and 6% depending on the page, versus roughly 2% at Lines.
A rushed ground stop and an unknown cause
The stop was ordered shortly before 1 p.m. Pacific time under ‘extraordinary circumstances.’ Transportation Secretary Sean Duffy described ‘a communications problem affecting all en route air traffic control centers.’ Aircraft already airborne were allowed to land, while inbound international flights were handled case by case. It was the second nationwide stop since September 11, following the failure of the NOTAM (Notice to Air Missions) system in January 2023.
In early statements the cause remained unknown. Citing two law enforcement officials, CNN reported that preliminary reports showed no sign of a cyberattack. The initial picture points to a communications failure rather than an intrusion, but no public conclusion has been reached.
SMART under the spotlight
SMART, short for ‘strategic management of airspace routing systems,’ is part of a 12-year contract worth $875 million signed with Boston-based Air Space Intelligence. The FAA extended it to airspace managed by its 22 en route control centers. According to GeekWire, it is a cloud-based system ingesting roughly 200 data feeds, including weather, flight trajectories and controller staffing.
SMART recommends schedules and routes, but FAA specialists review those recommendations and local facilities decide whether to apply them. In October, lawmakers had asked the FAA to suspend the tool in the Washington area. A faulty recommendation therefore does not mechanically produce a decision, but the human validation chain remains to be documented.
A disputed rollout timeline
- CNN, syndicated by Mediaite and Yahoo: launch on the same day as the national stop.
- Lines: rollout completed on November 10, 2026, three days before the incident.
- Polymarket’s automated summary: repeats the three-day hypothesis.
- GeekWire: extension announced Tuesday, with no explicit date in the quoted passage.
These discrepancies matter. A rollout three days earlier strengthens the chronological reading, while a same-day launch makes any correlation harder to establish.
Cautious experts, a government ruling nothing out
Mary Schiavo, former inspector general of the US Department of Transportation, calls the timing ‘simply too much of a coincidence.’ She notes that air traffic control has historically relied on a patchwork of systems, some dating to ‘radio, telephones and floppy disks,’ and that new software often struggles to communicate with legacy equipment. She does not, however, propose any official attribution.
“I don’t know if they are linked, but it’s simply too much of a coincidence.”
Mary Schiavo, former inspector general, US Department of Transportation
On the government side, Homeland Security Secretary Markwayne Mullin said the FAA was reviewing SMART through CISA. Asked about artificial intelligence, he corrected the terminology, saying ‘we call it SI,’ for ‘superintelligence,’ before adding: ‘we cannot rule anything out at this stage.’ Officials nonetheless cited ‘no indication of malicious attack.’ Mullin described communications still possible ‘at certain levels’ and said a return to normal would not happen within an hour.
“We are not ruling anything out for now.”
Markwayne Mullin, Secretary of Homeland Security
Polymarket: strict rules, diverging odds
The contract does not settle the technical cause of the outage, but an official attribution. It resolves ‘Yes’ if the US government explicitly attributes the incident to artificial intelligence before November 30, 2026 at 11:59 p.m. Eastern. The statement must come from an authorized federal official and assert that an AI system, model or agent itself caused the stop. Malfunctions, errors and autonomous actions qualify, including when AI is used by the FAA or a contractor. By contrast, AI described as ‘suspected,’ ‘probable’ or a contributing factor is not enough, and neither are anonymous sources, foreign governments or private companies. A qualifying attribution counts even if later retracted. The market is binary and pays 1 USDC on the winning outcome.
Polymarket’s experimental AI-generated summary, which plays no role in settlement, describes a different version: a legacy telecom failure, switch and router saturation, and reviews of software updates by homeland security and the FBI. GeekWire, however, reported that the cause was still unknown during Mullin’s briefing. The sources do not allow the timing of that shift to be pinned down.
| Source | Yes | No | Volume |
|---|---|---|---|
| CryptoSlate (Nov 14, 12:42 UTC) | 2.8% | 97.3% | $12,400 |
| Polymarket (header) | 5% | n.a. | $10,467 |
| Polymarket (FAQ) | 6% | n.a. | $10,467 |
| Lines (Nov 13) | 2% | 98% | $33,600 |
The odds converge on No, but they are not synchronized. Lines’ widget shows $34,000 in volume, 1% Yes and 98.6% No, while the text on the same page cites $6,508 in total volume. CryptoSlate and Polymarket volumes do not match either, which calls for caution in any fine-grained reading of the probabilities.
Manifold: classifying a still-unclear cause
A separate Manifold market asks a different question: will the root cause of the outage be publicly established before December 31, 2026, Pacific time? Outcomes range from a cyberattack with a material AI role, a cyberattack without an established AI role, sabotage, an AI malfunction or agent error, a software bug, a failed update, a configuration error, a hardware, power or cable failure, a natural event, to no public root cause. The initiating cause would prevail in case of multiple failures. If a cyberattack is excluded but the choice between non-malicious causes cannot be settled, the market resolves in equal shares.
The comments illustrate how hard classification is. One trader called the rules confusing and sold all positions. Another argues that installing faulty hardware may count as a software bug, citing a Financial Times report describing a gradual rollout of new equipment, with the effective failure being switch saturation. The debate over AI-written code also divides participants: it should not be automatically attributed to AI, yet code generated and deployed without validation arguably remains AI-attributable, even though human-written code can be defective too.
Outlook and scenarios
No public evidence settles the question yet. The scenario most consistent with official statements remains a communications failure on aging infrastructure, possibly compounded by interaction with a new tool. A closing investigation attributing the incident to hardware, telecoms or human error would mechanically reinforce No on both Polymarket and Manifold.
Two other scenarios bear watching. An anonymous leak could briefly lift Yes without meeting the contract’s rules. Conversely, an official statement asserting that an AI system itself caused the stop would flip the binary market outright. For now, caution is warranted: the data are partial, the dates conflict and the prices are not synchronized.
Sources
- CryptoSlate, FAA outage attributed to AI market
- Manifold Markets, root cause of the FAA outage
- Yahoo News, CNN report
- Polymarket, FAA outage attributed to AI market
- Lines, prediction market analysis
- GeekWire, Markwayne Mullin statements
Cet article est publié à titre informatif et éducatif. Il ne constitue en aucun cas un conseil en investissement. Faites vos propres recherches (DYOR) avant toute décision.
