Amazon

Showing posts with label altra. Show all posts
Showing posts with label altra. Show all posts

Saturday, August 29, 2020

No Buckles, No Support, Just the Darkness and Lots of Miles: Batona Out and Back FKT



"Disclaimer: I received Science in Sport isotonic energy gels to review as part of being a BibRave Pro. Learn more about becoming a BibRave Pro (ambassador), and check out BibRave.com to review, find, and write race reviews!"



I made the announcement not too long ago here on my blog, on an Instagram post, and on the FKT website that I was planning to make an attempt at the Batona trail self-supported out and back Fastest Known Time (FKT). As I write this, it’s been a week since the actual attempt and I am happy to report that I exceeded the highest tiered goal I set for myself! My top goal was to complete the 106ish mile route in under 24 hours. I was able to do so finishing in 22:46:42 bettering the supported FKT time by over 4 hours! It wasn’t easy and it wasn’t until I was nearly at the finish that I was sure it would happen, but I made it happen nonetheless.

Why was I so nervous and so uncertain over running what most trail runners would call flat and fast running terrain through the New Jersey Pine Barrens? The main reason for me was because this was going into unchartered territory for me figuratively. I had already run every step of the Batona trail multiple times so I was familiar with the trail and the terrain. However, this was my first time wading into the FKT world. I was going for the self-supported record meaning I could not receive any aid from pre-arranged people helping me. Additionally, it meant I would be alone for the entirety of the attempt as the FKT website states that “if a person is accompanied or paced for any distance, it automatically becomes a Supported trip (accompanied = paced = Supported).” The challenge of running through the night in the Pine Barrens by myself without aid stations to break up the miles and without any human contact scared me. Yes, the thought of the Jersey Devil roaming the Pine Barrens crossed my mind, but more concerning to me was the fear of drowsiness and exhaustion taking over while my motivation completely dropped off.

Artistic interpretations of the Jersey Devil

Being familiar with the trail prior to my attempt was a benefit, but it raised another concern: the fact that I knew how easy it was to inadvertently leave the trail. The Batona is a pretty well marked trail with pink blazes, but there are a lot of unmarked intersecting trails, fire roads, and fire breaks that look pretty much identical to the Batona. I knew that staying alert and constantly being aware of the trail blazes was going to be essential to my success.


Lastly, I was so nervous about this FKT attempt because this was my first run of an ultra distance in over a year. My longest training run since Eastern States 100 in August 2019 was about a 23 miler. With it having been so long since my last ultra distance run I wondered if I still had the drive to keep going when exhaustion set in. I usually escalate my race distance as the season continues, running a few 50ks, 50 milers, and/or 100ks before going for a 100 miler, but this year was different (thanks COVID). Without that gradual build up, I wasn’t sure how my body or mind would react to the challenge of a 100 miler let alone a self-supported one.

I tried to have all of the logistics in place well before even beginning my attempt. This involved having a packing list for what was in my car at the start, what was in my aid drops, what was in my hydration pack, and what was in my car waiting for me at the finish. It also meant planning out where all of my aid drops would be, my driving route to drop them all off, and how I would find them again while running past them. I packed five waterproof first aid boxes with gels, peanut butter and jelly sandwiches, Honey Stinger waffles, FBomb nut butters, and mint gum. These, along with a gallon of Gatorade and Shaklee Hydrate+, caches spaced about 10-13 miles apart would serve as my aid stations for my 100+ mile run. 

At the start!

Making the cache drops ended up taking a bit longer than I expected. When I mapped the route from my home to all of the aid drops and then to the north terminus of the Batona trail the total driving time according to Google maps was about two hours. I knew it would take a bit longer to actually do as I would have to park, stash the aid, and mark it, but it ended up taking about three hours total to complete. I tried to make this FKT attempt as relaxed as possible. Since there was no set date or start time to adhere to, I decided I would take a couple days off work when the weather looked good and go for it. My plan was to go to bed early the night before and get a good night’s sleep waking up without an alarm. Then eat a good breakfast, make the drops, and start running whenever all that was finished. I ended up making waffles for the kids then eating breakfast with them before leaving the house a little after 9am.

Starting to run was easy and felt good after all of the driving and preparations. I went out at what felt like an easy and maintainable pace, somewhere between 9-10 minute miles. It was faster than what I needed to do for my goal pace (about 13.5 minute miles) necessary to run a sub 24, but it felt like my pace at the time and I wanted to move. I quickly realized that I had not picked the most opportune time to go for this FKT. We recently had a pretty serious tropical storm with some very high winds pass through the region which resulted in many downed limbs and trees. After finding several pretty good size trees across the trail during the first 10 miles or so, I knew they were adding time by climbing through the limbs or going out and around off trail. I also knew that as I became more tired they would add more time. Not only were they adding time with every one I had to climb my way through or go around, but each one was also another opportunity to be the unwilling carrier for additional chiggers that I was picking up likely everytime I went through the brush off the trail. The little buggers wouldn’t bother me while I was running, but here I am a week later with my legs broken out in a terribly itchy rash from my ankles up to my mid thighs. 

Making my first aid drop!

I tried to rush through my first aid drop as quickly as possible. I devoured half a peanut butter and jelly sandwich and chugged my electrolyte mix after filling my bottles and exchanging my empty gel packets for full ones. A short time later I realized I may have eaten and drank a bit too much too quickly. My belly felt full and sloshy as I continued to run. In hindsight, this may have been the best mistake to make at the perfect time because it forced me to check my pace a bit before any symptoms of over exerting myself too early set in. The rest of the afternoon got a bit warm, but went without incident as I continued to try to move quickly and efficiently.

I took my hydration pack off for the first time when the sun was just starting to set to get my headlamp out. I had decided while running that this would be the ideal time to get my phone out as well and provide my wife with a wellness check and say goodnight to the kids. I was about 35 miles in at the time and the miles were beginning to take their toll on my mind and body. With this being my longest run in over a year, the thought of turning around and just doing a 70 miler had crossed my mind and didn’t sound like such a bad idea. I was hoping the conversation would help give me a bit of motivation. Maybe it was because it’s been so long since the last time I ran through the night or just the fact that this was my first solo FKT attempt, but my wife seemed genuinely worried about my safety in the middle of the Pine Barrens overnight. I assured her that I felt safe, hadn’t seen anything that would make me question my safety, and had some safety gear just in case. With that she was more supportive and encouraged me to finish, but it almost felt like I had to convince her to convince me this time. I said goodnight to my boys who gave me some well wishes then got my phone packed back away to continue on into the night. 

All prepped and ready to go!

It was well after dark by the time I got to the south end of the trail, my turn around point, and I had been moving for about 10 hours and 40 minutes. I felt good that I was well ahead of pace, but knew the second half would be tougher than the first. I took my longest aid station stop at this point because I had a towel and a 2Toms lube wipe stashed there.I did my normal fluid and calorie routine and then freshened up a little with the towel. I used the 2Toms anywhere I was feeling any hot spots; thankfully no major ones.

Overnight was the toughest part of this challenge for me. Not that the terrain had changed much, but it seemed like more portions of the south are multi use as a fire road. These portions seemed to have more frequent dips resulting in deep puddles stretching the width of the trail for lengths of up to 15-20 ft. I felt like anytime I had a decent running rhythm going, I would hit one of these massive puddles and break my stride to try to tiptoe around it to avoid getting my toesies wet. I know the simple answer to fix this is to run through the puddle, but tend to get blisters when I run with soggy shoes so if I don’t have to get my shoes soaked I do my best to avoid it. 

Calling my shot.

Besides the puddles, the night went pretty well other than when my head started playing games with me. Using a brighter headlamp (Nitecore 550 lumen) than my old one I was used to revealed a lot more in the woods than I am used to seeing. I kept seeing all so many reflective eyes in the dark and they seemed to be staring at me. At first it didn’t bother me at all. I just told myself it’s a deer (which I’m sure they were) and continued to run. But as I got more tired my mind started tricks on me and creating other scarier scenarios that became increasingly believable to my tired mind as the night went on. During those predawn hours as I was looking forward to the sunrise I had considered the possibilities that I was being stalked by a mountain lion, followed by a pack of coyotes, or that a big cat had escaped from the Six Flags Safari and was now living in the Pine Barrens.

Besides the tall tales I was creating in my mind, the night was peaceful. The night sky was clear and the stars above the lake clearings were beautiful. There were so many stars and they were so bright away from any lights that I took a quick moment to stand by one lake clearing and switch off my headlamp to enjoy the view for a few moments and mental pictures.

Even with all of my planning and marking to avoid missing my aid stops, I still managed to miss the second one during my northbound journey. Thankfully it was cooler overnight and I was drinking far less so it didn’t bother me too much; just surprised me. I was also pretty tired of gels at this point so I still had enough to keep me going until the next aid. Because of that missed aid drop, I covered nearly half (about a 23 mile section) of the northbound miles without any aid replenishments. 

The northern terminus.

By the last few hours of darkness I was feeling pretty physically exhausted and just plain tired. When it started to get light again I could feel a bit of rejuvenation and motivation to finish coming with it. With the four quarters of my total run clocking in at about 4:37, 6:01, 6:18, and 5:50 respectively, the two middle quarters of my total attempt were my slowest. I would attribute at least some of that being due to the night running and overnight drowsiness. Thankfully, my motivation to finish returned with the daylight. Although I was tired and in some pain, I would force myself to pick up the pace and at least “run slowly” everytime I caught myself walking. Then I would ask myself “Is this a walk in the woods or a FKT attempt?”

With about 20 miles left to go, I was sure I was going to finish sub 24 and also knew that sub 23 was possible if I kept my pace consistent. Everything had gone really well for it being my first self-supported FKT attempt. I only veered off trail once overnight and figured it out pretty quickly, like maybe after a tenth of a mile or so. But now with only a few hours to go until finishing I began to recognize a problem. My Suunto Ambit3 Peak will last 20, 30, or 200 hours depending on the accuracy it is set for. With this being an FKT attempt, I figured more accuracy is better so I set if for the most accurate which should have lasted 20 hours. I knew I would take over 20 hours to finish so I brought a portable battery and charged my watch for a few hours overnight. It still seemed a bit low in the morning so I left the charger connected while I continued to run.

Finished and kinda exhausted.


















However, it didn’t seem to be taking a charge. It seemed to be more or less just running on the connected battery. I got a bit worried when it became readily apparent that my watch wasn’t going to recharge off of the portable battery. I’m pretty sure it was an issue with the portable battery as I’ve used this method with my watch before and it has worked no problems. I didn’t want to lose my evidence of this FKT with only a few miles to go if my watch died so I left it connected to the charger. I was contemplating getting my phone out to record a Strava activity on the phone app and use that second GPS file from that activity as proof if necessary. Although it made the last 10 miles or so kinda stressful, I got pretty lucky and it wasn’t necessary; I arrived at the north end of the Batona trail with my watch battery connected to the portable battery and a remaining life of 14%.





A common description I hear about 100 mile finishes is how anticlimactic the finish can be when considering the enormity of the task. I haven’t done the research to assemble the statistics on crowd size at 100 mile finishes compared to marathon finishes. Anecdotally and based on my personal experiences at the two types of events, the crowd size at a marathon finish has always far surpassed the crowd size at any 100 mile finish I’ve run. I’ve had a 100 mile finish when it was just the two race directors there to congratulate me. I’ve heard stories of runners finishing a 100 miler to only find a volunteer there sleeping that they had to wake up to get their finishing time recorded. Based on my experience and the stories of other 100 mile finishes, I was prepared for an empty and somewhat insignificant appearance to the finish for this FKT. As expected, it was the most empty 100 mile finish possible; it was just me arriving at a completely empty trail head. My car was the only one in the small lot. I ran from the trail end to the final mile marker (Ong’s Hat Rack) and stopped my watch. I didn’t put my hands up in the air or even give a victory shout. I just sat down on the bench there and thought to myself “I did it!” And in the end, that’s all I really wanted. I’m not that interested in the swag or finishers’ medals that come with races. The cheers and motivation from other runners and volunteers are great and very much appreciated, but the main reason I do any of this stuff, whether it’s a race or a personal challenge, is to test myself. The majority of my gratification from running and my motivation to pursue running challenges is to see what I’m capable of and to test what I believe my limits to be.


Last mile marker!

That wraps up my first FKT experience, but I want to just give a quick summary of my nutritional intake during the course of this run. It was probably the least amount of real food I’ve ever consumed during the course of a 100 miler. The only real food I ate was a peanut butter and jelly sandwich, a couple Honey Stinger waffles, and a FBomb nut butter pack. The rest of my calories came from fluids and gels. In total, I ate 15 gels (mostly SIS). This totaled about 4,677 calories over the course of almost 23 hours. I’ve heard the body can only process about 200-300 calories per hour and if that’s the case I guess I was almost right on target with my calorie intake. If you want a full breakdown of my calorie intake, check out the super cool table that I put together below!

Scott Snell
August 29, 2020



Carry in, carry out!


Quantity

Description

Calories Ea.

Calories Tot.

Caffeine (mg) Ea.

Caffeine (mg) Tot.

2

Honey Stinger waffles

150

300

X

X

4

Honey Stinger gels

100

400

X

X

1

Honey Stinger gels (caffeinated)

100

100

32

32

3

SIS Double Espresso gels

90

270

150

450

5

SIS Apple gels

90

450

X

X

1

SIS Salted Strawberry gels

87

87

X

X

1

Boom Apple Cinnamon gels

110

110

X

X

1

FBomb Salted Chocolate Macadamia

210

210

X

X

1

Peanut Butter and Jelly Sandwich

350

350

X

X

2.5

Gallons Gatorade & Shaklee Hydrate+

960

2400

X

X

Totals:


4677


482







Saturday, May 16, 2020

High Desert Drop Bag Gear Review - Ditty Drop Bag


Update! The owner of High Desert Drop Bags recently contacted me to share this limited time discount code with all of my readers. Use code "BCTR-21" to receive 20% off of your order. Offer is valid 9/2/21 - 10/1/21.

I received a High Desert Drop Bag (Ditty Drop Bag) as a part of a swag package included with my entry to the inaugural Mines of Spain 100 mile trail race in October 2017. Since then it has become my “go to” and favorite drop bag I’ve used at any ultramarathon. It’s durable, keeps my gear dry, and cleans up easily after a day of getting tossed around and thrown in the dirt.

Some Quick Stats:
  • Front Identification Panel
  • Water resistant 400 denier nylon packcloth
  • #8 nylon coil zipper for easy access as well as security
  • 1/2" nylon webbing carry loop
  • Available in four easy-to-see colors
  • List price: $22.00 Plus shipping
  • Weight: 3.7 oz
  • Dimensions: 13.75 in × 16.75 in × 1 in

The Ditty Drop Bag is the smallest size drop bag offered by High Desert Drop Bags (Bishop, CA). They offer two larger size drop bags: The Dirt Bag (18.5 in x 19.5 in, 21 liters) and The Ultra (28.25 in x 19.5 in, 39 liters). Even though it is the smallest drop bag they offer, I have found the Ditty Drop Bag has plenty of room for everything I have wanted waiting for me at an aid station. I most recently used it at the Blackwell aid station (mile 80) of the 2019 Eastern States 100. For that race I easily fit all of the following in my Ditty Drop Bag.

In addition to the Ditty Drop Bag’s tolerance for rough handling without showing any signs of wear after a couple years of use, the other feature that stands out to me about this drop bag is the identification panel. It’s an aspect of the bag that may seem like a big fat nothing burger. At first take that was my thought about it as well. After using it a few times though, I realized how handy it was and how much more convenient and dependable it was than my previous methods of labeling my drop bags. In the past, I had attached some type of paper tag with all of my pertinent information to my makeshift drop bag with safety pins. To waterproof my homemade tag, I would seal it in box tape. This worked fine, but was a bit cumbersome and I always worried about the tag getting caught on something and ripped off or being made unreadable from rain seeping through my waterproofing. My other drop bag method was to just use a large Ziploc bag. This was super easy and completely waterproof, but I always worried about the bag tearing and losing some of my goods. The High Desert Drop Bag identification panel resolves all of these concerns. Now I just slap some duct tape on the panel and write my info on with a sharpie. Quick, easy, and no worries!

For me, High Desert Drop Bags have set the standard for other drop bags. No other bag I’ve used has worked as well or as conveniently as a drop bag than the Ditty Drop Bag. If you’re frustrated or even just kinda irked about a few issues your drop bag has caused you, I would recommend at least looking at what High Desert Drop Bags has to offer.

Sunday, December 29, 2019

2020 Running Goals


My top nine photos of 2019 from Instagram.

Shortly after finishing the Hyner View Trail Challenge 50k last year, I made the decision to change up my race selections for 2020. It wasn’t because of how Hyner went or because I don’t want to run Hyner again. I love the Hyner 50k and definitely want to run it again, but the catch for me is that once I’m registered for Hyner I end up following the inevitable path of running the entire PA Triple Crown Series. I figure if I’m doing Hyner, I might as well run Worlds End 100k and Eastern States 100 as well. I decided the best way to avoid getting caught in that trap and change up my race schedule was to not register for Hyner 50k. I have nothing against any of those three races. It’s just that after three consecutive years of my race schedule revolving around the three same “A” races, I felt it was time for a change.

For 2020 I want to make my “A” race a 24 hour timed event. A 24 hour event has been on my to do list for a few years now, but never a high priority, so it never happened (hence one of my favorite quotes below). I hope to change that this year and see what I’m capable of achieving in a 24 hour race. If things go well at whatever 24 hour event I decide to run, I should be able to finally achieve a second running goal that has eluded me for the last two years: to PR my longest distance in a single run. I’m hoping that if I choose a 24 hour event with an easy course I will be able to average at least 12 minute miles or 5 mph for a total of 120 miles at the end of 24 hours. This will easily be my longest distance run as my current longest distance is finishing the Tesla Hertz 100 miler which was actually about 104.8 miles. 




An additional goal for this year is to run another “last person standing” event. After running my first two events (Run Ragged) of that type last year and for the most part enjoying them while doing pretty well, I want to run some more of these types of events. Ultimately, I hope to get a chance to run at the original last person standing race, Laz’s Big’s Backyard. I realize it may not happen at all considering the growing popularity of those types of races, but I figure if I run races that build my running resume geared towards last person races it will better my odds to hopefully run at Big’s some day. Running Big’s Backyard definitely isn’t strictly a 2020 goal, but more of a long term goal to work towards year after year until it happens. In my opinion, it’s good to have the late game goals working in the background while having the short term goals mixed in to keep things interesting.



A non race related goal for 2020 is to run all the streets of my hometown, Egg Harbor Township, NJ. This goal was directly inspired by Rickey Gates’ project to run every single street in San Francisco. I started on this goal at the end of October this year with the intention of making it a longer term goal and hopefully completing it before the end of 2020. I’ve posted a couple blog posts specifically about this goal and plan to update with posts throughout the year as I make progress. You can get more details and background about the project from those posts (here and here), but the overall concept is just as the project name suggests, to run every single street of the town.

Another somewhat running related goal I have for this year is one just for fun: to run a Twinkie Weiner Sandwich Mile to celebrate the movie UHF. My plan is to do this the same way as I do the Annual Hot Dog Run every year, just with Twinkie weiner sandwiches in place of the hot dogs. If you’re not familiar with the Annual Hot Dog Run, just think beer mile with beer replaced by hot dogs. If you’re not familiar with UHF, go watch it. I plan to do this run either July 21st to celebrate the UHF release date or June 2nd in honor of Channel 62 (6-2), the focal point of the plot of the movie. If you have an opinion on which date is more appropriate, please vote!


My final running related goal for the year isn’t about any race I want to run or hitting a new running time or distance PR. It is to volunteer at a local race with my son and any of the other members of his scout troop that want to come along to help out. This is an idea/project that I had a while back, but have never acted on. I put it off for some time because I thought that he was a little young and having him and a few of his scouting friends volunteering at an aid station would be more of a hindrance than a help to the runners and the other aid station volunteers. I feel like he’s matured enough in the past few years to be able to handle some of the aid station tasks and at least help out and encourage some runners for a portion of a race if I stay with him to provide some guidance. I hope it happens and goes well as I see this as being a great fit for service projects for scout troops. The scouts get to help others stay fit and enjoy the outdoors responsibly while also contributing to another community (trail runners) that values the outdoors and our shared public natural areas. If you’ve brought kids to volunteer at a race, I’d love to hear about how it went for you and would greatly appreciate any kind of tips and advice you can provide that would have improved the experience.

2020, sure to be another great year as a BibRave Pro!


2020 Goals

  • Run at least one 24 hour event
  • PR longest distance in a single run (>104.8 miles)
  • Complete my "Run Every Street" of Egg Harbor Township project
  • Run at least one “last person standing” event
  • Volunteer at a local race with my son



Saturday, August 24, 2019

2019 Eastern States 100



PA Triple Crown Finisher Award Display

It’s been a little over a week since Eastern States (ES) 100 as I begin to write this and now that my sodden, pungent clothing and gear has been cleaned and the wounds are for the most part healed I am beginning to have a greater appreciation for how my day there played out. I went in with a single goal that I thought was well within reach given the year I had thus far. The goal was simple, finish in less time than it took me in 2017 (27:17:24). This would also ensure a faster cumulative time for the 2019 Pennsylvania Triple Crown Series over my 2017 time for the series (47:47:36). Since I had finished both Worlds End 100k and Hyner 50k faster in 2019 than 2017, this goal seemed well within reach. However, the uncertainty of the 100 mile distance and how things can go south at any point was a constant concern for me. Excessive worrying about the potential for things to fall apart may be what ultimately led to me failing to reach my goal. 

Pretty early in the race. Photo credit:  Joseph Hess
For about two weeks leading up to the race I was feeling extremely anxious, more so and for a longer period before the race than I have ever experienced in any other lead up to a race. Adding to my trepidation was a work trip that I had scheduled for the week just before race weekend. I would be flying back to Philadelphia Friday around noon, then getting picked up by my wife to make the remainder of the drive to Little Pine State Park. I packed my two drop bags and everything I would need at the start the weekend before the race then worried all week hoping I hadn’t forgotten anything. By the time the work week was over and I was picking up my bib at registration the relief I was expecting didn’t wash over me. I had my stuff ready a week prior, managed to get there without any flight delays interfering with my travel plans, and now all I had to do was run 103 miles on the rugged trails of the PA Wilds. I guess there was still good reason to have a fair amount of nervous excitement.

Lower Pine Bottom AS, Mile 17.8
Thankfully, I managed to get a pretty solid night’s sleep before the 5am start, but at the starting line the jitters were still present. I did my best to deal with them in hopes that they would subside once I got on the trail and put a few miles behind me. Everything went well for the first 50k or so. I knew what pace I had to keep to meet my goal and I was staying ahead of that pace and feeling comfortable doing it. The climbs didn’t seem as bad as I had remembered and my quads were handling them well. It almost seemed like it was too easy this trip around Pine Creek. It was shortly after AS5 (Happy Dutchman) that I got hit with my first blow when I realized my watch had led me astray. The actual mileage at AS5 is 31.6. My watch, which has otherwise always been reliable and pretty accurate, was reporting that I had covered a little over 36 miles. I was focusing on only getting aid station to aid station so I was mostly just using my total mileage to see how much farther to the next aid station. When the signage at AS5 showed the mileage to the next AS as 6.9 and I used the inaccurate information on my watch that would put me at about 43 miles total. That was a significant mile marker as it is the second crewed AS, Hyner Run. I got excited that I would get to see my wife and boys again and it felt so soon since I had just seen them at the first crewed aid station. Mileage and the next aid station came up in conversation with a couple other runners and when their watches synced I realized mine was off and there was one more AS between us and the next crewed AS. It was a bit shocking at the time, but I tried to comfort myself by saying I was happy to find out early how far my watch was off rather than later. However, later in the race while talking to one of the other runners that helped me realize my error, he would tell me that my face showed a bit of a soul crushed reaction when I realized it was my watch that was off.

One of the early climbs. Photo Credit:  Tomas Castillo
With that minor mishap out of the way early, the rest of the daylight hours of the race rolled by pretty pleasantly for the most part. I don’t know if it was due to the low temperatures we had on race day or just my misconstrued recollection of the course, but my second time running ES I was shocked by how much of the course felt runnable. The majority of my memories of the ES course was super technical descents intermixed with steep, rocky climbs. This time though,outside of two big early climbs (just before AS1, Ramsey Rd. and just after AS3, Lower Pine Bottom) the bulk of the first half of the course was feeling runnable. And I was running the bulk of it and staying on my target pace even after I adjusted for my watch’s misinformation without feeling like I was pushing myself even near the point where I thought a blow up was a possibility.

Another AS stop.
A second mishap started emerging or at least giving indications of larger problems about the same time as when my watch mishap was discovered. This mishap began with some slight discomfort around the bottom elastic of my hydration vest. I was wearing the same vest and same shirt that I have worn for 100ks and 100 milers in the past with only minor chafing issues, but this time around those minor chafing issues became exasperated and caused major chafing that was never resolved no matter how much or what kind of lube I threw at it. Since the equipment and clothing was the same, the only explanation I can come up with is that I was carrying more weight in the vest than I had ever packed before. I had trained with Science in Sport (SIS) gels all season and wanted to use them for the race so I packed 10 in my vest at the start and had 10 replacements in each of my drop bags. Also, I wasn’t positive gels would be available at every AS. Ten gels may not sound like much additional weight, but SIS gels are roughly about twice the volume of standard energy gels making a bit bulkier to carry and nearly doubling the weight. The best guess I have at this point is that the extra weight/volume in the vest made it fit and move differently than any time I’ve worn it in the past. Ultimately leading to some terribly painful chafing. I like to think I’m not one to complain about the little stuff, but this turned into a steady distracting pain from about the halfway point to the finish. I also like to think I’m not one to blame equipment for my failures, but in this situation the equipment had a major impact on my focus and overall mindset. I never thought about quitting because my sides had been rubbed raw by my pack, but the pain constantly pulled my focus off of running and moving efficiently to just thinking about taking this pack off as soon as possible.

The worst of my chafing.
The watch incident and the chafing issue are the only two concrete items I can point to that led to me falling off of my target pace, neither of which I truly deem responsible. I was ahead of my intended pace for a 27 hour finish at AS9, Halfway House (54.7 miles), but somewhere between there and AS14, Blackwell (80.3 miles) where I was picking up a pacer and had my next time goal calculated I was well over an hour behind where I wanted to be. It was strange because I never felt completely exhausted, but had this strange feeling of never feeling like I was pushing myself to the limit and always running overly safe without getting out of my comfort zone. In retrospect, it seems like I was so concerned about blowing up that I never pushed to my full potential for the day. Usually with hundred milers I feel like I get into some kind of singular focus and survival mentality, only concentrating on getting to the finish as quickly as possible. For whatever reason, that switch never got flipped this time.

A power hug from my youngest!
Even with my time goal out of reach and twenty some miles to go, I was excited to pick up a pacer at Blackwell. It was my first time using a pacer. It wasn’t the situation I had envisioned of being on pace and having my pacer push me to the finish ahead of pace, but he was able to up my morale and that of the couple other runners I had spent the majority of the night with. I will admit, we had a bit of a pity party on the trail overnight and it likely would have continued the rest of dark early morning hours if we were not joined by a pacer. With a bit of fresh energy provided by our pacer, Kurt Foster, we picked our pace up for the respectable climb out of Blackwell. Kurt continued to push our pace for the remainder of the race, reminding us every time the trail was runnable. With my time goal a lost cause, he kept me from basically giving up and walking it in, pushing me to earn a finish time that I could be proud of.

At AS11, Slate Run, 63.8 miles.
We grinded our way in the dark to the next AS, Skytop. It was a little tough mentally to leave this one because the crew there was so accommodating and we knew the stretch to the next AS was one of the longer ones of the race. Without getting too comfortable, we ushered ourselves out and pushed on. Thanks to Kurt, our pass through the second to last AS, Barrens, was one of our fastest. We refilled bottles, grabbed food, and were out in probably 1-2 minutes. We were as fast if not fastest passing through Hacketts, the final AS. With only about four miles left, not much was needed and the excitement to finish was peaking, at least I thought.

At packet pick up.
Shortly after leaving Hacketts near the top of the final climb of the course we heard a runner coming up behind us quick. Kurt turned to me and said something along the lines of “you don’t wanna get passed just a couple miles from the finish.” I replied by saying that I wasn’t sure if I have anything left. Then Kurt said something that finally lit a spark at the time. He basically said even if I attempted to outrun him for the last two miles and still got passed, then I could just walk it in and still get the same result even if I hadn’t made the effort. For whatever reason, at the time that got me to dig and give it my best effort to stay in front of this other runner. That’s when things finally started to become fun again. I was moving and feeling good. Before I knew it, I caught sight of a runner ahead of me. We passed him. Now things were getting really exciting for the finish and the final gnarly descent of the course. In the last two miles or so, we passed four runners. It amazed me that we were so close to these other runners and without that little spark provided by Kurt, I would have contentedly shuffled in to the finish after them.

My 2019 finish!
I crossed the finish line at 28:46:52, a full hour and almost 47 minutes after when I had intended to finish. At the beginning of this report I wrote that I failed. I may come off sounding like a bit of a jerk or a real pessimist by saying that I wasn’t entirely pleased with this finish. It’s easy to say that any 100 miler finish, especially a tough 100 mile course like ES, is something you should be proud of. However, after assessing how my legs felt during that last steep downhill this year compared to two years ago, I knew I had more left in me at the finish this year. In 2017 I was desperately bouncing from tree to tree to keep from going into an out of control tumble down the incline. This time, although my quads were screaming, I was bombing the downhill mostly in control. The fact that the spark to push harder earlier never happened is what I was really disappointed about. The “what if”s were what bothered me. After a few weeks to digest it all, I still can’t say that I’m not a bit disappointed that this final piece of my PA Triple Crown Series goal didn’t fall into place like I had hoped, but I can say that I am proud of the finish and to have completed the full series for a second time.


Getting my chafing patched up at the finish!

August 24, 2019
Scott Snell