Wildfires of 2000

Rankin Creek Fire

2000IdahoWildfire

The Rankin Creek Fire burned 6,710 acres in Idaho, in 2000. It was discovered on August 11, 2000, and contained on September 2, 2000. The cause was recorded as natural.

Size
6,710 acres
Discovered
August 11, 2000
Contained
September 2, 2000
Cause
Natural

Map

The burned area boundary MTBS mapped from Landsat imagery, 2,091 acres. Point of origin as reported, 44.372, -114.730.

The record

Reported final size
6,710 acres
Burned area mapped by MTBS
2,091 acres
Discovered
August 11, 2000, 7:30 a.m. local time
Contained
September 2, 2000, 9:00 a.m. local time
Cause
Natural
State
Idaho
Land ownership at origin
Forest Service
Reporting unit
Salmon-Challis National Forest
Agency
Forest Service
Incident type
Wildfire
MTBS fire identifier
ID4434311470620000811
MTBS assessment
Extended
Fire occurrence record
FS-358796

The three sizes are three measurements: the size the agency reported when the fire was out, the burned area MTBS drew from satellite imagery before and after, and the GIS area inside the final perimeter, unburned islands included. They rarely agree exactly.

From the incident teams’ reports

The status summaries (ICS-209 forms) the incident teams filed: 23, from August 11, 2000 to September 2, 2000. These are the teams’ own estimates, written while the incident was running, and personnel is totaled from the resources each report lists. A fact the reports leave blank is not shown, and a zero on the form is treated as blank.

Most structures threatened at once
33
Most personnel assigned
702 on August 18, 2000
Most aircraft assigned
3
Cost reported by the teams
$3.9 million, in 2000 dollars
Cause on the reports
Lightning or other natural

Acres reported by day

The largest rise between two days’ reports was 3,100 acres, on August 18, 2000.

Acres at the last status summary of each day. Days with no report are not shown.
Reported acres by day, as a table
DayAcresChange from the day before
Aug 11, 2000400
Aug 12, 20001,400+1,000
Aug 13, 20001,472+72
Aug 14, 20002,116+644
Aug 15, 20002,120+4
Aug 16, 20002,200+80
Aug 17, 20002,600+400
Aug 18, 20005,700+3,100
Aug 19, 20005,7000
Aug 20, 20006,500+800
Aug 21, 20006,700+200
Aug 22, 20006,7000
Aug 23, 20006,710+10
Aug 24, 20006,7100
Aug 25, 20006,7100
Aug 26, 20006,7100
Aug 27, 20006,7100
Aug 28, 20006,7100
Aug 29, 20006,7100
Aug 30, 20006,7100
Aug 31, 20006,7100
Sep 1, 20006,7100
Sep 2, 20006,7100

Other large fires in Idaho in 200012

FireAcresStartCause
Clear Creek Divide Complex (Clear Creek) Fire172,135Jul 10, 2000Natural
Diamond Complex (Diamond Peak) Fire149,772Jul 31, 2000Natural
Flossie Complex74,998Jul 31, 2000Natural
Coffee Point Fire68,952Jul 26, 2000Natural
Burgdorf Junction Fire64,631Jul 14, 2000Natural
Maloney Creek Fire64,510Aug 11, 2000Natural
Salmon Challis Wilderness Complex (Little Pistol) Fire63,760Aug 11, 2000Natural
Aperejo Fire55,279
Coffee Point North Fire36,041Jul 26, 2000
Grass Fire35,613Aug 5, 2000Natural
Trail Creek Fire35,238Aug 15, 2000Natural
Oregon Trail Fire31,316Aug 7, 2000Human

Every fire of 2000 Idaho fire history

Nearby

Sources

Burned areas and ignition dates from Monitoring Trends in Burn Severity (MTBS), a program of the US Geological Survey and the USDA Forest Service. Fire reports from Short, Karen C. 2022, Spatial wildfire occurrence data for the United States, 1992-2020 [FPA_FOD_20221014], 6th Edition, Forest Service Research Data Archive, doi.org/10.2737/RDS-2013-0009.6. Records before 2014 were joined by this site: a fire report to the burned area its MTBS identifier names, a perimeter to the burned area it lies in when the names or the sizes agree. Incident figures from ICS-209-PLUS: St. Denis, Lise A., Karen C. Short, Kathryn McConnell, Maxwell C. Cook, Nathan P. Mietkiewicz, Mollie Buckland and Jennifer K. Balch, 2023, All-hazards dataset mined from the US National Incident Management System 1999-2020, Scientific Data 10, 112, doi.org/10.1038/s41597-023-01955-0; data on figshare, doi.org/10.6084/m9.figshare.19858927.v3, licensed CC BY 4.0. This site matched each incident to the fire by the dataset’s own links where it has them, and otherwise by name, start date, state and size, and left out figures too large to be possible for a fire of its size.