2019: Marquette Half Marathon

Currently in week #05 of a training cycle towards a Fall marathon, my original plan for this event (like, when I first registered in December 2018) was to run the full distance as a supported long training run. Over the last 2-3 weeks (and even as late as Tuesday of this week), I flirted with the idea of sticking to the full distance at a fairly good pace … assuming the weather angels blessed us all with a day made for racing. As much as I believe in pushing the limits, I believe that I am a stronger believer in the process and its transformational power. Coupled with the advice Stephen Eles offered halfway through week #04, I decided to run just half the distance but almost entirely in an unwieldy zone. Doing so would have the added benefit of having plenty more time to cheer on John Farquhar as he punches his ticket to 2020 Boston and Bill Sved completes his 300th (yes, three hundred) marathon!

A recap of the 2018 edition

According to the training plan, this was supposed to be a regular 12 miles LSD run at the end of week #13 towards Chicago Marathon. But I decided to race a half marathon to get used to the real race atmosphere one more time about 5 weeks before the main event. The goal was to earn a PR (1:43:02 or below). I stayed at the Gracis (Kara, Sam and Walker) along with the Farquhars (Cheryl and John). After dinner at the house, John and I walked up the Third Street segment of the course – to measure the distance and in turn, have a better idea of what it takes for a final push.

I started slow averaging ~8 min/mile for the first 5 miles while accounting for rolling course. I cautiously pushed the pace for the next 5 miles once the course was all downhill while accounting for potential slippery surface and possible quadraceps pain. At about the 10 mile mark, a PR was well within range. But I gave into into the humid and muggy conditions on top of carrying thoughts about something that happened at an aid station shortly after mile 10. The latter most certainly didn’t help my cause … I was shy of the PR by about 4 minutes (57/534 overall, 38/198 in gender and 14/62 in AG).

Shortly after crossing the finish line, it was really cool to see Kara come through punching her ticket to 2019 Boston Marathon with nearly 7.5 minutes to spare! Jan and John won their respective age groups and Angela had a pretty good race too!! It was also disheartening to hear the story of an elderly gentleman that missed out on qualifying for Boston by just one minute. I felt pretty good about the impact of training so far in spite of missing a PR. I realized the need to continue working on letting things go as well as on improving and sustaining cadence over longer durations.

The Fall marathon training plan I am following called for a 17-mile LSD run on this day. Since I’d be racing today’s event, I split the distance into three parts: a 1-2 miles of warm-up, 13-mile race and 2-3 miles of warm-down. Also, I re-arranged the Friday’s 10 easy 10 miles into two parts: a 3-mile easy shakeout on Friday and a 7-mile easy recovery run on Sunday morning. As usual, the 3-mile shakeout run was completed by 9:30 am and having packed the car by mid Friday afternoon, I had ended the day’s proceedings around 10 pm. A full night of sleep meant waking up early and taking to the road by 5 am seemed quite relaxing. An easy 2-ish hour drive, similar to 2019 Paavo Nurmi Half Marathon, got me to Marquette with sufficient time to catch the shuttle to the start. After picking up my race packet at the Michigan Iron Industry Museum and chatting briefly with Angela, Claudio and Lynn, I completed the warm-up routine (similar to what Craig had shown me during 2019 Canal Run Half Marathon) few minutes before the national anthem and start of the race.

13.11 mi, 1:32:22, 7:03 min/mile (4:22 min/km), 8.51 mph (13.69 kmph)
Garmin Forerunner 935 and Tempe Sensor, Stryd Power Meter, and WP GPX Maps Plugin

The main goal for this event was to learn more about pacing: unlike the 2019 Canal Run and 2019 Paavo Nurmi half marathons (where I had held back in the first half and pushed the effort in the second half), the plan was to gradually push to achieve a comfortably uncomfortable pace by mile #5 and sustain/improve  it through the finish. And as a by-product of following this pacing strategy, I expected to earn a new PR for the half marathon distance (i.e., finish below 1:38:06).

Apriori knowledge of the course (especially the starting area that takes the shape of a funnel) meant that I started near the very front. Unlike the previous two half marathons, I didn’t peel back after the start … mostly because of the narrow trail and additionally because I didn’t want someone to clip my heels in that hurry. Flatter terrain (and some rolling stuff over miles #4 and #5) meant I could average 7:10 min/mile (about 10 seconds/mile faster than what Ray had prescribed) by the end of mile #5. Not making time to study/revise the course and in turn, not knowing where the course transitioned from gravel to pavement (or incorrectly assuming that it did so around mile 4.50) proved a little costly. I spent a little too much mental energy contemplating when to start the next push. Since the course remained about the same at the beginning of mile #6, I decided to risk and started pushing the pace to the neighborhood of 6:45 min/mile – something that I hadn’t tested or experienced before.

Thanks to Sir Isaac Newton’s ever-present gravity, holding that pace through mile #10 mile … something supposed to be uncomfortable … seemed rather easy and conversational. It felt quite surreal to be breezing past the mile markers … and that such a day was here lot sooner than I had expected. Breathing remained under control and cadence was in the vicinity of 175 spm throughout the run. I purposefully held back a little over the relatively flat miles of #11 and #12 … to save some for the final push up the Third Street hill to the finish line.

Goal: 13.11 miles in 1:38:05
Distance in miles, lap time in m:ss (cumulative time in h:mm:ss), average heart rate in bpm, average cadence in spm, elevation gain/loss in feet, average pace in min/mile and average temperature in fahrenheit.
Lap Cumulative
# Time Avg.
Distance Time Avg.
Finish Time
Goal Time
01 7:08 135 175 16 56 69.6 1.00 0:07:08 7:07 016 056 1:33:18 0:04:47
02 7:02 172 177 00 07 64.1 2.00 0:14:10 7:05 016 063 1:32:51 0:05:14
03 7:09 174 175 07 00 63.4 3.00 0:21:19 7:06 023 063 1:33:04 0:05:01
04 7:22 171 174 43 69 64.1 4.00 0:28:41 7:10 066 132 1:33:57 0:04:08
05 7:09 170 175 03 49 66.6 5.00 0:35:50 7:09 069 181 1:33:44 0:04:21
06 6:49 168 177 00 135 66.2 6.00 0:42:39 7:06 069 316 1:33:04 0:05:01
07 6:46 168 177 00 131 66.8 7.00 0:49:25 7:03 069 447 1:32:25 0:05:40
08 6:43 167 178 00 131 66.6 8.00 0:56:08 7:00 069 578 1:31:46 0:06:19
09 6:42 170 178 00 102 69.0 9.00 1:02:50 6:58 069 680 1:31:19 0:06:46
10 6:52 170 178 00 102 72.7 10.00 1:09:42 6:58 069 782 1:31:19 0:06:46
11 7:04 172 176 07 13 71.9 11.00 1:16:46 6:58 076 795 1:31:19 0:06:46
12 7:16 172 175 00 07 71.7 12.00 1:24:02 7:00 076 802 1:31:46 0:06:19
13 7:29 175 175 85 00 73.3 13.00 1:31:31 7:02 161 802 1:32:12 0:05:53
14 0:52 177 175 10 00 75.2 13.12 1:32:23 7:02 171 802 1:32:12 0:05:53
The final cumulative time, 1:32:23, may not match the actual time owing to rounding errors. The overall distance, 13.12 miles, may not match the designated event distance owing to idiosyncrasies associated with GPS data collection and in some rare cases, incorrectly measured courses. As a result, the cumulative pace and the projected finish time might not match the recorded values as well. The Garmin Tempe sensor doesn't work at times and as such, the recorded temperature could be that of my body ... shifted by prevailing ambient temperature.

I was quite happy to have executed the overall plan nearly as prescribed and completed the run at 1:32:22. It was good enough for 27/527 overall, 19/188 in gender and 6/52 in AG, and a shiny new PR. Similar to 2019 Paavo Nurmi Half Marathon, it helped to have a pro-active plan ready to counter any fear or pain that’d potentially derail my plans. I was satisfied with sustaining fairly even splits throughout the course (fastest mile at 6:42 and slowest mile at 7:29) and approximately even 5k chunks (22:07, 22:00, 20:53 and 22:07).

Furthermore, unlike last year, I did let go aid-station misgivings (e.g., plastic cups that were either difficult to squeeze or just would crack when squeezed losing all water, etc.) and enjoyed the benefits of lighter miles. Post-run activities included re-hydrating, running back down to the bottom of Third Street to accompany John as he finished a  marathon strong in spite of a nagging injury/pain for nearly 10 miles, congratulating Bill on completing his 300th marathon, grabbing one half burrito to re-fuel, getting a quick courtesy massage, meeting newly acquainted friends and making new ones. After joyfully spending rest of the afternoon and evening, I decided to drive back to Houghton … but not before meeting Tim, Jeremy, Carol and Andy … in Ishpeming to train for the upcoming Marji Gesick festivities.

Progress report
# Year Weight
kCal Position
01 2014 180.0 2:05:30 9:32 162 160 0.00 1471 ###/XXX, 86/YYY, 20/ZZZ
02 2016 171.9 1:58:05 8:56 171 161 0.00 1515 128/XXX, 71/YYY, 21/ZZZ
03 2018 166.9 1:46:49 8:06 171 162 0.00 1548 57/534, 38/198, 14/62
04 2019 157.1 1:32:22 7:02 168 176 272.00 1253 27/527, 19/188, 6/52

Thanks be to

the rejections and opportunities life has brought my way, event folks (organizers, sponsors, volunteers, timers, law enforcement officials, photographers, fellow participants and spectators), and the family of good friends in and outside of my community for all the unexpected, undeserved and unrewarded acts of constant encouragement as well as offerings of constructive criticism to improve myself as an athlete and a person. I am eternally grateful to all those who let me train with them, who shared their invaluable tips with me, who helped keep my mind, body and soul in good health, who helped me stay the course during the training cycle, who continued to teach me the value of work-life balance, and who cheered me on from home or along the course.

One Reply to “2019: Marquette Half Marathon”

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.