This is the conclusion of a 3 part series where I recap the shenanigans of my weekend at IMCT Connecticut 70.3(ish), formerly and currently known as Quassy. Part 1- The Swim can be found here. Part 2- The Bike can be found here.
---
Allow me, if you will, to paint the daunting picture of the challenge that lied ahead. In mid April, I developed a hamstring injury. At first I thought it was something I could run through. Nope. At second I thought it was something I could take a couple of days off and get better. Nope. At third I thought I could take nearly 2 weeks off and get better. Nope. At fourth I thought I could take an entire month off and get better. This race was going to be the test that decided if the 4th hypothesis would be validated or refuted. To sum up, had only run twice in the past 45 days, for a grand total of 7 miles and my last run was roughly 1 month prior, to the day. To make the picture even worse, I wasn't much of a runner to start with.
In case you were brought here against your will but for some reason decided to stay anyway, allow me to explain. No, there is too much, let me sum up... 70.3 races typically feature a 1.2 mile swim, 56 mile bike, and a 13.1 mile run. IMCT Connecticut 70.3(ish), formerly and currently known as Quassy did not feature a 1.2 mile swim (in their defense, they really wanted to but Mother Nature had better ideas). IMCT Connecticut 70.3(ish), formerly and currently known as Quassy did not feature a 56 mile bike. It was closer to 53.5 miles, which was pretty okay due to the ridiculously challenging hill profile. Well, IMCT Connecticut 70.3(ish), formerly and currently known as Quassy finally did something right in the form of the run distance. Just my luck.
When asked about my race goals, I had a clear picture of what I wanted to accomplish. I wanted to run without hamstring pain. That was it. I had predicted that I was going to be in a significant amount of discomfort on the run due to attempting a half marathon on no training. I was allowing myself to hurt pretty much anywhere with the exception of the back of my left thigh. And I had a strategy in place towards that end.
As I came out of transition, I was surprised as to how well I was actually feeling. I expected to be a bit more stiff due the crash while entering transition. I also feared that I over-biked. My bike plan allotted for about 215 watts (normalized for those who understand what that means). What I achieved was 229 watts. This translates to about 8% harder than I wanted and the 215 number was already at the top edge of what I was supposed to bike and feel good, according to science. As I started to run, I honestly felt like I could run, ya know, relative to myself anyway.
My run strategy was simple. Don't run too fast. (That was a joke and you were supposed to laugh. Running fast is never an option for me.) The concept remains, I needed to control the effort especially early on.
The hill profile was against me. The first mile was a nice, extended downhill. Downhills are good for speed, bad for leg injuries. The problem is that as you stride, your leading foot lands a couple of inches lower than it launched. Not only does this extend your leg a little further than normal, which can exacerbate a tight muscle, the extra vertical distance results in higher impact forces as your foot lands on the asphalt. I made it a point to stay nice and relaxed without attacking that section of the course.
It was obvious that I was the only one on the course with this strategy. As I controlled my descent, I got passed. And passed. And passed. The stream of people who ran by was relentless. I smiled anyway. Because I was running!
Now, before I got ahead of myself, I still had to remember that during one of those failed healing hypotheses, I felt good for about 3.5 miles before the injury popped up. Therefore, I was looking for excuses to slow myself down and not race the run part of the course. At mile 1.3, I stopped to go to the bathroom. At mile 4, I had a conversation with the girl handing out gels so that I could get a flavor that wouldn't make me hurl. At mile 6, I mixed a nice batch of ice and water so I could get something cold to drink. When the water was gone, I dumped the ice down my pants. There's nothing like a numb crotch to keep the pace at bay. And, the main point of this part of the story is just to brag that I was still running!
The course featured a lasso-shape. You ran down the handle and out to the loop. You did the loop twice, including the annoying out and backs designed to regulate the distance and ensure that we did the expected number of miles for at least one of the disciplines for the day, and hit the handle again for the trip to home base. As I started my second loop, there were still swarms of people passing and passing. And there were even more swarms of people entering the course. The passing parade was going to continue. It didn't matter. I was still running!
Right around mile 9, my lack of run training started to rear its ugly head. Fatigue was settling in and building a house to ensure permanency. I was searching for some kind of encouragement. As I crested one of the hills, a small crowd of people started cheering for me by yelling, "Go Kristy, go!" I didn't have the heart to tell them that my name wasn't Kristy because it was the perk I needed. Shortly thereafter, a woman ran by who was clearly struggling too and I felt bad since no one was giving her any attention. I was still running!
At mile 10, the hurt locker was officially opened. It was at this point of the run where the aforementioned yet highly predictable pain made an appearance in my legs. It started with early warning signs in my lower quads. I ran on. By mile 11, I had stepped into the hurt locker completely. Both legs were starting to cramp. Every once in a while, the right one would attempt to seize. I entered negotiations with my legs. I agreed to walk for 30 seconds out of every 2 minutes and the legs agreed to not fall off at the hips. My previous pace was now slow shamed as I made the turn off the loop, onto the handle, and headed for home. This is the time when most runners would get a boost and the end simply feels near. Not this guy. The passing parade was in full force. I was still running(ish)!
To add insult to potential injury, the hill profile was conspiring with my legs to work against me. Remember that 'problem' I was discussing at the beginning of the post about the dangers of running downhill? Yeah, well, running up that hill wasn't much of a picnic. (Aside: Come to think of it, at my pace, I could have busted out a picnic without too much of a dent in speed or dent in the picnic. /End Aside.) To put this in perspective, my pace for mile 9 was 8:40. Mile 10 was 9:39. Mile 11 was 10:40. Mile 12 was 11:26. Mile 13 was 12:22. My average pace fell from 8:45 to 9:30. You could watch the misery unfold just through the numbers.
At the end of the day, my official run time was 2:05.00. This was the 108th fastest in my age group, 634th fastest versus the boys, and 825th fastest overall. All of that swimming, biking, and plodding left me with an official time of 5:05.15 for 370th place in the race, 47th in my age, and 319th in my gender. And, my legs hurt everywhere, except, ironically for my hamstrings. I'll call that a win!
For your effort in making it through the series, I'll reward you with the many race faces of the Banter. Thanks for reading.
Epic. I knew you would emerge victorious from the fire swamp. So. Proud.
ReplyDeleteWoohoohoo, look who knows so much
Delete