Saddle Fire, June 2016 Washington
The fire started on 13 June 2016 in Washington, United States, and satellites saw it burning for 1 day. United States agencies (MTBS / NIFC) mapped an official burnt perimeter of 958 hectares, spread across a single county.
It is the 109th largest in Utah since 2016 (of 165 with a page). Number 277 in United States in 2016, of 475.
- Burnt area
- 958ha
- official perimeter (MTBS / NIFC)
- Duration
- 1day
- 13 Jun 2016 – 13 Jun 2016
- Municipalities hit
- 1
- counties
- Started on
- 13 Jun
- 2016
- Heat detections
- 326
- in a single hotspot: 189 MW
- Danger at start
- 30
- High · FWI index
Where it burned
The weather it burned in
It had gone one day 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
-
Washington where it started954 ha reached on 16 Jun0.2 %
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) |
|---|---|---|---|---|---|
| 13 Jun | 20.2 °C | 15 % | 49 km/h | 0.7 mm | High 30 |
| 14 Jun after | 23.2 °C | 11 % | 63 km/h | 0.0 mm | Very high 44 |
| 15 Jun after | 22.7 °C | 8 % | 85 km/h | 0.0 mm | Extreme 60 |
| 16 Jun after | 22.3 °C | 9 % | 64 km/h | 0.0 mm | Extreme 51 |
| 17 Jun after | 24.2 °C | 10 % | 64 km/h | 0.0 mm | Extreme 52 |
| 18 Jun after | 26.7 °C | 6 % | 58 km/h | 0.0 mm | Extreme 53 |
| 19 Jun after | 30.8 °C | 8 % | 45 km/h | 0.0 mm | Very high 48 |
| 20 Jun after | 33.0 °C | 6 % | 51 km/h | 0.0 mm | Extreme 55 |
| 21 Jun after | 32.1 °C | 6 % | 52 km/h | 0.0 mm | Extreme 61 |
| 22 Jun after | 30.5 °C | 8 % | 57 km/h | 0.0 mm | Extreme 61 |
| 23 Jun after | 30.1 °C | 7 % | 52 km/h | 0.0 mm | Extreme 59 |
| 24 Jun after | 29.2 °C | 6 % | 53 km/h | 0.0 mm | Extreme 60 |
| 25 Jun after | 28.6 °C | 7 % | 45 km/h | 0.0 mm | Extreme 62 |
| 26 Jun after | 31.1 °C | 5 % | 32 km/h | 0.0 mm | Very high 49 |
| 27 Jun after | 31.8 °C | 5 % | 36 km/h | 0.0 mm | Extreme 52 |
| 28 Jun after | 28.7 °C | 14 % | 42 km/h | 0.2 mm | Extreme 50 |
| 29 Jun after | 29.0 °C | 11 % | 46 km/h | 0.0 mm | Extreme 64 |
| 30 Jun after | 25.1 °C | 17 % | 41 km/h | 7.8 mm | Low 8 |
| 1 Jul after | 22.8 °C | 34 % | 38 km/h | 12.5 mm | Very low 2 |
| 2 Jul after | 19.7 °C | 53 % | 32 km/h | 8.6 mm | Very low 0 |
| 3 Jul after | 23.7 °C | 26 % | 42 km/h | 0.2 mm | Low 6 |
| 4 Jul after | 25.5 °C | 20 % | 47 km/h | 0.0 mm | Moderate 20 |
| 5 Jul after | 26.3 °C | 11 % | 62 km/h | 0.0 mm | High 34 |
| 6 Jul after | 25.4 °C | 9 % | 59 km/h | 0.0 mm | High 37 |
| 7 Jul after | 26.5 °C | 9 % | 54 km/h | 0.0 mm | High 37 |
| 8 Jul after | 26.8 °C | 9 % | 64 km/h | 0.0 mm | Very high 43 |
| 9 Jul after | 26.9 °C | 8 % | 68 km/h | 0.0 mm | Very high 47 |
| 10 Jul after | 25.6 °C | 12 % | 63 km/h | 0.0 mm | Very high 47 |
| 11 Jul after | 25.7 °C | 8 % | 52 km/h | 0.0 mm | Very high 46 |
| 12 Jul after | 27.4 °C | 7 % | 56 km/h | 0.0 mm | Very high 47 |
| 13 Jul after | 28.8 °C | 6 % | 38 km/h | 0.0 mm | Very high 41 |
| 14 Jul after | 30.5 °C | 5 % | 38 km/h | 0.0 mm | Very high 44 |
| 15 Jul after | 30.1 °C | 6 % | 55 km/h | 0.0 mm | Extreme 55 |
| 16 Jul after | 28.2 °C | 6 % | 67 km/h | 0.0 mm | Extreme 62 |
| 17 Jul after | 27.9 °C | 10 % | 75 km/h | 0.0 mm | Extreme 66 |
| 18 Jul after | 26.7 °C | 16 % | 58 km/h | 0.1 mm | Extreme 52 |
| 19 Jul after | 27.3 °C | 12 % | 56 km/h | 0.0 mm | Extreme 52 |
| 20 Jul after | 27.9 °C | 15 % | 52 km/h | 0.0 mm | Extreme 50 |
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 · 326Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 6,338 haForsyth WashingtonJune 2025 · 1 day · 6 km away
- 1,100 haVeyo West WashingtonJuly 2020 · 1 day · 13 km away
- 4,825 haWest Valley WashingtonJune 2018 · 1 day · 16 km away
- 4,836 haTurkey Farm Road WashingtonJuly 2020 · 1 day · 17 km away
- 1,001 haVeyo Road WashingtonSeptember 2020 · 1 day · 18 km away
- 643 haCottonwood Trail WashingtonJuly 2020 · 1 day · 21 km away
Frequently asked questions
- How long did the Saddle fire last?
- It burned between 13 June 2016 and 13 June 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 958 hectares (9.6 km²). Other tallies, such as daily incident reports, may give slightly different figures.
- Which counties burned?
- The fire only entered Washington (954 ha, 0.2 %).
- What was the weather like?
- During the fire the temperature reached 33.0 °C, humidity dropped to 5 % and gusts hit 85 km/h. The fire danger index (FWI) reached 64, 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.