StormProof → hail seasons → Birmingham → 2005
Birmingham hail season 2005
6 NWS-recorded hail reports ≥1″ within 30 miles, across 4 storm days, max 2.00". Every one of those reports is a dated, located, citable official record — the context behind this market's 2005 claim volume.
Biggest storm days (2005, final record)
| Date | ≥1″ reports | Max hail | Areas named in the record |
|---|---|---|---|
| March 30, 2005 | 3 | 2.00" | JEFFERSON, WALKER, BLOUNT |
| December 28, 2005 | 1 | 1.00" | SHELBY |
| August 5, 2005 | 1 | 1.00" | JEFFERSON |
| March 22, 2005 | 1 | 1.50" | SHELBY |
“Penny to quarter size hail was reported across the Birmingham metro area. Some of the locations that reported large hail include Hueytown, Bessemer, Legion Field, Trussville, Birmingham Southern, Huffman. Clay, Sylvan Springs and Chalkville.”
— NWS event narrative, March 30, 2005 (NCEI Storm Events)
When it fell
Mar 4 · Aug 1 · Dec 1
Wind context: the record also holds 24 thunderstorm-wind events ≥50 kt (≈58 mph, the NWS severe criterion) in this radius for 2005 — relevant where the dispute is wind vs hail causation.
Working a Birmingham claim from 2005?
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 Birmingham 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.