StormProof unlimited NWS storm verification · for pros

StormProofhail seasonsPhiladelphia → 2011

Philadelphia hail season 2011

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

Biggest storm days (2011, final record)

Date≥1″ reportsMax hailAreas named in the record
August 1, 201191.75"GLOUCESTER, CAMDEN, DELAWARE, PHILADELPHIA
August 18, 201151.00"NEW CASTLE, DELAWARE, GLOUCESTER, MONTGOMERY
September 11, 201121.25"CHESTER, BURLINGTON
August 9, 201121.25"NEW CASTLE
August 19, 201111.00"CAMDEN

“A severe thunderstorm dropped hail as large as quarter size in Malaga (Franklin Township). The same thunderstorm produced wind gusts of around 50 mph and knocked down branches.”

— NWS event narrative, August 1, 2011 (NCEI Storm Events)

When it fell

May 1 · Jun 3 · Aug 17 · Sep 2

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

Working a Philadelphia claim from 2011?

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 Philadelphia 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.