How the Whitewater Fire sent eclipse plans up in flames

On the evening of June 26, a thunderstorm rolled across the Central Cascade Range and raked the forest with more than 100 lightning strikes.

The storm would spark 12 different wildfires in Willamette National Forest, but because conditions were still wet, the blazes remained small and were quickly doused.

But it was a lightning strike that wasn’t detected, that sat smoldering in a tree for almost a month, that would spark Oregon’s second-largest and most significant wildfire of the summer so far.

The Whitewater Fire, now 5,884-acres in the Mount Jefferson Wilderness, blanketed the Willamette Valley with smoke, threatened two small communities and ruined the eclipse plans of people around the globe.

Prior to the fire, the area surrounding 10,495-foot Mount Jefferson was expected to draw tens of thousands for the total solar eclipse Aug. 21.

Now places such as Jefferson Park — a back-country meadow considered the ideal eclipse-watching destination — will be closed as flames blacken one of the most beloved hiking and backpacking spots in Oregon.

All totaled, 117,000-acres and almost 30 miles of the Pacific Crest Trail are closed to the public through eclipse day and beyond.

The fire likely won’t be extinguished until winter rains arrive, fire officials said.

“We understand how disappointed people are,” Willamette National Forest Supervisor Tracy Beck said.

“We threw everything we had at this fire when it started. But you can’t get them all.”

Smoldering tree undetected

It’s fairly common for lightning to ignite a wildfire long after the actual strike.

When lightning storms come through with rain, some fires pop up immediately while others smolder in what are known as strike trees — trees hit by lightning.

As the forest dries from the storm, the spark can remain for weeks and even months before the tree falls down, or a gust of wind sweeps it into the forest to catch fire.

In July of 2015, a weeks-old lightning strike ignited a fire along the shoreline of Marion Lake, also in the Jefferson Wilderness, on a blue-sky day. The column of smoke came as a shock to the handful of swimmers at the lake that day.

The same thing appears to have occurred with the Whitewater Fire.

One of the lighting strikes from the June 26 storm hit a tree near the top of Sentinel Hills, about 100 yards off Whitewater Trail, a popular pathway to Jefferson Park. 

Nobody was aware of the strike tree or smoldering spark, multiple Forest Service officials said. The agency does aerial patrols after lightning storms, but holdovers from previous strikes tend to pop up without warning.

“We can’t check every tree in the forest,” Beck said.

In any case, the lightning-struck tree eventually fell into a pile of dry brush and timber, igniting flames and sending up a smoke column spotted July 23. 

“As soon as it was spotted, we hit it with everything we had,” Beck said. “We used heavy helicopters, chainsaws, water pumps and engaged the fire directly. Our firefighters did everything they could to catch the fire before it spread.”

Fighting wildfires in wilderness areas is controversial. The Forest Service is charged with maintaining the "wild character" of the congressionally designated areas, and fires are a natural part of the ecosystem.

Many fire experts also believe decades of suppressing forest fires has made them more damaging in the long-term.

"The Forest Service acknowledges that putting out today’s fire will likely make tomorrow’s fire bigger, yet every day they still try to put out damn near every fire," said George Nickas, executive director of Wilderness Watch. "We need to stop seeing fire as something to fight, especially in Wilderness, just as we don’t see snowfall, rainfall, or wind as something to fight."

Grady McMahan, Detroit district ranger, said the agency decided to fight the Whitewater Fire because it was so early in the year and had the potential to grow beyond the wilderness boundaries.

"Our goal was to put the fire out while protecting wilderness characteristics and private land and structures," he said. "It's a difficult balancing act."

Blaze spills over a cliff

By the evening of July 24, officials knew the fire wouldn't go quietly.

High winds threw embers half a mile, starting spot fires in a forest that was bone dry. The fire grew from 50 to 80 acres, crossing the Whitewater Trail and threatening popular Jefferson Park, where backpackers remained.

But firefighters who hiked 4 miles into the wilderness, amid boiling temperatures, made progress on the fire. They built hand lines and kept the blaze limited to 80 acres by July 27.

“Hard work pays off,” said a press release from the fire. “The difficult, dirty and dangerous work by firefighters on the Whitewater Fire is starting to pay dividends.”

The problem was the terrain.

Sentinel Hills, where the fire started, sits atop steep cliffs. Late that week, winds kicked up and the fire spilled downhill, with flaming trees and boulders crashing into the Whitewater Creek valley. The fire roared down the cliffs and then burned back up it. 

Hot shot crews analyzed stopping the fire as it spread downhill, but the danger was too high.

“Once it spilled over the cliff, there was really no way of stopping it without a high risk of injury or death to the firefighters,” Beck said.

Search and Rescue teams were sent to evacuate backpackers from Jefferson Park as the fire spread to 167 acres July 30.

"You could feel the heat coming off the fire and see ash all over the snowfields at Jefferson Park — it looked like someone took a pepper shaker onto Mount Jefferson," said Jeremy Mitchell, a volunteer search and rescue team member. "We probably evacuated 25 people. I was surprised how many people were still there." 

The next day, Jefferson Park and all surrounding trails were officially closed.

"That ended up being a really good call," Mitchell said.

Wind and heat fuel flames

At the same time the fire was spreading, weather conditions went from bad to catastrophic.

The fire stayed around 167 acres for two days before growing to around 297 acres.

Then it blew up.

Fueled by high winds and temperatures in the 100s, the fire expanded fivefold to 1,500 acres and then to 4,579 acres by Aug. 3.

Smoke and ash rained down on nearby Detroit as the fire spread within a few miles of State Highway 22.

“Record-setting heat, rugged terrain and top of the fire season — it doesn’t get any worse,” said Steve Zeil, fire behavior analyst for the incident team during a meeting in Detroit.

“All the ingredients for extreme fire behavior (were) present.”

Fire teams stopped engaging the fire in the wilderness and instead focused on building containment lines on Forest Service Roads outside the wilderness.

As the fire spread beyond wilderness boundaries, the broad goal was to stop the fire from reaching highways, Marion Forks and the Breitenbush Community.

No evacuations were ever ordered, and the fire has remained 3 to 6 miles from the small towns.

Going forward

The fire has slowed its spread in recent days, growing a limited amount as weather conditions improved. 

Fire teams are now taking a more proactive approach, using controlled fire on containment lines to starve the blaze of the fuel it would need to grow.

With rain in the forecast, there's hope fire activity will tamp down enough to stop smoke from obscuring the sky during eclipse day.

More eclipse coverage: Here’s the weather forecast for Eclipse Day in Salem

Still, no matter how much the fire improves, Forest Service officials aren't considering re-opening Jefferson Park for the big day.

"One little rainstorm might slow it down, but it will still be a large, active fire that has behaved erratically this entire time," McMahan said. "I couldn't sleep at night knowing there were a hundred or a thousand people near a fire that with one strong gust of wind could turn things sideways in a moment."

Whitewater Fire acres by the day

July 25 - 50 acres

July 26 - 80

July 27 - 80

July 28 - 89

July 30 - 167

July 31 - 168

Aug. 1 - 297

Aug. 2 - 1,500

Aug. 3 - 4,579

Aug. 4 - 4,800

Aug. 5 - 5,206

Aug. 6 - 5,421

Aug. 7 - 5,515

Aug. 8 - 5,515

Aug. 9 - 5,580

Aug. 10 - 5,844

© 2017 KGW-TV


JOIN THE CONVERSATION

To find out more about Facebook commenting please read the
Conversation Guidelines and FAQs

Leave a Comment
TRENDING VIDEOS