Trail Fire, October 2020 Yavapai
The fire started on 25 October 2020 in Yavapai, United States, and satellites saw it burning for 1 day. United States agencies (MTBS / NIFC) mapped an official burnt perimeter of 687 hectares, spread across a single county.
It is the 288th largest in Arizona since 2016 (of 380 with a page). Number 338 in United States in 2020, of 441.
The power measured by the satellite is low (4.7 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
- 687ha
- official perimeter (MTBS / NIFC)
- Duration
- 1day
- 25 Oct 2020 – 25 Oct 2020
- Municipalities hit
- 1
- counties
- Started on
- 25 Oct
- 2020
- Heat detections
- 14
- in a single hotspot: 5 MW
- Danger at start
- 48
- Very high · FWI index
- Energy released
- 36MW
- 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 47 days without rain (1 mm or more) when it started.
This area had burned before
No earlier perimeters overlap this fire since 2016, when the satellite record begins.
What happened to each town
-
Yavapai where it started683 ha reached on 25 Oct0.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) |
|---|---|---|---|---|---|
| 25 Oct | 23.9 °C | 28 % | 71 km/h | 0.4 mm | Very high 48 |
| 26 Oct after | 16.2 °C | 22 % | 66 km/h | 0.5 mm | Very high 43 |
| 27 Oct after | 16.2 °C | 16 % | 58 km/h | 0.0 mm | Very high 39 |
| 28 Oct after | 21.2 °C | 16 % | 25 km/h | 0.0 mm | High 32 |
| 29 Oct after | 25.1 °C | 15 % | 29 km/h | 0.0 mm | High 37 |
| 30 Oct after | 26.1 °C | 14 % | 27 km/h | 0.0 mm | High 36 |
| 31 Oct after | 27.3 °C | 11 % | 23 km/h | 0.0 mm | Very high 40 |
| 1 Nov after | 29.5 °C | 11 % | 37 km/h | 0.0 mm | Very high 46 |
| 2 Nov after | 29.2 °C | 12 % | 33 km/h | 0.0 mm | Very high 44 |
| 3 Nov after | 28.0 °C | 16 % | 38 km/h | 0.6 mm | Very high 39 |
| 4 Nov after | 29.6 °C | 13 % | 23 km/h | 0.0 mm | Very high 41 |
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 · 14Every satellite heat detection, one by one, with time, satellite, power and coordinates.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 9,205 haSkeleton YavapaiAugust 2024 · 1 day · 8 km away
- 16,087 haBrooklyn YavapaiJuly 2017 · 1 day · 10 km away
- 6,629 haTiger YavapaiJune 2021 · 1 day · 10 km away
- 11,405 haGoodwin YavapaiJune 2017 · 1 day · 33 km away
- 5,405 haSears MaricopaSeptember 2020 · 1 day · 40 km away
- 4,549 haConstellation YavapaiAugust 2020 · 1 day · 40 km away
Frequently asked questions
- How long did the Trail fire last?
- It burned between 25 October 2020 and 25 October 2020: 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 687 hectares (6.9 km²). Other tallies, such as daily incident reports, may give slightly different figures.
- Which counties burned?
- The fire only entered Yavapai (683 ha, 0.0 %).
- What was the weather like?
- During the fire the temperature reached 23.9 °C, humidity dropped to 28 % and gusts hit 71 km/h. The fire danger index (FWI) reached 48, 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
- 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.