Jackpot Fire, August 2016 Washoe
The fire started on 7 August 2016 in Washoe, United States, and satellites saw it burning for 1 day. United States agencies (MTBS / NIFC) mapped an official burnt perimeter of 667 hectares, spread across a single county.
It is the 188th largest in Nevada since 2016 (of 237 with a page). Number 346 in United States in 2016, of 475.
The power measured by the satellite is low (6.7 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.
- Burnt area
- 667ha
- official perimeter (MTBS / NIFC)
- Duration
- 1day
- 7 Aug 2016 – 7 Aug 2016
- Municipalities hit
- 1
- counties
- Started on
- 7 Aug
- 2016
- Heat detections
- 18
- in a single hotspot: 7 MW
- Danger at start
- 55
- Extreme · FWI index
- Energy released
- 60MW
- sum of detected power
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.
What happened to each town
-
Washoe where it started655 ha reached on 7 Aug0.0 %
Burnt area inside each county, from crossing the official perimeter with administrative boundaries. The distance is from the town centre 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) |
|---|---|---|---|---|---|
| 7 Aug | 27.7 °C | 10 % | 40 km/h | 0.0 mm | Extreme 55 |
| 8 Aug after | 27.6 °C | 9 % | 52 km/h | 0.0 mm | Extreme 60 |
| 9 Aug after | 27.2 °C | 12 % | 37 km/h | 0.0 mm | Very high 48 |
| 10 Aug after | 26.7 °C | 10 % | 35 km/h | 0.0 mm | Very high 50 |
| 11 Aug after | 29.4 °C | 11 % | 25 km/h | 0.0 mm | Very high 45 |
| 12 Aug after | 31.9 °C | 11 % | 26 km/h | 0.0 mm | Very high 46 |
| 13 Aug after | 33.7 °C | 9 % | 43 km/h | 0.0 mm | Extreme 53 |
| 14 Aug after | 31.9 °C | 11 % | 51 km/h | 0.0 mm | Extreme 60 |
| 15 Aug after | 30.6 °C | 7 % | 26 km/h | 0.0 mm | Very high 46 |
| 16 Aug after | 30.9 °C | 10 % | 28 km/h | 0.0 mm | Very high 47 |
| 17 Aug after | 31.1 °C | 10 % | 29 km/h | 0.0 mm | Extreme 52 |
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 · 18Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 37,933 haBug WashoeAugust 2026 · 1 day · 7 km away
- 18,422 haLoyalton SierraAugust 2020 · 1 day · 14 km away
- 32,578 haLong Valley WashoeJuly 2017 · 1 day · 28 km away
- 43,900 haSugar PlumasJuly 2021 · 1 day · 31 km away
- 14,312 haTule WashoeJuly 2016 · 1 day · 34 km away
- 6,216 haAnderson WashoeJuly 2016 · 1 day · 35 km away
Frequently asked questions
- How long did the Jackpot fire last?
- It burned between 7 August 2016 and 7 August 2016: 1 day, according to the start date recorded by United States agencies (MTBS / NIFC) and the heat detections seen by satellite.
- How much area did it burn?
- The official perimeter published by United States agencies (MTBS / NIFC) is 667 hectares (6.7 km²). Other tallies, such as daily incident reports, may give slightly different figures.
- Which counties burned?
- The fire only entered Washoe (655 ha, 0.0 %).
- What was the weather like?
- During the fire the temperature reached 27.7 °C, humidity dropped to 10 % and gusts hit 40 km/h. The fire danger index (FWI) reached 55, 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
- NIFC · National Interagency Fire Center ↗
- InciWeb · Incident Information System ↗
- MTBS · Monitoring Trends in Burn Severity ↗
Satellite cross-check
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
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.