 |
| Crossing the finish |
Though my trip to the Grand Canyon for the double-rim crossing was an ultra
distance, Bootlegger was my much-anticipated first actual ultra
race. And it didn't disappoint.
First things first though. The folks at
Red Rock Running Company and a horde of awesome volunteers made this a really great race. The trail was well marked, organization was good, race website was awesome, aid stations were on point, and the swag was killer.
And I have to give a big shout out to my awesome crew chief -- my wife, Jackie. Sure this was only a 50K and I probably didn't need a crew, but it was really cool to have her there and she was great. Plus, a familiar face at an aid station is a nice psychological boost!
A clutch of really solid runners from Arizona came up for the race and rocked it. James Bonnett grabbed the W with a 4:09 finish. I wasn't too far behind (cough, cough) at 5:17. That scored me a 13th place finish, which I wasn't too disappointed with for my first shot at an ultra-distance race.
Rather than trudge my way through a blow-by-blow recap of the race, I figured I'd distill it down to a few "lessons learned" from the race.
1. If you want to post a killer time, don't punish your legs weeks before the race.
Tapering is common knowledge. That is, in the weeks leading up to a race, you reduce your training to make sure your legs are fresh and ready to go. I didn't do that this time around. Exactly two weeks ago, I did a 42-mile
double crossing of the Grand Canyon. Two weeks ago. That's 14 days. You don't have to be a runner to know that that's
not tapering.
Oh well. Would I have done it differently? Not a chance. The Bootlegger race was awesome, and I wanted to do my best. But running the Grand Canyon? That's something that's a huge privilege and I'm damn glad I did it, even if it did mean that I didn't put up the best time I could have at Bootlegger.
2. Go out amped, get slammed.
I was so excited for this race.
So excited. That's great, but it also meant that I completely ignored sticking to a sober racing strategy. I bombed down the short downhill that started the race, ate up the 1,000-foot climb into the canyon, and was logging 7:30 and 8-minute miles through the flatter sections. My split on the first 15+ mile loop was around 2:20. That's roughly a 9-minute-mile pace, which is no joke for a runner of my caliber when you've got around 2,000 feet of climbing.
The result? I got owned by the second lap. I did a bunch of walking on the initial climb, more walking on the backside climbing, and my legs felt like they were running through molasses even on the flat sections. I had hoped to run either an even effort or even negative splits -- not even close. My second loop was around 40 minutes slower, putting my second-lap pace at around 11 minutes per mile.
3. Fuel, fuel, FUEL!
 |
| Cruising into an aid station |
I generally try to take in around 250 calories per hour on efforts of three hours or longer. I whiffed on this badly in today's race. Why? Part of it was that cold temps early in the race seemed to sap my appetite. The brisk pace that I set at the outset of the race also made it more difficult to eat (mistakes often compound on themselves).
By the last two aid stations (roughly four hours in), I had taken in around 600 calories. Why is this a problem? The early intensity likely ate up a significant chunk of my glycogen stores and so it would surprise me not one bit if my late sluggishness had a lot to do with being low on fuel.
I gorged on pretzels, bananas, and Coke in the last two aid stations, which no doubt helped me on the last seven miles, but it would've been great to have done that earlier.
4. Downhill > Uphill
Downhill running can do a number on your legs, but I'd heard again and again that it's tough to gain too much of an advantage by being a bomb uphill runner, but sharp downhill chops can make a big difference. I saw that borne out today. Not surprisingly, I got passed while struggling up the climb into the canyon on the second lap and runners further back made up significant distance on me. But after cresting the peak I launched into some pretty quick downhill running that put me back ahead of the fella that passed me and left those closing in in the dust (well, except for one woman who ended up dusting me a few miles later).
5. You'll be warmer than you think.
I live in Las Vegas, which means that through September I'm still wrangling with 100-degree-plus temperatures. Since my blood has thinned out from years of living here, it also means that I'm not much of a fan of colder temperatures. For that reason, my immediate reaction to a chilly forecast is to layer up. But I've learned -- after doing that many times -- that I rarely end up being nearly as cold as I think I'll be once I start running. In fact, I generally end up overheating, sweating, and looking for the closest place to stash my heavier duds.
Though the forecast was for crisp 37-degree, wind-chilled temps for the morning of the race, I opted to go out with shorts, a short-sleeve shirt, thin running sleeves, and light gloves. Except for the gloves -- I ended up not being able to feel my fingers for much of the race -- it was a good call. I was plenty warm while temps were still cool and the sleeves were quick and easy to shed when it warmed up a bit.
6. Leave it all out there.
I made some mistakes today. My performance was probably hurt by the Grand Canyon voyage. Two of my goals were to run even or negative splits and finish in under five hours (the other was to just finish) and I didn't hit either. However, when I finished, I didn't have anything left in the tank. I'd put it all on the course. Perhaps I could have done better, but when you give it your all, there's not too much more that you can ask of yourself.
 |
| Loved the race, but happy to be done |
--