Sunday, November 23, 2025

What I Learned Wearing a Glucose Monitor...

Mile 42 at the San Juan Solstice
...craving the sweet embrace of the sugary aid-station carbs!

I don't think that it is a controversial statement to say that as we age out of our prime years and into our more "senior" years, our bodies become less resilient and more prone to infirmities. Joints start to hurt more, backs ache, eyesight worsens, metabolism slows down, and our ability to heal becomes less effective. More simply, we become less efficient as biological machines. Years of abuse and less-than-ideal habits have a way of catching up with us (especially for those of that truly "abuse" our bodies running ultramarathons or thru-hiking). In addition to the slow and insidious degradation of our bodies at the mercy of father time, there are also the genetic ailments that we cannot escape from (although with modern advances in genetic engineering, that may change one day).

As for myself, now within reach of my 50s, I certainly have my share of genetic predispositions that I'll need to forever be aware of. Despite three of my grandparents living into their late 80s, I do have some familial history of ailments such as stroke, dementia, and Parkinson's. Additionally, cancer hasn't entirely ignored my family either. The biggest genetic factor that I have been most acutely aware of however, and the one I've been most vigilant about tracking, is my blood cholesterol. My family is rife with high cholesterol (and triglycerides)...so much so that it has led to severe clinical atherosclerosis in many members of my immediate and extended family (heart attacks, bypasses, stents, major arterial blockage...etc). It's because of this that I regularly track my numbers. Even back in my late 20's I saw that my cholesterol levels were "borderline". In those younger years, my doctors were mostly unconcerned with my numbers, citing an overall low "risk score". But as I've aged, my cholesterol has taken a more front-and-center position with regard to my health.

Over the years, my total cholesterol numbers have hovered around the 200 mg/dL recommended upper limit (with it often creeping over slightly). More importantly though, my LDL (or bad cholesterol) has always been high (always over 100 mg/dL). This is the cholesterol that the majority of published research shows leads to problems such as heart disease and atherosclerosis. Over the years I tried experimenting with my exercise and diet to improve on that number. Ever the scientist, I would change one variable at a time, keep at it for a while, and then have my numbers checked again. No matter what I did though, my numbers never improved. Exercise volume didn't matter, over-the-counter supplementation of various fish oils or omegas didn't matter, heck, even going entirely vegan didn't help. The ultimate diagnosis was that I had a mild form of Familial Hypercholesterolemia. In other words, I inherited a trait that leads to higher-than-normal levels of "bad" LDL cholesterol in my blood (and starting at a younger age than is typical).

For anyone that knows me, it might be weird to think about this. I consider myself to lead a pretty darn healthy lifestyle. I typically run 40-50 miles per week, incorporate some strength training and yoga, eat mostly well (we'll come back to this), don't drink alcohol, and am fairly fit overall (a BMI in the low 20s). It is weird to think that despite all of this, it is very possible that I could be walking around right now with significant arterial blockage due to high cholesterol and early-onset heart disease.

The good news here is that a recent cardiac calcium exam came back normal, and that for now, I do have healthy arteries. I also had my lipoprotein(a) value checked, which is another direct measure of genetic predisposition to heart disease...and it too was normal. With all of this said though, I did finally reach a point where I had to accept that changing my habits was not going to keep my cholesterol numbers safe, and that it was time to start thinking about prescription medications. 

I have always prided myself on the fact that I didn't have to take any regular medications. Any time a medical form would ask me, "what medications do you take?", I would smugly respond, "N/A" or "none".  But the time came, where I finally had to admit medications were in order. About one year ago, I started taking the smallest possible dose of a blood statin (5 mg), and my cholesterol (and triglyceride) numbers finally moved in the right direction (and moved a lot!). Every three months when I check, my total cholesterol now floats around 160 mg/dL, with my LDL and HDL both sitting around 70 mg/dL. I loathe the fact that I now take a regular medication, but the peace of mind it brings me is well worth it. I was also worried about potential side effects (especially myalgia), but thankfully, I have not been sensitive to this medication at all, and have not experienced any side effects that I know of.

So where is this post all going then, and what's with the "glucose" title?

For the past year as I've been regularly taking my tiny 5 mg statin medication daily, I have slowly lulled myself into something of a sense of biological disregard and complacency--almost a feeling of anti-vigilance with the notion that "everything is fine now, and I have nothing to worry about." But as we all know, father time continues to insidiously gnaw away at our seemingly healthy bodies, attacking us on multiple fronts.

I recently signed up for a free health screening at my work targeted for individuals over the age of 45. I somewhat smugly signed up knowing that again I would "ace" my blood numbers, and that everything else would be "in the green" as well. As expected, all of my test came back normal: cholesterol was excellent as were my weight and blood pressure. I was even tested for a specific antigen that can target very early-onset prostate issues...and it too was normal. A bone density exam came back with a reading of "bones of a 30-year old!" - woohoo.

What I didn't expect, was being told that I was officially "pre-diabetic". 

WHAT!? How could I possibly be pre-diabetic (and what even is that!?). I am a healthy, fit, athletic person that is at an ideal weight. Diabetes is usually associated with being overweight, unhealthy, and eating really poorly!!!

What I came to learn, more specifically, was that my blood glucose fasting numbers were entirely normal (around 80 mg/dL). Going back through all of my past blood tests, this number has always been between 70 and 90 mg/dL...which is considered healthy. So why then was I being flagged as "pre-diabetic?" The answer is because of a different test that I was unfamiliar with: The A1C test. An A1C test measures the average blood glucose in a person over a roughly 3-month period and is reported as a percent. A normal A1C reading should be below 5.7%. My number came back exactly 5.7%. While this number is right at the absolute lowest limit of being in this "pre-diabetic" range between 5.7 and 6.5%, it is still in that range, and why I was flagged. 

How come I had never heard about this before?

When I again went back through my past lab results it quickly became clear why I didn't know about this...because I had never had this number checked before. Given my age and my normal fasting blood glucose numbers, my doctors never thought it necessary to measure my A1C...meaning it may have been in the pre-diabetic range for some time and I simply didn't know. For hours after reading these results I kept asking myself, "WTAF!? How could I possibly be pre-diabetic?! I run 50 miles a week and eat healthy!"

But you see, it's that second part of that last sentence that turns out to be the culprit. While I don't imbibe in alcohol or gorge myself on fast food, pastries, or sugary sodas...I have come to learn that I have always had a sweet tooth and really enjoy my sugars....particularly the starchy and/or refined sugars. For example, some might reach for a handful of nuts or beef jerky for a quick snack. I will most often reach for the bag of pretzels, or the big plain bagel. Another example: Many might start their day with a couple of eggs. I start nearly every morning with a bowl of cereal. And while that bowl might be something "healthy" like plain cheerios or even oats, that cereal is always high in carbs. The other habit I've noticed is that I would often eat that bowl of cereal, and then sit at my desk to work. So, in short, I was eating a load of carbs, and then not moving. Similarly, I would often eat my dinners late, usually with a lot things like pasta, potatoes, or other starchy carbs. I think you probably see the pattern already starting to develop here and it's quite simple. I like carbs. A lot. Especially breads. Sure, as an avid runner, I need a lot of carbs. My muscles need those sweet sweet sugars to be able to move better, but my problem is that I most often ingest too many carbs in any one sitting, and typically on an empty stomach (meaning they'd absorb really quickly).

But all of these thoughts were hypotheses, guesses, and/or conjectures. I wanted to "see" what my blood was doing and specifically what habits of mine (both physically and nutritionally) were causing my blood glucose to be higher than it should be for my age and lifestyle. At first I experimented with a blood glucose meter. I would literally prick my finger before and after meals to record my blood sugar. But this quickly became bothersome and it was only giving me periodic data points (I will say that I do now have a newfound admiration for diabetics that must do this countless times a day. My fingers hurt constantly after just a week). I wanted regularly timed data to monitor and correlate with my activities and food intake. This is when I discovered CGMs - Continuous Glucose Monitors (not to be confused with GCMs or Global Circulation/Climate Models - an acronym I use a lot as a glaciologist and climate scientist). If you don't know what a CGM is, you have likely already seen them and didn't even know it. For years CGMs have been available to diabetics to wear as a way to monitor their glucose levels continuously (often in conjunction with an insulin pump). These devices are small, and typically worn on the back of the upper arm...and present as just a small "pod" stuck to the arm. The way they work is simple. When applied, the device uses a minuscule needle to insert a small sensor into the interstitial fluid around the fat cells of the arm. This sensor then measures glucose in that fluid at a regular (usually 5-minute) interval...sending the data back to a smart-device over bluetooth. The downside to such a sensor is that it is not measuring the blood directly, meaning that the values it reports are delayed about 15-minutes behind the true blood values (it takes a while for glucose to diffuse out to the interstitial fluid). This means if you want to get a "live" blood glucose measurement, you'd still need to measure blood directly from a finger prick, but, if you're someone like me, and you are mostly just interested in trends of how the body reacts to certain activities and meal choices, a CGM is an excellent scientific tool for this purpose. In March of last year (2024), CGMs became available over-the-counter and without a prescription for anyone to purchase and use...
So I bought one...and started wearing it. 
Here's what I discovered...

First of all, the data are fascinating. There is something truly captivating and remarkable about watching your own biological processes unfolding before your very own eyes. It is almost like you get a secret window to peer inside your own body and catch a glimpse of the biological machine's inner workings. Every time I would eat anything, I would eagerly pull out my phone to watch what was going to happen. How high would that measurement get? Would I experience a rapid glucose spike, or a more protracted and gradual one? What food or drink was the absolute worst for causing spikes, and how did my exercise and daily routine affect my numbers? Are there any foods I could eat before a carb-rich meal that might help smooth out the glucose spike?

Very quickly I started noticing some obvious trends and patterns...and it's these revelations that I most wanted to share...

1. The absolute worst glucose spikes happen... when I ingest high-carb meals or drinks on a completely empty stomach. This is notably worse for drinks. The worst spike I have had over the entire time I've worn the CGM (more so than any ice cream, pasta, bagel, cookies, or pizza), was when I drank a full glass of oat milk on an empty stomach. Let me say that again, OAT MILK. Not gatorade or can of sugary soda....but OAT MILK...something considered by many as a "healthy" beverage choice. What also really surprised me was how even a single food item (like one single small cookie) could obliterate my blood glucose if I ate it on an empty stomach.

What I did about it: The habit that developed was that any time I knew I had an empty stomach, I would be careful about what I ate first. I now actively try to find ways to slow the digestion of those quick carbs. This typically means either eating something oily, fatty, or high in fiber BEFORE eating or drinking any significant carbs. I also now start every breakfast with a full glass of water (and my coffee), before eating any cereal. I have also recently found a few new cereal brands that are notably lower in carbs, but just as delicious. The last two weeks I have been eating a cereal known as "Three Wishes", which I sprinkle with a spoonful of high-fiber chia seeds. This single change alone dramatically improves my morning glucose levels. This entire experience has also just been quite revealing and my mentality over meals has simply shifted. The thought of eating something like two or three Oreo cookies on an empty stomach makes me quite uncomfortable knowing what it would undoubtedly do to my blood sugar. Yet, from a big picture view, eating a couple of Oreos as a snack doesn't really seem that ridiculous....does it? These are the types of observations and habits that the CGM made me really come to notice and appreciate.

My infamous "oat milk spike"

Glucose spike after a SINGLE small cookie 
(on an empty stomach)

2. Processed or highly refined starches are also really problematic for me. I LOVE a good bagel or sandwich...but white or refined flour annihilates my blood sugar, as do other snacks that are white-flour based or highly refined (like pretzels or crackers). A single plain bagel immediately spiked my glucose over 155 mg/dL. Ironically, had I eaten a fatty cream cheese with it, my spike may have been more gradual. 

What I did about it: To help mitigate this problem I simply dialed back the white-flour and refined starches. I now eat a multi-grain seed bread as my primary bread of choice, and do my best to stay away from processed flour snacks (like crackers, pretzels, and cookies, etc.). I still have an occasional snack (although definitely much less), but try to be good about eating something with the snack that will help slow digestion. A habit I've started at work is before lunch, I'll eat a handful of mixed nuts or have a small slice of seed-bread with almond butter. Then, even if my lunch is a pasta, my glucose spike is much less severe. I also tend to stay fuller for longer by doing this. At dinner time, I'll be sure to eat my meal in such a way that the greens, veggies, fats, or meats are eaten first...before I dig into those tasty carbs with their very high glycemic indices. I also drink a full glass of water before every dinner and am simply more selective about what I might fill my plate with (perhaps less potatoes, and more salad or broccoli). When I do eat desert, I eat it slowly, and only after a full meal. Lastly, I've been very deliberate with trying to eat my dinners earlier, so that I don't go to bed while my body is still peaking with glucose, and so that I have longer fasting intervals.

6 AM breakfast spike (w/old breakfast habits)
Note the quick onset

7 AM breakfast "bump" (after changing habits/diet)
Note the more protracted bump and no spike

3. Liquids are the worst! I've already noted this, but I've become extra aware of liquids. I only drink non-sugared drinks. I have always been pretty good about this and don't drink sodas or sugary teas, but there are other drinks that many simply don't think about. That delicious chai or caramel latte? - loaded with sugar. A glass of healthy oat milk? - loaded with carbs. Iced coffee with a single pump of sweetener and maybe topped with a dollop of whipped cream? - loaded with sucrose. You get the idea. One anecdote to share: On many of my long runs I will often drink a single bottle of Tailwind sports drink....and that also spikes my glucose drastically (even while in the middle of running upwards of 20 miles!)

What I did about it: I am very careful about my liquids now. I try to stick to water or beverages sweetened with non-caloric natural sweeteners like stevia or monk fruit. If I do order a "named" drink at a cafe like a "london fog tea", I make sure to ask for stevia in place of sugar. In general, I also just try to hydrate more. I'm now that guy that carries a re-usable stainless steel water bottle everywhere.

4. Snacks! Snacks have always been my weakness. I love to snack and have always known it was not a great habit. What's more, is that when I would snack, I was often turning to those refined carbs. Why yes! I would love a bag of pretzels to snack on! I've really noticed a change over the past few weeks simply by moving to more filling snacks like nuts or nut butters. Another interesting (although tangential) data point is that I never truly realized how much I snacked until I started an Invisalign treatment for my teeth last year. Having to wear the Invisalign trays made snacking a real pain to deal with. Every time I'd want to eat something, I'd have to take the trays out, and then brush and floss after the snack. I often found that I would just skip the snack and wait until meal time instead to avoid all the trouble. I can tell you that I have never lost so much weight, so fast, as I did for that year+ with those Invisalign trays (The Invisalign Diet is real!!). Turns out, the reason I wasn't losing weight before the Invisalign (and despite running 50 miles a week) was because I snacked.... A LOT!

What I did about it: In general, I try to eat more hearty meals with more oils, protein, fats, or fiber. These keep me full and keep the temptation to snack in-between meals, away. If the one bowl of high-grain (low-sugar) cereal doesn't adequately fill me at breakfast, I might top it with an egg, avocado, or a thin slice of seed bread with peanut or almond butter. Then, I am usually not hungry again until lunch. Before I eat my dinner I will often drink a full bottle of water (sometimes with some chia seeds thrown in) to help slow digestion and temper my hunger. One important thing to note is that snacks like nuts or cheese can be really high in fats--which is also not good in high volumes--so I'm definitely not advocating for just eating tons of fatty foods.

5. Moving is key! Yes it is true that I run upwards of 50 miles per week...but I also learned quickly that I was often NOT moving DIRECTLY after my meals. This is a really bad habit when trying to control blood glucose. One of the best ways I found to smooth out glucose spikes was to simply move around a bit after a big meal. Even just a few minutes of walking greatly reduced my glucose spikes. 

What I did about it: The most notable change I made was to deliberately move after meals. At breakfast, I now walk my dog immediately after eating so that it eases any potential spike. At lunch, I will get up and go for a short walk (or plan my daily run for right after lunch). At dinner, I simply try to eat earlier and then either walk the dog again, or simply move around the house more purposefully. I sometimes delay an evening run until after dinner as well. I'm convinced the worst habit in this regard is to simply eat a big meal...and then just veg-out on the couch (especially if that meal is very late in the day).

In Summary...

I look forward to re-checking my A1C values again after the holidays to see if my efforts have helped bring my average blood glucose numbers down. Regardless of what happens though, I can definitely say that I am now eating healthier and living with better habits overall. Cutting out starchy snacks and being hyper-aware of my empty-stomach foods and beverages has had the most dramatic effect on my levels. I don't feel like I've lost much in this process either. I do still treat myself to some sweets...I am just more aware of how much I eat, and when I eat.

Another piece of interesting data I've pulled from this experiment comes from my Garmin watch. I wear my watch to bed so that it can track my heart rate and sleep data. For the past few weeks, I have had the highest HRV (heart-rate variability) and sleep scores for the entire year. I consistently score over 85 for my sleep (was typically 75-80), and over 50 for my HRV (has typically been around 40). Additionally my quality of sleep cycles has improved. I have also noticed that my "stress" scores are much lower (although I do think that this is somewhat of a fuzzy and unscientific measurement coming from my watch). All-in-all, my body seems to be liking my new habits (at least over the short term). I think I'll really need to see how things shake out over the course of the next year to truly get a sense of any overall health benefits.

Lastly, if you're curious about what it's like simply wearing the CGM...I can tell you that I completely forget it's even there. Applying the sensor for the first time did come with a very slight needle prick (akin to maybe a vaccine shot), but once in place, I never feel it. I definitely don't walk around feeling like there is a needle constantly stuck in my arm...I genuinely don't notice it and it stays on in the shower. 

An applied CGM Sensor on the back of my arm
(shown with additional waterproof "over-patch")


A few notable caveats: 

First, CGMs aren't cheap. A single Stelo brand CGM costs $50 and lasts for 15 days....meaning it costs $100 a month to wear these sensors. I used my HSA to pay for the first 2-pack, but I'd prefer not to continue tapping into those HSA funds for this "experiment" should I choose to continue. 

Second, they aren't perfect. The accuracy is less than that of a prescription CGM and definitely less than a direct finger-prick blood test. I ran several comparative tests against finger readings and the CGM consistently reads about 5-10 points higher (even during fasting). For someone like me that is not as concerned about absolute values, and more about trends, this isn't a big problem. IF I were using a CGM as a true diabetic, I would absolutely get a prescription-level device that is more accurate and then calibrate it often with direct blood tests.

Third, they can glitch out. For the first 24 hours of wearing the device, the measurements were all over the place. I learned that this is very common and it typically takes about 24 hours for the device to "settle down". This is somewhat annoying given that each sensor only lasts about 15 days....so losing an entire day to unreliable data is notable. Additionally, those wonky measurements on the first day can skew any long-term averages that you are actively tracking. 

Chaotic readings on the first day of a sensor

Fourth, sleeping directly on the device can lead to "pressure failures" and cause it to lose connection and not report glucose data. This means that you have to be careful if you are a side sleeper. Some people have noted that they wear their sensors on their abdomen for this reason, with the caveat being that the device is "not officially FDA approved to be worn anywhere but on the back of the arm"...so any measurements from an alternate site may not be a as trustworthy.

Lastly, the CGM doesn't actually last 15 days. In most cases, the CGM starts having read failures by day 14 (meaning you really lose two days per sensor if you count the first "chaotic" day of readings).

Given all of these caveats, I still think that it has been worth it tracking my numbers and learning what I've learned. I am uncertain if I will continue to wear a CGM longer term, but the insights I have gained, and new habits I've formed thus far, have been invaluable.

Here is a link to a helpful glycemic index reference chart for common foods and snacks:


...and now I'm off to my physical therapist to deal with this nagging back pain.....sigh

Sunday, November 16, 2025

Stagecoaches and Masochism

The San Francisco Peaks (and Start Line for the SC 100)

It's been a while since a posted a good old fashioned race report up here, but I had such memorable outings this past few months that I felt compelled to share the stories.

On something of a whim, I decided rather last minute to throw my name in the hat for the local Stagecoach 100 trail race here in Flagstaff. Typically each year, I run the shorter (55K) edition of this race, and always have a blast running along the Arizona National Scenic Trail up and over the shoulder of Arizona's highest peak. This year however, my training has been going remarkably well, and sometime in August a gnawing thought crept into my mind: maybe I should go for the full 100...

The Stagecoach 100 full course runs almost entirely along the Arizona Trail and continues all the way up to the small town of Tusayan, just outside of the Grand Canyon's south entrance. The route actually parallels closely with the route I ran this past May on my Canyon to Crest (Hole to Hump) adventure, but more squarely on the single-track AZT (rather than on old forest roads). A few years ago I paced a friend over the last 20 miles of the Stagecoach race and really enjoyed the trails and scenery, so it didn't take much to convince myself to go after it. Lingering deep in my mind, another small question kept poking its head up as I was debating whether to sign up. That question was, At my age (now pushing 50)...am I still capable of completing a Trail 100-miler under 24 hours? 

A decade ago, running a sub-24 time over 100 trail miles was something I was doing with a fair amount of regularity. But, this was also during a time when I was running four or five 100-mile races each year. These days, I'm lucky to get in a single 100-miler in a calendar year, despite my love of the distance. In my almost 20 years of running ultras, I remain convinced that the 100-mile distance is not only my favorite to tackle, but that it is the purest ultrarunning distance (despite the rising popularity of the 200-mile distance).

My track record at 100-miles as of late hasn't been all that noteworthy. I did have one good outing last year at a 24-hour event (covering 110 miles), but that was on a closed, paved, loop course. All of my recent 100-mile trail efforts have been well over 24 hours. I've been seriously contemplating a lot lately if father time may have just caught up to me, and a sub-24 on trails is simply no longer within my reach. 

I can still vividly remember my very first trail 100, the 2009 Vermont 100...I crossed the finish line in 23:16 and was ecstatic to earn the coveted sub-24 belt buckle (a buckle that I still wear to this day). I wanted to know if I could still accomplish this feat now over 16 years later.

Mile 75 of the 2009 Vermont 100

At the finish line of of the 2009 Vermont 100

With my training moving about as well as I could have hoped, I reached the end of September as ready as I could be for a 100-mile jaunt through the wilderness of northern Arizona. Early in the morning, C and I drove up to the Snowbowl area at the base of the San Francisco peaks and we parked at the start line near the Flagstaff Hotshots Ranch. I took in the moment as the sun began to rise, and then made my way to the start line. After a few short words from the race director, we were all of on our adventure...

The view from the start

Hanging out with my doggo at the start

...And we're off!

Right out of the gate, the course would be familiar. The 55k course uses that same course as the 100-miler...meaning for the first 6+ hours things would feel just like they always do. I knew every inch of that first 55km so my strategy was to simply run like I usually do...only a bit slower. The course is quite forgiving in that most of the steep climbing is in the first 10 miles. My strategy would be to simply take it really easy during this stretch so as to conserve for later. It did feel weird to be moving so slowly on the first climb, and watching countless people pass me, but I knew it would pay dividends later.

In what seemed like the blink of an eye, I topped out on the first climb at mile 6 and was able to open my pace up a bit as we all ran down along Hart Prairie Rd. This section of the course is always so lovely. The sun was fully up by this point and it looked like that we were going to have a spectacular weather day (I didn't know about the pop-up showers that were forecast for later in the day)

The second notable climb back up to the Arizona Trail happens at mile 13 but then the course features a very long 15+ mile descent all the way to the finish line of the 55km course. It is this descent that makes the 55k race so much fun and allow for such fast finish times. Last year (2024), I somehow managed to finish the 55k as first-place masters (men).

During the descent I put on some good music on my little iPod shuffle, and simply found my flow. For hours it seemed as though I was just vibing along the trail, moving well, but still being a bit conservative. Somewhere around mile 30, I caught up to another Flagstaff local and friend, Claire, and the two of us ran on-and-off together to the 55k finish line. I had finished the 55k race last year right at 6 hours, so my goal for the 100-miler was to try to reach the same mark in under 6:30. When Claire and I rolled in, my watch read 6:13. I was a bit worried that perhaps I was moving too fast, but I still felt great, so figured I was still probably okay. We both sat for a few minutes rummaging through our drop bags and resupplying. This was my first planned aid-station resupply point on the course, so I made sure to take my time. My next big stop wouldn't be until the "Boundary" aid station about 25 miles later, so I took extra care to make sure I had enough layers and calories.

Stagecoach 100 elevation profile

Feeling good at the mile 34 aid station (55 km)

From the 55km point (mile ~34) all the way to about mile 65, the course is mostly flat and runnable. It is also entirely exposed to the elements (with very little shade). I knew I had to move consistently through this section, but I also had to be extra careful to not fall victim to the sun and heat. At my current pace I knew I would start to burn out if I tried to keep running, and I wasn't ready to incorporate walking breaks just yet, so I chose to simply slow my pace a bit. This turned out to be a well-timed strategy as I was able to move quite well over the next several hours. Claire went on ahead as her pace was a bit swifter, but I was happy to just settle back into my own groove. There were very long stretches during this middle section of wide-open and expansive miles. Behind me and back over the mountains, large pop-up storm clouds had started forming and dropping large volumes of rain. I was glad I had managed to get ahead of it all, but I could still feel a few stray rain drops making it to me. It all put a little bit of urgency in my step trying to stay ahead of it all. I managed to somehow never get fully rained on despite the now-frequent booming thunder over the high peaks.

Through these middle miles I passed by a handful of remote aid stations and I resupplied as best I could. When it came time for the longest unsupported leg of the race, up to the Boundary station,  I made sure to fill a third bottle. The race advertises this stretch as being 11 miles, but in reality it was closer to 14. I was glad I had the extra fluids. 

I reached Boundary (~mile 58) in about 11 and a half hours into my race, just as the sun was starting to set behind the mountains. I realized as I rolled in that I didn't have my headlamp on me, so I definitely cut it a bit close with this aid station. I did have my high-powered light in my drop bag, but I also made sure to grab my smaller back-up light just in case. I again spent several minutes refueling and resting while at this station. I was about to start into the long night miles of the course, and I wanted to make sure I had everything I needed: layers, lights, nutrition, music, clean socks, hat, gloves. Of all the aid stations, I spent the most time at Boundary...probably about ten total minutes. I knew this was a bit much, but I really didn't want to forget something and I wanted to make sure I was able to take in plentiful calories. 

Leaving Boundary, I continued to head north up towards the next pine forest. I had a somewhat protracted climb for many miles, but it was relatively gentle, so I was still able to jog for most of it. For several hours along this part of the course (from miles ~65 onward), I never saw another runner. I felt as though I was on a solo journey run (just like my canyon-to-crest run). I would roll into aid stations and surprise the volunteers. They'd tell me that they hadn't seen anyone in over 20 or 30 minutes. When I would leave, I was sure someone was going to catch up to me...but I never saw a single headlamp behind me, even in places where I could see back along the course for miles.

It's this exact time during a 100-miler that I so cherish. The wee hours of the night, all alone in the dark...it's simply indescribable. I was in may perfect happy place and the miles just melted away. I found myself in a truly blissful state until around mile 75 when my toe caught a rock and I went face down into the dirt. Thankfully, I was able to break the fall fairly well, but it was still wildly frustrating. My knees did get a little banged up, but otherwise I was just annoyed that the fall completely disrupted my positive vibes.

Around mile 80, the course takes runners on a 2-mile out-n-back stretch to the Hull Cabin aid station. I remembered this section from when I paced my friend a few years back. The course descends something like 400 feet down a steep road to the cabin, and then runners turn around and go right back up. It's annoying, but it also gave me a chance to see if anyone was even remotely close behind me. 

I spent only a few minutes at this station and then started the climb back up. Somewhere about half-way up the climb I finally saw a runner coming down towards me...putting them about 2.5 miles behind me. I realized at this point that as long as I kept moving, it was very unlikely anyone would catch up to me over the final 20 miles.

Once back up on the Arizona Trail the course trends back downhill over the final 20 miles. I was now hiking a fair amount as my legs were getting really heavy, but I continued to move over 3 mph pace on average. I hit the last aid station (~mile 91) under 21 hours, so I knew that as long as I kept moving, I should hit the finish in under 24. This realization put a little extra pep in my step and I picked up my pace.

I cruised along the gentle trail under the canopy of ponderosa pine trees and I could see the sky starting to light up a bit. By the time I reached mile 99 on the course and the last small climb, it was sufficiently light out to turn off my headlamp (although still before sunrise). I pulled out my phone--which had been off the entire race--and sent a quick text to C letting her know that I was about 20 minutes from the finish line. My watch read 23:20 at this point, so I knew I was going to make it under 24. 

Just as I was turning my phone back into airplane mode, I noticed that it started chiming with multiple text messages and voice mails. Weird, I thought. When I looked at who they were all coming from, I saw that they mostly came from work colleagues. One of the voicemail transcriptions simply said that the person needed to talk to me about one of my students. I noticed that these all came in several hours ago, so I figured whatever it was, it could wait another 20-30 minutes until I was sitting at the finish line. I switched off my phone, and it put it all out of my mind. I had a mission, and I wasn't going to get distracted now.

I rolled over the last small high point, trotted through the small tunnel that goes under the highway, and popped out on the final bike path that leads to the finish line. From here it was a mere 1/2-mile to the end. Over these final few minutes I thought back to early miles and I was thrilled at how the entire experience played out. I had a really good run, my body held up well, and I didn't have any major issues (other than the fall). I was able to run consistently for most of the race, and I was about to finish a 100-mile trail run under 24 hours (something I hadn't done for a while, and wasn't sure I could still do). Needless to say, I was feeling ecstatic. Just as I rounded the last bend in the bike patch, I could see the finish line stanchion. There waiting for me was C with my doggo. I stopped for a brief minute to hug them both, and the quickly jogged up through the finish line chute. I definitely was looking forward to sitting in that chair.

Nearing the finish line

My doggo waiting for me at the end...

My final finish time: 23 hours, 36 minutes.

When I rolled through the finish line, my watch read 23 hours, 36 minutes...and I couldn't possibly have been happier. But that's when everything changed.

As I eagerly sat down in that old camp chair, thrilled to be done with my run, and excited to eat whatever food I could shove down my gullet, I remembered my phone. I told C about how when I turned on my phone a mile back to text her, it was weird that I got a whole slew of messages from work colleagues. As soon as I said this, her entire demeanor changed. It was clear she had been holding something back, and she immediately started crying. What I learned in that moment was that while I was happily navigating beautiful single-track trails through the northern Arizona woods, one of my graduate students had been killed in a car accident. Never in my life can I remember falling from such a high moment, to such a low moment, so quickly. We gathered my belongings and left for home almost immediately. Along the 90-minute drive home, my conflicting emotions had become too much for me and my exhausted body revolted. In all my years of running ultras, only once before have I gotten so sick at a finish line (and that other time was when I had a stomach flu at Badwater). It is a strange juxtaposition: less than hour prior I was on cloud nine celebrating a sub-24 finish, and now I was leaning out of the car along Interstate-40 heaving violently.

It's been almost two months since that finish, and I still think of my student daily. I think of his family and how much joy and optimism he brought to the classroom. Just two days prior I had spoken with this student about jobs he was applying for post-graduation. It's hard now to think about Stagecoach, and I'm not sure I'll want to ever run it again because of this association. I suppose I wanted to share this story as a reminder that no matter how much we prepare for certain things, there are always other things that happen that we can't prepare for.

_________________________________________

In this post I wanted to also briefly speak about my recent running at the Mountain Masochist 50-miler. The MMTR is a race that I aim to run every year as it has become of a reunion of sorts with many of my fellow Barkley friends. I've written about this event many times before on this site, so I won't bore you all again with the details. The short of it is that this was my ninth running this year! I eagerly look forward to my tenth running next year as 10-time finishers are given a special finishers jacket and recognition. Ten finishes at the MMTR is a huge milestone that many strive for.

The short recap for this year was that it was an overwhelming success. I ran with fellow Barkley finishers Travis and Brett, as well for a few miles with JB. We had perfect weather, and our pace was again spot on (finishing in about 11 hours 45 minutes).

This event has become something I genuinely look forward to every year as it is one of the few times I get to spend a few days away with friends. This year, we all flew out of DC, so following our run, we spent an entire day touring the National Mall (on scooters no less!). We also watched game 7 of the world series together and had fun cheering for Toronto (even though they lost in the most heartbreaking way).

...and I think I'll end it there. The year is coming to an end soon and I have one 50k race left on the calendar. Otherwise, I look forward to winding things down a bit over the winter break.

The gang at mile ~36 on Mt. Pleasant

The gang at the finish line

Jefferson Memorial

Scooters at the Jefferson Memorial

Washington Monument

Lincoln Memorial

Capitol Building

Thursday, July 17, 2025

A 14-Year Colorado Mountain Journey Comes to an End...

On the summit of Snowmass Mountain (#58/58)

This past Wednesday, July 9th, I crested a mountain ridge after a several-hour-long approach climb, and walked over to the distinctive rock marking the highest point. Upon reaching this rock, I had achieved something that I had worked over 14 years to complete. This highest point was the summit of one of Colorado's well known 14,000+ foot peaks (aka "14ers"): Snowmass Mountain. This moment marked the 58th time I had reached such a peak, making it my final 14er summit. My celebration was somewhat subdued at the moment as I knew I still had a difficult down-climb back to relative safety, but in my heart I knew that my protracted and arduous mountain quest was finally over....and I had found success.

The story truly begins back in the summer of 2008. As a first year graduate student, I made my first trip out to Denver in order to process some ice-core samples at the National Ice Core lab. While there, I had my first taste of big mountains when I drove up my first 14er: Mt. Evans (now called Mt. Blue Sky). I can still recall driving to the summit parking area, and then hiking the few hundred feet up to the true summit...all while gasping for air. Just three weeks later, once I had completed my lab work, I thru-hiked the entire Colorado Trail just to fully immerse myself in the mountains and learn whatever it was they could teach me.

My first time on Mt. Blue Sky in 2008 (then Mt. Evans)

I would ultimately make many trips to Colorado over the next few years, but it was in 2011 while working alongside another student at the ice-core lab, that I first learned of the "14ers." This student, Nate, told me that there were 58 "official" 14er peaks, and that many set out to summit them all. He went on to tell me that while most of these 58 peaks are relatively easy climbs, at least a dozen would require difficult class 3 and even class 4 climbing (a concept completely foreign to me as an east coaster). A few days after learning of the 14ers, Nate suggested we head over to Mt. Bierstadt together, for what would be my first official "summit". While technically I had stood atop Mt. Blue Sky back in 2008, I had learned that a 14er summit doesn't really "count" if you drive it. In order to truly "earn" a 14er, you have to reach its summit under your own power.

On June 19th, 2011, Nate and I hiked up to the summit of Mt. Bierstadt and I checked off my first official 14er summit. From that moment, I was hooked and I knew that one day, I would finish them all...

Me and Nate on Mt. Bierstadt (#1/58) - 2011

Over the next fourteen years, I would make regular trips out to Colorado for lab work, races, or vacation. Each time I made my way out to the Rocky Mountain State, I would find time to squeeze in at least one or two 14er hikes. Sometimes I would get in several summits on one trip, other times, I would have to abort climbs due to bad weather. Typically though, I'd average about 4 or 5 summits per year and after several years and about 30 summits, I knew that things were getting serious. I started making sincere and strategic plans for how I might finish all the peaks, including the ones that would require incredibly difficult climbing that I wasn't yet prepared for.

One last note before we get to my journey: People always ask me how I'd rank the difficulty of the summits. I think this is a hard thing to quantify as the metrics are somewhat fuzzy and it frankly depends on who you ask. Some people really detest exposure (like me), while others don't mind it. Some love a good class 4 scramble (like me), while others are terrified by them. For me, difficulty comes down to how uneasy, scared, or anxious I felt on a mountain. So given this, I would rank my ten most difficult peaks as follows:
  • 1: Capitol Peak (most difficult)
  • 2: Pyramid Peak
  • 3. Crestone Needle 
  • 4. North Maroon Peak
  • 5. Maroon Peak
  • 6. Little Bear Peak
  • 7. Crestone Peak 
  • 8. Snowmass Mountain
  • 9. Sunlight Peak
  • 10. Wilson Peak and Mt. Eolus (tie)
Now...rather than litter this post with pages and pages of text, I figured I'd best share my journey through pictures. I went back through my digital photos and was able to find summit pictures from nearly every single 14er summit (with a few exceptions). So, given this, let's now revisit my journey through Colorado's 58 14er peaks....

NOTES:
  • All elevations reflect updated 2024 LiDAR measurements
  • I've included relevant links where I have them

#1/58 : Mt. Bierstadt - 14,069' - June 19, 2011
(Summited with Nate - First 14er)
*no GPS watch*

#2/58 : Mt. Sherman - 14,043' - June 26, 2011
(Summited after running the slacker half-marathon)
*no GPS watch*


#3/58 : Grays Peak - 14,275' - June 27, 2011
(Summited together with Torreys Peak)
*no GPS watch*

#4/58 : Torreys Peak - 14,272' - June 27, 2011
(Summited together with Grays Peak)
*no GPS watch*

#5/58 : Mt. Elbert - 14,438' - August 18, 2011
(Summited before running the Leadville Trail 100)
*no GPS watch*

#6/58 : Uncompahgre Peak - 14,318' - August 28, 2011
(Summitted with C, favorite 14er)
*no GPS watch*

#7/58 : Quandary Peak - 14,272' - August 4, 2012
(I would probably rank this as the easiest 14er overall)
*no GPS watch*

#8/58 : Mt. Democrat - 14,154' - August 5, 2012
(Summited as part of De-Ca-Li-Bron)
*no GPS watch*

#9/58 : Mt. Cameron - 14,248' - August 5, 2012
(Summited as part of De-Ca-Li-Bron)
*no GPS watch*

#10/58 : Mt. Lincoln - 14,293' - August 5, 2012
(Summited as part of De-Ca-Li-Bron)
*no GPS watch*

#11/58 : Mt. Bross - 14,178' - August 5, 2012
(Summited as part of De-Ca-Li-Bron)
*no GPS watch*

#12/58 : Longs Peak - 14,259' - August 14, 2012
(First true class 3 climb with exposure - Keyhole Route)
*no GPS watch*

#13/58 : Mt. Massive - 14,427' - August 16, 2012
(Summited before Leadville 100 Trail Run)
*no GPS watch*

#14/58 : La Plata Peak - 14,344' - August 14, 2013
(Summited before Leadville 100 Trail Run)
First 14er with GPS watch

#15/58 : Mt. of the Holy Cross - 14,007' - August 20, 2013
(First experience with bad weather)

#16/58 : San Luis Peak - 14,023' - August 26, 2014
(Summited from South Ridge via Creede)

#17/58 : Huron Peak - 14,006' - August 27, 2014
(Was snowed on during descent)

#18/58 : Mt. Blue Sky - 14,268' - June 5, 2016
*No summit photo taken on this climb*
I have been up Blue Sky more times than any other 14er
(Summited via complete road run/hike with friend Gina)

#19/58 : Mt. Princeton - 14,200' - June 18, 2016
(Summited as double with Yale via South Ridge w/Jared)

#20/58 : Mt. Yale - 14,200' - June 18, 2016
(Summited as double with Princeton via East Ridge w/Jared)

#21/58 : Missouri Mountain - 14,071' - June 26, 2016
(Summited as triple with Belford and Oxford)

#22/58 : Mt. Oxford - 14,158' - June 26, 2016
(Summited as triple with Missouri and Belford)

#23/58 : Mt. Belford - 14,202' - June 26, 2016
(Summited as triple with Missouri and Oxford)

#24/58 : Mt. Harvard - 14,424' - July 14, 2016
(Summited as double with Columbia)

#25/58 : Mt. Columbia - 14,075' - July 14, 2016
(Summited as double with Harvard)

#26/58 : Mt. Sneffels - 14,155' - July 15, 2016
(Summited in the evening - difficult class 3 sections)

#27/58 : Mt. Shavano - 14,230' - July 21, 2016
(Summited as double with Tabeguache)

#28/58 : Mt. Tabeguache - 14,158' - July 21, 2016
(Summited as double with Shavano)

#29/58 : Mt. Antero - 14,271' - June 17, 2017
(Last 14er in the Sawatch Range)

#30/58 : Humboldt Peak - 14,068' - July 4, 2017
(Summited on the Holiday)

#31/58 : Challenger Point - 14,068' - July 7, 2017
*No Photo - track shows climb from Willow Creek*
(Summited as double with Kit Carson)

#32/58 : Kit Carson Peak - 14,167' - July 7, 2017
*No Photo - track shows climb from Willow Creek*
(Summited as double with Challenger Point)

#33/58 : Blanca Peak - 14,359' - July 8, 2017
(Summited as triple with Ellingwood Point and Little Bear Peak)

#34/58 : Ellingwood Point - 14,057' - July 8, 2017
(Summited as triple with Blanca Peak and Little Bear Peak)

#35/58 : Little Bear Peak - 14,041' - July 8, 2017
First true Class 4 climb via Hourglass Route
(Summited as triple with Ellingwood Point and Blanca Peak)

#36/58 : Mt. Lindsey - 14,055' - July 12, 2017
(Route featured a sustained class 4 pitch)

#37/58 : Wilson Peak - 14,021' - July 13, 2017
(Overcast fog - First truly technical ascent)

#38/58 : Culebra Peak - 14,053' - January 14, 2018
(First and only Winter summit - Paid for permit to climb)

#39/58 : Redcloud Peak - 14,037' - July 12, 2018
(Summited as double with Sunshine Peak before Hardrock 100)

#40/58 : Sunshine Peak - 14,004' - July 12, 2018
(Summited as double with Sunshine Peak as training for Hardrock 100)

#41/58 : Wetterhorn Peak - 14,021' - July 13, 2018
(Summited as training for Hardrock 100)

#42/58 : Mt. Eolus - 14,087' - July 16, 2018
Hiked the four Chicago Basin peaks in two days with C
Took train and hiked in from Needleton trail head
(Summited as double with North Eolus)

#43/58 : North Eolus - 14,042' - July 16, 2018
Hiked the four Chicago Basin peaks in two days with C
Took train and hiked in from Needleton trail head
(Summited as double with Mt. Eolus)

#44/58 : Sunlight Peak - 14,061' - July 17, 2018
Hiked the four Chicago Basin peaks in two days with C
Took train and hiked in from Needleton trail head
I DID climb the final class 4 (exposed) summit block 
(Summited as double with Windom)

#45/58 : Windom Peak - 14,089' - July 17, 2018
Hiked the four Chicago Basin peaks in two days with C
Took train and hiked in from Needleton trail head
(Summited as double with Sunlight)

#46/58 : Handies Peak - 14,058' - July 22, 2018
*No Photo* - track shows descent from summit during race
(Summited during the Hardrock 100 Run w/Travis)

Hardrock 100 Finish Line - 2018

#47/58 : Mt. Wilson - 14,256' - August 17, 2018
(Summited as double with El Diente)

#48/58 : El Diente Peak - 14,175' - August 17, 2018
Did NOT do the traverse - was hailed on
(Summited as double with Mt. Wilson)

#49/58 : Crestone Peak - 14,299' - July 13, 2021
Difficult class 3
(Summited as double with Crestone Needle - No Traverse)
*no GPS watch - was broken*

#50/58 : Crestone Needle - 14,196' - July 13, 2021
Scariest summit to date - very difficult class 4 sections
(Summited as double with Crestone - No Traverse)
*no GPS watch - was broken*

#51/58 : Castle Peak - 14,274' - July 12, 2022
(Summited as double with Conundrum)

#52/58 : Conundrum Peak - 14,037' - July 12, 2022
Descended via long snow glissade
(Summited as double with Castle Peak)

#53/58 : Maroon Peak - 14,163' - July 10, 2023
Incredibly difficult climb - many technical class 4 pitches
(Summited before Hardrock 100 Run)

#54/58 : North Maroon Peak - 14,022 - July 14, 2024
(Incredibly difficult climb - On par with Crestone Needle and Maroon Peak)

#55/58 : Pyramid Peak - 14,029' - July 15, 2024
(Most challenging summit to date - incredibly difficult)

#56/58 : Pikes Peak - 14,109' - June 11, 2025
(Summited via Crags Trail - lots of snow up high)
I had been on pikes in 2017, but drove to summit

#57/58 : Capitol Peak - 14,138' - July 7, 2025
(Most difficult of all the 14ers - without any doubt)
...Knife edge was terrifying

#58/58 : Snowmass Mountain - 14,105' - July 9, 2025
(Summited via West Slopes - Difficult class 3)
Final 14er summit

...and just for fun....here is a little low-res video clip of me traversing the Knife Edge on Capitol. See if your palms get sweaty watching it...