Snowsports

Kachina Peak reopens at Taos Ski Valley

Announcement comes three weeks after deadly avalanche

By John Miller
jmiller@taosnews.com
Posted 2/10/19

Over the weekend, skiers and snowboarders who had waited out the closure posted photos to social media to mark the reopening of the mountain's 12,481-foot peak.

 

You have exceeded your story limit for this 30-day period.

Please log in to continue

Log in
Snowsports

Kachina Peak reopens at Taos Ski Valley

Announcement comes three weeks after deadly avalanche

Posted

Taos Ski Valley's Kachina Peak has reopened a little more than three weeks after a rare inbounds avalanche killed two skiers there last month.

Over the weekend, skiers and snowboarders who had waited out the closure posted photos to social media to mark the reopening of the mountain's 12,481-foot peak.

Chris Stagg, the resort's vice president, said the peak's challenging set of steep runs, cliffs and couliers was reopened for hikers on Saturday (Feb. 9).

The lift was running the next day, drawing crowds to the mountain's high point.

The area was temporarily closed on Jan. 17, the day an inbounds avalanche started in a chute  and swept two skiers under the snow, killing them both. The Kachina Lift had opened for the season only a few days earlier. The avalanche was the first to take lives inbounds since the resort was founded in 1955.

On Monday (Feb. 11), the ski lift was closed again due to high winds and heavy snow, Stagg said.

Over the past few weeks, the mountain's ski patrol team conducted their standard "control work," which involves detonating explosives and traversing the snow in order to reduce the risk of a slide.

Officials at the ski valley said the same precautions were taken early the morning of the fatal avalanche last month.

While the U.S. Forest Service continues to conduct a review of what might have caused the accident, the ski valley has declined to provide further comment on the tragedy or what policy changes it might spur at the resort.

Comments


Private mode detected!

In order to read our site, please exit private/incognito mode or log in to continue.