StormProof unlimited NWS storm verification · for pros

StormProofhail seasonsDayton → 2000

Dayton hail season 2000

9 NWS-recorded hail reports ≥1″ within 25 miles, across 7 storm days, max 1.75". Every one of those reports is a dated, located, citable official record — the context behind this market's 2000 claim volume.

Biggest storm days (2000, final record)

Date≥1″ reportsMax hailAreas named in the record
June 2, 200021.50"WARREN, GREENE
May 10, 200021.00"MONTGOMERY, MIAMI
July 28, 200011.00"CLARK
July 14, 200011.75"CLARK
June 14, 200011.00"MONTGOMERY

When it fell

May 4 · Jun 3 · Jul 2

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

Working a Dayton claim from 2000?

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 Dayton 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.