Cascade Fire, July 2026 Idaho
The fire started on 17 July 2026 in Idaho, United States, and satellites saw it burning for 8 days. United States agencies (MTBS / NIFC) mapped an official burnt perimeter of 4,095 hectares, spread across a single county.
It is the 83th largest in Idaho since 2016 (of 379 with a page). Number 105 in United States in 2026, of 423.
The power measured by the satellite is low (18.9 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.
Compare with…
- Burnt area
- 4,095ha
- official perimeter (MTBS / NIFC)
- Duration
- ≈ 8days
- 17 Jul 2026 – 24 Jul 2026
- Counties hit
- 1
- counties
- Started on
- 17 Jul
- 2026
- Heat detections
- 9
- in a single hotspot: 19 MW
- Danger at start
- 10
- Low · FWI index
- Average daily power
- 36MW
- detected power per day, on average
Where it burned
How it evolved, day by day
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
It had gone 2 days without rain (1 mm or more) when it started.
This area had burned before
No earlier perimeters overlap this fire since 2016, when the satellite record begins.
How big is it?
London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).
Paris boundary: geoBoundaries · Institut national de l'information géographique et forestière (IGN-F) (Etalab Open License 2.0).
Madrid boundary: geoBoundaries · Open Data ESRI, IGN Central Registry of Cartography Area (CC BY 4.0).
Berlin boundary: geoBoundaries · Federal Agency for Cartography and Geodesy (dl-de/by-2-0).
This compares size, not location: both shapes are at the same scale, north up, centred on each other.
What happened to each county
-
Idaho where it started4,134 ha reached on 22 Jul0.2 %
Burnt area inside each county, from crossing the official perimeter with administrative boundaries. The distance runs from the point marking the centre of each area to the nearest fire: staying a kilometre away does not mean it reached the houses.
The weather day by day
ECMWF ERA5 reanalysis at the fire location, the standard reference for past weather, and the Canadian Fire Weather Index (the same system Copernicus uses), computed by WorldFires from that data. Days after the fire run until the first rain.
Open-Meteo.com (CC BY 4.0) · Copernicus Climate Change Service (ERA5)
| Day | High | Min. humidity | Peak gust | Rain | Danger (FWI) |
|---|---|---|---|---|---|
| 17 Jul | 33.1 °C | 38 % | 35 km/h | 2.3 mm | Low 10 |
| 18 Jul | 31.1 °C | 50 % | 35 km/h | 5.5 mm | Very low 2 |
| 19 Jul | 32.2 °C | 24 % | 42 km/h | 0.0 mm | Moderate 15 |
| 20 Jul | 30.4 °C | 32 % | 34 km/h | 0.0 mm | Moderate 17 |
| 21 Jul | 34.2 °C | 31 % | 36 km/h | 0.0 mm | Moderate 20 |
| 22 Jul | 33.8 °C | 27 % | 34 km/h | 0.0 mm | High 22 |
| 23 Jul | 36.0 °C | 28 % | 27 km/h | 0.9 mm | Moderate 20 |
| 24 Jul | 35.9 °C | 26 % | 48 km/h | 1.0 mm | High 25 |
| 25 Jul after | 35.8 °C | 18 % | 49 km/h | 0.0 mm | High 34 |
| 26 Jul after | 32.5 °C | 32 % | 38 km/h | 0.0 mm | High 28 |
| 27 Jul after | 32.9 °C | 24 % | 35 km/h | 0.0 mm | High 28 |
| 28 Jul after | 33.5 °C | 21 % | 41 km/h | 0.0 mm | High 30 |
| 29 Jul after | 34.0 °C | 24 % | 38 km/h | 0.0 mm | High 31 |
| 30 Jul after | 34.2 °C | 26 % | 40 km/h | 0.7 mm | High 26 |
| 31 Jul after | 36.3 °C | 23 % | 28 km/h | 0.2 mm | High 30 |
| 1 Aug after | 33.5 °C | 26 % | 48 km/h | 0.0 mm | High 35 |
| 2 Aug after | 24.7 °C | 31 % | 44 km/h | 0.0 mm | High 30 |
| 3 Aug after | 25.6 °C | 26 % | 30 km/h | 0.0 mm | High 27 |
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
If the day is cloudy, change the date: each satellite passes once a day. In false colour the burnt ground looks brown or red.
The smoke
CAMS · CopernicusOn 27 July 2026 the air beside the fire reached 52 µg/m³ of PM2.5. That day averaged 39: 2.6 times the WHO daily guideline (15).
Particles from the Copernicus CAMS model at the centre of the perimeter; these are not measurements in each town. The pale bar is the worst hour, the solid one the daily average.
Open-Meteo.com (CC BY 4.0) · Copernicus Atmosphere Monitoring Service (CAMS)
Detections table · 9Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 6,889 haLone Pine IdahoJuly 2017 · 62 days · 10 km away
- 2,455 haBuck Lake Creek IdahoAugust 2017 · 7 days · 15 km away
- 8,598 haMoose Creek 1 IdahoJuly 2017 · 62 days · 21 km away
- 6,033 haIsland Creek IdahoAugust 2025 · 7 days · 23 km away
- 5,588 haLynx IdahoJuly 2021 · 84 days · 31 km away
- 4,530 haShissler IdahoAugust 2020 · 32 days · 36 km away
Frequently asked questions
- How long did the Cascade Fire last?
- The official perimeter only gives the start date (17 July 2026). The end comes from the heat detections inside the perimeter: it burned until 24 July 2026 (8 days from 17 July 2026), the last day with detections before more than 10 days in a row without any, so it is approximate.
- How much area did it burn?
- The official perimeter published by United States agencies (MTBS / NIFC) is 4,095 hectares (41.0 km²). Other tallies, such as daily incident reports, may give slightly different figures.
- Which counties burned?
- The fire only entered Idaho (4,134 ha, 0.2 %).
- What was the weather like?
- During the fire the temperature reached 36.0 °C, humidity dropped to 24 % and gusts hit 48 km/h. The fire danger index (FWI) reached 25, class High.
- Where does this data come from?
- From the official burnt perimeter of United States agencies (MTBS / NIFC, public domain), NASA FIRMS VIIRS hotspots and the administrative boundaries of United States. It is not an official report.
Where to verify it
A satellite detection is not an official report. Final figures and the fire’s status are published by each country’s emergency service.
Emergency number: 911 · Emergency number and official warnings ›
- NIFC · National Interagency Fire Center ↗
- InciWeb · Incident Information System ↗
- MTBS · Monitoring Trends in Burn Severity ↗
Satellite cross-check
History of this page Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
No changes since 24 October 2026.
Does something look wrong on this page?
This page is built from satellite data and official records, and it sometimes gets things wrong: the wrong dates, the wrong town, two fires merged into one, or something that was not a wildfire at all. If you know this fire first-hand (you live nearby, saw it, fought it or reported on it), tell us what really happened and we will check it.
Report an error
How we know this
- Perimeter: NIFC WFIGS (United States), official; 2 polygons grouped in this page.
- The official perimeter has no end date: the end is the last day with VIIRS detections inside the perimeter before a gap of more than 10 days (150 days at most), so it is approximate. 9 Suomi-NPP VIIRS detections on those dates.
- We have not matched this page with any official record.
- Weather: Copernicus ERA5 reanalysis at the fire location, in cells of about 25 km.
Where this data comes from
The perimeter is official and in the public domain. For past years it comes from MTBS (Monitoring Trends in Burn Severity), run by the U.S. Geological Survey and the USDA Forest Service, which map it on Landsat and Sentinel-2 imagery. For the current and last year it comes from WFIGS at the National Interagency Fire Center (NIFC): incident perimeters mapped by fire crews, aircraft and imagery. Heat detections come from the VIIRS sensors aboard Suomi-NPP and NOAA-20, distributed by NASA FIRMS at 375 m resolution. County boundaries come from geoBoundaries ADM2 (Public Domain). The area per county is computed by WorldFires by crossing the perimeter with those boundaries, so it may differ slightly from official figures.