A (Heavily) Modified Approach to 26.2

My last taper run is complete. I've got nothing but rest and sleep on the schedule for the next six days. I’m as prepared as I can be. The waiting…the long, agonizing, frustrating waiting is almost over.

This is a journey that started out with the best of intentions. In late December and early January I had begun ramping up my total mileage even hitting a high of 17 one very cold day in early January. While not where I wanted to be yet, I felt like I was on the right track.

Then, one of the worst injuries I’ve encountered hit me. This was unlike any nagging, chronic pain I’ve experienced in the past. Even the foot problems that required me to have surgery three years ago were not so pronounced.

Reading various online sources I tried to determine if I had a really bad case of IT Band Syndrome, ligament damage or tear to one of my calf muscles. Lacking an MRI, I guess no one can say for sure, but I think my doctor got it right when he said it was probably and injury to my soleus muscle. He noted this one is slow to heal.

So since early March, on his advice, I’ve been seeking treatment at the Lone Tree office of Cherry Creek Wellness Centers. Nick, my therapist, has done various things to help me heal more quickly than I might have on my own. Most if involves dry needling which is uncomfortable at best and very painful at worst. He also has been working me through various stretches, balance exercises and a taping regimen.

While this has helped, it was no magic bullet either. As March wore on, I became increasingly pessimistic about doing this race. Maybe I could switch to the half or perhaps just eat my entry fee and drop out.

I managed to start running again with less pain, but it was still there and it was clear that recovery from this injury would (and will) be measured in months rather than weeks. As I finished a short run one afternoon, I noticed that my walking pace was under 15:00 per mile. That’s not blistering, but that combined with some running would actually allow me to finish the race while there were still people at the finish line.

Hence, my decision back in early April to try a long run/walk with a big emphasis on the walk part. Figuring it made the most sense to mimic the actual Colorado Marathon course as much as possible, I set out on a point-to-point from home to the far side of the Cherry Creek Reservoir Dam:

It was not easy and a few hills near the end had me walking far more than I had planned to. But I did it. At the end of that run, I had covered 20.75 miles in about 4:06. Not exactly a blistering pace. In fact, slower than my pace from 7 years ago in the Rock-N-Roll San Diego, but not a DNF either.

A week later I fell a little short but still managed to run 17.25 and then a week later, I did 13.1 including a 300 foot climb in the second half.

All of this hurt quite a bit, but it has restored my confidence. So now I have an idea of what I’d like to try and accomplish this Sunday. This is an ideal, not necessarily what I think will happen, but it’s good to set a stretch goal so that even when falling short, you’ve still accomplished a lot.

Miles 1 - 5: Run four at 10:00 pace, walk 1 at 15:00 pace for a total time of 0:55:00

Miles 6 - 10: Run four at 10:00 pace, walk 1 at 15:00 pace for a total time of 1:50:00

I actually more or less did this on my 13.1 mile run a week ago.

Miles 11 – 15: Run four at 10:30 pace, walk 1 at 15:00 pace. Total time elapsed: 2:47:00

Miles 16 – 19: Run three at 10:30 pace, walk 1 at 15:00 pace. Time: 3:38:00

Miles 20 – 22: Run two at 10:45 pace, walk 1 at 15:00 pace. Time 4:14:30

Miles 23 – 24: Run 1 at 10:45 pace, walk the other at 15:00 pace. Elapsed: 4:40:15

Miles 26 – 26.2: If at all possible, run at 10:45 pace. Final time: 5:03:54.

I’m likely to be very tired and sore starting around 16 to 17 miles in. What’s more the steepest hill on the course is at about mile 19.

Yet there is also reason for optimism. Heat, as it has always been, is my enemy. It did me in at HITS last year and has made havoc of multiple training runs. Fortunately, the current forecast is a high of only 62 and that is likely to be later on in the afternoon, long after the race is over. Gravity is also an enemy. I know there are people out there who actually like running up hills, but I don’t understand them. Granted, I don’t like steep descents such as those found in the early part of the Horsetooth Half Marathon but this race averages an easy 0.8%. Indeed, the steepest hill I found on the course profile is 2.2% which is on the down side of the big hill at mile 19.  Finally, I’m resting all week. My sore legs will be given a break this week with nothing more than walking a few blocks in San Francisco when I’m out there for work for couple of days.

This will be a challenge. Next week at this time, I’ll be incredibly sore and tired. But in the end, I’d rather go out and do a full 26.2 at a slower-than-hoped-for pace than have an even more disappointing 13.1 or a downright demoralizing DNS.

Regardless of the outcome, look for a complete race report here next week.

Thanks for reading and have a great week ahead!

Twenty

Last I posted, completing the Colorado Marathon was all but a distant hope. I figured I’d be contacting them this week to change my distance down the half and then just hope I could complete it.

But a funny thing happened after my short run on Thursday.

I started that run the way I've been starting all of them lately—with a walk. Given my injured leg, walking for the first quarter mile or so gives me a chance to further loosen up the muscles. I definitely stretch before hand, but this is just a little more time to get ready for the run.

As I moved along, I noticed that my walking pace was in the low 13 minute range. It even dipped into the high 12 minute range a few times. As I ran, I started doing the math. Me doing math in my head is a dubious proposition at best, all the more so when running. However, I estimated about out about how long it would take to do a full 26.2 at an average pace of 13:00 per mile: 5:40. That’s pretty slow but still within the six hours permitted for the race. However, who said I would walk the whole thing.

I continued to crunch the numbers (this time on a spreadsheet instead of in my head) and determined I could reduce the time to under 5:15 if I could reduce the average pace to 12:00. So I could mostly walk, do some running, and still finish not much slower than my only other full Mary, the 2006 Rock-n-Roll San Diego. The time there was 5:01.

But figuring this out in my head and actually doing it are two different things. It had to be put to the test and with the race four weeks away, I decided to do just that on Sunday.

It was a pretty good day for a run. Low 60* range with a breeze to make it feel just a little cooler. I donned my triathlon shorts (they seem to be the best for longer distances) along with a long sleeve technical fleece which might have been a bit warm, but weather in Colorado changes rapidly. It would turn out to be a pretty good choice.

Since my home sits at over 6000 feet, nearly any out and back run involves climbing on the return. The longer the run, the more the climb. If I had been healthy, I would have done just that. However, my soleus muscle complains mostly when I’m going up hill. What’s more the Colorado Marathon is a mostly downhill affair since it starts in the mountains of the Poudre Canyon and finishes on the plains of Fort Collins. Being the supportive person she is, my wife gladly agreed to pick me up just outside of Cherry Creek State Park which would be the finish of my point-to-point trek.

From the mid-point of my drive way, I headed out, at a walk until reaching the Sulfur Gulch trail which is the main bike path through my neighborhood. It’s a slow descent from east to west until it intersects with the Cherry Creek Trail which would take me north toward the park.

The first four miles (save for that opening walk) were done at a moderate pace of a little over 9:30. My leg was complaining a fair amount as I reached mile four even though I felt okay from a cardio standpoint. I decided I would walk for the next two miles. However, I felt better as I reached the 6 mile mark so I decided I would run some more. Things were actually feeling okay until I hit something of a steep decline around 6.5 miles. It’s usually the uphill portion that hurt but this time, my leg felt really sore. I went a little further then stopped to stretch a little at 6.5. I started walking again and felt good enough to run until a little past 7 miles.

As I walked, I focused on trying to stay under a 13:00 pace. It’s not as easy as it sounds. You really do still but a lot of effort into it. In fact, I noticed my glutes becoming sore as I proceeded, but I still felt okay and kept going. At the nine mile mark I started up again for two miles of running. Things hurt but soon the pain became duller and I was aided by a mostly flat course. By now, I had crossed into Arapahoe County and was approaching the point where I would no longer be on the bike path. This was where the run became more exploratory.

I was pleased to still feel like I had plenty left as I reached mile 11. I walked off the path and across Arapahoe road and then on the unpaved side. It was a planned walk, but if it had been a run, I would have stopped and walked this section. The area was uneven and I even stumbled once. Fortunately, the whole rough section was only about a half mile long or so and then I was back on the sidewalk.

With a right turn on to Jordan road, I was on my way to the park. Several times I’ve ridden my bike out to Cherry Creek State Park and back. With a loop around the park, it’s a good way to get a forty miler in, even though the road in the park is particularly rough. Today, it was the same scenery, only slower. My next running section began at 13 miles and I went through the next two at a sub ten pace. My leg was not bothering me so much, but I started to feel winded. Somewhere around 14 and change, the rain started. It was really just a shower, but I knew it was also enough to get me pretty wet. Had it continued, I could see it sapping my energy and threatening my ability to finish. I put the thought out of my head. Shortly after starting my next walk break at 15 miles, the rain stopped and the sun started to come out again--typical Colorado weather.

By now, I was well into the park and was actually on the run section of the Creek Streak triathlon. I had, in fact, stopped to walk this very section during that hot run. Today was much cooler and I was walking through miles 16 and 17 rather than mile 5. I knew I was doing better!

Mile 17 was where I started running again and it started on a fairly flat stretch. However, it’s also here that the path starts a climb on the lake side of the dam that forms Cherry Creek reservoir. I’ve experienced all of this before because it is the outbound portion of the run for the Aqauman event. Coming back, you get to enjoy a nice downhill, but not today. I slowed back to a walk as I hit 17.5. There’s no question I was tired. But I was also concerned about pushing to hard and injuring something else. I continued until 18 when I was past the dam and looking at steady flat to down section that runs on the north (outside) face. I was only planning on going to 18.5, but I felt good enough to keep going to 18.75. It was there that I stopped running. The last section was back up hill again. It was not as steep as I expected, but at this point, even walking it was becoming a chore.

From then on, it was just a question of getting to the 20 mile mark before four hours had passed. I did that with time to spare. Ultimately, I hit about 20.35 before four hours. Again, I did the math in my head. Even if I could not run any more, but managed to walk at a 15:00 pace, that would mean in another hour, I would have covered 24.35 leaving 1.85 left. Doing so would result in an overall time of 5:27:45 which is not bad considering I’ve been running almost not at all.

There was a little more walking to get to the parking lot where my wife was meeting me. When I was done, the total distance covered was 20.75 with a total time of 4:05:56.

Today, I am sore as hell. My legs are aching and I’m moving slowly. But I also think I’ll be feeling better by the end of the week. I have no runs planned for the rest of the week, just riding and swimming.

I think I may just be able to shave a little more time of the run by the time May 5 rolls around. For starters, here’s the elevation profile for my race and below, the profile for the marathon:

No, those are not drawings from the same source, but you will notice the lack of steep hills at the end of the lower drawing. I know this is an accurate rendering because those last four miles are the same course as the Horsetooth Half Marathon which I ran almost a year ago. On that day, my biggest enemies were a steady breeze in my face and legs that were especially sore from climbing huge hills around Horsetooth Reservoir.  I may not be feeling any fresher, but I think I can walk at 15:00 and possible faster.

A stretch goal would be to average 11:27 which would bring me in right at the 5 hour mark. That would be great, but considering that a week ago I was thinking about pulling out altogether. So if that’s the stretch, the more likely would be around 12:00 which would result in a finish time of 5:14:24. And if I can’t pull that off and slow to a slow walk for the last four, I could still finish in under 5:30. Not what I hoped for when I started out, but better than not running at all or cutting the distance down to a mere 13.1

We’re forecast for some fairly severe weather in the next day or two, but by the weekend, spring is supposed to return. That means that this Sunday, I’m going to try and do this all over again. I’m also going to try and increase the distance to 23.

Beyond that, I still think a taper is in order so while I may do some run/walking at longer distances; they’ll be much shorter than this. Most of this will also depend on how quickly my body recovers during the week ahead.

More to come.

Thanks for reading!

Getting Older and Discovering New Injuries

The folk song tells us you don’t know what you got ‘til it’s gone. That could not be truer than when you are injured and have to modify your training schedule. Such is the recent development for me as the result of a lot of time on the run lately.

Last Saturday, I was pleased to have completed a 17 mile run as part of my preparation for the Colorado Marathon on May 5. It was a bitterly cold day. Like 1* with the wind chill cold. As in the tube running out of my Camelbak froze solid cold. You get the picture.

But despite all that, I did it and hit a major point in my training schedule. After a few days off I was ready to go out for a much easier 75 minute training run aimed at staying entirely within Z1. The course I chose seemed like a good one since it included a lot of downhill which is the most distinctive characteristic of my marathon.

Some where around the five mile mark, my left hamstring started complaining. I knew I had not pulled it, but I could tell it was tight and that the risk of an injury was higher. The solution was easy enough. Just shorten my stride, slow the pace and I would be fine. And that worked.

But meanwhile, the muscle behind my right knee was conspiring to cause me other problems. With about a mile and a half remaining, it started hurting more and more to the point that I slowed to a walk for the final four minutes. I wasn’t limping, but it definitely hurt. In fact it really hurt. Unlike some nagging injuries that bother me slightly over time, this one felt more acute.

By the time I went to bed, walking up stairs was difficult and walking down them was excruciating. When I woke the next morning, things were no better. I had to down the stairs leading with just my right foot. Walking was slow and a little awkward. As I continued to get ready, it felt a little better but the pain was still fairly pronounced.

Once I got to work, the first thing I had to do after parking was make my daily ascent up two flights of stairs out of the parking garage. Not fun.

So during a break, I started Googling items like “pain behind knee” and started getting a ton of information. Ultimately, I think I have developed either gastrocnemius tendonitis or, and I think more likely, a strain on the right lateral gastroc muscle. Specifically, said strain is near the popliteal area which is the area behind the knee.

The interwebs had all kinds of treatment suggestions which sounded great but not all that practical (when am I going to find time for ultrasound treatment?).

During the day, I noticed the pain would abate somewhat after I had been moving around. Sit behind the desk for a couple of hours and it would be sore. Walk around for a few minutes and it felt better. Simply put, the muscle was getting stiff when it was not in use.

For years, I dealt with pain in my lower back which was the result of some foolish decisions to lift heavy objects or work for hours shoveling. The best relief for this was to put a heat pad on the affected area. Once it was sufficiently warmed, everything felt better.

Applying this logic to a different muscle (but still a muscle) I wore the pad around my right knee last night. By bed time, I was walking up stairs like a normal person (rather than take a step with my left, then pull my right, repeat). Walking down still hurt, but was not excruciatingly painful.

When I woke the next morning, things were better. I did take two naproxen tablets at bed time which probably did not hurt either, but I do think the heat has relaxed the strained muscle enough to allow it function more normally.

I am neither a doctor nor do I play one on TV. So if the pain does not fully abate after some time off, I will go in and see my physician or an orthopedic specialist. However, I am encouraged and hopeful that what I thought might be a season-altering injury is in fact just a nuisance along the way.

Thanks for reading.

Committed

I am (or maybe should be) committed. I registered for two races this morning. The first is the local Turkey Trot in Parker. Having confirmed that I will be in town for Thanksgiving, I decided to give this one a shot. I’ve lived in Parker for about 13 years but ironically have never done a race in town. This one will be pretty easy just a 5K out and back along the Cherry Creek trail which I know well. It ought to be nice not to have to drive down to Castle Rock or north all the way to Washington Park.

I did register for another, slightly longer race as well. On May 5 of next year, it’s my intention to run the Colorado Marathon. 

Yes, I did say marathon, not half marathon. This will be my second attempt at the distance, the first being the Rock & Roll Marathon in San Diego in 2006. That one was not bad considering it was the first time. I finished at 5:01:07 after struggling mightily during the last 10K. The course was fairly flat, especially in the second half and while the weather was a bit warmer and more humid than I expected, I managed it okay.

There were other factors that slowed me up that year including plantar fasciitis and a nagging case of IT Band Syndrome. I have no regrets about the race. Running 26.2 miles is no mean feat for anyone. But despite coming out of the race thinking I would do another, I never did. Training proved to be too grueling and time consuming and I just lost my passion for it. That didn’t really change until I discovered triathlon.

That brings up the question of what has changed to make me want to do this again. There are multiple answers.

First: Last year I saw my brother have a lot of success in our 70.3 mile triathlon, HITS after having done a full marathon in the early season. That’s not to say he had an easy time of it (he assures me he did not) but while most of us had slowed to a walk, he ran it in. I doubt I’ll be as fast as he was in my next half iron event, but anything that would shave several minutes off my 2:46 time would be good. Imitating the success of others is always a good strategy!

Second: I meant it when I said that I had no regrets about that first race. However, that does not mean that improving upon the time has not been bothering me. Nothing drastic, just the ability to put a 4 at the front of the time would be nice. I have a much better training plan now. I’m also more disciplined in my training. Furthermore, I’ll be about 14 pounds lighter on race day than I was back in 2006. All bode well for a PR.

Third: Last weekend, I caught the highlight show from this year’s Ironman Championship in Kona. Let’s face it; it’s a lot easier to watch people out there suffering than to do it myself. Nevertheless, I felt a desire to be one of them. Not a competitor at Kona (that would be nice but it’s unlikely) but to be able to call myself an Ironman. Most folks who read a triathlon blog understand. For anyone else, if I have to explain, you wouldn’t get it.  Running a marathon as a stand-alone event is hard. Running it after swimming 2.4 miles (over an hour) and riding 112 miles (over six hours) is almost surreal. If I decide I’m going to commit to 140.6, then I need to know I can run the distance. That’s still a very big if, but I am still willing to explore it.

So now what? Cast aside the biking and swimming so I can prepare for a run event? Hardly! If I learned anything from my experiences several years ago it’s that cross-training can help me reach the cardio needs of such a race and help prevent injuries. I’ve been able to work out six days a week because I vary what I do.

This is a big step. Deciding you are going to run 26.2 miles always is. However, I feel like I’m going in the right direction on my path as an endurance athlete. If that path does not lead me to a full Ironman event, so be it. If it does, well, very few people can call themselves an Ironman. I would be honored to be one.

More to come on this one including training progress, deets about the race and how my 43 year old body holds up.

Thanks for reading!