Showing posts with label Mt. Diablo. Show all posts
Showing posts with label Mt. Diablo. Show all posts

March 15, 2014

Diablo Seco

Notices were posted: no water available until you reach the summit. Was there a contamination problem? A broken pipe?

Chalk it up to the drought. We learned that most of the water on Mt. Diablo is supplied by local springs, and they're dry.

“Thank you for stopping.” Despite his transaction with a car at the South Gate, the Ranger noticed and addressed me. As I pedaled forward, I was summarily passed by three cyclists who did not trouble themselves to stop. At the stop sign. Really, guys? It's not hard.

Charred trees and bare hillside near the top of Mt. Diablo
I had been looking forward to climbing Mt. Diablo one weekend last fall ... and then, it burned. A target shooter's stray bullet hit a rock on a hot day in a dry year. Six days, $4.5 million, and 3,100 charred acres later, the fire was contained. The enormous plume of smoke taught me that I could see Mt. Diablo across the bay, 28 miles away (in a straight line).

Six months later, we were riding through the burn zone. There were bare blackened trees next to the stone walls at the summit—the buildings had nearly been lost.

Thinking of the tower at the top of the mountain, this morning I donned a bike jersey featuring the tower on a far-away summit: Mont Ventoux. Not only was this a good conversation starter, it earned me some respect: not one patronizing comment about being “almost there” as I slowly made my way to the top.

My bicycle at Mt. Diablo State Park North Gate entrance sign
I felt so good at the summit, I decided to descend the mountain to the North Gate and climb back up to the junction before returning through the South Gate. The rest of the group had made a longer loop, to Morgan Territory; I didn't have the stamina for that distance.

The north side was more exposed. The day was warm, and the sun higher in the sky. Long before I reached the gate, I began to wonder ... what had I been thinking? What might have been, simply, a lovely day would now be a suffer-fest. I should have topped off my water bottles at the summit.

I peeled off my knee warmers, slathered on another layer of sunscreen, and started climbing. Forty-four miles, some 5,600 feet of climbing. It was worth it.

Field of California poppies overlooking distant hills

November 14, 2009

Top of the Mountain

Before the start of today's climb, a Low-Key regular from Team Spike asked what I thought my time would be. My guess?
About 100 minutes.
His reaction?
That's a long time to suffer!
Those words were echoing in my head at mile nine, 82 minutes and more than 2700 feet into the climb. I was working hard and my pace was slowing. Why was I doing this, again? I was not an athlete when I was young, and I am no longer young. Is it pure folly to push myself to the edge for a solid 100 minutes, or more? The final steep stretch to the finish loomed large in my mind's eye.

It was a trick of the hill that summoned such dark thoughts. Looking at my data post-climb, I can see that the gradient increased at that point. This was my fourth trip to the top of Mt. Diablo, so the nuances of the ascent are not familiar. The gradient of North Gate Road averaged a moderate 5.4%, but the road to the summit averaged 7.1% (with the penultimate mile at 8.3%).

When I reached the base of the final stretch, it didn't look as steep as I remembered. Steep? Yes. Difficult? Yes. Crazy steep? No! The biggest challenge was dodging a dad with a stroller and several errant children who should have been on the footpath, not on the road. The oldest child had noticed our "200 paces" sign and was counting them off.
Eighty-three, eighty-four ...
Would I reach the top before one of her siblings ran into me and toppled me over? Yes.

My results: 106 minutes, 42 seconds to climb 3,525 feet over 11 miles at an average heart rate of 173 beats per minute. My heart rate peaked at 185 on the final stretch, comfortably lower than my last assault on the summit (192 bpm).