StormProof → hail seasons → Midland–Odessa → 2018
Midland–Odessa hail season 2018
10 NWS-recorded hail reports ≥1″ within 25 miles, across 3 storm days, max 2.50". Every one of those reports is a dated, located, citable official record — the context behind this market's 2018 claim volume.
Biggest storm days (2018, final record)
| Date | ≥1″ reports | Max hail | Areas named in the record |
|---|---|---|---|
| June 3, 2018 | 8 | 2.50" | MIDLAND, MARTIN |
| July 31, 2018 | 1 | 1.75" | MIDLAND |
| March 27, 2018 | 1 | 1.00" | ANDREWS |
“A thunderstorm moved across Midland County and produced tennis ball sized hail. The National Weather Service conducted a survey in southern Midland County and found numerous dented vehicles, broken windows, and damaged siding on houses along South County Road 1226. The cost of damage is a very rough estimate.”
— NWS event narrative, June 3, 2018 (NCEI Storm Events)
When it fell
Mar 1 · Jun 8 · Jul 1
Wind context: the record also holds 8 thunderstorm-wind events ≥50 kt (≈58 mph, the NWS severe criterion) in this radius for 2018 — relevant where the dispute is wind vs hail causation.
Working a Midland–Odessa claim from 2018?
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.