Rim Fire

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Rim Fire
File:Rim Fire and American Fire large.jpg
Satellite image of the Rim Fire, on August 23, 2013
(The American Fire is also visible to the north)
Location Sierra Nevada, California, USA
Coordinates Lua error in package.lua at line 80: module 'strict' not found.
Statistics
Cost $127.35 million (2013 USD)[1]
Date(s) August 17, 2013 (2013-08-17) – October 24, 2013 (2013-10-24)
Burned area 257,314 acres (104,131 ha)[1][2][3]
Cause Illegal campfire
Buildings
destroyed
112, including 11 residences[1][4]
Injuries 10[3][5][6][7]
Fatalities None reported

The Rim Fire was a wildland fire that was started in a remote canyon in Stanislaus National Forest in California. This portion of the central Sierra Nevada spans Tuolumne and Mariposa counties. The fire started on August 17, 2013 during the 2013 California wildfire season.[1] It was the third largest wildfire in California's history,[8] having burned 257,314 acres (402.053 sq mi; 1,041.31 km2).[1][9] It is also the largest wildfire on record in the Sierra Nevada mountain range.[4] The Rim Fire was fully contained on Thursday, October 24, 2013 after a nine-week firefighting battle.[1] More than a year passed before it was declared out on November 4th, 2014.[10] Due to a lack of winter rains, some logs smoldered in the interior portion of the fire throughout the winter.

The fire was caused by a hunter's illegal fire that got out of control,[11] and it was named for its proximity to the Rim of the World vista point, a scenic overlook on Highway 120 leading up to Yosemite.[12][13] A total of eleven residences, three commercial buildings, and 98 outbuildings were destroyed in the fire.[1] A total of ten injuries from the wildfire were also reported, but no firefighters were killed during the suppression efforts.[1] Putting out the fire cost more than $127 million (2013 USD).[1]

Overview

The fire erupted on August 17, 2013 at 3:25 pm[14] in the Stanislaus National Forest, east of Groveland, when a hunter lost control of an illegal campfire.[15] The hunter was not identified publicly until a year later, when two felony, and two misdemeanor charges were filed against Keith Matthew Emerald of Columbia, California.[16] The fire had only consumed 40 acres when it was discovered, but it grew to 10,000 acres within 36 hours and 100,000 acres after just four days. In two days, in mid-August, the fire consumed nearly 90,000 acres. The fire's rapid spread was attributed to five factors: a record-breaking drought; a heat wave; past fire suppression efforts that had altered the normal fire regime; population growth, which complicates suppression tactics; and Forest Service budget cuts.[17] It burned into backcountry areas of Yosemite National Park. The park remained open, and though Yosemite Valley was never in danger, the fire did consume 78,895 acres of parkland.<[18] Heavy smoke was, at times, a factor.[19]

The blaze was difficult to fight because of inaccessible terrain and erratic winds, forcing firefighters to be reactive instead of proactive. More than 5,000 firefighters[1]–including more than 650 inmates who volunteered as part of California's "Conservation Camp initiative"[20][21]–worked to contain the fire, which was described by a Forest Service spokesman as "a real tiger."[4] At one point state officials asked residents to avoid social media, to stop exaggerated claims and rumors from spreading, and debunked a number of circulating stories.[22]

Atmospheric instability, hot temperatures, and a severe drought fueled the fire, making it difficult to combat. Also contributing to the intensity of the fire was a pre-1980s policy of suppressing small natural fires, which altered the natural fire regime leaving nearly a century's worth of fuel on the ground. This resulted in a massive forest fire that left large swaths of the forest, including the overstory, severely burned.[17] Forest officials estimated "that almost 40% of the area inside the fire's boundary is nothing but charred land" – nearly 160 square miles of the park's 400 square miles burned. They stated that the extent of destruction was "unprecedented" for historic Sierra Nevada fires.[23] On Thursday, October 24, 2013, the Rim Fire was 100% contained.[1]

Closures and evacuations

File:Rim Fire 2013 (9580046994).jpg
California Army National Guard's 1–140th Aviation Battalion at the Rim Fire near Yosemite, August 22.

Forest closures were put into effect and evacuation advisories were issued by Tuolumne and Mariposa counties. Several thousand people left their homes temporarily as a result of the evacuations.[1] The Tioga Pass Road (Highway 120) was closed for a time. Highways 140 from Merced and 41 from Fresno remained open throughout the fire, providing access to the national park.[24]

Smoke from the fire caused unhealthy air conditions in Reno, Nevada, and the Lake Tahoe area during the first week of the fire, forcing the cancellation of several outdoor events.[25] School children were sent home due to smoky conditions as well. From Yosemite to the San Joaquin Valley, air quality reached unhealthy levels several times according to the National Weather Service.

Berkeley Tuolumne Camp, a family camp operated by the city of Berkeley, established in 1922, was burned to the ground.[26] Nearby Camp Tawonga suffered some damage, including the loss of three buildings.[26][27] Camp Mather, operated by the city of San Francisco, suffered minor damage,[28] as did the San Jose Camp run by the city of San Jose.[29] Privately owned Evergreen Lodge was undamaged.[30]

The Rim Fire of 2013 was named after the Stanislaus National Forest's Rim of the World vista point.

State of emergency and federal funding

File:The Rim Fire in the Stanislaus National Forest on Aug. 17, 2013 -001.jpg
Much of the fire burned in crown-fire fashion, thus exacerbating rapid rates of spread.[31]

California governor Jerry Brown declared a state of emergency for the city of San Francisco on August 23,[32] after the fire caused damage to the power infrastructure serving the Bay Area, causing two out of the existing three hydroelectric power plants to shut down.[33] The fire also threatened the Hetch Hetchy reservoir, the main source of water for San Francisco, providing up to 85% of the city's supply[34] to 2.6 million customers.[35] On August 26, the San Francisco Public Utilities Commission moved water away from Hetch Hetchy into downstream reservoirs located in San Mateo and Alameda Counties as a precautionary measure, but did not expect the fire to cause any disruption to the city's water supply.[36][37] The fire advanced to within a mile of Hetch Hetchy by Monday, August 26, which was a concern to O'Shaughnessy Dam officials due to ash falling in the water.

On August 28, after receiving emergency approvals, an MQ-1 Predator unmanned aerial vehicle was flying over the area providing infrared video of lurking fires.[38][39]

The cost of fighting the fire was estimated at $127.35 million as of October 24, 2014.[1][40] The Federal Emergency Management Agency announced that it would reimburse the state up to 75% of the eligible costs of fighting the fire through a grant for "managing, mitigating, and controlling the fire".[41]

Forest and park issues

File:Rim Fire Yosemite August 2013 004.jpg
The fire as viewed from the Tioga Road on August 27.

The United States Forest Service made it their highest priority fire because of the threat to local communities and its proximity to Yosemite National Park.[42] Though Giant Sequoia trees are very fire-tolerant and, in fact, need fire to reproduce, concerns rose as the intense fire approached them - some of the biggest and oldest living things on Earth.[43]

Park officials set sprinklers to help protect nearby big trees,[44] but the sprinklers were then removed and careful low-intensity burns were successfully used instead.[45]

Wildlife officials took measures to help displaced animals. The Forest Service is currently studying the lasting effects on the habitat in the burned areas. Concerned biologists observed animals in the burned areas during the fire, including Western pond turtles that congregated in the small amount of water that did not evaporate and a number of bald eagle nests.[44]

Parts of the National Forest are used for grazing, and there was concern that hundreds of cattle could have been injured or killed. The blaze severely impacted 6 of 14 grazing allotments located within the fire perimeter and displaced cattle were scattered over a wide area.[46]

The fire also threatened the Stanislaus-Tuolumne Experimental Forest, one of California's main centers for forest fire research, located a few miles from the northern edge of the Rim Fire near Pinecrest. The experimental forest was created in the 1920s and has since served as an open-air laboratory to research how the density of vegetation impacts the diffusion of wildfires and the resilience of forests.[47][48]

Recovery

The 3 Forests Interpretive Association published three newsletters, highlighting various Rim Fire Recovery topics.[49]

Closed areas during recovery

On April 17, 2014, Stanislaus National Forest issued an order closing the majority of the burn area to the public through November 18, 2014, citing safety issues from potential falls of heavily burned trees, rock falls, and uneven ground.[50] The decision was met with disappointment by morel mushroom hunters who had looked forward to extensive post-fire fruiting of this highly sought-after mushroom.[51][52][53] The safety rationale was questioned, as Yosemite National Park, which largely prohibits mushroom collecting, had opened up the burn areas within its boundaries to the public earlier in the month.[53][54] Some mushroom hunters stated that they would be willing to sign liability waivers in order to enter the area, but the Forest Service rejected this idea, stating they were ultimately responsible for the safety of those entering the area.[51][52] Extensive harvesting of morels in the Rim Fire area nevertheless took place in May 2014, in a few cases legally by special permit, but in most cases through illegal harvesting.[51][52][55] The closure of the burn area was also criticized by the Tuolumne County Board of Supervisors for, among other reasons, causing the cancellation of grazing allotments by local ranchers.[56]

Salvage logging

In late 2013, a plan was considered for salvage logging approximately 30,000 acres (120 km2) of the Rim Fire. The snag patch forest, or habitat of forest-killed trees, is home to a wide variety of wildlife, some of which are management indicator species. Some scientists and conservation groups opposed the logging plan, contending that the removal of trees from this area would not only harm such species as Black Backed Woodpeckers, but could affect other cavity-nesting birds that follow in the wake of the woodpeckers. Other species of wildlife could also be at risk, such as frogs that inhabit forested streams, and deer.[57][58] However, other environmental groups, including the Environmental Defense Fund, endorsed the salvage logging plan as justified and necessary, given the unprecedented and unnatural level of destruction caused by the fire. Eric Holst, senior director of the EDF, said: "The Rim Fire has provided an overabundance of dead wood. Removing a responsible proportion of it and sending it to mills to create jobs and net revenue for restoration will not compromise ecological health."[59][60]

On August 28, 2014, Stanislaus Forest supervisor Susan Skalski signed a Record of Decision approving the Rim Fire Recovery Project. The plan allows logging within an area of 52 square miles (130 km2), including interior portions of the burned area and along roadways.[61] Its goals are to: "Salvage dead trees to capture economic value; remove roadside hazard trees to protect public and worker safety; reduce fuels for future forest resiliency; improve roads for hydrologic function; and, enhance wildlife habitat. A portion of the money captured from the salvage logging is ear-marked for ecological restoration projects following the fire."[62] The plan attempted to balance competing interests, an essential task for a multiple use agency such as the U.S. Forest Service. Instead of the 660 million board feet of salvage wood that could have been logged, the final plan dropped the estimated salvage removal to 210 million board feet. The new plan leaves vast areas untouched as snag habitat for Black-Backed Woodpeckers and other snag-dependent wildlife. Instead of building permanent new roads, the plan eliminated permanent new road construction and reduced the mileage of temporary roads as part of the salvage logging plan. The Forest Service acknowledged that the final plan reflected a collaboration between the timber industry and various environmental groups, who had joined together in an attempt to find consensus on the recovery process. Skalski cited that collaborative agreement from previously polarized groups as being influential in her decision to significantly reduce the amount of salvage material. Forestry officials praised the plan, but some environmental groups denounced it.[61] The excess fuel is anticipated to be sold to the timber industry for removal.

The purpose of salvage logging was to remove an enormous fuel load from the forest floor. As trees fall, they contribute to the potential for having future catastrophic fires. Severe soil damage, which can cause hydrophobicity, occurs when a fire lingers in an area for a long time such as beneath burning logs. The phenomenon is known as residence time. The longer a fire lingers over a given area and heats it up, the greater the potential damage to soils. Hydrophobic or "water-fearing" soils increase the chance for erosion and runoff. Sedimentation flows, flooding, mudslides, and rock slides can result when soils are badly damaged. Structurally damaged trees also pose a threat to visitors.

Reforestation efforts

An interdisciplinary team of 17 research specialists began working on the reforestation plan for the fire in the fall of 2014. Stakeholders were encouraged to participate in an open house that was held on December 16, 2014. A Record of Decision (ROD) will follow many months later and will outline the area to be replanted.

See also

References

  1. 1.00 1.01 1.02 1.03 1.04 1.05 1.06 1.07 1.08 1.09 1.10 1.11 1.12 Lua error in package.lua at line 80: module 'strict' not found.
  2. Rim Fire: No Structures Threatened | myMotherLode.com
  3. 3.0 3.1 Lua error in package.lua at line 80: module 'strict' not found.
  4. 4.0 4.1 4.2 Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Rim Fire continues to burn
  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. Lua error in package.lua at line 80: module 'strict' not found.
  12. Rim of the World Vista - Stanislaus National Forest 37.821949, -120.039153
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. California Department of Forestry
  15. 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. 17.0 17.1 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. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  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. 26.0 26.1 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. 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. Lua error in package.lua at line 80: module 'strict' not found.
  38. Elan Head. "Unmanned future" Vertical Magazine, November 7, 2013. Accessed: November 21, 2013.
  39. Elan Head. "Predator aircraft makes history in Rim Fire" Vertical Magazine, September 1, 2013. Accessed: 11 December 2013.
  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. 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 Lua error in package.lua at line 80: module 'strict' not found.
  45. Marcum, Diana. "Risky measures to save big trees from Rim fire worked", Los Angeles Times, 22 September 2013. Retrieved 1 September 2014.
  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. "Order No. STF 2014-01, Rim Fire Closure, Stanislaus National Forest"
  51. 51.0 51.1 51.2 Mushroom boom after massive fire. CNN.com Blogs: Eatocracy
  52. 52.0 52.1 52.2 Mushroom hunters follow fire into burned forest
  53. 53.0 53.1 Morel mushroom hunters banned from prime multimillion-dollar bounty near Rim fire site. Sacramento News and Review. April 21, 2014.
  54. Yosemite National Park Reopens Areas Affected by Rim Fire. U.S. National Park Service: Yosemite National Park.(
  55. Wild mushrooms entice smugglers to fire-ravaged California forest. Reuters
  56. Rim Fire closures panned by board. Union Democrat
  57. /Lua error in package.lua at line 80: module 'strict' not found.
  58. Nourished by Wildlife: The Ecological Benefits of the Rim Fire and the Threat of Salvage Logging, Center for Biological Diversity and the John Muir Project, January 2014.
  59. Lua error in package.lua at line 80: module 'strict' not found.
  60. Rim fire salvage logging wins support, Holland, John. The Modesto Bee, 22 April 2014
  61. 61.0 61.1 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.

External links