Article 4Y7CV Why isn’t California using more prescribed burns to reduce fire risk?

Why isn’t California using more prescribed burns to reduce fire risk?

by
Scott K. Johnson
from Ars Technica - All content on (#4Y7CV)
prescribed_burn_san_bernadino-800x450.jp

Enlarge / Crews carrying out a prescribed burn in California's San Bernardino National Forest. (credit: San Bernardino National Forest)

Whenever wildfires rip through an area, splashing nightmarish scenes across the evening news, people who live elsewhere seem to have a lot of suggestions. Why don't they log the forest so there's less to burn? Why don't they get millions of goats to graze the brush? Why live in such a dangerous spot? But as with most things, there are usually complications when you look closer.

A new study led by Stanford's Rebecca Miller analyzes one option for limiting fires in California: prescribed burns. The researchers interviewed experts in state government, federal agencies, non profits, and academia to find out what barriers are preventing greater use of prescribed burns.

Burning to avoid burns

Prescribed burns utilize low-intensity fires during favorable weather to safely remove some of the fuel that has accumulated on the ground-fuel present partly as a result of our past practice of putting out wildfires as aggressively as possible. It's often combined with mechanical thinning of brush and trees that serve as "ladders" for fires to climb into treetops, with the resulting brush piles burned later. The researchers say that about 20 percent of the state-20 million acres-could benefit from prescribed burns to reduce the wildfire hazard. But California is not currently on pace to complete that monumental task any time soon.

Read 13 remaining paragraphs | Comments

index?i=gAEIaSNyA5k:AgW59oTmFSA:V_sGLiPB index?i=gAEIaSNyA5k:AgW59oTmFSA:F7zBnMyn index?d=qj6IDK7rITs index?d=yIl2AUoC8zA
External Content
Source RSS or Atom Feed
Feed Location http://feeds.arstechnica.com/arstechnica/index
Feed Title Ars Technica - All content
Feed Link https://arstechnica.com/
Reply 0 comments