StormProof unlimited NWS storm verification · for pros

StormProofhail seasonsColorado Springs → 1999

Colorado Springs hail season 1999

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

Biggest storm days (1999, final record)

Date≥1″ reportsMax hailAreas named in the record
June 11, 199962.50"EL PASO
June 9, 199921.00"EL PASO
August 19, 199911.00"EL PASO
June 23, 199911.00"EL PASO
May 24, 199911.00"EL PASO

“A massive, long-lasting hail fall, with stones ranging from 1/2 inch to 2.5 inches in diameter, piled up to depths of 1 to 2 feet with hail drifts to 4 feet in heavy runoff areas. A final tally on damage amounts was not available as of late August.”

— NWS event narrative, June 11, 1999 (NCEI Storm Events)

When it fell

May 3 · Jun 9 · Aug 1

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

Working a Colorado Springs claim from 1999?

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 Colorado Springs 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.