What a beautiful day to run the trails along the Thames path. The 21st May 2017 marked the 2nd time I have ran this event, but the first time I have paced it. Not only did I pace this event for F3events, but also grabbed a group of fellow pacers to come and do it with me. This was the 31st event I have paced, something I enjoy doing week in week out.
The usual suspects all lined up. We were kitted out with tops by the organisers, and registration was relatively smooth. I had expected a flag or balloon for marking us, but in hindsight I’m glad we didn’t as this would have been impossible in the trails. We started off at the start of each wave, 5 minutes apart, and announced that we were running in 15 minute intervals. Nick ran 1:30; I ran 1:45; Gazza ran 2:00; Phil ran 2:15; Matt ran 2:30 and Simon ran 2:45.
At the start we spent a bit of time chatting with everyone. Unfortunately the pacers had not been announced far in advance, and people’s wave placements did not entirely match where we would start. I spent time going to each wave telling people where we would be positioned, and a few people changed waves to match their pacer.
It was small waves, but I picked up a good group, including Lee. Before long we were off, and the whole course follows the Thames Path along the river.
There were some narrow sections, and a few slippery parts, but on the whole it was a flat and fast trail route. You won’t find a faster trail half marathon out there. With all the rain lately it was surprisingly a really beautiful day, and a lovely peaceful route. After about 6 miles there is a small section where you go alongside a road, and cross over, but then join the beautiful river once again.
With the waves in 5 minute intervals I did not find any point that I was held up, except for before mile 12 where the marshal tried stopping me at the road. I found this very strange as there were so few of us and usual practice would be to stop the cars, not the runners? This was commented on by other pacers too.
The course and day was beautiful, but there were a couple of negatives. First the water did seem a little sparse, and was in cups. This is always a negative for me, but often to be expected at smaller events. The main criticism is the course measurement and mile markers. The mile markers were spot on for the first half, as were my splits, as I was hitting between 7:50 and 8:00 min miles (required sub 8’s). By about mile 9, 10 the markers then were coming up too soon, so suggested we were too fast. At mile 10 my watch only recorded 9:90 miles. This is not the end of the world, but a little strange as the opposite to what you usually expect. I’m used to mile markers being out, but usually they are too long,
I had my usual 25 second cushion so I gradually slowed, knowing that even if the markers evened out I was well within time. Both 11 and 12 were consistently under by .10, so those miles I recorded 8:07 and 8:09 to even up the miles (if I stuck to my watch I risked coming in at 1:43, which is too fast). Again this is pretty standard when pacing, trying to match the markers but ensuring you are on schedule or under with both watch and mile markers.
I felt really good and settled into a 8 min mile pace. Told those around me they had plenty of time, and for them to just push on for strong finish. We approached the final bridge and I could see people the other side, so assumed you just crossed the bridge and then that was the end. When I crossed the bridge I still had a couple of minutes to spare and it was past 13 miles (although I did not see this marker). Then I started to panic, where was the finish? I started to speed up at this point and caught up with those who I had sent on. I felt terrible as I realised the time slowly hit 1:45 and I still could not see the finish. I came in a minute over, and my watch recorded 400 metres over. At my pace that’s 2 minutes. If the markers had identified this throughout I could have adjusted accordingly, but at mile 12 my watch said 11:90, so the last 1:12 miles was actually something like 1:50, 3 minutes longer than expected.
I feel terrible because pacing is really important to me, and there were two that stuck to me until the end and I let them down. This is really disappointing to me.
As it turns out, every single pacer had exactly the same experience. All of us were about a minute or so over, and this included us all speeding up at the end. Very disappointing, but we all did a great job. Very proud of all the pacers and sorry the course was too long. More disappointing that we have had feedback from other runners that it is normally over by quarter of a mile. If we were told this at the beginning it would have made a huge difference.
Overall it was a great run, and until mike 12 everything was great. I really enjoyed it and so did everyone else. I can’t deny the course measurements ruined it for me personally today, because it’s so important for me to get everyone their target times. I know all the pacers feel the same. But it was still a fantastic day, and lovely route.
Check out Racecheck for more reviews. As always i am rewarded for running through my life insurance. See how Fitness Rewards can reward you here.
7 thoughts on “Windsor Trail Half Marathon 2017”
Hi Paul this is absolutely spot on in every detail and I still feel very disappointed with the course distance. I was actually telling people around me that we’re struggling in the final few miles to ease up a little; because I knew they had been with me for the whole duration and I was 48/50 sec under the 2hrs time.?
Rather than see them give up it so close to home I gave them my word if they eased off by 15/20 secs and kept me in sight we would ALL be under 2hrs.
Imagine my panic when I heard my watch signal 13 miles but couldn’t see the mile marker and I knew we were a bit out from the finish line!! Once I saw the aeroplane in the park by the Thames it dawned on me I still had another min or so to the finish line as we had walked from the car park past this to the registration. I naturally sped up (trying to claw back the time but it was far too late), dropping the large following I had around me for the whole run :-((. I’ve never seen so many people so disheartened and I blame myself as they trusted me and I paced 9.04/05 for the whole duration and still was over. I’ve paced lots of times and normally the mile markers are long so I would lap reset to pull the time in line accordingly. I enjoyed the route albeit very narrow and congested for the first 4 miles and very slippery in places but I guess that’s what you expect on trail races. The marshalls I found to be very helpful and lovely medal too. Water in cups , as you say is never a good thing but it neeeded to be at EVERY 5K point especially as it was very warm & humid. Afterwards I spoke with over a dozen people on their feedback and all those that had run it previously stated it has always been 0.3 miles long!!!! How I wish someone would have mentioned that before the start or even during the run as I would have ran 10 secs faster and gauged it better
This race has the potential to be an extremely popular event especially in the location it is in, if the organisers F3 events can just take on board the few ‘not so good parts ‘and iron these out
Would I pace this again?
Absolutely but I would make it clear to my runners in my pen that it a long course and I will be pacing 10/12 secs faster than usual to allow for this.
Thank you for the invite Paul much appreciated 👌
Thanks for comments mate. Completely agree, what is worse is that mile markers were saying we were ahead, so if in future they keep the course they need to advertise as longer, otherwise at mile 12 you would have to be over 2 minutes ahead of pace in order to finish on time
Must be gutting Paul, because I know how seriously you take this.
Yes mate, the worst bit was a runner who was looking to get 1:45 for first time and whole way told her how great she was doing. She could have went faster, we could have done it…
Thanks for the interesting article, which matches my experience yesterday, having also been monitoring distance on my watch. (You sped past me on the bridge and I finished 2 mins 10 over 1h45, which can all be explained by the extra distance and my 50-second wait at the road crossing!)
Hey chris. Well done and sorry you missed out because of the distance