StormProof → hail seasons → Dallas–Fort Worth → 2010
Dallas–Fort Worth hail season 2010
31 NWS-recorded hail reports ≥1″ within 45 miles, across 10 storm days, max 3.00". Every one of those reports is a dated, located, citable official record — the context behind this market's 2010 claim volume.
Biggest storm days (2010, final record)
| Date | ≥1″ reports | Max hail | Areas named in the record |
|---|---|---|---|
| March 10, 2010 | 8 | 1.50" | KAUFMAN, TARRANT, DALLAS, DENTON |
| May 20, 2010 | 7 | 1.75" | NAVARRO, ELLIS, KAUFMAN, DALLAS |
| October 24, 2010 | 6 | 3.00" | ELLIS, NAVARRO, KAUFMAN, COLLIN |
| May 17, 2010 | 3 | 1.75" | ELLIS, DALLAS |
| January 20, 2010 | 2 | 1.75" | KAUFMAN, HUNT |
“Quarter size hail fell near the intersection of Highway 380 and Interstate 35 in the city of Denton.”
— NWS event narrative, March 10, 2010 (NCEI Storm Events)
When it fell
Jan 2 · Mar 9 · Apr 1 · May 10 · Jun 1 · Jul 1 · Aug 1 · Oct 6
Wind context: the record also holds 38 thunderstorm-wind events ≥50 kt (≈58 mph, the NWS severe criterion) in this radius for 2010 — relevant where the dispute is wind vs hail causation.
Working a Dallas–Fort Worth claim from 2010?
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 45 miles of the Dallas–Fort Worth 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.