Skip to content
worldfires
US · United States · →

Baca Fire, July 2016 Yavapai

Out · last detection 8 Jul 2016, 21:23 UTC

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

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

Burnt area
1,651ha
official perimeter (MTBS / NIFC)
Duration
1day
7 Jul 2016 – 7 Jul 2016
Municipalities hit
1
counties
Started on
7 Jul
2016
Heat detections
90
in a single hotspot: 59 MW
Danger at start
51
Extreme · FWI index
Energy released
113MW
sum of detected power

Where it burned

8 Jul 2016
HOTSPOTS BY DAY 7 Jul7 Jul

How it evolved, day by day

78

Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.

The weather it burned in

33°high
59km/h · peak gust
7%lowest humidity

It had gone 4 days without rain (1 mm or more) when it started. Rain came after the fire: 1.0 mm on 19 Jul.

This area had burned before

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

What happened to each town

  1. Yavapai where it started
    1,655 ha reached on 7 Jul
    0.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)
7 Jul 29.7 °C 16 % 55 km/h 0.0 mm Extreme 51
8 Jul after 31.2 °C 13 % 51 km/h 0.0 mm Extreme 50
9 Jul after 31.6 °C 15 % 56 km/h 0.0 mm Extreme 54
10 Jul after 31.5 °C 9 % 59 km/h 0.0 mm Extreme 59
11 Jul after 30.8 °C 8 % 49 km/h 0.0 mm Extreme 53
12 Jul after 31.2 °C 9 % 52 km/h 0.0 mm Extreme 57
13 Jul after 32.3 °C 7 % 45 km/h 0.0 mm Extreme 54
14 Jul after 33.3 °C 9 % 46 km/h 0.0 mm Extreme 56
15 Jul after 33.4 °C 10 % 50 km/h 0.0 mm Extreme 60
16 Jul after 31.4 °C 15 % 56 km/h 0.0 mm Extreme 61
17 Jul after 30.5 °C 18 % 58 km/h 0.0 mm Extreme 60
18 Jul after 30.2 °C 17 % 45 km/h 0.1 mm Extreme 53
19 Jul after 29.8 °C 23 % 38 km/h 1.0 mm High 33

Before and after, from space

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

Before · 30 Jun 2016
After · 14 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 · 90Every 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 Baca fire last?
It burned between 7 July 2016 and 7 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 1,651 hectares (16.5 km²). Other tallies, such as daily incident reports, may give slightly different figures.
Which counties burned?
The fire only entered Yavapai (1,655 ha, 0.1 %).
What was the weather like?
During the fire the temperature reached 33.4 °C, humidity dropped to 7 % and gusts hit 59 km/h. The fire danger index (FWI) reached 61, 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

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.