
What caused the FAA's nationwide ground stop?
K 672.4K contracts
1
6
Current odds
Snapshot from
As of Nov 22, 2026, 3:00 PM UTC, the highest-priced outcome on Kalshi is Software/config error at 80%.
Kalshi
- Software/config error80%
- Human error34.5%
- Physical damage3%
- Verizon2.5%
- SMART system2%
Yes prices. They are not order quotes; check each platform's rules, fees and live prices before trading.
AI Analysis
Trader mode: Market mechanics, assumptions and risks
K 672.4K contracts
Reported volume · provider units
6
Saved contracts
0
Same-question pairs
Source snapshot: Nov 22, 2026, 3:00 PM UTC
This analysis was written from an earlier market snapshot, so its prices may be older than the odds above.
Snapshot observed Nov 18, 2026, 12:00 AM UTC. This analysis describes that snapshot and is not a live news update.
What the contract measures
This event asks what caused the FAA's nationwide ground stop. The rules define the ground stop as "the nationwide departure ground stop the FAA ordered on Nov 13, 2026" [1]. Each market is a separate yes-or-no question about one possible cause. A market resolves to Yes only if a Source Agency confirms that cause before the stated deadline. The markets are not mutually exclusive, so more than one can resolve to Yes [1]. The rules also say that if no cause is confirmed before Dec 1, 2026, the market resolves to No [1].
Wording matters. The software market covers a fault in software or a wrong setting in an FAA or contractor system. The human error market covers a mistake by a person, such as a wrong command or procedure [1]. A report that a cause is "suspected, being investigated or has not been ruled out" does not count [1].
Reading the snapshot
The provider data was observed at Nov 18, 2026, 12:00 AM UTC and retrieved at Nov 18, 2026, 12:22 AM UTC [1]. This is a saved snapshot, not a live reading, and prices may have changed since. The six saved Kalshi markets show these Yes prices: software or configuration error 0.755, human error 0.415, accidental physical damage 0.07, and SMART system problem, AI system error, and Verizon-run system failure at 0.025 each [1]. These are snapshots, not executable quotes or verified probabilities.
Each saved market lists an end date of Dec 8, 2026, 3:00 PM UTC, while the rules reference Dec 1, 2026 for confirmation [1]. The source excerpt states that the listed end time is not supplied, so close timing should be read from the market record and not assumed from the rules. The reported volume of 528,277 contracts is Kalshi's own figure for its event. It does not measure liquidity or the number of traders [1].
What remains uncertain
All six saved markets for this event are included, but the source notes that this does not establish that the provider lists every possible outcome [1]. The rules describe other categories, including maintenance or upgrade, contractor failure, and general system failure, that do not appear in this snapshot. No price is available here for them [1]. The snapshot also does not explain why prices sit where they do, and it does not report what any agency has said. Prices should not be compared with questions on other platforms, because wording and close times may differ.
References
- Kalshi: What caused the FAA's nationwide ground stop?. Provider data observed Nov 18, 2026, 12:00 AM UTC.
Snapshot observed Nov 18, 2026, 12:00 AM UTC. This analysis describes that snapshot and is not a live news update.
What the contract measures
These markets come from one Kalshi event, "What caused the FAA's nationwide ground stop?" [1]. The underlying event is the nationwide departure ground stop the FAA ordered on Nov 13, 2026 [1]. Each contract asks whether a specific cause will be confirmed. The rules state that the cause "must be confirmed, verified, or established as factual by at least one Source Agency" [1].
The categories are defined narrowly. For example, "System failure" excludes cyberattacks, and "Software/config error" includes a fault introduced by an update or upgrade [1]. The rules also state: "This market is NOT mutually exclusive: more than one market can resolve to Yes." [1] If no cause is confirmed before Dec 1, 2026, the rules say the market resolves to No [1]. The listed end date for these contracts is Dec 8, 2026, 3:00 PM UTC [1]. That date differs from the Dec 1 confirmation language in the rules, so readers should compare the rule text with the listed close time before relying on either one.
Reading the snapshot
The provider observation time is Nov 18, 2026, 12:00 AM UTC, and the source was retrieved at Nov 18, 2026, 12:22 AM UTC [1]. These times describe this snapshot only, not live trading.
The six Kalshi contracts show these Yes prices: 0.755 for a software or configuration error, 0.415 for human error, 0.07 for accidental physical damage, and 0.025 each for a SMART system problem, an AI system error, and a Verizon-run system failure [1]. Because the categories can overlap, these prices are not shares of one probability split. They should not be summed or averaged. The sample includes all six saved markets for this event, and no Polymarket markets were supplied for it. Kalshi reports 528,277 contracts of volume for its event [1]. That figure reflects activity in Kalshi's own units. It is not a measure of liquidity or the number of traders. These prices are snapshots, not executable quotes or verified probabilities.
The source also lists L3Harris in the rules, but no L3Harris contract appears in the supplied markets, so no price is available for it [1].
What remains uncertain
The evidence shows contract wording and prices, but it does not explain why prices sit where they do. It also does not show whether any Source Agency has named a cause. The source excerpt lists the event end time as "not supplied," so the 2026-12-08 date appears only in the market data [1]. The rules also state that "This market will close and expire early if the event occurs." [1] Differences in price between contracts with different wording do not by themselves indicate an arbitrage opportunity.
References
- Kalshi: What caused the FAA's nationwide ground stop?. Provider data observed Nov 18, 2026, 12:00 AM UTC.
AI-generated analysis based on market data. Not financial advice.
Saved Nov 18, 2026 UTCThis article was written from an earlier market snapshot and may be out of date. Use the dated market data and provider rules above for current information.
Overview
This contract asks which cause, if any, will be confirmed for the nationwide departure ground stop that the FAA ordered on Nov 13, 2026 [1]. According to a Wikipedia article on the event, the FAA issued the ground stop at 20:54 UTC because of a communication outage, first issued at O'Hare International Airport and Midway International Airport in Chicago, and it was lifted at 01:15 UTC, four hours and twenty-one minutes later [2]. A ground stop is an air traffic control procedure that requires certain aircraft to remain on the ground, and it can be airport-specific or tied to equipment or airspace depending on the event that caused it [3]. The Wikipedia material is historical background about the event, not confirmation of its current status. The contract rules define a set of possible causes and require that the cause be confirmed, verified or established as factual by at least one Source Agency before Dec 1, 2026 [1]. The categories include a system failure, planned maintenance or an upgrade, accidental physical damage, a software or configuration error, a failure by a contractor or telecommunications company, a malfunction in the FAA's SMART air traffic management system, human error, and an error by an AI system that the Source Agency describes as AI [1]. A deliberate act meant to disrupt equipment, such as cyberattack, jamming or sabotage, does not count [1]. A report that a cause is suspected, being investigated or not yet ruled out also does not count [1]. If no cause is confirmed before Dec 1, 2026, the market resolves to No [1]. The rules state that the markets are not mutually exclusive, so more than one can resolve to Yes [1]. The source gives an example: a problem with the SMART rollout could count as a maintenance or upgrade issue and, if it were a software or configuration fault, as a software or configuration error [1]. The rules also say the market will close and expire early if the event occurs [1]. The saved Kalshi snapshot was observed at 2026-11-19T00:00:06Z and retrieved at 2026-11-19T00:22:37Z [1]. In that snapshot, the Yes price for a software or configuration error was 0.855, for human error 0.245, for accidental physical damage 0.065, for a SMART system problem 0.035, for an AI system error 0.025, and for a Verizon network or system failure 0.025 [1]. These figures are snapshot prices from one provider at one time. They are not executable quotes or verified probabilities, and because the outcomes are not mutually exclusive, the Yes prices do not need to add up to a fixed total. The listed end date is 2026-12-08T15:00:00Z, which differs from the Dec 1, 2026 confirmation deadline stated in the rule text [1]. The source does not explain that difference.
Historical Context
Wikipedia reports that the FAA issued a nationwide ground stop on November 13, 2026, at 20:54 UTC because of a communication outage. The ground stop was first issued at O'Hare International Airport and Midway International Airport in Chicago, and the FAA ordered all airports to immediately ground flights due to "extraordinary circumstances and for reasons of safety" [2]. The ground stop was lifted at 01:15 UTC, four hours and twenty-one minutes later [2]. The retrieved Wikipedia excerpt does not identify a confirmed cause, and it is background information rather than verification of the current status of the event.
Why It Matters
The contract measures whether a Source Agency will confirm a specific cause for the telecommunications outage behind the November 13, 2026 nationwide ground stop [1]. Its categories separate different kinds of causes, such as equipment failure, human error, contractor work, the SMART system and AI system error, so traders can see that each category is a separate question [1]. The rules state that a general suspicion or a statement that the ground stop followed a communication or radar issue is not enough, which means a confirmation must name a particular malfunction, error, damage or other event [1]. A ground stop itself can delay or cancel flights and leave aircraft and crews unable to reach their next scheduled locations [3], so the cause question concerns the operational event that prompted the procedure [1][3].
Snapshot context
The latest published provider snapshot for this topic was observed on 2026-11-19 at 00:00 UTC. It contains listings from Kalshi. Market descriptions and listed closing times define the contracts; they do not establish that the real-world outcome has occurred. This article does not include a separately verified news update. [1]
Frequently Asked Questions
Does a suspected cause count for this contract?
No. The rules say a report that a cause is suspected, being investigated or has not been ruled out does not count, and a statement that the ground stop followed a communication, radio or radar outage does not count unless it says what caused that outage [1].
What happens if no cause is confirmed before December 1, 2026?
The market resolves to No if no cause is confirmed before Dec 1, 2026 [1].
Can more than one market resolve to Yes?
Yes. The rules say this market is not mutually exclusive, so more than one market can resolve to Yes [1].
Does a deliberate attack count as a system failure?
No. The rules say a cyberattack, jamming or sabotage is not a failure, and a deliberate act meant to disrupt equipment or operations does not count [1].
AI-written background. References identify the evidence used; Wikipedia links under Learn More are additional reading. Prices and provider rules are dated snapshots. This is not financial advice.
Related prediction markets
Prices are catalog snapshots and may have changed. Check each market's rules and observation time.

What technical failure caused the FAA's nationwide ground stop?
PM $86.6K
Las Vegas Grand Prix Main Race: Fastest Pit Stop
K 5.4K contracts
How much will ACA Marketplace enrollment decline in 2027?
K 1.5K contracts
Indiana enacts data center moratorium by...?
PM $7.13M · K 40.2K contractsWill Indiana enact a data center moratorium by December 31, 2027?
Kalshi: Will any state enact data center moratorium legislation before Jan 1, 2028?
Related contracts
Will Ohio enact a data center moratorium by December 31, 2027?
Kalshi: Will any state enact data center moratorium legislation before Jan 1, 2028?
Related contracts
Will Ohio enact a data center moratorium by June 30, 2027?
Kalshi: Will any state enact data center moratorium legislation before Jul 1, 2027?
Related contracts
Related or unreviewed contracts may settle differently. Their gap is not an equivalent-contract comparison.
Saved prices; check contract rules.

Will China unban Bitcoin?
PM $1.14M · K 1.6K contractsWill China unban Bitcoin by 2027?
Kalshi: Will People's Republic of China agree to or announce a nationwide policy permitting members of the general public in mainland China to legally buy and sell Bitcoin through a government-authorized exchange, bank, broker, or other regulated trading platform before Jan 1, 2027?
Related contracts
Related or unreviewed contracts may settle differently. Their gap is not an equivalent-contract comparison.
Saved prices; check contract rules.

Will China abolish hukou?
K 7.5K contractsMarket Insights
Price gaps of 2 pp+
0
Same-question pairs
0
No outcomes on this page have been reviewed as the same question on both platforms yet.
Price differences do not establish arbitrage. Check each pair's review, current order prices, fees and settlement rules.
