StormProof unlimited NWS storm verification · for pros

StormProofhail seasonsColumbus (OH) → 2006

Columbus (OH) hail season 2006

12 NWS-recorded hail reports ≥1″ within 30 miles, across 6 storm days, max 2.00". Every one of those reports is a dated, located, citable official record — the context behind this market's 2006 claim volume.

Biggest storm days (2006, final record)

Date≥1″ reportsMax hailAreas named in the record
October 4, 200652.00"LICKING, FRANKLIN
June 22, 200622.00"HIGHLAND, DARKE
April 12, 200621.00"LICKING, DELAWARE
October 11, 200611.25"FRANKLIN
July 3, 200611.00"HOCKING

“Large hail to golf ball size fell for an extended period of time across the far western portion of the county, causing widespread significant damage. Thirty to forty mobile homes and numerous vehicles were severely damaged. A few subdivisions in the Pataskala area had homes that sustained extensive roof and siding damage.”

— NWS event narrative, October 4, 2006 (NCEI Storm Events)

When it fell

Apr 3 · Jun 2 · Jul 1 · Oct 6

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

Working a Columbus (OH) claim from 2006?

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 30 miles of the Columbus (OH) 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.