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.
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.