Amazon

Friday, April 23, 2021

Adventure Trail Run - 24 Hour Event 2021


My first place overall finisher award!

It’s been about 3 days since the finish of the Adventure Trail Run - 24 Hour Event as I begin this report. Other than some sore toes from a few blisters that developed under my nails and minor muscle aches in my quads and calves, I’m feeling mostly recovered. For a 24 hour effort, the physical recovery seemed pretty quick and not too painful. It’s more the mental recovery that’s a little harder to move past with this race. It’s not that I’m not proud of the effort I put forth or what I did achieve. The truly stinging part of replaying all the scenes in my mind of how those 24 hours were spent is how close I came to nailing my top goal while just falling a little short. I had a very specific goal for this race: to break the course record of 108 miles. My final official mileage was 103.1 when I stopped with about a half hour left on the clock. When it’s that close for a nearly 24 hour effort, the “what if”s and “if only”s seem to breed and multiply in your brain.

The night sky the whining before the race.

The Adventure Trail Run is a timed trail running event held at Prince William Forest Park (National Park Service) in Triangle, VA. This year was the 15th anniversary of the event and they offered 8 hour solo, 4 person relay 24 hour, and solo 24 hour options. While I chose the solo 24 hour because I had never run that race format before and I wanted to test myself with that style of race, the 4 person 24 hour relay option definitely seemed like a fun way to spend a weekend running with friends.

Just before the start!

The course was basically a lollipop design with a 1 mile out and back to a 4 mile loop. The 1 mile out and back section was definitely the most challenging in my opinion. It was probably the most consistently technical section of the course with seemingly endless stretches of jagged rocks and ankle breaking exposed roots. It also had many short but steep climbs and descents to deal with. During the first mile of the race, I immediately thought I’d have to reevaluate my goals as I wasn’t expecting that technical of a course. Thankfully, the 4 mile loop was far more runnable. In addition to the technicality of that entirely narrow single track section was the fact that it was also the section of the course where you had to deal with two way traffic of runners. Since this was a relatively small event (around 100 runners) it didn’t present a major problem, but with 50k and 100k runners on the course at the same time as the 24 hour runners, it did feel a bit congested to me on a few occasions.

My gear for the race.

The 4 mile loop section of the course was a totally different story. Even the more technical sections, climbs, and descents were more runnable than the initial 1 mile out and back. This year the loop was run in a counterclockwise direction. Apparently the race reverses direction of the loop every year. From the start of the loop to the halfway point fluid only aid station was nearly all smooth, buttery, flat single track trails with the exception of a short climb with a couple switchbacks and few technical rocky sections where you had to be careful of your footing. Immediately after the aid station was a short stretch of boardwalk to run on and then the longest sustained climb of the course. The climb followed a stretch of what appeared to be a fire road for about a half mile and up about 150 feet. The rest of the loop was all single track trail with a few technical rooty sections and a few short climbs, but nothing too intense.

My cabin for the night before the race.

I alluded to it earlier about how the race went in my first paragraph, and I’ll expand on that now. I set what may have been a lofty goal for myself: to break the course record of 108 miles. Obviously, I came up a little short with my final official mileage of 103.1. It’s an especially disheartening form of failure when you’re on pace for your goal for so long and come so close to your goal, but it just very slowly becomes more and more apparent over the course of 24 hours of hard effort and battling exhaustion that it is increasingly unlikely of being attained. For the first 50k I was maintaining a pace faster than necessary and building in a bit of a cushion as I was pretty sure I would slow down for the last 12 hours and the early hours of the morning. As the day wore on and fatigue and exhaustion began to build, I checked my overall pace on my watch ever more frequently hoping to stay under that 12:48 pace that I had calculated I needed to hit my goal. I wasn’t exactly sure if or when my pace would roll over that threshold, so I continued to push on in hopes that I could fend off the ever slowing pace that my watch was reporting.

The inside of the cabin.

Initially it was mostly the aid station stops between loops that seemed to be the primary cause of my slowing pace. I’d check my watch going into and leaving and consistently find my pace slowed by about 10 seconds per mile with each pass through. I tried to get through more efficiently, but filling bottles, emptying gel packages, grabbing more gel packages, and eventually eating some real food all takes time. I was great through the 50k mark when all my calories came from gels and hydration, but when I started feeling the need to add some real food for calories my aid station stops tended to take a bit longer. The data shows that my slowest mile (with an aid station stop) up to the 50k mark was 15:55 and my overall average pace was 11:25 per mile.

A temporary tattoo I tried it for the race.

I still felt good and had hopes of hitting my goal even at the 50 mile mark. I was still at an overall pace of 12:31 per mile. I knew it was going to be close and a struggle at that point, but I thought it might still happen. But then around the 100k mark my pace began to suffer a bit more and my aid stops became more damaging to my overall pace. It was right around that point that my overall average pace rolled beyond my goal threshold and jumped to 12:50 per mile. Although this was a disheartening point for me, it didn’t crush me or make me want to quit. Even if I wasn’t going to hit my goal, I still wanted to get as close as possible. I held on to hope that things could still turn around. I was only about 13 hours into a 24 hour race at that point.

Most of my gel packaging.

Unfortunately, things never really turned around. I never got that major energy burst that I hoped for to put me back within reach of my goal. Things never got really bad either. I continued to move steadily and well, just not well enough. With about 8 hours left in the race the race director let me know that second place was only about 40 minutes behind me. That gave me a bit of a boost of motivation to pick up my pace for a couple laps, but it still wasn’t enough for me to get back to my target pace. As the 24 hour clock began to wind down, I finished my last full lap to hit the 100 mile mark with about an hour and 20 minutes left. I knew I wouldn’t complete another full loop, but I could get credit for a half loop if I made it to the midway aid station before the clock ran out. There was no reason not to keep going, so off I went for three more miles. I reached the midway aid station with about a half hour left in the race and called it there.

Preparing for the drive home.

With that half hour left to burn at the end of my race, I immediately began thinking about how many more minutes I would have needed to run the last 3 miles to finish that final lap which would have tied the course record. I thought another 15 would have gotten me damn close; 20 would have pretty much guaranteed it. After looking at my data, those thoughts turned out to be pretty accurate. My average pace for the last 20 miles without aid station stops was just over 15 minutes per mile. An extra 15 minutes may have gotten me back home to tie the course record. But where would that time have come from? I know I could have saved some time during my aid station stops. My 7 slowest miles included an aid station stop and clocked in at an average of 21:05 per mile; there is definitely room for improvement there.

At the finish!

And then that’s where the brain games start getting out of hand. If only I had changed shirts faster. If I had packed a 2 liter of Coke in my cooler instead of wasting time to have a cup filled at the aid station I would have saved a few minutes there. If I had eaten those 2 perogies while walking instead of while standing at the aid station I may have shaved off another 2 minutes. It’s all enough to drive you crazy at some point. It’s also enough to make you question why I can’t just be happy with a first place finish at my first 24 hour race. It’s not that I’m not happy about my performance or the win I managed to get. I’m proud of both of those accomplishments. But I don’t think it would be a healthy reaction to set a goal, not reach it, and then not at least be somewhat disappointed about it. It’s kind of the point of a goal. You set it, you aim for it, you work for it, you struggle to reach it. And after all of that, if you come so close but fall slightly short, you should be disappointed in my opinion regardless of other circumstances such as overall race placement which was irrelevant to my goal anyway. Maybe that’s wrong. Maybe I’m ungrateful. Maybe I set my expectations too high. Whatever it is, this one is taking some time to process completely. Regardless of failing to reach my goal, I am happy with my performance and what it indicates about my fitness level and ability to endure and continue to move forward despite a mentally challenging circumstance. It gave me an indication of what I may be capable of at my next race, Pennsylvania’s first backyard ultra, the Keystone Backyard!

Recovery time.





Scott Snell

April 22, 2021












No comments:

Post a Comment