StormProof unlimited NWS storm verification · for pros

StormProofhail seasonsEl Paso → 2016

El Paso hail season 2016

2 NWS-recorded hail reports ≥1″ within 25 miles, across 1 storm days, max 1.75". 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
November 4, 201621.75"EL PASO

“Supercell thunderstorms (very rare for November in this area) affected much of El Paso. The strongest, which actually weakened before moving into the United States, produced golf ball hail over far east El Paso into Horizon City. This caused record breaking insurance claims for a single hail event with a total of $200 million damage to vehicles and $100 million to homes. This doubled the previous record from 9-16-09”

— NWS event narrative, November 4, 2016 (NCEI Storm Events)

When it fell

Nov 2

Wind context: the record also holds 5 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 El Paso 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 25 miles of the El Paso 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.