StormProof → hail seasons → Omaha → 2016
Omaha hail season 2016
31 NWS-recorded hail reports ≥1″ within 30 miles, across 11 storm days, max 1.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 |
|---|---|---|---|
| June 29, 2016 | 11 | 1.75" | CASS, SARPY, DOUGLAS, POTTAWATTAMIE |
| April 27, 2016 | 6 | 1.75" | CASS, DOUGLAS, WASHINGTON |
| September 15, 2016 | 4 | 1.75" | DOUGLAS, WASHINGTON |
| May 30, 2016 | 2 | 1.00" | SARPY |
| April 24, 2016 | 2 | 1.25" | SAUNDERS, DODGE |
“Numerous reports from social media, spotters and media reported hail of quarter to half dollar size in Springfield that lasted for over 10 minutes.”
— NWS event narrative, June 29, 2016 (NCEI Storm Events)
When it fell
Mar 1 · Apr 8 · May 3 · Jun 13 · Aug 1 · Sep 4 · Oct 1
Wind context: the record also holds 20 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 Omaha 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 Omaha 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.