StormProof → hail seasons → Phoenix → 2010
Phoenix hail season 2010
3 NWS-recorded hail reports ≥1″ within 35 miles, across 1 storm days, max 3.00". Every one of those reports is a dated, located, citable official record — the context behind this market's 2010 claim volume.
Biggest storm days (2010, final record)
| Date | ≥1″ reports | Max hail | Areas named in the record |
|---|---|---|---|
| October 5, 2010 | 3 | 3.00" | MARICOPA |
“This storm moved from Firebird Lake, south of Chandler to the north Glendale/south Peoria area. This storm produced widespread golf ball to baseball sized hail along its path. Thousands of roofs and vehicles were damaged by the hail. Locations in northwest Phoenix and Glendale were impacted by this storm as well as the storm shortly after noon, compounding the damage. The football coach at Alhambra High School re”
— NWS event narrative, October 5, 2010 (NCEI Storm Events)
When it fell
Oct 3
Wind context: the record also holds 34 thunderstorm-wind events ≥50 kt (≈58 mph, the NWS severe criterion) in this radius for 2010 — relevant where the dispute is wind vs hail causation.
Working a Phoenix claim from 2010?
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 Phoenix 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.