StormProof unlimited NWS storm verification · for pros

StormProofhail seasonsPhoenix → 2002

Phoenix hail season 2002

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

Biggest storm days (2002, final record)

Date≥1″ reportsMax hailAreas named in the record
September 7, 200211.75"MARICOPA
August 28, 200211.00"MARICOPA

“Numerous reports of large hail throughout the West Valley, including Sun City, Peoria, and Phoenix. Winds to over 60 mph damaged homes, blew down power poles and uprooted trees. Streets were flooded in the West Valley as rain totals were as much as 1.85 inches. Arizona Public Service and Salt River Project estimated over 11,000 customers were without power.”

— NWS event narrative, September 7, 2002 (NCEI Storm Events)

When it fell

Aug 1 · Sep 1

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

Working a Phoenix claim from 2002?

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.