StormProof → hail seasons → Kansas City → 2016
Kansas City hail season 2016
109 NWS-recorded hail reports ≥1″ within 35 miles, across 10 storm days, max 3.00". Every one of those reports is a dated, located, citable official record — the context behind this market's 2016 claim volume.
Biggest storm days (2016, final record)
| Date | ≥1″ reports | Max hail | Areas named in the record |
|---|---|---|---|
| May 26, 2016 | 43 | 3.00" | JACKSON, JOHNSON, WYANDOTTE, LEAVENWORTH |
| April 26, 2016 | 22 | 1.75" | CASS, JOHNSON, JACKSON, LAFAYETTE |
| November 2, 2016 | 12 | 2.00" | CLAY |
| June 26, 2016 | 10 | 2.50" | JOHNSON, LAFAYETTE |
| April 27, 2016 | 9 | 2.00" | WYANDOTTE, CLAY, RAY, BUCHANAN |
“This hail occurred near I-470 and NE Bowlin Road near Lakewood. This report was gathered via social media.”
— NWS event narrative, May 26, 2016 (NCEI Storm Events)
When it fell
Apr 31 · May 47 · Jun 13 · Aug 5 · Sep 1 · Nov 12
Wind context: the record also holds 85 thunderstorm-wind events ≥50 kt (≈58 mph, the NWS severe criterion) in this radius for 2016 — relevant where the dispute is wind vs hail causation.
Working a Kansas City claim from 2016?
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.