2023 was a strange year in my running. It on one hand was the year that I ran the most, 3850km, more than the 3,111km in 2019; yet on the other hand, a year where I ran only two events and did not run my best. To be clear, I wasn't looking for personal bests - I was looking for a consistent year of running, and had two goals: a mileage goal of 4,000km in the year (not achieved) and a climbing goal of 52,000m ascent for the year (achieved) and that good performances might be a by-product. When the mileage goal started to slip out of reach, I switched to a new goal: pace.
For most of the year, I had been noticeably slower at the fastest part of my range compared to other years. To put some numbers to it, at my best I could run 5km in less than 20 minutes, but in late 2023 I would not be able to go under 21 minutes; in a half marathon at my best I could go under 1 hour 30 minutes, but I would struggle to go under 1 hour 40 minutes in 2023. These margins might seem small but the work to get them down would usually take a long time. So, I switched to pace training in December. The implications of this are that mileage comes down a bit and very specific work-outs are used to sharpen up. Such an example might be 10x400m, or 3x2mile runs, where you run particular distances at fast paces with rests in between.
The surprising thing was that the fruit came quickly. I ran a mile in 5:49, a lifetime best. At the end of the year, I almost broke 20 minutes for the 5km park run (where humorously all runners had to squeeze past a van and its trailer on two parts of the route). My pace training continued into 2014 to prepare for my main target event, the Coatesville Half Marathon.
I have a lot of affection for this event. Early in my running in 2017, I ran the Coatesville Classic (8km), which I described here: Crypticity's abound: Comeback and then the Half in 2019 (Crypticity's abound: Mark). Quoting myself for brevity: "The Coatesville Half course is notorious. It is the hilliest course of the series with one significant incline at 3km, another at 10km, another at 14km and another at 16km." In 2019, I ran 1 hour 37 minutes, which was a solid performance in what would be my best year in running, so I was looking for the run this year to be a bit of a bellwether for the year ahead.
The lead-up through January was very good. In a time-trial I ran 1 hour 35 for a flat half marathon distance. On the Saturday eight days before the run, I ran two training runs that surprised me in pace that exceeded what I thought I was capable of, a 5x1mile and a 2x4mile. Unfortunately on the last one at the very end of the last 4 mile I felt a tightening in my hamstring and I jogged home very gently. I gave myself a two day rest and then did some light runs to test it out again. I felt OK so continued with my normal "week before" taper runs. And then we come to the day of the race.
After a poor night sleep, I woke naturally at 6:12am with a start. My shock at the time jolted my heart and mind into action. Somehow, my 5:30am alarm had not vibrated me awake. In fact, it claimed it had and was doing it every eight minutes, as if self-snoozing itself without any fuss. I had to leave by 6:30am to realistically get to the venue and be ready for the 7:30am race start, so I exploded out of bed, changed, coffeed and threw everything in a bag and left the driveway at 6:32am. So far no speeding tickets have been received, so my arrival in the Coatesville Pony Club car park at 7:07am can be said to have been smooth and without issue. I grabbed my racebib and then to the back of a very long queue for the portaloos. I tried my best to do some dynamic stretches while in the line, and then after a quick prep in the loo, jogged over to the middle of a tightly packed starting chute at 7:27am without any real warm-up.
Perhaps due to the adrenalinised chaotic start to the morning, I was much faster than my race plan, which was to aim for 4:30/km pace (which would have me on a 1 hour 35 min finish speed) until the downhill speedy finish and go sub 1:35. I had to first push through the mid-pack runners to the front 10% to find people of a similar pace, and that meant my speed at the start was a bit reckless. Fortunately for me there was an easily recognisable Zimbabwean female runner, Ketina, who usually is about my pace, so I used her as an initial measure where I needed to be and I caught up to her and dropped a bit of pace for the hill.
There began the very familiar pattern of my usual strategy: slow on this hills (letting my pace peers pace me) and then reeling them in on the flats before passing them on the downhills. Ketina disappeared after the first such iteration, and once I was at the top of the first hill, I sped up and didn't slow down. Looking at my watch, I was clearly in the 4:10-4:25/km range - too fast but feeling strangely comfortable. I kept going pulling past more pace peers to the halfway turn when I had a rather cruel realisation that I should have anticipated. My watch had measured my distance 200m short of what the marker was indicating. This was a problem because that meant I was going even faster than my watch was telling me. I could have been going 5 seconds per kilometre faster than I was reading off my watch.
For any race, the best indication of whether you are going too fast is your breathing (and also one of the best ways to know if your running companions might be entering into a struggle phase). I checked myself and thought I was still breathing quite evenly so I held my pace for the last few hills and then made the final turn onto the downhill home straight. It was then that I knew that it should be just a matter of cruising to the finish line, a certain PB, probably a couple of minutes under, and done on one of the more difficult courses.
It wasn't to be though. About 2km from the finish, I felt the tightness in my hamstring return. I couldn't but cut pace just a little; then, a pain radiated out from that point, and I shortened my gait and cut pace once more. By the time I had entered the Coatesville Domain I was not enjoying running and would have had a noticeable limp. Only one person passed me though and I got over the line at 1:30:12, my third fastest half marathon time.
For perspective, despite the niggle, I would say this is my best performance. My other two fastest times are 1:29:58 at the Waterfront Half, the flattest possible course. and 1:30:04 on the trickier Millwater Half. But none of them are like Coatesville. It's kind of amazing that after all these years though all three PBs are clustered within 14 seconds of each other after different 21.1km races.
I gave myself a break of four days from running and then ran 5km on Friday evening with hamstring sensations but no pain. This morning I ran 22km with only mild sensations that never amounted to anything and then a massage and some strengthening work. I hope the hamstring is just an oddity that with a bit of rehab I'll get back quickly onto a regular routine.
So the omens are bad/good. Bad that I picked up a niggle/weakness of some sort. But good in that I have the best foundation for a year of good performances. My next chances to race are:
- Hobsonville Point ParkRun 24/02/2024 (goal: under 19:30)
- Waterfront Half Marathon 07/04/2024 (goal: 1:27)
- Kirikiriroa Marathon 09/06/2024 (goal: under 3:20)
- North Shore Marathon 15/09/2024 (goal: under 3:15)
All with ideal training...
No comments:
Post a Comment