Oklahoma women running far: Camille Herron sets a 24-hour record, and Bevin Ver Brugge claims a 100-mile first

Camille Herron

A couple of Oklahoma women decided this past week was a fine time to to make their mark. And by making their mark, I mean doing things no one — man or woman — had ever done.

First up is Camille Herron, of Warr Acres, Okla. Camille is a well-known ultra runner who last year set the U.S. record for a 100-mile race at the Tunnel Hill 100 (12:42:39, a stunning 7:38 per mile pace). That record was broken this year, but not one to stand still, Herron broke another record this past weekend, tallying 162.9 miles in a 24-hour period at the Desert Soltice Track Invitational (8:50/mile pace). And by breaking a record, I mean breaking a world record. In doing this, she also broke the 100-mile track record.

Next up is something more local, but also impressive. In Tulsa, runner Bevin Ver Brugge took on a very personal project: that of doing her first 100-mile run on her local trails.

Bevin created a loop at Tulsa’s Turkey Mountain Urban Wilderness that, when done eight times, would give her that 100-mile total. She set about doing it on Dec. 1.

A hundred miles is tough no matter what, but doing this at a place like Turkey Mountain is particularly difficult. The elevation changes aren’t as severe as you get in more mountainous states, but the trails themselves vary from mellow and runable to highly technical, riddled with rocks and roots that make for slow going. Compounding that is the presence of a bunch of fallen leaves, hiding all those tripping hazards.

She completed that task in a bit over 36 hours. But the time is not the record here. While Turkey Mountain is home to plenty of races (including a few 50Ks), it’s believed that she’s the first to run 100 miles there in one go. In doing so, she also picked up more than 9,000 feet of vertical gain — not too shabby in the middle of the Southern Plains.

Watch this video of the emotional finish at the trailhead.

Advertisements

Race recap: Running the 2018 Route 66 half marathon

Cruising along, wondering, “What’s over there? Tacos?”

At the end of last year’s fall race season, I was not in a great place. I’d worked hard to train for the Route 66 Marathon’s half marathon race, hoping to substantially improve my time. I was on my way to doing that, but an illness two weeks before the race left residual junk in my lungs that made it a fight just to shave 30 seconds off my previous year’s effort.

After that, my head was not in a good place when it came to running. I’d drive by places where my long runs would go and think to myself, “Glad I’m not doing that anymore.” Months passed by and still no itch to run more than a few miles at a time. Between that and a bout of plantar fasciitis in the spring, I was wondering if maybe this was the year I’d sit out of all fall races and do something else.

But around that time, a friend of mine from Colorado started asking questions about good races in the Tulsa area. After a few online chats, he decided he was going to run the Route 66 half and wondered if he could couch surf at my place.

Man, I could hardly host a guy from out-of-town for a race and not at least try to get ready for it myself. So once again, as August drew to a close, I drew up a plan and got to work on half marathon No. 7.

TRAINING

I used the same plan as last year, but with a few tweaks. First, I took my rest day when the plan said so: on Thursdays. Weird, but yeah. And it worked. I’d ride a bike for a specific amount of time on Sundays, run a short route on Mondays, a medium-length run on Tuesdays and then do speed work (either 400-meter intervals or 3-mile negative split runs) on Wednesdays. But the time that was all done, the Thursday break was a blessing. I’d chill at the house or go for a short hike in the woods. I looked forward to those Thursdays.

Fridays would include a shorter route, and then Saturdays would be the weekly long run.

I continued to lift weights, but backed off considerably from years past. I did three full-body workouts a week (Monday/Wednesday/Friday), and no lift lasted longer than 30 minutes. I knew I’d lose some strength, but that happens every time I jack up the miles anyway.

The plan itself was a modified version of the Hal Higdon Intermediate 1 half marathon program. You can check it out here.

To be frank, August and September sucked. It wasn’t blast-furnace hot, but still hot enough and unusually humid. Heat indexes were regularly over 100 degrees, and those mid-length to long run days were brutal. It was a major downer to slog along at slow paces and see very little improvement.

October started getting better, and the last Saturday or the month is the day of the annual Tulsa Run. It’s a great tune-up race for Route 66, which is held on the Sunday before Thanksgiving. I feared this would be my slowest 15K (based on long run times), but in fact, it was surprisingly better than expected. Nowhere near a PR, but not too bad.

And then, the switch got flipped. Every training run after that race saw better times, stronger running and a general feeling that my conditioning was coming around. It was the same last year (I peaked at the Tulsa Run last year, running my second-fastest 15K before that cold bug got me), so my hope is that my fitness arc would peak on race day Nov. 18. And hope no one would get me sick before then.

Cool part of the race where we’re actually running on old Route 66. And is it just me, or is the guy to the left stalking me? He looks fishy to me.

THE RACE

Weather is always a key variable at Route 66. November in Oklahoma can hit you with 70- to 80-degree days. It can also hit you with 18-degree days. Rain, snow and ice — or bright sunshine — are all possible. What we got were temps in the lower 30s, a little drizzle and a stiff north wind. It was the kind of cold that goes right through you, but not the worst I’ve seen on race day and totally fine once you get moving.

The course was changed slightly, too. Construction at a new park forced race organizers to reroute a portion of the course through a neighborhood that included a long, low-grade climb that can wear you out. Now that the park is open, the course went back to Riverside Drive, a long, flat stretch between Mile 7 and Mile 10 that’s a welcome relief after facing a hilly section from Mile 2 through 6.

If I were to give advice to anyone running this race, I’d tell them to not blow yourself out running that early stretch. The Maple Ridge neighborhood is scenic and interesting, but it’s full of hills. If you’re not careful, you’ll wind up gassed by the time you get to Woodward Park 5 miles in. Not good when you’re not even half done (and if you’re doing the full and feel bad at this point, good luck to ya. It’s gonna be a long day).

Last year, I knew 3 miles in I was in trouble. This time, I took it in stride. It was tough once again, but I was careful to breathe deep on the downhills and slow my heart rate down before the next incline showed up.

Once you get through Mile 6, the course mellows considerably. Last year, I hoped to recover here, but never did. This year I felt great cruising through Brookside, then getting ready to make the northward turn back toward downtown.

But boy, did we get a fun surprise making that northbound turn: a biting wind right in our faces. The trees in the neighborhood shielded us for those first six miles, as did our southbound trip through Brookside. But now we got a good 4 miles of running into the teeth of it.

Surprisingly, it didn’t bother me that much. The miles ticked by, and then we took a quick out-and-back on the Southwest Boulevard bridge before going back into downtown.

For the half marathoners, this is the crux of the race. You get two good-sized hills back-to-back as you gain elevation into downtown (Tulsa’s central business district is on top of a long ridge overlooking the Arkansas River), and this is the place that always bites me. It did again this time. I was gassed, slowed for a brief walk break, then got going again. One of these days I’m going to blast all the hills. Just not this time.

At the top of that second hill is a sweet, blessed, oh-so-needed downhill pitch that goes for about seven blocks. It’s here where the full-marathoners turn east to start their second loop while the rest of us head into the Tulsa Arts District toward the finish line. It’s here I always ask myself if I regret not doing the full. So far, four straight years of “nope.”

Earlier in the race, I was just behind the 2:10 pacer, but I consciously decided not to make a thing of it. “Just run your race,” I told myself. If I saw her close to the end of the race, I’d catch her with a final sprint to the end. If not, no biggie.

Yeah, I was not anywhere close enough for that. So I just cruised into the Arts District, rounded the corner and sprinted the last three blocks toward the end.

Checking the clock as I ran in, I knew I’d run faster than I had the previous year. And I was right: 2:13:41, just shy of 50 seconds better than a year ago. No PR (I still need to trim 2 minutes off that time to get there), and I’m far from my gold-medal goal of breaking 2 hours. But my thinking is I was faster than the previous year, that’s a success, even if just a modest one.

Sprinting it in to the finish.

POST SCRIPT

I’d say I’m satisfied, overall. Had I not let my conditioning slide over the summer, I could have done much better. But the training program worked. This is now three years in a row that I’ve been faster. Not a bad thing to get faster as I get older.

There was also something else that worked for me. During that first month, I was griping to myself that I wasn’t as mentally tough as I used to me. It became too easy to bag it. Sure, I’d get all the miles as prescribed. But in terms of performance, pretty meh.

To combat this, I’d play mental games. I’d say “Go this far before you slow down” or “see if you can skip that water break coming up and push through to the next one.” Little things that were a tiny bit harder than what I did the week before, or the day before.

That helped me on race day. I got out of the aid stations much faster than in past years, and even though my 10K and 10-mile splits were slower than last year, the final 3.1 miles to the finish was considerably faster.

But here’s the best part: Unlike last year, I don’t hate the idea of going for 60- to 90-minute runs. I don’t feel the need to back off my training. I look forward to upcoming races. Mentally, I’m in a much better place.

It’ll take a lot (keeping my base, trimming some weight) to get my sub-2 hour goal — shaving a full minute per mile from my current pace. But it seems doable with time, effort and planning. In late 2017, such thoughts were far from me.

Now I’m looking forward to more weight training, but also getting in “mountain shape.” I want to show up in the Rockies in great shape and not suffer at altitude. When next fall rolls around, maybe my base will be strong enough that I can blow past this year’s time, crush my PR and maybe even crack that 2-hour mark. And then see what happens from there.

Bob Doucette

Previewing the 2018 Route 66 Marathon

The Sunday before Thanksgiving is quickly approaching. For a bunch of us, that means running the Route 66 Marathon.

This race is where I cut my teeth on the marathon, and I’ve run the half marathon a number of times. So of course I’m running it again, as are thousands of you.

What you’re going to get is the same great event as always, But there are going to be some course changes, and from what I see, they are for the better.

So the purpose of this is to go over the course, and maybe give you a few observations before you toe the line on Sunday.

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 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. The big change in the course happens here. In the past few years, the course ducked back into the neighborhood and a long, gradual climb on Cincinnati Avenue. The detour was made because of construction at the Gathering Place park. The park is open now, and so is Riverside Drive all the way to downtown. Runners will enjoy a flatter stretch through the park, and that should help with people’s times. It will also help you save some energy as you get ready to head into downtown and into Mile 11. And then it gets real.

First, you’ll turn west and cross the Arkansas River on the 11th Street bridge, a stretch that is part of the historic Route 66. At the end of the bridge, you’ll turn around and run back into downtown.

At Southwest Boulevard, you will begin the climb back into downtown, and it’s not small, lasting the better part of a mile, comprising of two hills. 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 short 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 university 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.

Marathon starting line stoke: It’s real, man. (Kirk Wells/Route 66 Marathon photo)

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. It’s going to be a cold start, with gun-time temps about 28 degrees. The high is expected to top out at 42 degrees, and it will be cloudy with a north breeze. Dress accordingly, and keep watching the forecast. Weather in this state can be fickle.

Fourth, the start corral has a different format. It will be a spoke corral to work around a construction site on Main Street: A and B corrals will be on Main Street south of Fifth while the C and D corrals will be on Fifth Street on either side of Main. And I’ve been told to tell you all that you have to enter each corral from the back – no hanging out at the roundabout fountain at Fifth and Main and jumping in another corral will be allowed.

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

Welcome to the neighborhood: Cyclists, racing and a city’s biggest block party on Cry Baby Hill

Cyclists race by as crowds cheer – and drink – at the Riverside Criterium of Tulsa Tough on Cry Baby Hill.

When I got up Sunday morning, the parade was already started. Out my window, lines of people were strolling down the hill, coolers and lawn chairs in hand. Some were in costume. Most were dressed for the heat. Some were already half-tanked.

A typical Sunday morning for the third day of Tulsa Tough, an annual cycling race series and festival that has bike enthusiasts from across the country descend on T-town with all the spandex anyone could ever want. Crowds gather for all three days of Tulsa Tough, but it’s the third day, on Cry Baby Hill, that folks really get revved up.

And it happens in my neighborhood.

A little about my ‘hood: it’s tough to define. It’s older, right on the edge of downtown Tulsa, and built on the banks of the Arkansas River. It’s a mix of people, from bohemian to bums, families and retirees, living in stately older homes, shotgun houses, or in open fields not yet developed. It’s a place where you can watch incredible sunsets from your porch, or view transients stumbling down an alley. I feel perfectly safe here, but sometimes there are police helicopters and searchlights. Typical urban neighborhood, I suppose, and the site for the Riverside Criterium of Tulsa Tough.

So let’s talk about Tulsa Tough. This was the 13th year for the event, which attracts top cyclists from across the country and the world. For three days, they race through different courses downtown, and as the years have gone by the crowds have grown. There’s also a gran fondo ride that goes well outside the city and a townie ride where anyone with a set of wheels can take a more leisurely trek.

The climax of Tulsa Tough is the Riverside Criterium. It’s the toughest course, with steep inclines on every lap. I’m sure that’s something cyclists can appreciate and dread, but for most people, the Riverside Criterium is all about the scene that is Cry Baby Hill. It draws the biggest, most raucous crowds of the entire weekend, and I’d say most people are there more for the party than the races. Folks show up by the thousands.

It wasn’t always that way. When Tulsa Tough started, people in the neighborhood gathered at a house or two to watch the races, guzzle some beer and cheer them on. One legend has it that regulars at the Sound Pony, a downtown dive bar frequented by cyclists and other endurance athletes, started making the Sunday Tulsa Tough races a thing. However it started, someone built this party scene, and man, did it grow.

Today, the Riverview neighborhood is choked with Tulsa Tough spectators and revelers. There’s lots of skin, vats of beer, weird costumes and creepy baby-doll heads on sticks. There are a bunch of whistles and people in referee uniforms helping the crowds “mind the gap” so cyclists can actually freely race without fear of running into errant fans. It’s grown so big that the food truck cabal decided to come, and live music on a stage popped up. Debauchery of all sorts happens, though most people keep it in check. I think. Anyway, I tell people that Cry Baby Hill is an annual excuse to get drunk on a Sunday morning, and I think that’s mostly true.

Some of the cyclists get into it. If they’re not concentrated on actually winning, they’ll slow down and take a brew from the crowd before continuing. Cops are there in droves, as are paramedic crews. It’s hot out there, and sometimes the combination of a 12-pack of Natty Light and high heat/humidity doesn’t work out too well.

You might think the description of my neighborhood, the event, and the crowd is negative, but let me shut that down right now: I dig this scene. Endurance sports don’t get a lot of love, so when the hordes arrive to cheer on the competitors, I’m all for it. Come on down, invade the ‘hood for a few hours and have a good time. Too many parts of town (any town, really) are too buttoned down, becoming regimented to the point of lifelessness. My neighborhood is a trip pretty much every day, and I guess it’s fitting that Day Three of Tulsa Tough is sort of a holiday of weirdness for my weird little place.

That all of it surrounds cycling hits home, too. I don’t race, but I spend a decent amount of time in the saddle these days. I chose where I live so I could bike to work. It’s also close to a paved trail system that’s great for longer rides. I’m not a racer, but I get these people even if my ride costs less than the accessories they attach to theirs.

So how did all this go down for me? Well, as the crowds clogged my streets, I mowed my yard. Picked up a half-empty can of Coors Light kindly donated to my lawn. I dumped the rest out, recycled the can, then jumped on my bike and rode to the center of the action.

While recording part of the race from a more “family friendly” part of the course, a half-baked spectator noticed by Denver Broncos ballcap and proceeded to talk smack. Turns out, he was a Chiefs fan. They got us twice last year, but I reminded him that the Broncos have three Lombardis in the case to Kansas City’s one. He was forceful at first (I was hoping that this wouldn’t turn into a real fight), but chilled out long enough to have a more nuanced discussion about how the AFC West was going to play out. His girlfriend got bored, so we bro-hugged and they left.

I rode to a few more spots, taking pics and taking in the scene. Everywhere I went, the streets were lined with people, sometimes ten deep. Whistles would blow, a chase vehicle would zip by, and then a couple of cyclists would follow. Behind them, the whirring gears of a few dozen more cyclists, bunched up in the peloton, breezed by. The crowd cheered, yelled, rang their cowbells and took a swig from coozy-lined cans and red Solo cups.

This scene repeated itself for several hours until the last pro races were done. Podiums were mounted and trophies awarded. Fans eventually stumbled back into their houses, or toward their cars, and not a small number of them took the next day off.

What does this all mean? I’m not sure about the origins of Tulsa Tough. There’s a healthy cycling community in Tulsa, but not more than any other mid-sized city. Even so, Tulsa Tough is a huge success, an international draw, seemingly getting bigger every year. That an obscure endurance sport can become so huge here is encouraging, even if half the appeal is just showing up for the party. It’s a weird, geared-up and beer-soaked thread in a community tapestry that might otherwise be mildly bland.

Come next June, we’ll do it all over again. See ya next time for Year 14 of Tulsa Tough. Cry Baby Hill awaits.

Bob Doucette

Race recap: Fighting through the 2017 Route 66 half marathon

Wrapping up a tough Route 66 half marathon. At least there was enough left to sprint it in.

I walked into the starting corral at the Route 66 Marathon in perfect conditions. It was 38 degrees, with slight breezes and sunny skies. After a good, hard 12 weeks of training, this should have been the best half marathon I ever ran.

But strange things happen.

Instead of relishing the newfound conditioning I’d developed and soaking in another great race, I found myself in a fight. Just a few miles in, my body was saying, “Not today, dude. Not today.”

At the finish, the sprint at the end belied how I really felt, like I’d been beat up and denied what I’d trained so hard for.

But that’s not the whole lesson, and it’s not that one-sided.

THE RUNUP TO ROUTE 66

Over the summer, I’d set a goal time that I wanted to hit for this year’s race. Last year, I had a mellow training program that gave me a better-than-expected time of just over 2:15 (I’m not that fast, folks). I was happy with that, coming in a bit heavy and just four minutes off the best 13.1-mile time I’ve ever run, and five minutes under the previous year’s disappointment.

Surely with a more serious training schedule, I’d crush that PR and maybe get past that two-hour barrier. So I set out to make a more aggressive program that had me running more weekly miles than I’d done since I trained for a marathon back in 2013.

The training schedule. I was religious about following the plan, and if not for unforeseen circumstances, it would have paid off in spades..

Dude. I was religious about it. Aside from skipping one weekend 5K and doing a treadmill speed workout on a day when it was pouring rain, I nailed it every day. The weight peeled off, my cardio returned, and by the time I ran the Tulsa Run 15K eight weeks in, I was hitting mile paces I hadn’t seen in four years. Breaking two hours was probably not in the cards, but that PR seemed in the bag. During the Tulsa Run, my 5K splits were even, I crushed the hills and I had cardio for days. With three weeks of hard training left, it seemed inevitable that I’d smash a half marathon course of which I was intimately familiar.

UH OH…

Fast forward a couple of weeks. I’d just finished running an 11-miler on a warm day, capping off a 34-mile week. Not bad for me. But something felt off that night, and by the next day, when I was scheduled to do an hour-long bike ride (my standard cross-training workout), something was amiss. That night, I was sick as a dog.

The next day, it was worse. And worse again the day after that. Congestion, sore throat, drainage and junk in my chest. It knocked me out for a few days, killing off three runs. Later in the week, I felt good enough to get back to it, and to my surprise, a 3-miler went well. The next day, 12 miles were on tap, the first 6 of which were spirited, but the last 6 very meh. I headed into my taper, hoping the nagging cough and chest gunk would be gone by race day.

Too bad, sucka.

THE RACE

I paced myself fairly well in the first couple of miles, but about three miles in, I knew something was up. My lungs were working too hard, and my legs told me they didn’t want anymore. This was a bad sign, with 10 miles to go, and plenty of hills in front of me before the course flattened out about midway through. I told myself that I could catch my breath then, with the hills of midtown Tulsa behind me, and regroup before things got gnarly again at Mile 8.

I never recovered. Every mile was work. Hitting the mild but long incline at Cincinnati Avenue, the kick wasn’t there. I smashed this hill last year, but suffered this time around. Back down on the flat mile at Riverside Drive, I again hoped to recover just a little before the two big hills leading back into downtown.

And that didn’t happen, either. Facing the big inclines of Miles 11 and 12, the challenge was to not give in and peter out, but instead to run these things hard.

One of the things I made sure to do all season long was to run hills. Route 66 is a hilly course, and if all you run are flat sections, you’re going to suffer. The climbs up Southwest Boulevard, then Seventh Street nail me every time on this race, so I purposely created training routes that finished with long, steep hills. Practice makes perfect, and it sure made a difference at the Tulsa Run. It was a matter of pride to conquer these things.

Thankfully, I did. Not fast, but good enough to keep some sort of pace and not slow to a defeated walk. But there wasn’t much left in the tank after that, now that my legs and lungs had betrayed me.

Heading into the Tulsa Arts District, I plodded slowly until the finish was in sight. Just enough reserve was left to quicken the pace and sprint in.

But being nowhere close to a PR seemed inevitable. I wasn’t even sure I’d be faster than the year before, when I trained in a much more leisurely fashion.

THE RESULTS

Not sure it tastes like victory, but it does taste like getting it done.

Being in the B Corral, and well off the start line, it was hard to gauge my chip time finish. I don’t often run with tech, choosing instead to track my progress on the clocks set up on the course.

Instead of beaming in the post-race sun, I hunched down, deliberated what happened and guzzled a Gatorade. No point in lingering, I headed to the shuttle bus to take me back to the start line area.

While on the bus, I dared to look up the times. Punched in my name, then viewed the results. It popped up on my phone: 2:14:30.

Frankly, I was surprised. I was actually faster than last year. Even though I felt like hell, my body wasn’t cooperating and I ran with no fluidity to speak of, I’d somehow performed, well, better. Suddenly this result was now my new second-best half marathon time.

But it was a small consolation. I worked very hard for a mere 31 seconds. That’s the equivalent of walking through one extra aid station. It was also a good 3 minutes off my 13.1 PR. Oy. No two-hour mark, no PR. But faster than 2016. Call it a personal bronze medal.

THE TAKEAWAY

I could have been bummed by this. In some ways, I am. It’s not what I worked for. But I understand it.

When you have a bunch of gunk in your chest, you won’t have your normal cardio. And with that, there goes your breathing and your legs.

But there is something else. A tougher training season made me mentally stronger. There was a lot to fight through in this one, and it was a lengthy battle to keep going at a pace that eventually got me across the finish in a way that did not prove embarrassing. In the last couple of miles, I was wondering if the race might end up being one of my slowest half marathons. So seeing the chip time on my phone during the bus ride downtown showed me that even though I didn’t come close to my goals, I worked hard enough to make progress.

Silver linings, man. You take ‘em where you can.

Bob Doucette

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

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