StormProof → hail seasons → Greensboro–Winston-Salem → 2012
Greensboro–Winston-Salem hail season 2012
16 NWS-recorded hail reports ≥1″ within 30 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 2012 claim volume.
Biggest storm days (2012, final record)
| Date | ≥1″ reports | Max hail | Areas named in the record |
|---|---|---|---|
| March 24, 2012 | 7 | 1.25" | GUILFORD, DAVIDSON, ALAMANCE, CASWELL |
| July 23, 2012 | 3 | 1.25" | ALAMANCE |
| June 1, 2012 | 2 | 1.75" | GUILFORD |
| July 21, 2012 | 1 | 1.00" | RANDOLPH |
| July 1, 2012 | 1 | 1.00" | ROCKINGHAM |
“Quarter sized hail was reported along a swath from a couple of miles southwest of Swepsonville to couple of miles southeast of Haw River.”
— NWS event narrative, March 24, 2012 (NCEI Storm Events)
When it fell
Mar 8 · May 1 · Jun 2 · Jul 5
Wind context: the record also holds 102 thunderstorm-wind events ≥50 kt (≈58 mph, the NWS severe criterion) in this radius for 2012 — relevant where the dispute is wind vs hail causation.
Working a Greensboro–Winston-Salem claim from 2012?
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 Greensboro–Winston-Salem 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.