StormProof → hail seasons → Topeka → 2017
Topeka hail season 2017
38 NWS-recorded hail reports ≥1″ within 25 miles, across 9 storm days, max 2.00". 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 |
|---|---|---|---|
| May 18, 2017 | 15 | 1.75" | SHAWNEE, WABAUNSEE, JACKSON, JEFFERSON |
| June 17, 2017 | 10 | 2.00" | SHAWNEE, JEFFERSON, JACKSON |
| May 31, 2017 | 5 | 1.75" | OSAGE |
| May 30, 2017 | 3 | 1.75" | OSAGE |
| October 21, 2017 | 1 | 1.50" | WABAUNSEE |
“Time was corrected via radar. Small tree limbs were also reported down.”
— NWS event narrative, May 18, 2017 (NCEI Storm Events)
When it fell
Mar 3 · May 23 · Jun 11 · Oct 1
Wind context: the record also holds 43 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 Topeka 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 25 miles of the Topeka 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.