Looking back
On the Wintery side of things: Though not my first time following a well-written plan, preparing for Whitefish Point Marathon was my first time formally training through our snowy-icy conditions and learning to use cross-country skiing (and indoor biking; and even treadmill running) in lieu of or to complement scheduled runs. It was also the first time where hilly routes substituted for much of speed, tempo and race pace runs.
On the brighter side of things: What started out as another fad diet (or nutritional experiment) had become a lifestyle. I ate 1-2 quality meals home-cooked on most days, reduced sugary things and drastically cut out alcohol. The last item, a liquid form of tasty yet mostly empty sugar calories, was the sacrificial goat. I was getting sufficient rest – sleeping at least 7 good hours on most nights. As a result of consistent running through the said winter months, form (combination of breathing, heart rate, body posture and cadence) had improved significantly and I had moved away from being a heal striker.
After letting sufficient time (i.e., 48-72 hours) flow and take in its current any temporary and irrational feelings I might have had during or shortly after completing the aforementioned marathons, a numerical analysis (of heart rate and power) had indicated that I likely hadn’t given it all on the course. A brief-ish recovery time, though doubling up as a sign of improved fitness/endurance, was an added bit of evidence to this claim. I thought, deep in my mind, there likely was a struggle: between consciously wanting a finish time in the neighborhood of 3:20-ish and sub-consciously being comfortable and avoiding the pain cave. A combination of the following, I believed, was likely the fuel for the latter.
- Treating the PR earned halfway through or the ability to hold threshold pace for over 2 hours as success.
- The fear of bodily injury or worse, of success.
- Lack of sufficient mental fortitude.
Looking ahead
Compared to a year ago, I was in a much better place – in more ways than one. As of early June 2019, the cumulative mileage (running, skiing and biking) in 2019 calendar year was a mere 10 km shy of 1000 miles. Taking strength and flexibility activities into account, I had invested upwards of 215 hours. My body had shown signs of handling 50+ miles and my mind didn’t mind the week after week of high mileage. So, I had a lot of things going for me and there certainly wasn’t a need to re-invent the entire wheel. An additional goal in this training cycle was to earn the object of my desire – a new PR with some bells and whistles – without going to the well too many times and while remembering that visualization substitutes complements the training process.
Being a process personality for whom the pursuit and the anticipatory taste of the dangling carrot matters as much as, if not more than, the possession (thanks to my mothership, teachers and Gita 2:47), being committed to the training cycle and its goals wasn’t new or difficult. But training myself on other fronts (e.g., combating fears) wasn’t easy and I expected to get better at those along the way with help from dear friends (thanks, Lianna!). A customized training plan was designed by taking into account the relevant elements of previously used training plans and other pieces of literature mostly peer-reviewed in the field of exercise physiology/kinesiology. It was tweaked and fine-tuned with a lot of help from Stephen and Ray to reach and hold the desired needed pace for the entirety of marathon distance.
The plan for Chicago WhistleStop Marathon
If my original plan had stayed intact, I’d have run the Chicago Marathon this weekend as my primary (or goal) Fall race … at the end of a 15-week training cycle. But as usual, life happened and things changed – likely for the better. Thus, the 2019 Chicago Marathon became the last (but supported) 24-mile LSD run to mark the end of week #11 – to refine racing and pacing tactics as well as rehearse travel logistics – towards the 2019 New York City Marathon. However, by the end of week #07 of this revised training cycle, it didn’t make much sense to drive ~18-20 hours for a training run in a big city. To not let the retrospective cost (i.e., a cost that has already been incurred and cannot be recovered; e.g. the registration fee) negatively impact the prospective costs (i.e., future costs that may be avoided if an appropriate action is taken; e.g., hotel accommodation, fuel for the body and the car, investments in expo, etc.), I deferred the Chicago Marathon until 2020. By the end of week #09, Laura and Stephen gave reliable intel that the course through the five boroughs of New York City doesn’t easily lend itself for a PR-like attempt. So, the plan for weeks #10 and #11 was tweaked to accommodate a taper period. With necessary information from Jan, Kim, Ray and Dr. Suits, and following in the keystrokes of John, I signed up for the 2019 WhistleStop Marathon.
Quite a while ago, I had stumbled upon Jared Ward‘s manuscript – Analyzing Split Times For Runners In The 2013 St. George Marathon submitted to The Annals of Applied Statistics (I’m not sure if it was ever published). What appealed to me in this manuscript was the pacing strategy backed objectively by numbers – one in which the splits got incrementally faster with distance. The concept wasn’t entirely new to me and thanks to my friends, I had even enjoyed some success by implementing it in recent times at the half marathon distance. Though I’d like to run in and complete the St. George Marathon, owing to its altitude and my lack of acclimatization to/training at such altitude, it won’t be now or in the very immediate future.
It took very little effort to realize that Ashland, WI, was about 1700 miles closer than St. George, UT. With a little bit of research and help from friends, I found that both St. George (start: ~5240 ft; finish: ~2680 ft; ~51% drop) and WhistleStop (start: ~1170 ft; finish: ~670 ft; ~57% drop) marathons have similarly shaped elevation profiles. Furthermore, WhistleStop course runs on an old railroad grade (hence the logo of an old fashioned steam engine!) in the shadows of Lake Superior at an altitude (~600 feet above sea level) I am used to. If I haven’t disclosed it before, I LOVE me some trains … so much so that the last couple pages of just about every notebook between grades 3-10 contained hand-sketches of trains or train tracks. Coupled with an abundance of breathable oxygen, it lends itself to my live low, train low, race low practice. Plus, the weather in Northern Wisconsin is blessedly cool (40-50 F) and the autumn makes the scenery colorfully pretty!
All this gave me confidence that I should be able to execute an incrementally faster pacing strategy for the marathon distance. The finer numerical details of the pacing strategy were guided by my performance in the 2019 Bridges & Bluffs Half Marathon two weekends ago in Ironwood, MI, and in consultation with/guidance from Stephen and Ray. Barring an unforeseen circumstance or acts of ill-advised stupidity from my end, I believed I could significantly improve my time and bring it to the 3:20 neighborhood (current PR: 3:35:46, earned in the 2019 Illinois Marathon).
Training plan
|
Notation:
Easy (E) |
Long (L) |
Race (R) |
Speed (S) |
Tempo (T)
Distance in miles and time in h:mm:ss |
|||||||||
| Wk |
Mon |
Tue |
Wed |
Thu |
Fri |
Sat |
Sun |
Week | Cycle |
| 01 |
07/29 E 6.00 10.25 1:29:32 |
07/30 S 2.00 6.52 1:29:50 |
07/31 E 6.00 10.38 2:24:31 |
08/01 T 3.00 6.30 1:26:53 |
08/02 E 6.00 10.04 2:56:27 |
08/03 L 12.00 13.16 2:05:27 |
08/04 Rest - - |
35.00
56.65 11:52:40 |
35.00
56.65 11:52:40 |
| 02 |
08/05 E 6.00 11.35 1:45:11 |
08/06 S 2.00 6.40 1:27:59 |
08/07 E 6.00 10.34 1:37:54 |
08/08 T 4.00 8.03 1:09:28 |
08/09 E 6.00 3.15 1:59:55 |
08/10 L 13.00 13.10 1:38:06 |
08/11 Rest 7.16 1:11:56 |
37.00
59.53 10:50:29 |
72.00
116.18 22:43:09 |
|
W02D06 (08/10) was the 2019 Paavo Nurmi Half Marathon in Hurley, WI. |
|||||||||
| 03 |
08/12 E 6.00 11.46 1:53:28 |
08/13 S 3.00 7.41 1:33:49 |
08/14 E 6.00 10.14 2:06:07 |
08/15 T 5.00 9.10 1:48:23 |
08/16 E 6.00 10.03 2:37:23 |
08/17 L 15.00 15.62 2:12:21 |
08/18 Rest - - |
41.00
63.76 12:11:31 |
113.00
179.94 34:54:40 |
| 04 |
08/19 E 6.00 7.59 1:27:33 |
08/20 S 2.00 5.04 0:45:14 |
08/21 E 6.00 6.89 1:23:19 |
08/22 T 4.00 5.24 1:00:44 |
08/23 E 6.00 10.10 2:59:59 |
08/24 L 11.00 13.64 2:39:38 |
08/25 Rest 7.19 1:16:14 |
35.00
55.69 11:32:41 |
148.00
235.63 46:27:21 |
| Wk |
Mon |
Tue |
Wed |
Thu |
Fri |
Sat |
Sun |
Week | Cycle |
| 05 |
08/26 E 6.00 - - |
08/27 S 3.00 6.31 1:02:11 |
08/28 E 6.00 10.57 2:16:46 |
08/29 T 5.00 13.32 3:13:49 |
08/30 E 6.00 3.37 0:31:56 |
08/31 L 17.00 18.12 2:22:22 |
09/01 Rest 12.64 1:56:58 |
43.00
64.33 11:24:02 |
191.00
299.96 57:51:23 |
|
W05D06 (08/31) was the 2019 Marquette Half Marathon in Marquette, MI. |
|||||||||
| 06 |
09/02 E 6.00 5.47 1:03:48 |
09/03 S 4.00 - 0:30:00 |
09/04 E 6.00 - 1:30:00 |
09/05 T 6.00 - - |
09/06 E 6.00 2.58 0:22:51 |
09/07 L 18.00 9.37 1:11:04 |
09/08 Rest - - |
46.00
17.42 4:37:43 |
237.00
317.38 62:29:06 |
|
W06D06 (09/07) was the 2019 Last Chance BQ.2 Marathon in Grand Rapids, MI (DNF). |
|||||||||
| 07 |
09/09 E 6.00 12.66 1:49:07 |
09/10 S 3.00 6.46 0:58:04 |
09/11 E 6.00 8.42 3:31:39 |
09/12 T 6.00 - - |
09/13 E 6.00 - - |
09/14 L 20.00 16.60 2:08:06 |
09/15 Rest 5.01 0:52:55 |
47.00
49.15 9:19:51 |
284.00
366.53 71:48:57 |
|
W07D06 (09/14) was the 2019 Last Chance BQ.2 Marathon in Geneva, IL (DNF). |
|||||||||
| 08 |
09/16 E 6.00 - 1:30:00 |
09/17 S 4.00 6.64 1:14:56 |
09/18 E 6.00 8.40 1:16:49 |
09/19 T 5.00 - - |
09/20 E 6.00 - - |
09/21 L 13.00 20.21 2:55:00 |
09/22 Rest 6.27 1:08:32 |
40.00
41.52 8:05:17 |
324.00
408.05 79:54:14 |
| Wk |
Mon |
Tue |
Wed |
Thu |
Fri |
Sat |
Sun |
Week | Cycle |
| 09 |
09/23 E 6.00 6.26 1:05:59 |
09/24 S 4.00 7.05 0:59:21 |
09/25 E 6.00 10.03 2:01:25 |
09/26 T 7.00 7.14 3:12:10 |
09/27 E 6.00 - - |
09/28 L 20.00 16.11 2:03:07 |
09/29 Rest 5.45 0:55:45 |
49.00
52.04 10:17:47 |
373.00
460.09 90:12:01 |
|
W09D06 (09/28) was the 2019 Bridges & Bluffs Half Marathon in Ironwood, MI. |
|||||||||
| 10 |
09/30 E 4.00 - - |
10/01 S 2.00 - - |
10/02 E 4.00 5.52 0:48:37 |
10/03 T 4.00 - - |
10/04 E 4.00 6.28 2:00:42 |
10/05 L 10.00 10.01 1:56:07 |
10/06 Rest 12.03 1:44:39 |
28.00
33.84 6:30:05 |
401.00
493.93 96:42:06 |
| 11 |
10/07 E 3.00 3.21 0:33:33 |
10/08 S 2.00 - - |
10/09 E 3.00 7.02 1:33:41 |
10/10 Rest - 2:00:00 |
10/11 E 3.00 3.12 0:30:45 |
10/12 R 26.22 26.31 3:29:27 |
10/13 Rest - - |
37.22
39.66 8:07:26 |
438.22
533.59 104:49:32 |
|
W11D06 (10/12) was the 2019 WhistleStop Marathon in Ashland, WI. |
|||||||||
Training eye candies
Vitals (sleep, resting heart rate and weight) are/were measured every day shortly after waking up. If a measurement wasn't taken on a given day (say, due to laziness), then the recorded value from the previous day is used for computing the 7-day moving average.
The day before
Work (all aspects of it: teaching, research, HPC, administrative and synergistic activities) have been going well and this week was no exception. From a training perspective, things have been going well too, last two weeks serving as a taper period with sufficient rest. As I have done in case of organized events during this training cycle, an easy 3 miler was completed on Friday morning about 24 hours before the schedule race start time (8:30 am, Wisconsin Time) as a shakeout run.
An uneventful and short-ish drive on Friday afternoon brought John and I to the base camp in Ironwood, MI, on our side of the cheese curtain. We missed the turn towards Mass City along the way but instead of letting it bother us or turning around, John suggested we take the scenic drive through the Porcupine Mountains Wilderness State Park. It was certainly worthwhile as sunshine broke through the clouds just long enough to make a couple pit stops and check out the autumn’s splendor. We got a bite to eat (I got a salad) in Maplewood Steakhouse before checking in at the Quality Inn. Carrying a burrito from our own Rodeo Mexican Kitchen for dinner fixed the value of one variable. Needing to build on the full night’s rest from the night before, I ended the day’s proceedings around 8 pm, eventually falling asleep around 8:45 pm.
Race day
I don’t normally open the YouTube app at witching hours before a race day. But then again it’s not every day that I get to witness and be a part of, albeit on YouTube and from several timezones away, an attempt to break an improbable, if not impossible, barrier. Truth be told, I had set an alarm for 1:59 am (Eastern Time; with a 15 minute snooze buffer in case I didn’t wake up at first) to watch the live coverage of INEOS 1:59 Challenge on YouTube starting at 2:15 am (Eastern Time). Being pretty confident that Eliud would pull it off, I turned off the alarm before going to bed.
When I woke up around 1:45 am (Central Time) to use the bathroom, I was naturally curious as to how he was doing. As expected, he was doing just fine. I stayed up until he crossed the halfway point and with him running 10 seconds under the goal time, I fell asleep feeling confident that I would wake up to some wonderful news. I woke up a bit later but just not to the wonderful news but to a dream that he had broken the barrier. In a hurry, I opened the YouTube app again and was pretty thrilled to see the final kilometer or so of this epic adventure. With a little more than 500 meters to go, seeing Eliud emerge from the throng of the pacers and accelerate towards the finish line and cross it in a spec over 1:59:40 was a goose-bumpy and tear-jerker of an experience! As one of the commentators put it,
It’s a Saturday run like we’ve never seen before … Eliud Kipchoge has the hand of history on his shoulders … Eliud Kipchoge storms into the history books in Vienna … One final lung-busting stride for Kipchoge, one giant leap for human endeavor!
By the time I got done watching post-challenge interviews and opinions, it was close to 4:15 am. With first of the alarms to go off around 4:30 am, it didn’t make much sense to return to sleep. In hindsight, going to bed before 9 pm and waking up 15 minutes earlier than scheduled not only gave me sufficient rest but few extra minutes to get ready at a relaxed pace. After the usual preparation, John and I checked out of Quality Inn at 5:30 am. A 45-minute drive, some in snow and the rest in gusting winds, got us safely to Ashland, WI, around 6:30 am.
Picking up the race packet and verifying its contents were a breeze. Per guidelines from the race officials, I took first of the shuttles and it turned out to be a blessing. Not only I got to travel with Jim Engel, I got a comfortable seat in a bar that doubled up as a warming hut near the start line. A few minutes before the scheduled start were spent remembering things: apply vaseline to body parts exposed to the cold (thanks to an EMT staff in 2014 Kaiser Permanente San Francisco Half Marathon), consume water at every other aid station (thanks to Stephen) and not pour water over my head or throw away the gloves (thanks to Meb). The beautiful rendition of God Bless America was soon followed by the horn that sounded the start of the race at 8:30 am.
|
Goal vs Reality
Goal: 26.22 mi in 3:34:45 (8:11 min/mi) Reality: 26.31 mi in 3:29:29.0 (7:57 min/mi) |
|||||||||
| # |
Lap Distance mi |
Lap Pace min/mile |
Lap Elevation feet |
Total Distance mi |
Total Time h:mm:ss |
Total Elevation feet |
Total Pace min/mile |
Projected Finish Time h:mm:ss |
Differential Goal Time h:mm:ss |
| 01 | 1.00 | 7:54 | 66↑ 26↓ | 1.00 | 0:07:54 | 66↑ 26↓ | 7:54 | 3:27:08 | 0:07:37 |
| 02 | 1.00 | 7:34 | 20↑ 30↓ | 2.00 | 0:15:28 | 86↑ 56↓ | 7:44 | 3:22:46 | 0:11:59 |
| 03 | 1.00 | 8:43 | 26↑ 20↓ | 3.00 | 0:24:12 | 112↑ 76↓ | 8:04 | 3:31:30 | 0:03:15 |
| 04 | 1.00 | 7:28 | 10↑ 33↓ | 4.00 | 0:31:41 | 122↑ 109↓ | 7:55 | 3:27:34 | 0:07:11 |
| 05 | 1.00 | 7:27 | 16↑ 23↓ | 5.00 | 0:39:08 | 138↑ 132↓ | 7:49 | 3:24:57 | 0:09:48 |
| 06 | 1.00 | 7:28 | 10↑ 0↓ | 6.00 | 0:46:37 | 148↑ 132↓ | 7:46 | 3:23:38 | 0:11:07 |
| 07 | 1.00 | 7:28 | 10↑ 20↓ | 7.00 | 0:54:05 | 158↑ 152↓ | 7:43 | 3:22:19 | 0:12:26 |
| 08 | 1.00 | 7:30 | 10↑ 10↓ | 8.00 | 1:01:35 | 168↑ 162↓ | 7:41 | 3:21:27 | 0:13:18 |
| 09 | 1.00 | 7:34 | 20↑ 30↓ | 9.00 | 1:09:09 | 188↑ 192↓ | 7:41 | 3:21:27 | 0:13:18 |
| 10 | 1.00 | 7:22 | 0↑ 39↓ | 10.00 | 1:16:32 | 188↑ 231↓ | 7:39 | 3:20:34 | 0:14:11 |
| 11 | 1.00 | 7:28 | 0↑ 49↓ | 11.00 | 1:24:01 | 188↑ 280↓ | 7:38 | 3:20:09 | 0:14:36 |
| 12 | 1.00 | 7:18 | 0↑ 49↓ | 12.00 | 1:31:19 | 188↑ 329↓ | 7:36 | 3:19:16 | 0:15:29 |
| 13 | 1.00 | 7:30 | 0↑ 56↓ | 13.00 | 1:38:49 | 188↑ 385↓ | 7:36 | 3:19:16 | 0:15:29 |
| 14 | 1.00 | 7:13 | 0↑ 56↓ | 14.00 | 1:46:03 | 188↑ 441↓ | 7:34 | 3:18:24 | 0:16:21 |
| 15 | 1.00 | 7:39 | 0↑ 39↓ | 15.00 | 1:53:42 | 188↑ 480↓ | 7:34 | 3:18:24 | 0:16:21 |
| 16 | 1.00 | 7:49 | 10↑ 13↓ | 16.00 | 2:01:31 | 198↑ 493↓ | 7:35 | 3:18:50 | 0:15:55 |
| 17 | 1.00 | 8:01 | 13↑ 10↓ | 17.00 | 2:09:32 | 211↑ 503↓ | 7:37 | 3:19:42 | 0:15:03 |
| 18 | 1.00 | 8:06 | 7↑ 36↓ | 18.00 | 2:17:38 | 218↑ 539↓ | 7:38 | 3:20:09 | 0:14:36 |
| 19 | 1.00 | 7:57 | 0↑ 56↓ | 19.00 | 2:25:35 | 218↑ 595↓ | 7:39 | 3:20:34 | 0:14:11 |
| 20 | 1.00 | 7:52 | 0↑ 49↓ | 20.00 | 2:33:27 | 218↑ 644↓ | 7:40 | 3:21:01 | 0:13:44 |
| 21 | 1.00 | 8:15 | 0↑ 59↓ | 21.00 | 2:41:42 | 218↑ 703↓ | 7:41 | 3:21:27 | 0:13:18 |
| 22 | 1.00 | 7:54 | 0↑ 20↓ | 22.00 | 2:49:36 | 218↑ 723↓ | 7:42 | 3:21:53 | 0:12:52 |
| 23 | 1.00 | 8:30 | 0↑ 23↓ | 23.00 | 2:58:06 | 218↑ 746↓ | 7:44 | 3:22:46 | 0:11:59 |
| 24 | 1.00 | 10:07 | 33↑ 0↓ | 24.00 | 3:08:13 | 251↑ 746↓ | 7:50 | 3:25:23 | 0:09:22 |
| 25 | 1.00 | 10:31 | 10↑ 7↓ | 25.00 | 3:18:44 | 261↑ 753↓ | 7:56 | 3:28:00 | 0:06:45 |
| 26 | 1.00 | 8:25 | 20↑ 3↓ | 26.00 | 3:27:09 | 281↑ 756↓ | 7:58 | 3:28:53 | 0:05:52 |
| 27 | 0.31 | 7:25 | 0↑ 13↓ | 26.31 | 3:29:27 | 281↑ 769↓ | 7:57 | 3:28:27 | 0:06:18 |
| The final cumulative time, 3:29:27, may not match the official time (3:29:29.0) owing to rounding errors. Starting my watch a few seconds before the start and stopping it a few seconds after crossing the finish line can be an additional reason for this discrepancy. The overall distance, 26.31 mi, may not match the designated (or certified) event distance (26.22 mi) owing to idiosyncrasies associated with GPS data collection OR my inability to take the tangents OR the aforementioned early start/late stop reasons, and in some rare cases, incorrectly measured (or advertised) courses or DNFs. As a result, the cumulative pace and the projected finish time might not match the official values as well. | |||||||||
Fearing a gun time/mass start, I started near the very front of the pack but immediately held back my pace. The mental map I had of the course held true for the first mile. Once turned on to the Tri County Corridor Trail, the course was lot more rocky, rutty and frequented with sand, bumps and puddles than I had anticipated for the next 23-ish miles. With the mental map of the elevation profile no longer matching the reality by mile #2, I ditched the plan and replaced it with a conservative one. A brief 1-minute stop to use the bathroom punctuated mile #3 but it didn’t break my new plan or the rhythm.
The course felt like one of those flat hills or false downhills and fellow runners far ahead always seemed to be above my eye line. Maybe it was all in my head but the feeling was one of a grinding gradual climb that lasted 20+ miles … indicating the need, post-race, to step up my mental game because the elevation profile clearly shows something else. But the course had its share of pretty portions as well: a canopy of Fall-colored trees and blustery snow flurries, though far and few between in the beginning but more frequent during later miles, added a certain romantic touch to the run!
Still running conservatively and adapting my effort to what the course gave me, I reached the 10 mile mark around 1:16:30 (7:39 min/mile), the halfway point around 1:39:30 (7:36 min/mile) and the 20 mile mark around 2:33:30 (7:41 min/mile). But the cold (34 F at the start; predicted high of 42 F but never went above 36 F during the entirety of my run) and accompanying winds made my legs and torso region feel like blocks of ice by that point. I struggled in miles 24 and 25, and walked a few steps a few times. If not for John’s presence at several road crossings earlier and his frequent reminders to trust the process, I would have had a much harder time.
Just as the possibility of John’s efforts as well as a prime bib number (#241) going down the drain was leaning towards becoming a harsh reality, I attempted a few short surges to get out of this funk: most of them failed but the final one near the end of mile 25 worked. The last 1.50 miles were on paved path and I was able to sustain the pace gained from that last surge. I was even able to put one final kick over the final few hundred yards even though it had one too many sharp turns – easy candidates for bad wipeouts under slippery conditions. The official time, 3:29:29 (7:59 min/mile), was good enough for 33/210 overall, 28/122 in gender, 7/17 in AG and 15/69 in masters – earning me a new PR by 6 minutes and 17 seconds.
The post-run activities included catching up with John and my two new friends, Angel and Nick, from Colorado, re-hydrating and changing into warmer clothes. Our return journey, in light of the predicted snow/snowy rain, started shortly after we got a bite to eat at the Chequamegon Food Co-op, and was smooth and uneventful. Much of the evening after getting back to Houghton was spent thawing out from the inside, and the icing on the day was an ice cream gathering with good ole friends.
The day after
Nearly 10 hours of sleep helped not only thaw me out completely but also relieve much of the soreness from race day. Little did I know, when I turned on the Olympic Channel to watch the live telecast of 2019 Chicago Marathon (an event I was scheduled to run until about two weeks ago), I’d see yet another remarkable performance! Brigid Kosgei, who started faster than the commentator liked (or maybe it was the pacers’ fault?), went on to a world-record performance with a time of 2:14:05 (5:07 min/mile) breaking the previous record set by Paula Radcliffe (2:15:25) in 2003 London Marathon.
Those 2+ hours also provided sufficient opportunity to reflect back on yesterday: John, in spite of not being able to run himself as a result of stress fracture, had travelled with me on this trip – he drove the entire way and took care of all logistics, saving me a lot of mental energy to focus on the run; He had been driving from one road crossing to another in less than ideal conditions for spectating to remind me to trust the process; I had forgotten Jan’s suggestion to leave racing flats at home and use a pair with better cushion; I didn’t do the progressively faster splits as I had planned; I had perceived gradual downhill portions as mostly grinding uphill; I had adjusted my effort to the perceived elevation profile of the course; the average pace of the struggle bus I rode in miles #24 and #25 – 10:15 min/mile – was my top-end comfortable pace about a year go; I followed the nutrition (i.e., gel) plan faithfully throughout the course – taking one every 5 miles through the first 15 and then one every 4 miles over the next 8. I had missed the goal by about 10 minutes in what was mostly a trail marathon under less than ideal conditions for running. Taking everything into account, I had come away with more plusses than minuses, and had gained valuable confidence to run the second race of this training cycle in 3 weeks in the Big Apple.
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 my family of good friends, mentors and coaches in and outside of my community for all the unexpected, undeserved and unrewarded acts of kindness and constant encouragement as well as offerings of constructive criticism to improve myself as a human and an athlete. I am eternally grateful to all those who let me train with them, who shared their meals and experiences with me, who helped keep me in good health, who helped me stay the course, and who cheered me on from home or along the course.
3 Replies to “2019: WhistleStop Marathon”