2011 Baystate Marathon Race Recap

What a day and what a race!

Last Sunday, I completed the 2011 Baystate Marathon in 3 hours and 14 minutes, 87th overall, which well exceeded my goal of coming in under 3 hours and 20 minutes.  With my finish time, the near perfect race-day conditions, and (for the most part) even pacing, this marathon will not be forgotten.

Lauren and I jumped in the car around 6:15 AM, stopped at Starbucks to get a coffee and bagel, and began our hour-long drive to Lowell.   Once we arrived, I left my bag at the bag pick-up station, and meandered up to the starting line.  As I walked up looking for the 3:20 pacer (a race volunteer who runs the marathon at a pace of 3 hours and 20 minutes so less experienced runners can follow as opposed to worrying about their own pace), I saw that the 3:00, 3:10, and 3:15 pacers were at the front of the race pack.   Normally, they are much more spread out amongst the throngs of runners.  The race was noticeably smaller this year because the Boston Marathon changed the date of their deadline to qualify.  This year, the Baystate marathon occurred after the Boston Marathon qualifying deadline.  Needless to say, I found a spot about 10 yards away from runners who would be finishing this race much sooner than me.  No need to be anywhere near them and risk the chance of going out too fast.  After the national anthem and a moment of silence, a gun shot pierced through the air, and we were off!

The first three or so miles went through the busier part of Lowell.  I had plenty of room to run (not often the case during the beginning of a marathon) and there were plenty of people to speak with as I was running.  I chatted with a guy from Baltimore who had run some similar races as me in that area in the past, as well as a couple of other runners who didn't seem very interested in small talk.  Oh well.

The first three miles passed by at 7:27 (7 minutes, 27 seconds per mile), 7:20, and 7:02.  I knew that I needed to slow down or I would hit the wall by mile 12.  We passed our first bridge, and started the first of two 9 mile loops along the river.  The next two miles were the only section of the race where the course is not flat.  This first pass through the hills had no effect on my pace, at 7:20 and 7:15.

View along the course

The halfway point of this loop is a 150 yard bridge that has a separated walking path made of some sort of metal.  As I began to run over the bridge along with 40 or so other people, the walkway had a noticeable bounce to it, almost like you were jumping on a trampoline.  If the runners had a similar cadence running across the bridge, I could easily see a few of them getting some air from the bounce of the bridge.  Needless to say, it was a good laugh, and a good distraction from running for a few minutes.  At this point, I was still on a roll, with my mileage splits at 7:17, 7:10, 7:17, and 7:11.

After my first hour of running, I was still running at a pace that was faster than I planned, but I made the decision to try to hold this pace until mile 13, and then at that point I'd reconsider my strategy.  I had already had one of my four running Gu's (100 calories of carbohydrates in toothpaste form), and I had been alternating drinking gatorade and water at the water stops (which were every two miles on the course).

The next miles coming up to mile 13 came in at 7:12, 7:15, 7:07, and 7:13.  Wow, this was great! I still felt relaxed and the pace was still easy, considering I'd already completed half of the race.  I passed the 13.1 mile line (the official halfway point of the marathon) just over 1 hour and 35 minutes.  Keeping the same pace for the rest of the race, I could qualify for Boston.  Oh, the thoughts of grandeur one has while running a marathon....

The first few miles of the second loop required a little more focus, and were a little more challenging than the first loop because of the increased headwind.  While the cool air felt great, the wind in my face was something I'd rather not have to run through.  Still, I maintained the pace at 7:18, 7:07, and 7:20.

Merrimack River

As I bounced over the bridge again, I did so running with far fewer people than the first time around.  For the past few miles, there was a group of four or five runners that I ran with.  We were not exactly running together, but all of us would slowly pass each other (or be passed) depending upon how we felt at that particular moment.  While it was good to have the goal of keeping with this group, the constant passing and dropping was becoming annoying.  At this point, I needed to focus more on my pace, breathing, and body, and less on these guys trying to race.  And besides, the racing part of the marathon doesn't come until mile 20, and we were only at mile 17.  So, I made a deal with myself that I'd continue my pace for the next two miles and hang around with these guys.  If they were still around at mile 20 and I was still annoyed, then I would do something about it then.  The next miles come through at 7:18, 7:19, 7:18, and 7:16.

So that takes us to mile 20.  This is the infamous part of the marathon that makes or breaks you. The guys I had been running with were no longer to be seen.  They must have hit the "wall."  I still felt relatively comfortable keeping the pace, which is a huge accomplishment in and of itself.   I've always seemed to fall apart at this point in my previous marathons.  Now, I still felt like I had a chance to do something special.  Six miles is the length of my regular run at home, so I rationalized that this is just an easy 50 minute run that I do 2 to 3 times a week, so I should have no problems from here on out.  Marathon runners have also been known to hallucinate during this part of the run....

Perfect running weather

I passed mile 21 at 7:22, and it started to get more difficult.  My legs felt heavy, my heart rate was up much higher, and there was no one around to cheer us runners on.  There were a few runners about 75 yards in front of me, and I didn't hear anyone behind me.  So, I made it a goal to track those two guys down over the next five miles.  At this point, I'm worrying less about my pace, and more on catching up with the guys ahead.  I attempt to psych myself up and make it personal. Mile 22 comes at 7:28.

So far, I hadn't made up too much ground on the two guys in front of me, however, I hadn't lost any ground either.  Knowing that I had about a half hour left of running, I figure it's now or never, and I tried to pick up my pace a little bit more.  Guess what happened?  Here is where I hit the wall.  I ran for about a quarter of a mile at a quicker pace (or at least what I thought was quicker) before my hamstring started to get tight.  I immediately slowed down to avoid cramping up (and ruining any chance of running a good time), and then my body just hit a slump.  All of the energy I thought I had was nowhere to be found.  I sucked down my last running Gu, and walked through the water stop to make sure I drank an entire Gatorade in hopes of giving me one last extended jolt.  Miles 23 and 24 proved to be the hardest part of the race for me, and I completed them in 8:00 and 8:23, respectively.

With two miles to go, I pondered why I put myself through this misery.  Then I think about all of my friends who helped support Easter Seals on my behalf while running this race, and I finally get the jolt that I needed.  I didn't care how much this hurt, I had 2.25 miles left, and I was going to finish it as fast as I can.  I shortened my stride, and focused on how "easy" it is to turn my legs over. I thought of short, quick steps... chop, chop, chop.  My legs felt as heavy as roman cathedral pillars, but I was moving them as quickly as I could.  I passed mile 25 at 8:00 on the dot, and now I had a mile and change to go.

Mile 26 proved to be the most eventful mile of the entire race.  After the first quarter of a mile, both of my hamstrings attempted to shut me down.  I stopped for 5 - 10 seconds to gather myself and to prevent two massive cramps.  As I passed more and more spectators, the cheers and motivation become louder and louder, and I picked it up again.  My last mile consisted of many small races and accomplishments.  I told myself to sprint to the car 100 yards ahead of me, then sprint to the fire hydrant, and so on. I started to hear the announcer on his microphone at the end of the race, and I decided this is where I needed to go for an all-out sprint. 

I finished mile 26 in 8:15.  Everyone in the crowd is cheering, and as I continued to sprint to the finish line, I saw Lauren on the sidewalk cheering me on.  I picked up my pace, and within 10 seconds, boom, my hamstring cramped up, and brought me to a halt.  Damn!  I can see the finish line!  I quickly hopped along for a few steps, then one of the guys who I was running with runs right by me. Hell no.  I forgot about the cramp, sprinted by the guy, and finally finished my race in 3 hours, 14 minutes, and 25 seconds.

Running a marathon hurts during and after

What a race! I grabbed a bunch of waters, someone puts a medal on me, and I found Lauren waiting for me at the end of the runner's shoot.  A few medical volunteers came up to me to ask me if I needed any help (did I look that bad?), and I declined their offer and opted to sit down on a bench near by.  The next 25 minutes hurt almost as much as the last 6 miles, but the pain is the best that I've felt in quite some time.  The best medicine for this pain was the thought that I had raised a tremendous amount of money for Easter Seals, had a great race, and that I got to sit on the couch for the rest of the afternoon!

Thanks again to everyone who donated to Easter Seals on behalf of this race.  I really appreciate the support, and I had a great time sharing my training experiences with you.  And I also have to thank my wife, Lauren, for the continued support and motivation.  There were plenty of nights that I didn't want to run or blog, but she always helped remind me why I was doing this. 


If it's in the cards for you, I hope to see you out here with me lining up for another marathon soon! 

Twas the Night Before Baystate...

After 3+ months of training, the big day is less than a day away. I was able to squeeze in a couple of easy 5k runs yesterday and today just to keep loose and get the jitters out. After some light stretching and a 20 minute walk this evening, I'm as ready as I'm going to be for the race tomorrow.

As humor would have it, things remained interesting up until the last minute. Lauren and I drove up to Lowell this morning to pick up my number and visit the marathon expo. As we were waiting at a stop light near the finish line of the marathon, we noticed that there were a lot of people running on the side of the street.....wearing race numbers. Oh &#$@, I thought. Did I just miss my race? I could have swore it was on the 16th. After a moment of slight panic, we realized it was a 5k or some other race that was taking place. Once we parked and entered the expo, our assumption was confirmed, and I was good to go. Needless to say, today's blog post would have been...interesting...if I had to explain that I missed the race.

I wanted to take a moment again to thank everyone who has followed me these past few months and to everyone who has helped me support Easter Seals. Training for this marathon and raising awareness about this organization has been a great experience, and I'm really looking forward to tomorrow.

Wish me luck!

Pros and Cons

As I begin to re-define what it means to taper for a marathon (three runs in the last 10 days), I still feel like I'm in pretty good shape to have a successful race next weekend.  In general, a successful race would entail not having to walk or stop because of cramps, and running under an 8:00 minute per mile pace.  Looking back on the last two plus months of training, it's easy to see what went well (pros) and not so well (cons) with my training program.

Pros:
1.  Long Runs - Of the 12 weeks of my training program, 6 weeks have included runs longer than 17 miles.  I'm not sure I could say the same for any of the other marathons I've run.  Taking into consideration that one of the long runs was a race, I feel confident and prepared that I will finish the 26 miles next week.

2.  Injury free - No problems with my lower back, hamstrings, calves, Achilles tendons, or feet during the entire training program (knock on wood).  Not having to worry about an injury resurfacing during the race is a plus. However, I'm pretty sure my lack of injuries was also a result of.....

Cons:
1.  Lack of tempo and medium long runs - Tempo runs (fast-paced runs of 5 - 10 miles) and medium long runs (easy paced runs of 10 - 13 miles).  Simply put, tempo runs make you run marathons faster, and medium long runs make running marathons.  And more simply put, I rarely ran either.  For the medium long runs I did complete, they tended to hover around 10 - 11 miles, opposed to 12 - 13 miles.  The one positive is that these runs can take a toll on the body and a training program that incorporates these runs usually do not allow for as much rest following as a long run does.  Running these type of runs back to back, or within a couple of days of each other can easily cause injuries.  Plus, these runs can increase your weekly mileage by 25 - 40%.  High mileage is another big red flag for injuries.

2.  Consistency - As I'm sure almost everyone can relate to, sometimes life gets in the way and can prohibit running 5 or 6 days a week.  This definitely proved to be the case for me in the past three months.  Although I'm not too upset with the average number of miles I was able to run throughout the past three months (approx 35 miles), these miles were usually run within three to four day increments (normally from Friday to Monday).

With all of this in mind, I'm still looking forward to a fun race, and hoping for a great result.  And regardless of what happens, I'm looking forward to sharing my race day experiences with everyone.

Nighttime Running

Squeezed in eight miles tonight after a low mileage week last week.  Now that we live out in the sticks, additional tools and gadgets are necessary for a successful and safe run during the evening hours.  As you can see, I was both successful and safe.  And yes, it's OK to comment.

Running in California

Yesterday, Lauren and I arrived home from a week-long vacation in California.  We spent three days in San Francisco, and the remaining days exploring wine country.  Not only was it a great vacation, but it proved to be conducive to marathon training.  I was able to run on six of the seven days, three of which will never be forgotten.  Lauren and I ran twice in Napa Valley and once in Golden Gate park in San Francisco, and the scenery was nothing short of beautiful for both.

Any attempt to describe these runs would severely short-change both of these places.  Instead, our slideshow from the trip (running and non-running pics) sums up the scenery pretty well.

Last Run before Vacation

Snuck in a quick six-mile run before our trip out to San Francisco tomorrow morning. We will be enjoying some hills, some wine, and some runs during the next seven days!

Nahant 30K race recap

After running a few easy runs during the week, I figured it would be a good idea to put in a good hard effort on Sunday. My first thought was to find a local running club in the area so I can attempt to keep up with more of the seasoned runners.   After a few google searches for local running clubs,  I stumbled upon the Nahant 30K (or 18.5 mile) race, which happened to be this morning.  After getting the go-ahead from Lauren, I spent the rest of Saturday mentally preparing myself for my first long-distance race in five months.

As a quick aside, last night Lauren and I watched the movie 127 Hours. This is about the story of Aaron Ralston, a hiker who in 2003 was trapped in a canyon in Utah for six days when a boulder pinned his arm against the canyon wall. After five days of trying to free his arm, he came to the conclusion that the only way he was going to save his life was to break and amputate his arm to free himself from the canyon. If anyone ever needs any motivation to do anything, then I would highly recommend watching this film. It definitely fulfilled my objective of mentally preparing myself for the race.

On my hour plus ride to Nahant, I had my usual pre-race meal of an English muffin with peanut butter and a big thermos of coffee. It's not exactly a bowl of Wheaties, but my stomach seems to handle it fine during a race. Within 15 minutes of the start of the race, I jogged for a couple of minutes to loosen up my legs.  After drinking a bottle of water, I was ready as I was going to be this morning to run for 2 plus hours.

After a nice word by the race director in remembrance of 9/11, the gun went off, and so was I. There were approximately 300 people in the race, which made it easy to navigate through the first quarter mile of slower runners who like to sprint out of the gates (I've been guilty of this on more than one occasion, and made it a point to hold back for the first few miles).

Since I have not raced this distance is some time, I had no idea at what pace I should be running at. My first two miles clocked in at 7:14 and 7:13 minutes per mile. If only the rest of the race were this easy, I thought to myself. Halfway through the third mile, we came to the end of Nahant Beach, which meant two things: the end of the nice breeze off of the ocean, and the beginning of 12 miles of rolling hills. Needless to say, this was not a nice surprise. However, the next five miles went by with no difficulties, and I was able to keep my pace between 7:09 and 7:29 min/mile.

As the miles past, the cool morning at 9:00 AM had turned into a hot, bright, and sunny day by 10:30, and my legs began to get heavier and heavier. More hills meant more short, choppy steps up the hills, and then long strides leaning forwards on the downhills letting my weight and gravity do most of the work. Any time I lost going up the hills I more than made up on the down hill. Still, my pace was undeterred, keeping under a 7:30 min/mile pace.

Miles 15 through 18 were difficult, but somewhat manageable. The uphills took longer, and the downhills were not nearly as fast as they were at the beginning of the race. The last mile and half of the race was along the beach bike path. While the views of the beach couldn't have been better, I quickly noticed how cruel the ending of the race was. Being able to see the finish line with more than a mile to go made it seem like the race was never going to end. I managed to stick it out, and finished the race in 2:16:16. All in all, I was happy with the race, and I'm looking forward to the remaining six weeks of my training program.