Salisbury Plain 50-Mile Ultra: Why I Stopped at Mile 32

In spring/summer 2023 I entered a 50-mile event on Salisbury Plain as part of an attempt to return to long-distance running. I reached roughly mile 32 and stopped. I did not finish the planned 50 miles. That is the starting point for this story, because a race account should not make you read to the end to discover that its headline distance was an ambition rather than a result.

My recollection contains grass paths, unexpectedly deep water, hot exposed weather, difficult hills and cows. It also contains a line that I still want to keep: “It was a success even if I didn't get to finish it”. That was my reflection on the attempt, not an alternative classification of the result. Both statements can be true: I valued being there, and I did not complete the course.

Returning to distance, without borrowing a finish

Entering a long event gives an intention a shape. In this case that shape was fifty miles across Salisbury Plain. The distance on the entry was what I hoped to cover, not something already earned. My 2023 manuscript describes an attempt to return to long-distance running, and that is how I understand this chapter now: getting back into the experience, then encountering its limits on an actual course.

I have written about other steps beyond marathon distance in my earlier ultramarathon preparation account. That is a separate experience, not a training log for this event. Bringing the stories together helps explain the longer running journey, but it would be misleading to blend their details into one continuous, perfectly documented programme.

The instructions before the landscape

Before the race, the organiser supplied instructions covering route maps, the requirements of a cupless event and reminders about sharing military training land. Those details are part of the preparation I remember. A fifty-mile entry is not just a distance to think about; there is also a particular place, a route and a set of arrangements to understand.

I took normal race supplies, including hydration and electrolytes, and a hat. This is a description of what accompanied my attempt, not a complete kit list or an endorsement of particular products. I am not attaching quantities or a fuelling schedule to a recollection that does not establish them. For another edition, the organiser's own current instructions would be the relevant starting point.

The reference to military land belongs to the setting. This was a running event on shared land, not military training, an assessment or a qualification. It does not turn this race into part of my Army application story. The two experiences can occupy the same website without being made into the same claim.

Grass, water and an exposed course

The parts of the ground that stand out in my account are the grass paths and water deeper than I expected in sections. “Trail” is a useful category until you are actually on one; then the surfaces become particular. In this memory there was grass underfoot and water to encounter, rather than an uninterrupted line of dry, predictable running.

I do not have a measured depth, a named crossing or a reliable mile marker for those sections here. The useful detail is the contrast between what I expected and the ground I encountered. It is a memory of that attempt, not a forecast of what someone entering Salisbury Plain in a different year will find.

The weather I remember was hot and exposed. Difficult hills and cows also belong in the account. Those details make the day recognisable without needing to turn it into a catalogue of emergencies. I am not reconstructing the order of every obstacle, or claiming that one hill or one patch of water explains why I stopped. The available recollection supports the course's variety; it does not support a precise causal explanation for the nonfinish.

Roughly mile 32: the end of my attempt

I reached approximately 32 of the planned 50 miles, then stopped rather than complete the remaining distance. “Approximately” matters. It is the distance in my recollection, not a checkpoint result certified by an official timing record. I am not giving an elapsed time, a position or intermediate splits for this attempt because none is established for this account.

Why tell the story this way? Because the honest answer to what happened is that my return to distance included a nonfinish. I do not want to replace that decision with a more flattering ending, and I do not need an invented explanation to make it readable. The course, the intention and the point at which I stopped are enough to describe a real chapter.

There is a difference between valuing an effort and upgrading its result. I can write that the attempt mattered to me without calling it a fifty-mile finish. Stopping is part of the narrative, not a footnote to remove once a longer result comes along.

What I meant by calling it a success

“It was a success even if I didn't get to finish it” is the reflection recorded in my manuscript. I read it as a statement about the value I found in attempting the event, not as a rule that every disappointment needs to be relabelled positively. The planned distance remained unfinished. My own assessment of the experience did not change that.

For me, an adventure account becomes less interesting when the only permitted ending is victory. The landscape disappears behind the result, and the awkward chapters get edited out. Keeping this one makes the running story more accurate: it includes returning, attempting and stopping as well as later reaching finish lines.

That is not advice to stop at a particular distance or to continue regardless of circumstances. Another runner's decisions belong to their own situation. My account can offer recognition of a nonfinish without pretending to provide a universal rule for what someone else should do on the course.

June 2024: a different race, a verified finish

In June 2024 I completed South Downs Way 100 in 22:43:38. Unlike the approximate distance recalled here, that time is anchored in the official 2024 event tracker. My South Downs Way 100 report and post-race debrief keep the recorded result and my recollections distinct.

The later finish does not prove Salisbury caused an improvement, and it does not retroactively finish the fifty miles I entered in 2023. It simply adds another chapter. Read the endurance collection for the attempt alongside the hundred- and two-hundred-mile accounts, with their different evidence and outcomes left visible.

Sources and notes

This October 2026 retrospective adapts the course and nonfinish details from my unpublished 2023 autobiographical draft, with my permission. The private manuscript is not linked publicly. The season and roughly 32-mile stopping point are recollections; an exact race date, official timing and checkpoint chronology are not established here. The later South Downs result is separately sourced above. No photograph is presented as being from this Salisbury attempt.