Saturday, May 31, 2025

Biking the White Rim Canyonlands Trail With Young Bucks

Introduction

Every year or so I get together with my friend Peter to do a monstrously difficult bike ride. This year would have been in celebration of forty years of friendship, except that neither of us actually noticed this milestone at the time. (I did just now.) Just to mix things up, we brought along Pete’s son H— and two of H—’s friends from the Colorado State University cross-country running team. This is a little bit like inviting Godzilla to your garden tea party with his pals  Megalon and King Kong, expecting them to sip daintily and take just a few cucumber sandwiches instead of trampling everything. If you like the idea of me suffering, well, read all about it right here.



This was a one-day assault on the Canyonlands White Rim Trail, which Strava says most riders complete in two to four days. Pete had done it in three days with H— a couple years back, and this spring H— decided it would be a pretty good idea to hammer it out in one. (So honestly, it was me being brought along as an afterthought.)

Executive summary

As I’ve mentioned before in these pages, I’m not a big astronomy fan. The old cliché about staring up at the stars and saying, “Kinda makes you feel insignificant, doesn’t it?” doesn’t seem that profound to me, because all kinds of things make me feel insignificant (like being middle-aged, and an empty nester, for starters). I don’t need to travel to some remote place where there’s no light pollution just so I can feel like a trivial little speck.

Meanwhile, I learned through this exercise that if you travel to a sufficiently isolated place—in this case Canyonlands National Park near Moab, Utah—you can be so dwarfed by giant reddish rock formations towering above you that you never need to see the celestial heavens again, if feeling insignificant is your thing. In the photo above, look how Peter (the farther-away dude, in black) is so diminutive compared to the rock wall next to him. (If you can’t even make him out, click the photo to enlarge, which goes for all the pictures in this post.)

And yet, this being by far the longest mountain bike ride of my life, I feel like my Man vs. Nature battle didn’t come out so very badly. Despite a protracted ordeal in an unforgiving landscape, I find myself “still alive and bitching” (to quote the philosopher king Marshall Mathers). You might be alarmed to know we were out for almost 11 hours with virtually no shade but I barely noticed … we had far bigger difficulties to surmount than that. For example: the CSU brat pack; the relentless pounding of our tires over unforgiving landscape; and the formidable Shafer climb (starting at mile 75). If all you care about is the fact of us pulling this off, congratulations, this Executive Summary is all you need, and you can click here for dessert. Otherwise, read on for the gory details!


Short version

Dinner the night before, at our AirBRB (a nickname I’ve just coined, I think), was De Cecco pasta with trailer-trash sauce. This sauce is made by sizzling some crumbly house-brand Italian sausage in a pan, glugging some jarred sauce in there, and heating it up. Since I drove like a thousand miles for this get-together, I splurged on some weirdly high-end sauce that’s like $10/jar. (Did I pay that? Of course not. I had a digital coupon or something.)

I slept poorly the night before because a) I’d eaten way too much pasta, and b) during the two-day drive out to Moab I adopted an all-taqueria-all-the-time approach to dining, so I had percussive flatulence all night, loud enough to wake myself up (and probably some of the 100 or so species of arthropods we can presume were sharing my room, if this dwelling was typical). Did I regret all that Mexican food? No. Not even considering the long hair I found in one of my burritos, which was from a forlorn taco truck in the middle of a giant dirt lot in a remote part of Provo. I kept pulling on that hair and it just kept coming, like a magic trick. And yes, I did finish that burrito. Think of how many hairs are discovered and removed just before restaurant food is served, or hairs that we actually ate, unawares, because we were eating too fast. (Or is that just me?)

My breakfast on ride day was a seriously overripe banana (peel almost black) with peanut butter, and coffee blacker than the banana peel. The AirBRB had a coffeemaker, but they’d stocked the wrong size filters, so it’s a good thing I brought my own pour-over cone and filters from home (along with my standard-issue ground Peets). These items had saved me at the motel the morning before as well, where the only teabag-style “coffee” they provided for their stupid coffeemaker was decaf. I’m strongly considering bringing ground coffee, my cone, and filters with me every time I leave the house from now on.

During the ride I ate an untold number of Clif and Kind bars, washed down with about nine  or ten bottles of water. Knowing the precise number of bars wouldn’t properly document the actual caloric intake, because there’s a lot of chocolate in a Kind bar, most of which melted due to the desert conditions and couldn’t be extricated from the wrapper. I felt kind of foolish eating these bars because all of my riding pals ate almost nothing but peanut butter and jelly sandwiches. I really need to get in on that.

By the time we finished the ride, showered, limped back out to the cars, and drove into Moab for dinner, not much was open. We hit the Moab Grill which was still hopping. I knew as soon as we sat down that a) I wanted wings, real bad, and b) Pete would refuse to have anything to do with them. He’s above wings, apparently. We’ve argued bitterly over it in the past, sometimes after brutal bike rides such as this, and never order them. (It’s not that I couldn’t eat a whole plate of them by myself with no appreciable dent in my appetite; it’s that they’re meant to be shared. Solo winging would be like drinking alone.)

Of course we had the three young bucks at the table, but what if H— took after his old man with the buzzkill no-wings-ever policy? And what if the other two dudes, G— and T—, were, like, vegans or something? You never know with elite athletes. So I tentatively asked, “Would anyone be into getting an order of wings?” G— grinned and said, “That’s practically I’ll I’ve thought about for the last two hours.” Score! God, those wings were good. Buffalo style, with ranch, of course. I miss them. I just love how you can shove an entire wing in your mouth and then zip the bones out in one motion, leaving all the delicious meat to be exuberantly chomped. I also had a Reuben that was pretty darn tasty, on marbled rye that the waiter specifically recommended, with hella fries dragged through mayonnaise. I also inherited like half of H—’s “Dyablo” burger (jack, bacon, jalapeños, roasted red peppers, hot sauce) that was super good despite the misspelling. I don’t know what is wrong with that kid that he doesn’t even finish his burger after a 105-mile mountain bike ride, but at least he likes wings. And it’s not like I’m complaining about the secondhand food.

The really messed up thing is that I’d brought a four-pack of Fieldwork IPA all the way from California to drink with Pete après-bike (or should I say après-vélo?), but we were so shattered from the ride, we just didn’t feel like drinking. And we didn’t. Okay … now are you getting a sense of how hard this ride was?


Long version

This long version is truly long, even for an albertnet post. What can I say? It was a long ride. If you think reading this is hard, go try riding White Rim sometime.

You may have noticed from the map above that there’s almost nothing on it but the crenulations representing topography, and one little actual paved road, that being Country Road 143 that we were on for a few miles. No towns, no trailheads, no warming huts, no bailout roads to civilization. Granted, if the map were more complete it would show the little visitor’s station we stopped at, ~80 miles into the ride. Other than that there was just nothing and almost nobody. But we had each other.

Wait, did I just imply that having each other was a good thing? Honestly, endeavoring to keep up with three NCAA Division I cross-country runners is one of the dumber things I’ve ever done. Yeah, sure, they were on bikes, which is more Pete’s and my thing, but then, fitness is fitness, and youth is youth. Plus, they had their inevitable rivalry, leading to irrationally exuberant accelerations. For the first 40 miles, it was more or less a death march hanging on for dear life behind them. It wasn’t just hard physically (I mean, duh) but psychologically too … I kept thinking, wait, we’re only 20 miles in  and the temperature is climbing and I’m already suffering and shouldn’t I be saving some energy for later, and specifically for that monster climb, instead of accepting this breakneck pace? I didn’t realize until I looked at the bike computer data afterward that these first 40 miles were almost all uphill. That’s because everything is so  wide open, you can’t get a sense for gentle gradients. I just thought it was the rough terrain and the pace that were making it so hard.

Obviously it’s only the shallow climbing that’s invisible. It’s pretty hard to miss a steeper climb like this one:


That’s the Green River in the background there, BTW.

Climbing on a road bike, on asphalt, is hard enough, but at least that’s just a matter of turning the pedals. On a really rough trail—and I was surprised how legit and rocky and complicated a lot of this trail was, compared to the dirt road I’d naïvely imagined—you also need to steer around the bigger rocks, bumps, etc. because at such low speed, they can stop you cold. Sometimes you can’t avoid an obstacle and have to use body English to pop your bike over it, one wheel at a time. Meanwhile, the whole time you have to lean really far over the front wheel or else it’ll lift up off the ground (even if only slightly) at which point you lose the steering and your brain shuts the whole operation down so you unclip from the pedals and are dead stopped. Riding with your weight this far forward, you have barely enough traction on the rear tire, so it slips from time to time, costing you priceless forward momentum. Add in that you don’t know how long the climb goes on, and it’s hard to have faith you can make it to the top.

Sometimes we did give up and walk our bikes, which was a major letdown. For example, check out the pitch shown below, coming at the end of a prolonged section of brutally tough climbing. Pete almost made it. I was maybe 2/3 of the way before realizing (or at least imagining) that if I waited until the even steeper bit ahead to bail out, my shoes might slide out from under me. Pro tip: as you start to walk your bike, grab the rear brake to lock that wheel, or the bike will drag you backwards down the slope.


By the way, the shade you see in  the above pic is almost all we got the whole day.

We started getting some nice downhills. I don’t mean the super-steep technical ones where you’re hanging your ass over the rear wheel to keep from face-planting (though we did get those too, and they were glorious) but the more relaxing easy ones where all you have to do is steer around the larger rocks (because who wants a flat tire or other mechanical out in the middle of nowhere?). Unfortunately it’s really hard to take photos or make movies while doing these, but one of the young bucks somehow managed:


It was bumpy enough that I lost five bottles, only four of which I managed to retrieve. Three losses were from the side pockets of my CamelBak. I didn’t use the bladder with it, because I needed room for tools, the first aid kit, food, and five water bottles. (If you’re interested in everything a seasoned mountain biker has in his pack, click here.)

The trickiest part of these downhills was that you’d occasionally hit soft sand, which can sometimes seem to grab your wheel and twist it, so your bike starts to jackknife. Gave me the heebie-jeebies every time.

We stopped for rests periodically, especially in the more scenic places like this chasm we peered into.


Here is our lunch stop. (This happened to be around 1 p.m. but really, every food stop was lunch. It’s like when you’re in the grocery store checkout at like 4 p.m. and the manager says to your cashier, “Go take your lunch now.”) Look at H— peering at his PBJ. He’s probably thinking, “Come ‘ere, you.”


At around the southeastern-most point of the loop, at say 5 o’clock (i.e., the position of a hypothetical minute hand on a clock, not the actual time), several of our phones chirped because we randomly had a cell signal for the first time all day. We stopped and fired off some emails, because after all this was a workday. Kidding! But I did snap the below photo and texted it to my brother, and he actually got it!


By the time I tried to send the same pic to my daughter, the signal had evaporated. Probably it had been bounced off a passing jet, maybe even a spy plane, and was a flash in the pan.

I was about to type a thousand words about how majestic and architectural the landscape was, but instead here’s another photo.


If you’ve ever wondered how these formations got to be how they are, and especially if you’re a female reader, let me explain (or mansplain) it all from a geologic perspective. Wait! Come back! I was kidding! I have no idea how this land got to be this way. I’ve had it explained to me half a dozen times over the decades but I never listened. It’s complicated. Something about sedimentary, igneous (or is it Ignatius?) deposits, once submerged by an ancient ocean, or was it crushed by a glacier? I actually have no idea.

You might be wondering: does Canyonlands have anything to compete with the amazing pupfish of Death Valley? Well, not that I saw, but there were occasionally these darling little cactus flowers. (Bike tire included for scale.)


I count at least two or three species of insect in there. It’s like a big bug party in the desert!


While we were stopped for that photo and some chow, an SUV rumbled slowly by. A puffy middle-aged woman was in the front passenger seat and gave us a bored glance. She was wearing one of those ring-shaped neck pillows people use on long airline flights. Perhaps she was just doing this drive for the commemorative bumper sticker and couldn’t wait for it to be over (though that’s exactly what she was doing).

At around mile 60, an inventory of pain had assembled itself in my brain and my inner voice was whining. My back hurt (mainly from the strain of climbing). My right collarbone hurt where the strap of the (overloaded) CamelBak was pressing down, because of the heads of the screws holding the plate in there that fixed my once-broken collarbone. All my toes felt broken, which tends to happen on really long rides (despite my excellent footwear). Perhaps most of all, my hands hurt from my bike’s continuous impacts with rocks and hard-edged slabs we kept bumping up on and down off of. I’d brought long-finger cycling gloves and short-finger ones, the former without padding and the latter with gel, and ultimately opted for the long-finger. I don’t know what I was thinking … they’re just what I normally wear mountain biking, for protection against poison oak. But was I going to find that here? (I can sense you shaking your head.) I couldn’t switch to the padded gloves because G— had forgotten his gloves and was thrilled I had a spare pair. Would it be a dick move to demand that he trade with me now? Yeah, it would, dang it. So my palms were really raw. Have you ever gotten a little overexcited while tenderizing a pork chop, working out some demons perhaps, and you realize the meat has become so roughed up and soft it’s almost like moss? That’s how I imagined my hands had become.

Eventually we made it to the base of the dreaded Shafer climb. G— and H— took off ahead, ostensibly to make it to the ranger station before it closed. We didn’t actually know its hours, and it was already 4:30 p.m. with zero chance of getting there before 5 anyway, but the young bucks were out of water and thus desperate. Here’s Pete looking back at me as if to say, “Okay, they’ve got enough of a head start. I’m going hunting … see you at the summit.” The look I returned, as I snapped this photo, said, “Release the hounds!”


(Full disclosure: Pete’s look back surely meant nothing of the kind, nor did my return glance. I’m adding these subtexts only now, to give this report some drama and the shimmer of fiction.)

In the photo above, if you look straight up from the top of Pete’s head (zoom in!), you can see the switchbacks we would have to face.

Pete’s chase was swift and ruthless. The climb was ruthless but not swift, not for me. This next photo is from two minutes later. Not only has Pete caught H— but look how far ahead he is of me! I think I even used my camera’s zoom for this shot!


I rode my own pace, having released myself off the back on my own recognizance as I so often do. I know better than to try to run with the bulls. Here’s a little video documentary I made.


If you pause video that near the beginning to look at my bike computer readout, you’ll note I was going only 4 mph. Go ahead, mock me … but also consider the grade was 14%. (See what I mean about the wide open topography making the grade look shallower?)

Almost twenty years ago, my wife and I did a mountain bike vacation in Moab and, for shits and giggles, took a sunset river cruise narrated by a quasi-historian. The script he read from was cheesier than all-you-can-eat fondue. Our favorite line, delivered toward the end after a long pause (calculated to build suspense, I suppose), was, “And now, in the darkness of night, we ponder the legacy that is ours.” So pompous, and so meaningless! My wife and I like to trot out that utterance from time to time. And perhaps pondering our legacy is what G— was doing when I came around a bend to see him stopped.


Or maybe he was just enjoying the shade and taking a breather. I’d kind of been counting on these runners to eventually tire so they’d ease up on us. I’d asked beforehand how long their longest event is; it’s the 10K which takes them like half an hour. Obviously their training runs are longer, but then nobody runs for eight or nine hours at a stretch … and yet this kind of duration is typical for Pete and me on our monster rides. (Our 2022 slogfest took 8:37:47 and our 2023 gravel adventure took 8:37:32.) H— , T—, and G— are like greyhounds, whereas I’m more like a lobster lumbering across the ocean floor. As I distance cyclist I am kind of made for this, or more to the point I kind of made myself for this. We’d only ridden for six or so hours; I was just starting to find my groove.

I could still see Pete and H—, utterly dwarfed by the canyon wall.


The landscape was so literally awesome, so  sublime, that I kept trying—but always in vain—to  capture its grandeur with my phone camera. Perhaps my best effort is this accidental video, that was supposed to be a still photo. Though it’s obviously pretty sloppy camerawork, I think it captures the feeling of this climb better than any of my stills.

Switchback after switchback, the climb went on and on. Obviously I was suffering hugely, but at least the trail was smooth here and I settled in to a rhythm of sorts. If you read my posts from my epic French Alps cycling “vacation,” you’ll understand my point when I say this kind of suffering is the devil I know. (If you missed that series, cancel all your meetings and click here.) I felt like I could pedal like this all day, and probably would. At least it was easy to appreciate the progress I’d made, as shown by this photo. (SUV and T—, or maybe it’s G—, included for scale.)


Just before the summit of the climb, I caught Peter and H—. (The only explanation for this is that H— was hurting and had slowed down, and Peter hung back for some quality father/son time, to witness the lad’s suffering.) At the top, H— wobbled off the trail, set down his bike, and lay down on the ground to rest. Pete and I rode a couple miles to the Visitor’s Center to see about water. It was closed but had a spigot and we filled all our bottles. Bringing them back to the young bucks gave me a welcome paternal feeling, and I reconsidered my earlier plan to file charges of Elder Abuse against them.

We woke up H—, topped up everyone’s bottles, and set back out for what we thought would be a 20-mile descent, the first five miles or so being on actual asphalt. Instead it was rolling (if mostly downhill). That might not sound too bad, but each time the road tipped upward, it was like a slap in the face. Our group broke apart and regrouped a few times and over the last few miles I did some quality wheel-sucking behind T—, who’d caught a second wind at like mile 95. At one point I actually hallucinated and thought I saw buildings, like a small town, in the distance, indicating that we’d made a horrible navigational error and were screwed. “Do you see those buildings down there?” I asked T—. He looked at me as though I were crazy, which I suppose in the moment I almost was.

Eventually we reached the cars, our ride actually done, and busted out the cooler. There were only three Cokes, which were snapped up by the lads, but Pete and I were happy to make do with beers. Here is our official post-ride Beck’st:


Fortunately Mother Nature had put out some nice furniture to relax on. I love how, in this final photo, H— appears to be deep in thought, doubtless pondering his life choices and how he ended up here.


I can’t wait to return next year. With an SUV. And a neck pillow.

Stats

  • 105.1 miles
  • 8:44:05 ride time
  • 12 mph average speed (really not bad for mountain biking…)
  • 7,283 feet cumulative elevation gain (based on Pete’s Strava, presumably more accurate than the bike computer value shown above)
  • 6,207 feet maximum elevation
  • 120 bpm average heart rate
  • 157 bpm max heart rate
  • 4,316 kilocalories burned
—~—~—~—~—~—~—~—~—
Email me here. For a complete index of albertnet posts, click here.

1 comment:

Anonymous said...

Love the beer pic!

Post a Comment