StormProof unlimited NWS storm verification · for pros

StormProofhail seasonsOklahoma City → 2004

Oklahoma City hail season 2004

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

Biggest storm days (2004, final record)

Date≥1″ reportsMax hailAreas named in the record
April 21, 2004172.50"POTTAWATOMIE, MARSHALL, WOODWARD, SEMINOLE
June 2, 200461.75"OKLAHOMA, LOGAN, ALFALFA
May 29, 200462.75"LOGAN, CANADIAN, GRANT, KINGFISHER
April 30, 200463.00"GRADY, CANADIAN, KINGFISHER, LOGAN
August 10, 200441.75"OKLAHOMA, LOGAN, KINGFISHER

“Hail was reported on the west side of town. Penny, nickle, and quarter size hail was also observed to be covering the ground.”

— NWS event narrative, April 21, 2004 (NCEI Storm Events)

When it fell

Mar 1 · Apr 25 · May 8 · Jun 7 · Jul 2 · Aug 5 · Nov 1

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

Working a Oklahoma City claim from 2004?

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.