TEXT_SIZE

Wildfire

Reading Fire 8/15/2012 update

Feather Publishing
8/15/2012
8:00 a.m. update
The Reading Fire, burning in and to the north of Lassen Volcanic National Park, is now 23,958 acres and 23% contained. Full containment is projected to occur on August 21. Click here to see the most recent Reading Fire map.

A public meeting was held at the Old Station Volunteer Fire Department yesterday evening (Tuesday August 14th). Nearly 100 members of the local community were in attendance and received current information regarding the Reading Fire in Lassen National Forest. The Incident Commander of the California Interagency Incident Management Team 3, Jeanne Pincha-Tulley and Kit Mullen of the U.S. Forest Service were available to answer questions following the meeting. Other agencies in attendance were the American Red Cross, the Shasta County Sheriff's Department, the National Park Service, Cal Fire, and additional members of the California Team 3.

Read more: Reading Fire 8/15/2012 update

 

Wildfire smoke can affect health

Feather Publishing
8/14/2012

Plumas County Public Health Officer Dr. Val Armisen advises residents with sensitive health conditions to stay alert to changing smoke levels caused by the Chips Fire and be prepared to act accordingly.

Smoky conditions can be hazardous for certain high-risk groups such as young children, the elderly, individuals with heart conditions or chronic lung disease such as asthma and bronchitis, and individuals with other respiratory ailments. Residents in these high-risk groups who are in areas of heavy smoke should be prepared to stay indoors and limit their activity.

Read more: Wildfire smoke can affect health

 

Chips Fire 8/13/2012 update

Feather Publishing
8/13/2012
10:00 p.m. update

The Plumas County Sheriff issued a Voluntary Evacuation for Canyondam, Big Meadows, and Rocky Point Campground at 5 PM this evening. The Sheriff’s Advisement for the other communities along Highway 89 including Prattville, Almanor, and West Almanor remain in effect (see more details in Evacuation Section below).

Tonight crews will continue to work through the night to strengthen the containment line using both direct tactics near the edge of the fire, and indirect tactics in areas with steep terrain. North containment lines along the Humbug Road have held for more than 48 hours and will continue to be improved. No movement occurred along Highway 70 and the west flank.

New contingency lines along Highway 89 and north of Humbug Road are being improved with dozers and other heavy equipment. CalFire and Office of Emergency Services engines continue to arrive and will comprise a robust structural protection group for the communities threatened by the Chips Fire.

Read more: Chips Fire 8/13/2012 update

  

Reading Fire 8/13/2012 update

Feather Publishing
8/13/2012
8:00 a.m. update
Reading Fire grows to 20,642 acres

The Reading Fire has grown to 20,642 acres and is only 10 percent contained.

Burning operationswere successful last night. 1.8 miles of fire line from West Prospect Peak to Red Rock and 3.2 miles uphill to Rail Canyon were burnt out. An additional 1.4 miles were prepared from the 20 road to the 12 road around Badger Mountain.

Firing operations will continue along the indirect fire containment lines when and where burning conditions permit. These burning operations may be conducted either day or night as conditions allow, and will result in smoke appearing some distance from the wildfire edge. The firing operations will take place over a several day period in order to moderate fire effects.

Read more: Reading Fire 8/13/2012 update

 

Chips Fire public meeting in Chester tonight

Monday, August 13, 2012

Time: 6:00 pm

Location: Almanor Recreation Center

450 Meadowbrook Loop

Chester, CA

 

The Chips Fire Incident Management Team is holding a community meeting to provide the public with current information on fire suppression efforts.  Contact the Chips Fire Information Center if you have any questions at (530)283-3593/-3288.

  

Page 6 of 9

"); pageTracker._trackPageview(); } catch(err) {}