StormProof unlimited NWS storm verification · for pros

StormProofhail seasonsDallas–Fort Worth → 2017

Dallas–Fort Worth hail season 2017

128 NWS-recorded hail reports ≥1″ within 45 miles, across 16 storm days, max 4.25". Every one of those reports is a dated, located, citable official record — the context behind this market's 2017 claim volume.

Biggest storm days (2017, final record)

Date≥1″ reportsMax hailAreas named in the record
March 26, 2017334.25"DENTON, COLLIN
April 21, 2017262.75"DALLAS, ROCKWALL, COLLIN, DENTON
April 10, 2017152.00"JOHNSON, TARRANT, DENTON, COLLIN
February 27, 2017141.50"JOHNSON, ELLIS, KAUFMAN, COLLIN
May 3, 201781.00"ELLIS

“A trained spotter reported quarter-sized hail near the intersection of Interstate 35 and FM 407, approximately 5 miles east of Justin, TX.”

— NWS event narrative, March 26, 2017 (NCEI Storm Events)

When it fell

Jan 3 · Feb 14 · Mar 35 · Apr 60 · May 9 · Jun 3 · Jul 4

Wind context: the record also holds 89 thunderstorm-wind events ≥50 kt (≈58 mph, the NWS severe criterion) in this radius for 2017 — relevant where the dispute is wind vs hail causation.

Working a Dallas–Fort Worth claim from 2017?

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.