keep it simple

I'm sitting in the airport in Charlotte, North Carolina right now waiting to board a plane back to California. I've been out here all week for work, and managed to squeeze in a mountain bike ride on Tuesday.

I rode with a guy I know who lives here. Turns out my timing was perfect, because for the last 15 years or so, he's been organizing a Tuesday night ride with his friends. One of the guys owns a local bike shop and hooked me up with a bike - the Kona Hei Hei.

This bike, in many important ways, is the exact opposite of my mountain bike at home. This bike is full suspension - mine is a hardtail. This bike has gears - mine has but one. Needless to say, it took me a while to settle into it.

The group turned out to be a big one - larger than I have ever ridden with - 14 guys. There were a few guys named John, so by about the middle of the ride I was calling everybody John. They didn't care, and in return they called me the "new guy." During the ride we lost three Johns, because one of the Johns crashed real good and it took two other Johns to get him out.

We rode a great trail at the National Whitewater Center.

I was impressed with a couple of things on this ride. First, this group hammered the entire time. We started off fast with few stops and never slowed down. In an hour-and-a-half of riding, we stopped less than five times to regroup. That's rare in a group ride this big, and due to the fact that they ride so often together, I reckon. I was also impressed with the quality of the trails we were riding. Fifteen miles of singletrack with lots of climbing and tight turns. Didn't hurt that it was also a full moon that night.

So now the big question...do I want to go back to a geared, full suspension bike? The answer is a solid "no", and that makes me happy. Keep it simple.

conquered U-Conn trail today

I went for a mountain bike ride early this morning.

The skies still had the usual morning fog as I rode down Hwy 9.

I made it up the U-Conn trail without stopping today - 1.85 miles of singletrack on a 6.5% grade on a singlespeed. It felt good. I think the reason I made it is that I set up my GPS to show my heart rate. The last few times I've climbed U-Conn I've noticed that the limiting factor is cardiovascular, not muscular. My legs are strong enough to make it, but I feel like my heart is going to explode. So today, I strapped on the heart rate monitor to see exactly how hard I was working as I climbed. My maximum heart rate is 183 bpm (220 minus my age). As I was climbing the lower section my heart rate topped out around 167 bpm. Then, at the technical and steeper section near the top, my heart rate maxed out at 176 bpm. I figured I couldn't stop until I was giving over 100% (and what exactly would my heart do if it went over 183 bpm, anyway?). Before I knew it I had made it to the top. Here's the entrance to the U-Conn trail, off of Hwy 9.

I explored more trails, logged more waypoints on my GPS, and was bummed to find out when I got home that I never started the GPS. So all of those points aren't saved and I won't get to see my heartrate for the climb up U-Conn.

I do know that I rode for over 2 1/2 hours, covered 22 miles, and climbed over 2,000 feet.

I'm thinking about changing the rear cog on my mountain bike to one with a few more teeth, in order to make climbing easier. Riding a singlespeed definitely makes you a better climber, but it also wears me out faster. I'd like to be able to do longer rides over time, and I think that having an easier gear ratio will conserve energy for longer rides. The downside is that on flats and downhills, I'll start spinning earlier and won't be able to go as fast. We'll see.

You can barely see the trail, but it's there:

Spiderweb:

Singletrack:

like Disneyland

Yesterday I took a step towards my goal of finishing the week strong on my bike.

I left work a couple of hours early because it was slow and we were all caught up, got home and took Greta for a long run in the woods, then jumped on my mountain bike and rode down to the Rincon parking lot to hit the trails around UCSC.

Since I didn't want to drive to the trails, I was on Hwy 9 the four miles to the trails. My legs were stiff and my heart didn't really want to keep up with what I was asking it to do. I thought about turning around, and had a great excuse lined up in my head: "Clay, you've been up since 2:50 this morning. Just go home and relax. If you're not into it on pavement, how are you going to make it on the trails? And do you really want to do that climb to get to the top of the U-Conn trail?" Actually, that's three excuses.

I think it's worth exploring how I talked myself through this.

I started with the most common rebuttal - that, like a lot of endurance sports, it often takes a few miles to "settle in." I've experienced it on long-distance paddleboard events, I've heard other cyclists say it, I've heard Adria say it about her long trail runs, and even when she goes backpacking. Once we let our bodies take over what they really want to be doing (moving), our minds stop chattering.

The other rebuttal I used with myself to stay on my bike was a reminder to myself that the more miles I put in, the more money I raise for the people at the Homeless Garden Project. I stopped by the Garden a few weekends ago and met two people who work there. I'll post about that this weekend.

My final rebuttal was sitting about 16 inches below my face - my GPS! There was no way I was going to turn around after three miles!

So by the time I made it to the bottom of the U-Conn trail, I was nice and loose and my mind wasn't chattering. I climbed to the top of U-Conn, but still had to stop two times on the way. For those readers who don't live in Santa Cruz, or don't ride bikes, or haven't ridden U-Conn trail, there a reason why I am so fascinated by this trail. First, it's beautiful - narrow singletrack on packed dirt with some moderately technical sections, all under redwood trees. That, combined with the fact that it's f'ing steep!! If my math is correct it's a 6.5% grade for 1.85 miles. That and that, combined with the fact that I ride it on a singlespeed. Last season, when I was riding trails more, I was able to easily climb this trail without stopping. I think I'll get back there soon.

After the climb I played around on a lot of the same trails that I was on last Saturday, just reinforcing the way the trails link together. Another one of my biggest challenges is learning how this trail system is laid out. There's no published trail map. Some of these trails are "unauthorized" (i.e. illegal). When I ride with my friends on the trails, I'm impressed with how they link the trails together - we can ride for hours and never be on the same trail.

After about an hour of riding the same trails as last weekend, I explored some trails that branch off of these and saw how these new ones link up. I saved the locations of new trailheads on my GPS to help visualize it. I think what I'm going to discover when I plot all these trails on my GPS is that these woods are like Disneyland - lots of smaller sections of trails linked together to form one giant network of fun.

The condition of the trails was excellent - super tacky from the recent rains, but not muddy. And the heavy winds of the storm made it look like someone took a buzzsaw to the forest.

Today I'm going to ride down to Santa Cruz to run some errands, then do another mountain bike ride on campus. That should be about 40-50 miles. I need to make sure that I eat well all day to sustain.

Saturday mountain bike ride

One of the many great things about living in Felton is that I am so close to epic mountain bike trails. This really sunk home a few weekends ago when I drove for an hour and half, round trip, to ride Ft. Ord. I don't regret the ride, but it reminded me that I've got is so good at home!

So on Saturday morning, under the cover of rain clouds and fog, I rode down Hwy 9 towards the Rincon parking lot. Normally, I'm riding down Hwy 9 at 6am on my commuting bike, going to work. Riding a different bike, my single-speed 29'er, made it feel new.

After a 30 minute spin on asphalt, about 4 miles, I reached the trailhead and started the long, steep climb to the top of UCSC (see the profile below at mile 4). I played around on the intricate trail system for about an hour and a half - mostly just re-riding a short loop section, working on some technical skills. I also mapped a lot of trailheads on my GPS so I could find them later.

Fort Ord - misery on a single-speed mountain bike

On Saturday morning, I drove about 30 miles south of Santa Cruz to explore the trails of a place I have heard a lot about, but never ridden - Ft. Ord.

Ft. Ord, an infantry training center for the first 80 years of the 20th century, is now de-activated for military training and is open to the public. The Bureau of Land Management has created a network of multi-use trails that are free to the public.

It took about 45 minutes to get to the trailhead. As I was driving south on Hwy 1, I was excited about the prospect of riding in a place that warned of mountain lions, rattlesnakes, and live explosives in public areas!

An excerpt from one of Ft. Ord's websites:

>Explosives at former Fort Ord

While every effort has and is being made to clear dangerous materials, 60 years of military occupation make it possible that live rounds and explosives may remain in public areas as well as posted areas.

DO NOT TOUCH unfamiliar objects, especially metal. Instead, MARK THE LOCATION and CALL THE FEDERAL POLICE at (831) 242-7851 or (831) 242-7924.

After a little exploring, I found the trailhead parking lot nestled between a residential community and some strawberry fields. I grabbed a trail map and plotted a course that would satisfy my two objectives - keep me on as much singletrack as possible AND get me close to the yellow "DO NOT ENTER" section (see map below - I had to cut the map in half to post it here...so imagine that the bottom half is attached to the left of the top half.) For reference, I started my ride at the intersection of G17 (Reservation Road) and Hwy 67.

Less than a mile into my ride, I noticed three ways that Ft. Ord vastly different than the riding do on my local trails.

First, the trails are heavily signed. I couldn't ride for more than a half mile without having to stop to consult the map to see which trail to connect with. In general, I appreciate this because it makes it makes the outdoors accessible to more people, but I found that I could never settle in enough to enjoy the riding. And yeah, I know that I had an agenda for this ride (get to the yellow zone!), so that had a lot to do with it, too.

Second, the terrain was much different. Most of the riding I do is under the canopy of redwoods where I am the smallest thing on the trail. I ride on well-packed, cool soil with rocks and roots to navigate. This day, I found myself the tallest thing on the trail - I was fully exposed to the sun as I rode next to low scrub brush and madrone trees. The trail was sand - loose and deep in many spots. The riding here, unlike at home, did not require strong technical skills - only an ability to muscle through deep sand.
In my head, I started playing a game to minimize the suffering of riding in sand. I pretended that there were unexploded land mines all around me and that I couldn't put my foot down in or I would get blown up. That game ended when I realized that I had to put my foot down in order to stop to check the map to see which connecting trail to take. Aaargh.

The third way that Ft. Ord is different than riding at home is that it was H-O-T. Great for training military troops maybe, but not so good for riding bikes. Less than two miles into the ride, I had salt streaks on my sunglasses and my hands were slipping from the grips. It did feel good to sweat, though, and riding here reminded me that as much physical exercise as I do, I just don't sweat enough. Those people reading this who don't live in Central California may be rolling their eyes right now.

All was fine until about mile six. Like an animal that gets distracted by a shiny trinket, I got distracted from my goal of getting to the yellow zone. What distracted me was a named trail - called Lookout Ridge. I figured the views would be great, so I headed in that direction. And that took everything out of me - a 7% climb for just over a mile on a single-speed in the blazing sun. But at least I was on hard-packed soil instead of loose sand. If you check out the profile, you can see the climb at mile six.

After the blood drained from my eyes, I ate two melted Snickers bars while crouching under a madrone tree. Turns out madrone trees don't provide much shade, so I scarfed and barfed in order to get back on the bike and start suffering, I mean riding, again.

I started climbing again to meet up with more singletrack and work my way towards that ever-elusive yellow zone, but quickly bonked. It was just too hot and I was running out of liquids, even though I had started with a 100 oz. Camelbak with water and two water bottles full of electrolyte fluid. Also, my paper map was disintegrating from being stored in my jersey pocket which was soaked with sweat. So I turned around and enjoyed the downhill to get back on the asphalt and head back to the parking area.

As I was driving home I realized that this is the second time in a row that I didn't perform well on my single-speed mountain bike. It reminded me that I haven't spent enough time on it recently. So I need to do more of that.