Wildfires of 2009

Lily Lake Fire

2009Beaverhead County, MontanaWildfire

The Lily Lake Fire burned 2,120 acres in Beaverhead County, Montana, in 2009. It was discovered on August 13, 2009, and contained on October 9, 2009. The cause was recorded as natural.

Size
2,120 acres
Discovered
August 13, 2009
Contained
October 9, 2009
Cause
Natural

Map

The burned area boundary MTBS mapped from Landsat imagery, 2,019 acres. Point of origin as reported, 45.624, -113.317.

The record

Reported final size
2,120 acres
Burned area mapped by MTBS
2,019 acres
Area inside the final perimeter
1,744 acres
Discovered
August 13, 2009, 6:45 p.m. local time
Contained
October 9, 2009, 11:43 a.m. local time
Cause
Natural
State
Montana
County
Beaverhead County
Land ownership at origin
Forest Service
Reporting unit
Beaverhead-Deerlodge National Forest
Agency
Forest Service
Unit
MTNRC
Incident type
Wildfire
MTBS fire identifier
MT4562511330420090813
MTBS assessment
Extended
Fire occurrence record
FS-1483421
Perimeter records
2 on file for this fire; the largest is shown

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: 11, from August 28, 2009 to October 16, 2009. 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.

Injuries
1
Most personnel assigned
45 on September 26, 2009
Most aircraft assigned
2
Cost reported by the teams
$377,867, in 2009 dollars
Cause on the reports
Lightning or other natural
Primary fuel model reported
Timber (Litter and Understory)
Suppression strategy reported
Confine

Acres reported by day

The largest rise between two days’ reports was 399 acres, on September 29, 2009.

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 28, 2009180
Aug 29, 2009220+40
Sep 12, 2009430
Sep 14, 2009670
Sep 25, 2009900
Sep 26, 20091,160+260
Sep 27, 20091,308+148
Sep 28, 20091,701+393
Sep 29, 20092,100+399
Oct 1, 20092,120
Oct 16, 20092,120

Other large fires in Montana in 20098

FireAcresStartCause
Meissner Fire14,490Jan 31, 2009Human
Kootenai Creek Fire6,990Jul 12, 2009Natural
Table Mountain Fire5,280Sep 13, 2009Natural
Indian Trail Fire4,409Sep 9, 2009Human
Gird End Fire2,514Sep 9, 2009Natural
Lawrence Mountain Fire2,400Sep 2, 2009Natural
Bielenburg Fire1,950Jul 12, 2009Natural
Gabe Creek Fire1,932Jul 30, 2009Natural

Every fire of 2009 Montana fire history

Nearby

Sources

Perimeters from the National Interagency Fire Center’s Interagency Fire Perimeter History, compiled from the Forest Service, BLM, BIA, Fish and Wildlife Service, National Park Service, the Alaska Interagency Fire Center and CAL FIRE. 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.