StormProof → hail seasons → Lubbock → 2007
Lubbock hail season 2007
9 NWS-recorded hail reports ≥1″ within 25 miles, across 8 storm days, max 4.50". Every one of those reports is a dated, located, citable official record — the context behind this market's 2007 claim volume.
Biggest storm days (2007, final record)
| Date | ≥1″ reports | Max hail | Areas named in the record |
|---|---|---|---|
| April 17, 2007 | 2 | 1.50" | LUBBOCK |
| September 7, 2007 | 1 | 1.00" | LYNN |
| August 7, 2007 | 1 | 1.00" | LUBBOCK |
| June 19, 2007 | 1 | 1.00" | LUBBOCK |
| June 2, 2007 | 1 | 4.50" | TERRY |
“Multiple reports of hail that ranged in size from pennies to quarters were received around 12:45 CST across southwest Lubbock. The hail covered the ground and many roof-tops, and remained until it melted several hours later. No damage was reported.”
— NWS event narrative, April 17, 2007 (NCEI Storm Events)
When it fell
Mar 1 · Apr 2 · May 2 · Jun 2 · Aug 1 · Sep 1
Wind context: the record also holds 15 thunderstorm-wind events ≥50 kt (≈58 mph, the NWS severe criterion) in this radius for 2007 — relevant where the dispute is wind vs hail causation.
Working a Lubbock claim from 2007?
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 Lubbock 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.