Sage Fire, 28 July 2016 Washoe
The fire started on 28 July 2016 in Washoe, United States, and satellites saw it burning for 5 days. United States agencies (MTBS / NIFC) mapped an official burnt perimeter of 1,626 hectares, spread across a single county.
It is the 123th largest in Nevada since 2016 (of 237 with a page). Number 189 in United States in 2016, of 475.
Compare with…
- Burnt area
- 1,626ha
- official perimeter (MTBS / NIFC)
- Duration
- ≈ 5days
- 28 Jul 2016 – 1 Aug 2016
- Counties hit
- 1
- counties
- Started on
- 28 Jul
- 2016
- Heat detections
- 72
- in a single hotspot: 39 MW
- Danger at start
- 54
- Extreme · FWI index
- Average daily power
- 262MW
- 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 more than two months 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
-
Washoe where it started1,608 ha reached on 29 Jul0.1 %
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 2015Inside the perimeter there was no noticeable built-up land and almost nobody lived there (GHSL 2015, 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.
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)
| Day | High | Min. humidity | Peak gust | Rain | Danger (FWI) |
|---|---|---|---|---|---|
| 28 Jul | 37.3 °C | 12 % | 45 km/h | 0.4 mm | Extreme 54 |
| 29 Jul | 36.7 °C | 13 % | 50 km/h | 0.0 mm | Extreme 56 |
| 30 Jul | 35.6 °C | 12 % | 54 km/h | 0.0 mm | Extreme 61 |
| 31 Jul | 33.9 °C | 13 % | 53 km/h | 0.0 mm | Extreme 61 |
| 1 Aug | 34.3 °C | 9 % | 49 km/h | 0.0 mm | Extreme 59 |
| 2 Aug after | 33.9 °C | 7 % | 47 km/h | 0.0 mm | Extreme 58 |
| 3 Aug after | 32.6 °C | 7 % | 28 km/h | 0.0 mm | Very high 48 |
| 4 Aug after | 32.8 °C | 6 % | 49 km/h | 0.0 mm | Extreme 60 |
| 5 Aug after | 29.4 °C | 8 % | 56 km/h | 0.0 mm | Extreme 64 |
| 6 Aug after | 30.3 °C | 10 % | 46 km/h | 0.0 mm | Extreme 56 |
| 7 Aug after | 29.4 °C | 10 % | 42 km/h | 0.0 mm | Extreme 54 |
| 8 Aug after | 29.1 °C | 11 % | 55 km/h | 0.0 mm | Extreme 57 |
| 9 Aug after | 28.3 °C | 15 % | 36 km/h | 0.0 mm | Very high 44 |
| 10 Aug after | 27.9 °C | 12 % | 33 km/h | 0.0 mm | Very high 46 |
| 11 Aug after | 31.0 °C | 11 % | 24 km/h | 0.0 mm | Very high 43 |
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.
Detections table · 72Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 32,578 haLong Valley WashoeJuly 2017 · 7 days · 0 km away
- 6,216 haAnderson WashoeJuly 2016 · 4 days · 8 km away
- 14,312 haTule WashoeJuly 2016 · 7 days · 19 km away
- 37,933 haBug WashoeAugust 2026 · 8 days · 21 km away
- 43,900 haSugar PlumasJuly 2021 · 23 days · 25 km away
- 18,422 haLoyalton SierraAugust 2020 · 8 days · 37 km away
Frequently asked questions
- How long did the Sage Fire last?
- The official perimeter only gives the start date (28 July 2016). The end comes from the heat detections inside the perimeter: it burned until 1 August 2016 (5 days from 28 July 2016), 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 1,626 hectares (16.3 km²). Other tallies, such as daily incident reports, may give slightly different figures.
- Which counties burned?
- The fire only entered Washoe (1,608 ha, 0.1 %).
- What was the weather like?
- During the fire the temperature reached 37.3 °C, humidity dropped to 9 % and gusts hit 54 km/h. The fire danger index (FWI) reached 61, class 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.
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: 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. 72 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 2015, 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.