StormProof → hail seasons → Charleston (SC) → 2009
Charleston (SC) hail season 2009
17 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 2009 claim volume.
Biggest storm days (2009, final record)
| Date | ≥1″ reports | Max hail | Areas named in the record |
|---|---|---|---|
| May 4, 2009 | 8 | 1.75" | DORCHESTER, BERKELEY |
| April 20, 2009 | 3 | 1.00" | CHARLESTON |
| August 4, 2009 | 2 | 1.00" | DORCHESTER, CHARLESTON |
| June 11, 2009 | 1 | 1.00" | CHARLESTON |
| June 10, 2009 | 1 | 1.00" | BERKELEY |
“A trained weather spotter reported hail up to golf ball size along Cypress Gardens Road near Highway 52, three miles east-northeast of Carnes Crossroad, South Carolina.”
— NWS event narrative, May 4, 2009 (NCEI Storm Events)
When it fell
Mar 1 · Apr 3 · May 9 · Jun 2 · Aug 2
Wind context: the record also holds 46 thunderstorm-wind events ≥50 kt (≈58 mph, the NWS severe criterion) in this radius for 2009 — relevant where the dispute is wind vs hail causation.
Working a Charleston (SC) claim from 2009?
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 Charleston (SC) 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.