Previewing the 2017 Route 66 Marathon

The start of the 2015 Route 66 Marathon. (Route 66 Marathon photo)

It’s mid-November, and that means we’re in the heart of fall race season. Where I live, it also means the Route 66 Marathon is upon us.

This is one of the biggest races in the state and region, and it’s one I’ve been running every year since 2013. A lot of people in the Tulsa area and beyond are going to be in this one – several thousand, in fact – and the race is shaping up to be a good one.

If you’re running this one, listen up. I’ve got some information about the event you’ll want to see, and a detailed course description for all of you running the full and half marathon races. So, here goes…

First off: the packet pickup and expo. The expo takes place at the Cox Business Center in downtown Tulsa. You can pick up packets for your race from 11 a.m. to 8 p.m. Nov. 17 and 10 a.m. to 6 p.m. Nov. 18. At the expo, there are going to be a ton of vendors, speakers and a bloggers’ forum. If you’ve got time, check ’em all out.

Second: Let’s talk about the course. It’s the same as it was when the race changed its format to finish in the Tulsa Arts District downtown, right by Guthrie Green.

The marathon and half marathon follow the same initial loop right up into the 13th mile, when marathoners head out of downtown for their second loop. Here are some things you need to know…

Don’t be fooled by that first mile. It’s mostly downhill, so it’s fast, and the excitement of the race will amp up a lot of people’s paces. Soon after reaching 15th Street, you will meet a really big hill. You’ll climb part of it, then turn off into a neighborhood by Maple Park. Then it’s back east on 21st and a sizable hill. It will be the biggest incline you face until you hit Mile 11.

The hill gives way just before Utica Avenue, but the hilliness of the course won’t stop for a while. Running through the neighborhoods of near Woodward Park is scenic, but there is a lot of up-and-down between Mile 2 and Mile 7. Pace yourself accordingly.

The hills will relent as you go through Brookside, then turn west on 41st Street. Turning north on Riverside will remain flat, but the course ducks back east, then north again on Cincinnati Avenue and into a neighborhood. Mild elevation gains and losses prevail from Mile 8 to Mile 10. After that, it’s a good, flat section of Riverside Drive into Mile 11. And then it gets real.

At Southwest Boulevard, you will begin the climb back into downtown, and it’s not small, lasting the better part of a mile. Just past Mile 12, you’ll turn north at Denver Avenue and start heading north and downhill toward the Tulsa Arts District. Marathoners will turn back east at Second Street to begin their second loop while those doing the half will continue north on the last mile — one more climb, then a mostly flat finish.

For those going the full 26.2, it’s another trip out to midtown, but in different areas. You get to avoid the hills of 15th Street to start, instead eventually making your way south on Peoria between Mile 13 and Mile 15. Here, you’ll turn back east on a familiar road, south past Utica Square, but then farther east into different neighborhoods. I’ve found these areas not as hilly as Maple Ridge, but that will change soon enough. The mellower grades continue from Mile 15 through Mile 18 as you head north toward the University of Tulsa.

You hit one small but steep climb on 21st Street, then a long, gradual uphill slog toward the school between Mile 18 and Mile 20. The uphill continues through the school, then relents a bit as you leave and go back south on Delaware.

And then, my friends, comes the biggest mental test of the full, at least in my estimation. Just before Mile 22 begins, you hit 15th Street (also known as Cherry Street), and its sizable hills. Between Delaware and Peoria, they are big and somewhat steep.

Just when you think another huge hill awaits, you turn north back on Peoria (between Mile 23 and Mile 24) to start the trek back downtown. Fortunately, the hills of Midtown are behind you. If you have any gas left in the tank, you can make some time here. If you don’t, at least gravity won’t be devouring you the entire way there. A slight grade up takes you from Mile 24 to Mile 25, then a gradual downhill on First Street to Denver Avenue lets you coast.

If you want to do the Center of the Universe Detour, it pulls off the course in the middle of the First Street stretch. It’s a party up there, and they give you a commemorative coin for your trouble. Back on the main course, you go downhill fast on Denver Avenue, under a bridge, then one last, short uphill climb to the Tulsa Arts District and the final, mostly flat portion of the course to the finish.

Last few observations…

First, I hope you did some hill training. Though only a few of the hills are big and there are some sizable flat spots, this is not a flat course. At all.

Second, expect good course support. Organizers have lots of aid stations along the way, well-stocked and well-manned.

Third, watch the weather forecasts. So far, it looks good. A cool start in the mid-40s, and a high in the upper 50s. Dress accordingly, and keep watching the forecast. Weather in this state can be fickle.

Last, enjoy it! I’ve run this one a few times, and it stacks up well with any race I’ve done. The course is scenic and challenging, which always makes for a good time.

Bob Doucette

Advertisements

Training update: Signs of progress at the Tulsa Run 15K

For a short burst, I was actually fast. But really, this race went pretty well.

I set out in late summer to create a new challenge for myself. Knowing that the cooler temperatures of fall were approaching (and fall race season), it seemed like a good time to see what I could if I trained harder for a specific goal race.

For me, that’s the Route 66 Marathon’s half-marathon event. Last year, I surprised myself with my second-fastest half marathon time. I learned a lot from that and wanted to take those lessons into this fall to see what might happen. I snagged a more aggressive training schedule and got to work.

It’s important to follow your training plan. While it’s fine to have a plan, it doesn’t mean anything if you don’t follow it. So I’ve been strict about that. Since late August, I’ve missed one workout (I went hiking in Arkansas instead of competing in a 5K, per the schedule) and modified one other (speed work on a treadmill during a downpour instead of running four miles outside). On everything else, I’ve done the work, even when I didn’t feel like it.

What’s also important is measuring the results. If you’re not making progress, it means you’re either going through the motions to check a box or something else is wrong (illness, injury, etc.). I think I’ve been making progress. But they only way to know for sure is to test myself and see.

I had a good opportunity to do that last weekend. The Tulsa Run is a classic local race, and this was the 40th annual version of it. The main event is a 15K road race through some of the hillier portions in and around downtown Tulsa, a course layout that is a change from the race’s traditional out-and-back, mostly flat aspects. My training schedule called for a 15K race last weekend, so instead of a slow-go long run, it would be a more energetic effort on a race day.

I’ve run the Tulsa Run five times, including three times on the newer, tougher course. So how did it go?

Gratefully, the weather was perfect: 34 degrees at start time, sunny and light winds. There would be no overheating, so I’d be able to push myself.

The race starts out with about a mile leading out of downtown downhill. From there, it’s a roller-coaster of hills, some big, some small. I feel bad for the runners who didn’t train on hills. They suffered.

This lasted from Mile 2 through Mile 6. After that, there is a flat section that goes on for two more miles before the course winds its way back up the hill to downtown and the finish. In my opinion, that last mile is the toughest part, a series of rolling hills that goes ever up until you cross the finish line.

My expectations weren’t that high, seeing that I’m still weighing at or near 190 pounds (I do love me some barbecue and tacos). But during training, I’ve made sure to include hill climbs. Weekly mileage volume is in the 30s now.

All of that paid off. All my 5K splits were nearly identical. Yes, the hills were hard. But on the downhills, I could lengthen my stride, control my breathing and regain my wind while making up time lost on the inclines; running on hills is good practice for the real thing, and experience counts.

Oddly similar splits. Not bad.

I finished at 1:31:23, my second-fastest 15K and the fastest since the course change a few years ago. The 9:48 pace is not far from my goal pace for Route 66. Much closer than I thought it would be. These aren’t barnburner times by any stretch, but for a guy who has been slow for several years, it’s not too bad. And a sign of progress.

The Tulsa Run is a good test for people running Route 66, as the characteristics of the courses are very similar. I always fail that final hill climb on Route 66’s half, just like I used to do on the Tulsa Run’s last mile. This time was different, so I’m hoping I can make more progress these next few weeks, smash the remaining workouts and maybe hit that goal. And PR, of course. Either way, I’ll let you know.

Bob Doucette

What went right, what went wrong: Five lessons learned on the trail

All revved up and ready to go.

Experience can teach you a lot about hiking, and as the years go by, understanding yourself, your skills and your limitations goes a long way to being a safer hiker. Mistakes often turn into lasting lessons that make future outings much more enjoyable. And while that newbie phase can be fun and exciting, it can also put you in a world of hurt.

It’s one thing to use those lessons to help yourself. But what about the people you’re with? I hike solo from time to time, but many times I’m with other people, with varying levels of experience, ability and ambition. Mix a bunch of these folks into one outing, and you can have a comprehensive, positive experience, or you can have a hot mess.

Those years on the trail have given me a mix of both. I’ll summarize a few scenarios and go over what went right, and what went wrong.

BACKPACKING TRIP

View hiking up Wheeler Peak, NM.

Books, movies and tales told face-to-face can make outdoor adventures appealing to a wide group of people, and my own stories of hiking New Mexico’s highest mountain, Wheeler Peak, drew some interest. I took my wife, Bec, her sister, and two friends and we hauled our gear to the trailhead of the Middle Fork Trail. It is a 16-mile round-trip hike.

Our plan: Hike five miles to Lost Lake, camp there, summit the next morning and then head back down for steaks and high-fives in nearby Red River.

In terms of, well, everything, this group was all over the map. My friends had done plenty of backpacking in the western U.S. and in China, but were a little light on their fitness. The same could be said for Bec, who was also new to backpacking. Her sister, Liz, was also a relative noob in backpacking, but was in marathon-ready shape. People’s gear was anything from high-end to inadvisable.

In terms of our objective, all of us summited the peak and made it back to Red River safely. Success! Right? Well, sort of. My friends had their moments of altitude sickness. Liz did great. Bec’s boots lacked proper support and her socks gave her blisters early on in the hike. By the time it was over, her feet were wrecked and the back side of her foot was shredded. What should have been a tired but happy scene at the trailhead was really some dazed folks and no shortage of tears.

What went right: We got most of the gear right, and the scope of the trip was (barely) within the level of everyone’s abilities. We reached our objectives, and got back safe.

What went wrong: Plenty. Only two of us were really in shape for this effort, and it’s asking a lot of new hikers to embark on a higher-altitude backpacking trip in the Rockies. Footwear was obviously an issue. I’d say we got away with a lot of mistakes, and this easily could have bred more serious situations.

Being the leader of this group, a lot of that is on me. I could have easily picked a different objective more within the group’s collective abilities, and a pre-trip gear check would have saved my poor spouse a lot of grief. As for the others, they are responsible for their own conditioning, and to a degree, everyone is accountable to do the proper research on gear. We all learned from this one.

WEATHER ON THE MOUNTAIN

Marching up toward the Keyhole on Longs Peak, CO.

As you grow in your outdoor experience, bigger and tougher goals become more appealing. Easier walk-ups give way to scrambles, which often lead to exposed, airy climbs. Before you know it, the newbie hiker of years past is boasting summits of big Latin American volcanoes, or Rainier, or maybe Grand Teton while eyeing Denali.

That’s not me, but the progression is similar. I went with some friends to tackle Longs Peak, Colorado, a couple of years ago, hoping to knock off a tougher peak.

Longs Peak is a lengthy route. Alpine starts often have you hitting the trail at 2 a.m., with thoughts of beating the weather around this notoriously unpredictable mountain. It has a big stretch near the top where you don’t want to be when the weather goes south.

We set off at 2:15 a.m., and made OK time to the Boulder Field, a bumpy section just before the standard route’s famous Keyhole. The Keyhole is where hiking gives way to scrambling, climbing and exposure en route to the summit.

But we’d heard from others that a previous day’s storms had dumped some wet, sloppy snow over the upper portions of the mountains. Clouds were swirling around the summit. Winds were up. A couple of us (me, for one) were dragging a bit. When we got to the Keyhole, we took a peek around the corner and saw, with dismay, that the reports we heard were true. The route conditions looked bad, especially since some of us weren’t as salty as the rest.

The de facto leader of the group, a fella named Dillon, saw it right away. And he’s the one who called it. We munched our summit food at the rock shelter by the Keyhole, packed up and headed down the mountain, stopped well short of our objective.

What went right: We listened to the voice of experience. Dillon has it in bucketloads. Even though we were equipped for the task, those of us on the lower level of experience might not have been ready for the route conditions. And the weather’s unpredictability made it an obvious no-go. Any protests were weak and short-lived. We knew the truth.

What went wrong: Nothing for anyone else. I’d criticize my level of fitness for that one. I know better now. Aside from that, I have memories of a big, burly mountain, Chasm Lake, and sunrise over one of the nation’s iconic national parks.

PACING A NEWCOMER

Hiking down Mount LeConte.

A couple of years ago, my sister-in-law Jen wanted to go with me to Great Smoky Mountains National Park to hike Mount LeConte. While not the Rockies, the bigger mountains of eastern Tennessee can have long routes with plenty of elevation gain. LeConte was no different, with the route we chose being the Alum Cave Bluff Trail: 11 miles with nearly 3,000 feet of gain to its summit.

Jen’s a gamer, but she’s also new to this. We took off on the lower part of the trail, and I set my usual pace.

Not long after you hit Arch Rock, the route steepens. We live around 800 feet above sea level, and by this time we were getting into the upper 4,000-foot level. It was right about there that I figured it was wise to slow things down.

Once we got to Alum Cave Bluff, we took a break. I wasn’t sure how much further Jen wanted to go, but after catching her breath, we decided to keep going. With a more measured pace and breaks every 20 to 30 minutes, we topped out on one of Tennessee’s highest peaks. It turned into a spectacular day that lit a fire under her for more adventures.

What went right: Recognizing that our early pace was too fast, and breaking the hike down into more manageable chunks. This is what I have to do in the Rockies, and it would make sense to do that here where the elevation was significantly higher than at home. It was also important to “read” my hiking partner: She’s got a lot of heart and a true competitor’s spirit, so her capacity to endure some physical hardship was going to be greater than others. That, combined with the right pace, got us to the top and back safely.

What went wrong: Really, it went about as well as I could have imagined. Had I insisted on keeping a faster pace, our trip likely would have ended sooner, and might have led to some hard feelings. I can’t emphasize how important it is to observe your partners. Glad we nipped that in the bud early.

NOT FEELING RIGHT

Late light at Hobbs State Park, AR.

I’m going to rat on Bec again with this one.

We were out in Arkansas recently, having a very chill few days in the hills and woods near Bentonville. We wanted to spend one day hiking some trails, and I found some good ones at Hobbs State Park.

But Bec was suffering from allergies, which led to some allergy medicine being taken the night before our planned hike. It did great in helping her sleep. But it left her in a fog the next day.

My plan was to get out there and hike as long as she saw fit, then turn around and head back. In more recent months, she’s gone on day hikes with me that went anywhere from two to five miles, with our most recent outing in New Mexico. She handled five miles at 8,600+ feet just fine, so I had no real worries.

I wanted her to lead for a few reasons. First, I figured it would be more fun for her if she had something to look at other than my backside. Second, it would allow us (force us) to go at her pace. And third, she wouldn’t be pressured to keep going if I was plowing away in the lead.

But dang, that medicine. It left her groggy and her head was swimming. She was kicking rocks the whole way, just short of tripping on, well, everything. It was a gorgeous day with good temperatures, and the forest in this park is a fantastic mix of hardwoods and pines. No matter. The medicine’s after-effects were making this outing a big case of “nope.” A mile in, we turned around, headed back to the car and hunted down some dinner.

What went right: Making her lead was the right decision. I wanted this to be fun for both of us, and crashing down the trail as fast as I can wasn’t going to do anything for me. I was just happy to be out there, regardless of how far we went. Having her set the pace and lead the way gave us the best chance of both of us enjoying it. When that became impossible, it made sense to pack it in when she was ready.

What went wrong: Really, nothing. We missed out on the overlooks further up the trail, but had we pushed through and done the whole four-mile loop, would it have been any fun at all? Nope.

SICK AS A DOG AT 14,000 FEET

I wish I could say I was feeling great about this summit in this pic. I wasn’t.

Now I’m going to tattle on myself. Back in 2008, a group of us decided to take a shot at Mount Yale in Colorado, a 14,000-foot peak near Buena Vista.

I’d been battling respiratory issues in the weeks leading up to the trip. A hacking cough pestered me to no end. But I figured I could give it a go.

We backpacked in a mile, set up camp and set out for Yale’s summit the next morning.

Early on, things seemed fine. I started slowing down more around 12,000 feet. Nothing unusual there. But at 13,000 feet, I started feeling side cramps. Normally, cramps like that occur when you’re running or sprinting, not when you’re hiking. Leg cramps? Sure. A side-stitch? No. But that’s what I was feeling. With no real idea what was going on, I pushed on.

The cramps got worse, and by the time I topped out, I was gassed. Here’s where things got weird.

Those side cramps, which came with the expected heart/lung stress of going uphill at altitude, didn’t go away. Anytime I got moving, the cramps would take hold. When I stopped, I was getting strangely cold. Soon, symptoms of altitude sickness were taking hold. I was moving slowly down the mountain, and weather was moving in. Treeline seemed incredibly far off. My declining physical state, and the conditions moving in, got me worried.

I knew if I got to treeline, I’d be OK. But I also knew I needed to eat something. I did, though I almost barfed it up. Having been on the mountain much longer than I thought, I was running low on water.

Eventually I got to treeline. I ran into a group of hikers, swallowed my pride, and asked if they had anything they could spare to drink.

When I got back to camp, my condition only worsened. Back at home, a hospital visit revealed a severe case of pneumonia, pleurisy and fluid around my heart. Recovery from this mess took a couple of months.

What went right: Well, I did summit! In all seriousness, though, not much. It was good that I recognized my predicament, kept heading downhill and, when available, asked for help. I ate when I needed to. I put myself in a position to get home safely, see a doctor and get treatment.

What went wrong: Almost everything else. This trip is a laundry list of avoidable errors. For starters, I should never have gone. The hacking cough was a good sign that whatever was ailing me wasn’t done. Those weird side cramps should have been a big enough red flag to turn me around. The two liters of water wasn’t enough. Pneumonia is a serious condition anywhere, and downright dangerous at altitude (that’s what prompted the altitude sickness). Fluid around my heart and my right lung could have been lethal. Mount Yale is a beautiful mountain, but it’s not worth my life. It was good that I humbled myself and asked for help when I saw those other hikers. But that humility would have been better served by staying home.

I could go on, but that’s a good sampling of scenarios I’ve faced, along with the good and bad about the decisions that were made. Experience is a great teacher, and hopefully it’s made me a better – and safer – hiker.

Bob Doucette

Seen on the run: Reminders from the past of why I run

We have these, right here in town. (U.S. Fish and Wildlife Service photo)

I remember the first time I saw an eagle in the wild.

No, it wasn’t on some adventure deep in the Rockies, or some other rugged mountain landscape. It was about six miles from home, in the middle of a city, and not far from the river that splits my community two.

Not 30 feet from the paved path I was running on, and overlooking the Arkansas River, there it was: A big, bald eagle, surveying the waters flowing by and likely looking for lunch swimming under the surface. It was one of the coolest and most random things I’d ever seen on a run, and to see it smack in the middle of Tulsa’s southern reaches made it that much more unreal. And yet there it was, in all of its regal glory, presiding over its domain. As it turns out, bald eagles have become a fixture along the river. You just have to know where to look.

More importantly, you have to be out there in the first place. If I hadn’t been on my weekly long run, I’d never have seen it at all.

***

I remember when I first started running more seriously, and how enamored I became with the little details I saw during even the shortest, simplest runs. I made a point to take my phone with me not to provide music or capture my pace, but to snap photos of how the downtown Tulsa skyline looked from a certain angle, or the way the glow of a sunset bathed the buildings in warm, fading light.

I’d come home and write notes about interesting people I saw, weird things I smelled and small epiphanies I had while I ran. I learned a lot about my city. One park I run through commemorates the 1921 Tulsa Race Riot, something that for many Tulsans was left out of their history lessons despite being the scene of the single worst outburst of racial violence in American history. Years later, I still run through that park, reminded that we’ve yet to get past racial divides.

Night running scene.

There were other details of the city to be gleaned from these runs, too. On a couple of occasions, I’d run at night. An urban landscape has an entirely different feel at night than it does during the day. Light from street lamps catches broken glass on the pavement and in alleys, making them glisten in a harsh sort of way. It’s harder to see people’s faces, thus more difficult to discern intent. But no one ever bothered me. A smoky bar served up whiskey shots next door to a private workshop where a bearded, tattooed fella in a plain white tank tinkered under the hood of a classic car. Nighttime in the city, away from the “safer” venues, is just as alive as it is in the day. It just feels more mysterious, if not risky.

And many times, I’d notice people. The suits and the slackers mixed at different paces, and transients often barely budged. On one street, I’d spot someone talking to himself while walking briskly, totally focused on whatever conversation was happening via Bluetooth. Around the corner, someone else, slumped against a wall, might be wallowing in his own puke, having drank too much bourbon the hour before. Down the street, a tattooed pizzeria worker sat out by the curb, getting one last smoke in before his break was over.

I see scenes like this every day when I run. It fascinated me for a long time, me being a guy who until that time had spent a lifetime living in suburbs and small towns, far from anything one might define as urban.

As the years have gone by, however, all of this has become normal. I still see cool stuff, but more often any run is more of me and the run itself, battling through fatigue, the elements, injuries and whatever else is motivating me or telling me to stop. And as I age, the chorus of inner voices telling me to bag it seems to get bigger. And louder.

***

Last week was one of the lousiest weeks of training I’ve had in a while. Fall is here, but Oklahoma rarely pays attention to the calendar. It was just another hot, humid week, and if you run much you know that heat and humidity sucks all the fun out of running. If I didn’t have a couple of races to train for, I’m not sure I’d even have bothered.

But we got a break this week. On Monday, cloud cover. Blessed cloud cover. Eighty-eight degrees in direct sun (plus humidity) is one thing. But 88 and cloudy is another. As in better.

I was out on a simple four-mile out-and-back run through a neighborhood that might be generously classified as “working class.” It’s on the upswing, but there is plenty of industrial desperation still waiting to be remedied here. Not that it bothers me – that sort of environment is way more interesting than any suburban scene I’ve ever trodden.

Anyway, I ran by a house where a fella was on the porch, working on some sort of machine, and he had his tunes on full blast: ‘80s funk and R&B. I ran past, reached my turnaround place and headed back. I’d pass his house again, this time from the same side of the street. On deck: Rockwell’s “Somebody’s Watching me,” featuring none other than the King of Pop. I’m not sure why, but when I got in earshot, it gave me an extra bounce, and I made sure to let the dude know that I wish I had his tunes with me the rest of the way. We both got a laugh out of that.

Getting some miles on the trails. I see cool stuff out here. (Clint Green photo)

A day later, on a six-miler, I was on trails close to the Arkansas River again. I didn’t see them, but I heard them: eagles. Somewhere close by, the master raptors were calling out, and would likely be on the hunt for more fish soon. It got me thinking about all the other wildlife I’ve seen, usually when trail running through nearby wooded hills. Squirrels and rabbits, hurrying away from the path. An armadillo ambling along, rooting through the leaves for bugs. And on one blessed run, a massive owl that was silently gliding below the canopy, then extending its wings to make a full stop just a few feet away from where I ran. One of the most majestic things I’ve ever seen.

That’s when I was reminded why I still do this. Races are fun, and great motivation to get in shape. But for me, there’s no finish line or medal worth the weeks and months of training that it takes to finish a long-distance race. Instead, it’s the things I encounter along the way.

The random faces that make a city live and breathe.

The myriad of colors of a cool evening sunset.

The smell of fall from decaying foliage on the forest floor.

And timely reminders from the past, be it the cry of a regal bird of prey, or the music pumping from the speakers owned by someone getting their funk on during a warm autumn afternoon. Any finish line glory is gravy after that.

Bob Doucette

Mountain reads: ‘Exposed: Tragedy & Triumph in Mountain Climbing’ by Brad McQueen

NOTE: This is an installment of an occasional series on books, old and new, about outdoor adventures.

Put yourself in this situation: You plan a mountain adventure with your wife and your dad on what is supposed to be a straightforward alpine hike. As the day wears on, a few things go awry: You make a wrong turn and get off-route. The weather worsens. The darkness of night takes over. And when it’s all said and done, you end up in a freezing bivouac fighting off hypothermia. By the time morning arrives, your spouse has suffered permanent injuries due to frostbite, and all of you are lucky to be alive.

But despite the guilt over what transpired, the pull of the mountains remains so strong as to be undeniable.

That’s the backbone of the 2015 book “Exposed: Triumph and Tragedy in Mountain Climbing” by Brad McQueen, a Colorado mountaineer who has built quite the alpine resume.

When I started the Mountain Reads series, I wanted to find books that told interesting and important stories about adventures in the high country. McQueen’s book does both.

When something bad unfolds in the mountains, people often write a book about it, explaining the highs, lows and lessons that incident provided. “Exposed” does this, but doesn’t stop there. While his mishaps on Mount Evans provide the frame of his story, it’s just one part of a still evolving tale of McQueen’s mountaineering life.

McQueen details not only hikes and climbs in his home state, but also those in Wyoming, Washington, Tanzania, Ecuador and Alaska. You get a good sense of what it takes to prepare for his more ambitious climbs while learning the emotional pull that climbing can bring.

In that respect, “Exposed” is also a family story. McQueen and his wife, Melissa, are in fact an outdoors team, as she has also put together a respectable list of accomplishments in the mountains. Overcoming the trauma of their shared Mount Evans experience is a major thread in this story, and in several places throughout the book, Melissa McQueen adds her words to provide context to their tale.

You might also learn something about climbing in the process (there is a succinct appendix and glossary of terms at the end of the book), including a short but instructive bit about crampon technique on snow and ice. Nuggets like that are scattered throughout the text.

I liked this book, and I think most people who enjoy the high country will, too. Pick this one up and see how a regular guy has lived some extraordinary adventures.

Bob Doucette

With five deaths in six weeks on Capitol Peak, mountain safety takes on greater urgency

Capitol Peak, Colo. (Wikipedia commons photo)

Anytime someone dies in the mountains, it gets attention. Landslides, avalanches, falls, or otherwise, the terror of finding your end on a high peak garners headlines.

People speculate how it happened. They express grief and sympathy for the fallen climber’s family and friends. A few may even throw barbs toward the victim, though that is, thankfully, rare.

This is repeated every year, especially in the summer when hordes of hikers and climbers take advantage of longer days and more favorable weather to get their summit fix.

But this summer feels a bit different, in that the volume of deaths seems to be on the rise. And more than that, the number of fatalities on one particular mountain, Colorado’s Capitol Peak.

I’ve never climbed it, but I know some people who have. There is bountiful information about the peak and its challenges available online and in books. From these sources, I can tell you a few things about the mountain: It’s exposed, with large drop-offs and a number of “no-fall zones.” Like the rest of the Elk Range where it resides, it’s notoriously loose, with rotten rock in all the wrong places. It doesn’t take much for toaster-sized rocks – or boulders far larger – to tear loose from the mountainside and careen down its steep slopes, and God help you if you’re in the fall line. One friend of mine survived a rockfall incident, but deals with traumatic brain injury symptoms years later after having two loose rocks smash into her head during a climb in 2013. Thank God for climbing helmets, or she’d be dead.

More recent news has solidified the mountain’s reputation. Over the past six weeks, Capitol Peak has claimed five lives.

That’s an extraordinary number, given the fact that the mountain hasn’t had more deaths than that over the previous several years combined. And for more perspective, it’s just two fewer than Mount Everest recorded during its spring climbing season this year. I don’t want to equate the two mountains, but the numbers are what they are.

So what do we know of the 2017 fatalities? The first two seem to be cases of falls associated with loose rock. But the last three indicate something else.

The third and fourth deaths on Capitol Peak, Carly Brightwell and Ryan Marcil, were a couple who had climbed the mountain, then fell on a steep section below the summit but before the solid yet very exposed knife-edge ridge.

The fifth death, Zackaria White, was a climber who fell in the same area.

What separates these two incidents is the experience of the climbers. The couple in question had some time in the mountains under their belts. White did not. In fact, Capitol Peak was his first 14er (a mountain that meets or exceeds 14,000 feet above sea level).

The knife-edge ridge on Capitol Peak. (Wikipedia commons photo)

What they have in common is it appears all three people tried to find another route down the mountain to avoid traversing the knife edge, according to local search-and-rescue team reports. They cliffed out, got to a point where they could not ascend or descend, and fell to their deaths.

Those similarities would, at least, point toward some obvious lessons: Stay on the route, especially on challenging mountains like Capitol. But this is no cure-all, as evidenced by the other fatalities on Capitol, as well as two more deaths on the nearby Maroon Bells, a pair of striking but dangerous mountains in the same range.* The “Deadly Bells,” as they are known, are like the rest of the Elk Range: steep, exposed and littered with loose rock that can break off under you at any moment. Deaths on the Bells, as well as a number of mountains in this range and many others throughout Colorado (10 fatalities so far this year), come with a wide variety of causes.

In fact, if you were to make a list of causes of death (and preventative measures to minimize risks for each situation), it would be so broad as to nullify any attempt at standard, one-size-fits-all practices to curtail mountain tragedies. To wit: bring the 10 essentials; eat and hydrate; get an early start; watch the weather; study the route; bring an emergency locator beacon; be in top shape; don’t wear cotton; bring the proper footwear; don’t try a mountain beyond your abilities; hike with a partner; and so on. Even if you did all these things – and most people do – there is a chance that you could still die on a mountain by pure blind chance. That, too, has happened often enough, claiming newbies and veteran climbers alike.

It should be noted that the ratio of people who have safely summited Capitol Peak, and any number of other Colorado mountains, to those who have died on them is starkly in favor of survival. For every death, thousands have successfully climbed and come home intact.

But rescue and recovery missions are expensive, taxing and at times risky endeavors. Given that, and the growing number of people who try their luck in the high country (to the tune of hundreds of thousands every year) mean that the myriad of ways people can get into trouble will only ensnare more, which will mean more rescues, more risk on the part of the rescuers, and to those who can’t be saved, more deaths.

An exasperated Pitkin County Sheriff Joe DiSalvo told the Aspen Times his office would more aggressively educate people on the risks of climbing mountains, especially the ones in his jurisdiction. Mountain Rescue Aspen is drawing up plans to do just that.

But here is where we are: We exist in a time where outdoor adventure is more popular than ever. Social media, especially channels like Instagram and Facebook, drive people to do more, push harder and otherwise ply their skills for the sake of not just enjoying the high country, but to pursue “likes,” audience growth, and potential sponsorships from gear companies, retailers and others who seek out social media influencers to market their brands. They may not be the only drivers, but they are potent. And they will only grow more powerful as populations in Denver, Salt Lake City, Seattle and Portland, among others, swell.

To be frank, I don’t know if there’s an answer here. I can’t say if this summer in Colorado is an anomaly or the beginning of a trend. But it does bring me back to a couple truths.

First, the ultimate responsibility has and always will lie with the individual. No one forces anyone to climb mountains. For those who do, the burden of preparedness and safety is squarely on their shoulders. Given the massive volume of information out there on mountain safety, there is no excuse for being uneducated on the topic or on the peaks people climb.

Second, it’s important for people to have each other’s backs. Teach those with less experience than you. Be the one to give guidance on the trail to your partners, and take charge when needed. Know when it’s time to call it a day and turn around. Those lower on the pecking order need to pay attention to those with more experience. And those with the experience need to get a good read on their partners and understand their limitations, or any other problems that may arise. Teams should not split up unless absolutely necessary, and believe me, that’s rare.

We know people will have problems in the high country. We know people will die. And we’ll analyze these incidents, looking for answers. But don’t expect a cure-all solution. As lame as this might sound, we must do the best we can at taking care of ourselves, doing the things we love in the places we cherish, knowing that these marvels of nature can snuff us out at any time, with total indifference, even if we do everything right. It’s the nature of mountains, and one none of us should ever forget.

Bob Doucette

*An earlier version of this post said there were four deaths in the Maroon Bells this year. There have been two.

Road trip distractions: The value of getting sidetracked

I’m not sure how you do road trips, but my normal pattern has me going from Point A to Point B as quickly as possible. I want to get there, have my fun, and avoid dragging out the long drive home.

But there is something to be said for sacrificing a little time to enjoy the little distractions along the way. They might slow your journey, but sometimes that’s not a bad thing. I found one of my favorite barbecue joints in Salina, Kan., just because me and my travel buddy had a craving for pork. We blew more than an hour there, and it was worth every tasty bite.

On my last trip out west, we took a couple of stops to examine some scenery in northwest Oklahoma. The Sooner State is known as a prairie state, but there are some unique bits of scenery that are worth a stop.

First up, the Gloss Mountains. Or Glass Mountains. Officially, I think it’s Gloss, but Glass Mountain gets its name from the mineral formations visible at its peak.

Glass Mountain. Or Gloss Mountain? Whatever. It looks cool.

Gloss Mountains State Park contains loads of mesa-like formations like this. There is a bunch of hiking throughout this park, and it’s a cool contrast to the gently rolling plains that dominate the scenery in northwestern Oklahoma. The park is just east of Woodward, which, by the way, is home to another great barbecue find, Wagg’s. Trust me on this one.

Dramatic skies help frame the shot of this formation in the Gloss Mountains.

The Gloss Mountains were on our way to New Mexico, so it’s not like this stop took lots of time. But seeing Black Mesa on the way home would be a much longer detour. Again, totally worth it.

Black Mesa is in the far northwest corner of the Oklahoma Panhandle. Cimarron County is as flat as a board. But that changes abruptly when you get to area surrounding Black Mesa. One minute you’re in flat, high plains prairie. The next, you’re driving around and between high cliffs and hoodoos.

Hoodoos south of Black Mesa.

More hoodoos. There is also the remains of petrified trees at nearby Black Mesa State Park.

In some ways, Black Mesa is the easternmost outpost of the southern Rockies. Lava flows filled ancient valleys eons ago. As softer rock and soil eroded over time, Black Mesa’s harder volcanic rock remained. The Black Mesa summit is Oklahoma’s highest point (4,975 feet above sea level), and has a good trail to the top. As you drive west into New Mexico, more of these formations are visible, as well as a number of dormant volcanic cinder cones. All of these arise just before the Rocky Mountain uplift soars into the skies west of places like Raton and Cimarron. So yeah, Black Mesa is sort of where the Rockies and the high plains meet. It’s a cool place.

Black Mesa. Very green for this time of year.

Another shot of Black Mesa, near the trailhead. The formation is huge, so you’re looking at a small corner of it.

Near Black Mesa you can see dinosaur tracks. A number of bed and breakfasts operate near Black Mesa, and the natural setting of Kenton, a small town nearby, is about as scenic as you can get in this part of the world.

Going here added about 90 minutes to our return trip, but it was worth it. Cedar, cactus, sage and shortgrass carpet these rugged lands. If you’re looking for a place with an Old West feel, Black Mesa has it.

Anyway, all this is to say that if you have the time and can pull over from time to time, do it. You never know what  you’ll discover, or what you’ll learn from out-of-the-way places. And if you’re really lucky, maybe you’ll find a spot with good ribs.

Bob Doucette