Jack Fire, May 2016 Coconino
The fire started on 29 May 2016 in Coconino, United States, and satellites saw it burning for 1 day. United States agencies (MTBS / NIFC) mapped an official burnt perimeter of 14,530 hectares, spread across a single county.
It is the 16th largest in Arizona since 2016 (of 380 with a page). Number 25 in United States in 2016, of 475.
- Burnt area
- 14,530ha
- official perimeter (MTBS / NIFC)
- Duration
- 1day
- 29 May 2016 – 29 May 2016
- Municipalities hit
- 1
- counties
- Started on
- 29 May
- 2016
- Heat detections
- 1,005
- in a single hotspot: 71 MW
- Danger at start
- 30
- High · FWI index
- Energy released
- 71MW
- 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 10 days without rain (1 mm or more) when it started. Rain came after the fire: 4.3 mm on 28 Jun.
This area had burned before
No earlier perimeters overlap this fire since 2016, when the satellite record begins.
What happened to each town
-
Coconino where it started14,401 ha reached on 29 May0.3 %
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) |
|---|---|---|---|---|---|
| 29 May | 23.7 °C | 10 % | 49 km/h | 0.0 mm | High 30 |
| 30 May after | 22.2 °C | 11 % | 32 km/h | 0.0 mm | High 28 |
| 31 May after | 24.1 °C | 8 % | 25 km/h | 0.0 mm | High 27 |
| 1 Jun after | 26.6 °C | 9 % | 34 km/h | 0.0 mm | High 31 |
| 2 Jun after | 29.2 °C | 6 % | 35 km/h | 0.0 mm | High 34 |
| 3 Jun after | 30.7 °C | 5 % | 36 km/h | 0.0 mm | High 38 |
| 4 Jun after | 31.2 °C | 8 % | 34 km/h | 0.0 mm | Very high 41 |
| 5 Jun after | 31.8 °C | 7 % | 48 km/h | 0.0 mm | Very high 49 |
| 6 Jun after | 30.5 °C | 7 % | 61 km/h | 0.0 mm | Extreme 59 |
| 7 Jun after | 28.7 °C | 7 % | 44 km/h | 0.0 mm | Very high 48 |
| 8 Jun after | 30.2 °C | 12 % | 41 km/h | 0.3 mm | Very high 49 |
| 9 Jun after | 29.5 °C | 14 % | 48 km/h | 0.1 mm | Extreme 52 |
| 10 Jun after | 29.4 °C | 13 % | 58 km/h | 0.6 mm | Very high 43 |
| 11 Jun after | 24.7 °C | 26 % | 50 km/h | 1.5 mm | High 24 |
| 12 Jun after | 25.1 °C | 16 % | 64 km/h | 0.0 mm | Very high 49 |
| 13 Jun after | 23.7 °C | 12 % | 66 km/h | 0.7 mm | Very high 50 |
| 14 Jun after | 25.7 °C | 10 % | 49 km/h | 0.0 mm | Very high 47 |
| 15 Jun after | 24.9 °C | 8 % | 67 km/h | 0.0 mm | Extreme 62 |
| 16 Jun after | 25.9 °C | 11 % | 57 km/h | 0.0 mm | Extreme 56 |
| 17 Jun after | 28.5 °C | 7 % | 45 km/h | 0.0 mm | Extreme 52 |
| 18 Jun after | 32.5 °C | 4 % | 41 km/h | 0.0 mm | Extreme 56 |
| 19 Jun after | 34.7 °C | 7 % | 34 km/h | 0.0 mm | Extreme 51 |
| 20 Jun after | 35.5 °C | 6 % | 46 km/h | 0.0 mm | Extreme 60 |
| 21 Jun after | 32.4 °C | 12 % | 43 km/h | 0.0 mm | Extreme 58 |
| 22 Jun after | 32.0 °C | 13 % | 48 km/h | 0.0 mm | Extreme 59 |
| 23 Jun after | 30.9 °C | 13 % | 50 km/h | 0.0 mm | Extreme 65 |
| 24 Jun after | 30.0 °C | 13 % | 50 km/h | 0.4 mm | Extreme 59 |
| 25 Jun after | 30.1 °C | 14 % | 32 km/h | 0.0 mm | Extreme 54 |
| 26 Jun after | 32.4 °C | 10 % | 34 km/h | 0.0 mm | Extreme 53 |
| 27 Jun after | 28.7 °C | 16 % | 47 km/h | 0.3 mm | Extreme 57 |
| 28 Jun after | 29.0 °C | 27 % | 36 km/h | 4.3 mm | Low 10 |
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 · 1,005Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 4,040 haWolf CoconinoApril 2024 · 1 day · 16 km away
- 5,712 haSnake Ridge CoconinoMay 2017 · 1 day · 17 km away
- 4,299 haStill CoconinoSeptember 2023 · 1 day · 19 km away
- 6,503 haTinder CoconinoApril 2018 · 1 day · 23 km away
- 6,801 haColdwater CoconinoMay 2019 · 1 day · 26 km away
- 4,155 haWilbur CoconinoMay 2023 · 1 day · 26 km away
Frequently asked questions
- How long did the Jack fire last?
- It burned between 29 May 2016 and 29 May 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 14,530 hectares (145.3 km²). Other tallies, such as daily incident reports, may give slightly different figures.
- Which counties burned?
- The fire only entered Coconino (14,401 ha, 0.3 %).
- What was the weather like?
- During the fire the temperature reached 34.7 °C, humidity dropped to 4 % and gusts hit 67 km/h. The fire danger index (FWI) reached 62, 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.