Skip to content
TrailMath
Language EN FR

Heat and Altitude on Race Day: How Conditions Inflate Finish Times

Why the same fitness produces very different ultra finish times in heat and at altitude, how night running compounds the problem, and how to simulate conditions before you set a goal time.

Written by the TrailMath team Published 2 min read
Share
In this article

Fitness predicts finish time only in a vacuum. Real races add heat, altitude, and night - often in the same 24 hours. A predictor calibrated on a cool low-elevation effort will systematically lie about Western States canyon heat or Hardrock thin air.

Heat: the silent percentage tax

Hot running raises heart rate for the same pace, increases fluid and sodium needs, and eventually forces slower locomotion whether you like it or not. Canyons and exposed alpine bowls amplify radiant heat even when the start felt civilised.

Practical responses:

  • Lower the goal GAP early; banking “free time” in the heat rarely works.
  • Increase fluid and sodium with the nutrition calculator on heat-adjusted settings - then rehearse that intake.
  • Accept that mid-day sections may be hike-heavy even if the grade is runnable in April training.

Altitude: cost you cannot see on the watch

Above roughly 2,000–2,500 m, aerobic power drops for most sea-level athletes. Hardrock’s average elevation near 3,400 m is not a rounding error - it is the race. Pace charts from low-altitude ultras underpredict time and overpredict what “easy” feels like.

If your A-race is high, train some sessions elevated when you can, or at least arrive early enough to sleep high for several nights. Do not debut altitude on race morning.

Night: slower, clumsier, colder

Night running reduces visual confidence, cools the body, and often coincides with the sleepiest hours of an ultra. The same technical descent you flew in daylight becomes a hike with poles. Build darkness into the plan for any race that guarantees night hours.

Simulate before you commit to a number

Use the race conditions simulator to see how heat, altitude, and night compound on a base finish time - then compare with a terrain-aware race time predictor estimate. The useful question is not “what is my best possible time?” It is “what time survives a hot year?”

Plan for the hot year, not the perfect one.

Conditions are not excuses after the fact. They are inputs you can model before you write a goal on the hotel whiteboard.

Written by the TrailMath team

Training science, in plain terms - from the team building TrailMath.