What It Feels Like To Run 100 Miles Or Similar Long Ultramarathons

Sometime in the last year, I decided I wanted to run 100 miles. In part, because I wanted to tackle the complex challenge and problem-solving that is even figuring out how to do it.

My situation as an ultrarunner is slightly atypical: I have type 1 diabetes and need to closely manage insulin levels and glucose levels while running; I have celiac disease so I can only eat 100% gluten free things; and I have exocrine pancreatic insufficiency (EPI) so I need to swallow enzymes with everything that I eat, including when I run. It’s a logistical cornucopia of challenges…which is in part why I wanted to do it. It wouldn’t be half as rewarding if it were easy? Or something like that.

But mainly, I wanted to prove to myself that I can do hard things, even things that most people think I can’t do. No, I can’t produce my own insulin, but I can locomote for 100 miles at one time despite this and the other challenges I have to deal with along the way.

Plus, there’s the “normal” ultrarunning challenges of fueling, hydrating, managing electrolytes, keeping your feet from becoming a ball of blisters, etc.

Ultrarunning is a sport where it generally doesn’t matter how fast you go, and the farther the distance the more of an equalizer it is. I’m a slow runner, and I had trained at an easy slow pace that I planned to run during my race (self-organized). Not having the pressure of time cutoffs would help. I was also curious whether running so slow at the start would possibly help me maintain a more even pace split across the entire run, and whether I could ultimately achieve a reasonable time by keeping consistent slow paces, compared to many I’ve read about who go a bit too fast at the start and end up with wildly different paces at the end. Everyone hurts running an ultra no matter how much you run or walk or both and no matter how fast or slow you go, but I was hoping that more consistent pacing and effort would minimize how terrible everything felt if I could pull that off.

Background

I trained, ran a 50k in June, and resumed training and worked back up to 24 mile long runs and all was going well, until I massively broke a toe and had 6 weeks off. Then I resumed training and re-built back up to running 29 miles, ending around midnight for night-run training. At that point, I had one more long run scheduled (32-ish miles), but decided I would rather skip the last long run and push my 100 mile run up a few weeks to try to beat the impending rainy season that Seattle would eventually get.

The joke was on me. We had 6+ weeks of terrible air quality, which peaked into a two-day stretch of downright “hazardous” (ugh) air quality the two days before my run. Air quality was finally improving overnight before and the morning of my run, thanks in part to the most rain we had gotten in 128 days. Woohoo! So I got to add some wet and cold running challenges to my list of problem-solving that I’d tackle during my run.

Overall, though, my training had gone well, and I had spent enough time planning and prepping that I felt relatively confident. Mostly, confident that no matter how well or long I trained, it was going to hurt. All over. For what felt like forever, and then I still wouldn’t be anywhere near done. And confident that I had planned and prepped to the best of my ability, and that I could figure out how to tackle whatever situations I faced as they came.

How I felt before the race

Aside from having cabin fever from being inside (AQI was too hazardous to go out even with a mask), I felt fairly good in terms of running fitness. I had been tapering, my legs felt fresh, I was fueling and hydrating and everything felt fine. Unfortunately, though, while I managed to escape many taper niggles, I experienced a round of ovulation pain that I don’t get every month but was lucky enough to get this month, for the 3 days prior to my race. (I’m not sure why, but in the last few years after never experiencing ovulation pain, I have started to get ovulation pain similar to period pain and cramps and general icky feelings. My doctor isn’t concerned about it, but it’s unfun, and in this case poorly timed.) So I was a bit grumpy about going into my race in a less-than-perfect state, even though “perfect” state is an ideal and usually there is something wrong, whether it’s a taper niggle or something else.

The thing I was most pleased about was my feet. My broken toe had healed well and hadn’t been giving me any issues. However, after I broke my toe it changed my foot strike or how my feet move in my shoes in a way that caused epic blisters and then I kept getting blisters on top of blisters for several runs. I finally figured out that I needed to try something different, stopped causing new blisters, and the existing blisters healed, peeled off, and went away. So my feet were in great shape, and despite being nervous about the effect of the rain on my feet during my 100 miles, I at least was starting from a “clean slate” with healthy, non-blistered feet.

The start

I set my alarm and woke up and checked air quality. The winds and the start of the rain had blown it absolutely clear, so I was able to head out without a mask for the first time in weeks! (Last time I ran with it for all 8 hours of my long run, which is annoying when you need to fuel every 30 min.)

I wasn’t even a mile in when I had my first problem. I started with a long sleeve shirt and my rain jacket, knowing I’d warm up and want to take it off soon after I started. As I removed my arms from my rain jacket (keeping it zipped around my waist) and shuffled my arms in and out of my running vest, I suddenly felt water hit my feet and looked down. Water was gushing out of my hydration hose! I grabbed it and stuck my finger over the end: the bite valve had flown off somehow while I was getting out of my jacket. Ugh.

Luckily, though, this is where all of my planning and reading of others’ experiences had come in handy. While this had never happened to me, I had read in someone’s blog that this had happened and it took them 20 minutes to find the valve. I had a bright waistlamp and it was getting increasingly lighter outside as the sun rose, so I hoped mine would be easier to spot. I figured it was stuck in my rain jacket sleeve so I worked to check my sleeve and vest for the valve. No go. I looked around and didn’t see it. I turned and walked back a bit, looking for it on and off the trail. No luck. I finally pulled out my phone and called Scott, while still holding my finger over the hydration hose to keep it from leaking out 3 liters of water. While I talked to him and told him I probably needed him to get dressed and bike out a replacement valved to me, I turned around and walked forward again one more time. Aha! Found it. It had flown way to the left side of the trail. I replaced it and breathed a sigh of relief. It had added only 4 minutes to my first mile time.

Well, I thought: that’s one way to keep my early paces slow! I hung up with Scott, and carried on.

The first lap I was very focused on making sure my socks and shoes were in good shape. I am pretty good at gutting it out if I have blisters or foot issues, but that’s not a good strategy when you’re going to cover 99 more miles. So 6 miles into my first lap, I stopped at a bench, took my socks off, and re-lubricated my feet. Later on the way back (this first lap was an out-and-back), I stopped at mile 16 and similarly sat on a rock to re-lubricate and add lamb’s wool to reduce rubbing on the side of my foot.

A picture of Dana Lewis running down the rainy paved trail, with resupply gear (dry shoes, water, fuel) in the foreground of the picture. She's wearing shorts, a rain jacket, and a rain hat. She is smiling and around 12 miles into her eventual 82 mile run).

Yet overall, lap 1 went well. It started raining after about 20 minutes so I ran with my rain hat and rain jacket on (I put it on after my bite valve escapades at mile 1), and intermittently put my hood over my hat and took it off when the rain picked up or lessened, respectively. But it pretty much rained the whole time. Scott met me as planned after my turnaround spot (about 12 miles in) and refilled my hydration pack and I re-packed my vest with snacks, enzymes, and electrolytes and carried on.

At the end of lap 1 (almost 24 miles), I physically felt pretty decent. I had been working to focus on the lap I was in and what I needed to do for the next lap. Nothing else. No thoughts of how many miles I would run or hours it would take. My watch had stopped itself in the rain and canceled the run (argh), so I wasn’t going to have a running total of time throughout the entire run like I wanted. But this might have been a feature, as it kept me from using my watch for that and I set a new lap/run each time I headed out so I could keep an eye on the segment pace, even though I had no idea what the overall pace time really was.

A paved trail picture taken from on the trail. Trees and a river are to the left; more trees line the trail to the right. It is very cloudy, the trail is visibly wet.I went slow the first lap (part of why I was feeling so strong), and I took my time in between laps. I pulled off my socks and shoes. I used hand sanitizer on them to draw some of the water out, then re-lubricated and added Desitin (to continue to help draw water out of my feet and aid in preventing blisters). Then I put on a fresh pair of toe socks and added more lamb’s wool in between key toes that typically are blister-prone. At this stage I had no blisters, and other than wet soggy feet was in good shape! Sitting for 10 minutes for my sock and foot care change chilled me, though, and I was happy to start moving again and warm back up.

The middle

I headed out on lap 2, which similarly went well. This was my “triangle” shaped loop/lap. The only issue I had this lap was that it was the only section of my route where the trail crossed 3 small intersections. Two had lights but one did not. At the intersection without a light, there were no cars so I continued running across the pedestrian crossing. As I stepped out I saw a car whipping around the corner with their head turned looking for cars in the opposite direction. Not sure if they would turn in time to see me, I slammed on my physical brakes. They did turn and see me and stopped in plenty of time, so I continued across the crossing and on the trail. However, that had tweaked my right ankle and it felt sore and weak. Argh. It felt better after a few more minutes, but it intermittently (once every hour or so) would feel weak and sore throughout the rest of my run as a result.

After lap 2, I again sat to remove my socks and shoes, dry my feet, put hand sanitizer on them, re-lubricate, etc. My feet were definitely wet and wrinkly, so I added even more Desitin to my feet. It wasn’t raining super hard but it was a constant hard drizzle that was soaking through to my socks and feet even though there weren’t many puddles (yet). This time, though, I used some reusable hot packs while I sat to change shoes, so I wasn’t as chilled when I left.

Lap 3 (back to an out-and-back route) also went well, and I was starting to realize that I was in surprisingly good physical shape. My feet were intermittently a little bit sore from pounding the ground for hours, but they weren’t constantly annoying like I’ve had on some training runs. I had long surpassed my longest running distance (previously 32 miles; at the end of lap 3 I would reach 52 miles) and longest ever running time. I did develop one or two small blisters, but they didn’t bother me. Usually, I build up huge blisters and they’re a constant annoyance. During my race, maybe thanks to the Desitin etc, I only noticed the blisters (which were fairly tiny) when they popped themselves. I had one on each foot pop and sting for a minute and then not bother me again, which was pleasant! Lap 3 was also when it got dark, so I’d headed out with my double waist lamp. I have two sets of two waist lamps that we strapped to each other; I turn one on and run it out (somewhere around ~3 hours) and then turn the belt around and turn the other lamp on. This lasts me the longest laps I have, even if I was going at walking speed. It’s plenty of light for the paved trail even on the darkest nights, but because it was raining it was cloudy and the city’s light pollution reflected off the clouds so that trail itself was easy to see! So while I only saw a few stars at the end of the night in between patches of cloud, for most of the night the night-running aspects were pretty easy. Dana sits on a bench at a picnic table in a public park. It is dark. She is wearing long rain pants, a rain jacket, and a rain hat and is bent over her bare feet, applying lubrication. It is dark and nighttime, so she has an extra waistlamp on the table illuminating her feet. Other ultrarunning supplies are strewn across the table.

Interestingly regarding my feet, after lap 3 they were still white and wrinkly a bit, but they were definitely drying out. They were much drier than they had been after lap 2, so the combination of hand sanitizer and Desitin was working. I was pleased, and again slathered with more lubricant and Desitin before putting on fresh socks and heading back out for lap 4, which would be a repeat of my “triangle” lap.

Physically, I was mostly ok. My feet weren’t hurting. I had expected my IT bands to get tight and bother my right knee and for my hips and back to start getting sore: my left knee did intermittently hurt some, but it was like a 3/10 annoyance and came and went. Stretching my hip flexors didn’t change the tightness of my IT band, but it was also the least amount of knee pain I’ve ever had when things got tight, so it was very manageable and I didn’t stress about it. It was hard to believe that with the completion of this lap (lap 4) that I’d have finished a 100k (62 miles) and added a few miles to it!

It seemed like the triangle loop wanted to keep things interesting, though. On Lap 4, after I had turned off into the section that has the intersections and the “triangle” part of the loop, my hydration hose made a gurgling noise. I felt the back of my hydration pack, which was rock solid with ice…but no water left. Oops, I thought. I was at mile 6 out of 13. If I kept going forward on my route, it would take me an estimated 4+ miles to get back to the next water fountain. Or I could call and wake up Scott, who had just fallen asleep for his first 2 hour nap overnight (it was around 1am by now), to bring me water, but that would take him 20-30 minutes before reaching me.

It mattered that I didn’t have water. Not just in terms of thirst and hydration, but I also needed water to be able to swallow my electrolyte pills (every 45 minutes) and my fuel (every 30 minutes when I ate a snack) and the digestive enzymes I absolutely require to digest my food since I have EPI. I definitely needed water so that my hydration, fueling, electrolytes, etc. wouldn’t suffer.

I could go back, but I hated to backtrack. It would be a mile back to the previous water fountain, although I wasn’t even sure it would be turned on and working. Mentally, though, I groaned at the thought of “turning around” and finishing the loop in reverse and trying to figure out how many miles I would cut off that loop and how many I’d have to added to my very last loop to make up for it.

Luckily, I realized a better idea. Because I was on the section of the triangle running alongside a road (hence the annoying intersection crossings), the intersections are where the road turned off into various parking lots. Across the road at one of the two intersections with lights was a gas station! I could see it glowing from a quarter of a mile away. I crossed my fingers hoping it would still be open, because I could go inside and buy a bottle of water to hold me over. It was open! I crossed the intersection and went in, grabbed a liter of water, bought it, went outside, and refilled my hydration bladder under the bright lights of the gas station.

A 1-liter wattle bottle held in a hand covered with a blue nitrile gloves.
I’m wearing nitrile gloves to help keep my hands drier and warmer given the cold, endless rain.

I was pretty proud of that solution, especially because it was ~1am and I had been running for 17 hours and was able to troubleshoot and solve that problem on the fly! Without sending it, I also drafted a text to send to Scott near the end of that loop when he’d be awake, to list out which foods and gear I wanted at the next refuel, and to specify what happened and how I solved it and request that I get more water and less ice for the next loop.

(Running out of water was on my list of things I planned for in all of my preparation, so while I had low expectations of my mental capacity as the miles piled up, that likely helped because I had mentally listed out where all the available water fountains were, so I could run my loop mentally forward and backward to figure out where the closest one was. In this case it was a mile behind me; going forward it would have been 4+ miles or more than an hour away. The gas station ended up being 15 minutes from where I realized I was out of water).

Finishing lap 4 was exciting, because I only had 3 laps left to go! I had one more out and back loop, and my father-in-law was driving down in the wee hours of the morning to run part of it with me to keep me company. We hadn’t planned on that all along, but he and Scott had been texting and working it out, so Scott just told me that was the plan and I was thrilled. I was a little bit tired overall, but more energetic than I thought.

The sock change before lap 5 was disappointing, though. After lap 3, my feet had been drying out a little bit. Now after lap 4 they were wet and soft again, like they were after lap 2. The rain had been more constant. I took the time (15-20 min) I needed to dry and treat them with hand sanitizer, lubricant, Desitin, replace fresh toe socks and lambs wool and dry shoes. They weren’t hurting, so I was hoping the light rain would taper off and my feet would dry out again.

The (beginning of the) end

I headed out on to lap 5, buoyed by the thought that I only had ~4 miles ‘til I had company. The rain picked up again (argh) and as my father-in-law met me on the trail with his headlamp and rain gear, he asked if it had been raining this much the whole time. No, I said, and pointed out that it had only been raining hard in 10-20 minute chunks and this one had been going since before I met him so it should lighten up soon. He commented on how energetic and chatty I was. “You’re pretty chatty,” he said, “for 5am!” (I am well-known in both our families for NOT being a morning person). I joked about how impressive it was for me being this chatty not only at 5am but also for it being 22 hours into my run!

Unfortunately, 3 miles into the section he ran with me, it went from annoying hard drizzle to an epic mega downpour. My shoes went from damp from constant hard drizzle to super soaked from top all the way down to the insoles squishing with every step. I was frustrated, because this much rain was also making it hard to use my phone. My phone had an alarm going off every 30 minutes to remind me to fuel; I needed to pull out my phone each time and turn off the very loud alarm (it was effective!) and then open up my spreadsheet and enter what I ate and what electrolytes I took. Then I also had to pull the baggie out of my vest pocket, select out the number of enzyme pills I needed with wet and cold gloved fingers, re-seal the baggie and put it back in my vest, and get out the fuel from the other pocket of my vest and eat it. Even tired, I was managing to fuel successfully and stay on top of my schedule. I was increasingly proud of this.

But the rain and the inability to use my phone when I wanted to was starting to irritate me, in part likely because I was trying not to stress about what the volume of water was doing to my feet. They weren’t actively hurting, but I knew this much water for this long of time could be dangerous and I needed to be careful. It was still downpouring when we reached the turnaround and headed back to his car. I dropped him off at his car and carried on. I was tired, soaked, cold, but physically in great shape otherwise in terms of legs, knees, hips, back etc all holding up and not feeling like i had run ~78+ miles at that point!

I had just eaten another snack and went to press buttons on my pump to give myself some insulin for the snack. It didn’t seem to work. I have a vibration pattern so I can use the pump without seeing it; but the “enter” button was not working. I had been concerned about the volume of water my pump was going to be exposed to and mentally prepared for that, but it was SO disheartening to suddenly feel the pattern of 6+ vibrations followed by an audio beep indicating an error state had been reached on the pump. I cursed to myself, out in the rain after 24 hours of running, knowing what I would find when I pulled my pump out from under my jacket. Sure enough, “button error”, because water had gotten under the buttons and to protect itself, the pump went into a “I won’t do anything” state. That meant that the insulin I needed for my latest snack wasn’t going to happen and any future insulin wasn’t going to happen.

I pulled out my phone and started a text to Scott, explaining that I had a button error and needed him to pull out my backup pump. I told him where it was, told him to put in a new battery and program it with the basal rate that I wanted. I then sent a text saying it was raining a lot and it would be easier if he called me if he needed to talk, because it was so hard to use my phone in the rain. He read the text so I knew he was awake, so I called him and talked to him while I trudged on and he was getting dressed and packing up my replacement pump and the gear I needed for lap 6. Then we hung up and I carried on, grumbling along the way and starting to feel the physical effects of not having enough insulin for the past hour or so.

A picture of a glucose graph from a CGM. The dots are flat in the first hour of the screenshot, then slowly and almost exactly lineary head up and to the right.

My blood glucose levels were rising, but I wasn’t worried about that. I knew once I had replacement insulin my blood sugars would come down nicely. I had prepared for this; there was a “high BG” baggie with supplies ready to go! But the combination of the 25+ hours of rain, the extra hard rain and cold temps from the last several hours, my feet starting to be bothered from the wet soaking, and then on top of it all the chemical feeling of not having insulin going in my body: it was a lot. I really focused on the physical state I was in, evaluating what I wanted to do. I knew that I could fix the cold state (switch to dry clothes; use hot packs) and my blood sugars (new replacement pump, take some inhalable insulin for a faster fix while the new pump insulin would be kicking in within an hour and fixed from there). But my feet were starting to bother me in a way that I wasn’t sure could be fixed with a 20 minute sock change.

Scott biked up to me right as I passed my favorite trail bathroom, the stalwart of my ultra, and had me turn around and head in there to be out of the rain. It was clean, big, had toilet paper, and was well lit and had the door open (wasn’t locked) all night long. I stepped inside the bathroom while Scott parked his bike by the building and whipped out the baggie with the replacement pump. I checked that no one else was in the women’s bathroom and he stepped inside, and impressively (to me) pulled out the baggie that held a garbage bag. I had packed it so I could more easily change clothes in public bathrooms by standing on it and placing my clothes on it so they wouldn’t be on the ground. He instead laid the garbage bag on top of the garbage can lid and set out my dry clothes, helped me out of my wet soaked rain jacket, hat, and shirts, and handed me my dry shirts followed by some hot packs. He gave me a giant one and told me to stuff it down my shirt, which I did. I took some inhalable insulin (which hits in about 15 minutes), then held the smaller hot packs in my hands while he was pulling out the bag with my replacement pump. I rewound and primed the pump with my existing reservoir and tubing, then reconnected it to my pump site and primed it. That problem (lack of insulin) was now solved, and I knew that my blood glucose would come back down to target over the next hour.

Next up, I could walk/run (or walk) the remaining 1.5 miles back to my normal turn around point, which was a table under a park awning that was relatively dry. I knew that I needed to be warmer and stay dry, and although I had dry clothes on now, I wasn’t sure that sitting outside even with hot packs while I tried to address my feet would warm me up. I told Scott that I wanted to go back to the house (thinking I’d walk the ~1.5 miles to the house). Then I could dry out my feet, get warm, and go back out if I wanted to continue. But I had a hunch I didn’t want to continue. My feet were feeling like they were getting to be in a not-good state from the level of water they had retained after 25 hours, despite all the excellent foot care.

I thought about it and realized that I was satisfied with running 82 miles. I was in otherwise decent physical shape and energy, I had been nailing my electrolytes and fueling and blood sugars the entire run. I had successfully run overnight; more than 24 hours; and by far (2.6x) the longest distance I had ever run. I could keep running to 100 miles (about 18 more miles), but no one cared if I did. I didn’t have to prove anything to anyone, including myself. I had planned, strategized, and executed above and beyond what I had thought was possible, both in terms of physical and mental performance. I had no major injuries, and I wanted to keep it that way. I knew I had the willpower and persistence to keep going; I was stubborn enough to do it; but as the last bit of icing on top of my ultramarathon cake, I wanted to have the mental strength to decide to stop where I was so I wouldn’t create a long-lasting injury in the last 18 miles from sheer stubbornness.

So I stopped. I told Scott I would decide for sure after I got home and dried off and warmed up, but that I was pretty sure this would be a stop and not just a pause. Rather than let me walk home in the rain, he insisted I stay in the warm dry bathroom while he biked home and got the car and brought it to the nearest trail entrance, which was about a quarter of a mile away (more good planning on my part!). Once he had gotten in the car and called me, I slowly walked out to meet him at the parking lot, reaching it right as he pulled in. The walk on my feet confirmed to me that they were done. They weren’t exceptionally blistered or injured, but I knew the cumulative water effect and soggy skin would likely lead to some damage if I continued on them. We headed home. I sat down and took off my socks and shoes and sure enough, my feet were wet, white, and very wrinkly and starting to crease. I took a hot shower then dried off, put hand sanitizer on my feet to help dry them out, and laid down with them sticking out of the covers to help them air out. Within a few hours, they had dried out, and showed me some blisters on the bottom of my right foot that were not really bad, but if I had kept going on them, the wet wrinkly tissue would’ve been very prone to more extreme damage. I reflected on the choice to stop and was still happy with my decision.

The 24 hours after I ran 82 miles

After my shower and laying down, I realized that I was (still) in great physical shape. Some parts of me were starting to stiffen up now that I had stopped, but they hadn’t bothered me at all during running. That was my hips that now hurt if I tried to lay on my side but not on my front or my back; and my thighs felt sore when I straightened and bent my legs. I had never even been tempted during my run to take pain meds because I was never overly sore and didn’t have any injuries.

(Note: you shouldn’t take NSAIDs during extreme events due to the risks of overworked kidneys having problems. I had packed Tylenol, which is acetaminophen, in case I needed it for pain management, but specifically did not pack any oral NSAIDs and warned Scott about offering me any. I did pack topical NSAID *gel* which is an extremely low quantity of NSAID compared to even one oral NSAID pill, and I used that once on my shoulder blades during the run. After my run, I waited several hours and made sure my kidneys were fine via hydration before I took any NSAID.)

It is very surprising to me that despite my longest training runs being almost a third of the distance I did, that I ended up in better physical shape at the end than I did during some training runs! This is probably in part due to going even slower (as planned) during my ultra, but I was really pleased. It might have also been due to the fact that I mentally trained for it to hurt really bad and to continue anyway. Again, lots of mental training and prep.

I ended up napping 2 hours after I got home and showered, and then was awake a few more hours and took another one hour nap. I ate several small meals throughout the day and stayed in bed to rest and not stress my feet further, then went to sleep at a normal bedtime and managed to sleep 9.5 hours through the night. Woohoo! I really wasn’t expecting that. I did wake up many times and find myself bending and flexing my knees or my ankles to help me roll over and could feel them being sore, but it wasn’t painful enough to fully wake me up or keep me from falling back to asleep within seconds, so it felt like a fully rested un-broken night of sleep.

The bottoms of my feet felt weird as they dried out, but progressively felt better and felt close to normal (normal meaning as normal as you are with a routine blister on the bottom of your forefoot) by the time I woke up the next morning (24 hours after ending my run). Everything that stiffened up in the first few hours after I stop has been gradually loosening up, so other than my forefeet still being sensitive with blisters, I’m walking around normally again.

The good, the bad, the ugly, and what I wish I had done differently

I had prepared for so much to go wrong, both those things in my control and things out of my control. And I think that’s why it actually didn’t hurt as much or go as wrong as it could have, despite all the variables in play. I nailed my pacing plan, energy levels, hydration levels, fueling intake, electrolyte intake, and enzyme intake.

I had estimated that I would need to take up to ~160 enzymes to cover my fueling. Remember that I stopped at ~25 hours (82 miles) instead of ~32 hours (100 miles) so I took less than that, but still a lot.

I consumed 50 (fifty!!!) snacks, one every 30 minutes, and swallowed multiple enzyme pills each time. I consumed at least 98 enzyme pills (!!!) in this 25 hour time period. I was concerned that my body wouldn’t be able to digest the pills or have some other issue with them, because I have never taken anywhere near this number of pills in a single day. But, it worked, and flawlessly: I had ZERO EPI-related issues and ZERO other gastrointestinal (GI) symptoms. GI symptoms are super common in ultras, even for people without things like EPI, so I’m incredibly thrilled with how well my planning and practicing paid off so I could execute my fueling plan and not have any issues.

My goal had been to take in ~250 calories per hour and ~500 mg of sodium per hour (from both the snacks every 30 min and electrolyte pills every 45 min). I use calories as my rolling metric because while most ultrarunners prioritize carbs, I’m running slower and likely more fat adapted than most people, and also need digestive enzymes no matter what I’m eating so taking small amounts of fat and protein are fine for me. Plus it makes for more interesting running snacks. So using calories as the global running metric of consumption rather than just carbs or fat etc. works for me. I nailed it, and across all 25 hours of my run I averaged 671 mg of sodium per hour and 279 calories per hour. I did have one hour where I somehow dropped low on sodium and felt it, and took an extra electrolyte pill to help catch up. It fixed the “low on sodium” feeling and I didn’t have any issues again. I had slightly more variability toward the end of the run, but that’s just due to the timing of when I logged it into my spreadsheet (due to the wet-phone issues I described earlier) and the auto-calculation on which hour it falls into; overall I still was maintaining the goal levels every hour.

A graph of calorie consumption, sodium consumption, and carb consumption per hour for all 25 hours of the 82 mile run.

(The purple dotted line is carbs, because I was curious about how that level fluctuated given that I didn’t prioritize my run snacks based on carbs at all. I generally seek <20 grams of carbs per snack but have a few that are closer to 30 grams; otherwise <10 or so grams of fat and however many grams of protein I don’t care).

How do I have all this data? I used my macronutrient spreadsheet as I went, selecting the snack I was going to eat from the drop-down list that then pre-populated the rest of the data in the sheet and updated a pivot table that summarized my rolling totals per hour. It was getting increasingly hard to use my phone in the mega downpour rain in the last few hours, which is why the timing of logging them was a little variable and the numbers look a little more bouncy each hour toward the end, but my consumption was still on time thanks to my every 30 minute phone alarms and so the logging was the only thing that varied and I was still above-goal overall although trending downward slightly.

This spreadsheet means I can also summarize my total consumption across 25 hours: I consumed an eye-popping 817 grams of carbs; 365 grams of fat; 136 grams of protein; 16,775 mg of sodium; and 6,979 total calories. That matched the 98+ enzyme pills (and 33 electrolyte pills, which are 210 mg of sodium each and reflected in the overall sodium counts), so I also swallowed >131 pills in the 25 hour time period running. Wow.

It’s common to end up in a calorie deficit due to the hours and miles that an ultra demand of your body, but my watch estimates I burned around 8,000+ calories (maybe an undercount since it stopped itself a few times), so I didn’t have as big of a deficit as I had originally predicted.

There were so many (50!) opportunities to mess up my digestion, and I didn’t mess up once. I’m really proud of that! I also had such a variety of snack types and textures that even though I was never really hungry, I ate my snacks like clock work and didn’t get major palate fatigue or get to the point that I wanted to stop chewing and needed to switch to my backup list of liquid fuel. The only time I slightly felt off was when I did a Snickers for one snack at the end of my lap and then my next snack was hot mashed potatoes – combined, that was 390 calories (one of my top two hours of calorie consumption) and felt like a little too much food, either because of the calories or the volume of mashed potatoes. It was only a minor annoyance, though, and the feeling passed within another 15 minutes and I didn’t have issues with any other combination of snacks. I did get tired of peanut butter pretzel nuggets, because they’re drier than many of my other snacks and took a lot of water to swallow. So I stopped choosing those in lieu of my other snacks and left those as emergency backups.

Looking back, I wish I could have done something differently about my feet, but I don’t think there’s anything else I could have done. I changed socks and into dry shoes at every single lap. I dried them and tried to draw out water with hand sanitizer and Desitin. I lubricated with Squirrel Nut Butter and Desitin, and overall came out with very few blisters compared to my typical shorter long runs (e.g. 25-30 miles). But we did get 0.72 inches of rain in that 24 hour period, and a lot of it was dumped onto my feet in the 4-7am time period. If I’d had a way of knowing 24 hours in advance exactly when the rain was going to let up with enough confidence to delay the run for a day, it turns out it would’ve been drier, but the forecast before I started running was for similar chances of rain all weekend. The laws of feet physics and the timing was just not good, and that was out of my control. I’ll keep researching other strategies for wet feet management, but I think I had done everything I could, did it well, and it just was what it was.

Overall, I can’t think of anything else I would have changed (other than my training, it would have been swell not to have broken my toe and been not weight bearing for 6 weeks!). Fueling, electrolytes, enzymes, blood sugars, pacing, mental game: flawless. I was even picking up the pace and still running and walking 30:90 second intervals, and I think I would have continued to pick up the pace and pushed it to the finish, estimating that I would have come in under 32 hours overall for 100 miles (around a 19 min/mi average pace overall, or a bit under that).

But I chose to stop at 82 miles, and being willing to do that was a huge mental PR, too.

So I’m pleased, proud, and thrilled to have run an 82 mile ultramarathon, and physically and mentally feel better than I would have predicted would be possible after 24 hours.

What it feels like to run (almost) a 100 mile ultramarathon, by Dana M. Lewis on DIYPS.org

How I Organized Supplies For a 100 Mile Ultramarathon Run

One of the things I read trying to learn about best approaches for running 100 miles (an ultramarathon) is that it’s mostly mental and logistical challenges rather than physical, because after a certain point everyone is running much farther than they’ve ever trained and what makes the difference is how well you deal with the mental and logistical challenges and problem solving when you reach those points. I took that to heart and did a lot of pre-planning for my 100 mile run attempt. You can read more about the other types of prep and decision making that went into this, but the below is a more tactical “here’s how I organized” the different things I had been thinking about for months.

Route Planning and Pace Chart

First, you either need to plan your route (self-organized) or get the course map (organized race). This enables you to start to build out a pace chart. I did this first, because it then informed fueling strategy, planning, etc.

I laid out my route (7 laps, which later turned into 8 planned laps based on re-designing my routes). I had a column for the distance of each lap/segment, then a total distance column. This was mostly to make sure I had my distance add up to > 100 miles; otherwise I don’t care about the rolling distance total. I then built out a pace sheet with what I thought my paces would be. I’m very slow and run/walk, and planned to go as slow as possible at the start to be able to finish the entire distance. So while normally my running might be 14:00-15:30 min/mile pacing, I expected to want to start around 16:00-16:30 min/mi pace and that I’d likely slow over time. As a result, I started my pace chart with a 16min/mi pace and did a 17, 18, 19, 20, and 21 min/mi pace chart for each of my segments. This enabled me to estimate the time it would take to run each lap (segment) at each given pace, and also a clock time that I would be expected to roughly finish that lap.

Example of a 100 mile pace chart, with rows for each segment/lap run and then columns estimating a different minute per mile pace and how that changed the total segment time and clock time for each lap.

I also created a dynamic pacing chart that I could use to simulate different paces throughout my run. This enabled me to estimate what happens if I start fast and slow down a little or a lot and how that influences my overall time and pacing. During my run, my husband as crew updated the actual time to help estimate what my next segment time would be based on both the last segment time and overall pace. This helped him determine when he needed to set an alarm to come back out and meet me, as well as remind him where he was meeting me each time based on the route.

You’ll notice I’ve highlighted to make sure I remember to change the date when I cross over midnight, to make sure the pace chart updates accurately.

(Again, note these are simulated/fake times. The dark shading suggests when it’ll be dark, due to the time of year I’m running.)

Example of a dynamic pacing chart with the ability to enter the date and time I completed each segment or lap, and the right columns updated the segment pace and the overall run pace based on this input.

Fuel, Enzyme, and Electrolyte Estimates

These pace charts were useful for then estimating what I’d need when. Namely, how much fuel I’d need to prepare in bags for my husband to give me for each lap. I used the slower paces for each segment and my plan of fueling every 30 min to determine how much I needed. For example, if I’m fueling every 30 minutes, my second segment is 13.06 miles and I’d probably be running around or below a 17 min/mi pace at that point, which means it’ll be 3.7 hours or so. This is 7 snacks (one every 30 minutes, and I’ll be back before the next snack time for my refill). But, if I run slower, I want to round up slightly and add a snack to that estimate, so I put in 8 needed for that lap. I did that for all laps, rounding to the next hour and/or adding 1 to the estimate.

I also estimated my electrolytes similarly. I drink water and get my sodium and electrolytes via a combination of my fuel and electrolyte pills, with taking electrolyte pills every 45 minutes. Again, I used the slower pace times and the segment time to determine how many electrolyte pills I needed for the segment and listed those out.

Then, you’ll notice I also estimated “enzyme” needs. I have exocrine pancreatic insufficiency, known as EPI, which means I have to swallow enzymes anytime I eat anything to help my body digest it. Fun, right? Especially when I’m eating every 30 minutes across a 100 mile run and how many enzymes I need to take depends on what I’m eating! I typically take two (one each of two types) over the counter enzymes for a snack; although some bigger snacks I can take 2-3. Therefore, I estimated one per snack plus a few snacks where I’d take the 2-3, and also factored in dropping a few (it happens). It adds up to ~118 enzymes but again, that’s a lot of extra added in so I don’t have to worry about running out if I drop some or eat bigger snacks.  I calculated I’d probably end up consuming closer to ~80 of each type (so 160-ish total) across the 100 miles.

Another chart with the lap segment numbers and in columns to the right, estimates for the number of snacks, enzyme pills, and electrolyte pills for each segment. Totals of each type (snack, electrolyte, enzyme pills) are at the bottom of the chart.

Deciding What I Want to Eat, When

Next, I took these snack per segment estimates and decided what I actually wanted to eat. Based on my training, I ruled out some foods and perfected my list of what I wanted to eat and had practiced.

I listed all my preferred snacks down a column, then listed out the laps/segments in the row at the top. I then started playing around with what I wanted to eat at different times. Knowing I’d probably get tired of chewing crunchy things (for me it’s not the chewing but the texture of the harder things in my mouth), I put things like my chili cheese Fritos and peanut butter pretzel nuggets toward the first few laps. Later laps got easier to chew/swallow items like peanut butter M&M, fruit snacks, etc.

At the bottom you’ll notice I have a few different columns. A lot of the snacks indicated with numbers are ones that are shelf-stable and pre-packed. Others are snacks that are at home in the fridge or freezer or require prep (like mashed potatoes). I have a variety of quantities of those prepared (see right side of table) so I can choose any combination of 2 of those for my husband to bring out each lap, in addition to the pre-packed shelf-stable snacks. The bottom combinations make sure I have enough snacks between the pre-packed snacks and 2 fresh snacks every time, based on the above chart I had made to estimate how many snacks I needed for each segment.

A chart listing snack types in a row on the left; then the headers of the columns to the right list each lap number. Down the chart are numbers representing that snack and how many for each lap. A section at the bottom totals up the pre-packaged snacks per lap, as well as a row indicating that two extra home/hot snacks will be added, to estimate the total number of snacks I'll have for each segment or lap.

The other reason this chart is helpful is that I know how many extras of everything I have at home, too. So while I have certain amounts prepped and packed per column Z; column AA notes the extras I have pre-packaged and sitting at home, so if I get tired in lap 3 of beef sticks and want to not eat those, I can figure out what other 4 snacks I want that I have prepped and have my husband bring those alternatives.

One other note for nutrition and macronutrients: I use a macronutrient fueling tracking spreadsheet to help me track my calorie intake as well as sodium intake, to make sure I’m getting enough on a rolling basis. It also helps me figure out how many enzymes to take for each snack, if I don’t know it off hand or my brain forgets (as it might after running for 20+ hours!). You can read more about how I built and use this fueling spreadsheet here.

Planning Supplies

Over the last few months and especially the last training runs, I built a list/library of likely common issues I experienced or had learned about by reading other people’s race recaps and reports that I wanted to be prepared for. I organized it by type of problem, then listed potential supplies and solutions. For example, I had a blisters/feet section; low sodium; high or low blood glucose (because I have type 1 diabetes); etc.

The solutions list here is unique to me/how I solve things, but here’s an example of what I would include:

  • Sodium
    • More electrolyte pills more frequently than 45 min
    • Short term fix: Chicken broth (¼ is 530mg sodium. Entire thing is 2120mg)
    • Less sodium but variety: GZero (no carb) gatorade sips – whole bottle 270mg

I then also started a separate document for 100M Prep. This included a long checklist of all the items I had brainstormed as solutions – so in the above sodium example, it included extra electrolyte pills; chicken broth; Gatorade Zero; etc.

A screenshot of my 100 mile prep document showing the sodium section with chicken broth, electrolyte pills, and gatorade zero checked off the list, as I had already packed them.

This became helpful for me to a) make sure I had these things at home and to get them if I didn’t have them yet and b) to make sure I had set them out/organized them prior to my run so they’d be easily accessible for my husband to find.

The 100M Prep document also helped me break down larger tasks, too. Instead of “blister kit”, I started a sub-list that described everything I wanted in that baggie.

A contact case with a strip of purple painter tape that has "vaseline" written on it in sharpie; and three lip gloss tubes filled and marked with "NSAID", "salt", and "desitin".

This also helped me realize when I needed to add a task for splitting supplies. For example, if I had a big tube of cream or ointment that I possibly wanted to be in two places (such as a certain type of foot lubricant). I had previously bought a bag of empty lip gloss tubes for making travel size toiletries (shampoo, face wash, etc.). I realized that they also worked great for liquid, gel, cream supplies for ultra running, too. And so I added tasks for splitting those into smaller tubes once I decided and listed where they should go and thus how many I needed.

I also had a checklist for each lap bag, which is a combination of which snacks (planned above) and other supplies (like eye drops) that I wanted to have each time. I made a checklist for each lap, then laid out all my supplies and checked them off the list for each lap. Once I had all the supplies laid out, I then compiled them into one bag for each lap and added a label. This way my husband has one bag to bring for each lap, and there is a sticky note on top of each bag that has anything else (e.g. 2 fresh food items from home) he needs to add and bring that lap.

Laid out on the floor are baggies with enzymes and electrolyte pills for each lap; snacks surround the baggies. There are also individual pre-pasted toothbrushes and individual eye drop containers.

(Again, this is planned food, electrolytes, and enzymes for each lap. See the above section to see how I estimated the food/snacks, electrolytes, and enzyme needs.)

A gallon bag containing the enzymes, electrolytes, and snacks for each lap of my ultramarathon. Atop the bag is a printed sticky note with reminders of other fresh supplies my husband will bring each time.

I had started a list in a PDF for each lap, then printed the list for each lap on a sticky note so I could easily tape it to the bag and it would be easy for my husband to read.

Editor/Husband/Crew note from Scott: “These pre-prepped lap bags and printed sticky notes turned out to be most useful for making sure I got everything prepped each time. When I got home after each pit stop, I would pull out the next lap bag and make sure I had everything charging/washing/drying that I’d need at the next pit stop. Then when it got close to time to go, I’d work down the checklist, collecting each thing and putting it in my bike’s saddlebags, and then put the lap bag on top when I had everything packed.”

Crew Checklist

The same document as the overall solutions list became my Crew Checklist document. I added a checklist for what we should be doing at each lap. Again, this is unique to me, but it included things like putting my watch on the charger; removing trash from my vest; replacing water and ice in my hydration pack; replacing my battery for charging my phone; putting my fuel/enzymes/electrolytes into my vest and using eye drops; swapping socks; seeing if I need replacement supplies for low blood glucose; and after midnight considering whether I wanted to drink a Diet Mtn Dew for joy and caffeine.

A checklist in a Google Doc listing what my husband should make sure we do in between every lap, such as removed trash, replace water and ice and fuel, and make sure I have enzymes and electrolytes before I head out. It also reminds him to update the pacing spreadsheet with my latest lap time, and links to all spreadsheets he needs.

You’ll also spot the section I added for my husband for after he gets home to remember to charge batteries on various things, use the pacing spreadsheet to help him figure out when to come back out, etc.

At the bottom of my crew document (the lap checklist is at the top, followed by the comprehensive solutions list), I also included an example pep talk section with constructive things to say. If there’s things you don’t want your crew to say (e.g. “you’re almost there!” or “only X hours left” are on my ‘please no’ list), you can also list those out. I also have my list of run-ending situations that my husband and I agreed upon, which includes things like having a broken bone; severe dehydration or peeing blood; hypothermia; etc.

And finally in the document at the very bottom, I created a checklist for post-race care so when I get home and everything feels terrible and I don’t know what to do, my husband has my pre-thought-of checklist of things in the best order (shower then compression sleeves; making sure I eat something within an hour of finishing; etc) to help me do all the self-care things I’m probably going to forget about.

Editor/Husband/Crew note from Scott: “Peace-time plans are of no particular value, but peace-time planning is indispensable” and “No plan of operations extends with any certainty beyond the first encounter with the main enemy forces.”

– This particular document ended most useful for pre-race planning purposes, including our night-before review of all the plans. I glanced at it a couple times during the race, but mostly relied on the lap-bag checklist and the physical presence of items in my saddlebags at the pit stops.

DanaWatch

The other thing I had prepared was a document with instructions for friends who had agreed to help out during the overnight hours for me. My husband was “on call” and crewing the whole time, but overnight there were sections where I was out running 3-4 hours and he needed those times to sleep. For those hours, we set up “DanaWatch” (as I call it), with a friend who will text me every half hour or so to check on me. If they don’t get a text back (a simple emoji or other text from my watch), they were to call me, and if they couldn’t reach me, they’d call Scott. So, the document has these instructions, an outline of my safety plan, Scott’s number, etc. so everyone knows what the plan is. I had friends staggered over different times. For example, a friend in the UK was to text me starting around 8am his time, which is midnight for me. When another friend wakes up on the east coast (three hours ahead of me), she’d starting texting me, and so on. This way I wouldn’t feel “alone” and would have extra folks watching out to make sure I’m still on track.

I think that’s everything I did to prep in advance! Mainly, having those documents built to add ideas to (especially problems and troubleshooting solutions) and building out my pace chart so I could progressively make my fuel, electrolyte, enzyme and supply plans in advance was really helpful. Then I blocked off time the week before my run to make sure I had everything prepped and ready to go well before the day before my race, so I wasn’t stressed about getting ready. As I described in my other preparation for ultra post, anything I could do to limit stress and mitigate decision-making fatigue, I did. And it definitely helped!

How I Organized Supplies for a 100 mile (or similarly long) ultramarathon

How To Prepare Or Plan For A 100 Mile Ultramarathon (Or Similarly Long Ultra Run)

As I prepared for months for my first-ever 100 mile run, I did a lot of research to figure out how I should be prepared. There’s no one way to “prepare” for an ultramarathon of any distance, and much of the stuff online is about your training plan and physical preparations. Which is definitely important, but not the only thing that needs preparation.

After a lot of reading, thinking about my own plans and preparation, I’ve realized there are 4 general types of preparation for an ultramarathon that I’ve been doing: mental preparation and training; nutrition preparation and training; race day strategy preparation; and the actual physical training and running to prepare for an ultramarathon.

Usually, blog posts either cover the last category (training plans and physical training philosophies) or one of the other categories. This blog post summarizes everything I’ve done in all of these categories together in one place – in part to help me if I ever run another ultra following my first 100 mile attempt!

Almost everything I thought about and planned for a 100 mile ultramarathon, by Dana M. Lewis on DIYPS.org
  1. Mental preparation and training

It’s commonly said online that running 100 miles (or most ultra distances) is 80% mental and only 20% physical. (Or similar splits like 90/10). This is in part because it is not feasible to physically train to run the distance prior to your race (usually); and the first time you tackle a new distance, you always have many (often dozens!) of miles of distance that you’ve never covered before. It’s going to be uncomfortable, and you have to plan for that. Thus, mental preparation and training as much as possible to be prepared to deal with these challenges.

The first major aspect of this, for me, is practicing and reminding my brain how to process and work through discomfort. Discomfort is distinct from pain and being injured. (Pain and an injury should include evaluating whether you should cease your activity.) I’ve fortunately (and unfortunately) had recent experiences of pain when I broke my toe. Returning to walking and then running involved some discomfort as my body got used to covering miles again. It was a very distinct feeling that was not easily confused with pain from a broken bone, which to me feels like an “electrical” type of feeling.

This recent experience with pain is easy to differentiate from the discomfort of running long distances and being tired and sore. I’m working to capture these thoughts when I have them, and transition from “I’m tired and this hurts and this is terrible” during training runs and convert these thought patterns to “I’m tired and uncomfortable. But this is not pain; this is discomfort. This is how I’m going to feel at mile 34 or 57 or the back half of my 100M, and I’m going to keep running then and I’m going to keep running now to practice this feeling.” I want to register and save this feeling and mental state for what it’ll feel like during my 100M, so it’s easier to pull that out when I’m exhausted and uncomfortable at 3am and still likely have another 40-50 miles to go.

Similarly, I also try to envision different scenarios that I will experience in my “race” or 100 mile experience. In my case, I plan to run on a paved trail for a solo endeavor (DIY or self-organized, rather than an organized race with other people). Some of the scenarios I am expecting to experience and deal with include:

  • I will be running a course with 7 “laps” or loops of various lengths. This involves me coming back to the same point seven times so that I can get re-fueled by my crew (my husband), change clothes if needed, etc. I envision coming in for my second or third lap, having to turn around to head back out for another (but not my last) lap and not wanting to leave.
    • How I planned to deal with this scenario: I’ve written down crew instructions for my husband, which include how to refuel and replenish my supplies; a list of troubleshooting scenarios and supplies; but also specific things that would be constructive to say to me. In this instance, any of the following:
      • You are strong and you can do this.
      • You only have to do the current lap.
      • Walk as much as you need to.
  • This 100M will be one of the first times (other than a training run where I practice the transition) running all day and into the the night. I’m a little apprehensive about this idea of running for 14 hours in the dark (due to the time of year). Partially, this is because I’ve never run 14 hours before, and I’ll be doing it after already having run for 10 or so hours! And because I’m not as experienced running in the dark.
    • How I planned to deal with this scenario: I have a clear set of “day to night” transition supplies and instructions to gear up for the night. I will be equipped with reflective components on my vest; a bright colored shirt; a waist lamp; a head lamp; a blinky red light on the back of my vest. I will focus on getting geared up and recognizing that it’s a mental transition as well as a physical gear transition. I will also try to think about the novelty and adventure aspects of running through the night. It’ll probably be wet and cloudy – but it might clear up in patches enough to see some stars! And – the running through the night is something I didn’t think I could do, which is actually why I’m doing a 100M, to prove to myself that I can do anything I want to set my mind to. This is the purpose of being out here, and it’s a necessary part of achieving 100M.
  • At some point, most people do a lot of walking. I’m fairly unique in my “running” approach – I run/walk from the start, and also not like many people run/walk. In ultras, most folks walk every X minutes or when they reach hills. I consistently run/walk with 30s of running, then 60s or 90s of walking – from the very start. These are short intervals, but it’s what works well for me. But like everyone else, regardless of initial strategy, I expect there will be a time where it might be more efficient to try a brisk, consistent walk for a few minutes (or miles!), or a slow slog (inefficient walk) because that’s all I can convince myself to do.
    • How I planned to deal with this scenario: The goal is forward motion, however I can move. Walking is ok, and expected – and I will remind myself of that. I know there is a crossover point when running speed slows down to a certain degree and running becomes as efficient at a certain point. I also know these points, speeds, and effort levels will change throughout my 100M. It helps that I’m already a proactive walker; I have no shame, guilt, or hangups related to walking because it’s ½ or ⅔ of my forward motion strategy from the start! But I will remind myself that my plans for intervals can change and I can experiment to see what feels good throughout.
  • It’s possible that I could trip and fall, especially as I get tired and scuffle my feet on the trail, even though I’m on the paved trail. I also might get swooped by an owl or startled by something which causes me to trip and fall unexpectedly.
    • How I planned to deal with this scenario: I’ve got my safety plan in place (more on that below) and know I will first while on the ground disable the alarm on my watch so it does not call 911 (assuming this doesn’t appear to be needed). I will move my body to see if I’m just sore or if there are any scrapes or injuries that need addressing. I will stand up if possible, continuing to check myself out. I will slowly walk, if possible, and see how I feel. I’ll also probably call and let my husband know, and either ask him to come meet me earlier than expected that lap or just let him know so he can check on me when we meet up as planned. I will let myself walk any soreness off for a while (and turn off my interval alerts) before resuming a planned run/walk strategy.

So these are some of the scenarios I’m envisioning dealing with and my plans for them, with the hope and expectation that my brain will be better equipped to deal with them as a result of thinking about them in advance.

Depending on your race/route/plans, you might need to add other types of scenarios – such as leaving the aid station with warmth and light before heading into the night; or what to do if your crew doesn’t show up as planned; or your drop bag gets soaked with water; or the aid station is out of supplies or there is no one where you expect an aid station.

The other part of my mental preparation is a lot of pre-problem solving. Similar to the above scenarios, I have thought through what I need to do for the following:

  • I drop my fuel, enzymes, or electrolytes and can’t find them.
    • How I planned to deal with this scenario: I will call or text my husband and adjust plans for where he meets me. I will use the backup fuel supplies in my pack as needed to tide me over. (For my race, I have fuel in individual baggies and separated out for each “lap” or segment, plus extras and backups, so my husband can grab the backup bag or the next lap bag and bring it to me.)
  • I run out of water.
    • How I planned to deal with this scenario: There are 3-4 water fountains along or nearby my planned run route, and I can re-fill my hydration bladder within ~3 miles from any spot on the trail. I can also again call my husband and have him meet me sooner to re-fill my hydration pack.
  • My stomach gets upset.
    • How I planned to deal with this scenario: I have supplies (such as Immodium, GasX, Tums, etc) in my running pack that I can use. I also have more supplies laid out at home that I can ask my husband to bring.
  • I don’t feel like eating.
    • How I planned to deal with this scenario: I included this on the list because I read that it happens to a lot of people. But, as a person with type 1 diabetes…I have 20 years of practice of consuming sugar or food when my blood sugar is dropping or low, even when I’m not hungry. I have also practiced consistently fueling throughout my long runs, and I am used to eating when not hungry. I expect it is more likely that I will get tired of certain textures, so I have planned out my fuel so that “harder to chew” or crunchy foods that might hurt my mouth are the snacks I eat earlier, and then eat softer snacks or snacks that require less chewing later in the run. I also have a variety of backups that include different textures and some liquid options that I can substitute for my planned fuel.
  • Other scenarios I’ve pre-problem-solved are getting blisters or sore spots on my feet; chafing; getting low on sodium/electrolytes; muscles hurting on other parts of my body other than my feet; having feet that swell; getting itchy or having other types of allergic reactions; having trouble breathing; my eyes hurting; being really tired; being hot or cold or wet; my blood sugar staying higher or lower for a longer period of time; and mentally feeling “low” and unmotivated and wavering in the pursuit of my goal.
    • How I planned to deal with this scenario: As part of the ‘crew instruction’ list I’ve made for my husband, I have listed out all the supplies I have to address these categories. I will also have all of these supplies grouped and set out at home. My husband is awesome at troubleshooting problems in general, but he’ll also be tired at 2 am after only sleeping for 2 hours (plus I will be tired), so I created this to help me prep all the gear but also when I tell him “I’m ____”, he can offer the requisite supplies to address the problem without me having to try to figure out what my options are and decide what to do. All of this is to help mitigate the decision fatigue I will have and the overall fatigue he will have.
    • Note: I’ve also previously read a really good tip about managing decision fatigue. Tell your crew – in my case I’ve told my husband and written it onto the crew sheet – not to ask open-ended question, but to offer specific suggestions or options. For example, say “Do you want 2 or 2.5 liters of water in your hydration pack?” instead of “How much water do you want?”. For refilling my snacks, I’ve told my husband to refill my snack pack from the pre-filled bags, but the bag also has a sticky note about grabbing fresh prepared food. I told him to specifically ask “Do you want your waffle; sweet potato tots; mashed potatoes; or” (whatever is on my list of pre-prepared food for him to make and bring), instead of “What do you want?”

A lot of these I put on my list to think about based on race reports I’ve read from other people, that covers what they experienced (e.g. feet swelling and finding it helpful to have a half size bigger shoe to change into) and how they troubleshot things during the race while in between or at aid stations.

Some of my favorite race reports/blogs that I’ve learned a lot from include Rebecca Walker’s race reports; Wes Plate’s race recaps; Debbie Norman’s race reports (check out her sample crew sheet in that linked post); Bob Hearn’s thoughtfulness around pacing and walk strategy; and Sarah Lavender Smith’s race reports.

I have learned quite a bit and improved my planning and preparation by reading race reports of DNFs and also of finished races of different lengths. The longer the race, the more challenges there are and the more time to learn and sort them out. So that’s why I appreciate reading Wes’s multi day (eg 240 mile) recaps as well as 100 mile race reports, even though my focus has been on 50ks previously and now “just” a 100M.

One other thing I’ve thought about is the importance of knowing what your criteria for quitting/stopping/DNFing. For me this links back to discomfort versus pain. An injury should involve stopping temporarily and maybe permanently. But being tired, sore, uncomfortable – for me those should not qualify as reasons to stop. My goal is not to stop before 100 miles unless I have an actual injury (eg broken toe level pain).

2. Nutrition preparation and training

Yes, it’s worth “training” your nutrition. This means training your body by practicing fueling with the same foods and strategies as you want to use on your race. There’s a mantra of “nothing new on race day” that is both useful and not applicable to ultrarunning. In general, a lot of ultrarunners seem to do well (per my above search through many race reports) with eating small portions of “whatever looks good” at aid stations. If it looks good, their body is probably going to deal with it ok. But not always. And a lot of time people will bring fuel and rely on things they haven’t tested on their long runs prior to race day. Don’t be that person!

  • Test your fueling options and strategy (e.g. timing of fueling) on most runs, not just your very longest runs. For me, I do fuel for any runs of 2 hours or longer, because that correlates with when I bother to bring hydration and therefore also bring fuel. (That’s 8 miles for me at an average 15min/mile pace). Some folks use 1 hour or an hour and a half as their cutoff. But the point is – don’t just test your fuel on 6 hour runs. Fueling on shorter runs helps those runs feel better; you’ll likely recover from those runs more quickly; and it helps your body practice with those fueling options. You don’t want to find out at hour 8 of your 36 hour race that your body doesn’t do well with ___. It’s better to find that out at hour 3 of a 4 hour run, or similar.
  • Create your list of fuel that works for you. This should be based on your preferences but also how it helps you meet your fueling goals. When you have an idea for a new fuel, make sure you take it on your next run and try it. If you’re like me, you might want to try it near the end of your run, just in case your body doesn’t like it while running. If your body doesn’t like it, cross it off your list. You don’t want to be hauling or trying to eat food you know your body doesn’t like during a 100 mile run! I’ve found some things that I like to eat and found tasty fresh out of the oven – like ½ of a GF banana bread muffin – felt terrible in my mouth during runs. Some combination of the dry muffin (vs. freshly moist out of the oven) and the taste was not ideal for me. I ate it, and didn’t have GI distress, but I got home and promptly moved the remaining half portioned muffin baggies to my husband’s section of the fridge/freezer where my snack rejects go, and crossed it off my list. If it doesn’t bring you joy, or if it makes your brain cranky, it’s probably not a food you want for your ultra.
  • Don’t feel like there is a “wrong” food, as long as it’s something that’s not going to spoil easy or melt or be too hard to eat on the go. Look at snacks and meals you like to eat; is there a serving size or a variation that you like to eat? If so, try it! People eat all sorts of things in ultras, from puréed fruits and vegetables like applesauce or baby food pouches, to candy and chips to hamburgers and soup. Walk the store aisles (physically or virtually) and get ideas for food to try. But don’t limit yourself to sports “products” like blocks, gels, gu, drink mix, and similar. You’d be surprised about the variety of food that is portable, and in individual portions is close to the same macronutrients (calories, carbs, fat or protein, sodium, etc) as more expensive sports products. A lot of time you are paying for convenience and a certain texture/delivery method. But you can achieve the same intake of macronutrients through a variety of foods and beverages.
  • Some people stick with 1-2 foods or fuel sources (like liquid calorie/electrolyte solutions or gels/gu/blocks), but get tired of the sweet taste or the taste/texture of what they’re eating. Having a variety can help with this. Make your list, and for each run make sure you’re working through trying out and approving or removing the foods that you want to use during your race. Ideally, try them 1-2 times before your big run.
  • If you can, practice with some of the aid station type food including warm food (eg quesadilla or burger or whatever). Have someone meet you on longest runs with this freshly prepared, or take it with you and eat it for your first fuel. (Watch out for food spoiling/going bad – I always eat the hot/fresh prepared stuff first out of my set of fuel options when I get my pack refueled, to reduce the chance of bacteria growing or the food otherwise spoiling.) This is harder to do and may not be possible, but it could help expand your options for what you’re willing to take at aid stations if you’ve tested a version of a similar food before during a training run.
  • More planning ahead on nutrition for race day and training runs: figure out your timing of nutrition strategy and how many snacks or how much fuel (liquid or otherwise) you need to consume each hour or segment or between aid station. Pre-portion your fuel/snacks and if possible, label them. Plans can change and you can adapt on the fly, but having everything pre-portioned and ready to go means you can more easily start your training runs, fill your drop bags, or prep bags for your crew by having everything portioned out.
  • Planning ahead also means you get to the store or order however much you need so you’re not adding stress the last few days before you race or run in order to have your fuel set up and ready to go.
  • Don’t be afraid to use a timer. Some people wear running GPS watches that have alert/alarm features for fueling. You can use regular phone alarms, too, or apps like “Timer+” or “Intervals Pro” – both are ios apps that have free versions that allow one alarm each. You can choose whether it pushes a notification to your phone or watch or provides a verbal audio alert. I use both these apps and have one alarm that’s verbal audio reminding me to take electrolytes every 45 minutes; and the other one is a push-notification only that helps me remember to fuel roughly every 30 minutes. I generally am checking my watch so it’s easier to remember to fuel every :30 and 1:00 from when I start running, which is why I choose that one to be a push notification just in case. That works for me, but figure out your ideal timing and alert/alarm strategy to help you remember to fuel and electrolyte as you need to.

If anyone is curious about my individual approach to nutrition, I’ve written a bit more about it here, including how and why I actually use a spreadsheet to track nutrition and fueling during ultras and training runs. I separate my hydration (water only) and electrolytes (electrolyte pills; plus tracking the sodium in what I’m eating), so tracking my fueling serves many goals both during a run and after a run when I can look back and see if I need to tweak anything (such as not putting two smaller/lower-calorie, lower-sodium snacks back to back).

Since I’m running my ultra solo/DIY, I’m taking advantage of some fresh/heated fuel options, like mashed potatoes, ¼ of a ham and cheese (gluten-free) quesadilla, etc. For these, I am leaving a pre-printed sticky note on the baggie of shelf-stable fuel with a reminder for my husband to bring 2 of my fresh/hot options each time as well as anything else I need him to bring for that lap. To aid the bringing of the fresh/home food, I made a printed set of instructions that lists what these are, broken down by location (freezer, fridge, or on the counter) and instructions on how to make them. This is a critical step because what he predicts I want or how I want something to be cooked or prepped for a run doesn’t always match what I was wanting or expecting. Having clear instructions he can follow (eg heat ¼ quesadilla in microwave for 30s) works well for both of us and further helps with limiting his decision/processing fatigue since he’ll be responsible for grabbing and making 2 things; getting the lap bag of refuel; packing up ice and water; and getting all that and any other requested supplies out to the trail on time to refuel me as I pass by again.

If you have crew, think similarly about what food you want to have; how they’ll make it and serve it to you; how you’ll consume it at the aid station or as you move along on the trail. All of this planning will pay off.

(Another benefit of my macronutrient/fuel tracking spreadsheet is that my husband has access to it and can check it to see if I’m sticking to my fueling and electrolyte strategy, so he can troubleshoot and recommend things if I need support in fixing a problem. I don’t think he’ll use it much, but this secondary use of the spreadsheet was inspired by one of Heather Hart’s many excellent ultra posts talking about showing her empty fuel wrappers to her crew to prove that she was fueling. In my case, instead of counting wrappers, my husband can check my spreadsheet.)

3. Race day strategy (and pre-race and post-race strategy)

Continuing on the theme of pre-planning and laying out your strategy, I also think about strategy related to race day and leading up to race day as well as after race day.

My goal is to eliminate stress; pre-do as much work as I can physically and mentally to reduce the load when I will be physically and cognitively fatigued and overloaded.

Pre-race

For example, I look at my schedule prior to the race and try to clear out stressful activities (or prevent scheduling them, if possible). I know I’ll need to spend hours physically prepping (per above, making fuel and organizing supplies), so I put that on a to-do list and make a block of time on my calendar for it. I think about tasks that I will have before and after the race, such as changing my continuous glucose monitor (CGM) and pump sites to be in optimal locations on my body for the race; but also changing them early enough prior to the race so that they are settled in and I know they are working well. I also do things like pre-fill my reservoirs with insulin, and do enough reservoirs for a few days before and a week or so after the race. Like during the race, anything I can do to help reduce cognitive fatigue or pre-do steps of tasks that I know I will find harder to do is the goal.

This includes also blocking off my schedule with reminders to go to bed earlier. I think about when I’ll be waking up on race day and the night before, set my bedtime reminder for about 8 hours prior. Then every day before that I set it 15 minutes later, working back about a week and a half. I don’t always hit these sleep times, but progressively slightly shifting my sleep like this has been effective prior to international trips with a lot of time zone changes and also has paid off for getting a better night’s sleep the night or two before a race that involves waking up early.

I also specifically think through all the steps from waking up to starting my race, and how to optimize those. I eat a particular breakfast prior to the race, time it so that I can best get some macronutrients in, and time the insulin so I don’t have much of a BG spike but also then don’t have much insulin activity happening when I start my run. I don’t always get this right, but I attempt to line up my schedule so that I wake up and immediately eat what I have laid out on my bedside table and start hydrating, so that I can sleep as long as possible and don’t have to spend extra minutes convincing myself to get out of bed to go make breakfast. Some of these strategies are unique to me being a person with insulin-requiring (in my case, type 1) diabetes; but it’s pretty common for other ultrarunners to have strategies around what to eat the morning before a race; how many hours prior to the race; etc. I’d suggest you decide based on first principles and your own knowledge what to do for you.

Pro tip/personal vent: most people who blog or write about “avoiding insulin spikes” prior to the race or during the race – if they don’t actually administer exogenous insulin (aka inject or pump it, their pancreas makes it) – they also don’t usually actually know anything about the insulin response to food in their body. They are mostly repeating that from hearing it from others who repeat it from a long chain of people. You are SUPPOSED to spike insulin in response to what you’re eating: that’s good because it manages your blood glucose levels and helps your body process and store what it needs to be storing. It is also very normal for your blood sugar to rise in response to eating. The only people who need to think about “insulin spikes” are people who don’t think about it as insulin “spikes” but as insulin activity or more commonly “insulin on board” (IOB), which are people with insulin-requiring diabetes. This is different for us because we have to inject/pump insulin separately (our pancreases don’t make it on demand in response to sensing food in our bodies) AND because the insulin we use takes longer to act – 45-60 minutes instead of mere minutes – as well as has an hours-long “tail” effect. So it’s a lot of work to match the peak timing of insulin to the impact of different types of food in our bodies as well as watching out for insulin “stacking” over the many-hour activity curve for each dose. Your body, if you don’t have insulin-requiring diabetes? It does this, on its own, like magic. Yay, you! So ignore the stuff about “avoiding insulin spikes” and focus instead on things like whether the food feels heavy in your stomach when you run or gives you GI distress or otherwise doesn’t make you feel good. If it doesn’t, try different food and try different timing.

4. Race start and race strategy

You should definitely have a plan for how you run your race. In my case, because I’m a run/walker, I think about which set of intervals I will start at (likely 30:90, meaning 30s run and 90s walk, because that’s also how I train and helps me achieve my easy effort and easy paces). My goal is to start easy and limit excitement. Since I’m solo running, I don’t get swept up in other people running and racing. But, I always find the start and the first mile to be hard. So my strategy instead is to start, make sure all my intervals and run trackers are turned on; my electrolyte and fuel timers are set; and that I get my audiobook or podcast going. I troubleshoot any of these as needed on the walk intervals as I get going. I specifically try not to think about pace, especially the first half mile, nor how it’s feeling so I don’t catastrophize. I know the first 0.75 miles or so always feels pretty rough, so I aim to do no foreshadowing of how anything else is going to feel.

For most people running organized races, it helps to have studied the course maps and elevation profiles. Learn the course by heart, in terms of knowing how many miles to each aid station and what the elevation profile is like, and what your strategy is for each section. This means having a pace plan from the start and if you are going way too fast (due to excitement and other people around you), switching to walk breaks to help moderate your pace if you can’t slow your run pace down on its own. It also might help to not only have a pace plan but to also put time estimates on aid stations or check points. Use any extra time – especially if you are far ahead – to address any issues popping up (chafing, blisters or hot spots on your feet, etc.). Don’t start foreshadowing and forecasting that you can hold this too-fast pace through the whole race. You likely can’t (physically), and skipping the plan to stop and address issues will also doubly backfire later.

Even though I’m not running an organized race, this is still something I struggle with. I’m setting the goal to stop for bathroom breaks or shoe re-lacing or hotspot fixing in the first out and back “lap”, recognizing that it will help get my average time here to slow down a bit and keep me from powering through it too hard based on initial excitement. My goal is to make sure I don’t skimp on self-support (e.g. foot care or re-applying anti-chafe) by folding that it in to my goal pacing.

In general, though, because I’m running a 7 “lap” course, I focus on each lap. And only that lap. I’m running known out-and-back or triangle shaped “loops” that I know and love, so I can treat the first out-and-back like a long extra-easy run and settle in to watch landmarks while I listen to my audiobook and focus solely on managing effort. When I get back after the first loop and refill my vest, I then can think about the lap that I’m on (13 miles next, a much shorter loop). When I’m back, then I think about the next out and back (about 16 miles). And so on. My goal is to never think about how much time or distance is left. I’m not good at “running the mile I’m in”, as people often advise, but I am fairly good at focusing on a sub-component and the process overall. So focusing on each lap, and knowing there are 7 laps of varying lengths, helps me compartmentalize the experience. I’ll run ¼ of the first out and back in the dark and transition into the daylight; the second lap should also be during the day; then I’ll transition to my night gear for the third lap and be in the dark on the 4th, 5th, and 6th lap. I don’t have aid stations or elevation changes to really break up the course, but since I know the course and all the landmarks well, even with the variable distance “laps”, that aids me in knowing what to watch for and keep moving toward, even if I transition to a walk or get off track pace-wise from problem solving and am trying to re-orient myself again afterward.

It’s good to think about what supplies you’ll carry versus what you will have access to at aid stations, what you have in drop bags, and what your crew will have. I generally carry most of my needed first-aid/don’t feel good supplies on me: anti-chafing, kinesio tape for blisters or muscles, anti-nausea medication, etc. But I have a set of supplies prepped and ready for my husband (who is my crew) to bring to me if needed. I won’t have aid stations, so I think about my planned re-fuel stops as aid stations where he’ll primarily be. If something gets really bad, though, he can bike out to meet me. In some races you may have crew access to the trails wherever you need them; in other races, they are not allowed or able to access you outside designated points. Plan and carry supplies accordingly.

And, plan for your crew how to help you and how you’ll communicate with them. I will have cell service on my run, so I plan to text my husband to give him updates (in addition, he can geo-track my phone’s location) of when I’m on or off the last predicted pace to a refuel stop; what I want him to bring (e.g. the 2 hot/fresh food items, or any extra supplies from my laid-out stash); and how it’s going. We have practiced on training runs for him to grab my vest and refill ice and water, fuel, electrolytes/enzymes/eye drops, then bring it back to me (biking) or when I re-pass him after I’ve turned around and come back to the spot where he is per my course plan. But I also expect him, as crew, to also get tired and mentally fatigued, so I’ve made a checklist that he will use to make sure he completes the steps every lap. There’s also a checklist for day to night transition and night to day transition. This is in the same online document as my expert list of supplies and strategies to troubleshoot every issues, so he doesn’t have to guess what the good options are for fixing blisters or low sodium or whatever the issue may be. He runs, but he doesn’t do ultra runs, and regardless everyone is different in terms of what works for them and especially what works for them at different stages of an ultra; thus, having this crew guide or checklist or supply/strategy “cheatsheet” is a benefit, especially as both he and I get more and more tired through the night.

My strategy also includes making sure my devices stay powered. I always carry a small battery and a charging cord for my phone, and will keep my phone power topped off. This is because I use it for run tracking; geolocation for my crew (husband); fuel/electrolyte reminders; fuel tracking via my spreadsheet; and it is the “receiver” for my CGM so I know what my blood sugars are. Thus, it’s a mission-critical device and I always like to keep it charged. I will also grab a watch charger from my husband after a certain number of laps to top off the charge on my watch 1-2x, based on how it’s battery is doing. He’ll replace the battery in my vest each time after I’ve used it (we’ve got 2-3 small batteries for this purpose so he can take one home and re-charge it while I’m using the other, plus another backup). My phone then also serves as an emergency back-up light if my other two lights fail at night.

Speaking of lights and night gear, have a plan for when and how you’ll transition to night gear. Because I’m running a solo/DIY race and I’m not experienced at running at night (although I’ll do a run or two in training to practice the transition and my gear), I’m actually choosing to start my run at 6am so I run about 1.5-2 hours in the dark at the start of my race. Why? My husband doesn’t believe it’s necessary and is still arguing with me about it, but my strategy is intentional. I want to start the run in my lights and night gear and practice running in the dark again so that I can see if I need to tweak or adjust it for later that night around 6pm when I need to run in the dark again. This gives me one more practice round and mentally will help me – or at least, that’s the goal – know what it’s like to run in the dark. Given that I’ll run in the dark for 14h overnight, I don’t want to pick up my lights and take off and be 6-8 miles down trail from my husband and my backup gear if I realize something isn’t working well. I know I’ll be prone to just sticking it out for the entire lap; this way, I get a mini, 1.5h test of the gear on the same day and that way when I do a 3-5 hour first lap in the dark that evening, it’ll be slightly more likely to go smoothly and I’ll take all the smoothing I can get for my first 100M and my first all night and overnight run!

My other strategy involves self-care in the sense of regular medications that I need. Of course, I’ll be managing my blood sugars and insulin very carefully all day throughout (often thinking about it every 10-15 minutes to make sure everything is on track). But I also take allergy medication twice a day at morning and night, as well as a thyroid medication at night. So I have set reminders on my husband’s calendar to make sure he brings out my bags of night medication (e.g. allergy and thyroid) and in the morning (allergy) medication to make it less likely that I’ll forget to take them. Thankfully if I mess this up and am super delayed or forget to take them, it won’t derail my race/run much, but I definitely will feel not taking my allergy medication within hours so that will also help me remember to take my thyroid evening medication, too.

Another self-care strategy is around keeping my eyes hydrated with eye drops on a regular basis. In October 2021 I started to have really dry, gritty eyes and went to my eye doctor and was diagnosed with…dry, gritty eyes. Helpful! But, sarcasm aside (I love my eye doctor), I got eye gel to use before bedtime and eye drops to use throughout the day. Then in August 2022 I realized I had subclinical hyperthyroidism from Graves’ disease, which is an autoimmune disease (to go with type 1 diabetes, celiac disease, and exocrine pancreatic insufficiency) that causes eye issues. So! My dry gritty eyes were a precursor to my thyroid level changes. At any rate, learning how and when to use eye drops has become routine and I know how helpful it is to keep my eyes lubricated. I use preservative-free eye drops, not because the preservatives bother my eyes but because they come in miniature vials that are very easy to put in your pocket. Supposedly they are designed to be single use, but they usually contain enough lubrication for 2-3 rounds of drops for both eyes. So I twist off the lid, drop in both eyes, put the lid back on, and stuff it back in my pocket. I have set reminders on my calendar during the run to do this every few hours in case I forget, but I have also put vials in each lap bag (along with electrolytes and enzymes) and this presence of new eye drop mini-vials will help remind me (hopefully) to stay on top of eye lubrication.

Keeping my eyes from getting dry will hopefully help me be able to wear my contacts longer, because I usually take them out at night. But, I also will have my husband ready with my contact case and contact solution to take them out; then I will switch to my glasses or run without them (because I don’t need to see far or read signs off in the distance) for some period of hours, while still using the eye drops to keep them happy.

I’m fairly nervous about my eyes being an issue, since I’ve never run this long or all night. This was exacerbated by reading race recaps where folks talked about losing their vision! Yikes! I read a little bit more and realized they’re talking about corneal edema, where there is temporary swelling in the edema that makes your retinas visually look cloudy (if someone else looks at your eye). It usually goes away when people stop running after a few hours or day. But given my eye issues, before I had realized I was dealing with eye stuff related to Graves’ disease and thyroid stuff, I was concerned that my tendency to dry/gritty eyes would make me at higher risk of this, even though it seems like only 1-2% of 100M finishers ever deal with this. But, like everything else, I decided to have a strategy for this. I’ll seek to prevent it with regular lubrication and if it’s cold and windy, using my glasses (in lieu of contacts) or clear biker glasses or sunglasses to help protect my eyes from irritation and drying out further. But if it does happen, I’m using the advice from this post and bought a small vial of 5% hypertonic eye drops to use and try. (I had a regular annual eye doctor appointment a month prior, so I checked with my eye doctor about this. She had never heard of it and consulted a cornea specialist who had also not heard of it, which helps confirm that it’s pretty rare! Although they admitted they don’t get a lot of endurance athletes, looked it up on PubMed like I had, and agreed that if it happens to try the 5% hypertonic eye drops. Note that contact wearers want to take the contacts out before using these drops.) If I start to have vision issues; and I have the clear visual symptoms of this (according to Scott’s assessment of looking at my eyeballs); I’ll try the eye drops and ideally they’ll help. Since this is a known issue, if I still have some vision and can run safely (given my 6 foot wide paved trail in a safe location with no navigation required); I will likely try to continue – again based on discussion and advice with my doctor. But having a plan for this is much better than suddenly having vision issues in the ultra and feeling like I need to abort, when it might be ok to continue running (again on advice from my doctor).

Another strategy is thinking about how I’ll use caffeine. I usually drink caffeine up until noon, then switch to caffeine-free diet soda (and more water) in the afternoon and evening. I’ll drink a diet Mtn Dew when I wake up with my breakfast, but only one, and I will aim not to drink any throughout the day and save them for after midnight, when I’ll have been running for 18+ hours and have spent 6 hours in the dark. That way I have a “pick me up” to look forward to, both in terms of the taste/flavor of diet Mtn Dew, which I love, and some caffeine. There’s some suggestion that weaning off caffeine in the weeks prior to the race would make this a more effective strategy; but for me I think removing the joy of diet Mtn Dew would not be a net benefit. I’m also not convinced that I know what amount of caffeine is needed for an overnight boost, nor that I can test this reliably enough to have a solid evidence-based strategy here. So instead, I’m likely going for the mental boost of the taste change and the placebo effect of thinking the caffeine is helping. I have, however, tested drinking a diet Mtn Dew during a long run in the morning; so I do know that my body is ok taking it in.

This is yet another example of how I’m trying to remove decision-making during the race by pre-planning wherever possible for decisions like when to take caffeine or not; what to eat when; etc. I have laid out pacing sheets for a wide variety of run paces – so wide that the fastest pace (if all goes amazingly well) would have me finishing 8 hours faster than the slowest pace I have charted out. But the reason this matters is because I’m using the slowest time to estimate how much fuel I need to have prepared, then preparing more as backups (see more detail in the nutrition section). I created my overall fuel list then started putting in estimates of how many of each I would be willing to consume, also factoring in palate fatigue and texture fatigue and not wanting to chew or put ‘hard’ things (like Fritos) into my mouth in the later hours of my run. I balanced all of these variables and came up with 6 max servings of my chili cheese Fritos, most of which will be consumed in the earlier hours; 6 max servings of a few other routine things I can eat in most situations, then smaller counts (eg 1-4) of other things like the hot/home food that my husband will bring out in addition to the shelf-stable food. Once I had my overall counts totaling enough fuel for the slowest hour estimate and the number of servings; I then made a lap-by-lap list of what I wanted to eat when. I’m going to prepare these bags with the numbers I need per lap based on the timing (e.g. 10 snacks for the slowest pace estimated for my longest lap in between refuels, of which 8 are shelf stable and 2 will be added based on the sticky note reminder for the fresh/home options). Each of these lap bags will also include the requisite number of electrolyte pills I need, based on similar estimates from my “slow” paces, and the enzymes I need (because I have exocrine pancreatic insufficiency and need these to actually digest the fuel I consume), plus new eye drops. The point of this strategy is to remove decision making for both me and my husband: we don’t need to figure out how many enzymes or electrolytes I have “left” from the last lap (because I am off my fueling plan or more likely because I packed extra for each); instead, he can simply pull out all the trash, old enzyme/electrolyte bags, and replace with the new fuel, electrolyte, and enzymes along with my water/ice refill.

You may not have the complexity of my situation (type 1 diabetes, celiac, exocrine pancreatic insufficiency) influencing your fueling strategy and choices and how you’ll deal with fuel on the run. But, you might want to consider similarly planning your fuel. You may need to adapt your strategy based on how you’re feeling and what options you have in your pack, drop bag, with crew, or at an aid station, but you can plan for options to address issues of fatigue, palate/texture fatigue, etc. That, essentially, is what I have done.

Finally, I also consider a safety strategy part of my important race planning. I wear a watch that will generate an SOS alert and call emergency services if I fall during a run. I have the ability to press and hold a button on my watch or my phone to similarly generate an emergency services call. My location is tracked by my husband (and my mom from afar); and my husband also has access to my CGM for blood glucose tracking. He’ll have extra alerts and alarms set at different thresholds than we typically do for glucose levels. Finally, we’ve also created what I call the “DanaWatch” plan/squad, which is 3 people who will be texting me periodically from midnight to 9am my time, which is the overnight hours when Scott will be intermittently sleeping for 1-2 hour snatches in between refueling me. The plan is for my friend in the UK to text me every half hour and watch for a response that I’ll generate from my watch – probably a simple thumbs up emoji or tapping one of the auto-generated responses like “thanks” or “hi” or “I’m good”. After a few hours, a friend on the east coast will take over. Then my mom in central time zone after she wakes up will start texting. Nothing fancy, but the point is that they have ensured I’m still moving and ok. If I don’t respond within 5 minutes, they’ll call me; if I don’t pick up the phone, they’ll call Scott. This means that there wouldn’t be more than about 30 minutes where I’m not actively being “watched” virtually in case I get swooped by an owl, fall down and hit my head and am too disoriented to call for help (or some other very rare situation). I don’t expect that will happen; but I also think I’ll appreciate the “company” since I’m again, running a solo, DIY race where there aren’t aid stations, other runners, and other crew out and about to cheer me on. It’ll also help my husband sleep better/feel better, so any of those reasons are worth this strategy!

Post-race strategy

Like pre-race strategy, post-race strategy and planning is also critical for me. Once I cross the finish “line” and stop, I get cold and start to feel being wet (from sweat or rain) very quickly. My feet and everything hurt even more. I am absolutely not hungry despite knowing I need to re-fuel. But later I am ravenously hungry like a switch has shifted. So I plan accordingly.

First up, gear change. I want to change into dry clothes. I remind my husband to remind me that yes, despite the pain/hassle of getting out of a wet sports bra and changing it, I’ll regret not changing out of it in addition to changing my shirt. Sometimes, if we are getting in the car to drive home, I quickly swap to a dry shirt and then take the sports bra off under my shirt and just leave it off. No need for gymnastics to put another one on if I am just riding in the car. Same with shoes: once I take my sneakers off, my feet will not want to go back in sneakers. Definitely not the same sweaty, dirty shoes I was running  in, but also not cleaner and even bigger shoes. Instead, I prefer sandals/arch support flip flops. I have those, compression sleeves, and my clean dry clothes ready to go. I learned after my first trail marathon how good a washcloth feels for rubbing off sweat and dirt, so I also have a washcloth. It works for removing masses of mud before you get in the car, too. Or if you’re not muddy and hot and sweaty, pouring some cool water on it and washing your face feels heavenly.

Next up is fueling. When running an organized race, I don’t want to eat any of the race food, even if I can have it. (By “can have it” I mean that it’s safely gluten free with no cross-contamination risk, since I have celiac disease.) Usually I can’t have it, and I plan accordingly to bring food that is not the same food I’ve been eating throughout my ultra (because I have palate fatigue). I don’t want to eat as soon as I stop running, but usually after changing in the car and driving off, my body switches into “you’re safe” mode and wants to start refueling. Make sure you have all your food in the seat with you so you don’t have to stop and dig it out; or worse, have to try to twist around or reach for it (because you won’t want to do that most likely).

And again, you may have palate fatigue or similar (or it may disappear as soon as you are done), so having a few good options will be useful.

I also try to get enough groceries and prepare food for the following several days, too, when I’ll still be hungrier and making up for burned energy. My motivation to cook/prepare/put together food will be low, so having a stocked fridge and freezer with easy to prepare food is important.

Also, you may not be driving home from your race (or being driven home), so make sure to plan your logistics accordingly. Can you get to the airport that same day? Should you? Do you want to? And the next day? Is it safe to fly in your physical state? What different supplies do you need for flying that might be different (due to security regulations around liquid etc) than you would if you were driving home? Do you have enough snacks/food for the travel days following your run?

Training strategy

Oh, and yes, you have to physically train for your ultra. I am by no means a coach or an expert ultra runner. I am a solid, places-from-last back-of-the-pack runner who is a consistent run/walker. So get or make a training plan (Heather Hart has some great free ones for various distances). And stick to it. Except for when you don’t stick to it.

Wait, what?

You set your training strategy for “if all goes well”, but also build in flexibility and extra time for when things don’t go well. Like wildfire smoke season making it unsafe to run outside for a few days or weeks. Or you break your toe and spend 4 weeks not weight bearing. Or you have a lot of life stress, child or parental care, job stress, or any number of things. All this stress impacts training. Give yourself grace and be prepared to be flexible.

I have a hard time with this; I like my spreadsheets and my plans. But wildfire smoke and a broken toe were part of my 2022 ultra training experience this year, and I had to adjust training (and race plans) accordingly. At some point, you have to make the go/no-go decision about whether you’re going to run your race.

Think about what the “ideal training” is. Think about what is the “minimum training” to complete your event safety. If you’re somewhere in between, it’s going to be mental training and planning that can make the difference. At some point, if you’re above ‘minimum’ training you can decide to run even if your training isn’t ideal. Remember, it probably won’t be ideal and it isn’t for a lot of people. But per the mental training section and the wisdom I’ve gained from a lot of ultra runners…the most important factor might be deciding to do it. If you decide to, barring injury during the race or an accident, you will. If you decide mid-race you can’t or don’t want to, likely you won’t.

I think one thing I observe people not training is their walking strategy. Mine is baked in, because all my training short and long runs are intervals of run/walk. Many folks talk about walking hills or walking X minutes per Y minutes or Z miles. If that’s the plan for your race, train it during long runs. Walk hills or powerwalk or hike hills during runs or at the ends of runs. Practice a slow walk mixed in or a faster more efficient power walk. This will help build different muscles and help you maintain more efficient form (and speed) when you shift to it during the race, and help you go longer.

Similarly, practice with your vest/pack/handheld and other hydration gear. Practice with a similar stuffed and weighted pack. Practice with your head lamp. Do a run early in the morning as it transitions from dark to light; do a run into the evening as it transitions from light to dark to get used to your gear; practice troubleshooting it; and to improve your strategy for these transitions. If it’s wildfiresmoke season where you live, practice running masked as well. (On my last long run, I wore my mask for the full 8 hour run because air quality was so yucky.)

Also train and practice with your crew, if possible. Especially things like helping them tape or lubricate, tying your shoes, helping you put your pack on, them packing your pack/vest with supplies, etc. Any of these steps can be practiced during a training run so you and they can figure out what questions and assumptions you each have, and to build the crew checklist and instructions.

In my case, I’ve trained with my husband on refilling my ice and water in my pack during several training runs and previous races. We haven’t trained yet on him re-packing my (new) vest, though, so that’s on our list to practice on runs heading into my 100M. We did practice one run where I needed him to pick me up at a trail construction closure and drive me to the other side, with him bringing me a fresh/hot home-prepared fuel option. It worked well to a degree; I had a ¼ ham and cheese quesadilla slice in the microwave and had told him how to microwave it, which I had factored in cooling time for when he would be driving it to me before I would eat it. But he also tried to optimize and then put it in our car-based portable food warmer, which doesn’t do well with plastic bags (it needs a tupperware container) in general and was way too much heat. So it was scalding hot when I got in the car! Oops. Lesson learned. That was maybe unique to the car scenario but we will also test and practice the other food warming up options to make sure he doesn’t accidentally re-optimize where I’ve already optimized the food process; and make sure I have in fact optimally optimized the food strategy for each item.

Conclusion

Wow, that’s a lot of planning and strategy now that I’ve written it all out. Which makes sense, because I’ve been thinking about all these things for months and iterating on my strategies and plans. Hopefully, it’ll pay off and help immensely with making my 100M experience more smooth (note that I doubt any 100M would be easy/easier but I hope for “smoother”!) than it otherwise would be.

In summary, I pre-plan mentally for how it’ll feel running; I attempt to solve as many problems in advance as I can and prep supplies for fixing problems; I test, plan, and practice my fueling as much as possible; I aim to carefully pace effort as well as speed during my run; I break my run up into mental chunks so I am not dwelling on what’s to come but focusing on running the current segment; I try to minimize decision fatigue during and after the race by pre-doing anything I can and pre-supplying myself to make it easier; and of course, I train for months to prepare physically as best as possible while realizing that my training might not ever be ideal but that I can still safely attempt to run 100 miles.

PS – if there are any strategies, tips, or approaches you take to ultrarunning, especially 100 miles or more distance-wise, I’d love to hear them! Please share them in the comments or link to any posts you’ve written. I’m still learning and likely will always be evolving my strategies!

Note: I wrote this post before my 100 mile attempt. I ended up completing 82 miles and happily choosing to stop, knowing that I could physically keep going. Looking back at the above and reflecting on my experiences, I didn’t have a single challenge or experience that I wasn’t prepared to deal with or couldn’t deal with, thanks to all of the above work. So I’m thrilled and proud of my 82 mile experience!

If you found this post useful, you might also be interested to read this post with more details on how I developed my pacing, enzyme, and electrolyte estimates and more tactical specifics of how I prepped myself and my crew for my ultramarathon.

Reasons to “DIY” or Self-Organize Your Own Solo Ultramarathon or Ultra Run

I’ve now run two ultramarathons (both happened to be 50k races, with a race report for the second race here), and was planning my third ultrarace. I had my eye on the 50 mile (50M) version of the 50k I ran last year. It’s on a course I adore – a 6 foot wide crushed gravel trail that’s slightly uphill (about 1,000 feet) for the first 30 miles and then downhill at 2% grade for the remaining 20 miles. It happens to be close to home (hour and a half drive to the start), which helps for logistics.

I started training for the 50M weeks after my 50k this year, including talking my husband into taking me out to run some of the segments along the first 25 miles of the course. I’ve done the back half of the course several times through training and racing the 50k, and I wanted to check out each of the earlier segments to get a sense of what trail bathrooms existed on the course, make notes about milestones to watch for at various distances, etc.

After the first training run out there, when I started talking goal paces to get through the first and main cutoff at mile 30 (cutoffs got progressively easier from there, and even walking very slowly you could finish if you wanted to), my husband started to suggest that I should just run the course some other time on my own, so I didn’t have to worry about the cutoffs. I told him I didn’t want to do that. The cutoffs are a good incentive to help me push myself, and it’s worth the stress it causes in order to try to perform my best. (My target pace would get me through a comfortable 15 minutes before cutoff, and I could dial up the effort if needed to achieve cutoff). However, he suggested it another time and pointed out that even when running an organized race, I tend to run self-supported, so I don’t really don’t benefit as much from running in a race. I protested and talked again about the camaraderie of running when everyone else did, the fact that there were aid stations, the excellent search and rescue support, the t-shirt, the medal, the pictures! Then out loud I realized that I would be running at the back of the pack that I would miss the pictures at 25 miles because the photographer heads to the finish before I would get there. And they stop finish line pictures 3 hours before the end of the race. (Why, I don’t know!) And so I’d miss those photos too. And last year, I didn’t partake in the 50k staffed aid stations because I couldn’t eat any of their food and didn’t want any extra COVID exposure. Instead, my husband crewed me and refilled my hydration at two points on the course. The un-staffed aid stations didn’t have the plethora of supplies promised, and one race report from someone near the front of the pack said they were low on water! So it was a good thing I didn’t rely on the aid stations. I didn’t wear the tshirt last year, because it wasn’t a tech tee. Medals aren’t that exciting. So…why was I running the organized race?

My only remaining reasons were good search and rescue (still true) and the motivation of signing up for and committing to running on that date. It’s a commitment device. And my husband then smashed that reason, too, by reminding me that the only commitment device I typically need is a spreadsheet. If I decide I’m going to work toward a goal, I do. Signing up doesn’t make a difference.

And to be fair, he crews me whether it’s an organized race or not! So to him, it makes no difference whether I’m running an organized race or a self-organized long ultra.

And so I decided to give it some thought. Where would I run, if I could run anywhere in an hour’s distance from home? Do the same 50 mile course? Was that course worth it? Or was there somewhere closer to home where I could run that would be easier for my husband to crew?

He suggested running on our “home” trails, which is a network of hundreds of miles of paved trail that’s a short walk away. I immediately scoffed, then took the suggestion seriously. If I ran “from home”, he could crew from home and either drive out or e-bike out or walk out to bring me supplies along my route. If the park trail bathrooms ended up getting locked, I could always use the bathroom at home (although not ideal in terms of motivating myself to move quickly and get back out on the trail). I’d have a bigger variety of fueling options, since he could microwave and bring me out more options than if it had to be shelf-stable.

The list of benefits of potentially doing my own DIY or self-organized ultra grew.

(And then, I broke my toe. Argh. This further solidified my willingness to do a DIY ultra, because I could train up until when I was ready, and then run my distance, without having to choose between a non-refundable signup and not running or risking injury from running before I was ready.)

Eventually, my plans evolved (in part due to my broken toe). I was originally going to DIY a 50M or 100k (62M) over Labor Day weekend, recover, then re-train up and run a DIY 100 mile (100M) in late October or early November. When I broke my toe, I decided to scratch the “test” 50M/100k and just train and run the 100M, since that was my ultimate goal distance for the year.

Here are the pros of running a DIY ultra or a “self-organized” ultra, rather than an organized race with other people:

  • For me specifically, I have better trail options and route options. I can run a 95% flat course on paved, wide, safe trails through my local community.
  • These are so local that they are only a few minutes walk from my door.
  • The location means it’s easy for Scott to reach me at any point. He can walk out and bring me water and fuel and any needed supplies when I complete a loop every 4 or so hours. If needed, he could also e-bike out to bring me anything I need if I ran out or had a more urgent need for supplies. He can also drive out and access the course every half mile or mile for most of my planned route.

    This also means I have more fuel options that I can prepare and have for Scott to bring out. This is awesome because I can have him warm up ¼ of a ham and cheese quesadilla, or a corn dog, or sweet potato tots, or any other fuel options that I wouldn’t be able to use if I had to rely on pre-packed shelf stable options for a 30 hour race.

    (Note that even if I did an organized race, I most likely still wouldn’t benefit from aid station food. In part, because I have celiac and have to have everything gluten free. I also have to watch cross contamination, so a bowl of any kind of food that’s not individually packaged is something that’s likely contaminated by gluten. COVID has helped reduce this but not completely. Plus, I have diabetes so I need to be roughly aware of the amount of carbs I’m eating to decide whether or not to dose insulin for them, given what is happening to my blood sugar at the time. And, I have exocrine pancreatic insufficiency (EPI) which means I have to dose enzymes for everything I eat. Grazing is hard with EPI; it’s easier to dose and eat the amount that matches my enzymes, so pre-packaged snacks that I know the carb and fat and protein count means I know what insulin I need and what enzymes I need for each set of “fuel”. Guessing carb counts or enzyme counts in the middle of the night while running long distance is likely not going to be very effective or fun. So as a result of all that – pre-planned food is the way to go for me. Related, you can read about my approach for tracking fuel on the go with a spreadsheet and pre-planned fuel library here.)

  • There is regular public bathroom access along my chosen route.
  • I’ve designed out and back laps and loops that have me coming back by my start (remember, only a few minutes walk from home) and that make it so I am passing the bathrooms multiple times on a regular basis in case I need them.

    These laps and loops also make for mentally smaller chunks to tackle. Instead of 100 miles, I’ve got a ~24 mile out and back, a 13 mile loop, a 16 mile out and back, a repeat of the 13 mile loop, repeating again the 16 mile out and back followed by the 13 mile loop one more time, and then a quick 5 mile total out and back (so 2.5 out and back). These are also all routes I know well, so mentally finding waypoints to focus on and know how far I’ve gone are a huge benefit for mentally breaking down the distance into something my brain and body “know”.

  • There are no cutoffs or pace requirements. If I slow down to a 20 minute mile (or slower)…well hey, it’s faster than I was walking with my hands-free knee crutch a few months ago! (I rocked anywhere from a 45 minute mile to a 25 minute mile).

    There’s no pressure to go faster, which means I won’t have pressure to push my effort, especially at the start. Hopefully, that means I can maintain an “easy”, even effort throughout and maybe cause less stress to my body’s hormone systems than I would otherwise.

    The only pressure I have will be the pressure I put on myself to finish (eventually), which could be 26 hours or could be 30 hours or could be 36 hours or even slower… basically I have to finish before my husband gives up on coming out to refuel me!

  • And, once I finish, it’ll be ‘fast’ to get home, shower, refuel, and be done. This is in comparison to a race where I’d have an hour+ drive to get home. I’ll need to walk home which might actually take me much longer than that after I’ve ambulated for 100 miles…but it should hopefully be shorter than an hour!
  • Finally, the major benefit is flexibility. I can set my race date for a weekend when I’ve trained enough to do it. I can move it around a week or two based on the weather (if it’s too cold or too rainy). I can even decide to move it to the spring (although I’d really love to do it this year).

Here are some of the cons of running a DIY ultra or a “self-organized” ultra, rather than an organized race with other people:

  • Theoretically, it would be easier to stop because I am so close to home. I haven’t committed money or drive time or dragged my husband to far away places to wait for me to finish my run. (However, I’m pretty stubborn so in my case I think this is less of an issue than it might be for others?)
  • Yet, out and back loops and the route I’ve chosen could get monotonous. I chose these loops and the route because I know the distance and almost every tenth mile of the route super well. The first 6 miles of all the laps/loops are the same, so I’ll run those same 6 miles repeated 7 times over the course of the run.
  • I won’t have the camaraderie and knowledge that other people are out here tackling the same distance. I’m a back of the pack runner (and celebrate being places from last the way most people celebrate places from first!) and often don’t see anyone running after the start…yet there’s comfort in knowing I’m one of dozens or hundreds out here covering the same course on the same day with the same goal. I do think I’ll miss this part.
  • There is no one to cheer for me. There’s no aid station volunteers, fellow runners, or anyone (other than my amazing husband who will crew me) to cheer for me and encourage me and tell me I’m moving well.
  • There’s no medal (not a big deal), t-shirt (not a big deal), or official finishing time (also not a big deal for me).
  • There’s no cutoffs or pace requirements to motivate me to keep pushing when things get hard.

All in all, the benefits pretty clearly outweigh the downsides – for me. Again, I’m a back of the pack super slow runner (in fact, I typically run 30 seconds and walk 60 seconds throughout my whole race consistently) who can’t eat aid station food (because celiac/EPI makes it complicated) coming off of a broken toe injury (which messed up my training and racing plans), so my pros/cons lean pretty heavily toward making a DIY/self-organized solo ultra run an obvious choice. Others might have different pro/con list based on the above variables and their situations, but hopefully this helps someone else think through some of the ways they might decide between organized and un-organized ultramarathon efforts!

Reasons to "DIY" or self-organize your own ultramarathon run

What is in my running pack for running ultramarathons or training for a marathon

After three years of using a multi-purpose activity backpack as my running pack, the strap connector broke, and I had to find and re-stock a new running pack. I use a running pack for when I’m doing long runs for marathon or ultramarathon training.  I ended up pulling everything out of my old backpack and evaluating whether I still wanted to carry it on every long run. For the most part, everything got moved over to the new pack. There were a few cases where I had excessive duplicates (more on that below and why) where I ended up reducing the quantity. But everything else made the list for what I carry with me on long runs every single time.

  1. Hydration – via a camelbak or other bladder with a hose (example). I prefer straight water in my hydration pack and to separately manage electrolytes and fuel separately. The bonus of just having water is it’s easier to clean the hydration pack after each run!Tips: put ice cubes in your bladder and fill it with cold water. Cold water is awesome for long, hot runs in the sun. Also, my old hydration pack had an insulated compartment that kept the ice water cold for hours. My new running vest does not, and in fact has holes in the back for air flow that also means the heat from my back melts my ice pretty fast. To work around this in the new vest is to slide the filled hydration bladder into a padded mailing envelope that’s open at the top. It’s not quite as insulated as true insulation, but it protects the bladder from some of the heat coming off of your back and it probably stays cool 60% instead of 20% as long as before, which is a huge improvement.Extra tip: use a Qtip or similar to clean out the mouthpiece of your hose every few runs!
  2. Diabetes backups  – this means things like a backup insulin pump site. On long unsupported runs, it can also mean my blood glucose meter. (I wear a CGM so I don’t always take a meter along on runs unless it’s in an unsupported area where I don’t have easy crew access or support within a few miles). I’ve had several runs where my pump site has stopped working or ripped out, so having a backup pump site is just as necessary as having bandaids.The other source of backups is extra low carbs, e.g. sugar in case my blood sugar goes low. I usually keep a stash of carbs in my shorts pocket, but I also keep extra in my backpack in case I run through everything in my pocket. This is in addition to regular food/fuel for ultrafueling, it has to be faster-acting glucose/sugar that can more quickly fix a dropping or already-low blood sugar level.(This is one of the places I mentioned where I had excessive duplicates. I have continued to add extra to my backup stashes, and ended up with well over 100+ grams of “backup” carbs just in case. I ended up cutting down the total amount of carbs to closer to ~50 grams instead.)

    Emergency backup carbs maybe don't need to be 100g worth

    You can read some more about my strategy for running with diabetes here.

  3. Baggie with extra socks – I always carry a pair of extra socks, although I’ve never needed them in a normal training long run, I did end up using them in my 50k that involved crossing a river up to my knees five times.
  4. Bandaids – Just like hiking, but I carry bandaids in case of bleeding cuts or scratches or worse, blisters on my heels, feet, or toes. I carry some that are blister-style and some regular style, smaller ones and larger ones, all the way up to large multi-inch squares that can cover the backs of my heels if I don’t already have them covered.More recently, I also started carrying small squares and strips of kinesiology tape for the same purpose. I originally did kinesio tape strips in case my knee needed some extra support, but I’ve found the kinesio tape also works well to cover my toes or backs of my heels in lieu of bandaids for blister prevention. For fixing blisters, I have to dry my feet really well or the kinesio tape doesn’t stay well or easily rubs off; so I tend to cover the toes that blister frequently as well as my heels prior to my runs so they’re less likely to generate blisters and require fixing mid-runs. I get a large roll of kinesiology tape (example) and cut it into smaller pieces as needed for all of these uses cases.I also keep at least one mini individual packet of antibiotic ointment (example) in the baggie as well.
  5. Lubrication – I carry a lubrication stick (Squirrel Nut Butter, because it works for me and is easy to reapply) to making sure between my thighs and other areas don’t chafe. When I sweat a lot, I often have to reapply every few hours to my thighs. While this can also be accomplished by carrying dabs of vaseline or your preferred lubrication in a baggie, the SNB stick is lightweight and I don’t mind carrying it so it’s easy to reapply and the hassle doesn’t prevent me from wanting to prevent chafing.
  6. Stuff to fix GI problems – it’s common to have GI issues when running, but I also had a two-year stretch of known GI issues that ultimately turned out to be undiscovered exocrine pancreatic insufficiency. During this time, I always carried individual Immodium and GasX in case I needed them.
  7. Electrolyte pills – I prefer to measure and track electrolytes separate from my hydration, so I use electrolyte pills (example) that I swallow on a scheduled basis to keep my electrolyte levels topped off. I’ve tried chew kinds (but they make me burp), so I stick with a baggie full of electrolyte pills. I bring extra just in case I drop some, but I generally eyeball and count out to make sure I have enough for each super long run.
  8. Any medication you need during the run – For me, that includes enzymes for fuel because I have exocrine pancreatic insufficiency and I need enzymes to help me digest any of my fuel. I have expensive, larger dose prescription pills that I usually use for meals, but it would make running even more expensive if I had to use a $9 pill every 30 minutes for a fuel snack. Luckily, there are over the counter versions of enzyme pills (more about that here) that are single-enzyme or multi-enzyme, that are more in the ballpark of $0.35 per pill, and I have a baggie of both kinds that I use to cover each snack.
  9. Fuel or snacks – A lot of ultra runners use gels, but I have been experimenting with ‘real’ foods. Basically, anything that’s around ~20g of carbs and less than ~10g of fat and 5-10g of protein that I like to eat. So far, that list includes chili Cheese Fritos, yogurt covered pretzels, peanut butter pretzel nuggets, beef sticks, Honey Stinger Stroopwaffles (the gluten free kinds – beware that only some of their flavors are GF!), mini date or fruit bars, fruit snacks, sweet potato tots, ¼ of a ham and cheese quesadilla, ¼ of a PBJ sandwich, a waffle, mini PayDay bars…. Noting that all of these are gluten free versions or are naturally gluten free, because I have celiac disease. I do a lot of work in advance to test these snacks carefully on training runs before I commit to using them repeatedly throughout longer runs so I know my body likes them during runs as well as other times. I only take the fresh/hot snacks (sweet potato tots, quesadilla etc) and eat those at the start or when my husband re-fills my pack for me mid-run, so I don’t have to worry about them spoiling. Everything else is shelf stable so when I pack a few more than I need per run and leave some in my pack, they’re not an issue to sit there for weeks until I manage to eat them in my rotation of snacks on a future run.
  10. Miscellaneous other supplies – car keys, house keys, hand sanitizer, a mask for going into trail bathrooms, and a battery and cord for charging my phone.

Phew. That’s a lot of stuff. And yes, it does end up being more supplies and more weight than most people carry. But…I use pretty much everything in my pack every few runs. Stuff happens: pump sites fall out, blisters happen, chafing happens, GI stuff happens..and I’ve found that training and running with a little extra weight in my pack is worth having the proper supplies when I need them, rather than having to end runs early due to lack of preparation or minor supplies that would enable me to keep running.

Every time I go out for a run, I add the requisite amount of snacks, enzymes, electrolyte pills, and hydration for the run. Any time I come back from a run and I have depleted a supply off of the above list – such as using my backup pump site – I immediately go and refill that supply so I don’t have to remember to refill it prior to the next run. Keeping the above supplies topped off and ready to go always in my backpack means they’re always there when I need them, and the peace of mind of knowing how I can handle and that I can handle these situations while running is priceless.

Note: previously I was using a backpack, because it was $30 and for my running it was good enough. However, when the strap broke, I looked to buy the same backpack again and it was $60. It was fine for $30 but if I was going to double the cost, I decided to research alternative running packs and vests. Vests seem to be more common in ultrarunners, so I looked for those, although they’re a lot more expensive (often $125-200). I was disappointed with how small of a volume some of them held, or they were just ugly. I liked the look of a purple one I found that came with a 1.5L bladder….but ugh. I fit a 3L bladder in my previous backpack and typically fill it 2-2.5L full as a baseline, and all the way up for a longer (6h+) unsupported run. I decided to risk getting this vest even though it was smaller and try putting my larger 3L capacity bladder in the new vest. (Luckily it was on sale for $90 at the time  which made it a little less annoying to buy compared to a $150 one.) The bladder does fit, but it sticks out the top and hits the back of my neck if it’s all the way full (3L). So for the most part, I’m filling the 3L capacity bladder about 2L full (and as noted in this post earlier, putting it inside an insulated envelope to help retain the cold for longer), and that works for me.

One thing I do like a lot from my new running vest is the front pockets. My old backpack I had to partially take off and twist around me in order to get snacks out. With two large front pockets, I can fit several hours of fuel in there so there is no twisting involved to get my fuel out, which is helping with my goal to fuel every 30 minutes. I do wish there was a separate smaller pouch – my old backpack had a small old school flip phone size “cell phone” pocket that I used to keep my baggies of enzymes and electrolytes in. Right now, I just have those baggies floating around the top of those pockets and it’s fairly easily to grab and pull out the right baggie, but I’m toying with adding some kind of small strap-on holster/pouch to the shoulder just for enzymes so I don’t have to worry as much about them jostling out when my pockets are completely full of snacks. But otherwise, these front pockets are overall a nice improvement.

A purple running vest on the left; supplies described in blog post in the middle laid out on the ground, and my old purple backpack used for running on the right.
A cat in mid air jumping over the purple runing vest in the left of the picture; another cat sitting to the right of the old purple backpack used for running.
Outtake! Mint jumping over my new running vest and running supplies while Mo looks on from the right next to my old running backpack.
A cat sitting on and sniffing the new smells of a new, purple running vest
Mint helpfully inspected my new running vest as soon as I set it on the ground.

Tips and Tricks for Forefoot Bursitis or Intermetatarsal Bursitis

It’s apparently rare (ish) to get forefoot bursitis. If you look for information or treatment options about bursitis, most “foot bursitis” is about heel bursitis. If not foot, then it’s knee, elbow, or hip bursitis. All sounds unfun. But what’s also unfun is actual forefoot bursitis, which is usually intermetatarsal bursitis.

Flash back to when I broke my fifth toe on my right foot about 7 weeks ago. I cried, hard, after I broke it. Not only because it hurt, but also because I knew how hard it was to return to walking after I broke my ankle 3.5 years ago. And I knew from that experience that returning to walking would come not only with the standard trials and tribulations of injury recovery but also a risk of redeveloping intermetatarsal bursitis in not one but two parts of my foot. It was brutal, and I had to take another 6 weeks off of running last time after I discovered it. So when I broke my toe, I wasn’t looking forward to the recovery process, as I knew there was a greater than zero chance that I’d have to face bursitis again as well.

And sure enough, a week or so after I returned to full weight bearing and was working on extending my walking, I felt the no good terrible horrible pain in my forefoot that is intermetatarsal bursitis. Same spot as last time. And worse, because it actually was in the second spot, too, between my first and second toes as well as the third and fourth. Last time I primarily felt it in the third/fourth area of my foot while an MRI identified that I also had it between one/two. This time, I felt it in both places, and there was no winning and no reduction in pain no matter how I set my foot on the ground. Ahhh!

But I learned my lesson from last time, I think. I very quickly started trying to reduce the pain by changing the shoes I was wearing (didn’t help) and the way I was walking (didn’t help). I had been nearly to the stage of my recovery process where I could try to start running again, but I knew if I couldn’t even walk barefoot across a hard floor in the house that it likely wasn’t going to be bearable to run on my foot. And it wasn’t.

I gnashed my teeth and did a bunch of research, looking for solutions. I found heaps of information on every other type of bursitis, but very little on intermetatarsal bursitis. Harumph. (Thus, I’m leaving this post as breadcrumbs for anyone else in the future, and maybe for me, too, so I remember what works for next time if I ever have to deal with it yet again.)

Last time, I tried a metatarsal pad in a little sleeve for my foot, which didn’t help. Nothing helped except for trying to stay off my foot as much as possible. I tried a different insole for my shoe with a steel tip, to help reduce the force in the forefoot area as my foot hit the ground. That helped minimize the pain somewhat to make short daily walks tolerable. Otherwise, I waited 6+ weeks for the pain to go away.

This time, I was really hoping to not have another 6 weeks before I could run, since I was and am again training for an ultramarathon. Breaking my toe put a 6+ week snafu on my plans for the fall; I was hoping not to have to give up on my fall ultra plans completely.

Most of the research on bursitis in general suggests trying to reduce inflammation, because that’s what bursitis is: inflammation of bursa. Oral NSAIDs like ibuprofen may or may not help. In my case this time, I was already taking oral NSAIDs for other reasons and it didn’t seem to do anything in regards to bursitis pain. But this reminded me to try NSAID gel (such as this, a generic option, or there are brand name kinds that do the same thing) on my forefoot. It does seem to help a little bit with pain in the hours following using it. The challenge is putting it on and sitting to let it dry so it can get into the skin and start working.

But since I was so desperate, I dug through my cabinet of ankle braces and other foot-related gear and found the metatarsal sleeve pad that I didn’t use last time because it didn’t work. But lo and behold, this time it DID work! I tentatively walked around the house barefoot, amazed that it completely eliminated the bursitis pain in both spots of my foot, and enabled me to walk over my foot without having to compensate by putting too much pressure onto my recently broken (but now mostly healed) toe.

The metatarsal pad sleeve (similar to this one) is a small pad inside a sleeve that sits and takes weight and distributes it to different areas of your foot, rather than the same bursitis areas of your foot getting the full force of your step. I am not sure why it didn’t work well for me last time, but this time it’s the closest thing to magic that I’ve ever experienced. Usually, when something hurts, a solution might reduce pain, but there have been few things that completely eliminate pain during use like this does. (Note that I still have bursitis and will likely still have it for weeks, so I still have to wear flip-flops or the foot sleeve around the house to make sure my foot doesn’t hurt.)

Because it’s a fabric sleeve, it does take up space in my shoe, and I’ve found that even with a larger size shoe it’s uncomfortable to wear a sock when I’m wearing the sleeve on that foot. It feels weird, but the metatarsal sleeve and otherwise being barefoot inside my normal-size shoe works well. So well that I can get back to my running, even with bursitis, which is awesome.

The other trick that I learned last time is to leave a squishy or memory foam flip-flop by my shower. (Here’s an example. Although they’re harder to find, I’ve also found a random store brand memory foam flip-flop option that works well.) Some days standing in the shower hurts due to the pressure on the bottom of my foot, other days it doesn’t. Setting my right foot, the one with the intermetatarsal bursitis, on top of the flip-flop (or wearing it) helps distribute the weight in a way that doesn’t hurt the bursitis as much on the hard shower floor. (If you try this, I’d be sure to be careful getting in and out of the shower with it – I usually set it in the shower and step on it once I’m already in, and that way I step out of the shower without a wet flip-flop to worry about slipping with.)

So TLDR:

  • Intermetatarsal bursitis or forefoot bursitis is a thing.
  • It hurts, a lot. If you have it, I’m sorry.
  • It takes weeks for it to fix itself usually. Argh
  • Normal anti-inflammation things might help: ice, oral NSAID, NSAID gel, heat, etc.
  • Try to rest/not do things that make it hurt (if at all possible).
  • If you have intermetatarsal bursitis, look at getting a metatarsal pad to put in your shoe, or get a metatarsal pad sleeve that you can wear with any shoes, including when barefoot or in sandals.
  • Set a squishy or memory foam flip-flop by the shower to stand on if your foot hurts standing in the shower, or wear flip-flops in the shower.

2022 Strawberry Fields Forever Ultramarathon Race Report Recap

I recently ran my second-ever 50k ultramarathon. This is my attempt to provide a race recap or “race report”, which in part is to help people in the future considering this race and this course. (I couldn’t find a lot of race reports investigating this race!)

It’s also an effort to provide an example of how I executed fueling, enzyme dosing (because I have exocrine pancreatic insufficiency, known as EPI), and blood sugar management (because I have type 1 diabetes), because there’s also not a lot of practical guidance or examples of how people do this. A lot of it is individual, and what works for me won’t necessarily work for anyone, but if anything hopefully it will help other people feel not alone as they work to figure out what works for them!

Context of my running and training in preparation

I wrote quite a bit in this previous post about my training last year for a marathon and my first 50k. Basically, I’m slow, and I also choose to run/walk for my training and racing. This year I’ve been doing 30:60 intervals, meaning I run 30 seconds and walk 60 seconds.

Due to a combination of improved training (and having a year of training last year), as well as now having recognized I was not getting sufficient pancreatic enzymes so that I was not digesting and using the food I was eating effectively, this year has been going really well. I ended up training as far as a practice 50k about 5 weeks out from my race. I did several more mid- to high-20 mile runs as well. I also did a next-day run following my long runs, starting around 3-4 miles and eventually increasing to 8 miles the day after my 50k. The goal of these next-day runs was to practice running on tired legs.

Overall, I think this training was very effective for me. My training runs were easy paced, and I always felt like I could run more after I was done. I recovered well, and the next-day runs weren’t painful and I did not have to truncate or skip any of those planned runs. (Previous years, running always felt hard and I didn’t know what it was like to recover “well” until this year.) My paces also increased to about a minute/mile faster than last year’s easy pace. Again, that’s probably a combination of increased running overall and better digestion and recovery.

Last year I chose to run a marathon and then do a 50k while I was “trained up” for my marathon. This year, I wanted to do a 50k as a fitness assessment on the path to a 50 mile race this fall. I looked for local-ish 50k options that did not have much elevation, and found the Strawberry Fields Forever Ultra.

Why I chose this race, and the basics about this race

The Strawberry Fields Forever Ultra met most of my goal criteria, including that it was around the time that I wanted to run a 50k, so that I had almost 6 months to train and also before it got to be too hot and risked being during wildfire smoke season. (Sadly, that’s a season that now overlaps significantly with the summers here.) It’s local-ish, meaning we could drive to it, although we did spend the night before the race in the area just to save some stress the morning of the race. The race nicely started at 9am, and we drove home in the evening after the race.

The race is on a 10k (6.2 miles) looped course in North Bonneville, Washington, and hosted a 10k event (1 lap), a 50k event (5 laps), and also had 100k (10 laps) or (almost) 100 miles (16 laps). It does have a little bit of elevation – or “little” by ultramarathon standards. The site and all reports describe one hill and net 200 feet of elevation gain and loss. I didn’t love the idea of a 200 foot hill, but thought I could make do. It also describes the course as “grass and dirt” trails. You’ll see a map later where I’ve described some key points on the course, and it’s also worth noting that this course is very “crew-able”. Most people hang out at the start/finish, since it’s “just” a 10k loop and people are looping through pretty frequently. However, if you want to, either for moral or practical support, crew could walk over to various points, or my husband brought his e-bike and biked around between points on the course very easily using a mix of the other trails and actual roads nearby.

The course is well marked. Any turn had a white sign with a black arrow on it and also white arrows drawn on the ground, and there were dozens of little red/pink fluorescent flags marking the course. Any time there was a fork in the path, these flags (usually 2-3 for emphasis, which was excellent for tired brains) would guide you to the correct direction.

The nice thing about this race is it includes the 100 mile option and that has a course limit of 30 hours, which means all the other distances also have this course limit of 30 hours. That’s fantastic when a lot of 50k or 50 mile (or 100k, which is 62 miles) courses might have 12 hour or similar tighter course limits. If you wanted to have a nice long opportunity to cover the distance, with the ability to stop and rest (or nap/sleep), this is a great option for that.

With the 50k, I was aiming to match or ideally beat my time from my first 50k, recognizing that this course is harder given the terrain and hill. However, I think my fitness is higher, so beating that time even with the elevation gain seemed reasonable.

Special conditions and challenges of the 2022 Strawberry Fields Forever Ultramarathon

It’s worth noting that in 2021 there was a record abnormal heat wave due to a “heat dome” that made it 100+ degrees (F) during the race. Yikes. I read about that and I am not willing to run a race when I have not trained for that type of heat (or any heat), so I actually waited until the week before the race to officially sign up after I saw the forecast for the race. The forecast originally was 80 F, then bounced around mid 60s to mid 70s, all of which seemed doable. I wouldn’t mind some rain during the race, either, as rainy 50s and 60s is what I’ve been training in for months.

But just to make things interesting, for the 2022 event the Pacific Northwest got an “atmospheric river” that dumped inches of rain on Thursday..and Friday. Gulp. Scott and I drove down to spend the night Friday night before the race, and it was dumping hard rain. I began to worry about the mud that would be on the course before we even started the race. However, the rain finished overnight and we woke up to everything being wet, but not actively raining. It was actually fairly warm (60s), so even if it drizzled during the race it wouldn’t be chilly.

During the start of the race, the race director said we would get wet and joked (I thought) about practicing our backstroke. Then the race started, and we took off.

My race recap / race report the 2022 Strawberry Fields Forever Ultramarathon

I’ve included a picture below that I was sent a month or so before the race when I asked for a course map, and a second picture because I also asked for the elevation profile. I’ve marked with letters (A-I) points on the course that I’ll describe below for reference, and we ran counterclockwise this year so the elevation map I’ve marked with matching letters where “A” is on the right and “I” is on the left, matching how I experienced the course.

The course is slightly different in the start/finish area, but otherwise is 95% matching what we actually ran, so I didn’t bother grabbing my actual course map from my run since this one was handy and a lot cleaner than my Runkeeper-derived map of the race.

Annotated course map with points A-I
StrawberryFieldsForever-Ultra-Elevation-Profile

My Runkeeper elevation profile of the 50k (5 repeated laps) looked like this:
Runkeeper elevation profile of 5 loops on the Strawberry Fields Forever 50k course

I’ll describe my first experience through the course (Lap 1) in more detail, then a couple of thoughts about the experiences of the subsequent laps, in part to describe fueling and other choices I made.

Lap 1:

We left the start by running across the soccer field and getting on a paved path that hooked around the ballfield and then headed out a gate and up The Hill. This was the one hill I thought was on the course. I ran a little bit and passed a few people who walked on a shallower slope, then I also converted to a walk for the rest of the hill. It was the most crowded race start I’ve done, because there were so many people (150 across the 10k, 50k, 100k, and 100 miler) and such a short distance between the start and this hill. The Hill, as I thought of it, is point A on the course map.

Luckily, heading up the hill there are gorgeous purple wildflowers along the path and mountain views. At the top of the hill there are some benches at the point where we took a left turn and headed down the hill, going down the same elevation in about half a mile so it was longer than the uphill section. This downhill slope (B) was very runnable and gravel covered, whereas going up the hill was more dirt and mud.

At the bottom of the hill, there was a hairpin turn and we turned and headed back up the hill, although not all the way up, and more along a plateau in the side of the hill. The “plateau” is point C on the map. I thought it would be runnable once I got back up the initial hill, but it was mud pit after mud pit, and I would have two steps of running in between mud pits to carefully walk through. It was really frustrating. I ended up texting to my parents and Scott that it was about 1.7 miles of mud (from the uphill, and the plateau) before I got to some gravel that was more easily runnable. Woohoo for gravel! This was a nice, short downhill slope (D) before we flattened out and switched back to dirt and more mud pits.

This was the E area, although it did feel more runnable than the plateau because there were longer stretches between muddy sections.

Eventually, we saw the river and came out from the trail into a parking lot and then jogged over onto the trail that parallels the river for a while. This trail that I thought of as “River Road” (starting around point F) is just mowed grass and is between a sharp bluff drop with opening where people would be down at the river fishing, and in some cases we were running *underneath* fishing lines from the parking spots down to the river! There were a few people who would be walking back and forth from cars to the river, but in general they were all very courteous and there was no obstruction of the trail. Despite the mowed grass aspect of the trail, this stretch physically and psychologically felt easier because there were no mud pits for 90% of it. Near the end there were a few muddy areas right about the point we hopped back over into the road to connect up a gravel road for a short spurt.

This year, the race actually put a bonus aid station out here. I didn’t partake, but they had a tent up with two volunteers who were cheerful and kind to passing runners, and it looked like they had giant things of gatorade or water, bottled water, and some sugared soda. They probably had other stuff, but that’s just what I saw when passing.

After that short gravel road bit, we turned back onto a dirt trail that led us to the river. Not the big river we had been running next to, but the place where the Columbia River overflowed the trail and we had to cross it. This is what the race director meant by practicing our backstroke.

You can see a video in this tweet of how deep and far across you had to get in this river crossing (around point G, but hopefully in future years this isn’t a point of interest on the map!!)

Showing a text on my watch of my BIL warning me about a river crossing

Coming out of the river, my feet were like blocks of ice. I cheered up at the thought that I had finished the wet feet portion of the course and I’d dry off before I looped back around and hit the muddy hill and plateau again. But, sadly, just around the next curve, came a mud POND. Not a pit, a pond.

Showing how bad the mud was

Again, ankle deep water and mud, not just once but in three different ponds all within 30 seconds or so of each other. It was really frustrating, and obviously you can’t run through them, so it slowed you down.

Then finally after the river crossing and the mud ponds, we hooked a right into a nice, forest trail that we spent about a mile and a half in (point H). It had a few muddy spots like you would normally expect to get muddy on a trail, but it wasn’t ankle deep or water filled or anything else. It was a nice relief!

Then we turned out of the forest and crossed a road and headed up one more (tiny, but it felt annoying despite how small it looks on the elevation profile) hill (point I), ran down the other side of that slope, stepped across another mud pond onto a pleasingly gravel path, and took the gravel path about .3 miles back all the way to complete the first full lap.

Phew.

I actually made pretty good time the first loop despite not knowing about all the mud or river crossing challenges. I was pleased with my time which was on track with my plan. Scott took my pack about .1 miles before I entered the start/finish area and brought it back to me refilled as I exited the start/finish area.

Lap 2:

The second lap was pretty similar. The Hill (A) felt remarkably harder after having experienced the first loop. I did try to run more of the downhill (B) as I recognized I’d make up some time from the walking climb as well as knowing I couldn’t run up the plateau or some of the mud pits along the plateau (C) as well as I had expected. I also decided running in the mud pits didn’t work, and went with the safer approach of stepping through them and then running 2 steps in between. I was a little slower this time, but still a reasonable pace for my goals.

The rest of the loop was roughly the same as the first, the mud was obnoxious, the river crossing freezing, the mud obnoxious again, and relief at running through the forest.

Scott met me at the end of the river road and biked along the short gravel section with me and went ahead so he could park his bike and take video of my second river crossing, which is the video above. I was thrilled to have video of that, because the static pictures of the river crossing didn’t feel like it did the depth and breadth of the water justice!

At the end of lap 2, Scott grabbed my pack again at the end of the loop and said he’d figured out where to meet me to give it back to me after the hill…if I wanted that. Yes, please! The bottom of the hill where you hairpin turn to go back up the plateau is the 1 mile marker point, so that means I ran the first mile of the third lap without my pack, and not having the weight of my full pack (almost 3L of water and lots of snacks and supplies: more on that pack below) was really helpful for my third time up the hill. He met me as planned at the bottom of the downhill (B) and I took my pack back which made a much nicer start to lap 3.

Lap 3:

Lap 3 for some reason I came out of the river crossing and the mud ponds feeling like I got extra mud in my right shoe. It felt gritty around the right side of my right food, and I was worried about having been running for so many hours with soaked feet. I decided to stop at a bench in the forest section and swap for dry socks. In retrospect, I wish I had stopped somewhere else, because I got swarmed by these moth/gnat/mosquito things that looked gross (dozens on my leg within a minute of sitting there) that I couldn’t brush off effectively while I was trying to remove my gaiters, untie my shoes, take my shoes off, peel my socks and bandaids and lambs wool off, put lubrication back on my toes, put more lambs wool on my toes, put the socks and shoes back on, and re-do my gaiters. Sadly, it took me 6 minutes despite me moving as fast as I could to do all of those things (this was a high/weirdly designed bench in a shack that looked like a bus stop in the middle of the woods, so it wasn’t the best way to sit, but I thought it was better than sitting on the ground).

(The bugs didn’t hurt me at the time, but two days later my dozens of bites all over my leg are red and swollen, though thankfully they only itch when they have something chafing against them.)

Anyway, I stood up and took off again and was frustrated knowing that it had taken 6 minutes and basically eaten the margin of time I had against my previous 50k time. I saw Scott about a quarter of a mile later, and I saw him right as I realized I had also somewhere lost my baggie of electrolyte pills. Argh! I didn’t have back up for those (although I had given Scott backups of everything else), so that spiked my stress levels as I was due for some electrolytes and wasn’t sure how I’d do with 3 or so more hours without them.

I gave Scott my pack and tasked him with checking my brother-in-law’s setup to see if he had spare electrolytes, while he was refilling my pack to give me in lap 4.

Lap 4:

I was pretty grumpy given the sock timing and the electrolyte mishap as I headed into lap 4. The hill still sucked, but I told myself “only one more hill after this!” and that thought cheered me up.

Scott had found two electrolyte options from my brother-in-law and brought those to me at the end of mile 1 (again, bottom of B slope) with my pack. He found two chewable and two swallow pills, so I had options for electrolytes. I chewed the first electrolyte tab as I headed up the plateau, and again talked myself through the mud pits with “only one more time through the mud pits after this!”.

I also tried overall to bounce back from the last of mile 4 where I let myself get frustrated, and try to take more advantage of the runnable parts of the course. I ran downhill (B) more than the previous laps, mostly ignoring the audio cues of my 30:60 intervals and probably running more like 45:30 or so. Similarly, the downhill gravel after the mud pits (D) I ran most of without paying attention to the audio run cues.

Scott this time also met me at the start of the river road section, and I gave him my pack again and asked him to take some things out that he had put in. He put in a bag with two pairs of replacement socks instead of just one pair of socks, and also put in an extra beef stick even though I didn’t ask for it. I asked him to remove it, and he did, but explained he had put it in just in case he didn’t find the electrolytes because it had 375g of sodium. (Sodium is primarily the electrolyte I am sensitive to and care most about). So this was actually a smart thing, although because I haven’t practiced eating larger amounts of protein and experienced enzyme dosing for it on the run, I would be pretty nervous about eating it in a race, so that made me a bit unnecessarily grumpy. Overall though, it was great to see him extra times on the course at this point, and I don’t know if he noticed how grumpy I was, but if he did he ignored it and I cheered up again knowing I only had “one more” of everything after this lap!

The other thing that helped was he biked my pack down the road to just before the river crossing, so I ran the river road section like I did lap 3 and 4 on the hill, without a pack. This gave me more energy and I found myself adding 5-10 seconds to the start of my run intervals to extend them.

The 4th river crossing was no less obnoxious and cold, but this time it and the mud ponds didn’t seem to embed grit inside my shoes, so I knew I would finish with the same pair of socks and not need another change to finish the race.

Lap 5:

I was so glad I was only running the 50k so that I only had 5 laps to do!

For the last lap, I was determined to finish strong. I thought I had a chance of making up a tiny bit of the sock change time that I had lost. I walked up the hill, but again ran more than my scheduled intervals downhill, grabbed my bag from Scott, picked my way across the mud pits for the final time (woohoo!), ran the downhill and ran a little long and more efficiently on the single track to the river road.

Scott took my pack again at the river road, and I swapped my intervals to be 30:45, since I was already running closer to that and I knew I only had 3.5 or so miles to go. I took my pack back at the end of river road and did my last-ever ice cold river crossing and mud pond extravaganza. After I left the last mud pond and turned into the forest, I switched my intervals to 30:30. I managed to keep my 30:30 intervals and stayed pretty quick – my last mile and a half was the fastest of the entire race!

I came into the finish line strong, as I had hoped to finish. Woohoo!

Overall strengths and positives from the race

Overall, running-wise I performed fairly well. I had a strong first lap and decent second lap, and I got more efficient on the laps as I went, staying focused and taking advantage of the more runnable parts of the course. I finished strong, with 30:45 intervals for over a mile and 30:30 intervals for over a mile to the finish.

Also, I didn’t quit after experiencing the river crossing and the mud ponds and the mud pits of the first lap. This wasn’t an “A” race for me or my first time at the distance, so it would’ve been really easy to quit. I probably didn’t in part because we did pay to spend the night before and drove all that way, and I didn’t want to have “wasted” Scott’s time by quitting, when I was very capable of continuing and wasn’t injured. But I’m proud of mostly the way I handled the challenges of the course, and for how I readjusted from the mental low and frustration after realizing how long my sock change took in lap 3. I’m also pleased that I didn’t get injured, given the terrain (mud, river crossing, and uneven grass to run on for most of the course). I’m also pleased and amazed I didn’t hurt my feet, cause major blisters, or have anything really happen to them after hours of wet, muddy, never-drying-off feet.

The huge positive was my fueling, electrolytes, and blood glucose management.

I started taking my electrolyte pills that have 200+mg of sodium at about 45 minutes into the race, on schedule. My snack choices also have 100-150mg of sodium, which allowed me to not take electrolyte pills as often as I would otherwise need to (or on a hotter day with more sweat – it was a damp, mid-60s day but I didn’t sweat as much as I usually do). But even with losing my electrolytes, I used two chewable 100mg sodium electrolytes instead and otherwise ended up with sufficient electrolytes. Even with ideal electrolyte supplementation, I’m very sensitive to sodium losses and am a salty sweater, and I have a distinct feeling when my electrolytes are insufficient, so not having that feeling during after the race was a big positive for me.

So was my fueling overall. The race started at 9am, and I woke up at 6am to eat my usual pre-race breakfast (a handful of pecans, plus my enzyme supplementation) so that it would both digest effectively and also be done hitting my blood sugar by the time the race started. My BGs were flat 120s or 130s when I started, which is how I like them. I took my first snack about an hour and 10 minutes into the race, which is about 15g carb (10g fat, 2g protein) of chili cheese flavored Fritos. For this, I didn’t dose any insulin as I was in range, and I took one lipase-only enzyme (which covers about 8g of fat for me) and one multi-enzyme (that covers about 6g of fat and probably over a dozen grams of protein). My second snack was an hour later, when I had a gluten free salted caramel Honey Stinger stroopwaffle (21g carb, 6 fat, 1 protein). For the stroopwaffle I ended up only taking a lipase-only pill to cover the fat, even though there’s 1g of protein. For me, I seem to be ok (or have no symptoms) from 2-3g of uncovered fat and 1-2g of uncovered protein. Anything more than that I like to dose enzymes for, although it depends on the situation. Throughout the day, I always did 1 lipase-only and 1 multi-enzyme for the Fritos, and 1 lipase-only for the stroopwaffle, and that seemed to work fine for me. I think I did a 0.3u (less than a third of the total insulin I would normally need) bolus for my stroopwaffle because I was around 150 mg/dL at the time, having risen following my un-covered Frito snack, and I thought I would need a tiny bit of insulin. This was perfect, and I came back down and flattened out. An hour and 20 minutes after that, I did another round of Fritos. An hour or so after that, a second stroopwaffle – but this time I didn’t dose any insulin for it as my BG was on a downward slope. An hour later, more Fritos. A little bit after that, I did my one single sugar-only correction (an 8g carb Airhead mini) as I was still sliding down toward 90 mg/dL, and while that’s nowhere near low, I thought my Fritos might hit a little late and I wanted to be sure I didn’t experience the feeling of a low. This was during the latter half of loop 4 when I was starting to increase my intensity, so I also knew I’d likely burn a little more glucose and it would balance out – and it did! I did one last round of Fritos during lap 5.
CGM graph during 50k ultramarathon

This all worked perfectly. I had 100% time in range between 90 and 150 mg/dL, even with 102g of “real food” carbs (15g x 4 servings of Fritos, 21g x 2 waffles), and one 8g Airhead mini, so in total I had 110g grams of carbs across ~7+ hours. This perfectly matched my needs with my run/walk moderate efforts.

BG and carb intake plotted along CGM graph during 50k ultramarathon

I also nailed the enzymes, as during the race I didn’t have any GI-related symptoms and after the race and the next day (which is the ultimate verdict for me with EPI), no symptoms.

So it seems like my practice and testing with low carbs, Fritos, and waffles worked out well! I had a few other snacks in my pack (yogurt-covered pretzels, peanut butter pretzel nuggets), but I never thought of wanting them or wanting something different. I did plan to try to do 2 snacks per hour, but I ended up doing about 1 per hour. I probably could have tolerated more, but I wasn’t hungry, my BGs were great, and so although it wasn’t quite according to my original plan I think this was ideal for me and my effort level on race day.

The final thing I think went well was deciding on the fly after loop 2 to have Scott take my pack until after the hill (so I ran the up/downhill mile without it), and then for additional stretches along river road in laps 4 and 5. I had my pocket of my shorts packed with dozens of Airheads and mints, so I was fine in terms of blood sugar management and definitely didn’t need things for a mile at a time. I’m usually concerned about staying hydrated and having water whenever I want to sip, plus for swallowing electrolytes and enzyme pills to go with my snacks, but I think on this course with the number of points Scott could meet me (after B, at F all through G, and from I to the finish), I could have gotten away with not having my pack the whole time; having WAY less water in the pack (I definitely didn’t need to haul 3L the whole time, that was for when I might not see Scott every 2-3 laps) and only one of each snack at a time.

Areas for improvement from my race

I trained primarily on gravel or paved trails and roads, but despite the “easy” elevation profile and terrain, this was essentially my first trail ultra. I coped really well with the terrain, but the cognitive burden of all the challenges (Mud pits! River crossing! Mud ponds!) added up. I’d probably do a little more trail running and hills (although I did some) in the final weeks before the race to help condition my brain a little more.

I’ll also continue to practice fueling so I can eat more regularly than every hour to an hour and a half, even though this was the most I’ve ever eaten during a run, I did well with the quantities, and my enzyme and BG management were also A+. But I didn’t eat as much as I planned for, and I think that might’ve helped with the cognitive fatigue, too, by at least 5-10%.

I also now have the experience of a “stop” during a race, in this case to swap my socks. I’ve only run one ultra and never stopped before to do gear changes, so that experience probably was sufficient prep for future stops, although I do want to be mentally stronger/less frustrated by unanticipated problem solving stops.

Specific to this course, as mentioned above, I could’ve gotten away with less supplies – food and water – in my pack. I actually ran a Ragnar relay race with a group of fellow T1s a few years back where I finished my run segment and…no one was there to meet me. They went for Starbucks and took too long to get there, so I had to stand in the finishing chute waiting for 10-15 minutes until someone showed up to start the next run leg. Oh, and that happened in two of the three legs I ran that day. Ooof. Standing there tired, hot, with nothing to eat or drink, likely added to my already life-with-type-1-diabetes-driven-experiences of always carrying more than enough stuff. But I could’ve gotten away very comfortably with carrying 1L of water and one set of each type of snacks at a time, given that Scott could meet me at 1 mile (end of B), start (F) and end of river road (before G), and at the finish, so I would never have been more than 2-2.5 miles without a refill, and honestly he could’ve gotten to every spot on the trail barring the river crossing bit to meet me if I was really in need of something. Less weight would’ve made it easier to push a little harder along the way. Basically, I carried gear like I was running a solo 30 mile effort at a time, which was safe but not necessary given the course. If I re-ran this race, I’d feel a lot more comfortable with minimal supplies.

Surprises from my race

I crossed the finish line, stopped to get my medal, then was waiting for my brother-in-law to finish another lap (he ran the 100k: 62 miles) before Scott and I left. I sat down for 30 minutes and then walked to the car, but despite sitting for a while, I was not as stiff and sore as I expected. And getting home after a 3.5 hour car ride…again I was shocked at how minimally stiff I was walking into the house. The next morning? More surprises at how little stiff and sore I was. By day 3, I felt like I had run a normal week the week prior. So in general, I think this is reinforcement that I trained really well for the distance and my long runs up to 50k and the short to medium next day runs also likely helped. I physically recovered well, which is again part training but also probably better fueling during the race, and of course now digesting everything that I ate during and after the race with enzyme supplementation for EPI!

However, the interesting (almost negative, but mostly interesting) thing for me has been what I perceived to be adrenal-type fatigue or stress hormone fatigue. I think it’s because I was unused to focusing on challenging trail conditions for so many hours, compared to running the same length of hours on “easy” paved or gravel trails. I actually didn’t listen to an audiobook, music, or podcast for about half of the race, because I was so stimulated by the course itself. What I feel is adrenal fatigue isn’t just being physically or mentally tired but something different that I haven’t experienced before. I’m listening to my body and resting a lot, and I waited until day 4 to do my first easy, slow run with much longer walk intervals (30s run, 90s walk instead of my usual 30:60). Day 1 and 2 had a lot of fatigue and I didn’t feel like doing much, Day 3 had notable improvement on fatigue and my legs and body physically felt back to normal for me. Day 4 I ran slowly, Day 5 I stuck with walking and felt more fatigue but no physical issues, Day 6 again I chose to walk because I didn’t feel like my energy had fully returned. I’ll probably stick with easy, longer walk interval runs for the next week or two with fewer days running until I feel like my fatigue is gone.

General thoughts about ultramarathon training and effective ultra race preparation

I think preparation makes a difference in ultramarathon running. Or maybe that’s just my personality? But a lot of my goal for this race was to learn what I could about the course and the race setup, imagine and plan for the experience I wanted, plan for problem solving (blisters, fuel, enzymes, BGs, etc), and be ready and able to adapt while being aware that I’d likely be tired and mentally fatigued. Generally, any preparation I could do in terms of deciding and making plans, preparing supplies, etc would be beneficial.

Some of the preparation included making lists in the weeks prior about the supplies I’d need in my pack, what Scott should have to refill my pack, what I’d need the night and morning before since we would not be at home, and after-race supplies for the 3.5h drive home.

From the lists, the week before the race I began grouping things. I had my running pack filled and ready to go. I packed my race outfit in a gallon bag, a full set of backup clothes in another gallon bag and labeled them, along with a separate post-run outfit and flip flops for the drive home. I also included a washcloth for wiping sweat or mud off after the run, and I certainly ended up needing that! I packed an extra pair of shoes and about 4 extra pairs of socks. I also had separate baggies with bandaids of different sizes, pre-cut strips of kinesio tape for my leg and smaller patches for blisters, extra squirrel nut butter sticks for anti-chafing purposes, as well as extra lambs wool (that I lay across the top of my toes to prevent socks from rubbing when they get wet from sweat or…river crossings, plus I can use it for padding between my toes or other blister-developing spots). I had sunscreen, bug spray, sungless, rain hat, and my sunny-weather running visor that wicks away sweat. I had low BG carbs for me to put in my pockets, a backup bag for Scott to refill, and a backup to the backup. The same for my fuel stash: my backpack was packed, I packed a small baggie for Scott as well as a larger bag with 5-7 of everything I thought I might want, and also an emergency backup baggie of enzymes.

*The only thing I didn’t have was a backup baggie of electrolyte pills. Next time, I’ll add this to my list and treat them like enzymes to make sure I have a separate backup stash.

I even made a list and gave it to Scott that mapped out where key things were for during and after the race. I don’t think he had to use it, because he was only digging through the snack bag for waffles and Fritos, but I did that so I didn’t have to remember where I had put my extra socks or my spare bandaids, etc. He basically had a map of what was in each larger bag. All of this was to reduce the decision and communication because I knew I’d have decision fatigue.

This also went for post-race planning. I told Scott to encourage me to change clothes, and it was worth the energy to change so I didn’t sit in cold, wet clothes for the long drive home. I pre-made a gluten free ham and cheese quesadilla (take two tortillas, fill with shredded cheese and slices of ham, microwave, cut into quarters, stick in baggies, mark with fat/protein/carb counts, and refrigerate) so we could warm that up in the car (this is what I use) so I had something to eat on the way home that wasn’t more Fritos or waffles. I didn’t end up wanting it, but I also brought a can of beef stew with carrots and potatoes, that I generally like as a post-race or post-run meal, and a plastic container and a spoon so I could warm up the stew if I wanted it. Again, all of this pre-planned and put on the list weeks prior to the race so I didn’t forget things like the container or the spoon.

The other thing I think about a lot is practicing everything I want to do for a race during a training run. People talk about eating the same foods, wearing the same clothes, etc. I think for those of us with type 1 diabetes (or celiac, EPI, or anything else), it’s even more important. With T1D, it’s so helpful to have the experience adjusting to changing BG levels and knowing what to do when you’re dropping or low and having a snack, vs in range and having a fueling snack, or high and having a fueling snack. I had 100% TIR during this run, but I didn’t have that during all of my training runs. Sometimes I’d plateau around 180 mg/dL and be over-cautious and not bring my BGs down effectively; other times I’d overshoot and cause a drop that required extra carbs to prevent or minimize a low. Lots of practice went into making this 100% TIR day happen, and some of it was probably a bit of luck mixed in with all the practice!

But generally, practice makes it a lot easier to know what to do on the fly during a race when you’re tired, stressed, and maybe crossing an icy cold river that wasn’t supposed to be part of your course experience. All that helps you make the best possible decisions in the weirdest of situations. That’s the best you can hope for with ultrarunning!

The multivariable equation that is running with type 1 diabetes, celiac disease, and exocrine pancreatic insufficiency

I’ve written in the past about running with type 1 diabetes. I’ve tried running fasted, which works well in one sense because I have no extra insulin on board. I’ve modified my strategy further to run 2 or more hours after breakfast, so I have fuel but don’t have (much) IOB. But as I’ve extended my forays deeper into longer distance ultrarunning, and as I learned I have exocrine pancreatic insufficiency (EPI), running is getting a little more complicated.

For past thoughts on T1D running, here’s my post on running fasted and thinking about IOB. I also wrote more here last year about marathon and 50k ultramarathon training and how I use small doses of carbs to “correct” for dipping blood sugars. Last year, my body didn’t seem to need or want much additional fuel, so I didn’t force it. Part of that was likely a symptom of my undiscovered EPI. Now, however, that I am taking enzymes for pancreatic enzyme replacement therapy so I can digest what I eat, I have more energy (because my body is actually using what I eat), but I also get hungry and seem to need more fuel while running. But everything I eat needs enzymes to help me digest it, even things that I eat while ultrarunning.

So…it’s complicated to run with type 1 diabetes and micromanage insulin and carbs to manage blood glucose levels; and I’m limited in my fuel choices because I have celiac disease; and now I have to also carry, titrate, and dose enzymes for any fuel that I eat on the run as well.

Oh, and like insulin, the timing of enzymes matters. But there are no studies on enzyme digestion and how that changes during exercise, let along endurance activities like ultrarunning. So I am running in the dark, so to speak, trying to figure out things myself as I go along.

Here is more detail about what I’m doing and why I’m constantly running multivariable equations in my head while training for a 50k, 50 mile, and maybe even 100 mile run later this year:

First and foremost, managing blood sugar levels comes first.

I wear a CGM, so I can see how my blood sugar (BG) is changing during the run. I have a pump, so I can make any changes to insulin dosing. I also have an open source AID system (OpenAPS), so before running I set a higher target which tells the system not to give me as much insulin as it would otherwise. (It also does an awesome job with post-run insulin sensitivity changes! But that’s another post.) As I’ve previously written about, reducing insulin on board (IOB) when I know I’ll be running is the important first step, so I don’t have to start taking carbs and treating a low at the start of my run. Usually, my open source AID and I (by giving it a temporary target) do a good job getting me to my run start without much IOB, and ideally somewhere around 120-130 mg/dL.

From that level area, I can see rises and dips in BGs and dose accordingly. I carry easily dissolving small mint-like candies that are a few carbs (3-4g), or Airhead minis (8g of carbs), and with any dip below 120 or recurring drop that’s not coming up after 15 minutes since my last carb, I take more. These are pretty much straight sugar, and my body seems to do ok with absorbing carbs without enzymes, as long as there is no fat or protein involved.

However, with ultrarunning it’s generally considered to be ideal to proactively be consuming fuel to balance out the energy that you’re burning. Again, this is where I’m less experienced because for the last years, my body never wanted fuel and I did ok. However, now I seem to need fuel, so I’m working on figuring this out because food typically has some fat and protein, and I have to dose enzymes for it.

I carry a baggy with some single-enzyme (lipase) pills and some multi-enzyme (lipase for fat, amylase for carbs, and protease for protein) pills. I carry carefully measured single-serving snacks that I know the fat and protein quantity of. For each snack, I might need 1-2 enzyme pills of various sorts.

Timing matters: I can’t take enzymes and then snack slowly for 30 minutes. To eat slowly, I would need to take enzymes every 10-15 minutes to match the speed of eating so it will ultimately be there to help the food digest.

But, more carbs/food at once has an effect on how I feel while running and also to my BGs. I’ve tried to find things I love to eat running and can eat within 5 minutes – even while running 30 seconds and walking 60 seconds repeatedly – that are also less than 1-2 enzyme pills worth of fat and protein and aren’t too many carbs at once. These may be 15-20g carb snacks which means a bigger impact to my BG levels, and I may need to even do a small bolus (give insulin) for what I am eating. The challenge again is that food can hit BGs in about 15 minutes but it takes ~45 minutes for insulin activity to peak. And, during exercise, I’m more sensitive to insulin than I normally am. There’s no magical calculation to know how much “more” sensitive I am in the midst of a run, so I have to guess and thread the needle between not giving too much insulin that would cause a low BG but giving enough so I don’t spike above 180 mg/dL, which is what makes me feel icky while running.

Preferably, and very personally, I’d like to float up and down between 120-140 mg/dL or 130-150 mg/dL, which is higher than BGs usually hang out for me without exercise (remember: open source AID!), but is high enough that I have buffer against a low, so if I suddenly dip and I haven’t looked at my BGs in 15 minutes, I can usually still carb up and prevent an annoying low. (Lows matter even more on runs because they slow me down physically, which is usually not what I’m going for.)

It doesn’t always work that way. Sometimes I undershoot the insulin because I’ve miscalculated my effort running, and my BG drifts high and I have to decide whether or not to correct further. Other times, I overshoot (or have increased my run effort and didn’t take that into consideration) and cause BG to dip or dive toward low. Then I have to carb up but hopefully not so much that I cause a high.

My priority list therefore is: manage BGs, take in fuel, try not to over or undershoot on insulin for the fuel or overshoot carb corrections for drifting BGs, plus remember to take enzymes for the fuel and dose the right amount, plus stay on top of my electrolytes. Oh, and keep run-walking.

And along the way, I am also trying to document and learn whether the absorption of enzymes changes during different intensities or lengths of exercise; whether these over the counter enzymes are reliably measured enough for small snacks, and whether my personal ratios for fat and protein are any different during exercise the way my sensitivity to insulin changes during exercise.

It’s a lot of work. Plus, the pre-work that goes in to finding, measuring, and preparing foods that I think I want to eat during the run!

My current short list of single-serving snacks that I can tolerate while doing long runs includes: 8 gluten free peanut butter pretzel nuggets; 1 serving of chili cheese Fritos; 6 gluten free yogurt covered pretzels; and 1 gluten free stroopwaffle. Each of those is 15-20g of carb, 1-2 enzyme pills, and some of them have a bit of sodium. (I’m also fairly sensitive to sodium so I take electrolyte pills every 30-45 minutes while racing, but I’ve realized the extra fueling with a bit of sodium makes it so I don’t have to take the electrolyte pills every 30 minutes like I used to.)

When I build up to my longer (50 mile or maybe 100 mile ultras, if I get there!) runs, I’m also going to need additional “real food” options, as I doubt I will be able to or want to eat stroopwaffle and Fritos for as long as the run will take. This is just a theoretical list, but it includes tomato soup (sodium and warm liquid!), instant mashed potatoes (soft and not much chewing involved), grits and oatmeal (not together, but same reason as mashed potatoes). These all luckily also happen to be lower in fat and protein, which means easier to digest (in theory), and I am less likely to have better error margins against getting the enzyme dosing wrong given the small amounts of fat and protein.

What it comes down to is that running with type 1 diabetes is a giant constant personal science experiment. Celiac makes it more work, but also removes some of the variables by limiting what I can to eat: as at races I can’t eat out of any open bowl or package due to cross contamination concerns, and reading packages takes time, so it’s way safer to just eat what I bring myself. Having EPI on top of that means mastering the art of digesting food with pancreatic enzyme replacement therapy, which is its own special form of science experiment.

There’s a lot of variables, a lot of science, and a lot of learning going on every time I go for a run. Doesn’t it sound fun?!


(PS – If you’re someone with EPI who has some experience with endurance activity and changes to dosing enzymes..or find that it doesn’t change anything…please reach out! I’d love to chat and take my knowledge base from n=1 to n=2!)

Multivariable Equations: Running with Type 1 diabetes, celiac disease, and Exocrine Pancreatic Insufficiency

How to run 1,000 miles in a year

Everything I read about “how I ran 1,000 miles!” didn’t actually explain how to run 1,000 miles. Or it did, but not in terms I could understand.

For context, I’m a slow runner. REALLY slow. My fast days (12-13 minute miles) are most people’s super slow days. More often, I’m a 14-15 minute per mile runner. And I historically haven’t run very much. Most years I ran ~60 miles. My biggest running year was the year I ran my first marathon (2013), when I accomplished 356 miles. Since then, I’ve never gone much above 200 on a really good year. It didn’t help that I broke my ankle in January of 2019 – or maybe it did, because it made me determined to learn how to walk and run again, and use running to help me regain and improve my overall biomechanics. So I decided to run a second marathon in 2020, which was canceled from the pandemic, and 2021 became the year of the second marathon. It was scheduled for July 2021, and my goal was 400 miles for the year IF I was successfully training for the marathon, and back to a “stretch” goal of 200 miles if I didn’t end up training (because of injury or other reasons like the pandemic).

But I set out, managed 400 and even 600 miles by the end of July when I ran the full marathon. And because my training had gone well (more below with the “how to”), I decided to also continue training and tackle a 50k (31 mile) ultramarathon at the end of September. From there, I thought I’d be stuck around 800 miles but then I decided with effort that I could make 1,000 miles. And I did. Here’s how it happened:

My activity tracker after it hit 1000 miles of running

Baby steps, a focus on process, and a heck of a spreadsheet. Or as they say in answer to “how do you eat an elephant?”, “one bite at a time”, ergo, one run at a time.

I focused on building consistency first, and at a weekly level. My goal was 3 runs per week, which I had never consistently managed to do before. That started as Monday, Wednesday, Friday, with a rest day in between each run. After a few months, I was able to add a 4th run to my week, which was often Saturday. This was my first time running back to back days, and so I started with my 4th run being only one mile for a few weeks, then increased it to two miles, then up to 3 miles. My other three runs consisted of one “long” run and two other short, 3ish mile runs.

The focus on consistency at a weekly level is what enabled me to run 1,000 miles in a year. Even 400 miles felt like too much for me to tackle. But 3 (then 4) runs a week? I could focus on that.

The spreadsheet helped. I had the number of miles for each run laid out. After I completed the run (using Runkeeper tracking on my phone so I knew how far I’d gone), I would hop on my spreadsheet (using Google sheets so it could be on my laptop or on my phone), and log the miles. I found just recording in Runkeeper wasn’t a good enough psychological anchor, I wanted to “write down” the run in some way. The other thing I did was put checkboxes for the number of runs per week into my spreadsheet, too (did you know you can do that? Awesome Google Sheets feature.) So it was satisfying to open my sheet and first, check the box that I had done one of my weekly runs. Then, I entered the miles for the run. I had put in conditional formatting to check for how many miles I was “supposed” to run for that run, so that if I was within a half mile or over the run distance, it turned bright green. Another nice feedback mechanism. If I was off by more than half a mile, it was a lighter green. But regardless, it turned a nice color and emphasized that I had been putting in some miles. And, I also had a formula set to calculate the weekly total, so after each run I could see my weekly total progress. (Again, all of this is automatically done in Runkeeper or Strava, but you have to go to a different screen to see it and it’s not as satisfying to be able to track inputs against multiple outputs such as weekly, monthly, and overall totals at a glance, which is how I designed my spreadsheet).

I added a miniature chart to visualize weekly mileage throughout the year, and also a chart with a monthly view. All of these made it easier to “see” progress toward the big mileage goals.

If you’re a well-established runner, that might sound silly. But if you’re trying to build up to consistent running…find a feedback mechanism or a series of logging mechanisms (maybe it’s a bullet journal, or a handwritten chart or log, or moving marbles from one jar to another) that you can do to help cement and anchor the completion of a run. Especially when running feels hard and terrible, it’s nice to find something positive and constructive to do at the end of the run to feel like you’re still moving forward toward your goal, even when it’s hard-earned progress.

The ‘baby steps’ I took to build up to 1,000 miles literally started from baby steps: my first run was only 5 steps of running. After I broke my ankle, it was a huge effort to return to weight-bearing and walking. Running was also a huge hurdle. I started with literally running 5 steps…and stopping. Calling that a success, and going home and logging it on my sheet with a checkbox of “done!”. The second time I went, I did 5 steps, walked a while, then did a second 5 steps. Then I stopped, went home, checked the box, etc. I focused on what the smallest running I could do successfully without pain or stress, built up a series of intervals. Once I had 10 intervals strung together, I expanded my intervals of running. 10 seconds, 20 seconds, 30 seconds, etc. That took months, and that was ok. The point I focused on was the attempt: go out and “run”, with the smallest measurable interval counting as success, and not worrying about or really even focusing on overall mileage. In part, because the amounts were SO small (0.07 miles, 0.12 miles, etc – nothing to write home about). Most people who talk about starting running focus on “30 minutes” or “1 mile” or “5k” which felt so far beyond my reach coming off of the broken ankle.

So take it from me (or really, don’t listen to anyone else, including me): focus on YOUR achievable interval of running (even if it’s measured in a handful of steps), do that, call it a win, and repeat it. Over and over. You’ll find you build some strength and endurance and improve your biomechanics over time, even with baby steps and small intervals of running. The consistency and repeated efforts are what add up.

It’s ok if you find a distance or time interval that you can’t go past – maybe it’s 15 seconds or 30 seconds (or more or less) of consecutive running that’s your sweet spot. Great, stick with it. Run that interval, then walk, then run again. There’s no wrong answer for what’s the best length of interval for you. I had a bunch of foot issues pop up when I was trying to lengthen my intervals, and it turns out 30 seconds of running is my sweet spot. I can run longer (now) but I still prefer 30 seconds because psychologically and physically that feels best, whether I’m running faster or slower. So I do most of my runs with a run of 30 seconds, then walking whatever intervals I want for that run, e.g. 30:30 (run 30 seconds, walk 30 seconds), or 30:60 (run 30 seconds, walk 60 seconds), etc.

Don’t believe it’s possible to do long distances that way? I did it for my 50k ultramarathon. In my July marathon I ran 60 seconds and walked 30 seconds. I achieved my time goal but it was hard and less fun during the race. For my ultramarathon two months later, my goal was to just finish before the time limit and to have more fun than I did during the marathon. I used 30 second run, 60 second walk intervals for the ultramarathon, and it was fantastic. I beat my time goal (finishing hours before the cutoff), and felt awesome throughout and at the end of the 50k. I even passed people at the end!

Remember, there are no rules in running, other than the ones you make for yourself. But don’t listen to rules you read on the internet and feel bad because you can’t do what other people do. Do what you can, repeat it, build up safely, and if you’re having fun you’ll be more likely to continue. And like my running 1,000 miles in a year, you may find yourself reaching goals that you never would have thought were possible!

Everything I did wrong (but did anyway) training for a marathon after a broken ankle and marathon running with type 1 diabetes

This is another one of those posts for a niche audience. If you found this post, you’re likely looking for information about:

  • Running after a broken ankle (or are coming from my “tips for returning to weight bearing” and looking for an update from me, two years after my trimalleolar ankle fracture)
  • Running with the “Galloway method”, also known as run-walk or run/walk methods for marathon or similar long distances – but with information about run-walking for slow runners.
  • Running a marathon with type 1 diabetes, or running an ultra with type 1 diabetes
  • Running a marathon and training for a marathon and going without fuel or less fuel
    *Update: also running an ultramarathon with the same methods (less fuel than typical)!

There’s a bit of all of this in the post! (But TLDR – I ran my marathon (finally), successfully, despite having a previously broken ankle. And despite running it with type 1 diabetes, I had no issues managing my blood sugars during even the longest training runs, even with significantly less fuel than is typically used by marathon runners. I also ran a 50k ultra using the same methods!)

running a marathon after a broken ankle and with type 1 diabetes

First up, some context that explains why I chose run-walking as my method of running a marathon (as that also influences fueling choices) and what it is like to be a slow marathon runner (6 hour marathon ish). I broke my ankle in January 2019 and began running very tiny amounts (literally down the block to start) in summer 2019. I progressed, doing a short run interval followed by a walk interval, increasing the total numbers of intervals, and then slowly progressing to extend the length (distance and/or time) of the running intervals. In early fall 2019, I was attempting a couch-to-5k type program where I would extend my running intervals even longer, but I still had subsequent injuries (a very stubborn big toe joint, then intermetatarsal bursitis in TWO spots (argh)) that made this not work well. Eventually, I went back to running 30 seconds and walking 30 seconds, then keeping those “short” intervals and extending my run. I focused on time at first: going from 5 to 10 to 15 to 20 etc minutes, rather than focusing on distance. Once I built up to about 30 minutes of run-walking (30:30, meaning running 30 seconds and walking 30 seconds), I switched to adding a quarter or half mile each time depending on how I was feeling. But doing 30:30 seemed to work really well for me in terms of the physical impact to my feet, even with long miles, and also mentally, so I stuck with it. (You can go read about the Galloway run-walk-run method for more about run-walking; most people build up to running more, say 5 minutes or 8 minutes followed by a minute of walking, or maybe run 1 mile and then walk for a minute, or walk through the aid stations, but I found that 30:30 is what I liked and stuck with it or 60:30 as my longest intervals.)

This worked so well for me that I did not think about my right ankle a single time during or after my marathon! It took days to even remember that I had previously broken my ankle and it could’ve been problematic or weaker than my other ankle during my marathon. It took a long time to get to this point – I never thought I’d be forgetting even for a few days about my broken ankle! But two years later, I did.)

When COVID-19 struck, and as someone who paid attention early (beginning late January 2020), I knew my marathon would not be taking place in July 2020 and would be postponed until 2021. So I focused on keeping my feet healthy and building up a running “base” of trying to stay healthy feet-wise running twice a week into fall 2020, which worked fairly well. At the start of 2021, I bumped up to three runs a week consistently, and eventually began making one run every other a week longer. My schedule looked something like this:

Monday – 3 miles  Wednesday – 3 miles   Friday – 3 miles

Monday – 4 miles  Wednesday – 3 miles   Friday – 3 miles

Monday – 5 miles  Wednesday – 3 miles   Friday – 3 miles

Monday – 6 miles  Wednesday – 3 miles   Friday – 3 miles

Monday – (back to) 3 miles  Wednesday – 3 miles   Friday – 3 miles

Monday – 8 miles  Wednesday – 3 miles   Friday – 3 miles

Monday – (back to) 3  miles  Wednesday – 5 miles   Friday – 4 miles

Monday – 10 miles  Wednesday – 3 miles   Friday – 3 miles

Note that these runs I refer to were all technically run-walks, where I ran 30 seconds and walked 30 seconds (aka 30:30) until I covered the miles. I was running slow and easy, focusing on keeping my heart rate below its maximum and not worrying about speed, so between that and run-walking I was often doing 15m30s miles. Yes, I’m slow. This all enabled me to build up to safely be able to run 3 runs weekly at first, and then eventually progressed to adding a fourth run. When I added a fourth run, I was very conservative and started with only 1 mile for two weeks in a row, then 2 miles, then up to 3 miles. Eventually, later in my training, I had some of my other runs in the week be a bit longer (4-5 miles) in addition to my “long” run.

But, because I’m so slow, this means it takes a lot of time to run my long runs. If you estimate a 15-minute mile for easy math, that means an 8 mile “long” run would take at least 2 hours. With marathon training (and my goal to train up to multiple 22-24 mile runs before the marathon), that took A LOT of time. And, because of my broken ankle and intermetatarsal experiences from 2019, I was very cautious and conservative about taking care of my feet during training. So instead of following the usual progression of long runs increasing 2-3 weeks in a row, followed by a “cutback” long week, after I hit two hours of long running (essentially 8 miles, for me), I started doing long runs every other week. The other week was a “cutback” long run, which was usually 8 miles, 10 miles (for several weeks), up to eventually 12-14. In terms of “time on feet”, this meant 2-3 hours “cutback” long runs, which according to many people is the max you should be running for marathon training. That doesn’t quite work for slow runners such as myself where you might be doing a 6-hour marathon or 7-hour marathon or thereabouts. (The standard advice also maybe doesn’t apply when you are doing run-walking for your marathon training.)

I had ~6 months to build up to my marathon (from January to the end of July), so I had time to do this, which gave me a buffer in my overall training schedule in case of scheduling conflicts (which happened twice) and in case of injury (which thankfully didn’t happen). I ended up scheduling training long runs all the way to full marathon distance (26ish miles), because I wanted to practice my fueling (especially important for type 1 diabetes marathon runners, which I’ll talk about next) as well as get my feet used to that many hours of run-walking. I did my long runs without care for speed, so some of them were closer to 16-minute mile averages, some were around 15-minute mile averages for the entire run, and the day I ran the full marathon course for training I ended up doing 16+ minute miles and felt fabulous at the end.

I ended up doing a few “faster” “shorter” long runs (on my cutback weeks), where I would do a half marathon-ish distance on the actual marathon course (a public trail), and try to go faster than my super slow long run pace. I had several successful runs where I was at or near marathon pace (which for me would be around 13m30s). So yes, you can train slow and run fast for a marathon, even without much speed work, and even if you are doing a run-walk method, and even if you’re as slow as I am. Running ~15-minute miles took forever but kept my feet and body healthy and happy through marathon training, and I was still able to achieve my sub-6 hour marathon goal (running 13:41 average pace for 26.2+ miles) on race day.

Now let’s talk about fueling, and in particular fueling for people with type 1 diabetes and for people wondering if the internet is right about what fueling requirements are for marathon runners.

I previously wrote (for a T1D audience) about running when fasted, because then you don’t have to deal with insulin on board at the start of a run. That’s one approach, and another approach is to have a smaller meal or snack with fewer carbs before the run, and time your run so that you don’t need to bolus or inject for that meal before you start your run. That’s what I chose for most of my marathon training, especially for longer runs.

On a typical non-running day, I would eat breakfast (½ cup pecans, ¼ cup cranberries, and a few sticks of cheese), my OpenAPS rig would take care of insulin dosing (or I could bolus for it myself), and my BGs would be well managed. However, that would mean I had a lot of insulin on board (IOB) if I tried to run within an hour of that. So instead, during marathon training, I ended up experimenting with eating a smaller amount of pecans (¼ cup) and no cranberries, not bolusing or letting OpenAPS bolus, and running an hour later. I had a small BG rise from the protein (e.g. would go from 100 mg/dL flat overnight to 120-130 mg/dL), and then running would balance out the rest of it.

I generally would choose to target my blood sugar to 130 mg/dL at the start of long runs, because I prefer to have a little bit of buffer for if/when my blood sugar began to drop. I also figured out that if I wasn’t having IOB from breakfast, I did not need to reduce my insulin much in advance of the run, but do it during the duration of the run. Therefore, I would set a higher temporary target in my OpenAPS rig, and if I was doing things manually, I would set a temporary basal rate on my insulin pump to about ⅓ of my usual hourly rate for the duration of the run. That worked well because by the time the beginning of my run (30-45 minutes) brought my BG down a little bit from the start with the protein breakfast bump (up to 130 mg/dL or so), that’d also be when the reduced insulin effect would be noticeable, and I would generally stay flat instead of having a drop at the beginning or first hour of my run.

After my first hour or so, I just kept an eye periodically on my blood sugars. My rule of thumb was that if my BG drifted down below 120 mg/dL, I would eat a small amount of carbs. My carb of choice was an individually wrapped peppermint (I stuffed a bunch in my pocket for the run) that was 3-4g of carb. If I kept drifting down or hadn’t come back up to 120 mg/dL 10-15 minutes later, I would do another. Obviously, if I was dropping fast I would do more, but 75% of the time I only needed one peppermint (3-4g of carb) to pause a drift down. If you have a lot of insulin on board, it would take more carbs, but my method of not having IOB at the start of long runs worked well for me. Sometimes, I would run my entire long run with no carbs and no fuel (other than water, and eventually electrolyte pills). Part of this is likely due to the fact that I was run-walking at such low intensity (remember 15-ish minute miles), but part of this is also due to figuring out the right amount of insulin I needed for endurance running and making sure I didn’t have excess insulin on board. On my faster runs (my half marathon distance fast training runs, that were 2+ minutes/mile faster than my slow long runs) and my marathon itself, I ended up needing more carbs than a super slow run – but it ended up being about 30 grams of carbohydrate TOTAL.

Why am I emphasizing this?

Well, the internet says (and most coaches, training plans, etc) that you need 30g of carbs PER HOUR. And that you need to train your stomach to tolerate that many carbs, because your muscles and brain need it. And without that much fuel, you will ‘hit the wall’.

My hypothesis, which may be nuanced by having type 1 diabetes and wearing a CGM and being able to track my data closely and manage it not only by carbs but also titrating insulin levels (which someone without diabetes obviously can’t do), is that you don’t necessarily need that many carbs, even for endurance running or marathon running.

I’m wondering if there’s a correlation between people who max out their long runs around 16-20 miles and who then “hit the wall” around mile 20 of a marathon. Perhaps some of it is muscle fatigue because they haven’t trained for the distance and some of it is psychological of feeling the brain fatigue.

During my marathon, in which I ran 2+ min/mi faster than most of my training runs, I did not ever experience hypoglycemia, and I did not “hit the wall”. Everything hurt, but I didn’t “hit the wall” as most people talk about. Those might be related, or it might be influenced by the fact that I had done a 20, 22, 24, 26, and another 21 mile run as part of my training, so my legs were “used” to the 20+ mile distance?

So again – some of my decreased fueling needs may be because I was already reducing my insulin and balancing my blood sugars (really well), and if my blood sugar was low (hypoglycemia), I would’ve needed more carbs. Or you can argue my lower fueling needs are because I’m so slow (15-16 minute mile training runs, or a 13m40s marathon pace). But in any case, I wanted to point out that if the fueling advice you’re getting or reading online seems like it’s “too much” per hour, there are people who are successful in hitting their time goals and don’t hit the wall on lower fueling amounts, too. You don’t necessarily have to fuel for the sake of fueling.

Note that I am not doing “low carb” or “keto” or anything particular diet-wise (other than eating gluten-free, because I also have celiac disease) outside of my running fuel choices. This was a successful strategy for me, and I eat what might be considered a moderate carb diet outside of running fuel choices.

Ps – if you don’t fuel (carbs or other nutrients) during your runs, don’t forget about your electrolytes. I decided to keep drinking water out of a Camelbak in a running pack, rather than filling it with Gatorade or a similar electrolyte drink, but I’m pretty electrolyte sensitive so I needed to do something to replace them. I got electrolyte pills and would take them every 30 minutes or so on long training runs when it was hotter. Play around with timing on those: if you don’t sweat a lot or aren’t a salty sweater, you may not need as many as often. I ended up doing the bulk of my long runs on hot days, and I sweat a lot, so every 30 minutes was about right for me. On cooler runs, one per hour was sufficient for me. (I tried these chewable tabs in lemon-lime but didn’t like the salt feeling directly in my mouth; I ended up buying these to swallow instead: I didn’t have any digestion issues or side effects from them, and they successfully kept my electrolytes to manageable levels. The package says not to take more than 10 within a 24 hour period, but I ended up taking 12 for my longest training run and the marathon itself and suffered no ill effects. It’s probably set to max 10 because of the amount of salt compared to the typical daily amount needed..but obviously, if you’re doing endurance running you need more than the daily amount of salt you would need on a regular day. But I’m not a doctor and this isn’t medical advice, of course – I’m just telling you what I chose to do).

In terms of training, here’s everything the internet told me to do for marathon training and everything I did “wrong” according to the typical advice:

  • Your long run should be 20-30% of your overall weekly mileageWhat I did: Sometimes my long runs got up to 70% of my weekly mileage, because I was only running 3 and then 4 days a week, and not doing very long mid-week runs.
  • Have longer mid-week runs, and build those up in addition to your true long runWhat I did: I did build up to a few 5-6 mile mid-week runs, but I chose consistency of my 4 runs per week rather than overdoing it with mid-week medium runs
  • Run 5-6 days a weekWhat I did: Only run 4 times a week, because I wanted a rest day after each run, and wanted a rest day prior to my longest run. I ran Monday, Wednesday, Friday, then added Saturday short runs. Monday was my long run (because I have the benefit of a flexible schedule for work).
  • Get high mileage (start from a base of 30-40 miles a week and build up to 50-60 miles!)What I did: I started with a “base” of 10 miles a week with two runs that I was very proud of. I went to three runs a week, and then 4. My biggest running week during training was 40.55 miles, although they were all 20+ mile weeks (long or cutback weeks) after the first two months of training.
  • Do progressively longer long runs for two or three weeks in a row and then do one cutback week, then continue the progressionWhat I did: Because of the time on my feet cost of being a slower runner, I did an every-other-week long-run progression alternating with a shorter cutback week.
  • Long run, tempo run, speed work, etc. plus easy runs! All the things each week!What I did: a long run per week, then the rest of my runs were usually easy runs. I tried a handful of times to do some “speed” work, but I often time was trying to keep my feet from being injured and it felt like running faster caused my feet to be sore or have other niggles in my legs, so I didn’t do much of that, other than doing some “cutback” long runs (around half marathon distance, as well as my last 21-mile run) at close to marathon pace to get a feel for how it felt to run at that pace for longer.

TLDR, again:

I signed up for a marathon in fall 2018 planning to run it in July 2019 but was thwarted by a broken ankle in January 2019 and COVID-19(/20) for 2020, so I ultimately trained for and ran it in July 2021. I am a slow runner, and I was able to achieve my sub-6 hour marathon goal using run-walk and without causing additional injury to my feet. And, because of my “slow” or less intense running, I needed a lot less fuel than is typically recommended for marathoners, and still managed my blood glucose levels within my ideal target ranges despite 5, 6, and even 7 hours run on my feet. Yes, you can run marathons with type 1 diabetes. And yes, you can run any length endurance runs with type 1 diabetes! I also ran a 50k ultramarathon using the same methods.