StormProof → hail seasons → Kansas City → 2017
Kansas City hail season 2017
88 NWS-recorded hail reports ≥1″ within 35 miles, across 12 storm days, max 2.85". Every one of those reports is a dated, located, citable official record — the context behind this market's 2017 claim volume.
Biggest storm days (2017, final record)
| Date | ≥1″ reports | Max hail | Areas named in the record |
|---|---|---|---|
| March 6, 2017 | 31 | 2.75" | DOUGLAS, JOHNSON, JACKSON, LEAVENWORTH |
| May 18, 2017 | 19 | 2.85" | JOHNSON, WYANDOTTE, PLATTE, CLAY |
| February 28, 2017 | 14 | 2.50" | CASS, JACKSON, JOHNSON, LAFAYETTE |
| June 15, 2017 | 7 | 1.50" | LEAVENWORTH, CLAY |
| June 29, 2017 | 4 | 1.00" | CLAY, PLATTE |
“Half dollar sized hail was reported at 50th St and Stateline Road in Jackson County Missouri.”
— NWS event narrative, March 6, 2017 (NCEI Storm Events)
When it fell
Feb 14 · Mar 35 · May 23 · Jun 11 · Jul 1 · Aug 4
Wind context: the record also holds 172 thunderstorm-wind events ≥50 kt (≈58 mph, the NWS severe criterion) in this radius for 2017 — relevant where the dispute is wind vs hail causation.
Working a Kansas City claim from 2017?
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.