StormProof → hail seasons → Oklahoma City → 2011
Oklahoma City hail season 2011
90 NWS-recorded hail reports ≥1″ within 35 miles, across 14 storm days, max 4.00". Every one of those reports is a dated, located, citable official record — the context behind this market's 2011 claim volume.
Biggest storm days (2011, final record)
| Date | ≥1″ reports | Max hail | Areas named in the record |
|---|---|---|---|
| May 23, 2011 | 17 | 3.00" | OKLAHOMA, CANADIAN, KINGFISHER |
| June 14, 2011 | 16 | 2.75" | GRADY, MCCLAIN, CLEVELAND, OKLAHOMA |
| May 24, 2011 | 15 | 2.75" | MCCLAIN, CLEVELAND, OKLAHOMA |
| October 22, 2011 | 12 | 4.00" | MCCLAIN, CLEVELAND, GRADY, CANADIAN |
| April 24, 2011 | 10 | 1.75" | MCCLAIN, CLEVELAND, LINCOLN, LOGAN |
“The hail was reported near Exit 136 on Interstate 35, near the Turner Turnpike.”
— NWS event narrative, May 23, 2011 (NCEI Storm Events)
When it fell
Apr 17 · May 33 · Jun 17 · Jul 1 · Aug 9 · Oct 12 · Nov 1
Wind context: the record also holds 66 thunderstorm-wind events ≥50 kt (≈58 mph, the NWS severe criterion) in this radius for 2011 — relevant where the dispute is wind vs hail causation.
Working a Oklahoma City claim from 2011?
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 Oklahoma 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.