How long did the Shady fire last?

It burned between 10 July 2019 and 10 July 2019: 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 2,694 hectares (26.9 km²). Other tallies, such as daily incident reports, may give slightly different figures.

Which counties burned?

The fire only entered Custer (2,709 ha, 0.2 %).

What was the weather like?

During the fire the temperature reached 24.9 °C, humidity dropped to 14 % and gusts hit 64 km/h. The fire danger index (FWI) reached 31, class 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.

US · United States · 2019-07-10 → 2019-07-10

Shady Fire, July 2019 Custer

Out · last detection 11 Jul 2019, 21:38 UTC

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

It is the 110th largest in Idaho since 2016 (of 379 with a page). Number 102 in United States in 2019, of 367.

Burnt area: 2,694ha; official perimeter (MTBS / NIFC)
Duration: 1day; 10 Jul 2019 – 10 Jul 2019
Municipalities hit: 1; counties
Started on: 10 Jul; 2019
Heat detections: 352; in a single hotspot: 511 MW
Danger at start: 22; High · FWI index
Energy released: 451MW; sum of detected power

HOTSPOTS BY DAY 10 Jul10 Jul

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

25°high

64km/h · peak gust

14%lowest humidity

It had gone 5 days without rain (1 mm or more) when it started. Rain came after the fire: 1.1 mm on 7 Aug.

This area had burned before

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

What happened to each town

Custer where it started

2,709 ha reached on 11 Jul

0.2 %

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)
10 Jul	23.1 °C	25 %	52 km/h	0.4 mm	High 22
11 Jul after	24.2 °C	23 %	61 km/h	0.0 mm	High 26
12 Jul after	24.6 °C	23 %	51 km/h	0.0 mm	High 25
13 Jul after	24.1 °C	24 %	56 km/h	1.8 mm	Moderate 12
14 Jul after	21.8 °C	23 %	55 km/h	1.4 mm	Moderate 15
15 Jul after	17.9 °C	36 %	49 km/h	4.5 mm	Very low 3
16 Jul after	17.4 °C	39 %	49 km/h	3.5 mm	Very low 2
17 Jul after	18.3 °C	31 %	63 km/h	0.0 mm	Low 9
18 Jul after	17.8 °C	34 %	64 km/h	0.0 mm	Moderate 14
19 Jul after	18.0 °C	16 %	50 km/h	0.0 mm	Moderate 19
20 Jul after	20.1 °C	21 %	45 km/h	0.0 mm	Moderate 20
21 Jul after	24.9 °C	18 %	35 km/h	0.0 mm	High 23
22 Jul after	24.4 °C	22 %	47 km/h	2.2 mm	Low 8
23 Jul after	24.1 °C	21 %	39 km/h	0.8 mm	Moderate 15
24 Jul after	21.2 °C	15 %	58 km/h	0.0 mm	High 27
25 Jul after	24.3 °C	14 %	42 km/h	0.0 mm	High 27
26 Jul after	21.9 °C	20 %	34 km/h	1.5 mm	Moderate 13
27 Jul after	23.1 °C	18 %	59 km/h	0.3 mm	High 27
28 Jul after	23.4 °C	17 %	58 km/h	0.0 mm	High 31
29 Jul after	22.8 °C	26 %	41 km/h	3.5 mm	Very low 5
30 Jul after	22.6 °C	26 %	45 km/h	0.0 mm	Moderate 16
31 Jul after	24.7 °C	19 %	49 km/h	0.9 mm	Moderate 21
1 Aug after	24.4 °C	22 %	40 km/h	0.7 mm	High 22
2 Aug after	23.6 °C	29 %	40 km/h	5.9 mm	Very low 3
3 Aug after	25.2 °C	16 %	47 km/h	0.0 mm	Moderate 18
4 Aug after	25.1 °C	17 %	32 km/h	0.0 mm	High 23
5 Aug after	25.5 °C	16 %	42 km/h	0.0 mm	High 27
6 Aug after	22.2 °C	22 %	44 km/h	0.2 mm	High 27
7 Aug after	22.4 °C	23 %	46 km/h	1.1 mm	Moderate 18

Before and after, from space

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

↔

Before · 3 Jul 2019

After · 17 Jul 2019

Before After

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 · 352Every 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 time	Satellite	FRP (MW)	Lat	Lon

Other fires nearby

All fires in United States ›

Frequently asked questions

How long did the Shady fire last?: It burned between 10 July 2019 and 10 July 2019: 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 2,694 hectares (26.9 km²). Other tallies, such as daily incident reports, may give slightly different figures.
Which counties burned?: The fire only entered Custer (2,709 ha, 0.2 %).
What was the weather like?: During the fire the temperature reached 24.9 °C, humidity dropped to 14 % and gusts hit 64 km/h. The fire danger index (FWI) reached 31, class 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

NASA FIRMS ↗
NIFC · Fire maps ↗

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?

Dates or duration Place or towns Burned area Name It was not a wildfire Same fire as another page Something else

What really happened?

Your connection to the fire (optional) Email (optional)

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.

Where it burned