Wildfires of 2005

West Omak Lake Fire

2005WashingtonWildfire

The West Omak Lake Fire burned 11,330 acres in Washington, in 2005. It was discovered on July 12, 2005, and contained on July 17, 2005. The cause was recorded as equipment and vehicle use.

Size
11,330 acres
Discovered
July 12, 2005
Contained
July 17, 2005
Cause
Human

Map

The burned area boundary MTBS mapped from Landsat imagery, 11,441 acres. Point of origin as reported, 48.242, -119.391.

The record

Reported final size
11,330 acres
Burned area mapped by MTBS
11,441 acres
Area inside the final perimeter
11,258 acres
Discovered
July 12, 2005, 1:07 p.m. local time
Contained
July 17, 2005, 6:00 p.m. local time
Cause
Human, Equipment and vehicle use
State
Washington
Land ownership at origin
Bureau of Indian Affairs
Reporting unit
Colville Agency
Agency
Forest Service
Unit
WACOA
Incident type
Wildfire
MTBS fire identifier
WA4820111938520050712
MTBS assessment
Initial
Fire occurrence record
W-512423
Perimeter map method
Other
Perimeter records
2 on file for this fire; the largest is shown
Note on the perimeter
Washington State DNR data

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: 7, from July 12, 2005 to July 17, 2005. 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
18
Most personnel assigned
747 on July 15, 2005
Most aircraft assigned
4
Cost reported by the teams
$2 million, in 2005 dollars
Primary fuel model reported
Timber (Grass and Understory)

Acres reported by day

The largest rise between two days’ reports was 7,200 acres, on July 13, 2005.

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
Jul 12, 2005800
Jul 13, 20058,000+7,200
Jul 14, 200511,300+3,300
Jul 15, 200511,3000
Jul 16, 200511,3000
Jul 17, 200511,3000

Other large fires in Washington in 200512

FireAcresStartCause
School Fire52,000Aug 5, 2005Human
Walker Canyon Fire25,000Jun 25, 2005
Mcclane Fire6,851Aug 9, 2005Human
Wood Gulch Fire5,400Jul 23, 2005
Wall Lake Fire5,178Jul 27, 2005Human
Juniper Canyon Fire5,000Jun 22, 2005
Weather Station Fire4,917Jul 5, 2005
Second Hud Fire4,274Jul 4, 2005Human
I 82 Fire2,200Aug 19, 2005Human
Badger Road Fire2,000Jul 25, 2005
Harker Canyon Fire1,566Aug 10, 2005Human
Burnt Bread Fire1,246Aug 6, 2005Human

Every fire of 2005 Washington 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.