Skip to content
worldfires
US · United States · →

Coco Fire, July 2016 Coconino

Out · last measured on 22 Jul 2016

The fire started on 22 July 2016 in Coconino, United States, and satellites saw it burning for 1 day. United States agencies (MTBS / NIFC) mapped an official burnt perimeter of 906 hectares, spread across a single county.

It is the 237th largest in Arizona since 2016 (of 380 with a page). Number 290 in United States in 2016, of 475.

Burnt area
906ha
official perimeter (MTBS / NIFC)
Duration
1day
22 Jul 2016 – 22 Jul 2016
Municipalities hit
1
counties
Started on
22 Jul
2016
Heat detections
27
in a single hotspot: 20 MW
Danger at start
45
Very high · FWI index

Where it burned

HOTSPOTS BY DAY 22 Jul22 Jul

The weather it burned in

34°high
56km/h · peak gust
6%lowest humidity

It had gone one day without rain (1 mm or more) when it started. Rain came after the fire: 7.1 mm on 1 Aug.

This area had burned before

No earlier perimeters overlap this fire since 2016, when the satellite record begins.

What happened to each town

  1. Coconino where it started
    922 ha reached on 26 Jul
    0.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)
22 Jul 32.0 °C 11 % 35 km/h 0.2 mm Very high 45
23 Jul after 34.2 °C 9 % 37 km/h 0.0 mm Very high 44
24 Jul after 32.7 °C 10 % 52 km/h 0.1 mm Very high 50
25 Jul after 31.2 °C 12 % 44 km/h 0.0 mm Very high 47
26 Jul after 31.5 °C 12 % 26 km/h 0.0 mm Very high 44
27 Jul after 34.5 °C 7 % 25 km/h 0.0 mm Very high 45
28 Jul after 34.2 °C 6 % 30 km/h 0.0 mm Very high 49
29 Jul after 32.9 °C 12 % 56 km/h 0.9 mm Very high 49
30 Jul after 30.4 °C 18 % 54 km/h 2.1 mm High 26
31 Jul after 27.5 °C 30 % 44 km/h 0.4 mm High 29
1 Aug after 27.4 °C 28 % 33 km/h 7.1 mm Very low 4

Before and after, from space

Drag the line to compare the same ground before the fire and after it.

Before · 15 Jul 2016
After · 29 Jul 2016

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 · 27Every satellite heat detection, one by one, with time, satellite, power and coordinates.
⬇ Download CSV Times in UTC. Each detection is a 375 m pixel: a large fire yields hundreds per pass.
Date and timeSatelliteFRP (MW)LatLon

Other fires nearby

All fires in United States ›

Frequently asked questions

How long did the Coco fire last?
It burned between 22 July 2016 and 22 July 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 906 hectares (9.1 km²). Other tallies, such as daily incident reports, may give slightly different figures.
Which counties burned?
The fire only entered Coconino (922 ha, 0.0 %).
What was the weather like?
During the fire the temperature reached 34.5 °C, humidity dropped to 6 % and gusts hit 56 km/h. The fire danger index (FWI) reached 50, class Very high.
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

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
What do you think is wrong?

We will only use your email to reply about this report. Privacy. This is not an emergency service: if there is a fire now, call 911.

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.