Tubbs Fire

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
Tubbs Fire
File:Map of Tubbs fire.png
Map of the burn area of the Tubbs Fire (top) and 2 other nearby fires
Location Sonoma County, California, Napa County, California, U.S.
Coordinates Lua error in package.lua at line 80: module 'strict' not found.
Statistics[1]
Cost ~$1.3 billion (2017 USD)[2][3]
Date(s) October 8, 2017 (2017-10-08) – October 31, 2017 (2017-10-31)
Burned area 36,807 acres (149 km2)[4]
Cause Unknown
Buildings
destroyed		 5,643 structures[4][5]
Injuries 1
Fatalities 22[4]
Syntax error
<maplink zoom="8" latitude="<strong class="error"><span class="scribunto-error" id="mw-scribunto-error-2">Lua error in package.lua at line 80: module 'strict' not found.</span></strong>" longitude="<strong class="error"><span class="scribunto-error" id="mw-scribunto-error-3">Lua error in package.lua at line 80: module 'strict' not found.</span></strong>" text="[Full screen]">

[


{"type": "FeatureCollection",

 "features": [


{ "type": "Feature",

  "geometry": {"type": "Point", "coordinates": [Lua error in package.lua at line 80: module 'strict' not found.,Lua error in package.lua at line 80: module 'strict' not found.] },
  "properties": {
   "title": "Tubbs Fire", 
   "description": "",
   "marker-symbol": "-number", "marker-size": "medium", "marker-color": "#B80000" }
}






























] }

]</maplink>
Location of Tubbs Fire

The Tubbs Fire was the second-most destructive wildfire in California history, behind only the Camp Fire of 2018,[6][4] burning parts of Napa, Sonoma, and Lake counties in Northern California during October 2017, and affecting the city of Santa Rosa the most. It was one of more than a dozen large fires that broke out in early October and were simultaneously burning in eight Northern California counties in what was called the "Northern California firestorm."[7] By the time of its containment on October 31, the fire was estimated to have burned 36,810 acres (149 km2),[8][9] and at least 22 people had been killed in Sonoma County by the fire.[10]

The fire incinerated more than 5,643 structures,[4][5][11] including more than 2,800 homes in the city of Santa Rosa.[12] In that city, the damage from the Tubbs Fire was estimated at $1.2 billion (2017 USD), with five percent of the city's housing stock destroyed.[2] The Tubbs Fire also incurred an additional $100 million in fire suppression costs.[3]

The Tubbs Fire started near Tubbs Lane, named after Alfred Tubbs, the owner of a winery in that area in 1882. The Tubbs mansion had burned down in the Hanly Fire in 1964.[13]

Timeline

File:Tubbs Fire, 09 October, 2017, MODIS Terra 721 satellite image.tif
Tubbs Fire, 10 October, 2017, MODIS Terra 721 satellite image,
File:Tubbs Fire, 09 October, 2017, MODIS Terra visible satellite image.tif
Tubbs Fire, 09 October, 2017, MODIS Terra visible satellite image
File:Tubbs Fire, 10 October, 2017, MODIS Terra visible satellite image.tif
Tubbs Fire, 10 October, 2017, MODIS Terra visible satellite image

October 8

The Tubbs Fire started near Tubbs Lane in Calistoga[14] around 9:43 p.m. on Sunday, October 8.[15] Although the cause of the fire remains under investigation, Sonoma County emergency dispatchers sent fire crews to at least 10 reports of downed power lines and exploding transformers as the North Bay fires, including the Tubbs fire, began. At a weather station in north Santa Rosa, the peak wind gusts at 9:29 p.m. hit 30 mph; an hour later, they were 41 mph.[16]

Pushed by strong winds from the northeast, the front of the fire moved more than twelve miles in its first three hours.[15] The Mark West Springs area, north of Santa Rosa in unincorporated Sonoma County, was directly in the path of the fire. One exception to the destruction in that area was that all of the more than 1,000 animals at the renowned Safari West Wildlife Preserve were unharmed by the fire, saved by owner Peter Lang, who, at age 76, single-handedly fought back the flames for more than 10 hours using only garden hoses.[17][18]

Sonoma County officials could have sent out an emergency alert to every cellphone in the region on Sunday night as the fire grew, but chose not to, saying such a widespread alarm would have hampered emergency efforts. Instead, Nixle SMS and email alerts were broadcast — the first of these text messages going out at 10:51 p.m., and used a system called SoCo Alerts to notify people via cellphone; both are limited to those who sign up for these services. Officials also used a reverse 911 system that called landlines in certain areas.[19] At 11:58 p.m., firefighters called for an evacuation order encompassing the area between the city of Calistoga and Santa Rosa. [20]

October 9

File:Puerto Vallarta burns.jpg
The Puerto Vallarta restaurant burns on October 9, 2017
File:JEMHP.jpg
Smoldering remains of the Journey's End Mobile Home Park on October 9, 2017
File:Fountaingrove after the October 2017 Northern California wildfires.jpg
Remains of a house on Cross Creek Road in Fountaingrove on November 1, 2017
File:Hilton staircase.jpg
Staircase leading to the west wing buildings of the Hilton Sonoma Wine Country Hotel on November 17, 2017
File:FI and JEMHP overview.jpg
Overlook view of the damage to the Fountaingrove Inn (foreground) and Journey's End
File:FRB before and after.jpg
The historic Fountaingrove Round Barn before and after the fire

By 1 a.m. on Monday, the fire, spreading quickly to the south and west, had reached Santa Rosa city limits.[15] The front entered the city from the north,[21] moving into the Fountaingrove area, then moving down ravines between Mark West Springs Road and Fountaingrove Parkway.[22] At about 1:30 a.m., Sonoma County officials began to evacuate neighborhoods in and around Santa Rosa.[22] In all, tens of thousands of people were evacuated with very little notice.[23]

By about 2 a.m., the fire, carried by near hurricane-level winds,[22] had spread further to the west, crossing Highway 101.[14] By 4:30 a.m., the winds had reached their peak speed of more than 60 miles per hour.[15]

The fire devastated the Coffey Park neighborhood,[24][25] where an estimated 1,300 structures, mostly detached homes, were leveled.[26] Meanwhile, east of the highway, the Fountaingrove Inn, the historic Fountaingrove Round Barn nearby, and a large Hilton hotel were destroyed;[27][28] 116 of the 160 units at the Journey's End Mobile Home Park burned to the ground, while the remainder of the park was later red-tagged due to heavy damage.[29] Other damage along several streets bordering Highway 101 included a Kmart store and numerous restaurants that burned to the ground.[30][31]

By noon on Monday, two medical centers in Santa Rosa, Kaiser Permanente and Sutter Health, had been evacuated.[32] Some Kaiser employees reportedly used their personal vehicles to evacuate some of the 130 patients at that hospital.[33]

The destruction on Monday also included the complete loss of a senior living complex, Oakmont of Villa Capri; Hidden Valley Satellite, a primary school; and the Santa Rosa portion of Paradise Ridge Winery.[31] The Cardinal Newman High School campus was badly damaged, as was one end of the Luther Burbank Center for the Performing Arts.[31] Redwood Adventist Academy was also destroyed in the fire. [34] Another large concentration of incinerated homes was in the Larkfield-Wikiup area, about a mile north of the city, where about 500 buildings were destroyed.[11]

Of the 2,900 homes destroyed in Santa Rosa, over 200 of them belonged to doctors associated with the area hospitals, including Kaiser Permanente, Sutter Hospital's Santa Rosa Center, and Santa Rosa Memorial Hospital. [35] Additionally, the fire destroyed Santa Rosa Community Health's Vista Campus, the largest in its system, which served 24,000 people annually. [36]

Pacific Gas and Electric Company cut off natural gas to 31,000 customers in the Santa Rosa and Windsor areas as a precaution.[37]

October 10

Wind direction turned clockwise from northeasterly to southerly (compare MODIS satellite images). At a town hall meeting on the evening of October 10 in Santa Rosa, Cal Fire representatives reported that there could be as many as 3,000 structures lost to the Tubbs and Atlas fires. [38][39]

October 11

On Wednesday, October 11, the entire town of Calistoga was evacuated[40]; about 2,000 people were asked to leave.[41] The escape for some was along roads walled by flames.[42] The Lake County Sheriff’s Office issued an advisory evacuation notice for residents in the Middletown area, to the north of Calistoga.[43]

One active part of the fire was east of the town of Windsor, with the fire burning from Shiloh ridge to Chalk Hill Road and Knights Valley.[42]

October 12

As of 7 a.m. on Thursday, the Tubbs Fire had burned 34,270 acres, and was 10 percent contained.[44] In the city of Santa Rosa, officials said that the fire had destroyed an estimated 2,834 homes, along with about 400,000 square feet of commercial space.[12]

As of Thursday morning, efforts continued to be focused on two areas:

  • Near the northwest corner of Napa County, firefighters were battling the fire around Mount St. Helena, but they started pulling back before noon; the fire had hopped Highway 29, which runs adjacent to the mountain north of the evacuated town of Calistoga.[44] There was no fire activity in the town itself,[12] with the blaze spreading north and east of Calistoga through rugged terrain into Lake County, south of Middletown.[45] By Thursday afternoon, only a few dozen people had refused to evacuate from Calistoga.[46]
  • In northern Sonoma County, the fire was being monitored in the area to the east of Healdsburg and Windsor. Sonoma County ordered Rio Lindo Adventist Academy, a boarding school on the outskirts of Healdsburg near the edge of the Tubbs fire, to prepare to evacuate if necessary.

Among the losses reported on Thursday was the destruction of the Santa Rosa hillside home of late Peanuts creator Charles Schulz; his widow, Jean Schulz, escaped unhurt.[44][45] By Thursday evening, 28,000 customers in the Santa Rosa and Windsor areas still had not had their gas service restored.[37]

October 13-31

On Friday morning, October 13, the fire was 25 percent contained.[47] It remained about two miles outside of Calistoga's city limits.[48]

A fire erupted in the hills east of Oakmont late Friday night, prompting the mandatory evacuation of neighborhoods early Saturday morning from Calistoga Road to Adobe Canyon Road, along Highway 12. The zone included several schools and the Oakmont Village retirement neighborhood. Evacuations for the area were lifted by late the following Wednesday.

By Saturday morning, October 14, the fire was 44 percent contained.[49] A "small army of firefighters and police" was positioned between where the fire was most active, north of Calistoga, and the city itself.[50]

In the Fountaingrove area of Santa Rosa, firefighters and utility crews combed through the ruins left by the fire. Fire officials searched for dangerous hot spots that could re-ignite the blaze, and utility workers began cleaning up the demolished neighborhoods.[51]

File:11 November 2017, Napa, Sonoma fires, Landsat 8, bands 753.tif
11 November 2017, Landsat 8 OLI, bands 753, Napa, Sonoma fires of October 2017
File:11 November 2017, Tubbs Fire, SantaRosa, Landsat 8, bands 753.tif
11 November 2017, Landsat 8 OLI, bands 753, false color infra-red satellite image, zoom to full resolution on Santa Rosa, California. Scale: 1:24,000.

Containment progress

Fire containment status[52]
Date Acres burned Containment
Oct 9 25,000[53]
0%
Oct 10 27,000[54]
0%
Oct 11 27,363[55]
10%
Oct 12 34,770[56]
10%
Oct 13 35,270[57]
44%
Oct 14 35,470[58]
50%
Oct 15 35,470[59]
60%
Oct 16 36,432[60]
75%
Oct 17 36,432[61]
87%
Oct 18 36,432[62]
91%
Oct 19 36,432[63]
92%
Oct 20 36,432[64]
93%
Oct 21 36,793[65]
94%
Oct 22–25 36,807[66][67][68][69]
94%
Oct 26 36,807[70]
95%
--- --- ---
Oct 31 36,807[71]
100%

Comparison to the Hanly Fire

In 1964, the Hanly Fire, the largest fire in Sonoma County history, burned 52,700 acres, with striking similarities to the Tubbs Fire.[72] The two fires differed, however, because since 1964, hundreds of expensive homes, a golf course and clubhouse restaurant, office and medical buildings, light industry, lakeside retirement homes, a long row of nursing facilities, and two hotels were built in the Fountaingrove area, which had been almost entirely open land in 1964.[73]

The path the Hanly Fire took in 1964, as well as the areas it burned, were very similar to the Tubbs Fire: from Calistoga, along Porter Creek and Mark West Springs roads into Sonoma County, burning homes along Mark West Springs and Riebli roads, through Wikiup, and to Mendocino Avenue, where it stopped, across the street from Journey’s End Mobile Home Park.[74] The fire was propelled by 70 mph winds, close to hurricane strength; it initially went east from Calistoga, but on the third day its direction switched, going south-west from Calistoga to Santa Rosa in only about half a day.[72] But the fire only destroyed a few dozen homes, because the area it burned was so sparsely settled in 1964.[75]

Sonoma County has four "historic wildfire corridors,"[76] including the Hanly Fire area. New homes in the fire zones must meet building code requirements for fire-resistant materials for siding, roofing and decks, with protected eaves to keep out windblown embers.[72] Those measures made little difference. For example, despite a 100-foot fire break that ringed much of the Fountaingrove II subdivision, which consisted of 600 upscale homes in the same path as the Hanly Fire,[77] virtually the entire subdivision was destroyed by the Tubbs Fire.[78][79]

News and social media coverage

The fire was covered extensively and in-depth by news outlets from around the San Francisco Bay Area and beyond.[lower-alpha 1] In addition to local coverage, CNN and Fox News were on scene in Sonoma County, focusing primarily on northern Santa Rosa, California.[81][82] The majority of communication regarding the fire came from social media websites such as Twitter, Facebook, Snapchat and Nixle.[83]

From October 9 through 13, Snapchat ran a geolocation tagging filter to isolate material about the fire, and these posts were featured on the Discover page.[84] By October 11, over 12,000 videos and images had been uploaded to Snapchat.[85] Donald Laird, a professor at Santa Rosa Junior College, and Richard Dunn, a local photographer, submitted featured posts. [86]

On social media sites such as Twitter and Facebook, hashtags used to identify information about the fire included #santarosafire, #tubbsfire, and #santarosastrong.[87]

Twitter analytics revealed that the majority of tweets about the Tubbs Fire were posted on October 11.[88]

The Press Democrat staff also won the 2018 Pulitzer Prize for Breaking News Reporting for "[f]or lucid and tenacious coverage of historic wildfires that ravaged the city of Santa Rosa and Sonoma County". [89]

See also

Notes

  1. ↑ Several local outlets would receive national recognition for their broadcasts. KXTV (Continuing Coverage) and KNTV (Hard News, News Documentary) won Edward R. Murrow Awards, while KPIX won the National Headliner Award and the Sigma Delta Chi Award (both for Breaking News coverage).[80]

References

  1. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ 2.0 2.1 Lua error in package.lua at line 80: module 'strict' not found.
  3. ↑ 3.0 3.1 Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ 4.0 4.1 4.2 4.3 4.4 Lua error in package.lua at line 80: module 'strict' not found.
  5. ↑ 5.0 5.1 Lua error in package.lua at line 80: module 'strict' not found.
  6. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  7. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  8. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  11. ↑ 11.0 11.1 Lua error in package.lua at line 80: module 'strict' not found.
  12. ↑ 12.0 12.1 12.2 Lua error in package.lua at line 80: module 'strict' not found.
  13. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  14. ↑ 14.0 14.1 Lua error in package.lua at line 80: module 'strict' not found.
  15. ↑ 15.0 15.1 15.2 15.3 Lua error in package.lua at line 80: module 'strict' not found.
  16. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  17. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  18. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  19. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  20. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  21. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  22. ↑ 22.0 22.1 22.2 Lua error in package.lua at line 80: module 'strict' not found.
  23. ↑ Fires burn across Sonoma and Napa counties as thousands flee devastating flames. Santa Rosa Press-Democrat, 9 October 2017
  24. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  25. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  26. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  27. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  28. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  29. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  30. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  31. ↑ 31.0 31.1 31.2 Lua error in package.lua at line 80: module 'strict' not found.
  32. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  33. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  34. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  35. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  36. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  37. ↑ 37.0 37.1 Lua error in package.lua at line 80: module 'strict' not found.
  38. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  39. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  40. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  41. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  42. ↑ 42.0 42.1 Lua error in package.lua at line 80: module 'strict' not found.
  43. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  44. ↑ 44.0 44.1 44.2 Lua error in package.lua at line 80: module 'strict' not found.
  45. ↑ 45.0 45.1 Lua error in package.lua at line 80: module 'strict' not found.
  46. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  47. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  48. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  49. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  50. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  51. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  52. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  53. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  54. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  55. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  56. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  57. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  58. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  59. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  60. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  61. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  62. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  63. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  64. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  65. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  66. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  67. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  68. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  69. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  70. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  71. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  72. ↑ 72.0 72.1 72.2 Lua error in package.lua at line 80: module 'strict' not found.
  73. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  74. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  75. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  76. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  77. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  78. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  79. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  80. ↑ Lua error in package.lua at line 80: module 'strict' not found.
       Lua error in package.lua at line 80: module 'strict' not found.
  81. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  82. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  83. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  84. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  85. ↑ Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  86. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  87. ↑ See, for example, Lua error in package.lua at line 80: module 'strict' not found.
  88. ↑ Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  89. ↑ [1]

External links

Retrieved from "https://infogalactic.com/w/index.php?title=Tubbs_Fire&oldid=725738994"