Monday, May 26, 2014

Sage Burner 50K Race Report

Wow. Quad Rock certainly took its toll on my legs. Three days later I was still hobbling around the house in the morning, wincing with each step. Picking up my kids took considerable effort and was usually accompanied by a melodramatic groan or two. I biked for an easy 30 minutes on Sunday and Monday, and then went for a short 3 mile jog around the block on Tuesday, Wednesday, and Thursday. I took Friday off. Each jog felt a little better than the last. I could feel the various aches and pains from Quad Rock diminishing. Thankfully, I had no major injuries. Just the typical soreness and tweakiness that follows an all-day effort.

Of all my three back-to-back-to-back races this May I gave Sage Burner the least amount of attention. Perhaps because it was the last race. Perhaps because I felt my PR there was soft. I glanced at the GPS tracks from my previous races on Thursday night. It still amazes me how badly I blew up last year. Truly epic. All I really had to do this year was stay properly hydrated. How hard could that be? Simple, right? Yet somehow I've managed to dig myself into a hole almost every time I've run Sage Burner. The weather at Quad Rock never really got that hot, so yet again Sage Burner would prove to be my first ~70 degree race of the year.

I drove down to Gunnison on Friday evening. It's a nice drive, which I joke can be briefly summarized as: mining, cows, mining, cows. I picked up my bib in town, ate a huge dinner at Garlic Mike's, and then drove to Hartman Rocks to camp. I slept in the Subaru just a few feet off the course. Even in the car, it was a bit chilly at night and I was glad to have a down jacket and sleeping bag to keep me warm. My alarm woke me at 4am, I ate a small breakfast, and then rolled over and went back to sleep until 6am or so.

My secret race strategy this year? Carry two water bottles. Yup, genius. The aid stations are generally not that far apart (4-6 miles), but I didn't want to ever be caught without water or energy drink. Throughout the race, I usually kept one bottle full of energy drink and the other bottle about half full of water. Any extra water I would dump on my head as I approached an aid station.

After a short speech from the RD, and a brief countdown, the race immediately began with a short climb straight up onto the mesa. Sage Burner doesn't really have that many long, sustained climbs, but it certainly undulates up and down almost continuously. You run up to the edge of the mesa, then off to a scenic high point with a juniper tree and a pile of rocks to negotiate, then back down off the mesa, then climb back up a gulch, then pick a different high point to visit, then down off the mesa again, repeat for 31 miles.

I took the first half of the race very easy. I just enjoyed the scenery, chatted briefly as I passed various racers, and kept a careful eye on my fueling. My legs felt fine. Not exactly springy, but nothing to complain about. I was very happy to be feeling as good as I was a mere week after Quad Rock.

The 25K and the 50K run more or less together for a while, making for a more social experience. But after the split, it's just the hardy 50K racers. There are generally only 50 or so of us every year, and you can get quite spread out across the starkly beautiful, sage-filled landscape.

I had been leap frogging with a few racers during the first half, but ended up passing them as the uphills kept coming. After the aid station at Skull Pass, around mile 16, I mentally flipped a switch. I had reached the 3 hour mark, I felt great, and I was ready to make my move. So I put on my ipod, cranked up the music, and went to work.

The second half of my race was one of the most satisfying experiences of my brief running career. I felt strong, totally in control, and unfazed by the distance. In some ways, having run a grueling 50 miler the week before was an advantage. Sixteen miles? It's nothing. A warmup. As I cruised across the desolate mesa top towards a distant high point, I could barely catch a glimpse of a red shirt more than a mile ahead of me. My first target. I passed him maybe three miles later, walking, depleted in the growing afternoon heat. That was me last year.

Where was everyone else? I bombed down a technical drainage and out onto a road, where I saw the next runner. I was running sub 8's at this point-- about my top speed. After a short flat stretch on the road, the course climbs up an incredibly steep jeep road back up onto the mesa again. Ah ha! I could see a pack of four runners ahead of me on the switch backs. I grinned at the contrast. A moment ago I was hauling ass on the flats, and now I was passing folks just as convincingly while dropping agonizingly slow 20 minute miles! Ultrarunning is certainly not about locking into a particular pace, but rather a particular level of effort. I was running everything, but my pace was all over the map.

And so the race went. I have rarely felt as confident as I did that afternoon. I was on fire. Everything felt effortless. It wasn't like I was running faster than I normally do on a typical training run, but the distance was having absolutely no effect on me. It was like I somehow managed to string together six 5-mile runs all run at my typical 5-mile training pace. It was glorious.

I finally charged across the finish line in 5:36 in 10th (?!) place. A whopping 45 minute PR. I negative split the race by about 25 minutes and passed about a quarter of the field in the final 10 miles. I had zero stomach issues and felt perfect the whole day. If anything, I probably took the first half of the race a little too easy. But, damn, I wouldn't trade anything for feeling like I did during the second half. Perhaps this was the race that my training this year has best suited me for-- not too fast, not too vertical, yet long enough that endurance matters.

A blurry picture of me near the start. (C) Gregg Morin.
Everyone was very friendly at the finish line, and I was touched by how many racers took the time to shake my hand and tell me how strong I looked as I passed them. I made sure to emphasize that it had taken me five years to finally get it right!

Sage Burner was my very first ultra (and my first marathon!) back in '10, so it holds a special significance for me. I've run it every year since and have accumulated quite a few memories on the course. ("Oh, look! I think that's where I threw up in '12!") I'm so happy to have finally beat the heat and had a successful race there. I've always felt that I hadn't yet reached my potential on the course, but feeling and doing are two very different things. I'm proud to have finally executed. That's all you can ever really ask for in any given race.

I'm so happy to have been able to end my streak of racing this May on a high note. I've got three more weeks of training left before tapering for Bighorn. I'm actually looking forward to taking things a bit easier next week-- especially on my long run. I think I've got enough quality long runs under my belt, and now it's time to focus on some shorter, mid-week quality sessions. Most of the regular trails I run around Leadville should melt out next week. I can't wait.

Next up: the Turquoise Lake Half Marathon. A very different beast. It's going to hurt; it's going to be fun. It's always a good workout. (Probably a better workout for me than yet another 20 miler at this point...)

Friday, May 23, 2014

Quad Rock 50 Race Report

After my debacle at Collegiate Peaks, I paid special attention to recovering as well as I could before Quad Rock-- not just recovering from the race, but from my April training in general. I definitely didn't want to start another race-- especially a 50 miler-- with dead legs. I biked around Turquoise Lake on Sunday, took Monday off, ran an easy 6 miles on Tuesday on the Mineral Belt, took Wednesday off, ran an easy 3 miles on Thursday around the block, and then took Friday off. In one week I more than doubled the number of days I've taken off since the beginning of the year.

As far as goals for Quad Rock went, they were much looser and hand-wavy than my goals for Collegiate Peaks. The only historical data point I had for comparison was my 25 mile run in '12, Quad Rock's inaugural year. I finished that race in 5:17, which seemed about right for the halfway mark of the full 50. Given my modest ranking, Ultrasignup was predicting an 11:48 finish for me. But comparing the course to other 50 milers I've run recently (keyword: recently) I thought that was a bit too conservative.

The biggest unknown for me was really the timing of the race. The earliest 50 miler I've ever run is the San Juan Solstice 50 in mid-June. And I've really struggled each time I've run it. My normal 50 miler every year is the Silver Rush 50 in July. That's the timing I'm most familiar with. So, how would my body respond to running a 50 miler six weeks earlier than I ever have in my training cycle (and nine weeks earlier than I normally do)? I guess I was about to find out! I laughed to myself when I realized that Quad Rock-- in a single day-- would represent a quarter of my total mileage in April and about half of my total vertical!

The other consideration I factored in was that out of the seven 50 milers I've run in the past, I'd say all but one were severely limited by serious nutrition mistakes on my part. Historically, I've really struggled to consume enough calories during the 10+ hours it generally takes me to run 50 miles. However, I finally found a system that worked for me last year, and that has made a huge difference in longer races (i.e., 50's and 100's). So, assuming I could stick to my nutrition plan, I anticipated that I could run Quad Rock faster than my past results might suggest.

So, anyway... taking that all into consideration, and waffling back and forth a bit, I finally guessed that I might finish somewhere between 10.5 and 11 hours. Just my best guess. I would finish when I would finish. My primary goal was to take care of myself-- stay on top of my hydration and nutrition, and try not to kill myself on the downhills. It was going to be a long day of running. Enjoy it.

The Friday before the race, I drove down to my friend Alex's house in Louisville. We're both running Bighorn together in June, and we both signed up for Quad Rock as a training race. The last time we saw each was when I paced him at Run Rabbit Run last September. We enjoyed a quick dinner together, went to his son's t-ball practice, made some last minute preparations, and went to bed early-- our alarms set for the ungodly hour of 2:45am. That would give us just enough time to get dressed, make some coffee, eat a quick breakfast, and drive up to Ft. Collins for the race. I remembered feeling rushed at the starting line in '12, so I didn't want that to happen again.

When we arrived, we were just about to park in a long line of cars about a third of a mile from the start, when someone noticed we had carpooled and directed us to a closer parking lot-- much closer! We ended up parking about 30 ft from the starting line. Sweet! Donning our headlamps in the pre-dawn darkness, we went about our final preparations.

We wished each other good luck, and as the sun finally rose we all took off.

They've re-routed the start of the race so that you stay on the dirt road much longer before hitting the single track. This is definitely a good thing. It made it much easier to spread out and find a good pace. As I ran the initial rolling miles, I was very relieved to feel my legs respond. There was no obvious fatigue like the soreness/tightness that was immediately obvious at the start of Collegiate Peaks. However, temperature-wise, I was much too comfortable at the starting line and, as soon as the sun peeked over the eastern hills, I started becoming too warm. Before the initial climb began, I pulled off the trail and took a minute to take off all my extra layers and throw them in my pack. (I'd eventually dump them in my drop bag.)

The first ascent up to the Towers aid station went well. I slowly jogged the whole thing, moving up many places, passing folks who were hiking. On a few of the steeper sections, my legs actually burned from the effort, which is a rarity for me as Leadville's lack of oxygen is usually my limiting factor! Still, I didn't feel like I was pushing too hard. I had memorized some of my splits from '12 and I knew I was already ahead of my former self by the first aid station.

By the time I had dropped down to the Horsetooth aid station, I had gained yet more time. Everything was going great. However, I had to make one more visit to the bathroom. I ended up waiting in line for what seemed like an eternity. Ah, well... Enforced rest, I guess. I picked up more fuel, refilled my bottles, and headed up the next climb.

My oh-so-fashionable shirt got a lot of comments!
Up, down, refuel, up, down, up, down, refuel, up, down, up, down, refuel, up, down, finish.

And that's pretty much how the day went!

After 11 hours and 6 minutes, I sprinted across the finish line to cheers of "It's the J Crew guy! Yeah!" I certainly felt fatigued, but I was happy. It was a solid race-- and a solid workout, for sure. My legs were toast, but I kept my stomach under control the entire day. It was definitely the longest I've ever been able to run without any stomach issues at all. A victory for me.

The weather was perfect. It started out sunny and cool in the morning and never really got hot as the clouds moved in in the afternoon. It spat rain a few times, and the wind picked up briefly, but I never had to battle the heat. Just to be safe, I dumped water on myself a few times, and dunked my hat in a few streams as a precaution.

I hit the turnaround at 5:02, a 15 minute PR over my previous time for the 25 mile race. I jogged every step of the course until mile 32 or so and then I started mixing in hiking on some of the steeper sections. While the uphills were definitely tough and unrelenting, I felt stronger on them than I did on the downhills later in the race. On the final two descents my quads were screaming. This was definitely way more downhill running than I had ever done in training so far this year. I'm guessing that mashing big gears on my bike trainer has helped build my uphill strength some, but has done nothing for my downhill strength. It's become probably my primary training goal for the next few weeks-- hit the downhills hard to prepare for Bighorn.

My stomach felt solid throughout the day. I constantly tried to strike a good balance between water and calories. I'd often carry one bottle of pure water and another bottle of energy drink and alternate between the two, using the water to flush my stomach out if I ever felt full. I'm convinced that most of my past bouts of nausea have been caused by dehydration. A few times during the race, usually while on a downhill, I did get a side stitch. I took that as a sign that I was falling behind on hydration, and I'd try to drink more water, while jabbing my other bottle into my diaphragm to relieve the pain. All told, I consumed approximately 3,360 calories during the race (10.5 320 calorie bags of energy drink mix). That's about perfect for my body weight and finishing time.

The slower 50 mile pace allowed for lots of friendly conversations during the race. It was great to meet folks and pass the time chatting as we fought the hills together. Despite the grey weather, the post race festivities were great. I scarfed down multiple hamburgers and enjoyed the complementary beer. One of the best signs that you've fueled properly during a race is how quickly you can eat a normal meal afterwords.

While ideally I would've liked to have not have slowed down quite so much during the second half of the race, I feel like I can't complain too much. I felt good out there. Certainly not overwhelmed by the distance. I keep coming back to the word "solid". You know things have gone pretty well if that's the adjective that keeps popping into your head.

Next up: the Sage Burner 50K. It'll be the fifth time I've run it, and I have a score to settle with the course. It's time to recover as best I can, and hopefully time for a little redemption!

Monday, May 19, 2014

Collegiate Peaks Race Report

A quick report on my CPTR 25 experience this year. It's short on narrative flourish, but hopefully captures some of the details of the event.

The weather on race day was beautiful. Probably the warmest day of the year so far. While I imagine the 50 milers might have suffered a bit in the afternoon heat, for the 25 milers it was perfect. I was excited to race and soaked up the energy at the starting line. Before I knew it, we were off.

Within the first mile of the race I found myself uttering, "Uh, oh... Oh, crap!"

My legs felt strangely tight/sore during the first 3 paved, flat miles. Mostly my calves, but also my legs in general. Still, I made it to the turn at mile 3 on PR pace. Next came a rolling, single track section. I didn't obsessively check my GPS between aid stations, but instead ran by feel. I was only 1 minute back at the first aid station at mile 6. Certainly not time to panic yet, but I knew I wasn’t really feelin’ it. For some reason, I hadn’t recovered fully during the week leading up to the race. Why were my legs so unresponsive?

The next 4 mile uphill section would be a test. I tried to stay positive and not succumb to any negative self-fulfilling thoughts. Unfortunately, I slipped to 4 minutes down at the second aid station. Not good. I wasn’t really passing anyone on the uphills. My last hope for a PR was to try to make up some time on the downhills, but all I could do was maintain my pace-- barely. The 7:30 min/miles I was hoping for were not happening. I was still about 4 minutes down at the base of the final uphill. Could I push harder up Lenhardy Hill than I did last year? Doubtful. I honestly thought the best I could do was to maybe stay on pace. Nope, not even that. I was down 9 minutes at mile 18 at the top. A PR just wasn't happening today. There was no way I could make up 9 minutes in the final 7 miles-- certainly not with the way my legs were feeling. Dammit. Ah, well...

At that point, I gave up trying to PR. I switched modes to "just get ‘er done" and stopped chasing splits. I passed a couple of blown up people in the final miles, but nobody that was really running. I chatted with Adrian S. (who I recognized from the Silver Rush 50 and Sage Burner 50K last year) for the last 3 miles. He was running the 50 today. I settled into a relaxed 50-mile pace with him and took it easy to the finish. It was nice to be able to pass the time chatting with someone. Finally, I jogged across the finish line, down 14 minutes from last year. 4:16. I didn’t even bother trying to squeak in ahead of the racer in front of me. I had no desire to pass. I had stopped racing miles ago.

If I had kept pushing for the full 25 miles, maybe I could’ve finished only 10 minutes back from my PR... I just couldn't motivate with my legs feeling like they did. I'd like to think that I'd be more willing to push through leg soreness that arose during the race itself, but pre-existing leg pain due to inadequate recovery? Not so much. I don’t think I really made any mistakes during the race, I just hadn’t recovered fully. Not enough rest during the final week. I think my high-cadence bike workout on Monday really worked my calves in a way that they're not used to. Then I simply slogged up and down the Boulevard a bit too much-- trying to get 200 miles for April. Trying to keep the daily training streak going. I should’ve skipped some days if I really wanted to race fresh. Basically, my race this year felt like a ho-hum training run. Fine, but not great. If I hadn't been racing I probably would’ve stopped a dozen times and rested and soaked up the views. My energy levels were fine, but my legs had no pop.

Of course, I never fully taper for any non-focus race like CPTR, so I don't expect to be at 100%, but-- superficially, at least-- my mileage for the week leading up to the race was the same as last year. That's all I was hoping for: to make it to the starting line as rested as I had been previously in '13.

In hindsight, I really think I pulled off something special last year when I set my PR of 4:02. I really raced the course, and as I kept beating my past splits I got more and more excited and motivated and really kept up the intensity. Having people to chase was great, too. There was a small group of runners that I hung with throughout the race in '13. This year, I tried to keep my spirits up and enjoy the race, but eventually I knew a PR wasn’t going to happen. There was no desire to hurt more than necessary. Thoughts of conserving myself for the Quad Rock 50 the following week crossed my mind. I was actually fairly comfortable on the uphills, but the lack of “pop” slowed me down ~1 min/mile. I just slowly jogged uphill, losing some distance on folks-- not that much, but enough that I noticed it. I’d actually close gaps on the super steep sections when people dropped to a hike. I did manage to run the entire course again, never resorting to a power hike.

Ironically, I finished in 46th place-- the exact same place I finished last year, despite being 14 minutes faster.

Not so much green. I had no uphill legs (miles 4, 9, 10, 16, 17, 18). Stopped chasing my former self at mile 18.

After looking over my training data from last year again, it’s interesting to note that I had a lot of “blah” training runs after CPTR last year. CPTR was really the only long run I nailed in May '13. My average pace on all my other May training runs (which all had roughly equivalent vertical) was about 1-2 minutes slower per mile. So, maybe I just hit that “blah” period a little earlier this year because of the extra miles/long runs I’ve been running? However, even if I had started the race totally fresh this year, I bet I could have done no better than, say, 3:55.

My extra training this year has put me in a good place, but not one that’s radically different.

I knew it would be difficult, but not setting a new PR this year was a little tough to swallow. I thought I was fit enough-- and that I had recovered enough-- to have a chance, but apparently I was wrong.

Well, I know of no better remedy for a disappointing race than to get back out there and race again! I'm looking forward to the Quad Rock 50 next weekend. While certainly more epic, I think it will also be more low stress. I've never run the full 50 mile distance before, so I won't be obsessing over splits. Plus, the longer distance will make the race more about taking care of yourself throughout the day.

Despite no PR, I still had a lot of fun at Collegiate Peaks this year. It's always a great race. And, hey-- it was my second fastest time ever! My wife and kids joined me at the finish line. I got to say hi to a lot of running friends and catch up with various folks. The weather was truly beautiful. Afterwards, the kids and I played in the ice cold stream while mama went off for a run by herself. It was good to relax and enjoy a lovely spring day in Buena Vista with my family. I topped it off with a giant blackberry shake at K's. A classic.

Wednesday, April 30, 2014

Month in Review (April)

4/2010: 163.3 miles
4/2011: 135.0 miles
4/2012: 164.9 miles
4/2013: 175.0 miles
4/2014: 200.1 miles

TL;DNR: Training is going well! I have lots of races coming up! I overthink things!

Well, somehow, I actually managed to survive April intact. All things considered, I'm pretty happy with where I'm at training-wise and I'm certainly excited for the next three weeks of racing.

I've been looking forward to May for a long time.


Three races, three weeks, 106 miles. One final month of training before the Big Horn 100 in June.

Heading into this year's training I knew April would be logistically tough. Perhaps my toughest month. Two months out from a hundred miler, variable spring conditions (to put it mildly), a family vacation, ten days of single parenting while my wife was off backpacking in Utah, and my precocious daughter's 5th birthday. There were a lot of responsibilities to balance. I'd have to get creative with my schedule and sneak in workouts whenever I could.


Colorado National Monument, Fruita, CO. A nice escape from winter.

This month was an incremental improvement over previous Aprils. Nothing fancy. No radical departures from my typical spring routine. I ran more or less the same routes I usually do this time of the year. I just tried to focus a little more on quality, pushing it a bit more than usual once or twice a week. Usually on the downhills. Earlier in the year, I was worried about trying to get a lot of vertical in April and I imagined myself climbing Mt. Elbert and/or doing laps up and down Ski Cooper. Instead, I eventually decided to let that dream go and focus more on speed. (Or, what passes for speed for me at 10,000 ft.) It was logistically easier, if nothing else (i.e., less driving to trailheads, more road running from my door). Plus, looking at my monthly totals over the years, it struck me how much my average pace slows down in June, July, and August when all I'm doing is running up and down the local peaks. April has always been one of my fastest months, simply due to the fact that my long runs tend to be flatter and at lower elevations. Perhaps I've under-appreciated the benefits of a 3 hour 20-mile run. Of course, aesthetically, I'll always prefer the 5 hour 20-mile trip over Hope Pass and back in June. There's no question about that. It's just more fun. But that doesn't necessarily mean that a flatter option run at a faster pace doesn't have its place. Variety is the key to adaptation and improvement-- or so I tell myself.

On top of Red Hill, Carbondale, CO. 800 ft of vertical in 1 mile. Mt. Sopris in the distance.

So, with the generous help of my wife, babysitters, Aunt Jennifer, and some PTO, I managed to string together four weeks of relatively consistent training. Sure, I spent a fair amount of time on the bike trainer, but no more than last April. I ran a long run every week, plus a couple of 10-milers midweek when time and weather permitted. Though we still have plenty of snow leftover from winter, April's weather was actually pretty nice. Much better than the blustery, grey April we had last year, that's for sure. I set a few PRs on some local routes around town, so that was a nice confirmation that my training was headed in the right direction. Still, I had some nagging doubts about my fitness as I never quite nailed a long run. I was putting in some solid efforts, but generally a bit slower than similar runs I ran last April. On paper, I was supposed to be in better shape this April as I had more miles, more time, and more long runs under my belt than ever before.

Expectations are dangerous things.

Last Friday, on my long run down in Buena Vista, I finally nailed it. As has become my tradition, I run a 20-mile loop on the course the week before the race. I took the first 13 miles pretty casually, up until the top of Lenhardy Hill. It was a gorgeous spring day. Checking my watch, I was about 2-3 minutes slower than my effort up until that point on last year's training run. Then I gritted my teeth and pushed for the final 7 miles, making up ~1 min/mile, and set a 5-minute PR for the route. It felt great.


Around mile 14 on the Collegiate Peaks course. Mt. Princeton in the distance.

Setting a PR on a long run was the final missing piece of evidence that I was hoping for. All my training these past four months seems to have paid off. And, maybe-- just maybe-- another PR at Collegiate Peaks is possible this year.

I consider last year's race one of the best races I've ever run-- second maybe only to last year's Silver Rush. It was a good day. A very good day. I surprised myself. I honestly think it would be easier (though by no means easy) for me to set another PR at the Leadville 100. So, another PR at Collegiate Peaks will be very tough-- far from guaranteed. If I could improve my time by 5 minutes and go sub-4 hours, I'd be thrilled. Of all my races this May, I find Collegiate Peaks (the shortest race) to be the most intimidating-- precisely because my PR is so stout; the margin for error so slim.

Even though it isn't a focus race for me, I am still very motivated run Collegiate Peaks as well as I can. I often tell myself that I should just relax and quit obsessing over splits... If I PR, great. If not, who cares? But, I do enjoy the challenge of setting a PR. It's a very personal challenge-- I'm racing against my previous self, chasing my own ghost. It's an affirmation of all the extra work I put in during training this year. All those slow, snowy slogs up California Gulch. I know at some point the PRs are going to stop. And I certainly can't expect the ridiculous PRs I managed to set last year to continue indefinitely. I love trail running for its own sake. And I can think of no better way to spend my days during Leadville's wonderful summers. But, I can't deny that working hard and seeing an improvement is very rewarding too. So, I guess I'll enjoy it while I can! Like everything, there's a balance. You want to see constant improvement, but there are limitations and factors beyond your control. Tight calves. A side stitch. Heat. A strong headwind. A cold. Any of those things could easily slow me down the few minutes it would take to put a PR out of reach.

So, we'll see... I'm excited. I'll be grateful to show up at the starting line healthy, ready to race. Who knows what will happen? That's why we run these things...

Saturday, March 29, 2014

Month in Review (March)

3/2010: 109.0 miles
3/2011: 129.6 miles
3/2012: 153.3 miles
3/2013: 174.7 miles
3/2014: 192.4 miles

Looking Behind

March was a month of extremes. There were many days when all I could muster was a 30-minute ride on the bike trainer or a 3-mile run down the Boulevard. It was exceptionally difficult to motivate myself to get outside the week after I returned from the warmth of Florida. But, in contrast to these short bouts of exercise, I did manage to get in 5 long runs-- one each week. Definitely an improvement over last year. I'd estimate that those long runs accounted for half of my mileage every week-- meaning they accounted for half of my mileage for the entire month! So, I hit my modest mileage goals for March, but the distribution of those miles was perhaps a bit... unorthodox.

My daily exercise streak is now at the 3-month mark. I like the discipline of carving at least 30 minutes of time out of my day to exercise-- even if it means riding the bike trainer at 9pm after the kids are asleep and the dishes are done. There is no waffling, pondering "Should I exercise today?", there is only "When should I exercise today? What should I do? Bike? Run? Ski?" I keep waiting to come down with a cold and be forced to skip a day or two, but luckily that hasn't happened yet. Everyone in my family is hacking up a lung except for myself. Knock on wood.

So, I'm feeling pretty fit. Not amazingly fit by any means, but better than I've ever felt for this time of year. If I had to guess, I'm maybe as fit as I was last year in May. Maybe. It's hard to tell. Hopefully I can buckle down, continue to improve in the coming two months, and whip myself into shape for Bighorn.

Salida Marathon

Of course, one of my long run runs-- in fact, the longest of my long runs-- was the Salida marathon. As always, it was a great race and a ton of fun. It's sooo nice to be able to run on (relatively) snow-free trails at this time of year! My race went well-- not off the charts by any means-- but I'm pleased with the result: 4:46. That represents an 11-minute PR for the course. Secretly, I was kind of hoping for something closer to 4:30, given all my extra training this year, but that would've required much more effort on my part. In retrospect, I think I ran the race a little bit too comfortably. I felt absolutely great before, during, and after. I kept things conversational almost the entire time. I enjoyed myself. I ran the last mile of the course at basically the same pace as I ran the first mile. And I was able to grunt up the hill at mile 21 more than a minute faster than I did last year. Everything felt very sustainable. I didn't listen to any music during the race, which is rare for me, and probably made me a little less aggressive and more inclined to chat up neighboring runners and simply enjoy the sights.


Mile 3

One thing I did differently-- which led to humorous results-- was try to drink more water. I'm convinced that when things go badly for me during a race it's almost always due to dehydration. So, I wanted to practice drinking more fluids. Since I pack 310 calories into every bottle I drink, I only get about 18 oz of liquid per bottle. Which means I generally only get 18 oz of liquid per hour. Not quite enough, I've learned. I think I want to be closer to 24 oz of water/hour, depending on the conditions. This will hopefully keep the osmolarity of my energy drink lower and make it easier to digest. So, I carried two water bottles during the race even though the aid stations were generally less than an hour apart. The exact numbers were difficult to keep track of, but I'd generally try to hit my targets for calories and liquid by keeping one bottle at full concentration and another bottle at a more diluted concentration and alternating between the two. Of course, the cool, cloudy weather on race day did not warrant 24 oz of water/hour, so I must've spent 5 minutes peeing on the side of the trail throughout the day! The sacrifices we make for science...

Looking ahead

So, I survived March. April's next. I think it's going to be my most difficult month of training, at least from a motivational perspective. It'll also be logistically tricky. My wife will be in the field for 10 days-- overlapping two weekends-- leaving me as the sole parent. The rough goal is another 5 miles per week, bringing me up to ~45 miles/week. The question is how to best divide up those miles into quality workouts given the conditions in Leadville.

According to the calendar, it's spring. Looking out my window, it's winter. The roads around town are beginning to melt out, but the trails will have to wait at least another month. Looking at my training log, I can see that in '12 I was running the local trails during the first week of April. That was a very dry winter. Last year, they didn't melt out until May. This year, it's looking like I'll have to wait until May again. My dreams of another early melt don't look like they're going to happen.

So, what does that mean? Running roads, roads, and more roads. Some dirt, but I'm going to have to embrace the asphalt for most of my running next month. And, given my limited options, that means that April probably won't be very big in the vertical department-- at least, certainly not where I would normally like to be at two months before a 100. I'm going to have to mix things up a bit and try to substitute some speed for elevation gain. Given the choice, I prefer the later. But, I've come to accept the fact that I'll have to wait until May to start running up mountains... In a lot of ways, what I've been doing so far is just base building. Sure, I've had a smattering of quality workouts where I pushed myself-- most notably in Florida-- but mostly I've just been slowly ramping up the miles without ramping up the intensity. That's going to have to change in April, I think.

May will be fun. The leaves will come out; more and more of my favorite running routes will open up. In many ways, May will be the reward for all this early season training-- huffing-and-puffing up and down the same roads every week. I've got 3 back-to-back-to-back races lined up: the Collegiate Peaks 25, the Quad Rock 50, and finally the Sage Burner 50K. It will be a cycle of race, recover, race, recover, race, recover. Then a final two weeks of peak training, then the taper for Bighorn. It's crazy to think how close it is!

Friday, February 28, 2014

Month in Review (February)

2/2010: 100.9 miles
2/2011: 111.3 miles
2/2012: 151.9 miles
2/2013: 137.8 miles
2/2014: 186.5 miles

Well, another month of training is in the books. I'm pleased with how it went, all things considered. My goal for February was roughly 35 miles/week, and I ended up running closer to 40 miles/week, with a 60-mile week thrown in while I was on vacation down in Florida. I very rarely run more than 50 miles/week-- even during peak training-- so that was notable. Naples, FL is flat, fast, and oxygen-rich compared to Leadville, that's for sure. Oh, and humid. Incredibly humid. I would return from early morning runs completely drenched in sweat. Running in the dry mountain air of Colorado is downright civilized in comparison!


Not Leadville.
February began with the snowshoe marathon as my first long run, and then I managed to get in another 20-mile run in Florida. (One took >5 hours, the other <3 hours. I'll let you guess which one was which.) I integrated some skate skiing into the mix early in the month, to keep things interesting. I resorted to the bike trainer 8 times-- usually when the weather was nasty or when I was recovering from a hard workout. The other statistic that jumps out at me is that I managed to run 7 runs longer than 10 miles in February. The way my training schedule tends to work is that the only run I'll run longer than 7 miles will be a 20-mile long run. I don't often run any distance between 7 and 20 miles. Just a quirk of habit, I guess. I'm sure more tempo runs around the half-marathon distance would be beneficial. I think I just naturally gravitate to hill workouts during the summer-- like the Powerlines, which is 3.5 miles up and 3.5 miles down (with 1,700 ft of vertical).

Speaking of which, the one area I wish that I was doing better in is vertical gain. Sure, I've logged plenty of miles. Last year, I didn't run more than 180 miles in a month until May. But, if we compare February of '14 to, say, April of '13, yes, I ran 10 more miles this February, but with only half the vertical gain. I find that the snow makes it tough to get in a lot of vertical around town. For plowed roads, you've got 7th St, 5th St, and Cal Gulch. All uphill, but nowhere near as steep as the trail options that are available in the summer. If you want something steeper you pretty much have to wear snowshoes and wade through thigh-deep powder. Not necessarily a bad thing, but not exactly, well... running. I'll be honest and confess that I've had "inappropriate" thoughts about giving in and joining the local gym just so I can use the treadmill. That would not only give me another pre-breakfast (too cold outside) or post-dinner (too dark outside) workout option, but could also help in the vertical department. (I know, I know... I should just suck it up and go snowshoe up a mountain.)

They say that the foundation of proper periodization is making your training look more and more like your goal race the closer to the race you get. So, I guess, I can rationalize all this by saying that now is the best time for me to be running fast(er) and flat(ter). As I get closer to Bighorn, my runs will get slower, hillier, and longer. A better match for the conditions I'll encounter during the race itself. With this in mind, I've started to experiment with incorporating a tiny bit of speedwork into some of my midweek runs. Mostly just a few short fartleks. Trying to hold a 6:30-7:00 min/mile pace for half a mile or so when the terrain is flat. (Don't laugh.) This is all very new to me. I've never tried speedwork before. Damn, it's hard. And humbling. But it's one more dynamic to keep things interesting during these winter months. Plus, if I'm not happy with my performance I can always blame it on the snow! Or the headwind ripping off of Mt. Massive. Or the altitude. Or...

The new version of the FluidFlex came out in February! I'll be ordering a few more pairs...
So, ultimately, I find myself feeling pretty confident in my early-season fitness going into March. The Salida marathon is only two weeks away, which is exciting to think about. On paper, I should be in better shape than I've ever been in at this time of year. How much better? Who knows? I'd really like to believe that another PR at Salida is possible. I've already glanced at my splits from last year's race and identified a few sections that I feel I could improve on-- mostly on the downhills. So, we'll see... 4:57:36 is the time to beat. I'd be happy with 4:45:00.

My goals for March? Pretty simple. 40 miles/week. And a long run every week. Let's hope the trails down in Buena Vista melt out soon! It's go time.

Monday, February 10, 2014

2014 Training Plan

So, I took some time to scribble down (metaphorically speaking) some training notes and goals for this year. I've been tossing a lot of these ideas around in my head (and in previous blog posts), but I wanted to write them all down in a single place for reference and (hopefully) motivation.

As I've said before, with the Bighorn 100 looming in June, April and May will be the most important and challenging months for me. I'm basing my training this year off of my previous year's training (which I feel went extraordinarily well), just pushing things up about a month; trying to take what worked and making small improvements when I can. Consistency is the key.

Even if my training goes perfectly, I don't think I'll be in quite as good shape this June as I was last August, but hopefully I'll be pretty close. Regardless, I'm very excited for something new.

In other news, last night I set a PR for the most pieces of pie eaten during a workout!

December Plan

‘12: no real training.

‘13: Races: Ha!

25 miles/week. Survive the holidays. Diversify training: add in snowshoeing.

(Mixed. I didn’t quite get in the mileage I wanted. No big deal.)

January Plan


‘14: Races: None.

30 miles/week. Nothing too crazy. Just exercise every day. Two flat long runs. Snowshoe a lot. The two long runs will easily push me over my mileage goals for the month.

(Success.)

February Plan


‘14: Races: Leadville Snowshoe Marathon.

35 miles/week. Again, nothing too different. Exercise every day. (I missed a lot of days in ‘13 due to sickness and travel.) Two long runs (the same number as in ‘13). One of which will be the snowshoe marathon and the other one will be in Florida. Take advantage of Florida vacation to put in a hard training week. (Lots of flat tempo runs.) The timing for the Salida Marathon (3 weeks out) is perfect. Skate ski to stay motivated.

(So far, so good.)

March Plan


‘14: Races: Salida Marathon.

40 miles/week. Nothing too radical, but careful planning for long runs will be required. I want to get in a long run every week. (4 or maybe 5 long runs?) That should get me more than enough miles for the month. Looking at April ‘13 for comparison, my long runs were all easy. Only 2,500 ft of vertical each. The CPTR course (x2) and around town. The Grand Canyon was the only exception. (And who knows how good a workout that really was due to the stomach flu?) Perhaps a snowshoe up Mt. Elbert near the end of the month? A PR for the Salida Marathon would be nice, of course. And a confidence boost for my early season training. Not sure I can really get a lot of vertical midweek in town. Up to Adelade, I guess? Maybe a Mosquito Pass snowshoe? Black Cloud gets me 1,200 ft vert in 10 miles. Fri: Blackcloud + Sat: long run would be a good combo. Hopefully BV will open up as a weekend long run possibility. If not, another flat/fast 20 to Halfmoon Rd might be required. Historically, my first training run in BV was: ‘13 3/7, ‘12 3/23, ‘11 3/1, ‘10 2/27. So, there’s hope, but-- damn-- we have a lot of snow right now.

April Plan


‘14: Races: None.

45 miles/week. This will probably be the month that will be the most difficult for me to hit my training goals. There’s just a lot going on and conditions will still be snowy in town. I want April ‘14 to look like May ‘13. ~225 miles, 27,000 ft vert. Except, I want more vertical on my long runs. I was only getting 3,500 ft vert with each long run in May last year. So, maybe 30,000 ft vert total for the month as a goal? I won’t have to taper like I did in May ‘13 because I have no races in April ‘14. I’ll need to take advantage of high vert midweek runs (1,000+ ft vert). However, with Christina in the field for a week, it will be tough to get in adequate miles. There’s also our family vacation to Fruita/Moab… I will probably have to take a few midweek days off from work to get in my long runs. Maybe throw in some two-a-day workouts? Maybe I can get some vertical doing sections of the Colorado Trail + 14ers down near Salida? I also kind of wanted to do some speed work in April prior to CPTR. That would not help with the vertical, though. Maybe total vertical shouldn’t be the emphasis for April… Sure, maybe get in 1 high vert long run, but the rest are my normal spring long runs (CPTR course, Clear Creek Road, Twin Lakes, etc.). I could tack on Midland Hill for more vertical during my BV long runs… Fri: quality + Sat: long run will be important.

May Plan


‘14: Races: CPTR 25, Quad Rock 50, Sage Burner 50K.

50 miles/week. I want May ‘14 to look like June ‘13. ~250 miles, ~50,000 ft vert. Racing in warmer climates will help (BV, Ft. Collins, Gunnison). I have 3 back-to-back weekends of racing planned. I only need to go on non-racing long runs twice. Memorial Day weekend will be my final uber long run (Mt. Elbert + Mt. Massive: 26 miles, 10,000 ft vert). Due to all the racing, and the warmer weather, my May goals actually seem more doable than my April goals.

June Plan


‘14: Races: Bighorn 100.

June will be: taper, race 100 miles, and then recover. I’ll run Native Lake (18 miles, 3,500 ft of vert) 3 weeks out. Then a 10 miler the following weekend. Then Bighorn 100. Fill early June with lots of power hiking leading up to Bighorn. No hard downhills. Try to run every day, just get slower and shorter as Bighorn approaches. Take care of knee. Stay loose. More power hiking and biking for recovery after Bighorn. Due to the race, and all the hiking for taper/recovery, I will probably match my ‘13 levels for total mileage and vertical for the month, I think.

July Plan


‘14: Races: None.

An easy week at the beginning of the month, for sure. More power hiking. More biking. Continue to recover. Maybe run (not race) the Silver Rush 50 if I’m feeling good? That would be 3 weeks after Bighorn. Then two weeks of quality training (probably do Hope Pass at least once, if not twice) and then my taper for the Leadville 100 begins! Due to Bighorn recovery, I will not be able to match my monthly totals from ‘13.

August Plan

Races: Leadville 100.

Same as last year. Taper, taper, taper. Then race Leadville. Goin' solo: no pacers this year. 5-10 minutes slower to Twin Lakes, hydrate better, make improvements over Hope Pass, both out and back (goal: 3:30 each way), and from Mayqueen to the finish (goal: 3:00-3:15).  Finish strong. Another PR would be nice, of course, but I'm doubtful that I'll be in better shape than last year. Most importantly: just enjoy it.