Tag Archives: road running

Shepperdine Marathon: race report

by Ben

Background and training summary

I’m both not that keen on running long races, and honestly not that experienced at it. Of the 85 races I ran from 2012 to 2020, only one was longer than 20 miles (the Snowdonia Trail Marathon) and fourteen were over 10 miles (around 16%). In fact, since running Snowdonia in the summer of 2018, I did 19 races, the longest of which was a 10-miler. Over half were 10k races. Through the summer, I often raced two or even three times a month.

So when Covid returned in winter 2020, my first thought was to keep working on what has been a target since 2017: a sub-40 minute 10k. But… I also had a crazy thought: without the continuous grind of 10k races, maybe I could train for a marathon…

I had got into a good training groove through the latter half of 2020, hitting good (for me) monthly mileages:

  • July: 113 miles
  • August: 130 miles
  • September: 138 miles
  • October: 128 miles
  • November: 100 miles
  • December: 103 miles

My overall mileage was okay, but my long runs sat at around 10 miles, so in January and February I started to work them up a bit longer; 14, 15, 17, 14, 18, 20… and then we moved house, roughly a month before the race. Let me tell you, moving house just before a big race is not ideal preparation! But still, my monthly mileages remained okay:

  • January: 102 miles
  • February: 123 miles
  • March: 111 miles
  • April: 115 miles (including the marathon)

Pre-race

As I mentioned above, my only previous marathon was off-road and went over Snowdon. So I didn’t have anything like a representative time. Based on my 10k times race converters suggested I could run something around 3:15, but I am well aware of my own capabilities and experience. As well as very rarely running longer races, I know that my body just isn’t that well suited for it. So I added a bit on, rounded it off, and came up with a target of 3:30.

This was quite a personal target – mostly I was telling people that I just wanted to get a good representative time, and would be happy with whatever I got if the race felt like it went well. You know, that rubbish.

Due to Covid restrictions, the race was pretty barebones, which honestly suits me quite well, as I’m used to small local races anyway. I’ve never really fancied the idea of a big city marathon. My only real concern was what looked like a lack of hydration stations, so I resolved to train with, and expect to race with, a hydration vest (actually a Montane VIA Jaws 10 litre pack for those interested, with bottles, not a bladder).

On race day, I arrived with a fair amount of time, and as it was a rolling individual start, I could more or less start at any point within a two-hour window, although I did have a recommended start time. My only real concern at this point was that after a couple of months of training in wet, cold conditions, the sun had come out in force, and it was that typical ‘London Marathon April Sunday’ – one of the first “hot” days of the year. And… for reasons, I didn’t end up putting sun cream on.

The race

One of the nice things with targeting a 3:30 marathon is that the pacing is pretty simple. It is pretty much 8 minute miles. Mentally, this is a comfortable pace for me to run over distance; the group I lead with the running club runs at 7:30 to 8:00 pace, and anything at “effort” is normally between 6:45 and 7:15. So I headed out with a plan of aiming for around 7:50 per mile, hoping that would be easy enough, while still giving me a bit of a time buffer in case I slowed towards the end.

So, obviously, my first mile was 7:36, followed by a 7:29. But honestly, it felt pretty nice and comfortable, so I decided to sort of stick with it; I decided to ease back a little, but settle at around 7:40. The course was an extended lollipop: a 5.5-mile ‘stick’ with three five-mile loops, and then back along the stick to the finish, just beyond the start. The overall course was pretty damn flat – my Strava recorded 417 feet across the whole thing, but the out-and-back “stick” did have some noticeable rises and falls. They all felt pretty friendly on the way out though!

The rolling start meant that I was continually passing people, and quite often being passed by others – there was no real way of gauging your pace other than simply by feel and your watch. Even so, I managed to run pretty consistently: according to Strava my first five 5km splits were 23:33, 23:54, 23:52, 24:09 and 24:18. That took me to just over 16 miles, and the start of the third loop.

Ah… the marathon runner’s grimace. Yeah… this was about 20 metres in.

The looped nature of the course had been a little bit of a worry – especially as at one point it had been advertised as a five-lap route! But I knew that the marathon would be as much as mental fight for me as a physical one, so I just viewed it as another part of the battle. And honestly, while it was a little bit difficult (I won’t lie, towards the end of that second loop, I was quite tempted just to call it quits and head back), it was fine.

Starting that third loop, my mile splits had slipped to around 7:50, but I wasn’t really that worried. I was still splitting under 8:00, which meant I was still gaining time on my target of 3:30. I figured that with some slower miles towards the end, I was looking at a good chance of somewhere around 3:25, and was feeling pretty happy with the idea. Maybe this marathon lark wasn’t as bad as it seemed?

So, of course, then things started to go a little bit wrong. I got little niggles of cramp in my right leg; both my hamstring and groin. Nothing too bad, but worries in my head. I was drinking plenty of water, but it was hot, I was sweating a lot, and probably hadn’t been taking on gels regularly enough. The combination of the hot sun and the wind, which was quite a strong headwind on the latter half of each loop was getting to me, mentally as much as physically.

My splits began to slip more, but I still wasn’t too worried, I had time in hand. 8:10, 8:06, 8:19, that’s fine, I can manage that. Then, just as I was nearing the end of mile 21, disaster. My left hamstring cramped up completely. Just seized – I couldn’t run, I couldn’t walk. Heck, I couldn’t really move my leg at all. I could see the 21-mile marker just ahead of me, but it didn’t matter, I couldn’t move.

But then I had a bit of water, took a bit of time, stretched my leg out, and managed to start slowly walking. As I did so, it freed up, and I could walk more naturally, and eventually start running, slowly, again. Physically, I was back in action, but mentally, I was thrown. I still had over five miles to go, and I was limping along. The aid station was only about half a mile back – shouldn’t I just go back there, DNF and get a lift back? Did I really want to hobble another five miles?!

I kept going, but I was hyper aware of my hamstring (and any other potential cramping muscles). I was mentally broken, the fatigue of the marathon catching up with me. I was run/walking, not necessarily because of the injury, but just because it had all become too much. The next four miles came in at 9:18, 9:25, 9:05 and 9:46, and hopes of sub-3:30 were gone. That knowledge made things worse – mile 25 was an 11:01. I just couldn’t really be bothered anymore.

Then, I knew I was getting closer to the end. I was still run/walking, but I knew I just had a mile and a bit to go, and you know what, I could still get some sort of time. A 9:35 for mile 26 was hardly setting the world alight, but mentally I’d won, I had come back from the darkness. I actually cracked out something of a sprint finish, sort of, at the end.

I finished in a time of 3:37:21, and once I got over the initial disappointment of the wheels falling off, I was happy enough with it. Sure, it isn’t the best I could do. But you know what, that’s the marathon. Two YouTubers that I follow both did marathons that day (in fact one did Shepperdine), and neither of them went to plan. Sometimes, rarely, the perfect marathon happens. But mostly, it goes wrong to varying degrees, and that’s what happened to me. You live, you learn, you improve.

So, does that mean I might give the marathon another go? Maybe. I’ve got that itch to try again, to fix the things that went wrong and to get that sub-3:30. But… I still hate long runs.

Run Exe Winter 5: race report

by Ben

Within reason, I’m racing more or less anything I can find at the moment, given the dearth of races. But that said, this race was organised by City Runs, who I’ve always heard good things about, and was along Exmouth promenade, which is as flat as you can get. As an added bonus (of sorts) I’ve never raced a 5 miler before, so it was a guaranteed PB!

The race did have two potential downsides: it was on a Tuesday evening, and racing is always slightly tougher in the evening; and Exmouth promenade is very exposed to the weather, so if there was any wind, it would have an impact on my race.

This event was a trial race, ahead of a planned monthly series. My current running is all based around improving my 10k time, and a 5-mile race is a great substitute for the 10k distance, so hopefully I can get as many of these done as possible to benchmark my progress (weather and Covid-depending, of course).

Race day

Things worked out quite conveniently, and I was actually doing a training course at home on race day, which meant that I wasn’t as exhausted as I might have ended up. It also meant that I was a bit more in control of what and when I ate, so really I had close to ideal preparation. I took my weekend runs pretty easy ahead of the race, and was rewarded with the rarely seen “Peaking” from my Garmin: result!

I headed down in plenty of time, and arrived on the promenade about 50 minutes before my start time. The race was organised into waves of six runners, each released a minute apart. I was in the fourth wave, giving me a 7:03 start time. I had a little wander around, used the toilet, and then warmed up along the course, just to get a feel for the route. (Sure, it was just along the promenade, but it was also getting pretty dark, so I wanted to check out how good the pavement was and stuff…)

The race was twice out-and-back along the promenade, so each leg was 1.25 miles. The wind had died down from earlier in the day, and was also coming off the sea, which meant that for most of the course it was a cross-wind, rather than a headwind, though it did feel slightly against you on each of the “back” parts of the course.

Race

Soon enough, it was time to get into my ‘race pen’. Each pen was coned off with plenty of space for six people to socially distance, and the race rules also meant that we had to wear a face covering until 30 seconds before we started. I opted for a buff, which I then put onto my wrist as a sweatband, which I tend to wear anyway.

3-2-1-GO: It soon became clear that I didn’t want to run as fast as the other guys in my group, and I let them move away from me. I was still dragged along a little quicker than I should have been, I probably went through the first quarter of a mile averaging sub-6 minute miles, which is far too fast for me. But, I regained a bit of discipline, and brought my pace back under control within the first mile.

I started passing slower runners from the earlier waves within about half a mile, and not much later I, in turn, started to be passed by quicker runners from later waves. Although this was quite odd, constantly passing and being passed by other runners, it did mean that it was rare to be alone for long during the race.

My first mile came in a little bit quicker than I had been aiming for: 6:26. My expectation was that something around 6:30 would be about the quickest I would manage. Even though there was only a slight wind, I planned to focus on good “out” legs, to try and offset any time-loss in the “back” legs.

According to Strava, I slotted into a decent rhythm for the rest of the race. It felt like it was just getting harder and harder, and my pace was falling off a cliff, but actually, it was pretty perfect. I clocked through the middle three miles in 6:32, 6:34 and 6:33. Honestly, I don’t think I could have hoped for any better, even if it felt like my legs were going to fall off. I absolutely did not realise how well it had gone until I got home and checked Strava: I even told Lolly that I’d run a horrible positive split. (In fact, I ran a to-the-second-perfect even split.)

The second lap was quieter than the first, but there were still plenty of other runners about, going in both directions, so the race was never lonely. I had seen the “race leaders” during my first “back” leg; they had started in the final wave, and I wondered if they would catch up with me. Some quick mental maths suggested that they probably wouldn’t. Spoiler: I was wrong.

I was starting to really feel the exhaustion in my legs during the final mile. The start/finish end of the course was not that well lit for long sections, and by this point, there were few to no runners heading back the other way. Then, with around a third of a mile left, the lead (well, not exactly) bike passed me: “Keep left, lead runners coming through.”

The finish area was exceptionally well lit!

The combination of the bike, and then the runners gave me an injection of pace, allowing me to be dragged along behind them slightly. Sure, they were running over a minute per mile quicker than me, so I couldn’t actually keep up with them, but it still gave me that push (well, pull) when I needed it. I completed the final mile in 6:31, to finish in 33:00 exactly. (Sure, my mile times don’t add up to 33:00: my GPS tracked 5.07 miles, so there are another 23 seconds, but whatever.)

Summary

Before the race I’d used McMillan Running to work out some decent race paces.

  • My recent 10k PB at the Power Run 10k had been 41:57 in windy conditions: that was equivalent to 33:30, so that had been my minimum target: Done.
  • The next target at 10k, which had been my target at the Power Run 10k was 41:00, that was the equivalent of 32:44: Not done: target for the next race.
  • The ultimate target of my current 10k training is 39:59, which is the equivalent of 31:56: Not done: target by the end of the winter, maybe?
  • Did I enjoy this race? Yes, definitely.
  • Would I do this race again? Yes, definitely.
  • What’s next? Probably the next of these. I had another race cancel, the Big Cheese, a 15-mile hilly trail race, so I guess my training now can be completely focused on this flat and fast stuff.

Power Run 10k @ Exeter Racecourse: race report

by Ben

Turns out that this is a bit of a long one, sorry about that…

In January of this year, I ran the Waves on the Prom 5k, and three days later, I also ran the Storm Force 10. It turns out, three days is the shortest span I’ve ever had between two races. I didn’t expect it to be another eight months (to the day) before I ran another race: the longest span I’ve ever had between two races. The reason for this is obvious (in case you are reading this years later for some odd reason, it was the Covid pandemic). I had a few races booked, but they, like most, were cancelled.

I had some ankle issues in February/March, and was then furloughed at the start of April. I then went through a pretty inconsistent patch: I’d have a few good weeks, then a couple of weeks when I really couldn’t be bothered and barely got out. That sort of pattern continued for a while, until I picked up another niggly injury around June. Finally though, I strung some consistency together: 113 miles in July and 130 in August, never dropping below a 25-mile week since the start of July.

I looked around, fancying a crack at my 10k PB, the lowest-dangling fruit of my collection of PBs: 42:06 set at the 2017 Chard Flyer. I had come close twice in 2019, running 42:23 at the Pawlett Plod, shortly followed by 42:28 at the Wessex 10k. I found the Power Run 10k advertised at Exeter Racecourse, and set myself a crash four-week training plan to hone my speed.

Okay, so the training plan was actually just an adaptation of Runner’s World’s 4-week 10k training for 5 days a week. It mostly involved dropping the mileage of my long run from what I had been doing (around the half-marathon distance) and focusing more on quality mileage. I stuck to the interval sessions, but a lot of the other runs got adapted to fit in with life better.

Race-day

I wondered what affect socially-distanced racing would have on my day. I was definitely more nervous pre-race than I normally would be, although that might have been the combination of the period of time since my last race, combined with the pressure and expectation of going for a PB time. (The last time I beat a PB was actually that 2017 10k…)

The race instructions were great: very clear on what would happen, and what was expected of runners. There would be no water station, so bring your own water. It was three and a third laps of the race course service road. The start would be a mass rolling start, to avoid us all standing close together in a pack. Each race would have multiple waves, so only restricted numbers of runners would be on the course at a time. Come ready to run, collect your own medal after. Very stripped back.

I arrived about 45 minutes before the race was due to start. I was directed into the car park: “Park wherever you like, but leave an empty space between you and the next car. The toilets are over there..” Yes, that was my next stop. On the way back I had a bit of a chat with Chris, another RFRC member who had run in the first wave. He gave me some useful information: the wind is horrible, and it is hillier than you might think.

Okay: my initial target had been to run something around 41 minutes. I had always hoped to take it easy early on and then assess it, but hearing about the course cemented that in my mind, especially given I was out of practice at the whole racing thing.

The chat was useful, but it also meant that I ended up running a bit late. Normally I aim to warm-up for about fifteen minutes, but I had to make do with an abbreviated seven minutes – that’ll teach me for chatting too long!

Technically a post-race flat-lay, but does it really matter?
Race

At the start, we were funnelled into three files approached the line: I was in the second row from the front, as everybody else had declared that they were too far forwards, and dropped back. As we shot off, I made a concerted effort NOT to shoot off too fast, while also bearing in mind that the pace gap would be much smaller than usual: the sub-40 guys were in later wave. A few people went past me, and I settled in around eighth or ninth. Through the first kilometre, I let a gap grow between me and the leading pack, while inadvertently, I also developed a gap from the group behind me, leaving me somewhat in no man’s land. Great.

I was glad of my chat with Chris for the mental preparation: on the far side of the lap, it dropped down a dip, and then rose back up to our starting position. At the start of the second lap, turning onto the main straight revealed a horrible headwind during the gentle ascent. I hadn’t noticed it first lap, probably through a combination of the pack ahead of me, and early-race adrenaline. The pack ahead of me started to break up, and runners fell back towards me. Each runner gave me a little target, but I knew it was still important for me to be disciplined and run my own race.

Consistent pacing was impossible with an undulating course and a steady headwind along the finishing straight. There was also the slight oddity that the dip on the other side of the course was slightly protected from the wind, and so felt quite hot under the sun – such variety in a 3 km loop! I concentrated on strong, consistent effort, albeit with a slight increase during the descent, figuring that it played to my strengths and was the least sapping part of the course to press a little harder.

I passed the halfway stage, 5 km, in around 20:30, which told me that a 41-ish finishing time was out of the window, and I immediately began readjusting my thoughts for something around 42, if I could hold on for that.

I never used to be too keen on multi-lap courses, or at least the idea of them. But touring around so many parkruns has got me used to the concept, and honestly, it was quite nice today. After the first lap, I was able to plan better, knowing where I would lose and gain time. Each kilometre marker I set myself a target time to reach the next marker, bearing in mind whether it was a faster or slower part of the course. I not only considered how quickly I thought I could cover that section, but also what that would leave me needing in the remainder of the race: ‘If I reach 8 km in 33 minutes, I have nine minutes to do that final two kilometres, that should be doable.’

I worked my way through the field, and entered the final lap fourth in the wave: the chap in first was way ahead, but both second and third seemed to be falling back towards me. I closed in on third and passed him through the dip, as we hit 8 km: 33:05. I started to push from here; normally 2 km would be a little too far out, but I knew that most of the last kilometre would just be about holding on into that headwind, so if I was going to make an impact, it was now.

I pressed as the course rose out of the dip and along the back straight, and ran that penultimate kilometre in 4:04, closing the gap significantly on the guy in second. I continued to close in as we rounded the bend onto the home straight, a roughly 600 metre stretch to the finish. I tucked in behind him to shield myself from the wind, hoping to draft for a while before moving out towards the end, depending on how our time was looking.

Even behind him, the wind felt horrible, but I also felt like I had more to give. The pace felt like it was slowing too much, and I stepped out from behind him. Oh, okay, that’s definitely worse. I tucked back in. We passed the ‘400 m to go’ board with just under two minutes in hand. That should be easy enough?!

I stepped out again, but again, I couldn’t make an impression, and tucked back in. We were both getting quicker now: whether he reacted to my move, or it was just the closing push, I don’t know. Either way, I felt pretty sure we’d make it in under 42 minutes. In the final 20-30 metres, I moved into a gentle sprint, as did he: maybe if we had genuinely been battling over second, I could have pushed for an all-out sprint and beaten him, but it didn’t really matter. He finished in 41:55, and I finished in 41:57, officially a nine-second PB.

Post-race

I grabbed my medal, and chatted to a few of the other finishers, during which we mostly commiserated each other on the wind. On the way home, I stopped for McDonalds at the very handy restaurant which is less than a mile from the race course: great post-race fuelling!

Forgive the poor quality – it’s a screenshot of my Instagram story…

I’m pretty chuffed with the effort. Although I ended up around a minute slower than my vague target, I think that on a flatter, less windy course, I would have easily achieved that. I ran strong, and with a consistent effort that I maintained to the finish. I ran the first lap in 12:25, the second in 13:00, and the third in 12:50; then it was just the horrible final drag to the end.

Now I’m just champing at the bit for an opportunity to prove that I can run faster, and finally beat the 10k distance PB that I set during the 2016 Great Bristol Half Marathon.

  • Did I enjoy this race? Yes, definitely.
  • Would I do this race again? Yes, probably.
  • What’s next? No idea. I’m signed up for The Big Cheese (which I ran before, back in 2017), but I might find something else before then. Or… a second wave might put an end to races for the year.

Wellington Monument Race: race report

by Ben

The last few months have been pretty quiet for me on the racing front. Way back in July and August, I ran the Pawlett Plod and the Wessex 10k, posting my third and fourth fastest 10k times. I had then hoped to run the Taunton 10k to set a new 10k PB. Unfortunately, I basically didn’t bother to put in the hard yards in training, and didn’t run Taunton at all. Since then, my training has continued to be inconsistent until a few weeks ago. And, although I have managed to improve my consistency, I am still lower on mileage than I would like to be.

Not ideal.

All that said and considered, the Wellington Monument Race was never going to be a PB attempt. It starts in Hemyock, roughly 128 metres above sea-level, and then climbs and climbs to Wellington Monument, the world’s tallest three-sided obelisk, about 272 metres above sea-level. Then we turn around, and go all the way back down (and up, a little). The monument is having some work done at the moment, so isn’t quite as picturesque as usual – this also had a slight knock-on effort on the race distance.

Wellington Monument vs Wellington Monument at the moment…

For some reason (probably mostly because it isn’t in the Somerset Series), this is a race that I’ve never done before, even though it is under half an hour from home. In fact, although Wellington Monument is in Somerset, Hemyock is in Devon – thankfully I wasn’t asked for my passport though. (They are funny, thems Devon folk.)

Pre-race

A local race meant a bit of a lie-in, although only until 8 am, as the race was a 10 am start. Originally Lolly was going to take Lani down to Exeter for junior parkrun, but Lani sensibly decided to have a morning off: they will be plenty of opportunities to parkrun over the next week or so! Despite the whole family now being free, I travelled down alone, and found a parking space in the village, just under half a mile from the start.

After making sure I had everything I needed from the car, and nothing much that I didn’t, I headed over to Hemyock Primary School, which hosted the race. It was all pretty easy and straightforward: number collected, pre-race poo, number pinned onto vest, warm-up run, hoodie stashed, jog to the start. During the jog to the start, I realised that I was a bit warm with a long-sleeve tee under my race vest, and found a fellow RFRC member who was spectating to abandon it with.

The race
Where’s Ben?

Compared to most of the races I do, this one attracted a fast field. I had noticed this when I checked the entry list the evening before, but it became even more obvious when I was waiting at the start. He’s quicker than me, he’s quicker than me, he’s definitely quicker than me… But this was never about time or position – for once I was just racing for the… uhmmm, fun(?)… of it.

The race started on a road junction about quarter of a mile away from the school, and then dropped down through the village… Ah, ‘dropped down’. In an out-and-back. Bummer dude. I had done minimal homework on this race – as far as I was aware it was an out-and-back in which the first half was uphill, and the second half downhill. With a short muddy stretch at the top around the Monument. Maybe I should have done more research – it was clearly a little more nuanced.

I mostly focused on trying not to run too fast, before the hill started. But then… blimey. Again, a lack of research meant that I didn’t realise that the first climb out out of Hemyock was the toughest part of the whole race. I survived that climb by using a common strategy: If no one else I can see is walking, then I don’t need to walk either… Around a mile and a half in, the course then descended gently for half a mile. Oh blimey, not again! Andy, who I used to run with regularly, was marshalling at this point and shouted some encouragement at me, but I was so zoned in on the run, and the effort, that I didn’t really notice who it was until it was too late to respond!

Actually, I think this is sort of bollocks, given that it isn’t really a mirror image: that bit near the end should be as low as the bit at the start. This Garmin elevation monitor thing obviously isn’t working great. But anyway, observe steep climb near the start.

The course climbed again after that short descent, but the hill was less vicious now, and was softened somewhat by the knowledge that there was less than a mile of ‘up’ left. A left turn was coned off and very well marshalled, and then we crossed the road into a muddy car park to make the last bit of the ascent to the monument. In all honesty, by this stage it was barely a climb at all. Because of the renovation work on the monument, we just rounded some cones and a marshal at the top, and then it was just back again!

The descent was relatively straightforward. On the top part of the hill, it was gentle enough to encourage without being too dramatic. The half-mile ‘climb’ where Andy was marshalling didn’t feel too bad; it was mostly just flat, rather than a hill either way. I even managed to thank him this time around, and apologise for not doing so on the way up!

After Andy’s marshalling spot though was the steep drop; the part that had been so horrible on the way up. I hoped that my downhill running would help me here, but in all honesty, the field was so spread by this point that it didn’t really make much difference. I went past one chap who looked like he was struggling with something, and I closed in on another runner, but as soon as the course levelled off I stopped gaining on him.

For me, this last part was the toughest of the whole race. Thankfully, someone had told me beforehand that the finish was at the school, and thus that extra quarter of a mile beyond the start line. It was a slog back up through the village, with more of a climb up to the school itself. In reality, it should have faded into insignificance in comparison to the main climb we had endured earlier in the race. But that isn’t how running works.

Still, despite having no one around me, I think I managed to push myself well enough to the finish. I did feel that the marshalling, which was so good all the way around the course, could have done with being a bit clearer, and more present, for that final climb. I naturally found myself on the pavement, only to be shouted at very late on that I needed to move onto the road, which left me dodging through a narrow gap between parked cars to do so. But that was probably just me.

I didn’t look at my watch when I crossed the finish line. In fact, I didn’t check my time until a few hours after the race. As I said, it wasn’t really that sort of race for me. However, I’m pretty chuffed with a 43:44. Roughly speaking, I ran 23:34 for the first half of the race and 20:10 for the second half. Which is pretty good, but also slightly disappointing that I didn’t manage to run sub-20 for the predominantly downhill 5k…

On the other hand, using Strava’s ‘grade-adjusted pace’, my 43:44 is equivalent to a 41:42 on a flat course, which would have been a PB, so, you know. Not so bad. In a fortnight I have the Stoke Stampede, which I ran way back in December 2013, my first ever sub-50 minute 10k. There would be a nice symmetry to it being my first sub-40, but there is no way I’m in that sort of form. But maybe, just maybe, I can get the PB I’m craving?

Post race

Immediately after the race, I had a chat in the school hall with Nadine, and then collected my cider from Emma. I ambled back through the village towards my car, but stopped to have a lengthy chinwag with Simon, before eventually I got too cold, and headed to my car. Did I mentioned that this race was very local, and so I knew a lot of the volunteers? The support, not just from those I knew, was exceptional throughout the race.

On my drive home, I stopped off for a foot-long Chicken Pizziola from Subway… because Subway is good post-race ‘recovery’ food.

  • Did I enjoy this race? Sort of. I mean, no. But yes.
  • Would I do this race again? Yes, probably.
  • What’s next? Race-wise, the Stoke Stampede on 5 January 2020, but there’s a Christmas Day parkrun and two New Years’ Day parkruns before then…

Wessex 10k: race report

by Ben

Right, how does this writing thing work? I’ve missed a few race reports; the last one I wrote was for the Town Tree Trail, back in May. Since then I’ve ran the Crewkerne 10k (abandoned draft blog post), Piddle Wood Plod, the Quantock Beast (another abandoned post), and the Pawlett Plod. As a quick summary:

  • Crewkerne 10k: pretty good
  • Piddle Wood Plod: meh
  • Quantock Beast: good
  • Pawlett Plod: felt not great, but pretty good actually

This race was the first part of my planned summer of speed, aiming to improve my 10k PB, and ideally set a sub-40 time. Unfortunately, after a good first half of my eight-week training ahead of this race, the wheels fell off somewhat, and I’ve barely done anything over the last four weeks. So, coming into this race, I didn’t really know what I’d be able to do. Sub-40 wasn’t going to be in the picture, but maybe I could still get a new 10k PB? To review, my planned targets are:

  • Gold: 39:59 (sub-40)
  • Silver: 41:23 (distance PB)
  • Bronze: 42:05 (race PB)
Pre-race
Ready to race

I chose the Wessex 10k because it described itself as “a fairly flat mainly road”. I had a look at some of the Strava traces from last year, and decided that the hill looked small enough that this could still be considered a decent PB route. The date also worked out quite nicely, and I seem to recall that it was priced relatively reasonably too. (Just checked, £16.) What I failed to notice until a couple of weeks before the race was that it was a 19:00 start time on the Saturday; I had spotted it was on a Saturday, but not that it was an evening race. This threw me off a little: I have it in my head that I don’t race so well in the evening, and I was just annoyed at not having noticed.

In the end though, being in the evening worked quite well; it meant that we still had all of the day on Saturday as a family, and would have on Sunday too (though I’m sat here writing this, so go figure.) I left just after five, which gave me lots of time to get to Somerton and then bimble around for plenty of time before the start. I didn’t have to worry about registration, as the race number had been sent out through the post. Just after half six I started my warm-up; I had intended to go for a longer warm-up, as I generally find them more effective, but it ended up being just over a mile, which is about my normal.

At around five to seven, we started to gather at the start line, and I got chatting to another chap on the start line, but it quickly became apparent that I wouldn’t be using him as a pacer; he was aiming for around 38 minutes! In the inaugural race in 2018, only six runners went sub-40, so I was half aware that there might not be too many ahead of me, and so lined up in the front row.

The race

I almost managed to not go off too fast. As I wasn’t too sure what time I would be capable of, I opted to aim for 41 minutes, and see what happened. That would equate to a time of 4:06 per kilometre. After the initial rush, I settled down to 3:55 for the first kilometre, which was pretty flat, heading out of the sports club, along the main road, and then hooked right onto the back-roads. It was obvious that there were more quick runners than in 2018, but that was to be expected for the second year of an event.

Shortly after the end of the first kilometre, we started to drop down the hill; this was the same one that we would return up later. And, well, it looked worse than I had hoped. In place of the gentle slope I had been expecting, or at least hoping for, was a genuine hill. Okay, no worries, I could make time up heading down the hill, and just see how well I could hold on up the hill in the second half. Downhill-assisted, the second kilometre clocked in at 3:45, and the third, still with a modest descent, was 3:58, leaving me 40 seconds up on an even-split 41:00 time. But of course, it wouldn’t be an even-split race, and I was aware that I could lose close to that same 40 seconds on the hill alone.

Any hopes of managing to make up more time, or at least hold steady were immediately dashed, as at the 3 km marker, we started on the rough stuff. A dusty, rocky, pot-holed farm track. This wasn’t part of my plan, and brought back memories of the Bridgwater 10k way back in 2014, when I destroyed myself chasing a PB on a course with a farm-track in the middle. Thankfully, I’m a bit more experienced now, but I was still losing time against my 41 minute target. Partly, this was probably just lack of fitness due to my reduced training lately, but the terrain clearly won’t have helped. Through the fourth and fifth kilometres, I clocked 4:13 and 4:19, taking me through five kilometres in 20:11; still theoretically 19 seconds up on my target, but in reality, starting to really struggle.

I’d developed an odd pain high on my chest; either my lung or a muscular pain, I couldn’t tell which. It was annoying without being debilitating, but I was very much hoping that it didn’t get worse. Just after the halfway stage, we had the only drinks station on the course, from which I took a quick swig, and then we returned to the road. I tried to get my legs turning over a bit quicker on the better surface, but to little avail; the next three kilometres came in at 4:36, 4:30, 4:30.

Not the best running form late in the race! (Credit: Martin Edwards)

Then the hill hit. It actually was not so bad as I had worried; I managed to run up the whole thing. That shouldn’t have been an achievement, but I’ve really struggled with hills this year for some reason, so I was pretty proud of it. The hill last for pretty much a whole kilometre, starting just before the 8 km marker in actual fact, and correspondingly, finished just before 9 km. It was by far my slowest kilometre of the race, a 4:54, but Strava’s grade-adjusted pace (GAP) was 4:25, which was quicker than my GAP for kilometres six and seven.

Over the top of the hill, and I knew I just had a kilometre to go. I willed my body to run faster, damn it! I managed it. Not consistently, but effectively; I oscillated between a 3:50 and 4:20 pace, and despite telling myself that I was now in energy-saving mode ahead of another race on Wednesday, I engaged in a sprint-finish when the runner behind me tried to get past. Helped by his push at the end, I ducked in just under 42 and a half minutes, officially posting a time of 42:28.

Post-race

After getting my breath back from my quick finish, I grabbed a cup of water, and then had another chat with the chap I’d been taking to before the race. After a quick analysis of each of our races, I commented that I noticed he was from 26.2 RRC (the best running club in Surbiton), made famous by Danny Norman on the With Me Now podcast. It turned out that I’d been chatting to none other than Chauffeur Ramek – what a small world it is! After some more parkrun chat, we headed off our different ways.

Shiny medal!

The medal was really nice; probably the second biggest in my collection, though I don’t really do the type of races that give big medals. (Because I’m cheap.) (Because I race so much that if I did expensive races, we would miss our mortgage payments.)

How about my time? It ranks as my fourth best 10k time; just behind my Pawlett Plod time from a few weeks ago:

  • 42:06, Chard Flyer, January 2017
  • 42:19, Battle of Sedgemoor 10k, August 2015
  • 42:23, Pawlett Plod, July 2019
  • 42:28, Wessex 10k, August 2019
  • 43:18, Round the Tor 10k, May 2016

That two of my quickest ever 10k times have come this year is encouraging. That my two overall quickest times are two and four years old respectively is disappointing. It’s another eight weeks now until the Taunton 10k, and if I want to get a new PB, then I simply have to put the training in. No excuses.

  • Did I enjoy this race? If I’m honest, not really. But that was no fault of the race, or the course. Sure, I’d have liked the hill to be flatter, and the rough track to be smoother. In reality though, I just wasn’t fit enough to run this race as I wanted.
  • Would I do this race again? Probably not, no. I signed up hoping that it was a good PB course, and it wasn’t really. If it was a Somerset Series race, I’d do it and enjoy it well enough, I’m sure. But as a standalone race, it probably won’t be for me again. Never say never though, I guess.
  • What’s next? The Haselbury Trail 10k on Wednesday.

Crewkerne 10k: race report

by Ben

TL:DR summary: Not my best day.

I ran the Crewkerne 10k previously in both 2015 and 2017. A truly undulating road course that departs Crewkerne and visits the villages of Merriott and Hinton St George before finishing back in Crewkerne (a bit further in than the start!) In 2015, I found the hills really tough, while in 2017, I was far more at ease, but a bit off the pace still after the birth of our second child.

This year, I looked on this as one of my favourite routes. The hills were rolling, but no individual hill is too bad, and I felt that it played to my strengths: achievable climbs and fun descents. On the day though, nothing really felt right. I woke up feeling overtired (a theme all week – possibly my 19.3 mile, 3,500 ft long run last Sunday was still working its way out of my system). I got to Crewkerne and found the warm-up tough. It was pretty warm – not so crazy hot as the London Marathoners had it this year, but plenty hot enough. According to Garmin, it was 13.9°C in both 2015 and 2017, while this year it reckoned 20°C.

Now that I’ve got all my excuses lined up early, let’s cut to the crux of the matter. I started too fast. A fair bit too fast. I had looked at my splits from last year, reckoning that I was in similar shape (not thinking about the heat), and had seen that the first couple of miles came in just under seven-minute miles. Forgetting that the fact that the first mile has a climb followed by a long descent would mean that my time would improve throughout that mile, I pushed myself too hard around half a mile in to up my pace. My attempt to aim for a 6:55 mile resulted in a 6:40 mile. Sigh.

Unfortunately, this error was compounded by the fact that I didn’t even notice I’d done it. By the time I glanced down at my watch after passing the mile, it was showing a time in the early seven minutes, and I assumed I’d clocked through at about what I’d expected. A 6:40 pace might not sound too extreme, but Strava made it a 6:10 grade-adjusted pace, which definitely wasn’t going to be sustainable. My second mile of 6:57 was much closer to what I should have been running, but felt awful, as runners seemed to stream past me.

I set four Strava segment PRs during this race, despite being slower than last year. Three of them were within the first four kilometres of the race. I was a little surprised to find that one of these segment records came during the climb through Merriott. On reflection I guess it makes sense – both times previously, I’d felt like I was cruising this section, whereas this year it felt like a slog. I’d assumed it was because I was struggling, but in fact, it looks like it was because I was going too fast and pushing myself too hard.

By mile four, my pace was definitely taking a downturn though. I was really suffering from the heat. I’d trialled running with a cap to protect against the sun, and although it was working well from that point of view, it was just a normal cap, rather than a running one, and it was too thick. I eventually (around mile 5) gave up and took it off, but the damage was done by then. Matt Powell from Burnham (@no1mattpowell) was chasing me down, and although I managed to keep him behind for a time, I crashed on the final hill climb and had to walk, letting him through. Looking now, he had a brilliant finish anyway, so it seems unlikely I’d managed to stick with him even if I hadn’t been forced to walk.

Great honeymoon souvenir. Sub-standard running cap.

Somehow, I managed to set a PR on the “One Last Push” segment near the end of the race, but it didn’t really reflect how I was doing at that stage. I managed to sneak in sub-45, timed as 44:44 by my Garmin, 40 seconds slower than last year.

Next up, next weekend, is the Piddle Wood Plod 10k.

Snowdonia Trail Marathon: Week 2

by Ben

After a pretty positive week one, despite not hitting 30 miles, I was looking forward to getting some more miles under my belt in week two. The P&D plan introduced some strides into a general aerobic run on the Tuesday, before a midweek 10 miler on Thursday. With my lower mileages at the moment, the latter was never going to happen, but I was keen to try and incorporate the strides into my running.

Tuesday: 7-ish planned. 0 completed.

As Lolly was travelling away with work, and would be away Tuesday and Wednesday evening, I had to either run early Tuesday morning, or fit my run into my workday. I chose the latter: I planned something like a seven mile route based around Brean Down, which I could do after my first job in Weston-super-Mare. Unfortunately, I ended up coming straight home after that job, as we got a call from nursery to say that our little boy had to see a doctor. As it turned out, he was fine, and went back to nursery that afternoon. But my planned run had been ruined.

At this point, I got into my own head. It was still only 13:00. I could easily fit in a run; more or less any run I wanted. I didn’t have to pick the children up from nursery until 17:30. But for some reason, I just couldn’t quite get myself out the door. After my planned route, I decided that anything from home would be too boring. Fine – that shouldn’t be a problem, a 15-20 minute drive can get me to some gorgeous places. But no. Alas, I couldn’t get over myself, and I didn’t run at all.

Wednesday: Tuesday’s run (8 miles)

It’s not trail running, but it’s still scenic enough.

Not running on Tuesday put a lot of pressure on me for Wednesday. If I didn’t manage to get out for a run, then it was unlikely I was going to be able to match the previous week’s mileage, and my main aim, for the first four weeks of the plan, was consistency. Thankfully, I managed to finish work around three, and had none of the previous day’s head issues. I got home, changed and went straight back out for a run along some of the roads at the base of the Quantocks. The route was loosely based on a reverse part of The Humdinger course. Although it was road mileage, it was pretty lumpy and, with the snow around, simply pretty. I averaged just slower than 8:30 per mile, which I was pretty happy with, considering the terrain, and that I wasn’t pushing myself.

Thursday: Getting out on the river (5 miles)

There’s a huge cliche about the first light evening runs, but they are genuinely so uplifting. I managed to use the last bit of light to start my run along the river, before ducking off around some residential estates to get back home. Like the previous day, I was pleased with the pace given that I never really pushed myself. It was a pretty modest 8:12 per mile average, but after so much time on the trails, I’ve got used to paces in the 9s, 10s and even slower. As I mention above, my focus at the moment is on consistent running; getting the miles done week after week, and building to a decent platform. Once at that platform, I’ll switch my focus more to pace. Trying to build mileage and pace at the same time is just a recipe for injury.

Saturday: Longrun Meadow parkrun (5 miles inc run there and home)

Splash splash.

It’s been ages since I’ve run at Longrun Meadow. Over three months in fact. The underfoot conditions were pretty bad, though far from the worse that I’ve run in there. As I was racing the next day, I was intending a relatively gentle run, though ended up going a bit quicker than expected as I ran with a mate. It was good to be back and to socialise with a few people I hadn’t seen for a while. It’s also a pretty (mentally) easy way to get five miles in.

I’ve got out of the habit of parkrun – partly because I was injured for so long, partly because when I was training before it didn’t fit in very well, and partly because I have given Lolly priority for parkruns lately. It’s a habit I’d like to get back into, even if I can’t make it every week these days. I ran 38 parkruns in 2014, 20 in 2015, 36 in 2016 and 18 in 2017. Based on these numbers, I’m due for 34 this year, though that seems unlikely so far!

Sunday: Race day (11.5 miles total)

Climbing through Butleigh Wood.

For a full race report, see my previous post. While the race was important to me, namely for Somerset Series points, I also needed to make sure to top my mileage for the day up to 10 or 11 miles. A one mile warm-up was followed by the Butleigh 10k. The race went pretty well; I was more or less where I expected to be, though I’d have liked to be 30 seconds to a minute quicker. (Always).

Race done, I caught my breath and chatted for a while, before switching from my race vest into a t-shirt, and my trail shoes into road shoes, and then headed off for another four miles. I opted for a simple two miles out, two miles back route, rather than trying anything fancy and getting lost! I found the miles came surprisingly easy, and although I was a bit bored of the flat roads by the end, it was a pretty nice end to a higher mileage day.

Weekly summary: 4 runs, 29.9 miles

So, yeah… If I’d known I was that close to 30 miles, I’d have cleared tacked another 0.1 miles onto my run. But never mind. Overall I’m happy with what I got done this week. I struggled early on, but in the end, I built the mileage nicely from last week, and the race went about as well as I could realistically expect given the current focus of my training. It’d be nice to get out on the trails a bit more, but sometimes life just gets in the way. More races are due to follow next week, with the Isle of Man Easter Festival of Running; a 10k on Good Friday and then a 3.5 mile hill race on the Saturday.

Babcary 7.5: race report

by Ben

The second part of my weekend back-to-back, after completing leg one of the Hills to Coast Relay with Minehead RC the day before. This was also my second visit to the Babcary 7.5 mile road race, which I also ran last year.

This race, like all of those in the Somerset Series, was pencilled into my diary as soon as I knew the date. It’s a bit of an oddity of a race – 7.5 miles is hardly a normal race distance, and the profile of this course means that it isn’t particularly quick either. But that is part of the joy of this race – it’s challenging no matter what.

No matter where they take us, We’ll find our own way back. (Well, actually we’ll follow the hi-vis arrows and marshals…)

My legs – nay, my whole body – was feeling pretty rundown after the relay on Saturday. Apparently 1,000 ft over 10 km in just under 54 minutes isn’t brushed off too easily. That said, I wanted to run 10 miles on Sunday in terms of progression for The Big Cheese race in a few weeks, and also in preparation for my upcoming marathon training for the Snowdonia Trail Marathon. Bizarrely, running a 7.5 mile race, and topping the mileage up with a warm-up and cool down seemed a preferential option to 10 easy miles on my own.

Generally, my preparation for this race was awful. Not just the fact I’d raced the day before, but also the fact that at 9:15 I still hadn’t really started packing. The race was about 35 minutes away, and on-the-day entries officially closed at 10:30. I also had no fuel in my car and no cash to actually pay for entry….

After some rather rushed packing, I was off. Via a cash machine and a petrol station. About halfway there, I was getting confused; my sat nav was trying to send me an odd route, and I was getting concerned that maybe a road was closed ahead. I pulled over, and realised that I’d written down the wrong postcode. A quick search on Strava for last year’s activity, and I simply put the street name into the sat nav, et voilà!

So, about that rushed packing. When I arrived, I found I was missing my running socks. And my Garmin. Thankfully, I was wearing socks, so I just had to give my Fozzy Bear socks their running debut. The Garmin situation was also averted, as I had my FlipBelt with me, so was able to pop my phone into that with Strava tracking the run. Because after all…

The Race

My race strategy was much as at the relay the day before, and at this event last year. It was nothing special: ‘take it easy early, get a feel for your capabilities, see what you can do later’. Largely, I think I managed to stick to the plan. I held back on the initial climb, and then allowed a few runners that I’d normally run with slip away ahead of me. I was a little concerned that Graham, my usual Somerset Series sparring partner was still near me, but the positions of everyone else told me I was about right.

The whole race undulates – although none of the climbs are particularly tough, it is non-stop. Uphill, downhill, uphill, downhill, uphill… you get the idea. My first two miles were significantly down in pace compared to last year, dropping about a minute between the two. Shortly after this, on the climb that started at around 2.5 miles, my legs started to feel pretty wiped. I’d dropped back from Graham and another Wells City Harrier, while a third was now running with me, having caught me around the two mile marker.

As I spent the next half mile climbing that particular hill, I was starting to seriously doubt the wisdom of racing two days in a row after a six month absence. While I was never in danger of dropping out of the race, I did worry that I might embarrass myself by falling like a rock through the field. However, as hard as it felt, I found that I wasn’t really dropping back from the group in front, nor were those behind closing the gap. I settled in, and remembered that racing never feels easy. It’s kind of the point.

I lost another couple of minutes compared to last year over the undulations of the middle few miles. As we ran through one village, I had a little faux race with one of the spectators, who looked to be coming out of her garden to stand with some friends. It was a nice little mental break from the race, though it only lasted a few metres! Otherwise, there was little to mark these middle miles – I went up some hills, down some hills, passed some barns. You get the idea.

Interestingly, my pace over miles six and seven was actually very close to last year; 7:20 and 7:08 this year, compared with 7:12 and 7:08 last. Finally it seems that my efforts to take it easy early in a race actually came to some fruition. The final half mile is the reverse of the start, and drops back down hill. With no one forty yards either side of me, I didn’t push too hard, but kept a decent pace that removed any real possibility of me being overtaken. Last year, I had a sprint finish with Graham which saw me peak at about 4:45/mile. This year, after easing my pace up to 5:50/mile down the hill, I slowed back down to cross the finish line. Twentieth overall, and eighteenth male, is a solid finish for me in terms of the Somerset Series; in each of the last two years I’ve averaged around 21 to 22 per race.

After a mile and a half cool down (mileage top-up) I was done. My two-race weekend was concluded. I grabbed some lunch from Burger King just down the road, and headed back. This morning (Monday) I had some serious DOMS. But now, this evening, it seems okay. And I seem to have planned a 2,000 ft run for tomorrow…

A race report catch-up: part three

by Ben

This is the third and final instalment of my race report catch ups, going through all the races that I’ve done in the past few months, most of which I didn’t manage to get around to writing up at the time as I was too busy doing other things.

  • Part one: Butleigh MT 10k, Yeovilton 5k (May), Wambrook Waddle 10k, Crewkerne 10k
  • Part two: Red Bull Steeplechase

<dramatic voiceover> And now… the conclusion. </>

Quantock Beast – 2 July

This was the third year in a row that I took on this race, put on by the local Quantock Harriers, and only a few miles up the road.

The race came just a couple of weeks after the Red Bull Steeplechase, and off the back of a not great week of running. I ran 8 x 200 metre repeats on the Tuesday evening, and I think it wiped me out – I was using a football pitch to estimate the distance, and I think I ended up doing too far, too fast. The following night I wiped out during our club run, and just felt completely drained. I didn’t run again before the race – so I was a little concerned about how it would go.

As usual, we had a good club turnout for this race, and we were especially we represented near the front of the race: Iain, Tim and Andy all run with group 1, although I hoped that on a hilly, off-road course I might be able to challenge Andy.

The race begins with a fast road descent that lasts just over a kilometre, and despite feeling like I was taking it easy, I ended up being six seconds quicker than last year. I continued to be significantly quicker over the next kilometre, although the drier weather might have something to do with that, as the second kilometre moved off-road and climbed gently uphill. I stayed in touch with Andy through these early sections, and as the course dropped to a steep downhill, I was able to pass him, though he got straight past me again as we climbed back up the hill.

After a couple more little lumps, this climb settled into the big one, almost a mile and a half long. Although it is rarely too steep, the climb is sapping, and I struggled a bit with it. I can’t really put my finger on why I didn’t do too well on it: there is a Strava segment for the hill, and my best time remains that from 2014. I’ve done lots of hill training since then, so logically I should be significantly better at it, but last year I was almost two minutes slower, and even this year I was about 30 seconds off the pace. I can only put it down to a ‘longer race mentality’ which means I’m taking more walking breaks than I did before. Maybe. Looking at Strava, I was massively slower at the bottom of the hill this time (7:32 km compared to 6:38) while I pretty much the same towards the top. This definitely suggests I started walking earlier and more. Something to consider for future shorter races with hills!

Anyway, over that hill I just had the long road descent back to the start/finish. I could still see Andy ahead, and hoped that I might catch up down the hill, but he (and everyone else) maintained their pace far more than I remembered in previous years. Despite running this final section quicker than I’d managed before, I was actually caught during it, though I managed to time my sprint finish better to beat him to the finish line.

I was generally disappointed with this race – it should have played to my strengths, but for whatever reason I just didn’t seem to be quite there on the day. On reflection I guess that given how I was earlier in the week, along with everything else going on, meant that it was actually a decent performance. It just didn’t really feel much like that at the time.

Yeovilton 5k – 12 July

After my first Yeovilton appearance of the summer, I wanted to set things straight a little with this race. My actual time in May hadn’t been awful (considering), but my pacing had shown how poorly my head had adapted to a slowing in my pace. After running the first two kilometres at 3:57/km, I then dropped off dramatically, running the final two kilometres at 4:24/km to finish in 20:48. So this time around, I wanted to be a bit more realistic.

I was boosted somewhat by this being a Somerset Series race, which meant the field was a bit bigger, but most importantly, there were more recognisable figures. Most significantly, the chap who I’d just pipped to the finish at the Quantock Beast was there, and we ended up running most of the race together, along with a couple of other familiar figures. This meant that although I was a little concerned with my quick early kilometres; 3:52, 3:53, I didn’t have to worry too much about the numbers as I was around people I considered my peers.

In fact, it worked out pretty nicely. After the quick start, we then dropped to almost dead-on 20 minute pacing, running the last three kilometres in 4:00, 4:02, 4:03 (though that last one was only due to a sprint at the end). I finished in 19:46, a little quicker than this race last year, but most importantly, back under 20 minutes. It’s a silly little thing, but in my head, I’m a sub-20 minute 5k runner, and until I’d got back to actually doing that, I just felt a bit out-of-place, almost a fraud. It also meant that I could see everything was coming back in the right direction, which was a huge boost.

Haselbury Trail 10k – 2 August

Another race that I’ve done a couple of times before.

I had a good few weeks between the Quantock Beast/Yeovilton races in early July until the Haselbury Trail at the start of August, and I clocked up the training miles, including a few decent speed workouts. Haselbury was well timed after a recovery week as well, meaning that I went into it feeling the best I had been for a while. We had a surprisingly good club turnout again at this race, especially considering the awful weather – it had been raining all day long, and that didn’t stop in the evening. For me, this was great – the Quantock Beast had been too dry for my liking, so I was looking forward to a wetter off-road race!

Again, there were all the familiar Somerset Series regulars (well, minus the two Matts, one of whom has been injured most the year, and the other of whom has just had a baby). My previous two visits to this race finished with near identical times; 47:08 and 47:07, though conditions had differed significantly between the years, making the 2015 time the more impressive. This year’s conditions were definitely more akin to 2015!

Unsurprisingly for similar overall times, my splits were similar in places too: both years started with 4:01, 4:20, 4:52 kilometres (give or take a second). Both years, my race report talked about having gone off too fast, and needing to rein it in. Which I sort of managed this year – my opening kilometre was 4:11, though I then ran 4:18 for the second and 4:45 for the third. Those good at arithmetic will notice that as a result, my first three kilometres were actually therefore more or less done in exactly the same time in 2017 as the two years before…

But despite the similar overall time, I think the specific kilometre splits made a difference. I didn’t destroy my legs so much with an over-fast sprint start, and I think I’m in better shape anyway than the previous two years. By the end of the third kilometre, I’d settled in behind Graham, figuring that given our recent relative results, I didn’t want to get ahead of him. However, the pair of us were stuck behind another runner who seemed to be struggling on the slippier off-road sections, and when Graham didn’t pass him on a wider section, I opted to pass them both, backing myself to manage my own pace. As it happened, Graham must have passed him soon after, and was back on my heels by the end of the fourth kilometre.

Shortly after came the first climb of the “Horrible Hill” (to quote the Strava segment). I was fully expecting to lose ground here – in previous years I had been passed on the hill, and after my Quantock Beast experience I had no reason to think it would change this year. But amazingly, not only did I not lose any positions, but I actually gained time on those around me. Admittedly, I was probably a little bit slow to speed back up again on the level, but still! As we came around to begin our second lap, there were a group of four of us, strung out a little; a runner from Maiden Newton, a chap in a triathlon club top, me and Graham. The pace was being pushed by the two runners I didn’t know, particularly the triathlete, though I was a little confused at his variations in pace. Sometimes he was sprinting along, easily passing me, but then at others, I cruised up to pass him.

Although I made some decent pace down the hill to start the lap once more, I decided not to push along with the other two initially, but temper my pace closer to Graham’s once more. As the lap continued though, I kept swapping positions with the triathlete, and I soon worked out it was because he had road shoes on. On the more solid terrain, he was much quicker than me, but when we were on the slippier sections, I had the edge. Coming back around to the hill at the end of the lap, he was slightly ahead of me, but really struggled in the mud that had been ground up at the bottom of the hill. In trying to go around him, I ended up more or less running into him as he slipped around, but I pushed myself hard up the hill, and over the last section of off-road terrain. I knew that my only chance to keep ahead of him was to have a decent gap before we got back on the road.

My hard work paid off, and I retained my position to the end; the group of four of us that had started the lap together ended up finishing within 1:10 of each other, having gained a couple of positions past some struggling runners. I was very happy with finishing 22nd, especially doing so ahead of Graham.

A race report catch-up: part one

by Ben

So, it would be fair to say that I’ve got out of the habit of updating the blog with my race reports. Well, to be honest, I’ve just stopped writing pretty much anything on it. Which is annoying, as reading my blog reports from previous years is one of my most effective pre-race preparations. This year I’ve raced 11 times, and yet I’ve only put up 4 race reports. Now two of those were Yeovilton 5k races, which I don’t tend to write up properly, but that still leaves five whole races unrecorded.

With this in mind, I’m going to try and summarise my thoughts on each, going back over some short notes I made at the time and the Strava report.

Butleigh MT 10k – 19 March

This was another “new to me” Somerset Series race for 2017. It used to be 7 miles, but this year they dropped it down to 10k. Unfortunately, to make it this distance, the race had to loop some fields at the start and end of the course, which wasn’t great – I’m not convinced that it is important enough to make a race 10k that this looping was needed. But whatever.

I probably, definitely started the race too fast on the initial lap of the field, but wanted to make sure I was in a decent position to avoid having to wait to cross the stile out of the field, which became something of a bottleneck for those behind. We then entered another field (there were lots of the them) which was extremely boggy. Everyone was taking different lines, trying to find some firm ground, but there simply wasn’t any. I ended up tight against the fence on the right-hand side, which I’d initially worried was electric, but it turned out not to be!

At the end of this field, the course rose up towards the road, though we didn’t actually run on the road, but through the trees alongside it. This was apparently the local fly-tipping area too, which a range of furniture and tyres on offer. It wasn’t great terrain to run on, but thankfully I was following another runner, so was able to keep track of the track, so to speak. We dropped back downhill into the fields after this section, and were helpfully warned by the marshal “Careful as you go, very slippy.”

Pack running

He was right – I slipped over. Thankfully it was all just mud, so no harm done, and I barely even lost any time on those I could see ahead of me. I picked up the pace a bit down the hill, but a little more cautiously than normal after my fall. After a short stint back on the road, we turned off it again and up hill. I was passed by another Series regular, Graham, (no surprise there) as we climbed up, but I went back past him once we headed downhill again. For most of the last two miles, four of us ran close together, our positions switching around a few times.

Graham’s course knowledge helped a couple of times, but I was leading the group coming into the last mile. Until the bloody “main” road crossing, when I got held up by a car passing, and the group caught back up to me again!

After a few more twists and turns (and the bloody pointless lap of the field) I finished in a reasonable (given the course and conditions) 48:01. More importantly, I was around, or ahead of, those I considered competitors in the Series.

Yeovilton 5k – 10 May

After Butleigh, I had a couple more weeks of good running before illness (a sinus infection) and the arrival of my new son stymied my running for a while. I skipped the April edition of the Yeovilton 5k Series, and returned in May. My hope was for a time around 20:15. Last year I peaked at 19:13 in September, but I was obviously going to be well short of that. Rightly or wrongly (the latter) I headed out at sub-20 minute pace, ticking off 3:56 and 3:58 for the first two kilometres. Then the wheels fell off; 4:12 for the third kilometre followed by 4:25 and 4:22. My body had just given up on me, though I shouldn’t have been surprised. I finished in 20:48, more or less equivalent to my time at this race in May last year, when I ran 20:44. So, if nothing else, I knew I was in roughly the same place, and so could improve back to the same place as last year.

Wambrook Waddle 10k – 14 May

Lani probably had as much fun as I did at this one!

This race came on the Sunday following the Yeovilton race, and so I was feeling a mixture of disheartened by the 5k result, and confident that hopefully if I had more or less matched my 2016 5k performance, I could more or less match my 2016 Waddle performance. Which I guess I more or less did. I opted to follow the Nigel Baker Race Start TacticTM, which I admit probably isn’t the best long-term plan. It essentially involves doing a race with a downhill start, and then absolutely pegging it down the hill. It was great fun. It probably killed my legs. Unsurprisingly, I lost a lot of places on the subsequent uphill, though I had plenty of fun dropping back down it again after.

In essence, this race was categorised by me not really being mentally prepared for racing in the Somerset Series “lower down the pack”. I saw those that I had previously raced around, but they were way ahead of me, and it was difficult to deal with. I probably had a reasonable race considering my fitness levels, but it just felt like a bit of a fail. But if there is anywhere to do that, it’s the Wambrook Waddle, which remains a gem of a course – impossibly hard for a race that is only 10 kilometres long (though in fact, most of the work is done in the first 5k, it’s just that your legs are completely shot for the second half.) Again, my race time was more or less equivalent to what I ran in 2016 (about 20 seconds slower.)

Wells 10k – 28 May

I did actually do a full write-up on this race, which you can find here: Wells 10k: race report. In summary; felt tough, but managed to equal last year’s time.

Crewkerne 10k – 4 June

This was the final of the more or less back-to-back-to-back Somerset Series races, which featured three 10k events in four weeks. This was a return to a race that I last did in 2015, when I found it really, really tough. The race starts with a steep hill climb, then drops down just as steeply, and then undulates until it loops back around to do that hill in reverse once again. When I did this race in 2015, I’d done about 1,800 ft of elevation so far that year. This time, I’d done 17,300 ft. It’s fair to say that I’m a bit better prepared for hills these days. In fact, the whole race only has about 500 ft of climbing, which isn’t unusual for Somerset Series races.

My time of 44:03 was almost identical to my Wells time of 44:02 the week before, and gave me a lot more confidence. For whatever reason, I just felt strong on the hills, and quick on the descents. Sure, I was still a distance back from the pack of runners I felt I should be with – I could see them for most of the first half of the race before they got too far ahead of me. But I’d come to terms with that now, and knew that I was running for myself, and working my way back to where I had been. Even if I wasn’t there yet.

Right, that’s enough for the moment. I’ll follow this up with part two later on; another go at the Red Bull Steeplechase, the Quantock Beast and my second Yeovilton 5k of the year.