StormProof → hail seasons → Wichita → 2016
Wichita hail season 2016
116 NWS-recorded hail reports ≥1″ within 30 miles, across 15 storm days, max 2.75". 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 |
|---|---|---|---|
| April 26, 2016 | 39 | 2.00" | SUMNER, SEDGWICK, BUTLER |
| June 15, 2016 | 23 | 2.50" | SEDGWICK, HARVEY, BUTLER |
| May 27, 2016 | 10 | 2.75" | COWLEY, BUTLER, SEDGWICK, HARVEY |
| May 26, 2016 | 9 | 2.75" | SEDGWICK, BUTLER, HARVEY |
| May 13, 2016 | 8 | 1.25" | BUTLER, SEDGWICK, HARVEY |
“The hail occurred near the S. 55th St./Broadway Intersection and was reported via Twitter. No damage was reported.”
— NWS event narrative, April 26, 2016 (NCEI Storm Events)
When it fell
Mar 3 · Apr 40 · May 39 · Jun 24 · Jul 2 · Sep 1 · Oct 7
Wind context: the record also holds 112 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 Wichita 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 30 miles of the Wichita 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.