Monthly Archives: November 2011

race report: marine corps marathon

Well, the race was a month ago. Oops. But I couldn’t skip the write-up!

The Marine Corps Marathon was only 15days after the Baltimore Marathon — my first time doing two marathons so close together! I’m happy with how I felt and ran on race day.

It was a very chilly morning — in the low to mid 30s in the pre-dawn hours. Since we were taking Metro to the start line and had a ways to go, we gave ourselves a lot of travel time. So of course we were in the start line area with two hours to spare.

I was glad I met up with some friends at the train, it would have been lonely passing all that time by myself! Well, at least we got there before there were lines at the port-o-potties. And in fact, I got to break in a pristine facility.  Once we were all set (for the time being), we huddled under a tent to try to stay a little warm as we waited.

Thankfully time seems to pass quickly. I ate my peanut butter sandwich. We made another trip to the port-o-pots. And then it was time to head to the start corrals!

It was my second MCM, and the second time I wound up on the wrong side of the fence while trying to seed myself. Maybe next time I’ll figure it out! We squeezed in as soon as we found a spot in a reasonable pace group. I knew I wasn’t going for last year’s speed, and lined up with my friends. We were different paces and split up within the first mile, but it was nice to start together.

I was trying to do a better job pacing myself than I did in Baltimore — where I tried to be slower in the first half, but was still probably running too hard, which made for a pretty miserable second half. I was barely looking at my pace at all during Marine Corps — I was focusing more on keeping my heart rate low. A new strategy for me, but I wanted to make sure I wasn’t pushing too hard!

I was hoping I’d be able to pick it up in the last 10K rather than fall apart.

And, well, it sort of worked.

Unlike Baltimore, where my walk breaks kept getting longer and more frequent, I kept them quick — just at the water stops —  and I resumed running soon after. I also felt good later in the race. I remember hating mile 17-18 in MCM last year (and in Baltimore it started around 16!), but I was still a happy runner this time around. I did stop briefly to stretch my hip, but got back on the road feeling OK pretty quickly.

This year, though, the bridge seemed a lot more awful than last year. Yeah, I did kind of hate the bridge this time around. But I felt better as we headed into Crystal City.

I willed my legs to move faster, and occasionally I’d glance down at my watch and my current pace *was* faster. But it seems I wasn’t holding it long enough to make a difference in my mile splits. Oh well.

Once again I was thankful for my Strider friends for being out there with gummy bears (and hugs).  Helps that they were around mile 23, so it meant I was almost done!

Those last few miles weren’t too bad, and I even managed to pick it up a little bit for the last two.  My last half mile (yikes! I tracked 26.51) wasn’t the sprint I can usually manage at the end … but I guess I probably was a little tired after a second marathon.

Overall time was 3:14 slower than Baltimore … but I was 5:26 slower than Baltimore at the halfway point.  Still not the negative splits I wished I could do, but at least I didn’t fall apart as badly!

Baltimore MCM
First Half 2:15:57 2:21:23
Second Half 2:28:08 2:25:56
Total 4:44:05 4:47:19

The crowd at the finish was a lot worse than last year. Maybe because I was 25 minutes slower this year? I almost couldn’t hit the second mat due to a wall of people. And then it took forever to weave through the crowd to pick up food and get to the finish area.

I still love this race. I plan to be back in 2012!

Chip Time: 4:47:19
Overall Place: 11770 / 21023
Gender Place: 3916 / 8596
Division Place : 631 / 1309

race report: potomac heritage trail 50K

Yesterday I took on what is probably the most difficult challenge I’ve ever put my body through. There were times when I wanted to quit. There’s no shame — plenty of people cut the mileage short, and this low-key event doesn’t even record DNFs. They record how many miles you completed.

But I’m stubborn. And in the times when quitting was possibly an option, the thought ran through my head that if I didn’t finish the distance, then I would have to try again. And if I kept going, well, this could be my one and only ultramarathon.

I know at least during the first 10 miles as we ran from DC into Virginia, when I was still hanging with a nice woman experienced with this trail, there were people behind us. And while she charged forward when we hit the first rocky portions that slowed me down — trail inexperience plus the extra caution I was using — nobody passed me. Well, except for one woman who got lost and ran four extra miles by the time she passed me.

By the time we got to a short out-and-back portion that checked in at the same aid station around miles 17 and 20, I knew there was nobody else behind me. I saw all the other runners already on their way back.

I was alone. I was dead last. And I didn’t care.

My legs were aching, and I was barely running. The downhills started to hurt my knees, and the uphills just hurt everything. I would attempt to run whenever it was flat — but it was typically short-lived until I got to a stream crossing or rocky trail.

Most of my (limited) trail training was on fairly runnable trails. The only streams I’d crossed were so small you could probably jump over them. I didn’t know that much about this trail, but had seen some pictures of stream crossings and rocky terrain. I knew this was going to be a challenge, but I wasn’t prepared for how difficult this course was going to be!

Midway through probably the biggest climb of the course. I had been running along the river. Oh, and there used to be a handrail, but the boulder it was attached to collapsed in the earthquake.

I do think I got lucky — one picture from last year showed people actually wading in the water. We must have had more rain last year. I was happy there were always enough rocks to cross, and I only got my feet wet a tiny bit.

I did almost fall in a stream around mile 24, but since I caught myself, I find it funny.

Just after that crossing, I hit the last aid station. They cheered for me and offered me a ride if I wanted to call it quits. At the pace I was going, I risked not finishing before it got dark. One volunteer asked if I had a flashlight. I didn’t, just my phone’s flashlight app, assuming the battery didn’t die searching for signal in the woods.

There was no way I was going to get that close and quit. After a quarter of a PB&J sandwich and some peanut M&Ms,  I continued on the course and hoped for the best.

After crossing Chain Bridge,  I was able to run for a bit along the canal, until I got back into the woods and had a few more rocks to climb. The trails in DC are a little easier, though. While I was still walking a lot I attempted running more frequently. Still very slowly. But mentally, I was feeling better. I was in the home stretch.

It was starting to get darker, but there was enough light to see the chalk markings to find my way back. I was glad there were still people walking the trails, it might have been a little scary to be in the woods alone at dusk.

The last mile was in the street, so I didn’t have to worry about darkness anymore.

I made it.

Nine hours and six minutes later, I am an ultramarathoner.

Looking up from the same spot I took the other photo. I was following the green blazes (see rocks on the right).