StormProof unlimited NWS storm verification · for pros

StormProofhail seasonsMiami–Fort Lauderdale → 2016

Miami–Fort Lauderdale hail season 2016

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

Biggest storm days (2016, final record)

Date≥1″ reportsMax hailAreas named in the record
May 24, 201641.00"MIAMI-DADE
September 30, 201611.00"BROWARD
July 8, 201611.00"BROWARD

“A trained spotter called to report quarter size hail falling at SW 107th Avenue and Bird Road. There were also many other reports of dime and pea size hail falling in the same area. Pea size hail was also reported at the local National Weather Service office in Miami located on FIU South Campus.”

— NWS event narrative, May 24, 2016 (NCEI Storm Events)

When it fell

May 4 · Jul 1 · Sep 1

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

Working a Miami–Fort Lauderdale claim from 2016?

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.