Ascent of Lost River Mountain on 2016-08-12

Climber: Paul Lind

Date:Friday, August 12, 2016
Ascent Type:Successful Summit Attained
    Motorized Transport to Trailhead:4x4 Vehicle
Peak:Lost River Mountain
    Elevation:12078 ft / 3681 m

Ascent Trip Report

Took Sean Williams with me in attempt to find the best traverse S-N from Lost River Peak to Breidenbach Ridge. Went up Super Gully to get up top. As always, the left side has best rock to get out of scree field on the way up.

On the traverse we cliff'd out pretty quickly but work our way around to the west side, then back up top and snaked down a couple pretty technical class 4 drops. The crux is a vert-vert down-up that is pretty sketchy. I can see why Nate found this route easier than Luke/Jarod did going N-S, as going S-N you see the up you have to take, where going the other way it just looks like a cliff-out all around. It will be the toughest part of the climbs on the 12'ers 36hour attempt next weekend.

And the final block of cliffs (so the first ones coming from Breidenbach going N-S), it is easiest to just suck it up and drop a couple hundred feet and go around through the Lost River class shit scree and then come back up to the ridge.

We dropped out of Pete creek, which has even more stinging nettle in the upper end than in the past.

NOTE: wanting to drop out the scree chutes early is NOT an acceptable alternative- major cliff out drops. Gotta to all the way towards the waterfall. I did drop through the final scree chute before the waterfall which was fine. Came out drainage and ran back to truck which was parked at the base of the Super Gully
Summary Total Data
    Quality:8 (on a subjective 1-10 scale)
    Route Conditions:
Unmaintained Trail, Open Country, Bushwhack, Scramble, Exposed Scramble, Rock Climb
    Weather:Pleasant, Calm, Partly Cloudy
Ascent Statistics
    Route:Super Gully - left side
Descent Statistics
    Route:Pete Creek

This page has been served 315 times since 2005-01-15.

Copyright © 1987-2020 by All Rights Reserved. Questions/Comments/Corrections? See the Contact Page Terms of Service