Clark's Pittsburgh Marathon Race Report
Clark's Pittsburgh Marathon Race Report
This was my first stand alone marathon and my race plan can be found here.
The lead up to race day was pretty normal. My long training runs all went well with no injuries or significant issues. I was able to train on the actual course quite a bit so that was confidence inspiring. The only real question mark coming out of training was some disconnect between RPE and heart rate on several of my long runs. In spite of this, I felt prepared, healthy and ready to go.
Race day logistics were EASY. The start was only a mile from my house and my route to the start was not impacted by any of the nearly one million road closures that come with a major city marathon. I was time seeded into the A start corral, which closed at 6:45, so I left the house at 6:20. My wife dropped me off, I did some warm up running and I slipped into the corral at ~6:40. I found a spot in the very back and ran into a coworker, Tim, who was in the very front of the B corral. He and I were both shooting for similar times, so we chatted for a bit until the time was right and then he slipped into A so that we could run together for the first few miles.
Tim ran the Pittsburgh Marathon last year, his first, and he had some early pacing problems, so I think he was happy with my plan to go out relatively slow. We ran together for the first three, or so, miles (8:32, 8:10 and 8:23). We talked some about RPE and the disconnect that I've seen between heart rate and RPE. I know my first three miles were all RPE 1 because we carried on a seamless conversation the entire time. This is not at all consistent with my measured heart rate for those miles and that is a theme that's going to keep coming up in this race report...
At around mile three Tim decided it was time to pick up the pace and we parted ways. I wished him good speed and told him I hoped to see him at the finish.
The next several miles were pretty routine (8:06, 8:40 and 8:09). The weather was generally cooperating, which was unexpected but nice. The slow rain was helping to keep things cool without raising the humidity or really getting my feet wet. Things seemed pretty good so I decided it was time to pick up the pace before I dug my time hole any deeper.
Miles 7, 8 and 9 (7:53, 7:53 and 7:46) all went by without incident. However, the disconnect between RPE and heart rate persisted. Those are typically high Z2 paces for me and are inline with my expected marathon pace. However today they were at a solid Z3 heart rate.
In mile 10 I finally stopped to pee and discovered that "holding it" was not the best strategy because peeing took forever..... I finally ran out of the port-a-john and my watch beeped an 8:45 split for mile 10. Ugh!
In the middle of mile 11 (7:58) I got to see my wife, which is always great! Mile 12 is the one major up hill on the course (8:38). At the end of mile 13 (7:44) the mental math started up and I knew I would need to keep up a strong pace if I was going to slide in under my 3:30 goal!
Miles 14 - 23 all went pretty much as planned (7:44, 7:55, 7:40, 7:34, 7:47, 8:00, 7:41, 7:44 and 8:01) with the slower splits coming from elevation change and not fatigue or loss of effort.
Right at the end of mile 23 I caught up with Tim. He was moving along well but as I passed him, it was clear that he was not going to try and keep up. I was still trying to make up time, so I wasn't slowing down! Mile 24 is the only major downhill on the course (7:17) so my pre-race thought that miles 12 and 24 would cancel out turned out to be on the money.
Mile 25 was flat and slow (8:06). I'm not exactly sure what happened here but I was certainly not expecting to be back above an eight minute pace. I picked up the pace for miles 26 (6:57), but not to the extent that my split indicates. The course runs back into down town here so perhaps the buildings messed with the GPS data.
At this point you would expect that the finish would be in sight, but actually, it's not! The half marathon has a nice straight path to the shared finish line, but the full marathon requires a 90 degree right turn before you can see the finish. Working off of my 26 mile split time, I knew things were going to be close. I was in a full sprint at this point and the only way I was going sub 3:30 was if the finish line was right around the corner.
It wasn't.
I kept up my sprint and crossed the line at 3:30:21, which is a fantastic time for me and is 26 minutes under my best Ironman marathon time. Of course, it's also 21 seconds over my 3:30 Boston Marathon standard time. I have no illusions that a 3:29:59 would actually get me into Boston, but I was really hoping to turn in a qualifying time.
Final details: 3:30:21, 14/202 in M45-49 and 317/3652 Overall
So what do I take away from this and where do I go from here? Although I took this day very seriously, my real goals were more around Ironman and less around Boston or marathons in general. I'm not planning another marathon this season and I'm totally comfortable with that decision. Based on my Ironman training, I figured a 3:30 stand alone marathon was possible and clearly I've proven that. Now that I've actually experienced the pace and the effort, I hope I'll be able to translate that experience into something meaningful for Ironman. I'm not saying I'm going to go run a 3:30 Ironman marathon, cause that's not going to happen. However, I do think I learned some things that will help me improve both training and running for IMAZ this fall, which is my A race this season.
Next up on my schedule is the Laurel Highlands Ultra in June. This is a small, local, trail-race with two distances, 50K and 70.5 miles. I'm doing the 50K again (previous race report) and I'm really looking forward to having FUN. Although they make me wear a number, that day will be about having a good time and running on a trail that I first experienced as a Boy Scout back in the 1970's. The last time I ran this race I was four weeks post IMTX and although it was a tough day, I had a blast! I'm curious to see how my current fitness compares.
0
Comments
Looking at the heart rate track in Strava, it looks exactly like I would expect, except that it's shifted up by ~10 bpm. Again, according to Strava, I spent 2:05:32 in Z4, based on heart rate but only 21 minutes in Z4 based on pace. This the disconnect that I'm struggling with.
On the heart rate, I've had a couple races where it was mysteriously high. The bike at IMAZ 2014 and the run at St George last year. I've never been able to find a root cause. I just go with RPE and hope I don't blow up. The only thing I've noticed is my HR reads high if the strap slide down my chest a few inches, almost exactly 10 beats like you experienced. This generally shifts me up into the next HR zone. I wear the HR strap pretty tight now.
Going back several years here ... but didn't a 3:30 Boston qualifying time used to be anything 3:30:59 and under?
Go Steelers!!!