Coordinates: 38°47′33″N 122°46′48″W / 38.792458°N 122.780053°W / 38.792458; -122.780053

Kincade Fire

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

Kincade Fire
Part of the 2019 California wildfires
File:Kincade Fire tmo 2019297 MODIS.jpg
Satellite image of smoke from the Kincade Fire on October 24
Date(s)
  • October 23, 2019 (2019-10-23) –
  • November 6, 2019 (2019-11-06)
LocationJohn Kincade Road and Burned Mountain Road, northeast of Geyserville, Sonoma County, California, United States
CoordinatesLua error in Module:Coordinates at line 489: attempt to index field 'wikibase' (a nil value).
Statistics[1][2]
Burned area77,758 acres (31,468 ha)[1]
Impacts
Non-fatal injuries4[1]
Structures destroyed374[1]
Ignition
Causeelectrical transmission lines located northeast of Geyserville owned and operated by PG&E[3]
Map
Lua error in Module:Location_map at line 411: Malformed coordinates value.

The Kincade Fire was a wildfire that burned in Sonoma County, California in the United States. The fire started northeast of Geyserville in The Geysers at 9:24 p.m. on October 23, 2019, and subsequently burned 77,758 acres (31,468 ha) until the fire was fully contained on November 6, 2019. The fire threatened over 90,000 structures and caused widespread evacuations throughout Sonoma County, including the communities of Geyserville, Healdsburg, Windsor, and Santa Rosa. The majority of Sonoma County and parts of Lake County were under evacuation warnings and orders. Lake county only had one evacuation order and that was the town of Middletown. The fire was the largest of the 2019 California wildfire season, and also the largest wildfire recorded in Sonoma County at the time before being surpassed by the LNU Lightning Complex fires in 2020.[4]

Progression

[edit | edit source]

The Kincade Fire was reported burning at John Kincade Road and Burned Mountain Road in The Geysers, northeast of Geyserville, California, at 9:57 PM on October 23, 2019.[5][6] The fire started at 9:24 PM during an extreme wind event.[7]

Cause

[edit | edit source]

A compulsory report shows that the fire started when a 230,000 volt transmission line failed near the point of origin, just as power was about to be shut off in the area.[8] On October 26, PG&E began shutting off power in an attempt to prevent additional fires, leaving an estimated three million people without power.[9] On October 28, the California Public Utilities Commission announced an investigation into the shutoffs.[10]

"Despite the latest shutdowns, PG&E admitted last week that its equipment may have started the Kincade fire," said the San Jose Mercury News in an editorial condemning the utility's practices and calling for regulatory action.[11] A San Francisco Chronicle editorial also called for the California Public Utilities Commission to

"give PG&E the kind of serious regulatory attention it should have been subject to many years ago."[12]

and noted that while California governor Gavin Newsom expressed an interest in a Berkshire Hathaway takeover of the utility, "[a]nyone who would bid for PG&E would also be bidding for all of its liabilities -- from the bankruptcy proceedings to fire victim claims to safety improvement bills ... "[12]

Effects

[edit | edit source]
File:Orange sunset from Kincade Fire, October 2019.JPG
An orange sunrise over San Francisco, caused by smoke from the fire, on October 29, 2019

The fire "chewed through more than 100 sq mi (260 km2) and destroyed or damaged over 120 buildings."[13] Eighty thousand more structures were threatened by the fire, and PG&E said it had cut off power to more than a million customers.[13] According to the Federal Communications Commission, hundreds of cell phone towers were down because of power shutoffs.[14] The Soda Rock Winery in Healdsburg was destroyed and the Field Stone Vineyard was heavily damaged.[15]

Closures and evacuations

[edit | edit source]

On October 26, compulsory evacuations had been issued for 90,000 people. As the fire spread, by October 27, evacuation orders and warnings grew to encompass nearly all of Sonoma County, including about 190,000 people, making it the largest evacuation ever in Sonoma County. Many people were forced to flee in the darkness due to ongoing power shutoffs in the region.[9] From an analysis of the historical GPS data, it was predicted that 35% of householders evacuated while the remaining decided to stay and defend their property. These results are comparable with the evacuation percentages observed in the previous wildfire affecting the same area: the 2017 Tubbs Fire.[16] On the other hand, find from a questionnaire study indicate that 79% of householders decided to evacuate.[17] Finally, traffic data indicate that the traffic slow down during the evacuation stage which might indicate congestions in some areas.[18]

File:California National Guard Kincade Fire Roadblock Healdsburg.jpg
National Guard Roadblock during Kincade Fire

The Sonoma County government, in conjunction with Esri, published an interactive map containing incidents and evacuation zones associated with the fires.[19]

Sonoma–Marin Area Rail Transit commuter rail offered free service between October 30 and November 6 initially as far north as Downtown Santa Rosa, then eventually on the whole line for those needing transportation alternatives.[20]

Utilities

[edit | edit source]
Further information: 2019 California power shutoffs

In the early weeks of the fire, PG&E initiated a massive power shut-off to nearly 940,000 customers by October 26, with a projected total number of customers impacted to be close to 2.5 to 2.8 million. There were to be six phases of power shutoff between October 26 and 27.[21] The outages did not go over well. "The issue isn't even all of the power shutoffs," said Mendocino County chief executive Carmel Angelo. "It's the lack of communication."[22]

Fire growth and containment progress

[edit | edit source]
Fire containment status[23]
Gray: contained; Red: active; %: percent contained;
Date Area burned acres (km2) Containment
Oct 23 400 acres (2 km2)[24]
0%
Oct 24 16,000 acres (65 km2)[25]
5%
Oct 25 23,700 acres (96 km2)[26]
5%
Oct 26 25,955 acres (105 km2)[27]
11%
Oct 27 54,298 acres (220 km2)[28]
5%
Oct 28 74,324 acres (301 km2)[29]
15%
Oct 29 76,138 acres (308 km2)[30]
15%
Oct 30 76,825 acres (311 km2)[31]
30%
Oct 31 76,825 acres (311 km2)[32]
60%
Nov 1 77,758 acres (315 km2)[33]
65%
Nov 2 77,758 acres (315 km2)[34]
72%
Nov 3 77,758 acres (315 km2)[35]
76%
Nov 4 77,758 acres (315 km2)[36]
80%
Nov 5 77,758 acres (315 km2)[37]
84%
Nov 6 77,758 acres (315 km2)[38]
100%

Cause of the fire

[edit | edit source]

Initially, it was unknown whether or not PG&E was at fault for the fire.[39] In a filing with the Securities and Exchange Commission (SEC), PG&E estimated a minimum loss of $600 million before available insurance.[40] On July 16, 2020, which was after PG&E exited bankruptcy, Cal Fire reported that the fire was caused by PG&E transmission lines.[3][41] Cal Fire did not make the report public, but forwarded the investigation report to the Sonoma County District Attorney's Office for further investigation.[clarification needed] Wildfire victims filed a civil lawsuit for damages caused by the fire.[42][43] Damages would not be covered by the settlement for wildfire victims that was part of the PG&E bankruptcy.[41][44]

See also

[edit | edit source]

References

[edit | edit source]
  1. ^ a b c d Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  2. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  3. ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  4. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  5. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  6. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  7. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  8. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  9. ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  10. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  11. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  12. ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  13. ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  14. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  15. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  16. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  17. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  18. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  19. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  20. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  21. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  22. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  23. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  24. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  25. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  26. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  27. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  28. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  29. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  30. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  31. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  32. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  33. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  34. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  35. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  36. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  37. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  38. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  39. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  40. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  41. ^ a b Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  42. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  43. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
  44. ^ Lua error in Module:Citation/CS1/Configuration at line 2172: attempt to index field '?' (a nil value).
[edit | edit source]
  • Error creating thumbnail: File missing Media related to Lua error in Module:Commons_link at line 62: attempt to index field 'wikibase' (a nil value). at Wikimedia Commons
Retrieved from "http://70.231.62.181/index.php?title=Kincade_Fire&oldid=23450701"