StormProof → hail seasons → Tampa–St. Petersburg → 2003
Tampa–St. Petersburg hail season 2003
12 NWS-recorded hail reports ≥1″ within 30 miles, across 8 storm days, max 2.00". Every one of those reports is a dated, located, citable official record — the context behind this market's 2003 claim volume.
Biggest storm days (2003, final record)
| Date | ≥1″ reports | Max hail | Areas named in the record |
|---|---|---|---|
| March 27, 2003 | 4 | 1.75" | HILLSBOROUGH, PASCO |
| August 1, 2003 | 2 | 1.00" | HILLSBOROUGH |
| July 30, 2003 | 1 | 1.00" | HILLSBOROUGH |
| July 18, 2003 | 1 | 1.00" | HILLSBOROUGH |
| June 16, 2003 | 1 | 1.00" | HILLSBOROUGH |
“Cars were dinged at and near a strip mall while moderate winds (less than 50 knots) downed a tree onto a car and downed a power line that cut off power to 1,375 homes.”
— NWS event narrative, March 27, 2003 (NCEI Storm Events)
When it fell
Mar 4 · Apr 1 · May 2 · Jun 1 · Jul 2 · Aug 2
Wind context: the record also holds 26 thunderstorm-wind events ≥50 kt (≈58 mph, the NWS severe criterion) in this radius for 2003 — relevant where the dispute is wind vs hail causation.
Working a Tampa–St. Petersburg claim from 2003?
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 Tampa–St. Petersburg 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.