← Back to scans

Major meteor strike (10kt+) in 2026?

0xeb85e2b50d4d691325f8e906fff3ab156ad7d2b4086d7b5c19108d601969c628 · Climate and Weather · 2026-08-30
9%
Agent
15%
Market Price
-6.0%
Edge
67%
Confidence
Volume: 201,968
Spread: 2.0c
Days to resolution: 123
Markets in event: 1
Final Rationale
Both forecasters correctly time-condition the Poisson base rate: with no ≥10kt event through ~August, only ~4 months of exposure remain, giving a memoryless forward probability of roughly 4-6% (1−e^(−λ/3) at λ=0.11–0.19). The critique's strongest point is the unexplained 2x gap to the rising Polymarket anchor (14.5%), which may reflect informed positioning on classified-sensor reporting lag or an unverified proxy — this warrants slightly more weight to Yes than the 7-8% consensus, but not full anchor adoption since the market plausibly hasn't fully time-decayed and full-year base rates cap at ~17% pre-conditioning. The AMS attribution of the Q1 fireball uptick to detection changes, and all 2026 events being an order of magnitude below threshold, support No. I set Yes at 9%, modestly above consensus to account for the anchor gap, contested historical count (N=4-7), and late-report optionality.
Price vs. prediction
How the market moved after the agent's call. Solid blue line is the actual market price; dashed line is the agent's static forecast at $t{=}0$.
$n = 3$ follow-ups
Re-scan Context
This market has been scanned before. Previous predictions:
DatePredictedMarket PriceConfidence
2026-08-23 12% 15% 65%
1. Planner Opus · Fermi decomposition + tool plan
Tools chosen: polymarket_direct claude_news code_execution kalshi_related polymarket_related gdelt_news wikipedia
Sub-questions (Fermi decomposition)
  1. How many natural bolide events with Impact Energy ≥ 10 kt have been recorded in the NASA JPL CNEOS fireball database since ~1988, and what is the implied annual rate?
  2. Has any bolide event ≥ 10 kt already occurred or been reported between January 1, 2026 and now?
  3. What is the current Polymarket YES price and volume for this market, and how has it trended?
  4. Given a historical Poisson rate of ≥10 kt events per year, what is the probability of at least one such event in a calendar year?
  5. Are there any known detection/reporting lags or coverage gaps in the CNEOS database (e.g., DoD sensor data release delays) that could affect resolution by Feb 28, 2027?
  6. Do related markets on Kalshi or Polymarket (e.g., asteroid/meteor impact markets) price similar events, and do they agree?
Planner reasoning
This is primarily a base-rate question: how often do natural bolides with ≥10 kt impact energy occur, per the CNEOS fireball database? A superforecaster would anchor on the historical Poisson rate of such events (~a handful in the last 35 years of monitoring), check whether any qualifying event has already occurred in 2026, and compare against the market price. Cross-market prices and news of recent large fireballs round out the plan.
2. Research Parallel tool calls
ToolStatusTimeItemsSummary
polymarket_direct OK 0.5s 1 ## This Market's Polymarket Data **Major meteor strike (10kt+) in 2026?** - Current price (probability): 14.50% - 7-day price change: +3.00% - 30-day price change: +3.00% - Total volume: $201,968 (USD notional) - Price range: 8.50% - 14.50% - Data points: 90 days
claude_news OK 27.7s 11 Based on the research, here are the key findings: - **Historical CNEOS base rate context**: The oldest event in the catalog dates back to April 15th, 1988, and in total CNEOS includes 954 fireballs (as of May 2023) — of which only a small fraction reach the 10kt+ threshold (Chelyabinsk ~440kt in
code_execution OK 10.5s 0 **Poisson Base Rate Calculation: Major Meteor Strike (≥10 kt) in 2026** - **Observation window:** ~37 years (CNEOS fireball database, 1988–present) - **Event count scenarios (N):** 4, 5, 6, or 7 qualifying events ≥10 kt (Chelyabinsk 2013 ~440 kt, Bering Sea 2018 ~173 kt, Sulawesi 2009 ~33 kt, Marsh
kalshi_related OK 1.8s 0 0 related markets / summaries. keyword 'meteor': no matches | keyword 'asteroid': no matches | keyword 'bolide': no matches
polymarket_related OK 0.2s 0 Scanned 100 active Polymarket markets, kept 0 matches. keyword 'meteor': 0 markets | keyword 'asteroid impact': 0 markets | keyword 'bolide': 0 markets
gdelt_news OK 55.8s 10 GDELT: 10 articles across 2 queries (lookback=60d). 'large fireball bolide 2026': error HTTPSConnectionPool(host='api.gdeltproject.org', port=443): Max retries exceeded with url: /api/v2/doc/doc?query=%28large+OR+fireball+OR+bolide+OR+2026%29+sourcelang%3Aenglish&mode=ArtList&format=json&startdateti
wikipedia OK 0.1s 3 Fetched 3 Wikipedia entries (0 missing pages).
3. Evidence Brief Sonnet · 6619 chars
# Current state No natural bolide ≥10 kt has been confirmed in 2026 through the latest available reporting (~Aug 2026). Multiple sub-kiloton to low-kiloton fireballs have been documented (Koblenz, Ohio, Boston), and CNEOS/AMS have noted an unusual *increase in fireball detections* in Q1 2026, but analysts explicitly state this reflects detection sensitivity, not larger events. Resolution requires CNEOS "Impact Energy (kt)" ≥10, so the question remains open and unresolved pending any late-2026 event. # Timeline of key events - 1988: CNEOS fireball database begins recording (954 total fireballs cataloged by May 2023) [claude_news/A&A]. - 2013-02-15: Chelyabinsk superbolide, ~440–500 kt — largest atmospheric event since Tunguska (confirmed) [Wikipedia]. - 2018-12: Bering Sea bolide, ~173 kt (confirmed) [code_execution/claude_news]. - 2020-12: China bolide, ~9.5 kt — largest over-land event since Chelyabinsk, notably just under the 10 kt threshold (confirmed) [Wikipedia/claude_news]. - 2026 Q1: American Meteor Society flags anomalous rise in fireball reports (2,322 total events, 40 with 50+ witness reports, 16 with 100+) — attributed to detection/reporting shifts, not larger objects (reported) [amsmeteors.org]. - 2026-03 (~26th): NASA "Fireball Season" blog addresses public questions amid Q1 activity (confirmed) [nasa.gov]. - 2026-03: Koblenz, Germany meteor — few-meter object, airburst ~50km altitude, meteorite fragments recovered; no kt figure published, but scale suggests well under 10kt (reported) [Wikipedia: 2026 Koblenz meteor]. - 2026-03: Valley City, Ohio fireball — ~6ft/7-ton asteroid, fragmented, meteorites recovered; small, sub-kiloton scale (confirmed) [claude_news/NASA]. - 2026-04-01: "Polar Interstellar Meteor" claim by Avi Loeb — speculative/unverified interstellar classification (rumored) [avi-loeb.medium.com]. - 2026-05-30: Boston fireball, ~1.1 kt (~7% of Hiroshima yield) (reported) [claude_news]. - 2026-07/08: Seasonal meteor shower coverage (Perseids, Delta Aquariids) — no bolide/impact energy events reported (confirmed, non-events) [gdelt_news]. - Through Aug 2026: No IAWN/ESA/DoD-confirmed ≥10 kt event reported anywhere (reported absence). # Event Will a natural meteoroid/bolide airburst with impact energy ≥10 kilotons TNT-equivalent occur and be recorded (CNEOS or consensus sources) between Jan 1–Dec 31, 2026? # Outcomes to forecast - Yes - No # Kalshi market anchor No kalshi_direct data was returned for this ticker (kalshi_related search found 0 matches for "meteor"/"asteroid"/"bolide"). **Best available cross-platform anchor is Polymarket**: current YES price **14.5%**, up +3pp over both 7-day and 30-day windows, trading range 8.5%–14.5% over 90 days, total volume ~$202K. Treat this as a proxy consensus in the absence of direct Kalshi pricing. # Sub-question answers 1. **Historical count/rate since 1988** — CNEOS has cataloged 954 fireballs (as of 2023); analysts estimate only ~4–7 events have reached ≥10 kt in ~37 years (Chelyabinsk ~440kt, Bering Sea ~173kt, Sulawesi ~33kt, Marshall Islands ~30-40kt, Antarctica ~13kt, plus 1-2 borderline cases), implying λ ≈ 0.11–0.19/year [code_execution]. 2. **Any ≥10kt event in 2026 so far** — No. Largest documented 2026 events (Boston ~1.1kt, Ohio, Koblenz) are all sub-kiloton to low-single-digit kt; no CNEOS, IAWN, ESA, or DoD report of a ≥10kt event found [claude_news]. 3. **Polymarket price/trend** — 14.5% YES, +3% over both 7d/30d, volume ~$202K [polymarket_direct]. 4. **Poisson probability given historical rate** — P(≥1 event in 2026) = 1−e^(−λ) ranges 10.3%–17.2% depending on N=4–7 assumption; central estimate ~12–15% [code_execution]. 5. **Detection/reporting lag risk** — Yes: CNEOS data derive from classified US Government sensors and are revised/updated after initial release; a late-2026 event could be delayed beyond the Jan 1, 2027 close or require the Feb 28, 2027 fallback consensus-source clause [claude_news]. 6. **Related markets agreement** — No Kalshi or Polymarket related markets found via keyword search (0 matches each), though claude_news notes sibling Polymarket markets exist for 5kt/100kt/1Mt thresholds using the same CNEOS source, confirming this is a recognized market family, but no cross-validation data was retrieved. # Key facts (high-confidence, factual) 1. [Wikipedia] Chelyabinsk (2013, ~440-500kt) and Bering Sea (2018, ~173kt) are the two largest CNEOS-catalogued events since 1988. 2. [Wikipedia] 2020 China bolide (~9.5kt) is the closest recent near-miss to the 10kt threshold, illustrating rarity even near-threshold. 3. [claude_news/NASA] All confirmed 2026 fireballs to date (Koblenz, Ohio, Boston) are well below 10kt. 4. [amsmeteors.org] Q1 2026 fireball report volume rose anomalously, but AMS attributes this to detection, not larger impactor sizes. 5. [code_execution] Base rate analysis yields λ≈0.11–0.19/yr, translating to ~10-17% annual probability of ≥1 qualifying event. # Cross-market signals - Kalshi related: no matching markets found. - Polymarket: 14.5% YES (same event, likely the reference market), rising trend (+3pp/7d, +3pp/30d), moderate volume (~$202K). - Sportsbook implied: N/A (not applicable to this event type). # Analyst opinions and speculation - AMS: rise in fireball detections is a sensor/reporting artifact, not evidence of increased large-impact risk. - Avi Loeb's "Polar Interstellar Meteor" claim (Apr 2026) is speculative and unrelated to size/kt threshold — not corroborated elsewhere. - No credible analyst source forecasts a 2026 ≥10kt event as imminent or overdue beyond generic base-rate reasoning. # Directional lean per outcome - **Yes**: Supported only by generic base-rate math (10-17%/yr) and Q1 2026 uptick in fireball reports (weak/indirect); no direct 2026 evidence. - **No**: Supported by absence of any confirmed ≥10kt 2026 event through Aug 2026, historical rarity (single-digit events in 37 years), and Polymarket pricing YES at only 14.5%. # Gaps / unknowns - No direct Kalshi YES price retrieved (data gap) — Polymarket used as proxy. - Exact historical count of ≥10kt events is contested (N=4-7), producing meaningful probability spread. - Coverage for Sep-Dec 2026 not available in this research; a late-year event could still occur. - Reporting/classification lag risk near year-end could affect timely resolution (fallback clause invoked if needed). # Calibration anchors - Polymarket YES price (proxy anchor): 14.5%, rising. - Poisson base-rate model: ~10-17% (central ~12-15%). - Historical frequency: ~1 qualifying event per 6-9 years on average (4-7 events in 37 years).
4. Forecasters Opus + GPT · in parallel
claude-fable-5
0.62
Yes 8%
No 92%
No ≥10kt bolide has been recorded through ~Aug 2026, meaning only ~4 months of exposure remain. The historical base rate (λ≈0.11–0.19/yr, ~4–7 events in 37 years) implies roughly 4–6% probability for the remaining Sep–Dec window; the largest 2026 event so far (Boston, ~1.1kt) is an order of magnitude below threshold, and the Q1 fireball uptick is a detection artifact per AMS. The Polymarket proxy at 14.5% YES appears stale relative to elapsed time or is pricing reporting-lag optionality, so I discount it toward the time-adjusted Poisson estimate while allowing some premium for late-reported classified-sensor events. Net: modest but nonzero Yes probability of ~8%.
gpt-5.6-sol
0.72
Yes 7%
No 93%
The historical rate of 0.11–0.19 qualifying events per year supports a 10–17% full-year YES probability, broadly consistent with the 14.5% Polymarket proxy anchor. However, no ≥10 kt event has been confirmed through roughly August, so conditioning that Poisson rate on only four months remaining lowers the forward occurrence probability to about 4–6%. The reported increase in fireballs does not raise the size-adjusted risk because AMS attributes it to detection and reporting changes, while all identified 2026 events were far below the threshold. I assign a modest additional allowance for reporting lag or an already-occurring but unpublished event, producing a 7% YES forecast.
5. Devil's Advocate Sonnet · red-team critique
1. Both forecasters converge to nearly identical point estimates (7–8%) despite the brief's own base-rate model spanning 10.3%–17.2% pre-time-adjustment (driven by contested N=4–7 historical count); collapsing this range without acknowledging the width understates tail uncertainty in a genuinely rare-event process. 2. Neither forecaster grapples seriously with the ~2x gap between their own estimate and the Polymarket anchor (14.5%, rising +3pp/7d and +3pp/30d) — both simply label it "stale" or "pricing reporting-lag optionality" without evidence; a persistently rising price on real volume ($202K) plausibly reflects informed positioning (e.g., anticipation of AMS Q1 anomaly resolving into something material, or awareness of the classified-sensor lag issue) that deserves more weight than a dismissive discount. 3. The brief flags a structural resolution risk: "a late-2026 event could be delayed beyond the Jan 1, 2027 close or require the Feb 28, 2027 fallback consensus-source clause." Both forecasters treat this only as a small upward adjustment to YES, but it could equally cut the other way — a real ≥10kt event occurring in Dec 2026 might not be confirmed/published by close, meaning the market could resolve No even if a qualifying event physically happened, which neither analysis models explicitly. 4. Both treat AMS's "detection sensitivity, not larger objects" conclusion as fully dispositive, but improved sensor coverage could in principle also raise the probability of catching an actual large event that would have gone undercatalogued in earlier decades (i.e., λ estimated from a shorter/less-sensitive historical record may be a downward-biased base rate for the current detection regime) — this counterargument is absent from both rationales. 5. Neither forecaster flags the acknowledged data gap that no direct Kalshi price was retrieved and Polymarket is only a proxy for "the same event" (unverified); given this, both should express wider uncertainty bands rather than converging to single-point 7–8% estimates with stated high confidence (0.62–0.72). 6. The Poisson time-conditioning (linear pro-rating vs. exponential memorylessness) gives similar numbers but is applied inconsistently in exposition — both frame it as "no event yet, so lower remaining-year risk," which could mislead readers into thinking a homogeneous Poisson process exhibits path-dependence, when the correct memoryless calculation should be stated explicitly rather than approximated by "4 of 12 months remain."
6. Aggregator Opus · final calibrated forecast
9% (67% confidence)
Yes: 9% No: 91%
Both forecasters correctly time-condition the Poisson base rate: with no ≥10kt event through ~August, only ~4 months of exposure remain, giving a memoryless forward probability of roughly 4-6% (1−e^(−λ/3) at λ=0.11–0.19). The critique's strongest point is the unexplained 2x gap to the rising Polymarket anchor (14.5%), which may reflect informed positioning on classified-sensor reporting lag or an unverified proxy — this warrants slightly more weight to Yes than the 7-8% consensus, but not full anchor adoption since the market plausibly hasn't fully time-decayed and full-year base rates cap at ~17% pre-conditioning. The AMS attribution of the Q1 fireball uptick to detection changes, and all 2026 events being an order of magnitude below threshold, support No. I set Yes at 9%, modestly above consensus to account for the anchor gap, contested historical count (N=4-7), and late-report optionality.
Pipeline Timing
Total pipeline time: 169.4s
Per-tool research timings shown in the Research section above.