Racing Ultras at Altitude: A Sea Level Guide
Racing Ultras at Altitude: What Sea Level Runners Need to Know¶
You trained all year at sea level. Your legs are strong, your fueling is dialed, your long runs are locked in. Then you fly to Leadville, step out of the car at 10,200 feet, and walk up a flight of stairs that makes you breathe like you just ran 400-meter repeats.
Altitude changes everything. It changes how fast you can run, how well you digest food, how deeply you sleep the night before, and how your body processes the effort you're giving it. The runners who have good days at altitude are rarely the fittest runners on the start line. They're the ones who understood what altitude would do to them and planned for it.
This guide covers exactly that. You'll learn:
- How much altitude actually slows you down (with real numbers)
- The acclimatization timelines that matter for race week
- How to adjust your pacing, fueling, and hydration above 5,000 feet
- What to do if you can only fly in a day or two before the race
How Altitude Affects Your Body (and Your Pace)¶
At sea level, the atmosphere pushes oxygen into your lungs at full pressure. At 5,000 feet, that pressure drops roughly 17%. At 10,000 feet, it drops about 30%. Your body responds by working harder to deliver less oxygen to your muscles.
The measurable impact is significant. Research published in the Journal of Applied Physiology found that VO2max decreases approximately 6-7% per 1,000 meters (3,280 feet) of elevation gain in trained endurance athletes. In practical terms:
- 5,000 feet: Expect 3-5% pace reduction at the same effort
- 7,500 feet: Expect 8-12% pace reduction
- 10,000+ feet: Expect 12-18% pace reduction
For a sea level ultra runner who runs comfortable long run pace at 10:00/mile, that same effort at 10,000 feet might feel like 11:15-11:50/mile. And that is not accounting for the additional elevation gain most mountain ultras throw at you.
The key point: altitude does not make you less fit. It makes the same fitness produce less speed. If you try to run your sea level paces at altitude, you are not being tough. You are blowing up.
The Acclimatization Timeline: When to Arrive¶
This is the single most confusing part of altitude racing, and the answer depends on how much time you have.
The 24-72 Hour Danger Zone¶
When you arrive at altitude, your body starts responding immediately. But the first two to four days are actually the worst. Your blood plasma volume drops, sleep quality tanks, and many runners experience headaches, nausea, and fatigue. This is when acute mountain sickness is most likely.
Racing during this window (24-72 hours after arrival) is the worst possible timing. You get none of the acclimatization benefits and all of the negative acute effects.
Three Arrival Strategies¶
Strategy 1: Arrive the morning of (or the night before)
If you cannot get to altitude early, this is your best fallback. You race before the acute effects fully kick in. You will still feel the reduced oxygen, but you avoid the worst of the adjustment period. Many experienced altitude racers use this approach when logistics prevent early arrival.
Strategy 2: Arrive 5-10 days early
This is the sweet spot for most runners. By day five, the worst acute symptoms have passed. Your body has begun increasing red blood cell production and your breathing rate has normalized. You will not be fully acclimatized, but you will feel dramatically better than you would on day two or three.
Strategy 3: Arrive 3-6 weeks early (or live at altitude)
Full acclimatization takes three to six weeks. This is the gold standard but impractical for most amateur runners. If you can swing even two weeks, you will recover most of the performance gap.
The Bottom Line¶
If you have less than five days, arrive as late as possible (ideally race morning or the night before). If you have five or more days, arrive early and give your body time to adjust. The middle ground of two to four days is the worst of both worlds.
Pacing at Altitude: Throw Away Your Watch¶
This is where most sea level runners destroy their race. They look at their watch, see a pace slower than training, and speed up. By mile 20, they are walking.
Use Effort, Not Pace¶
At altitude, your GPS pace is lying to you. A 10:30 mile at 9,000 feet might require the same cardiovascular effort as an 9:15 mile at sea level. If you pace by the watch, you will run too hard.
Switch to effort-based metrics:
- Heart rate: Expect your heart rate to run 10-20 BPM higher than sea level at equivalent effort when racing above 7,000-10,000 feet. The response is individual and non-linear, so do not apply a simple per-thousand-feet formula. Instead, test your altitude HR during easy runs in the days before the race and recalibrate your zones.
- Perceived effort: Learn the RPE scale and trust it. Your long run effort should feel like a 5-6 out of 10 in the early miles, even if the watch says you are slow.
- The talk test: If you cannot speak in full sentences on the climbs, you are going too hard. Period.
The First Third Rule¶
In any ultra, the first third of the race should feel easy. At altitude, this rule becomes even more important. Start 10-15% slower than your target effort, not your target pace. Your body needs the first several miles to calibrate to the altitude, especially if you arrived recently.
Mid-Race Altitude Gain: The Part Most Guides Skip¶
Mountain ultras do not stay at one altitude. At Leadville, you start at 10,200 feet, climb to over 12,600 at Hope Pass, and do it twice. At Hardrock, you hit 13,000+ feet multiple times. Your body has not acclimatized to 13,000 feet even if you spent a week at 10,000.
Think in terms of time-to-next-aid-station and effort management, not pace per mile. At mile 55 with a 3,000-foot climb ahead and six hours of daylight left, the question is not "what is my pace." It is "can I sustain this effort for the next three hours without cracking." That reframe changes how you allocate energy across the entire race.
When you hit sections above your acclimatization altitude, slow down further. Power hike aggressively. Eat and drink at every opportunity. These high points are where races are lost, not won.
See how NavRun builds race-day pacing plans from your actual Strava data ->
Fueling and Hydration Above 5,000 Feet¶
Altitude changes your fueling equation in three ways that catch runners off guard.
You Burn More Carbs¶
At altitude, your body shifts toward carbohydrate as its preferred fuel source. Research shows that carbohydrate oxidation rates increase at elevation, meaning you burn through glycogen faster than at sea level. For ultra runners, this means:
- Start fueling within the first 20-30 minutes, not the first hour
- Target 10-15% more calories per hour than your sea level plan
- Lean toward simple sugars and easily digestible carbs (your gut is already under stress)
You Lose More Fluid¶
The air at altitude is drier. Your breathing rate is higher. Both of these increase fluid loss through respiration. Many runners do not realize how much water they are losing just by breathing harder in dry mountain air.
- Front-load hydration the day before the race
- Sip consistently rather than drinking large volumes at aid stations
- Monitor urine color as a practical hydration gauge
- Add electrolytes to every bottle, not just when you feel thirsty
Your Gut Gets Unpredictable¶
Reduced blood flow to the digestive system at altitude can make foods you tolerate perfectly at sea level suddenly problematic. The higher you go, the more your gut rebels.
- Test your race nutrition at altitude during training if possible
- Bring backup fuel options you have never tried at altitude but know your stomach tolerates at sea level
- Liquid calories (gels, drink mixes) are generally easier to absorb than solid foods above 8,000 feet
Training for Altitude When You Live at Sea Level¶
You cannot fully simulate altitude at sea level. But you can prepare your body for what it will face.
Build a Bigger Aerobic Engine¶
A larger aerobic base gives your body more headroom when oxygen availability drops. Focus on:
- High-volume, low-intensity weeks in the 8-12 weeks before your race
- Long runs at conversational pace (these build the mitochondrial density that helps at altitude)
- Consistent easy mileage rather than occasional big weeks
NavRun's AI training plans build around your actual training history ->
Hill Work and Vertical Gain¶
Mountain ultras at altitude are almost always steep. Your sea level training should include:
- Weekly vertical gain targets (aim for at least 50-75% of your race's weekly vert in peak training)
- Power hiking practice on steep grades (most runners walk anything over 15-20% grade at altitude races)
- Downhill-specific training to prepare your quads for the pounding
Consider Altitude Simulation¶
If budget allows, altitude simulation tools can help:
- Altitude tents: Sleep in a hypoxic tent at simulated 8,000-9,000 feet for 4-6 weeks before the race. Research on "live high, train low" shows meaningful increases in red blood cell production.
- Altitude masks: These increase breathing resistance but do not actually reduce oxygen percentage. They train breathing muscles, not altitude adaptation. Limited evidence of real altitude benefit.
- Pre-race altitude camps: Even one to two weeks at moderate altitude (5,000-7,000 feet) can jumpstart acclimatization.
Check Your Iron¶
This is the overlooked piece. Your body needs iron to produce the extra red blood cells that altitude demands. If your ferritin levels are low (below 30-40 mcg/L), your adaptation will be blunted. Get bloodwork done 8-12 weeks before your race. If ferritin is low, work with your doctor on supplementation.
Race Week at Altitude: A Practical Checklist¶
Whether you arrived a week early or flew in the night before, here is how to handle race week.
If you arrived 5+ days early:
- Keep runs short and easy for the first 3 days. Drop intensity and volume by 20% beyond your normal taper
- Do not test fitness with hard efforts at altitude. Trust your sea level training
- Sleep may be rough the first few nights. This is normal. It improves by night 4-5
- Hydrate aggressively starting the day you land
If you arrived the night before:
- Do not explore the course on foot the day before. Conserve energy
- Sleep as low as possible if the race start is at a higher elevation than town
- Eat familiar foods. Do not try the local cuisine the night before
- Accept that the first few miles will feel strange. Your body will adjust somewhat during the race
Every runner, regardless of arrival time:
- Pack 20% more nutrition than your sea level calculations suggest
- Carry extra layers (mountain weather at altitude changes fast)
- Set your watch to show heart rate or effort, not pace
- Brief your crew (if you have one) that you will be slower than sea level paces and that this is the plan, not a problem
Altitude Racing Mistakes That End Races¶
Learn from the runners who went before you.
Going out too fast. This is the number one race-ender at altitude. The first few miles at a mountain 100 feel great because of race adrenaline. By mile 25, you are paying for it with interest. Start boring-slow.
Ignoring early symptoms. Headache, nausea, dizziness in the first hours at altitude are signals, not inconveniences. If you feel acute mountain sickness symptoms building, slow down immediately. Pushing through AMS does not make it go away. It makes it worse.
Sticking to sea level nutrition plans. Your gut is different at altitude. If your plan says 250 calories per hour and your stomach says no, listen to your stomach. Switch to liquids. Eat smaller amounts more frequently.
Neglecting sun protection. UV exposure increases roughly 10-12% per 1,000 meters of elevation gain. At 10,000 feet, you are getting significantly more UV radiation than at sea level. Sunburn drains energy and causes dehydration. Wear sunscreen, a hat, and consider arm sleeves.
Skipping the power hike. Walking steep climbs is not a sign of failure at altitude. It is a pacing strategy used by every experienced mountain ultra runner. Walk the uphills aggressively, run the flats and downhills. Your finishing time will thank you.
Common Questions About Altitude Ultra Racing¶
Q: How much slower should I expect to be at altitude compared to sea level?¶
For most runners, expect 10-15% slower overall times at races above 8,000 feet, compared to a flat sea level ultra of the same distance. At 10,000+ feet with significant climbing, 15-25% slower is realistic. The exact impact depends on your acclimatization status, the course profile, and individual physiology.
Q: Does fitness level matter? Are faster runners affected more or less?¶
Research suggests that highly trained athletes may actually experience a slightly larger relative performance decrease at altitude because they are already operating closer to their physiological ceiling. However, fitter runners also tend to acclimatize faster. The net effect is roughly equal across fitness levels.
Q: Can altitude tents really help?¶
Yes, if used correctly. Studies on "live high, train low" protocols show that sleeping at simulated altitude for 4-6 weeks can increase red blood cell mass and improve performance at altitude. However, the tent needs to maintain consistent simulated elevation (typically 8,000-9,000 feet), and you need to spend at least 8-10 hours per night in it.
Q: I only have two days before the race. What should I do?¶
Arrive as late as possible. The worst time to race is 24-72 hours after arriving at altitude. If you land two days before, you are racing at the worst possible moment. Instead, fly in the morning before or the night before the race. You will still feel the reduced oxygen, but you avoid the acute adjustment period.
Q: Should I change my fueling strategy at altitude?¶
Yes. Increase calorie intake by 10-15% (emphasizing carbohydrates), hydrate more aggressively, and favor easily digestible foods. Your gut will be less reliable at altitude, so liquid calories often work better than solid foods.
Q: What about medications like Diamox (acetazolamide)?¶
Diamox is a prescription medication that can reduce acute mountain sickness symptoms. Some ultra runners use it when arriving at altitude with limited acclimatization time. However, it can cause tingling in extremities, increased urination, and altered taste. Talk to your doctor well before race week. Do not try it for the first time on race day.
Q: How does altitude affect sleep before the race?¶
Altitude commonly disrupts sleep, especially in the first 3-5 nights. You may experience frequent waking, lighter sleep, and periodic breathing (alternating deep and shallow breaths). This is normal. It improves over time. Consider arriving early enough that your sleep normalizes before race day, or arrive so late that you only have one disrupted night.
Key Takeaways¶
- Altitude reduces your pace, not your fitness. A 12-18% slowdown at 10,000 feet is normal physiology, not a sign you trained wrong.
- Arrival timing matters more than most runners realize. Either arrive 5+ days early or the night before. Avoid the 24-72 hour window.
- Race by effort, not pace. Heart rate, perceived exertion, and the talk test are your real guides at altitude.
- Fuel more, fuel earlier, fuel simpler. Your body burns more carbs and loses more fluid at altitude.
- Power hike the climbs. Every experienced mountain ultra runner does it. It is strategy, not weakness.
Start Running Smarter¶
Altitude racing rewards preparation over raw fitness. The runners who have great days above 8,000 feet are the ones who built a plan around altitude's realities instead of fighting them.
NavRun's AI-powered training plans and race-day pacing strategies are built from your actual Strava data, not generic calculators. Connect your account and see what your sea level fitness looks like when the air gets thin.
Free forever for core features.