The 90km bike leg of an IRONMAN 70.3 accounts for roughly half of your total race time. It's also where the most time is gained or lost — not by who rides fastest, but by who rides smartest.
Our analysis of 840,000+ triathlon race results reveals a consistent pattern: athletes who ride above 78% of their Functional Threshold Power (FTP) for the 70.3 bike leg lose 8-12 minutes on the run compared to athletes with similar fitness who ride at 70-75% FTP. The fast bike riders are slower overall because the run collapse wipes out their bike advantage and then some.
This guide covers exactly how to pace the 70.3 bike based on your fitness level, your course, and race-day conditions.
The Optimal Power Range for a 70.3 Bike
The evidence points to a clear range: 68-76% of FTP produces the best overall 70.3 times for the vast majority of age-group athletes.
Here's why. At 68-76% FTP, you're riding primarily in your aerobic system. Fat oxidation is contributing meaningfully to energy production, sparing glycogen for the run. Lactate accumulation is minimal — your body is clearing it as fast as it's produced. Your core body temperature rises slowly, keeping thermoregulation manageable.
Above 78% FTP, the equation shifts. Glycogen burn rate increases sharply. Lactate begins accumulating. Your body diverts more blood to cooling. And critically, your gut's ability to absorb nutrition decreases, which means the fuel you're taking in isn't reaching your muscles efficiently.
By athlete level:
| Level | FTP % Target | Example (250W FTP) | Rationale |
|---|---|---|---|
| Beginner (first 70.3) | 65-70% | 162-175W | Protect the run. A comfortable bike ensures you can actually run 21km. |
| Intermediate (sub-6:00) | 70-75% | 175-188W | You have the fitness for moderate intensity. Discipline is the limiter, not watts. |
| Advanced (sub-5:00) | 73-78% | 183-195W | Higher end is achievable with strong run-off-bike history and dialed nutrition. |
| Elite (sub-4:15) | 78-82% | 195-205W | Only for athletes who have demonstrated they can run well off high-intensity bikes in training. |
If you're unsure, go lower. It is always better to arrive at T2 with energy to spare than to arrive depleted. A "too easy" bike followed by a strong run produces a faster total time than a hard bike followed by a walk-run.
How to Pace by Course Profile
A flat 70.3 and a hilly 70.3 require the same average effort but very different execution.
Flat courses (e.g., 70.3 Dubai, Bahrain): Steady-state pacing works well. Hold your target power with minimal variation. Focus on aerodynamics — your position matters more than watts on flat courses. A 5% improvement in CdA (drag coefficient) at 35km/h is worth roughly 1km/h, which translates to 3-4 minutes over 90km.
Rolling courses (e.g., 70.3 Boulder, Marbella): Aim for a Variability Index (VI) below 1.05. That means your Normalized Power should be no more than 5% above your Average Power. Practical execution: push 5-10% above target on short climbs (under 3 minutes), return to target power on the flats, and reduce to 50-60% FTP on descents. Don't chase speed downhill — gravity is doing the work.
Hilly courses (e.g., 70.3 Zell am See, Chattanooga): The climbs are where you lose or save your run. The temptation is to push hard uphill because you feel strong. Resist. Limit your climbing power to no more than 110% of your flat target. For a 180W target, don't exceed 200W on any climb. Standing for 15-20 seconds every 5-10 minutes helps distribute the load between muscle groups.
The descent trap. Many athletes "recover" on descents by coasting. This seems smart but creates big power spikes followed by near-zero power, which is metabolically inefficient. Instead, maintain 50-60% FTP on descents — enough to keep blood flowing and muscles engaged, not enough to add meaningful fatigue.
Heart Rate as a Backup Metric
If you don't have a power meter, heart rate is your best alternative. Target Zone 2 to low Zone 3 for the bike leg — roughly 70-80% of your maximum heart rate.
However, heart rate has limitations for pacing:
- Cardiac drift: Over a 2.5-3 hour bike, your heart rate naturally rises even at constant power. A steady 155bpm at hour 1 becomes 165bpm at hour 2 at the same wattage. If you pace by heart rate alone, you'll slow down unnecessarily as the ride progresses.
- Heat effect: Hot conditions elevate heart rate by 5-15 beats per minute independent of effort. On a 32°C day, your "Zone 2" heart rate may actually correspond to below-target power.
- Adrenaline spike: Race-day excitement raises your heart rate for the first 20-30 minutes regardless of effort.
The practical solution: use heart rate as a ceiling, not a target. If your HR exceeds 82% of max on the bike, you're likely above your target power range and should ease off.
Nutrition Integration with Pacing
Your pacing and nutrition strategies are interdependent. At higher intensities, your gut's ability to absorb fuel decreases. If you're riding at 80% FTP, you may only absorb 40-50g of carbs per hour instead of the 60-80g you need.
This creates a doom loop: ride too hard → can't eat → glycogen depletes faster → run collapses.
The fix is to pace conservatively enough that eating is comfortable. If you find yourself unable to eat at your current intensity, you're riding too hard. Drop 5-10 watts and try again.
Set a timer on your bike computer for every 20 minutes. At each alarm: take a sip of fluid and a bite of food. This removes the decision and turns nutrition into a mechanical habit.
Read the full nutrition plan: 70.3 Nutrition Timeline →
Adjustments for Race-Day Conditions
Heat (>25°C / 77°F): Reduce target power by 3-5% per 5°C above your typical training temperature. If you trained through winter at 15°C and race day is 30°C, that's a 5-8% reduction. Accept the slower time.
Headwind: Drop target power by 5%. Fighting wind at full power produces disproportionately small speed gains because aerodynamic drag scales with the cube of velocity. Ride at target watts and accept the slower speed.
Rain: Pacing doesn't change, but execution does. Wider lines on corners, more braking distance, and careful handling. The mechanical risk of crashing vastly outweighs the 30-second time savings from aggressive cornering.
Altitude (>1,500m): Reduce all targets by 5-8%. Oxygen delivery is compromised, and your body produces lactate at lower power outputs. Add another 3-5% if you haven't acclimated for at least 10 days.
The Mental Game: Staying Disciplined
The hardest part of 70.3 bike pacing isn't physical — it's mental. You'll feel great at km 20. Other athletes will pass you. You'll think "I can push harder." Don't.
The athletes passing you at km 20 will often be the ones you pass at km 16 of the run. Every watt you save on the bike is a second you gain on the run.
One useful mental technique: think of the bike as a 90km warm-up for a 21km race. The run is where the race happens. Your job on the bike is to arrive at T2 ready to run.
Build Your Bike Pacing Plan
Want power targets specific to your FTP, your course profile, and your race-day weather? RaceDayAI generates segment-by-segment pacing for your exact race.
Build Your Free Bike Pacing Plan →
← Back to The Complete 70.3 Race Execution Guide
Last updated: March 2026