StormProof → hail seasons → Miami–Fort Lauderdale → 2012
Miami–Fort Lauderdale hail season 2012
14 NWS-recorded hail reports ≥1″ within 35 miles, across 6 storm days, max 3.00". 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 |
|---|---|---|---|
| June 15, 2012 | 5 | 3.00" | MIAMI-DADE, BROWARD |
| May 9, 2012 | 3 | 1.50" | MIAMI-DADE |
| June 6, 2012 | 2 | 1.00" | MIAMI-DADE |
| May 18, 2012 | 2 | 1.25" | MIAMI-DADE |
| May 27, 2012 | 1 | 1.00" | BROWARD |
“Hail the size of baseballs to large apples reported in the Coral Gables area. Pictures of the hail were received at the NWS office with a confirmed diameter of up to 3 inches.”
— NWS event narrative, June 15, 2012 (NCEI Storm Events)
When it fell
Apr 1 · May 6 · Jun 7
Wind context: the record also holds 31 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 Miami–Fort Lauderdale 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 35 miles of the Miami–Fort Lauderdale 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.