Skip to content
worldfires
US · United States · →

Limbo Fire, July 2017 Pershing

Out · last measured on 9 Jul 2017

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

It is the 172th largest in Nevada since 2016 (of 237 with a page). Number 444 in United States in 2017, of 619.

We have the official perimeter (MTBS / NIFC) for this fire, but the VIIRS sensors did not capture it in enough detail: no day-by-day evolution, but the split by county is there.

Burnt area
772ha
official perimeter (MTBS / NIFC)
Duration
1day
9 Jul 2017 – 9 Jul 2017
Municipalities hit
1
counties
Started on
9 Jul
2017
Danger at start
65
Extreme · FWI index

Where it burned

The weather it burned in

38°high
60km/h · peak gust
4%lowest humidity

It had gone 26 days without rain (1 mm or more) when it started. Rain came after the fire: 1.9 mm on 6 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. Pershing where it started
    767 ha
    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)
9 Jul 36.8 °C 6 % 43 km/h 0.0 mm Extreme 65
10 Jul after 35.3 °C 5 % 47 km/h 0.0 mm Extreme 65
11 Jul after 34.1 °C 8 % 41 km/h 0.0 mm Extreme 60
12 Jul after 34.8 °C 8 % 39 km/h 0.0 mm Extreme 57
13 Jul after 35.6 °C 9 % 40 km/h 0.0 mm Extreme 57
14 Jul after 36.9 °C 9 % 35 km/h 0.0 mm Extreme 63
15 Jul after 35.9 °C 7 % 39 km/h 0.0 mm Extreme 62
16 Jul after 35.1 °C 8 % 36 km/h 0.0 mm Extreme 61
17 Jul after 34.2 °C 10 % 51 km/h 0.0 mm Very extreme 70
18 Jul after 33.5 °C 5 % 50 km/h 0.0 mm Extreme 67
19 Jul after 32.6 °C 6 % 38 km/h 0.0 mm Extreme 58
20 Jul after 32.2 °C 8 % 34 km/h 0.0 mm Extreme 59
21 Jul after 33.3 °C 6 % 31 km/h 0.0 mm Extreme 56
22 Jul after 36.0 °C 9 % 37 km/h 0.0 mm Extreme 57
23 Jul after 37.8 °C 6 % 43 km/h 0.0 mm Extreme 61
24 Jul after 34.2 °C 12 % 43 km/h 0.1 mm Extreme 60
25 Jul after 32.9 °C 11 % 41 km/h 0.7 mm Very high 48
26 Jul after 31.4 °C 15 % 34 km/h 0.5 mm Extreme 52
27 Jul after 32.4 °C 14 % 22 km/h 0.0 mm Very high 41
28 Jul after 35.6 °C 9 % 32 km/h 0.0 mm Extreme 50
29 Jul after 33.7 °C 9 % 32 km/h 0.0 mm Extreme 56
30 Jul after 36.0 °C 9 % 20 km/h 0.0 mm Very high 46
31 Jul after 37.3 °C 9 % 28 km/h 0.0 mm Very high 49
1 Aug after 38.4 °C 6 % 19 km/h 0.0 mm Extreme 52
2 Aug after 38.1 °C 6 % 27 km/h 0.0 mm Extreme 64
3 Aug after 38.1 °C 6 % 28 km/h 0.0 mm Extreme 61
4 Aug after 36.2 °C 10 % 46 km/h 0.0 mm Extreme 63
5 Aug after 31.6 °C 16 % 46 km/h 0.0 mm Extreme 55
6 Aug after 29.6 °C 23 % 42 km/h 0.7 mm High 36
7 Aug after 31.0 °C 16 % 38 km/h 0.0 mm Very high 46
8 Aug after 32.2 °C 15 % 22 km/h 0.0 mm Very high 43
9 Aug after 31.2 °C 17 % 26 km/h 0.4 mm Very high 40
10 Aug after 32.0 °C 16 % 34 km/h 0.0 mm Very high 42
11 Aug after 33.3 °C 9 % 35 km/h 0.0 mm Extreme 53
12 Aug after 32.7 °C 13 % 49 km/h 0.0 mm Extreme 59
13 Aug after 32.1 °C 10 % 49 km/h 0.0 mm Extreme 56
14 Aug after 27.3 °C 21 % 37 km/h 0.1 mm Very high 42
15 Aug after 30.6 °C 15 % 23 km/h 0.0 mm Very high 39
16 Aug after 31.7 °C 15 % 28 km/h 0.0 mm Very high 43
17 Aug after 33.0 °C 8 % 29 km/h 0.0 mm Very high 47
18 Aug after 35.0 °C 7 % 26 km/h 0.0 mm Very high 46
19 Aug after 32.5 °C 9 % 31 km/h 0.0 mm Extreme 52
20 Aug after 32.8 °C 12 % 36 km/h 0.0 mm Extreme 54
21 Aug after 33.4 °C 10 % 30 km/h 0.0 mm Extreme 50
22 Aug after 30.2 °C 17 % 32 km/h 0.3 mm Very high 45
23 Aug after 31.5 °C 18 % 42 km/h 0.0 mm Very high 47
24 Aug after 33.2 °C 13 % 40 km/h 0.0 mm Very high 50
25 Aug after 34.5 °C 12 % 30 km/h 0.0 mm Very high 47
26 Aug after 36.6 °C 5 % 26 km/h 0.0 mm Very high 49
27 Aug after 36.8 °C 7 % 22 km/h 0.0 mm Extreme 52
28 Aug after 37.1 °C 6 % 36 km/h 0.0 mm Extreme 62
29 Aug after 36.4 °C 10 % 60 km/h 0.3 mm Extreme 66
30 Aug after 33.5 °C 9 % 48 km/h 0.4 mm Extreme 62
31 Aug after 31.7 °C 5 % 19 km/h 0.0 mm Extreme 51
1 Sept after 34.4 °C 6 % 27 km/h 0.0 mm Extreme 52
2 Sept after 37.0 °C 4 % 20 km/h 0.0 mm Very high 48
3 Sept after 36.9 °C 5 % 23 km/h 0.0 mm Extreme 56
4 Sept after 36.0 °C 7 % 27 km/h 0.0 mm Extreme 56
5 Sept after 34.9 °C 9 % 25 km/h 0.0 mm Extreme 59
6 Sept after 31.9 °C 19 % 46 km/h 1.9 mm High 28

Before and after, from space

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

Before · 2 Jul 2017
After · 16 Jul 2017

If the day is cloudy, change the date: each satellite passes once a day. In false colour the burnt ground looks brown or red.

Other fires nearby

All fires in United States ›

Frequently asked questions

How long did the Limbo fire last?
It burned between 9 July 2017 and 9 July 2017: 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 772 hectares (7.7 km²). Other tallies, such as daily incident reports, may give slightly different figures.
Which counties burned?
The fire only entered Pershing (767 ha, 0.0 %).
What was the weather like?
During the fire the temperature reached 38.4 °C, humidity dropped to 4 % and gusts hit 60 km/h. The fire danger index (FWI) reached 70, class Very 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.