NOAA STORM EVENTS · COMPLETE YEARS 2016–2025HISTORICAL REPORTS, NOT A FORECAST OR RISK SCORE
STORM EVENTLEDGERCOUNTY REPORTS · SEASONALITY · IMPACT
EVENT FILE / 30013MINIMUM 5 REPORTS

CASCADE · MT

Flood history

NOAA records coded as Flood in Cascade during the ten complete years from 2016 through 2025.

Reports9NOAA county-coded rows
Population context10.6per 100,000 residents · 2024 ACS denominator 84,606
Injuries0direct + indirect fields
Fatalities2direct + indirect fields
Not a probability

9 reports in ten years does not mean a 0.9-event annual forecast. Reporting units, event segmentation, coverage, and local exposure all affect the count.

01 / YEAR-BY-YEAR

How the record changed

20182
20194
20201
20232
03 / RECORDED CONSEQUENCES

Impact fields on these rows

Damage estimates are nominal values as filed by the reporting source and retained by NOAA.

Property damage$60Knot inflation-adjusted
Crop damage$0not inflation-adjusted
First report year2,018within selected window
Latest report year2,023within selected window
04 / RECENT ROW SAMPLE

Latest records in this slice

Up to eight latest rows are shown for auditability. Open NOAA for complete narratives and revisions.

DateEvent IDSourceMagnitude / scaleFiled damage
2023-05-17NOAA 1,102,212River/Stream Gage$60K
2023-05-06NOAA 1,102,210River/Stream Gage$0
2020-07-23NOAA 904,775Emergency Manager$0
2019-06-27NOAA 836,951NWS Employee$0
2019-06-27NOAA 836,950NWS Employee$0
2019-06-27NOAA 836,949NWS Employee$0
2019-05-27NOAA 818,926Department of Highways$0
2018-06-21NOAA 763,401NWS Employee$0
READING THE RECORD

History is evidence—not a forecast.

A NOAA record count describes reports entered for a place and period. It does not estimate the chance, severity, or location of a future event. For active hazards, use your local National Weather Service office and official alerts.