Skip to content
worldfires
US · United States · →

Box Canyon Fire, July 2016 Summit

Out · last detection 29 Jul 2016, 21:31 UTC

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

It is the 75th largest in Utah since 2016 (of 165 with a page). Number 171 in United States in 2016, of 475.

Burnt area
1,813ha
official perimeter (MTBS / NIFC)
Duration
1day
28 Jul 2016 – 28 Jul 2016
Municipalities hit
1
counties
Started on
28 Jul
2016
Heat detections
232
in a single hotspot: 698 MW
Danger at start
49
Very high · FWI index
Energy released
4.1GW
sum of detected power

Where it burned

HOTSPOTS BY DAY 28 Jul28 Jul

How it evolved, day by day

29

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

The weather it burned in

27°high
68km/h · peak gust
9%lowest humidity

It had gone 25 days without rain (1 mm or more) when it started. Rain came after the fire: 3.8 mm on 14 Sept.

This area had burned before

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

What happened to each town

  1. Summit where it started
    1,809 ha reached on 29 Jul
    0.4 %

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)
28 Jul 26.7 °C 12 % 55 km/h 0.0 mm Very high 49
29 Jul after 26.9 °C 14 % 56 km/h 0.0 mm Very high 48
30 Jul after 24.3 °C 23 % 53 km/h 1.5 mm High 22
31 Jul after 24.1 °C 27 % 46 km/h 0.3 mm High 28
1 Aug after 24.8 °C 17 % 38 km/h 0.1 mm High 34
2 Aug after 26.4 °C 13 % 33 km/h 0.0 mm High 36
3 Aug after 22.8 °C 21 % 45 km/h 3.0 mm Low 11
4 Aug after 25.6 °C 12 % 34 km/h 0.0 mm High 28
5 Aug after 23.3 °C 19 % 43 km/h 0.3 mm High 31
6 Aug after 21.3 °C 26 % 43 km/h 0.3 mm High 32
7 Aug after 21.1 °C 37 % 48 km/h 3.0 mm Low 7
8 Aug after 24.3 °C 12 % 56 km/h 0.0 mm High 30
9 Aug after 23.9 °C 11 % 62 km/h 0.0 mm Very high 43
10 Aug after 21.8 °C 18 % 58 km/h 0.2 mm Very high 41
11 Aug after 18.9 °C 22 % 56 km/h 0.7 mm High 29
12 Aug after 21.3 °C 15 % 52 km/h 0.0 mm High 34
13 Aug after 22.5 °C 15 % 40 km/h 0.0 mm High 33
14 Aug after 24.9 °C 11 % 42 km/h 0.0 mm Very high 38
15 Aug after 21.7 °C 16 % 40 km/h 1.2 mm Moderate 20
16 Aug after 23.5 °C 19 % 36 km/h 2.6 mm Low 8
17 Aug after 22.3 °C 21 % 40 km/h 1.8 mm Low 11
18 Aug after 21.1 °C 22 % 37 km/h 1.8 mm Low 9
19 Aug after 22.0 °C 18 % 57 km/h 0.0 mm High 29
20 Aug after 22.4 °C 16 % 38 km/h 0.0 mm High 30
21 Aug after 23.5 °C 15 % 37 km/h 0.0 mm High 32
22 Aug after 22.4 °C 18 % 47 km/h 1.5 mm Moderate 21
23 Aug after 20.1 °C 22 % 52 km/h 0.2 mm High 28
24 Aug after 18.1 °C 14 % 59 km/h 0.0 mm High 37
25 Aug after 17.7 °C 18 % 45 km/h 0.5 mm High 30
26 Aug after 18.4 °C 25 % 50 km/h 2.7 mm Low 8
27 Aug after 19.5 °C 20 % 40 km/h 0.2 mm Moderate 19
28 Aug after 20.8 °C 18 % 32 km/h 0.0 mm High 25
29 Aug after 23.7 °C 15 % 21 km/h 0.0 mm High 27
30 Aug after 24.5 °C 15 % 24 km/h 0.0 mm High 31
31 Aug after 24.5 °C 13 % 36 km/h 0.0 mm High 35
1 Sept after 21.8 °C 27 % 48 km/h 2.3 mm Low 10
2 Sept after 21.0 °C 22 % 56 km/h 0.1 mm High 26
3 Sept after 18.1 °C 28 % 63 km/h 0.7 mm High 25
4 Sept after 17.7 °C 24 % 68 km/h 0.3 mm High 31
5 Sept after 14.9 °C 28 % 44 km/h 2.2 mm Low 7
6 Sept after 18.1 °C 17 % 56 km/h 0.0 mm High 23
7 Sept after 18.5 °C 18 % 48 km/h 0.0 mm High 28
8 Sept after 18.3 °C 22 % 58 km/h 0.0 mm High 32
9 Sept after 17.4 °C 9 % 42 km/h 0.0 mm High 33
10 Sept after 20.6 °C 10 % 43 km/h 0.0 mm High 37
11 Sept after 21.5 °C 15 % 62 km/h 0.2 mm Very high 43
12 Sept after 18.9 °C 13 % 58 km/h 0.5 mm Very high 42
13 Sept after 16.9 °C 21 % 55 km/h 6.6 mm Very low 5
14 Sept after 12.7 °C 31 % 56 km/h 3.8 mm Very low 3

Before and after, from space

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

Before · 21 Jul 2016
After · 4 Aug 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 · 232Every 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 Box Canyon fire last?
It burned between 28 July 2016 and 28 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,813 hectares (18.1 km²). Other tallies, such as daily incident reports, may give slightly different figures.
Which counties burned?
The fire only entered Summit (1,809 ha, 0.4 %).
What was the weather like?
During the fire the temperature reached 26.9 °C, humidity dropped to 9 % and gusts hit 68 km/h. The fire danger index (FWI) reached 49, 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.