StormProof → hail seasons → Dallas–Fort Worth → 2003
Dallas–Fort Worth hail season 2003
84 NWS-recorded hail reports ≥1″ within 45 miles, across 19 storm days, max 4.50". 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 |
|---|---|---|---|
| April 5, 2003 | 29 | 4.50" | DALLAS, WISE, ROCKWALL, HUNT |
| May 24, 2003 | 6 | 1.75" | KAUFMAN, HUNT, COLLIN |
| April 6, 2003 | 6 | 1.75" | FANNIN, HOPKINS, COLLIN |
| August 11, 2003 | 5 | 1.75" | TARRANT, DENTON |
| July 22, 2003 | 5 | 1.75" | TARRANT, DENTON, COLLIN |
“Weather observer reported golf ball size hail. 59 aircraft were damaged and 121 flights were cancelled due to severe weather.”
— NWS event narrative, April 5, 2003 (NCEI Storm Events)
When it fell
Mar 1 · Apr 38 · May 25 · Jun 3 · Jul 10 · Aug 7
Wind context: the record also holds 56 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 Dallas–Fort Worth 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 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.