StormProof → hail seasons → Kansas City → 2000
Kansas City hail season 2000
33 NWS-recorded hail reports ≥1″ within 35 miles, across 9 storm days, max 2.75". Every one of those reports is a dated, located, citable official record — the context behind this market's 2000 claim volume.
Biggest storm days (2000, final record)
| Date | ≥1″ reports | Max hail | Areas named in the record |
|---|---|---|---|
| May 26, 2000 | 8 | 2.75" | CASS, JOHNSON, LEAVENWORTH, WYANDOTTE |
| September 11, 2000 | 6 | 1.75" | DOUGLAS, JOHNSON, LEAVENWORTH, CLAY |
| May 21, 2000 | 5 | 1.75" | JACKSON, CASS, JOHNSON, WYANDOTTE |
| March 26, 2000 | 4 | 1.75" | JOHNSON, JACKSON, WYANDOTTE |
| May 11, 2000 | 3 | 1.25" | LEAVENWORTH, BUCHANAN, CLINTON |
“Flat hail up to 2.5 inches in diameter fell at the NWS office in Pleasant Hill.”
— NWS event narrative, May 26, 2000 (NCEI Storm Events)
When it fell
Mar 4 · Apr 3 · May 16 · Jun 3 · Sep 7
Wind context: the record also holds 120 thunderstorm-wind events ≥50 kt (≈58 mph, the NWS severe criterion) in this radius for 2000 — relevant where the dispute is wind vs hail causation.
Working a Kansas City claim from 2000?
These are aggregates. A claim file needs the per-address record: every recorded event within 1, 3 and 10 miles of the property, distances, official narratives, and citations an adjuster can check line by line. That's the report — generated in seconds, hosted on HailEvidence (the neutral evidence surface), formatted as an insurance-appeal attachment.
Unlimited reports — Pro $99/mo Single report $29
Provenance
Final counts: NCEI Storm Events Database, file vintage c20260527, hail events with recorded magnitude ≥1.00″ and point coordinates within 35 miles of the Kansas City anchor. NWS records are point and path observations. The absence of a nearby report does NOT prove that no hail fell at this address — it means no observation was logged nearby. A report of nearby hail documents the event; it does not by itself prove damage to a specific structure. Spotted an error? Email the address on our terms page and we correct against the source.