Burned area
satellite only7,365ha
Perimeter published by MTBS (USGS/USFS).
- Source
- MTBS (USGS/USFS)
- Date
- 24 Jul 2024 – 31 Jul 2024
+− cross-check
No official record is matched to this page to compare it with.
US · United States · –
Stockade Canyon Fire, July 2024 Washoe
Out · last detection 31 Jul 2024, 21:05 UTC
The fire started on 24 July 2024 in Washoe, United States, and satellites saw it burning for 8 days. United States agencies (MTBS / NIFC) mapped an official burnt perimeter of 7,365 hectares, spread across a single county.
It is the 35th largest in Nevada since 2016 (of 236 with a page). Number 62 in United States in 2024, of 371.
Use this data
Compare with…
Use this data
Fire page data · version 2026-10-24matches the official recordwith caveatssatellite onlymodel
When copying, the sentence is
Tick the figures you want: they make up the lede and the CSV.
Duration by satellite
satellite only8days
24 Jul 2024 to 31 Jul 2024: first and last day with fire on the page.
- Source
- MTBS (USGS/USFS) · NASA FIRMS · VIIRS
- Date
- last detection: 31 Jul 2024, 21:05 UTC
+− cross-check
Satellites pass a few times a day and cloud or smoke can hide the fire: a lack of detections is not an official extinction. Each country’s emergency service declares a fire contained or out.
Start
satellite only24 Jul 2024
First day with fire seen by the satellites or the perimeter.
- Source
- MTBS (USGS/USFS) · NASA FIRMS · VIIRS
- Date
- 24 Jul 2024
+− cross-check
No official record is matched to this page, so the alert time and the cause are not known here.
Hotspots
satellite only412
VIIRS detections at 375 m. Most intense hotspot: 426 MW.
- Source
- NASA FIRMS · VIIRS (Suomi NPP + NOAA-20)
- Date
- 24 Jul 2024 – 31 Jul 2024
+− cross-check
There is no official record to compare with. Each hotspot is a pixel detected in one satellite pass, not a separate fire.
The worst day
satellite only11,109MW
Total radiative power on 26 July 2024; hotspots that day: 191.
- Source
- NASA FIRMS · VIIRS (FRP)
- Date
- 26 Jul 2024
+− cross-check
Fire radiative power (FRP) measures the energy the fire gives off when the satellite passes. Added up by day, it compares intensity, not area.
Danger at the start
model43.0FWI · very high
Fire Weather Index (Canadian system) computed by WorldFires for the day the fire started. Consecutive days without rain before: 0.
- Source
- WorldFires calculation (Canadian FWI system)
- Date
- 24 Jul 2024, local noon
- Model
- ERA5 0,25° (ECMWF · Copernicus C3S) · Open-Meteo.com
+− cross-check
This is an index computed from weather model data, not a measurement of the fire nor an official warning. Danger warnings are issued by each country’s authority. Emergency number and official warnings
Weather during the fire
model34.3°C · 12% RH
High of 34.3 °C and minimum humidity of 12% on 24 July 2024; gusts of 59 km/h on 24 July 2024.
- Source
- weather model at the fire’s grid cell
- Date
- 24 Jul 2024 – 31 Jul 2024
- Model
- ERA5 0,25° (ECMWF · Copernicus C3S) · Open-Meteo.com
+− cross-check
These are model values for a cell of about 25 km, not from a weather station: they may differ from what was measured on the ground.
This page’s change log has been kept since 24 October 2026: every night what it publishes is compared and the difference is logged. Anything earlier is reconstructed from each source’s date and marked as reconstructed.
Show
-
· reconstructed weatherWeather and FWI computed from the ERA5 reanalysis
-
· reconstructed GHSLPopulation and built-up area computed
What was saved on 24 October 2026
Every night a snapshot of what the page shows is saved. If anything changes, it appears in the list as a log entry.
- Area
- 7,365 ha
- Dates
- 24 Jul 2024 – 31 Jul 2024
- Name
- Stockade Canyon
- Official record
- —
Versioned permanent link
https://worldfires.org/en/fire/stockade-canyon-fire-2024-07?v=2026-10-24A version keeps the area, dates, name and official record; the area as it was logged (changes under 2% are not logged). The map, hotspots and weather always show today’s data.
Citation
A lede of about 60 words figures only, no adjectives
CSV for this fire stockade-canyon-fire-2024-07.csv · daily, no individual hotspots
| fecha | focos_viirs | frp_mw | tmax_c | tmin_c | hr_min_pct | viento_max_kmh | racha_max_kmh | precip_mm | fwi | clase_fwi | dentro_del_incendio |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2024-07-24 | 37 | 2,935 | 34.3 | 20.4 | 12 | 30.6 | 59 | 0.4 | 43 | muy_alto | 1 |
| 2024-07-25 | 76 | 3,904 | 32.9 | 19 | 9 | 25.1 | 54 | 0 | 80.1 | muy_extremo | 1 |
| 2024-07-26 | 191 | 11,109 | 32.1 | 15.7 | 6 | 23.9 | 47.5 | 0 | 78.1 | muy_extremo | 1 |
| 2024-07-27 | 57 | 775 | 26.1 | 14.6 | 15 | 16.8 | 38.9 | 0 | 57.9 | extremo | 1 |
| 2024-07-28 | 14 | 51 | 27.8 | 9.9 | 12 | 15.6 | 37.1 | 0 | 56.2 | extremo | 1 |
| 2024-07-29 | 27 | 1,134 | 28.6 | 10.4 | 11 | 19.1 | 44.6 | 0 | 61.9 | extremo | 1 |
| 2024-07-30 | 2 | 9 | 29.6 | 12.8 | 15 | 14.4 | 34.6 | 0 | 57.8 | extremo | 1 |
| 2024-07-31 | 8 | 245 | 31.7 | 14.8 | 12 | 11.4 | 28.8 | 0 | 54.4 | extremo | 1 |
| 2024-08-01 | 0 | 0 | 34.5 | 16.8 | 8 | 15.7 | 34.9 | 0 | 62.8 | extremo | 0 |
| 2024-08-02 | 0 | 0 | 34.4 | 16.2 | 9 | 20.6 | 42.1 | 0 | 56.5 | extremo | 0 |
| 2024-08-03 | 0 | 0 | 28.6 | 19.1 | 23 | 16.3 | 41.4 | 0.8 | 57.8 | extremo | 0 |
| 2024-08-04 | 0 | 0 | 32.1 | 13.6 | 19 | 15 | 30.6 | 0 | 42.2 | muy_alto | 0 |
| 2024-08-05 | 0 | 0 | 33.6 | 17.1 | 9 | 17 | 38.5 | 0 | 69 | extremo | 0 |
| 2024-08-06 | 0 | 0 | 34.1 | 15.4 | 5 | 18.1 | 36.4 | 0 | 69.8 | extremo | 0 |
| 2024-08-07 | 0 | 0 | 33.6 | 15.8 | 11 | 17.8 | 38.2 | 0 | 66.1 | extremo | 0 |
| 2024-08-08 | 0 | 0 | 33.4 | 16.3 | 10 | 19.3 | 42.1 | 0.1 | 71.5 | muy_extremo | 0 |
| 2024-08-09 | 0 | 0 | 33.5 | 14.8 | 10 | 18.4 | 40.3 | 0 | 69.8 | extremo | 0 |
| 2024-08-10 | 0 | 0 | 32.1 | 14.9 | 8 | 16.3 | 34.6 | 0 | 67.3 | extremo | 0 |
It is generated in your browser from this page’s data: one file per fire, aggregated by day and without individual hotspots.
Live widget for your story
It updates itself while the fire is still active and links to this page. Free, with the attribution shown at the bottom.
Sources for this page: MTBS (USGS/USFS), NASA FIRMS (VIIRS), ERA5 (ECMWF/Copernicus C3S) · Open-Meteo.com (CC BY 4.0), GHSL (JRC). Open-Meteo.com · How we build fire pages: methodology
- Burnt area
- 7,365ha
- official perimeter (MTBS / NIFC)
- Duration
- ≈ 8days
- 24 Jul 2024 – 31 Jul 2024
- Counties hit
- 1
- counties
- Started on
- 24 Jul
- 2024
- Heat detections
- 412
- in a single hotspot: 426 MW
- Danger at start
- 43
- Very high · FWI index
- Average daily power
- 2.5GW
- detected power per day, on average
Where it burned
HOTSPOTS BY DAY
24 Jul31 Jul
31 Jul 2024
How it evolved, day by day
24 Jul
26 Jul
28 Jul
30 Jul
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
34°high
59km/h · peak gust
6%lowest humidity
It had gone 0 days without rain (1 mm or more) when it started.
This area had burned before
2% of the perimeter overlaps earlier fires recorded since 2016: 135 ha in 2016, 1 ha in 2020.
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
-
Washoe where it started7,384 ha reached on 24 Jul0.4 %
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.
People and buildings inside the perimeter
GHSL 2025Built-up area< 0.1 ha
Residents< 20
Inside the perimeter there was no noticeable built-up land and almost nobody lived there (GHSL 2025, satellite-based estimate).
This is an estimate on 100 m cells, made from satellite imagery and census data: it does not mean that homes burned or that anyone was harmed. The perimeter also contains land that never burned. The GHSL 2025 epoch is a projection made from 2020 and earlier data.
Source: Global Human Settlement Layer (GHS-BUILT-S and GHS-POP R2023A), European Commission Joint Research Centre (JRC), © European Union, CC BY 4.0. Sum inside the perimeter computed by WorldFires. human-settlement.emergency.copernicus.eu
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)
Started with Strong wind: 27 % of the area in United States Very dry air: 41 % of the area in United States
| Day | High | Min. humidity | Peak gust | Rain | Danger (FWI) |
|---|---|---|---|---|---|
| 24 Jul | 34.3 °C | 12 % | 59 km/h | 0.4 mm | Very high 43 |
| 25 Jul | 32.9 °C | 9 % | 54 km/h | 0.0 mm | Very extreme 80 |
| 26 Jul | 32.1 °C | 6 % | 48 km/h | 0.0 mm | Very extreme 78 |
| 27 Jul | 26.1 °C | 15 % | 39 km/h | 0.0 mm | Extreme 58 |
| 28 Jul | 27.8 °C | 12 % | 37 km/h | 0.0 mm | Extreme 56 |
| 29 Jul | 28.6 °C | 11 % | 45 km/h | 0.0 mm | Extreme 62 |
| 30 Jul | 29.6 °C | 15 % | 35 km/h | 0.0 mm | Extreme 58 |
| 31 Jul | 31.7 °C | 12 % | 29 km/h | 0.0 mm | Extreme 54 |
| 1 Aug after | 34.5 °C | 8 % | 35 km/h | 0.0 mm | Extreme 63 |
| 2 Aug after | 34.4 °C | 9 % | 42 km/h | 0.0 mm | Extreme 56 |
| 3 Aug after | 28.6 °C | 23 % | 41 km/h | 0.8 mm | Extreme 58 |
| 4 Aug after | 32.1 °C | 19 % | 31 km/h | 0.0 mm | Very high 42 |
| 5 Aug after | 33.6 °C | 9 % | 38 km/h | 0.0 mm | Extreme 69 |
| 6 Aug after | 34.1 °C | 5 % | 36 km/h | 0.0 mm | Extreme 70 |
| 7 Aug after | 33.6 °C | 11 % | 38 km/h | 0.0 mm | Extreme 66 |
| 8 Aug after | 33.4 °C | 10 % | 42 km/h | 0.1 mm | Very extreme 72 |
| 9 Aug after | 33.5 °C | 10 % | 40 km/h | 0.0 mm | Extreme 70 |
| 10 Aug after | 32.1 °C | 8 % | 35 km/h | 0.0 mm | Extreme 67 |
Its twins: fires that started in the same weather
It started with an FWI of 43.0, a minimum humidity of 12% and rain the day before. Fires in the area that started in weather like this since 2016: 39.
FWI at the start
43.0
Minimum humidity
12 %
Days without rain
0
this fire
chosen twins
rest of the area
Almost identicalSimilar
Outlines of the closest twins
This fire · Stockade Canyon Fire, July 2024
7,365 ha
8 days
FWI 43.0
Min. humidity 12 %
R-14 Buffalo Fire, August 2025
585 ha
1 day
FWI 41.1
Min. humidity 12 %
6 km away, in 2025
First rain (1 mm or more) after it ended: 1.1 mm on 5 Sept.
Parker2 Fire, August 2017
3,097 ha
6 days
FWI 43.0
Min. humidity 11 %
90 km away, in 2017
First rain (1 mm or more) after it ended: 1.7 mm on 9 Aug.
Moonshine Fire, July 2025
1,159 ha
2 days
FWI 42.4
Min. humidity 14 %
168 km away, in 2025
First rain (1 mm or more) after it ended: none in the following ten days.
Devils Lake Fire, July 2017
711 ha
4 days
FWI 39.5
Min. humidity 12 %
200 km away, in 2017
First rain (1 mm or more) after it ended: 2.3 mm on 6 Aug.
Perry Fire, July 2018
21,751 ha
7 days
FWI 40.4
Min. humidity 8 %
112 km away, in 2018
First rain (1 mm or more) after it ended: none in the following ten days.
What happened to them
- 2 days
- median duration
- 1,606 ha
- median area
- 64 %
- went past 1,000 ha
- 1.6 mm
- rain at the end (median; 19 of 39 had it)
It was 4.6 times larger than the median of its twins and lasted 8 days, against 2 days.
Only 8 of its 39 twins burned more. The weather on the first day does not explain everything: the wind in the following days, the fuel and the firefighting also count. In 20 of 39, not even 1 mm fell in the ten days after the end: they went out without rain. In the rest, the first rainy day brought a median of 1.6 mm.
This is a bank of analogues: it shows what usually happens, not what will happen. With fewer than 15 twins we give no figures. How we calculate it
How it ended
—first rain
—no rain in ten days
59km/h · max. gust
It was considered over on 31 Jul, and not even 1 mm fell in the following ten days: it went out without rain. Twins with rain when they ended: 19 of 39, with a median of 1.6 mm.
Weather on this page: Open-Meteo.com (CC BY 4.0) · Copernicus Climate Change Service (ERA5)
How a twin is chosen
- Same area: fires that have already ended, less than 250 km from this one, since 2016.
- Same start: we compare the FWI on the first day, the minimum humidity that day and the run of days without rain before it. The slider sets how much they may differ.
- Only pages with final weather data (ERA5 reanalysis) calculated in the same way as this fire’s; agricultural and grass burns and pages with data under review are left out.
- Fires burning at the same time as this one (a week before or after) are left out: they share the same spell of weather and do not count as a precedent.
- They are sorted by similarity, and the outlines of the first five are drawn.
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
↔
Before · 17 Jul 2024
After · 7 Aug 2024
Sentinel-2 did not pass over on that day. Try another date, or use false colour, which is daily.
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 2024 the air beside the fire reached 62 µg/m³ of PM2.5. That day averaged 30: 2.0 times the WHO daily guideline (15).
PM2.5 peak62 µg/m³
Days over the guideline2 days
PM1088 µg/m³
Optical depth0.74
WHO 15
22 Jul24 Jul26 Jul
Good
Fair
Moderate
Poor
Very poor
Extremely poor
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 · 412Every satellite heat detection, one by one, with time, satellite, power and coordinates.
⬇ Download CSV
Times in UTC. Each detection is a 375 m pixel: a large fire yields hundreds per pass.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
Frequently asked questions
- How long did the Stockade Canyon Fire last?
- The official perimeter only gives the start date (24 July 2024). The end comes from the heat detections inside the perimeter: it burned until 31 July 2024 (8 days from 24 July 2024), 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 7,365 hectares (73.6 km²). Other tallies, such as daily incident reports, may give slightly different figures.
- Which counties burned?
- The fire only entered Washoe (7,384 ha, 0.4 %).
- What was the weather like?
- During the fire the temperature reached 34.3 °C, humidity dropped to 6 % and gusts hit 59 km/h. The fire danger index (FWI) reached 80, class Very extreme.
- 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.
- How did the fires that started in similar weather in this area end?
- Fires less than 250 km away that started since 2016 with a similar FWI, humidity and dry spell: 39. Their median duration was 2 days and their median area 1,606 ha; 64 % went past 1,000 ha. Only 8 of its 39 twins burned more. The weather on the first day does not explain everything: the wind in the following days, the fuel and the firefighting also count. In 20 of 39, not even 1 mm fell in the ten days after the end: they went out without rain. In the rest, the first rainy day brought a median of 1.6 mm.
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.
RSS Changes to this page With cross-checks and a citable version
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: MTBS (US Geological Survey and US Forest Service), official.
- 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. 412 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.
- Built-up area and population come from the JRC Global Human Settlement Layer (epoch 2025, 100 m cells), summed inside the perimeter: an estimate of what was there, not a damage count.
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.