On October 17, 2004, I ran my first marathon - the Wichita Marathon. It was a truly awesome experience that I will never forget. My time was just over 3:57, but I wasn't overly concerned (to the good or the bad). After all, I had finished what I thought was never possible - a marathon - and I lived to tell about it. And I had finished it any a time that I was proud of. I was exhausted, but I had been bitten by the marathon bug.
Fast forward now some five-plus years. In April 2010, I would run my first Boston Marathon, a dream of mine since approximately 3 hours and 58 minutes after starting the Wichita marathon in 2004. It was a dream that I thought would never come to fruition. From my first marathon I would have to improve my time by over 47 minutes just to qualify (as a male under 35 years of age, I had to run under 3:10 to qualify even to enter). Never did I think I could improve as a runner that drastically. But at last, on March 15, 2009 in Little Rock, Arkansas, I broke the 3:10 barrier (3:09:44) to finally qualify for Boston. To Boston I would go!
With a goal of this nature comes great nervousness. Sure, I had qualified to run Boston, and I had even improved on my time since March 2009 (I ran the New York City Marathon in 3:00:14). Sure, I had now run 49 previous marathons. But something as historic as "Boston" I had never run. I was as nervous as I was in 2004 before my first Wichita Marathon.
But in Boston I was, and running I would do. The evening prior was a nervous evening. I stressed about what I would eat, how much I could sleep, what to drink and how to nurse the sore hip that had seemingly crippled my running throughout the week. As fate goes, following my Eisenhower Marathon last weekend, I had developed some significant inflammation in my right hip. Throughout the week it had taken my runs to a standstill at times. I could never quite loosen it up, and the pain at times was throbbing. While it had progressively improved throughout the week with a heavy dosage of anti-inflammatories, I could tell that the underlying issue was only being masked. Would the hip give me trouble and ruin my plans for a great Boston?
Speaking of plans, my goal for Boston was a big one. As I mentioned, I nearly broke 3 hours in New York City this past November. But nearly breaking 3 hours and breaking 3 hours is a very different thing. Either you are a sub-3 hour marathon or or you are not, or so I felt. 14 seconds might as well be 14 days. So at Boston I wanted to right that wrong and actually break 3 hours. But my ultimate goal was a bit loftier. I had a glimmer of hope of a 2:55 marathon. At least that was the plan, to try for the 2:55 in the first half of the course that tends to be faster, and try to hold it through the hillier second half. If I should fade in the last half, I would have a cushion for a sub-3 hour finish.
The morning of the race I awoke at 5:30 a.m., in time to shower, prepare and head the 3/4 mile to the bus loading area for the long ride to rural Hopkinton, Massachusetts. The ride was a long one, nearly an hour, but I chatted with some interesting folks from across the county. When we arrived at the small school near town, we crowded into some open fields, and waited. And waited.
The race would begin at 10:00 a.m.. I was set in the second of twenty-six corals. If I may digress for a moment. And I do so with all humility. The Boston Marathon is historic. It is also exclusive. It is reserved for the few lucky percent at the front of each age group. I knew I was in rare company. And that is a big deal. But it is also intimidating. As I have shared before, I still haven't developed the mental confidence to consider myself in such rare company. I top this general intimidation with having to walk past about 25,000 other runners (of the 26,000 in the race) to find my way to my starting area near the front. It is beyond intimidating to take your place at the front of such an historic and exclusive event.
The gun sounded and I was off. Those unfamiliar with this course should know that the first 4 miles are notoriously fast. First, they are progressively downhill (not all downhill, as they are rolling, but eventually lose altitude). Second, they are loud with excitement, so the adrenaline pumps and pushes you faster. I felt both, and went out strong with a 6:20-6:30 pace over those first miles (with the exception of a short pit stop). The pace was well within my goal 2:55 pace but I knew the later miles would take that back. It felt fast, but it felt great, almost effortless, as I cruised down the hills. I maintained solid running form, which is critical on steep downhills, and I did so with no hip pain.
Miles 5-12 flatten a bit on overall elevation change, but continue to roll. I maintained my sub 6:40 miles through mile 9. We would pass through Ashland (were the race originally started before the standard distance or 26.2 miles was establish) and Framingham. Both towns came out in enormous support.
And then mile 10 hit. As I had mentioned, I had struggled with my hip throughout the week. At about mile 10, it was back with a vengeance. Despite popping two Alieve early that morning, and a few Tylenol about 2 hours ago, the pain was throbbing. It became incredibly painful to lift my leg as necessary for a 6:30 pace. I was suffering physically and mentally. Could I even finish with this pain? What should I do? By mile 11 I had popped two more Tylenol (probably shouldn't have done that) and had found a medical tent for some Bengay. While it cost me 30 seconds or so for that stop, I was back on pace, and the pain was beginning to subside.
Mile 12 came quite quickly, and with Mile 12 comes the famous ladies of Wellesly College. The Wellesly College girls are crazy loud, and as tradition requires, will kiss any runner passing by. While this was an interesting proposition, surprisingly few in the sub-3 hour pace group stopped (we all took ourselves way too serious, and barely had a word to say to each other after we passed the first 10 miles or so). It was very encouraging, however. And it made me forget about my hip for a while.
Mile 13 came, and I hit the half-marathon point in 1:27:33, dead on for a 2:55 marathon. My hip was improving, but I knew I would have that to work against, and I knew the second half of the course is notoriously hard. So although on pace for 2:55, my real strategy was to maintain a sub 3 hour marathon, and to give as little time back as I could.
At about this time, something else weird happened. I lost myself. I'm not exactly sure of the cause. I knew I was pushing hard (for those of you familiar with heart rate, I was already well into the red zone, averaging over 90% of my maximum heart rate from about mile 11 on through the end of the race, with later mileage at the 95% in higher range). I know the pain from my hip was causing me to hyper-focus on the race as to forget about that pain. And I know I was a bit in a zone pushing through the mileage. But the end result is that I remember very little about the last half of the course.
At mile 16, the notorious Newton hills begin. These are a series of four fairly rough hills back-to-back-to-back-to-back, the forth of which is called "Heartbreak Hill." While they are steep, they are long and unforgiving. At mile 16, the first began, which summits with a false flat and then right back up to finish the hill. A brief reprieve downhill, and then back up the second hill at mile 17. The course then rolls down to mile 19 (still holding a 6:50 or so pace) and back up, flattening (i.e., rolling) until the last big climb of Heartbreak Hill at mile 21.
I maintained pace (6:50 to 7:00), but my legs were about to give by the end of the last hill. At last, we would have the last 5 miles that again lose 250 feet, but continue to roll. I was still on pace for a sub-3 hour marathon, but I had little time to give back. My pace was slowing, as to prevent cramping, but I continued to push on. Unfortunately, even though the course is progressively down those last miles, the course is rolling and you can never quite get in a good stride.
By mile 24, the course is at its lowest elevation, with rolling hills into the finish. My legs were shot, slowing me to 7:00-7:15 miles at 95%+ heart rate. Each hill proved more difficult. Nonetheless, I maintained a close eye on my watch, calculating at each mile the number of minutes and the pace to maintain to meet my goal. I had little room to spare, but couldn't pick up the pace for fear of leg cramps.
At the 25 mile point, I knew I could make 3 hours, unless a heavy cramp hit. I maintained a conservative pace (7:15) down a few downhills, and pushed up the final hill (up an underpass). I knew I had a half-mile or so to go, but until I turned the final corner onto Boylston Street, I just didn't quite know how close I was.
With 1/3 mile to go, I take a hard left onto Boylston. I can see the finish and I awaken. Seriously, that is the first moment in the past 2 hours that I really vividly recall anything. I see crowds lining the street eight people deep (too many people to find my wife and son cheering me on). I do a final check of my watch and know I can make it. My legs feel fresh, and I push on to the finish. Final time 2:59:22. I made it!
Proudly, I finished 1253 overall, and 886 in my division (Men under 39 years old). Very happy with that result. 50th marathon, first Boston and first time under 3 hours. It was a success.