Singletrack trail along a steep mountainside above a green valley in early morning light

Spartan Utah Ultra 50K: What My Training Data Says I Got Wrong

This post contains affiliate links. As an Amazon Associate I earn from qualifying purchases.

Thirty miles. Nearly 8,800 feet of climbing. Sixty-ish obstacles stacked on a ski mountain above 6,400 feet. I signed up for the Spartan Utah Ultra 50K with six months of honest, steady training behind me, and the mountain still took me apart. This is the post-mortem: what my training log says I did, what the race data says happened, and exactly what I would change if I toed that line again.

I have written plenty of race prep guides on this site. This one is different. Instead of telling you what should work, I pulled six months of my own training data, lined it up against the race file, and let the numbers argue with my memory. Some of it made me proud. Most of it made me wince. All of it is useful if you are thinking about a mountain ultra with obstacles, especially if you live somewhere flat.

Quick note: every number in this post comes from my own GPS watch log. I have stripped out names, locations, and route data. What is left is the training itself.

The race at a glance

30.3 midistance on my watch
8,806 ftelevation gain
12:52finish time (elapsed)
3.5 hrsstopped at obstacles, aid, and transition

The Utah Ultra ran out of Snowbasin Resort, the old Olympic venue above Ogden. Start and finish sit around 6,450 feet, and the course topped out near 9,200 feet. The Ultra format is basically the Beast course twice, with a transition area at the base where your drop bin waits for you. That bin becomes very, very tempting around mile 16. Ask me how I know.

My watch logged 9 hours and 21 minutes of moving time against 12 hours and 52 minutes on the clock. That 3.5-hour gap is obstacles, penalty loops, carries, aid stations, and one long sit at the base area. More on that later.

Know thy enemy: what this course actually is

Here is the number that should scare every flatlander reading this: the course averages about 290 feet of climbing per mile. That is not a trail race with some hills. That is a vertical race with some running.

  • Altitude is real. You spend the whole day between roughly 6,400 and 9,200 feet. If you live near sea level, your easy pace up there will feel like tempo effort.
  • The climbs are ski runs. Steep, exposed, and long. Mile 2 alone averaged a 12.7% grade. Several later miles averaged 9 to 14%.
  • The descents are loose and steep. Some miles averaged 11 to 13% downhill. Your quads pay for every one of them on lap two.
  • The obstacles hit when you are cooked. Bucket carry, sandbag carry, stone carry to the finish, and a spear throw with a penalty loop waiting if you miss. (I missed. Of course I missed.)
  • July sun at altitude. Dry air, thin air, and very little shade on the open slopes. You will dehydrate faster than you think.
Bar chart comparing 38 feet of climbing per mile in training to 290 feet per mile on the race course
Training averaged 38 feet of climbing per mile. The course averaged 290. That is the whole story in one picture.

Backwards-plotting six months of training

I took every activity from the 26 weeks before race day and rolled them up. Here is what I actually did, not what I remember doing:

  • 109 runs, 617 miles. About 23 miles per week on average.
  • Peak week: 37 miles, two weeks out.
  • Longest run: 18 miles, 20 days out, flat, a little over three hours.
  • Only three runs of 13 miles or more in the entire block.
  • 23,500 feet of total climbing in six months. That is less than three race days’ worth.
  • One logged strength session. One.
  • Nine hikes, all of them flat walks. Zero long, steep, loaded hikes.
  • Arrived at altitude five days before the race and got in three short shakeout runs.
Bar chart of weekly running miles over 26 weeks, averaging 23 miles with a 37-mile peak, and dots showing the longest run each week, maxing at 18 miles
Consistent? Yes. Enough for a 13-hour mountain day? No. Most weeks topped out with a 5 to 8 mile “long” run.
Bar chart of weekly elevation gain, typically about 920 feet, compared with a line at 8,806 feet for race day
My biggest week of climbing in six months was under 2,000 feet, and it was race week. The race asked for 8,806 in one day.

What the race data says happened

Two things jump off the race file. First, I went out way too hot. Second, the engine quietly shut down after the base area.

Two stacked charts: course elevation by mile, and heart rate by mile, showing an average of 146 bpm for the first 16.5 miles and 116 bpm for the final 13.8 miles
Same mountain, very different athlete. Heart rate averaged about 146 bpm through mile 16.5 and about 116 bpm after.

Mistake #1: I raced the first hour

Miles 3 through 5 run flat to downhill, and my heart rate sat between 165 and 169 the whole way. It peaked at 184 in mile 3. That is near-max effort in the first hour of a 13-hour day, at altitude, from a guy who trained at sea level. It felt great at the time. Fresh legs, cool morning air, everybody bombing the descent. That is exactly the trap.

Mistake #2: The second half was survival, not racing

The first 16.5 miles took about 6 hours. The final 13.8 miles took about 6.5 hours of moving and obstacles, plus a 27-minute stop at the base area. When I split the course into climbs, rolling terrain, and descents, every single terrain type slowed by roughly 30% in the back half.

Grouped bar chart of minutes per mile on climbs, rolling terrain, and descents, showing the final 13.8 miles about 30 percent slower than the first 16.5 on each
Climbs slowed 32%. Rolling terrain slowed 29%. Descents slowed 32%. This was not one bad hill. It was the whole engine.

Here is the part I find most telling. My heart rate dropped about 30 beats per minute while my pace got slower. If I were simply tired but still pushing, heart rate would have stayed up. Instead, my legs and my energy gave out before my cardio did. On the late descents my heart rate was sitting under 100 bpm. I was not running those. I was negotiating with them.

My honest read: that is what happens when your longest training day is about three hours and your race day is nearly thirteen, your legs have never seen more than 2,000 feet of climbing in a week, and you burn your matches in the first hour. Fueling probably played a role too. I can’t prove that from the watch, but nobody makes good fueling decisions after redlining at 184 bpm at 7 a.m.

What worked (credit where it is due)

  • Consistency. 26 straight weeks with no zero weeks, through a travel-heavy spring and a lot of cold, early mornings. That base is why I finished at all.
  • Durability. No injuries in the block and none from the race. Frequent, moderate runs build tough tendons.
  • The first big climb. I hiked the early ski-run climbs at a sane effort and moved well up to the high point. The problem was everything I did between the climbs.
  • Showing up a few days early. Five days at altitude is not enough to adapt, but it beats flying in the night before. I at least knew what the air felt like.
  • Finishing. Embrace the suck. It is not supposed to be easy. That’s the point.

What I would change: the flatlander’s fix

If I were training for this race again, these are the six changes I would make, in order of impact.

1. Train vert, not miles

Set a weekly climbing target and build it over 12 to 16 weeks, starting around 2,500 feet per week and working toward 6,000 to 8,000 by your peak. No mountains? Use a treadmill at 12 to 15% incline, stadium stairs, a stair machine, or parking garages. Long sessions of steady stepping beat short, hard intervals here. This is the single biggest gap in my data, and it is the cheapest to fix.

2. Build time on feet, not just distance

Your long day matters more than your long run. Work up to at least one 5 to 7 hour day: a long hike with a pack, or a back-to-back weekend (long run Saturday, long hike Sunday). On race day you will be out there 10 to 14 hours. Your body needs to have at least seen half of that.

3. Lift twice a week, and train for downhills

Step-ups and step-downs with a weighted vest, walking lunges, Bulgarian split squats, and slow eccentric squats. Those slow lowering reps are what protect your quads on miles 20 through 30. Add carries with a sandbag and dead hangs for grip. One strength session in six months does not cut it.

4. Cap your effort for the first two hours

Pick a heart rate ceiling around your normal easy-run heart rate and obey it no matter how good you feel. Hike every climb with your hands on your knees. Let people go on the first descent. You will see half of them again on lap two.

5. Have an altitude plan

The two common approaches are to arrive one to two weeks early so your body can start adapting, or to arrive within about 24 hours of the start so you race before the worst of the altitude fatigue settles in. Five days, which is what I did, is the awkward middle. Either way, slow down, drink more than you think, and take your electrolytes seriously.

6. Fuel on a clock, and treat the transition like a pit stop

Eat something every 30 to 45 minutes from the first hour, whether you feel like it or not. Pack your drop bin with a checklist: fresh socks, refill bottles, real food, sunscreen, headlamp. Then get in and get out. My 27-minute sit at the base area was comfortable. It was also 27 minutes my legs spent stiffening up.

Gear that matters on this mountain

Here is what I would pack for Snowbasin today, based on what I ran in, what failed me, and what I have tested since.

Shoes and feet

  • Topo Ultraventure 4: my current pick for long mountain days. Wide toe box for swelling feet, a Vibram outsole that grips loose dirt, and enough cushion for 4,000 feet of descending per lap. (Read my full 50-mile review.)
  • Injinji toe socks: pack a fresh pair in your drop bin. Dry socks at mile 16 feel like a spa day.
  • Powerstep Pinnacle Plus insoles: if your feet ache after long days, these are worth trying in training first.
  • Anti-chafe balm: apply before the start and again at transition. Thirteen hours of sweat and dust finds everything.

Hydration and fuel

  • Hydration vest: carry more water than you think you need. The dry air up there pulls it out of you all day. (Bladder or soft flasks both work. Personal preference.)
  • Honey Stinger gels and chews: still my go-to. Easy on the stomach when your heart rate is high and your appetite is gone.
  • Electrolyte drink mix: altitude plus sun plus 13 hours. Don’t skip salt.

Obstacles and conditions

Books that would have changed my training

  • Training for the Uphill Athlete by Steve House, Scott Johnston, and Kilian Jornet. If I had read this before 2022, this post would be a lot shorter. It is the manual for building vertical fitness and muscular endurance.
  • Relentless Forward Progress by Bryon Powell. The best practical guide to your first ultra: pacing, fueling, drop bags, and the mental game.
  • Endure by Alex Hutchinson. The science of why your body slows down long before it is truly empty. It explains my lap two better than I can.
  • Spartan Up! by Joe De Sena. For the obstacle mindset, straight from the founder.

The Utah Ultra is gone. The mountain isn’t.

Spartan dropped the Utah Ultra after 2022. Snowbasin is now a Sprint, Super, and Beast weekend every July. But in September 2026, the UTMB World Series launched Snowbasin by UTMB on the same slopes. No obstacles, just trail, altitude, and a shot at the Chamonix lottery.

  • 58K: about 36.7 miles and 5,800 feet of climbing, 12-hour cutoff, 2 UTMB Running Stones.
  • 28K: about 18 miles and 2,600 feet of climbing, 7-hour cutoff, 1 Running Stone.
  • Next edition: Saturday, September 18, 2027.

The 58K is about half as steep per mile as my Spartan course, but the cutoff is the real boss: under 19:37 per mile. My 2022 race averaged about 25:30. Everything in the flatlander’s fix still applies. Shift toward runnable climbing, long runs of 20 to 22 miles, and downhill running on tired legs. If you’re aiming for 2027, start your vert block in late May.

Still want obstacles? The Utah Spartan Beast runs every July on the same climbs. It’s basically lap one of my race, and every chart in this post applies.

Final word: the mountain doesn’t grade on effort

Six months of steady, consistent training got me to the finish line. It did not get me there strong. The data is blunt about why: I trained for miles when the race was about vertical feet, for hours when the race was about half a day, and I raced the first hour like it was a 10K.

If you live somewhere flat and you have Snowbasin on your calendar, take my log as your warning label. Climb more. Stay out longer. Lift heavier things slowly. And when the gun goes off and everyone sprints for the first descent, let them go.

See you on the mountain. Bring water.

Some links in this post are affiliate links. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you. I only recommend gear I have used or would use myself.

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *