Race Report: Jack & Jill Marathon 2017
On July 30, 2017 I ran the Jack & Jill Marathon, finishing in 5th place overall with a time of 2:51:07. The guys I ran, Wes & Jonathan Coopersmith, finished in 3rd & 4th place respectively, with times of 2:47:23 and 2:49:02. Here is the race report.
This is a race I should be happy with. I didn’t plan on racing this year and only did so to train with my friend Coop so we could get a Boston Marathon Qualifying time for next year. After the time stress of my 2016 season, I had a conversation with my wife and we decided that I should cut my training to three runs per week, 1-2 of which I’d take kids in the running stroller. I averaged just 27 miles (just barely longer than a marathon) each week. Running a 2:51:07 off of that training plan is more than I had expected going into the season when I had hoped I’d be able to get across at 3:02 or 3:03, barely a BQ.
That said, I am pretty bummed at how I crashed at the finish. My training ended up going really well and I took the first half of the race very conservatively. I expected I should have been able to finish strong. I’ve crashed during a marathon before, but at least with NYC last year, where my crash was even more spectacular, I have very clear evidence that I just went out too hard. Here it seems like I did everything right and still, the wheels came off one mile to the finish. That is what hurts the most. As I think about future races, I’m less confident in my training and race strategy now.
- Finish – ACCOMPLISHED
- Get a Boston Marathon Qualifier: 3:05 – ACCOMPLISHED
- Whole group qualifies for Boston – ACCOMPLISHED
- Sub 3:00 – ACCOMPLISHED
- Qualify for the New York City Marathon: 2:53 – ACCOMPLISHED
- Top 5 overall – ACCOMPLISHED
- Average heart rate over 166.15 (my best for a marathon) – Not Accomplished
- Beat my personal record: 2:42:25 – Not Accomplished
- Sub 2:40 – Not Accomplished
- Win – Not Accomplished
Controlled first half (At least 4 of the following) – ACCOMPLISHED
- Between 1:23-1:25 – YES (Technically 4 seconds over – but I’m counting it)
- No miles >165 heart rate – YES (Highest mile in the first half was 159)
- No going into the 170s at all – YES (Highest moment was 165)
- No miles faster than 6:15 – YES (One mile said 6:13 via GPS but was slower by course marker)
- Consume 450 calories – Was probably closer to 380
- Consume 1 liters of fluids – Was probably closer to half a liter
Courageous second half (At least 6 of the following) – Not Accomplished
(Did many of these for the first ~10-12 miles, but failed in the last two)
- Negative split – faster second half – was 59 seconds slower
- No miles <165 heart rate – the last two were 155 & 149
- No going under 160 at all – low of 147
- No miles slower than 6:30 – last full mile was 7:45 and last partial was at 8:30 pace
- No miles lower than 180 average cadence – was at 166 by the end
- Last mile is the fastest of the day – mile 22 was the fastest
- Have my highest 5-mile-heart-rate-average hits after mile 18 – YES – mile 21-25 were my highest heart rate
- At least 3 of the last 5 miles are 168+ – YES – miles 22, 23 & 24 were all 168+
What am I proud of from race day?
- Demonstrated I can run sub-3 on 3 days a week training
- Our whole group achieved our goal of getting BQs
- Kept as a pack for 20 miles (learning from last year)
- Executed my first half strategy really well (learning from last year)
- Transitioned & began putting in the effort to hit my second half strategy
- When the floor fell out, pushed enough to grab the NYC qualifier
- Tried a new pre-cooling strategy that seemed to work
- Really restful pre-race week and morning (learning from last year)
- No flashlight failure (learning from last year)
What areas could I improve for future races?
- Weak final 2 miles
- Messed up my 1/2 way frozen-towel grab
- Used a pair of flats with a hole in the drain-mesh that let rocks in
- Didn’t have a frozen water bottle at the half-drop
What that was out of my control am I thankful for?
- A cool morning
- Two friends to run with
- A healthy training season
What that was out of my control do I wish had happened differently?
- Rocks in my shoes – didn’t have this issue last year
- The guy right behind us for miles 2-10 with the watch that beeped every 20 seconds
Like always, I hardly slept the night before the race. I just get too nervous.
The morning however was very restful as we had it coordinated like a space shuttle launch. Instead of meeting the busses at 3:30 AM, which would have meant leaving the house before 3:00 our group took one vehicle right to the start at 4:30 AM. We had our wives meet us at the finish line with another vehicle. We got an extra hour of sleep because of that and didn’t have to sit around at the start line for a really long time.
Due to having run this race last year I had a bit of insider knowledge. We ended up pulling an advanced move and dropping off a bag at the half with a few emergency supplies, extra water & nutrition before we went to the start.
I tried a new pre-cooling strategy for this race. I was doing some reading that one of the main inhibitors in longer races is heat accumulation and that the colder it is, the faster runners tend to go. Interestingly, there doesn’t seem to be a point at which it is too cold. This is very different from other races like the 5k where you want to be warmed up and ready for your top gear the second the gun goes off or the 100 meter sprint where you need to be warm so that you don’t pull a muscle.
Because of that I tried some pre-cooling – a technique I had read about runners using in races where the temps were in the 70s or 80s, even though it was 50* on my race morning. I drank a slushie of some juice, I wrapped myself in a damp towel that had been the freezer and I held a couple of ice packs against my wrists, where a lot of blood flows. I was freezing. I also skipped warming up, opting for just some light stretching cold. I would use the first miles of the race as my warm up and save the calories for that rather than spending them before the race.
Gun went off and our group, Jonathan, Wes and I went out in the front. Two runners ended up going a bit ahead of us by the 1 mile, but we figured we’d see them again – turns out we didn’t, they finished 1st & 2nd and our group got 3rd-5th.
Our goal was to split the half at 1:25 – exactly 6:30 mile pace. We wanted to do that by running the first few a bit closer to 7:00 pace, then holding just under 6:30s for the rest, maybe dropping a few seconds off mile 12 & 13 to get ready for a faster second half.
The first miles felt so easy it was actually hard to go that slow. I’d only ever raced two marathons, one where I was having equipment trouble over the first miles and one where I went out way too fast. So this was a new feeling for me – being in peak race performance, going race pace, and feeling like it was a walk.
As we came out of the tunnel they snapped this shot of me doing the banana phone. Yes, I ran the first few miles with a banana and then ate it while running. Yes, I was feeling that good at mile 3 that I was making jokes to the photographer.
Miles 3-12 were really uneventful. We just held our pace, drank some water, took down some nutrition and made sure we were all feeling well. I ate the banana and I believe 3 gels. Once in a while someone would stop at an aid station to fill up their water bottle, get about 10 seconds behind us and then close that gap over the next quarter mile.
Looking at my watch, my heart rate was around 155. In my best marathon my average was 166 for the whole race. So at this point I felt great and knew I was sticking to my conservative strategy.
We crossed the half in 1:25:04 – just four seconds behind our target. Basically we were running like clockwork and barely breaking a sweat. My hair only looks wet in the picture below because I was dumping ice water on it as part of that cooling strategy.
So we started to pick up the pace a bit.
You’ll recall that before the race we dropped off a bag at the half way point – actually it was a bit beyond the half way point where there was road access to the trail. As we approached it we agreed on a 30 second stop. Jonathan was going to change shoes into his backup pair. I was going to get my frozen towel. Wes was going to grab a water bottle. We were all going to pee.
We executed well and after that stop we got back moving again, now beginning to pick up the pace. After averaging 6:30 for the first half, our next splits were 6:16, 6:15 and 6:12.
Somewhere in this stretch Jonathan got a cramp in his calf that he thought was related to changing his shoe. He started to worry it was going to get worse and that he wouldn’t finish. He was debating dropping out and trying to find another race a few weeks later to get his BQ, rather than running all-out, missing the qualifying time and being too injured to run another race.
We talked it out and did some math. 16.2 miles in, we had been running for 1:45. With a BQ time of 3:05 that meant he could run 8:00 pace for the next 10 miles and still get it. Pretty reassuring, especially since we had just logged a few low 6s. I dug out a few salt pills from my water bottle’s pocket, handed those to him and convinced him to give it a few more miles. Our cheering squad was going to be at mile 21, so if he still felt bad then, he could drop out, but if he could hang at 6:30 until then, he would be able to hit 9:00 pace to the finish and still qualify. We backed off of the pace a bit and he was able to hang on. I think I had my 5th gel around this point but am not positive.
Around mile 20 is when our pack split apart. I was really excited we were able to run this much of the race together after running the previous year’s race completely alone. We stopped to fill up our bottles, one of the longer stops and got split apart a bit. When we started running again Wes was maybe 15 seconds ahead of Jonathan and me. I picked up the pace a little, like we’d done the rest of the race to catch back up to each other, but he wasn’t coming closer, so I dropped back and ran with Jonathan for a bit. Turns out he wasn’t coming back because he had just clocked a 6:02 mile. Apparently as we got close to mile 20, Wes just clicked into the zone and was heading to the finish like a heat seeking missile.
As we crossed mile 21 I decided to give it another go, I had hoped to catch Wes and that maybe we could work together to get the #2 or #1 runners. We weren’t sure how far ahead they were but knew that anything could happen at the end of a marathon. Jonatan was doing well, mostly recovered from the cramp, but clearly didn’t have a big push in him, so after making sure he was ok to hit at least those 8:00 splits I started pulling away.
My wife and kids, along with Wes’ wife were cheering on the 21st mile. That ended up being one of the fastest of the day.
My wife grabbed a shot as I passed by them, at this point I was about 20 seconds behind Wes and 20 ahead of Jonathan. I look pretty happy & casual for a guy 20 miles in, logging low 6s.
My next splits were 6:06, 6:04 & 6:10. 23 miles in I’m looking at 2:27 on the watch which means I can hit 2:45 or 2:46 if I keep this pace going. That would have been amazing – only 3-4 minutes slower than my PR from the year prior when I had double the training.
My heart rate was no longer 157 though, I was up near 175, which is dangerous for me. 185 is about my max and I’ve found once I start going past 170 I tend to cramp or shut down within a mile or two. I was supposed to have a 6th gel around here, but skipped it because I wasn’t sure I could keep it down and I thought I was close enough to the finish. That was probably a bad move. My body can’t process the gel fast enough to use the energy consumed at that point for the race, but sometimes just putting them in tells your body it is ok to use the last bits of energy it has, because it knows there is something else coming.
This was the tricky part about this race strategy, and using heart rate to gauge it. My heart rate was so low for the first half, that if I were going to try and get my average up to 166, what I had raced last time, I was going to need to be in the high 170s. But racing in the high 170s was begging for a crash.
I felt the hurt happening. I noticed as I started worrying less about how far Wes was in front of me and more about how for Jonathan was behind me. I caught myself looking back for the first time, which isn’t a good sign. My next miles were a bit more relaxed, 6:30 and 6:45 with my heart rate at 168 and 166. This was probably healthy, but at this point the results were written. I was starting to crash.
Jonathan had closed the ~30 second gap I had put on him during those two miles and caught me at mile 25. I had hoped to run it in together but he was actually running really strong, all that cramping business was behind him. Meanwhile I was getting worse with each step.
This is where I start doing math in my head. I have 1.2 miles left to go I’m looking at about 2:42 on the clock. That means I can basically walk and I will still get my BQ. I know I can’t catch Wes or Jonathan at this point, set a new record for myself. There is no one else behind me as far as I can see. The only other milestone of note is the NYC qualifier at 2:53, which requires me to go about 9 minute pace – that is what I locked on.
In retrospect, I was actually really close to hitting my second half goals. Had I thought about that a bit more and locked in on that target, perhaps I could have stayed around 7 flat and shaved that minute off my time to keep me in the 2:40s. I would have needed to keep my heart rate at 165, which is a pretty solid effort level, but not impossible. Unfortunately I wasn’t thinking about that, a clear planning failure, that is why it is always good to have some fallback goals, so that even if you miss your top goals, you still have something to push towards.
Mile 26 was a 7:45 and the final .2 miles was around 8:30 pace. I crossed the line at 2:51:07. That means my second half was 59 seconds slower than the first half of the race. At mile 24 I was actually 2:45 ahead of first half pace, meaning I had gained 15 seconds per mile, but I was able to blow all of that and a minute more in a horrible last 2.2 miles.
Despite that, it was a great finish. Our crew went 3, 4 & 5 and took home some age group medals. After the race we picked up our car from the start and had a picnic at a nearby park. That ended up tying the whole season together nicely – what had started as a team plan, ended up as team training, a team race and a team meal. Very much different and more enjoyable than my solo experience in 2016, even if I was 9 minutes slower.
Most races give our participant medals to every finisher – it is always nice when you walk away with an age group medal as well. Funny enough those always tend to be the smaller ones. That middle award is my favorite though. Half of my training runs had the stroller in tow and my boys’ favorite thing to yell was ‘go faster daddy’. I’m so happy they could see me in the race and be a part of that.
It wouldn’t be a Greg post without a few charts. Here are a few of the interesting bits from this race.
First, here is the breakdown of all finishers by 15 minute increments – I was in the red bar – not the top one this time.
If we filter to just young males, 34 and under specifically, the results are a little less pronounced. Part of the reason the red bar is so high is our group of 3 who showed up together to turn in that time. The BQ time for these age groups in 3:05 – about 12 of the 45 finisher got it, which is really high. Its a fast course thanks to the continual slight elevation drop.
Looking at pace (blue line) and heart rate (red line), you can see 20 miles of a very consistent race pace with a continual heart rate drift. Basically it gets harder to run the same pace as the race goes on. That all starts to come apart around mile 23, but I managed to hang onto the pace until closer to 25.
Drilling into just the heart rate, you can see I hit peak exertion during the 23rd mile.
My cadence, how many steps I took per minute, was low early on as we started off at such a slow pace. It got up to speed around mile 3 though and stayed relatively consistent until mile 22, minus a stop during mile 13 to pee and a longer water bottle fill up around mile 19. In the end my cadence was dropping, despite my focusing hard on keeping it up, my legs just turned into bricks.
Here you can see a scatter plot of my heart rate and pace for each mile of the race. Generally these follow a trend where the faster you are going the higher your heart rate is. Usually due to exhaustion, the latter miles are a bit slower, even at the same heart rate.
Evidence of my crashing not being a complete lack of effort is clear in those two dots to the far right. Those are my last mile and 0.2 miles respectively. You can see that a 155 heart rate had gotten me around 6:20-6:40 earlier in the race, but by the last mile all it got me was a 7:45. That is bonking right there.
Another thing that stands out to me is that 166 bpm, the rate I averaged last year, would have gotten me about 6:15-6:20 per mile, according to a best fit line. That comes out to a 2:46 finish. I probably didn’t have the stamina to hit quite that level of exertion for that long, but a 2:47-2:49 definitely should have been possible.
Here is a look at my breakdown at mile 25 compared to another runner. The red line is the distance between Coop and I at any given point. You can see we ran together the whole time an the deviance is usually GPS error. Around mile 20 I started to pull ahead and managed to get about 30 seconds ahead. Then around mile 22 or 23 he started to reel me back in. He made the pass at mile 25 and then immediately stopped to get some water, allowing me to pull a few feet ahead. I tried to go with him at that point, but I was just dead. That last spike from 25-26 looks much steeper than from 23-25. That is the difference between shutting down but fighting to get any speed possible and shutting down while giving up. I still ran into the finish, but there is a big difference in speed between digging deep and just running – especially at the end of a marathon.
Here is my time compared to the winner of the race. We exited the tunnel around the same time and he slowly gained distance until mile 20 when I started going their exact pace for about 4 miles – I might even have gained some ground. I would have loved it if he had been there last year, his finish time was 2:39:18, which is about 3 minutes faster than I ran last year. Having him there the whole time would have given me someone to pace with though, so perhaps I would have been able to break 2:40 had he been there.
This next chart is my heart rate per mile in all of my marathon races. You can see the red line which is last year’s Jack and Jill, the race I won, is fairly consistent, with a slight drop in the latter miles but a strong finish. New York in blue started off higher in the first few miles, remained high and then crashed huge.
This year’s Jack and Jill race, in orange is really interesting. Is is incredibly low for the entire first half, then quickly becomes the highest output I’ve ever had in the latter miles, until the crash. Had I been able to keep that orange line above the red line at the end, I’d be happy with my strategy and probably my time as well.
We can see that in comparison to NYC 2016, this crash was about the same trajectory, but because it happened later, it didn’t end up getting as bad. In an ideal race, that crash starts happening at mile 26, but the excitement of the finish lets you push through it for just a bit and then you never see the drop on the chart. I think that is what happened for me in the red line, I was going to crash but decided to finish hard and did so just in time.
In retrospect it appears like I just pushed too hard from miles 21-23 and that cost me the energy for the last mile. Had I gone 6:20 instead of 6:10, maybe I would have been able to go 6:20-6:40 instead of 8:30 at the end. What is so difficult about that idea is mile 21 seems like the right place to start pushing if you’re feeling really good and your heart rate is way below target. By this point you only have 5 miles left to make a dent in your time that you’ve been logging for 21.
What I always try to identify after a race is whether the result was because of a training error, a race strategy error, and execution error or just a bad day. With the marathon it is so hard to tell because you can only race a few times per year.
With the 5k in college I used to sometimes get really down after a slow race and think my training was off, only to have a great race the next week with the same race strategy and realize I just had a bad day the previous week.
With this marathon, I’m really not sure what it is. It could be a training failure. I know I cut my training by a ton. I only ran 3 days per week, logged half the mileage and only had 3 20 mile+ runs leading up to the race, as opposed to 7 the year prior. But my expectations weren’t to get another low 2:40s, I would have been happy with a negative split and 2:49 finish and ecstatic to finish with Wes around 2:47.
I can’t blame the race strategy that much either, because three of us ran that strategy and the other two ended up doing great.
I think it comes down to a bit of execution failure. I missed my half way cool down towel because it was too frozen, I didn’t eat as much as I had wanted to, especially near the end, and I pushed a bit harder than I would have liked to during miles 22 & 23. Combine that with what was possibly just not a great day and I think that is difference between a crash that cost me 2-3 minutes and an otherwise strong finish in the high 2:40s.
One final interesting point. This race actually ran twice over the weekend, once on Saturday and once on Sunday. Had we been there Saturday and ran the same times, we would have ended up 1, 2 & 5 instead of 3, 4 & 5. Having those other runners closer to us might have been enough to change things a bit though – perhaps they would have gone faster if there were competition, or perhaps we would have gone faster knowing we could pull 1, 2 & 3. Either way, it is interesting how races often come down to a bit of luck and who shows up on a given day.
What is Next?
I qualified for the Boston Marathon with this race, so I intend to go out and run that in the spring. That course is a bit slower, but there will also be a lot more runners around my pace for me to group up with.
I’d like to try the same training plan, except focus a bit more on finishing stronger. I’ll likely emphasize more long runs where the last few miles are at race pace to get me into the mentality of digging deep when it seems like I have nothing left.
I’ll also try a similar race strategy, with a conservative start and courageous finish. Probably aiming for the same paces, hoping to hit 1:25 and sub-1:25 for the two halves. On Boston’s course a 1:25 first half will seem a little less conservative and so I won’t try to run any 6:00-6:10s in the second half, I’ll probably aim for 6:25s or so with a strong finish to just barely hit a negative split.
Prediction: 2:49:10. We’ll see…