StormProof → hail seasons → Fort Collins → 2024
Fort Collins hail season 2024
17 NWS-recorded hail reports ≥1″ within 25 miles, across 3 storm days, max 2.00". Every one of those reports is a dated, located, citable official record — the context behind this market's 2024 claim volume.
Biggest storm days (2024, final record)
| Date | ≥1″ reports | Max hail | Areas named in the record |
|---|---|---|---|
| July 20, 2024 | 8 | 1.50" | LARIMER |
| May 28, 2024 | 8 | 2.00" | WELD |
| August 7, 2024 | 1 | 1.75" | WELD |
“Broadcast media source provided numerous photos of crop damage due to hail and wind at a malthouse. Significant crop loss was noted across 120 acres of distillers corn, 12 acres of trial blue corn, 300 acres of alfalfa and 70 acres of Genie barley. All of the corn and barley acreage was considered a total loss.”
— NWS event narrative, July 20, 2024 (NCEI Storm Events)
When it fell
May 8 · Jul 8 · Aug 1
Wind context: the record also holds 7 thunderstorm-wind events ≥50 kt (≈58 mph, the NWS severe criterion) in this radius for 2024 — relevant where the dispute is wind vs hail causation.
Working a Fort Collins claim from 2024?
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 Fort Collins 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.