StormProof → hail seasons → Midland–Odessa → 2003
Midland–Odessa hail season 2003
10 NWS-recorded hail reports ≥1″ within 25 miles, across 6 storm days, max 2.75". Every one of those reports is a dated, located, citable official record — the context behind this market's 2003 claim volume.
Biggest storm days (2003, final record)
| Date | ≥1″ reports | Max hail | Areas named in the record |
|---|---|---|---|
| October 5, 2003 | 2 | 1.75" | MIDLAND |
| September 8, 2003 | 2 | 1.00" | ANDREWS, MARTIN |
| September 7, 2003 | 2 | 2.75" | DAWSON |
| June 1, 2003 | 2 | 1.75" | MARTIN |
| July 23, 2003 | 1 | 1.75" | ECTOR |
“Large hail ranging in size from pennies to golfballs fell across the north side of Midland. The largest hail was observed in the area along Loop 250 between Midkiff and Midland Drive. No damage was reported.”
— NWS event narrative, October 5, 2003 (NCEI Storm Events)
When it fell
Apr 1 · Jun 2 · Jul 1 · Sep 4 · Oct 2
Wind context: the record also holds 20 thunderstorm-wind events ≥50 kt (≈58 mph, the NWS severe criterion) in this radius for 2003 — relevant where the dispute is wind vs hail causation.
Working a Midland–Odessa claim from 2003?
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.