In my last post I promised an update when I hiked Camelback Mountain. But I never promised when!
Well, I actually did that first hike the day after my last post - on May 15. So why has it taken me this long to finally write about it? Was I so tired it took me this long to recuperate sufficiently to type again? Or was I procrastinating? Or just lazy? Or too busy doing other things? I'll let you speculate.
May 15 actually turned out to be a triathlon for me - a run, followed by hiking Camelback, followed by a bike ride, and the above calorie and mileage count is the sum total of all three.
For the run I did 4.63 miles through the local neighborhoods before sunup, taking about 51 minutes and burning 672 calories. But that was nothing special and I'm sure you're more interested in hearing about Camelback, so I'll get to the point.
Wow. The first thing you need to know about hiking Camelback is that there's a bit of a preliminary hike involved as the nearest parking is a third of a mile away - with a respectably uphill walk all the way to the trailhead. So when you start, you're already well warmed up. The trail actually starts out deceptively easy at the beginning, but then gets progressively more challenging as you go on, due not only to increasing grade but increasingly challenging terrain, with rocks and uneven and potentially slippery surfaces.
On Sunday morning when I did this hike, the trail was CROWDED with other people - which I expected and which I had planned and hoped for (all the better to have several other moving bodies on there to scare away any rattlesnakes or bobcats from my path - or to be aware of my disappearance if a slip sent me down one of the steep dropoffs).
What was really interesting to see was the wide variety of styles employed by all these other hikers. Most people moved along with a steady speed and reasonable caution. But at the one extreme was a smaller percentage of more hardy souls who actually jogged up and down these slippery rocks with the same nonchalance that might have been expected had they been on level asphalt. A large number of these were teenagers obviously still blissfully ignorant of their own mortality.
Finally, at the other extreme was an old fart in gray hair, a first-timer, who proceeded with all the alacrity of a snail swimming through a pool of molasses, occasionally down on all fours to carefully steady himself against any possible slippage, and spending half of his time moving to the side every time one of these joggers-with-a-death-wish approached. Yep, "the snail" was none other than yours truly, and it didn't bolster my confidence one bit as I watched a helicopter rescue some other hiker from somewhere on the other side of the mountain. But on the bright side, all my diligent caution paid off and I'm still here and alive to blog about the experience, and to post the pictures I took of the elements I was up against:

I'd like to say I made it to the summit, but that is an achievement that is probably going to require the experience of many more hikes before I feel comfortable enough attempting it. If I ever do. As it is, what I did accomplish was a more than ample workout, and trained and developed muscles I previously didn't even know I had. Even though I only made it probably about two-thirds of the way up this Beast of a Camel, I did still capture some impressive views of Paradise Valley and Scottsdale:
All in all, the round trip hike took a total of an hour and 35 minutes, and when I got back home I replenished with a quick lunch before heading out on a 3 hour, 8 minute, and 32 second marathon bike ride almost down to Tempe (1125 calories, 26.63 miles). Hey, it wasn't as bad as it might sound - after all, it did use different sets of muscles!
My next goal is literally a bit more lofty - and I hope to meet it tomorrow and then write about it (but note, once again, I'm not saying WHEN I'm going to write about it!) See those mountains in the background of the second picture above? Those are the McDowells. And see the highest peak in the middle of those mountains? That's Thompson Peak. I'm going to try to get there tomorrow morning. I ran pretty close to that area earlier today while on my now-almost-routine 9.5 mile Saturday morning run. I've researched The Road To Thompson Peak over the last couple of days, and learned that it's a 4.5 mile road (over 9 miles round trip), and I'm planning to walk that road to the top tomorrow morning. On the bright side, it's allegedly a vehicle-quality unpaved but relatively smooth road. There shouldn't be any back-breaking boulders to scale. And if there are any bobcats or rattlers they should be relatively easy to spot ahead of time. Walking, the round trip should take me about 3 to 3-1/2 hours. Wish me luck. And stay tuned for the statistics and the pictures!
(Oh, and Mom? The top of Thompson Peak is LOADED with cell phone towers. And I'll have my iPhone with me. So if a bobcat does come after me, I'll be sure to call and let you know).