When the Marathon Fights Back Loch Ness Marathon 2026 Race Report
Some marathons unfold exactly as planned. Loch Ness Marathon 2026 was not one of them.
It had the controlled start I wanted. It had a long middle section where I felt locked in. It also had a stretch late in the race where the plan cracked, the pace slipped, and the marathon reminded me that 26.2 miles is never just a fitness test.
This is my Loch Ness Marathon race report, but it is also a reflection on marathon pacing, effort, fatigue, and what running a marathon teaches you when the numbers stop looking neat.
Because that is where the real lesson was for me. Not in the miles that felt smooth, but in the miles where I had to respond.
The opening miles felt controlled
The first mile came in at 9:04 per mile, with my heart rate sitting at 134 bpm. On paper, that looks calm, and physically it felt that way too. I was not forcing the pace. I was trying to settle, stay patient, and avoid the classic marathon mistake of treating early comfort as permission to push.
The next few miles sat mostly between 9:00 and 9:50 per mile. That range might look a little uneven if you only glance at the splits, but Loch Ness is not a flat city marathon. The course gives you downhills followed by spikey up hill running early on, and hilly pace can be deceptive.
This is where pace alone can lie to you.
A faster mile on a downhill section does not always mean you are working harder. By the same logic, a slower mile on a climb does not always mean you are falling apart. That is why I kept coming back to effort. Grade Adjusted Pace attempts to show what the pace might be worth on flat ground, taking the terrain into account.
It is not perfect, but it is useful. On a hilly marathon course, effort matters more than the exact number on the watch.
Early downhill miles can also be a trap. They feel free, but they are not always free. The legs still absorb the impact. The quads still take a huge load. The nervous system still has to stabilise every stride. You can run downhill too aggressively and pay for it much later, even if your breathing felt easy at the time.
That was in my head during the opening miles. Stay relaxed. Do not chase. Let the course come to me.
Finding rhythm from mile 7 to mile 18
From around mile 7, the race began to settle into something that felt strong. This was the best section of the day.
Most miles through to mile 18 came in around 8:30 to 9:20 per mile. There were a few miles that stood out:
Mile | Pace |
9 | 8:29 per mile |
10 | 8:44 per mile |
14 | 8:43 per mile |
16 | 8:56 per mile |
18 | 9:21 per mile |
These were not wild surges. They felt like I had found a proper marathon rhythm. The kind where the body and the course briefly agree with each other.
Mile 9 at 8:29 was one of the quicker miles of the race. Mile 10 followed at 8:44, and I still felt composed. Later, miles 14 and 16 came in at 8:43 and 8:56, which gave me confidence that I was moving well deep into the middle of the race.
But the heart rate told a fuller story.
Through this section, my heart rate gradually climbed into the high 170s and low 180s. The pace was relatively stable, but the cost of holding that pace was rising.
That is one of the most honest parts of marathon running. You can be doing the same thing externally while your body is working harder internally. Same pace, higher heart rate. Same stride, more effort. Same plan, more negotiation.
This is often described as cardiac drift. In simple terms, heart rate can rise over time even when pace stays steady. Heat, hydration, fatigue, fuelling, terrain, stress, and normal marathon effort can all play a part. The watch does not tell the whole story, but it gives clues.
By the middle of the Loch Ness Marathon 2026, the clues were clear. I was still running well, but the race was becoming more expensive.
Pace and effort were not the same thing
This race reminded me that marathon pacing is not just about hitting numbers. It is about understanding what those numbers are costing.
A pace can look sensible but feel too hard. A pace can look slow but be the right call on the day. A mile split is a result, not a full explanation.
On a course like Loch Ness, that matters even more. Terrain changes the meaning of pace. Downhill running can make you look brilliant early. Rolling sections can make steady running feel less steady than the watch suggests. Small climbs can ask questions that do not show up clearly unless you look at heart rate, effort, and how your legs feel.
For anyone thinking about marathon training, this is the big lesson I would take from the data:
Do not train yourself to obey pace at all costs. Train yourself to understand effort.
Pace is useful. I love having the numbers. They help build discipline and give structure to the day. But the marathon does not care what pace you wrote down in your plan. It responds to terrain, weather, fuelling, fatigue, and the condition you brought to the start line.
That is why I would rather be a runner who can adapt than a runner who can only follow a "perfect" script.
The race changed around mile 19
The turning point came around mile 19.
Mile 18 was 9:21 per mile, which still looked within the range of a solid day. Then mile 19 dropped to 10:31. Mile 20 was the real shift: 13:36.
That was the point where the race stopped being smooth.
Miles 20 to 22 were difficult:
Mile | Pace |
20 | 13:36 per mile |
21 | 13:11 per mile |
22 | 12:56 per mile |
It would be easy to look at those splits and try to create one neat explanation. But I do not think that would be honest.
The data shows what happened. It does not prove exactly why.
It could have been accumulated fatigue. It could have been the earlier downhill load catching up with my legs. It could have been fuelling, terrain, pacing, muscular fatigue, or a mix of all of them. In a marathon, it is rarely one thing. More often, several small costs add up until the body demands a conversation.
And that conversation is rarely polite.
This phase felt like the marathon pushing back. The confidence of the middle miles disappeared. The rhythm broke. The gap between what I wanted to run and what I could run widened quickly.
That is a hard place to be mentally. You start doing maths you do not want to do. Most question decisions from ten miles earlier. You wonder whether this is the start of a long, ugly slide to the finish.
For me, this was the part of the race that mattered most.
Not because it was fast. It was not.
Because it asked me to stay involved.
Responding instead of surrendering
The most important split in the race might have been mile 23.
After miles of 13:36, 13:11, and 12:56, I managed to bring mile 23 back to 9:13 per mile.
That did not erase the difficult section. It did not magically put the whole race back on the original plan. But it proved something to me in the moment.
I had not given up ownership of the race.
That is a different kind of win. It is not as clean as a perfectly paced negative split. It will not look as tidy on Strava. But it matters.
There is a mental danger when a marathon starts going wrong. You can let one bad mile become the story of the whole day. Then one bad mile becomes three. Then the race becomes something that is happening to you, rather than something you are still taking part in.
Getting back to 9:13 for mile 23 was a reminder that even when a race breaks, it does not have to stay broken in the same way.
I had another difficult final section after that. The finish did not suddenly become easy. But by then the task had changed. It was no longer about protecting the perfect plan. It was about managing the reality of the race I was actually in.
That is a skill. It is part of marathon running, and it is part of life outside running too.
The final stretch still had something left
The final 0.16 miles came in at roughly 7:42 per mile, with my heart rate reaching 185 bpm.
I always find those final scraps of pace strange. You can feel completely emptied out, then still find something when the finish line is close enough to believe in.
It does not mean you had loads left. It means the brain and body can sometimes access effort differently when the end becomes real. The same legs that were struggling earlier can suddenly respond for a short burst, not because the fatigue has gone, but because the demand has changed.
That finishing kick mattered to me. Not because it transformed the result, but because it showed I was still competing with myself. Still asking. Still willing.
This was not a perfect race. It was not the clean execution every runner dreams of. It was not the kind of day where every split lines up and the finish time tells a simple story.
But it was a real marathon.
And real marathons are rarely tidy.
What this Loch Ness Marathon taught me
I came away from the Loch Ness Marathon with more than a finish time or a Personal Best.
I came away with a clearer understanding of how fragile pacing can be on a hilly course. I came away with respect for how much early downhill running can cost later. I came away with another reminder that heart rate can drift even when pace looks steady, and that the body is always keeping score.
Most of all, I came away with a deeper respect for adaptability.
A Marathon Personal Best is alway nice. Every runner understands that pull. We train, plan, taper, and imagine the day where everything clicks. But if the only measure of a marathon is whether it followed the dream version, we miss half the value of the experience.
This race gave me lessons I can use.
For my next marathon, I would take these forward:
Be even more patient on early sections.
Watch heart rate trends without panicking over single-mile changes.
Practise fuelling and late-race effort in training.
Prepare mentally for the moment when the plan needs adjusting.
That last point might be the biggest one.
Marathon recovery is not just physical. Yes, the legs need time. The body needs rest. But the mind also needs space to make sense of the race. To separate emotion from information. To see the hard miles as feedback rather than failure.
What I will carry into the next marathon
When I look back at Loch Ness Marathon 2026, I do not want to judge it only by the finishing time.
The splits tell a better story than that. They show a controlled start, a strong middle, a hard collapse in pace, a response, another struggle, and a final push. That is not the perfect marathon script, but it is an honest one.
I learned that fitness gets you to the start line with belief. Pacing gives you a plan. Training gives you tools. But resilience decides what happens when the race stops matching the plan.
That is what I will carry into the next one.
Not just the need to run smarter, fuel better, and respect the course. I will carry the memory of mile 23, when the race had already gone wrong and I still found a way to respond.
Because a marathon is not only defined by the miles where everything feels good. Sometimes it is defined by the miles where it does not, and by what you choose to do next.
Comments