Tenderfoot Fire, June 2016 Yavapai
The fire started on 8 June 2016 in Yavapai, United States, and satellites saw it burning for 5 days. United States agencies (MTBS / NIFC) mapped an official burnt perimeter of 1,765 hectares, spread across a single county.
It is the 145th largest in Arizona since 2016 (of 380 with a page). Number 179 in United States in 2016, of 475.
- Burnt area
- 1,765ha
- official perimeter (MTBS / NIFC)
- Duration
- 5days
- 8 Jun 2016 – 12 Jun 2016
- Municipalities hit
- 1
- counties
- Started on
- 8 Jun
- 2016
- Heat detections
- 71
- in a single hotspot: 170 MW
- Danger at start
- 54
- Extreme · FWI index
- Average daily power
- 514MW
- 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 20 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.
What happened to each town
-
Yavapai where it started1,755 ha reached on 9 Jun0.1 %
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) |
|---|---|---|---|---|---|
| 8 Jun | 31.1 °C | 14 % | 37 km/h | 0.0 mm | Extreme 54 |
| 9 Jun | 30.4 °C | 17 % | 41 km/h | 0.0 mm | Extreme 53 |
| 10 Jun | 28.8 °C | 18 % | 40 km/h | 0.5 mm | Very high 47 |
| 11 Jun | 27.7 °C | 24 % | 52 km/h | 0.2 mm | Extreme 51 |
| 12 Jun | 28.4 °C | 12 % | 53 km/h | 0.0 mm | Extreme 55 |
| 13 Jun after | 26.5 °C | 12 % | 41 km/h | 0.0 mm | Very high 48 |
| 14 Jun after | 27.7 °C | 10 % | 41 km/h | 0.0 mm | Very high 49 |
| 15 Jun after | 27.1 °C | 7 % | 52 km/h | 0.0 mm | Extreme 60 |
| 16 Jun after | 28.3 °C | 11 % | 48 km/h | 0.0 mm | Extreme 57 |
| 17 Jun after | 30.4 °C | 8 % | 37 km/h | 0.0 mm | Extreme 51 |
| 18 Jun after | 33.7 °C | 5 % | 40 km/h | 0.0 mm | Extreme 61 |
| 19 Jun after | 38.5 °C | 8 % | 40 km/h | 0.0 mm | Extreme 62 |
| 20 Jun after | 38.4 °C | 6 % | 44 km/h | 0.0 mm | Extreme 65 |
| 21 Jun after | 34.1 °C | 12 % | 38 km/h | 0.0 mm | Extreme 60 |
| 22 Jun after | 34.2 °C | 12 % | 45 km/h | 0.0 mm | Extreme 63 |
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 · 71Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 3,044 haCellar YavapaiJuly 2019 · 6 days · 25 km away
- 4,549 haConstellation YavapaiAugust 2020 · 4 days · 26 km away
- 3,711 haHorse YavapaiOctober 2020 · 7 days · 26 km away
- 3,711 haCrooks YavapaiApril 2022 · 13 days · 30 km away
- 1,187 haWaterman YavapaiJuly 2024 · 1 day · 30 km away
- 2,256 haTussock YavapaiMay 2021 · 5 days · 31 km away
Frequently asked questions
- How long did the Tenderfoot fire last?
- According to the heat detections seen by satellite inside the perimeter, it burned from 8 June 2016 to 12 June 2016 (5 days). The perimeter dates it from 8 June 2016 to 8 June 2016.
- How much area did it burn?
- The official perimeter published by United States agencies (MTBS / NIFC) is 1,765 hectares (17.6 km²). Other tallies, such as daily incident reports, may give slightly different figures.
- Which counties burned?
- The fire only entered Yavapai (1,755 ha, 0.1 %).
- What was the weather like?
- During the fire the temperature reached 31.1 °C, humidity dropped to 12 % and gusts hit 53 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.