You should: Sign up > Write articles > tell people about your articles > Monetize them > Earn money  > learn/do/earn more

2020 Western United States wildfire season

From Wikiafripedia, the free afripedia (encyclopedia)
Jump to navigation Jump to search

Template:Current wildfire

2020 Western United States wildfire season
GOES17 geocolor Western US 2020-09-09 1100AM.jpg
September 9 satellite image of the wildfires burning in California and Oregon
LocationWestern United States
Statistics[1]
Total fires100+
Total areaOver 6,609,880.1 acres (2,674,923.6 ha)[2]
Cost>$1.7 billion (2020 USD)[2]
Date(s)July 24, 2020 (2020-07-24) – ongoing (ongoing)
Buildings
destroyed
7,500+[2]
Fatalities37[3][4][5]
Non-fatal injuriesUnknown

In 2020, the Western United States experienced a series of major wildfires. Severe August thunderstorms ignited numerous wildfires across California, Oregon, and Washington, followed in early September by additional ignitions across the West Coast. Fanned by strong, gusty winds and fueled by hot, dry terrains, many of the fires exploded and coalesced into record-breaking, fire-cloud-forming[6] megafires,[7] burning more than 6.6 million acres (2.7 million hectares) of land,[2] mobilizing tens of thousands of firefighters, razing thousands of buildings, and killing at least 37 people.[3][8] Climate change and poor forest management practices contributed to the severity of the wildfires.[9]

Background[edit source | edit]

For further information, see Disturbance (ecology)

Fire, environment, and cultural shift[edit source | edit]

Fire regimes of United States vegetation

Save for areas along the northern and southern extents of the Pacific coast, North America tends to be wetter in the east and drier in the west, ideal conditions for the lightning and wind of storms to spark and spread large-scale, seasonal wildfires,[10][11] alongside the development of human societies practicing cultural burns. Various Indigenous controlled fire practices[11] have been curtailed and outlawed since European colonization of the Americas, such as through the Weeks Act, which brought paradigmatic changes in ecosystem priorities and management.[10][better source needed][12]

Land was protected from fire, and vegetation accumulated near settlements, increasing the risk of explosive, smoky conflagrations. Karuk and other aboriginal fire-keepers have passed down knowledge of vegetation clearing practices. In the last few decades, these cultural memories has been acknowledged by the United States Forest Service, NOAA,[13] and other agencies in American colonial nations.[12][14]

While non-human-caused ignitions are typical of fire-prone ecosystems, higher human population and settlement extending into the wildland–urban interface has brought with it increased accidental and intentional sparking of fires.[citation needed] With the advent of the worldwide, widespread increased burning of fossil fuels the climate has changed, and the globe has heated by around 1 degree C.

Record hemispheric heat[edit source | edit]

The Northern Hemisphere January–August land and ocean surface temperature tied with 2016 as the warmest such period since global records began in 1880. The Southern Hemisphere had its third-warmest such period (tied with 2017) on record, behind 2016 and 2019.[15]

— United States National Oceanic and Atmospheric Administration, September 14, 2020
Year-to-date (through September 8, 2020) animation of extent and intensity of drought in the United States maintained by the University of Nebraska-Lincoln[16]

Record dry weather struck the Western United States in late 2019, extending to January and February 2020, prompting initial concerns from state governments and the press.[17]

California was the first to call out a warning.[18] On March 22, a state of emergency was declared by California Governor Gavin Newsom due to a mass die-off of trees throughout the state, potentially increasing the risk of wildfire. Oregon officially declared the start of their wildfire season that same month.[18][19] Despite light rain in late March and April, severe drought conditions persisted, and were predicted to last late into the year, due to a delayed wet season.[20] After fires began in Washington in April, several more fires occurred throughout the West Coast, prompting burn ban restrictions in the Washington and Oregon, come July.[21]

Year-to-date wildfire figures[edit source | edit]

United States agencies stationed at the National Interagency Fire Center in Idaho maintain a "National Large Incident Year-to-Date Report" on wildfires, delineating 10 sub-national areas, aggregating the regional and national totals of burn size, fire suppression cost, and razed structure count, among other data. As of September 18, "Coordination Centers" of each geography report the following:[2]

Note: Check primary sources for up-to-date statistics.

National Interagency Fire Center Geographic Area Coordination Centers
National Interagency Fire Center Geographic Area Coordination Centers
Coordination Center Acres Hectares Suppression Costs Structures Destroyed
Alaska Interagency 171,045.7 69,219.7 $14,837,241.00 8
Northwest Area 1,894,689.2 766,753.5 $241,771,756.78 4,256
Northern California Area 3,357,844.0 1,358,871.3 $697,836,173.93 3,702
Southern California Area 965,999.5 390,926.1 $459,489,882.00 1,434
Northern Rockies 326,491.4 132,126.4 $59,274,372.00 222
Great Basin 769,517.2 311,412.6 $180,322,529.00 174
Southwest Area 951,609.6 385,102.7 $183,563,964.96 48
Rocky Mountain Area 480,662.8 194,517.3 $156,241,217.34 73
Eastern Area 10,071.8 4,075.9 $491,898.58 18
Southern Area 2,665,951.3 1,078,872.2 $14,605,789.11 310
Totals[lower-alpha 1] 11,593,882.5 4,691,877.8 $2,008,434,824.70 10,245

Timeline of events[edit source | edit]

Initial ignitions and weather conditions[edit source | edit]

The CZU Lightning Complex fires were sparked by lightning in mid-August[22]

April saw the beginning of wildfires in the west coast, as Washington experienced two fires: the Stanwood Bryant Fire in Snohomish County (70 acres (28 ha)) and the Porter Creek Fire in Whatcom County (80 acres (32 ha)).[23] The Oregon Department of Forestry declared fire season beginning July 5, 2020, signaling the end of unregulated debris burning outdoors, a major cause of wildfires.[24]

Between July 16 and 30, the Washington State Department of Natural Resources (DNR) and many county governments – including Mason, Thurston, King, Pierce and Whatcom Counties – issued fire safety burn bans due to elevated risk of uncontrolled fires.[25] In late July, a brush fire in Chelan County, the Colockum Fire, burned at least 3,337 acres (1,350 ha) and caused homes to be evacuated.[26] A fire on the Colville Reservation near Nespelem called the Greenhouse Fire burned at least 5,146 acres (2,083 ha) and caused the evacuation of the Colville Tribal Corrections Facility and other structures.[27][28]

Between August 14 and 16, Northern California was subjected to record-breaking warm temperatures,[29] due to anomalously strong high pressure over the region. Early on August 15, the National Weather Service for San Francisco issued a Fire Weather Watch[30] highlighting the risk of wildfire starts due to the combination of lightning risk due to moist, unstable air aloft, dry fuels, and hot temperatures near the surface. Later that day, the Fire Weather Watch was upgraded to a Red Flag Warning,[31] noting the risk of abundant lightning already apparent as the storms moved toward the region from the south.

In mid-August, the remnants of Tropical Storm Fausto interacted with the jet stream, resulting in a large plume of moisture moving northward towards the West Coast of the U.S., triggering a massive siege of lightning storms in Northern California, and setting the conditions for wildfires elsewhere.[32] Due to abnormal wind patterns, this plume streamed from up to 1,000 miles (1,600 km) off the coast of the Baja Peninsula into Northern California. This moisture then interacted with a high-pressure ridge situated over Nevada that was bringing a long-track heat wave to much of California and the West.[33] These colliding weather systems then created excessive atmospheric instability that generated massive thunderstorms throughout much of Northern and Central California. Such thunderstorms are rare for California, but were more typical of Midwest garden-variety storms, with one location near Travis Air Force Base going from around 80 °F (27 °C) to 100 °F (38 °C) in nearly 1–2 hours.[34] Additionally, much of these storms were only accompanied with dry lightning and produced little to no rain, making conditions very favorable for wildfires to spark and spread rapidly.[35]

As a result of the fires, on August 19, Governors Kate Brown and Jay Inslee declared a state of emergency for Oregon and Washington respectively.[36][37]

Growth of fires[edit source | edit]

Six of the twenty largest wildfires in California history were part of the 2020 wildfire season. Five of the new wildfires ranking in the top 10 were all a part of the August 2020 lightning fires.

By August 20, the Palmer Fire near Oroville, Washington – which started August 18 – had reached 13,000 acres (5,300 ha) and forced evacuation of up to 85 homes.[38][39] The largest of the fires in the Olympics reached 2.4 acres (0.97 ha) by August 20.[40]

View of the Bobcat Fire from a kitchen window in Monrovia, California

The Evans Canyon Fire, a few miles north of Naches, began around August 31 and expanded to tens of thousands of acres, shut down Washington State Route 821 in the Yakima River Canyon, burned several homes and caused hundreds of families to evacuate, and caused unhealthy air quality in Yakima County.[41] By September 6, it had burned almost 76,000 acres (31,000 ha).[42]

The August 2020 lightning fires include three of the largest wildfires in the recorded history of California: the SCU Lightning Complex, the August Complex, and the LNU Lightning Complex. On September 10, 2020, the August Complex became the single-largest wildfire in the recorded history of California, reaching a total area burned of 471,185 acres (1,907 km2). Then, on September 11, it merged with the Elkhorn Fire, another massive wildfire of 255,039 acres (1,032 km2), turning the August Complex into a monster wildfire of 746,607 acres (3,021 km2).[43]

In early September 2020, a combination of a record-breaking heat wave, and Diablo and Santa Ana winds sparked more fires and explosively grew active fires, with the August Complex surpassing the 2018 Mendocino Complex to become California's largest recorded wildfire.[43] The North Complex increased in size as the winds fanned it westward, threatening the city of Oroville, and triggering mass evacuations.[44] During the first week in September, the 2020 fire season set a new California record for the most area burned in a year at 2,000,000 acres (810,000 ha).[45] As of September 13, 3,200,000 acres (1,300,000 ha) had burned in the state.[46]

On September 7, a "historic fire event" with high winds resulted in 80 fires and nearly 300,000 acres (120,000 ha) burned in a day. Malden, in the Palouse Country of Eastern Washington, was mostly destroyed by one of the fires.[47] By the evening of September 8, the Cold Springs Canyon and adjacent Pearl Hill Fires had burned over 337,000 acres (136,000 ha) and neither was more than 10% contained.[48] Smoke blanketed the Seattle area on September 8 and caused unhealthy air conditions throughout the Puget Sound region, and affected Southwest British Columbia.[49][50]

The cities of Phoenix and Talent in Oregon were substantially destroyed by the Almeda Drive Fire. State-wide, at least 23 people have been killed.[51][52] On September 11, authorities said they were preparing for a mass fatality incident.[53] As of September 11, 600 homes and 100 commercial buildings have been destroyed by the Almeda Drive Fire.[54] Officials stated that the Almeda Drive Fire was human-caused.[54] On September 11, a man was arrested for arson, for allegedly starting a fire that destroyed multiple homes in Phoenix and merged with the Almeda Drive Fire.[55] A separate criminal investigation into the origin point of the Almeda Drive Fire in Ashland is ongoing.[55]

Around September 11–12, wildfires were starting to encroach upon the Clackamas County suburbs of Portland, Oregon, especially the fast-moving Riverside Fire which had already jumped the nearby community of Estacada, but shifting wind directions kept the fire away from the main Portland area.[56]

Through much of September, at least 8 large wildfires, each of 100,000 acres (400 km2) or more, were burning in Washington and Oregon, with 3 in Washington and 5 in Oregon. This was unprecedented for those two states, which combined only saw a total of 26 large fires from 1997 to 2019.[57] On September 22, 10 large fires, each of at least 100,000 acres, were burning across California, including 5 of the 10 largest wildfires in the state's history.[58]

Evacuations[edit source | edit]

The Government of California's video about COVID-19 protocols in place at wildfire evacuation centers

The first evacuations began on September 4, when almost 200 people were airlifted out of the Sierra National Forest due to the rapidly exploding Creek Fire. Then on September 9, most of the southern area of the city of Medford, Oregon was forced to evacuate and almost all of the 80,000 residents living in the city were told to be ready if necessary[59] because of the uncontained Almeda Drive Fire, which was fast encroaching on their city.[60][61] As of September 11, about 40,000 people in Oregon had been instructed to evacuate, and 500,000, accounting for about 10% of the state's population, had received instructions to prepare for evacuation, being under a Level 1, 2, or 3 fire evacuation alert.[62][63]

List of wildfires[edit source | edit]

For further information, see 2020 California wildfires#List of wildfires

The following is a list of fires that burned more than 1,000 acres (400 ha), or produced significant structural damage or casualties.

Name County Acres Start date Containment date Notes Ref
Interstate 5 Kings County, California 2,060 May 3 May 7 [64]
Range San Luis Obispo County, California 5,000 May 27 May 28 [65]
Scorpion Santa Barbara County, California 1,395 May 31 June 1 [66]
Quail Solano County, California 1,837 June 6 June 10 3 structures destroyed [67][68]
Wood San Diego County, California 11,000 June 8 June 12 Burned on Camp Pendleton [69]
India San Diego County, California 1,100 June 8 June 14 Burned on Camp Pendleton [70]
Soda San Luis Obispo County, California 1,672 June 10 June 11 2 structures destroyed [71][72]
Grant Sacramento County, California 5,042 June 12 June 17 1 structure damaged [73]
Walker Calaveras County, California 1,455 June 16 June 20 2 structures destroyed [74]
River San Luis Obispo County, California 15 June 22 June 23 2 structures destroyed, 9 damaged [75]
Grade Tulare County, California 1,050 June 22 June 26 [76]
Pass Merced County, California 2,192 June 28 June 30 [77]
Bena Kern County, California 2,900 July 1 July 3 [78]
Crews Santa Clara County, California 5,513 July 5 July 13 1 structure destroyed; 1 damaged; 1 injury. Resulted in evacuations of rural Gilroy. [79]
Soledad Los Angeles County, California 1,525 July 5 July 15 1 injury [80]
Mineral Fresno County, California 29,667 July 13 July 26 7 structures destroyed [81][82]
Coyote San Benito County, California 1,508 July 15 July 18 [83]
Hog Lassen County, California 9,564 July 18 August 8 2 structures destroyed [84]
Gold Lassen County, California 22,634 July 20 August 8 13 structures destroyed; 5 structures damaged; 2 firefighters injured in burnover [85]
July Complex 2020 Modoc County, Siskiyou County, California 83,261 July 22 August 7 1 structure destroyed; 3 outbuildings destroyed [86]
Blue Jay Mariposa County, Tuolumne County, California 4,598 July 24 50% contained as of September 24 Lightning-sparked [87]
Red Salmon Complex Humboldt County, Siskiyou County, Trinity County, California 110,113 July 26 31% contained as of September 25 Originally started as both the Red and Salmon fire (both started by lightning strikes), but have since merged into one fire [88][89]
Chikamin Chelan County, Washington 1,685 July 31 September 24 [90]
Apple Riverside County, California 33,424 July 31 95% contained as of September 16 4 structures destroyed; 8 outbuildings destroyed; 4 injuries [91]
Pond San Luis Obispo County, California 1,962 August 1 August 8 1 structure destroyed; 1 damaged; 13 outbuildings destroyed[92] [93]
North Lassen County, California 6,882 August 2 August 10 6,882 acres in total, of which approximately 4,105 acres burned in Washoe County, Nevada [94]
Stagecoach Kern County, California 7,760 August 3 August 16 23 structures destroyed; 4 damaged; 25 outbuildings destroyed; 2 damaged;[95] 1 firefighter fatality[96] [97]
Neals Hill Harney County, Oregon 3,391 August 5 August 20 Caused by lightning [98][99]
Wolf Mariposa County, Tuolumne County, California 1,077 August 11 35% contained as of September 24 Lightning-sparked [100]
Lake Los Angeles County, California 31,089 August 12 95% contained as of September 19 Lightning-sparked, 33 structures destroyed; 6 damaged; 21 outbuildings destroyed; 2 injuries [101][102]
Ranch 2 Los Angeles County, California 4,237 August 13 96% contained as of September 18 Lightning-sparked [103]
Loyalton Lassen County, Plumas County, Sierra County, California 47,029 August 15 September 14 Lightning-sparked, Caused National Weather Service to issue first ever Fire Tornado Warning; 5 homes, 6 outbuildings destroyed [104][105]
Hills Fresno County, California 2,121 August 15 August 24 Lightning-sparked; 1 fatality [106]
River Monterey County, California 48,088 August 16 September 4 Lightning-sparked; 30 structures destroyed; 13 structures damaged; 4 injuries [107]
Dome San Bernardino County, California 43,273 August 16 September 14 Lightning-sparked, Burned in the Mojave National Preserve [108]
Beach Mono County, California 3,780 August 16 August 28 Lightning-sparked [109]
SCU Lightning Complex Santa Clara County, Alameda County, Contra Costa County, San Joaquin County, Merced County, Stanislaus County, California 396,624 August 16 98% contained, as of September 19 Deer Zone, Marsh, Canyon Zone and other surrounding fires combined into one multi-fire incident by CalFire; all believed to have been sparked by an intense and widespread lightning storm; 222 structures destroyed; 26 structures damaged; 6 injuries. It is the third-largest fire complex in California history. [110]
August Complex Glenn County, Mendocino County, Lake County, Tehama County, Trinity County, California 870,200 August 16 43% contained, as of September 26 Lightning strikes started 37 fires, several of which grew to large sizes, especially the Doe Fire; 1 firefighter injury; 1 firefighter fatality. It became the largest fire complex in California history and combined with the Elkhorn Fire on September 10. [111][112]
CZU Lightning Complex San Mateo County, Santa Cruz County, California 86,509 August 16 September 22 Several lightning-sparked fires burning close together across San Mateo and Santa Cruz Counties; 1,490 structures destroyed; 140 structures damaged; 1 injury; 1 fatality. [113]
Rattlesnake Tulare County, California 4,070 August 16 0% contained, as of September 10 Lightning sparked a slow-growing fire in inaccessible terrain. [114]
Lionshead Jefferson County, Oregon 204,340 August 16 28% contained, as of September 25. Merged into the Beachie Creek Fire and became the Santiam Fire on September 8. [115]
Beachie Creek Linn County, Oregon 192,838 August 16 52% contained, as of September 25. Merged with the Lionshead Fire and became the Santiam Fire on September 8. [116]
Santiam Clackamas County, Jefferson County, Linn County, Marion County, Wasco County, Oregon 401,787 September 8 28+% contained, as of September 25 Includes the Lionshead, Beachie Creek, and P-515 Fires, which merged [117][118][119]
Downey Creek Douglas County, Oregon 2,570 August 16 0% contained, as of September 13 [120]
Frog Crook County, Oregon 4,020 August 16 September 1 Caused by lightning [121]
Green Ridge Deschutes County, Oregon 4,338 August 16 September 1 Caused by lightning [122]
Indian Creek Malheur County, Oregon 48,128 August 16 September 16 Caused by lightning [123]
White River Wasco County, Oregon 17,383 August 17 85% contained, as of September 21 [124]
Jones Nevada County, California 705 August 17 August 28 Lightning sparked, 21 structures destroyed, 3 structures damaged, 7 injuries [125]
Sheep Plumas County, Lassen County, California 29,570 August 17 September 9 Lightning-sparked, 26 structures destroyed, 1 injury [126][127]
LNU Lightning Complex Colusa County, Lake County, Napa County, Sonoma County, Solano County, Yolo County, California 363,220 August 17 98% contained, as of September 19 Multi-fire incident that includes the Hennessey Fire (305,651 acres), the Walbridge Fire (55,209 acres), and the Meyers Fire (2,360 acres) sparked by lightning; 1,491 structures destroyed; 232 structures damaged; 5 injuries; 5 fatalities. It is the fourth-largest fire complex in California history. [128]
Holser Ventura County, California 3,000 August 17 September 6 [129]
Butte/Tehama/Glenn Lightning Complex (Butte Zone) Butte County, California 19,609 August 17 97% contained as of September 19 Lightning sparked 34 fires throughout Butte County; 14 structures destroyed; 1 structure damaged; 1 injury [130]
North Complex Plumas County, Butte County, Yuba County, California 304,881 August 17 78% contained, as of September 24 Lightning strikes, includes the Claremont Fire and the Bear Fire; 2,000 structures destroyed; 10 fatalities; 13 injuries; It is the sixth-largest fire complex in California history. [131][132]
Salt Calaveras County, California 1,789 August 18 August 24 Lightning-sparked [133]
W-5 Cold Springs Lassen County, Modoc County, California 84,817 August 18 September 14 Lightning-sparked. Fire spread eastward into Washoe County, Nevada. [134]
Carmel Monterey County, California 6,905 August 18 September 4 Lightning-sparked, 73 structures destroyed; 7 structures damaged [135]
Dolan Monterey County, California 128,417 August 18 57% contained, as of September 26 Cause not officially determined; however, a suspect was charged with arson in connection to the fire[136] [137]
Woodward Marin County, California 4,929 August 18 97% contained, as of September 19 Lightning-sparked [138]
SQF Complex Tulare County, California 148,850 August 19 36% contained, as of September 25 Lightning-sparked, contains the Castle Fire and the Shotgun Fire [139]
Laurel Wheeler County, Oregon 1,257 August 19 September 14 [140]
Moc Tuolumne County, California 2,857 August 20 August 30 Lightning-sparked [141]
Slink Mono County, California 26,759 August 29 86% contained, as of September 24 Lightning-sparked [142]
Evans Canyon Kittitas County, Washington 75,817 August 31 90% contained, as of September 12 [143]
Creek Fresno County, Madera County, California 292,172 September 4 36% contained, as of September 25 855 structures destroyed, 71 structures damaged; 12 injuries; 1 fatality [144][145][146]
El Dorado Riverside County, San Bernardino County, California 22,616 September 5 83% contained, as of September 26 Sparked by a pyrotechnic device at a gender reveal party. 10 structures destroyed, 6 structures damaged [147][148]
Valley San Diego County, California 16,390 September 5 September 24 51 structures destroyed, 11 structures damaged, 2 injuries [149]
Bobcat Los Angeles County, California 114,004 September 6 61% contained, as of September 26 Unknown cause [150]
Cold Springs Okanogan County, Washington 189,923 September 6 95% contained, as of September 20 1 fatality [151][152]
P-515 Jefferson County, Oregon 4,609 September 7 95% contained, as of September 11. Merged into the Lionshead Fire on September 8. [118]
Oak Mendocino County, California 1,100 September 7 September 14 Unknown cause, 25 structures destroyed, 20 structures damaged [153]
Slater/Devil Siskiyou County, Del Norte County, California, Josephine County, Oregon 153,850 September 7 25% contained, as of September 25 2 fatalities, 1 structure destroyed [154][155]
Two Four Two Klamath County, Oregon 14,473 September 7 89% contained, as of September 22 [156]
Brattain Lake County, Oregon 50,951 September 7 90% contained, as of September 24 [157]
Holiday Farm Lane County, Oregon 173,094 September 7 45% contained, as of September 26 1 fatality [158]
Echo Mountain Complex Lincoln County, Oregon 2,552 September 7 75% contained, as of September 20 293 structures destroyed, 22 structures damaged [159]
Babb-Maiden/Manning Spokane County, Washington 18,254 September 7 90% contained, as of September 24 [160]
Whitney Lincoln County, Washington 127,430 September 7 95% contained, as of September 16 [161]
Inchelium Complex Ferry County, Washington 19,399 September 7 85% contained, as of September 23 [162]
Pearl Hill Douglas County, Washington 223,730 September 7 94% contained, as of September 16 [163]
Apple Acres Chelan County, Washington 5,500 September 7 99% contained, as of September 16 [164]
Fork El Dorado County, California 1,667 September 8 70% contained, as of September 22 [165]
South Obenchain Jackson County, Oregon 32,671 September 8 95% contained, as of September 26 [166]
Riverside Clackamas County, Oregon 138,029 September 8 34% contained, as of September 24 [167]
Big Hollow Skamania County, Washington 24,995 September 8 40% contained, as of September 26 [168]
Almeda Drive Jackson County, Oregon 3,200 September 8 September 15[169] 2457+ Structures destroyed, 3 fatalities [170][171][54][55]
Chehalem Mountain- Bald Peak Washington County, Oregon 2,000 September 8 September 14 [172][173][174][175][176]
Thielsen Douglas County, Oregon 9,971 September 9 69% contained, as of September 26 [177]
Willow Yuba County, California 1,311 September 9 September 14 41 structures destroyed; 10 structures damaged [178]
Archie Creek Douglas County, Oregon 131,642 September 9 64% contained, as of September 26 [179]
Bullfrog Fresno County, California 1,185 September 9 45% contained, as of September 26 [180]
Fox Trinity County, California 2,188 September 14 83% contained as of September 26 [181]
Snow Riverside County, California 6,254 September 17 90% contained as of September 26 [182]

Causes[edit source | edit]

Fire policy[edit source | edit]

Prior to development, California fires regularly burned significantly more acreage than has been seen in recent history. Wildfires have been aggressively suppressed in recent years, resulting in a buildup of fuel, increasing the risk of large uncontrollable fires. There is broad scientific consensus that there should be more controlled burning of forest in California in order to reduce fire risk.[183][184][185] Controlled burning is hampered by wildfire litigation models that present wildfires in court cases as the result of careless ignition events while discounting underlying forest conditions.[186][187] A 2020 ProPublica investigation blamed the culture of Cal Fire, greed on the part of fire suppression contractors, and risk aversion on the part of the U.S. Forest Service from preventing appropriate controlled burns from taking place.[188]

Climate change[edit source | edit]

Secretary of California's Natural Resources Agency Wade Crowfoot urges President Trump to not ignore the science on climate change to which Trump responds "I don't think science knows, actually"[189][190] and "It'll start getting cooler. You just watch."[191]

Climate change has led to increased heat waves and the risk of drought in California, creating the conditions for more frequent and severe wildfires.[192][193] It has been observed that since the early 1970s, warm‐season days in California warmed by ca. 1.4 °C. This significantly increases the atmospheric vapor pressure deficit, the difference between the actual and a maximum moisture content for a certain temperature. These trends are consistent with human-induced trends that were simulated by climate models. Summer forest‐fire area reacts to the vapor pressure deficit exponentially, i.e., warming has grown increasingly impactful.[193]

David Romps, director of the Berkeley Atmospheric Sciences Center summarizes the situation as follows: "To cut to the chase: Were the heat wave and the lightning strikes and the dryness of the vegetation affected by global warming? Absolutely yes. Were they made significantly hotter, more numerous, and drier because of global warming? Yes, likely yes, and yes."[194] Similarly, Friederike Otto, acting director of the University of Oxford Environmental Change Institute states, "There is absolutely no doubt that the extremely high temperatures are higher than they would have been without human-induced climate change. A huge body of attribution literature demonstrates now that climate change is an absolute game-changer when it comes to heat waves, and California won't be the exception."[195] Susan Clark, director of the Sustainability Initiative at the University at Buffalo, states, "This is climate change. This increased intensity and frequency of temperatures and heat waves are part of the projections for the future. [...] There is going to be more morbidity and mortality [from heat.] There are going to be more extremes."[195]

Obstacles to fire control[edit source | edit]

Rumors about political extremist involvement[edit source | edit]

Rumors were spread on social media that far-left antifa rioters involved in the arson and vandalism accompanying the nearby George Floyd protests in Portland, Oregon, were deliberately setting fires, and were preparing to loot property that was being evacuated. Some residents refused to evacuate based on the rumors, choosing to defend their homes from the invasion. Authorities told residents to ignore the rumors and abandon their property.[196] QAnon followers participated in spreading the rumors, with one claim that six antifa activists had been arrested for setting fires specifically amplified by "Q", the anonymous person or people behind QAnon.[197][198] Days earlier, U.S. President Donald Trump and U.S. Attorney General Bill Barr had amplified social media rumors of preceding months that planes and buses full of antifa activists were preparing to invade communities, funded by George Soros.[199][200][201][202][203][204]

Rumors also circulated that members of far-right groups such as the Proud Boys had started some of the fires. However, authorities labelled the claims as false, saying that people needed to question claims they found on social media.[205]

There have been a number of arrests for arson surrounding the wildfires, but there is no indication that the incidents were connected to a mass arson campaign, according to some law enforcement officers.[206][207][208]

COVID-19 pandemic[edit source | edit]

The COVID-19 pandemic brought new challenges for firefighters fighting wildfires due to measures intended to reduce the transmission of the disease. The California Department of Forestry and Fire Protection (CAL Fire) implemented new protocols such as wearing face masks and maintaining social distancing while resting, and reducing the number of occupants in the pickup trucks used to transport firefighters.[209]

California relies heavily on inmate firefighters, with incarcerated people making up nearly a quarter of CAL FIRE's total workforce in 2018–2019.[210] Coronavirus measures within the prison system, such as early release and quarantine policies, have reduced the number of inmate firefighters available, necessitating the hiring of additional seasonal firefighters.[211]

Impacts[edit source | edit]

Fire[edit source | edit]

In Oregon, wildfires throughout the whole year, with most occurring in September, charred a record of 1,000,000 acres (4,000 km2), destroying a total of 4,800 structures, including 1,145 homes, and killing 9 people.[212] In Washington, 2020 wildfires burned 800,000 acres (3,200 km2), with 418 structures, including 195 homes, burned. In California, about 3,300,000 acres (13,000 km2) burned from wildfires in 2020, the highest burned acreage ever recorded in a fire season. About 2,100,000 acres (8,500 km2) burned in the August lighting wildfires and 1,000,000 acres (4,000 km2) more in September.[213] 4,200 structures were destroyed the whole year in California, and 25 people were killed.[214]

Smoke and air pollution[edit source | edit]

The fires resulted in worsened air pollution across much of the western U.S. and Canada, from Los Angeles to British Columbia. Alaska Airlines suspended its flights from Portland, Oregon, and Spokane, Washington, due to poor air quality.[215] Some cities in Oregon recorded air quality readings of over 500 on the AQI scale, while readings of over 200 were recorded in major cities.[216] Smoke from the fires were carried to the East Coast, causing yellowed skies but having little impact on air quality.[217]

The heavy smoke had resulted in several smoke-related incidents. In California, for example, a San Francisco resident was hiking through Yosemite National Park on September 5 when suddenly the sky turned a dark, ugly color and the temperature dropped greatly, reminiscent of a thunderstorm. Ash and smoke started falling, and this erratic weather was caused by the nearby Creek Fire.[218] In another incident, an Oakland A's player was at a game at the Seattle Mariners' stadium, when suddenly in the middle of the game he started gasping for air.

Red skies have appeared over many cities over the West Coast, due to smoke from the wildfires blocking lighter colors, created from light infraction.[219]

Ecological effects[edit source | edit]

Habitat destruction[edit source | edit]

The unique sagebrush scrub habitat of the Columbia Basin in Washington was heavily affected by the fires, devastating populations of the endemic Columbia Basin pygmy rabbit and endangered, isolated populations of greater sage-grouse and Columbian sharp-tailed grouse. About half of the pygmy rabbit population and over 30-70% of the grouse population may have been lost to the fires, reversing decades of conservation work. Aside from climate change, the spread of the fires may have been assisted by the intrusion of invasive cheatgrass into the habitats. Fires in old-growth forests of Oregon may negatively affect the populations of the endangered northern spotted owl and pine marten, and the resulting ash from the fires may be washed into streams and threaten endangered salmon.[220][221] Climate change also reduces the likelihood of forests re-establishing themselves after a fire.[222]

Possible bird mortality[edit source | edit]

Since August 20, a mass mortality event of migratory birds has been reported in the Southwestern United States, especially New Mexico, with hundreds of thousands to potentially millions of birds being affected. The majority of deceased birds are insectivorous ones including warblers, tyrant-flycatchers, and swallows, and are likely migrants from outside the region, as resident birds have not been affected. Of these, violet-green swallows represented the vast majority of deceased birds, at over 85%.[223] Although the exact causes are as of yet unknown and under review, it has been theorized that the birds originated from areas affected by the fires and had their migration patterns altered by both the fires and a major cold front, forcing them into drought-stricken desert areas where they were unable to find food and eventually died from exhaustion. Smoke inhalation from the fires may have also played a part.[224][225] However, an analysis later in the month by the American Birding Association found the cold front to be the most likely cause of the deaths, with the fires playing a minimal impact, if any.[226]

See also[edit source | edit]

Other wildfires[edit source | edit]

General[edit source | edit]

Notes[edit source | edit]

  1. Year-to-date totals as of September 18, 2020

References[edit source | edit]

  1. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  2. 2.0 2.1 2.2 2.3 2.4 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  3. 3.0 3.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  4. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  5. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  6. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  7. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  8. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  9. Is climate change worsening California fires, or is it poor forest management? Both, experts say Archived September 14, 2020, at the Wayback Machine. San Francisco Chronicle. Retrieved: September 14, 2020.
  10. 10.0 10.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  11. 11.0 11.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  12. 12.0 12.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  13. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  14. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  15. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  16. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
    • Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
    • Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
    • Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  17. 18.0 18.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  18. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  19. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
    • Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
    • Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
    • Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
    • Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
    • Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
    • Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
    • Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  20. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  21. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  22. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  23. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  24. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  25. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  26. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
    • Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
    • Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
    • Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  27. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  28. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
    • Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
    • Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  29. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  30. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  31. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  32. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  33. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  34. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  35. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  36. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  37. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  38. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  39. 43.0 43.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  40. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  41. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  42. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  43. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  44. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  45. Template:Cite twitter
  46. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  47. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  48. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  49. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  50. 54.0 54.1 54.2 Benda, David. "Southern Oregon wildfires update: 700-plus homes, businesses destroyed as officials' investigate fire's cause Archived September 12, 2020, at the Wayback Machine", Redding Record Searchlight. September 11, 2020. Retrieved September 11, 2020.
  51. 55.0 55.1 55.2 Deliso, Merideth. "Man charged with arson in connection with Almeda Fire in southern Oregon Archived September 12, 2020, at the Wayback Machine", ABC News. September 11, 2020. Retrieved September 12, 2020.
  52. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  53. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  54. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  55. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  56. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  57. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  58. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  59. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  60. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  61. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  62. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  63. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  64. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  65. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  66. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  67. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  68. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  69. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  70. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  71. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  72. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  73. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  74. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  75. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  76. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  77. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  78. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  79. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  80. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  81. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  82. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  83. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  84. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  85. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  86. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  87. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  88. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  89. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  90. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  91. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  92. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  93. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  94. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  95. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  96. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  97. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  98. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  99. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  100. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  101. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  102. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  103. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  104. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  105. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  106. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  107. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  108. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  109. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  110. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  111. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  112. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  113. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  114. 118.0 118.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  115. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  116. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  117. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  118. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  119. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  120. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  121. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  122. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  123. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  124. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  125. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  126. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  127. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  128. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  129. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  130. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  131. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  132. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  133. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  134. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  135. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  136. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  137. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  138. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  139. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  140. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  141. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  142. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  143. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  144. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  145. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  146. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  147. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  148. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  149. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  150. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  151. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  152. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  153. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  154. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  155. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  156. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  157. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  158. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  159. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  160. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  161. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  162. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  163. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  164. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  165. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  166. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  167. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  168. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  169. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  170. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  171. Mark Miller, "Most evacuees can return as Chehalem Mountain Fire 75% contained" Archived September 25, 2020, at the Wayback Machine Portland Tribune website (last accessed September 14, 2020
  172. "Chehalem Mountain-Bald Peak Fire 100% contained, Level 3 'GO' orders lifted" KATU News. September 14, 2020. Retrieved September 14, 2020.
  173. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  174. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  175. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  176. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  177. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  178. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  179. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  180. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  181. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  182. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  183. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  184. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  185. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  186. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  187. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  188. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  189. 193.0 193.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  190. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  191. 195.0 195.1 Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  192. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  193. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  194. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  195. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  196. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  197. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  198. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  199. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  200. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  201. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  202. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  203. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  204. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  205. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  206. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  207. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  208. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  209. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  210. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  211. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  212. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  213. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  214. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  215. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  216. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  217. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  218. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  219. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  220. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  221. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).
  222. Lua error in ...ribunto/includes/engines/LuaCommon/lualib/mwInit.lua at line 23: bad argument #1 to 'old_ipairs' (table expected, got nil).

External links[edit source | edit]

Template:2020 wildfires Template:California wildfires Template:California wildfires by size Template:Oregon wildfires Template:Washington wildfires