Ascent of Meade County High Point on 2011-05-06

Climber: Gustav Sexauer

Other People:Solo Ascent
Only Party on Mountain
Date:Friday, May 6, 2011
Ascent Type:Successful Summit Attained
    Motorized Transport to Trailhead:Car
Peak:Meade County High Point
    Location:USA-South Dakota
    Elevation:5460 ft / 1664 m

Ascent Trip Report

I parked at the large white boulder mentioned in previous trip reports. The stream is narrow enough to jump across in several places in this area. From there I went straight up the ridge, which was made more difficult by hundreds of trees laying on the ground. I was uncertain whether this was logging work or not. From there I followed the ridge up to where it became flat and there were marvelous views to the South. I found a rocky meadow which I thought was the highest point, but this is indeed a false summit. It is not high enough to be shown as a separate bump on the topo, so be careful not to confuse it. I then used my compass to travel Northwest through some easily navigable trees for about five minutes, until I spotted one tree that wasn't exactly big, but it was indeed bigger than the rest. Thinking this was the highpoint mentioned in other reports, I walked up to it and found a cairn just in front of it. Success!
Summary Total Data
    Elevation Gain:720 ft / 220 m
    Elevation Loss:720 ft / 220 m
    Distance:1.3 mi / 2.1 km
    Grade/Class:Class 1
    Quality:5 (on a subjective 1-10 scale)
    Route Conditions:
    Weather:Cool, Breezy, Clear
Ascent Statistics
    Elevation Gain:700 ft / 214 m
    Extra Loss:20 ft / 6 m
    Distance:0.7 mi / 1.1 km
    Trailhead:Large White Boulder on Vanoocker Canyon Road  4780 ft / 1456 m
    Time Up:28 Minutes
Descent Statistics
    Elevation Loss:700 ft / 214 m
    Extra Gain:20 ft / 6 m
    Distance:0.6 mi / 1 km
    Trailhead:Large White Boulder on Vanoocker Canyon Road  4780 ft / 1456 m
    Time Down:18 Minutes

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

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