Soldier Fire, July 2016 Graham
The fire started on 27 July 2016 in Graham, United States, and satellites saw it burning for 1 day. United States agencies (MTBS / NIFC) mapped an official burnt perimeter of 1,344 hectares, spread across a single county.
It is the 174th largest in Arizona since 2016 (of 380 with a page). Number 209 in United States in 2016, of 475.
The power measured by the satellite is low (26.6 MW in the strongest hotspot), more typical of grass or stubble burning, or a slow surface fire, than of a large crown fire.
- Burnt area
- 1,344ha
- official perimeter (MTBS / NIFC)
- Duration
- 1day
- 27 Jul 2016 – 27 Jul 2016
- Municipalities hit
- 1
- counties
- Started on
- 27 Jul
- 2016
- Heat detections
- 19
- in a single hotspot: 27 MW
- Danger at start
- 29
- High · FWI index
- Energy released
- 135MW
- 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 2 days without rain (1 mm or more) when it started. Rain came after the fire: 4.8 mm on 31 Jul.
This area had burned before
No earlier perimeters overlap this fire since 2016, when the satellite record begins.
What happened to each town
-
Graham where it started1,347 ha reached on 28 Jul0.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) |
|---|---|---|---|---|---|
| 27 Jul | 33.8 °C | 23 % | 35 km/h | 1.7 mm | High 29 |
| 28 Jul after | 34.9 °C | 22 % | 39 km/h | 1.1 mm | High 30 |
| 29 Jul after | 34.7 °C | 14 % | 28 km/h | 0.0 mm | Very high 41 |
| 30 Jul after | 32.3 °C | 23 % | 33 km/h | 0.0 mm | Extreme 50 |
| 31 Jul after | 32.4 °C | 27 % | 38 km/h | 4.8 mm | Moderate 12 |
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 · 19Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
Frequently asked questions
- How long did the Soldier fire last?
- It burned between 27 July 2016 and 27 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,344 hectares (13.4 km²). Other tallies, such as daily incident reports, may give slightly different figures.
- Which counties burned?
- The fire only entered Graham (1,347 ha, 0.1 %).
- What was the weather like?
- During the fire the temperature reached 34.9 °C, humidity dropped to 14 % and gusts hit 39 km/h. The fire danger index (FWI) reached 50, 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.