StormProof → hail seasons → Dayton → 2016
Dayton hail season 2016
5 NWS-recorded hail reports ≥1″ within 25 miles, across 3 storm days, max 1.00". Every one of those reports is a dated, located, citable official record — the context behind this market's 2016 claim volume.
Biggest storm days (2016, final record)
| Date | ≥1″ reports | Max hail | Areas named in the record |
|---|---|---|---|
| April 28, 2016 | 3 | 1.00" | GREENE |
| July 13, 2016 | 1 | 1.00" | PREBLE |
| April 26, 2016 | 1 | 1.00" | GREENE |
When it fell
Apr 4 · Jul 1
Wind context: the record also holds 55 thunderstorm-wind events ≥50 kt (≈58 mph, the NWS severe criterion) in this radius for 2016 — relevant where the dispute is wind vs hail causation.
Working a Dayton claim from 2016?
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.