StormProof → hail seasons → Midland–Odessa → 2004
Midland–Odessa hail season 2004
9 NWS-recorded hail reports ≥1″ within 25 miles, across 7 storm days, max 2.50". 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″ reports | Max hail | Areas named in the record |
|---|---|---|---|
| August 21, 2004 | 2 | 1.75" | MIDLAND, MARTIN |
| March 4, 2004 | 2 | 1.75" | UPTON, REAGAN |
| October 4, 2004 | 1 | 1.00" | MIDLAND |
| September 23, 2004 | 1 | 1.00" | MIDLAND |
| August 12, 2004 | 1 | 1.00" | MIDLAND |
“Convective development quickly increased north of the stalled frontal boundary. A severe thunderstorm developed in northeastern Midland County, and produced golfball size hail in Greenwood. No damage was reported.”
— NWS event narrative, August 21, 2004 (NCEI Storm Events)
When it fell
Mar 3 · Jun 1 · Aug 3 · Sep 1 · Oct 1
Wind context: the record also holds 8 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 Midland–Odessa 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 25 miles of the Midland–Odessa 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.