Almost a year ago, I had a crack at the London Marathon. A big occasion that lives up to the hype. I didn’t get my target time of 4 hours, running the distance in 4:10:46. Which is why I’m having another go this year in the Brighton marathon. So what went wrong?
I picked up a bug about one month before the event which took miles out of my training regime, and left me short of fitness in the final days. I was ill for one week, but it impacted greatly on the next three weeks.
Being Honest About My Expected Finish Time
On the race application, I said that I expected to finish in 4 hours. It seems that a great number of people were more dishonestly optimistic about their times than I was. As a result, I spent the whole race stuck in heavy traffic, struggling to run past slower runners. The end of race stats told me I ran past 15,000 people. That’s 15,000 people who over-estimated their abilities and got in my way!
I almost had the fitness, but I was slightly off. I trained up to 38 miles a week. This year I’ve been nailing 40 miles.
For the 2017 marathon, I trained for 4 months. This year I will have trained for 5 months.
That’s enough moaning. This year I have tweaked my approach rather than changed it radically. I will have completed the same number of big runs (3 x 20 mile runs). But getting in more miles per week and over a longer period of time should yield some great results. Add to that the fact that Brighton should give me a lot more running space than the London marathon could. Sure it will be busy at the start, but after that, I should get some space.
So here is the evidence…