StormProof → hail seasons → Wichita → 2014
Wichita hail season 2014
50 NWS-recorded hail reports ≥1″ within 30 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 2014 claim volume.
Biggest storm days (2014, final record)
| Date | ≥1″ reports | Max hail | Areas named in the record |
|---|---|---|---|
| April 2, 2014 | 16 | 2.00" | SUMNER, SEDGWICK, BUTLER |
| May 10, 2014 | 10 | 1.75" | COWLEY, SEDGWICK, BUTLER |
| April 13, 2014 | 8 | 1.50" | SEDGWICK, HARVEY |
| June 5, 2014 | 7 | 2.75" | SEDGWICK, BUTLER |
| October 2, 2014 | 2 | 1.25" | SEDGWICK |
“Hail up to 2 inches in diameter pounded the parking lots of the Kansas Star Casino near Mulvane. Numerous car windshields were busted, with damage to the roof of the casino.”
— NWS event narrative, April 2, 2014 (NCEI Storm Events)
When it fell
Apr 24 · May 14 · Jun 9 · Sep 1 · Oct 2
Wind context: the record also holds 26 thunderstorm-wind events ≥50 kt (≈58 mph, the NWS severe criterion) in this radius for 2014 — relevant where the dispute is wind vs hail causation.
Working a Wichita claim from 2014?
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.