StormProof unlimited NWS storm verification · for pros

StormProofhail seasonsOklahoma City → 2009

Oklahoma City hail season 2009

77 NWS-recorded hail reports ≥1″ within 35 miles, across 16 storm days, max 3.00". Every one of those reports is a dated, located, citable official record — the context behind this market's 2009 claim volume.

Biggest storm days (2009, final record)

Date≥1″ reportsMax hailAreas named in the record
February 10, 2009152.75"GRADY, CANADIAN, OKLAHOMA, LOGAN
May 12, 2009102.00"CLEVELAND, MCCLAIN, POTTAWATOMIE, OKLAHOMA
July 16, 200983.00"CLEVELAND, OKLAHOMA
May 13, 200971.50"CLEVELAND, OKLAHOMA, LOGAN
July 18, 200961.00"OKLAHOMA, LOGAN

“The hail was reported at the intersection of Council Road and 113th Street. Up to quarter size hail covered the ground one inch deep.”

— NWS event narrative, February 10, 2009 (NCEI Storm Events)

When it fell

Feb 15 · Mar 9 · Apr 4 · May 23 · Jun 3 · Jul 19 · Aug 4

Wind context: the record also holds 36 thunderstorm-wind events ≥50 kt (≈58 mph, the NWS severe criterion) in this radius for 2009 — relevant where the dispute is wind vs hail causation.

Working a Oklahoma City claim from 2009?

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.