How do you pace the marathon leg of an Ironman?

Why is the Ironman marathon slower than your open marathon?

The marathon leg of an Ironman starts after roughly 9 to 10 hours of racing for most amateurs — about 60 to 90 minutes of swimming plus 5 to 7 hours of cycling. By the time you hit T2, your muscle glycogen has been drawn down significantly (though not completely, if fueling was handled well), your liver glycogen is under stress, your core temperature is probably elevated, your hydration status is fragile, and your neuromuscular system has been cycling for hours in a posture and recruitment pattern very different from running. None of these conditions exist at the start of a standalone marathon.

The result is a predictable slowing. Almost every amateur Ironman athlete runs the marathon leg 10 to 20 percent slower than they would run a standalone marathon on the same day at the same effort. For a 3:30 open marathoner, the Ironman marathon typically comes in around 3:50 to 4:15. For a 4:00 open marathoner, it's usually 4:25 to 4:50. For a 4:30 open marathoner, it's often 5:00 to 5:30. These numbers assume the bike was well-paced; if the bike was overcooked, the marathon slowing can easily reach 30 percent or more.

The implication is that planning Ironman marathon pace as 'my open marathon pace minus a little' is a recipe for blowing up. The correct planning approach is to add 45 to 75 seconds per kilometer to your open marathon pace as the starting point for your Ironman marathon target, then adjust based on your 70.3 split, your experience, and the course conditions.

The rule of thumb that experienced Ironman coaches use is that Ironman marathon pace should feel 'easy' for the first 10 km. If it feels even moderately hard at 5 km, you are going too fast for the state of your body, and the second half of the marathon is going to be catastrophically slow regardless of what the watch says.

How do you calculate a realistic goal Ironman marathon pace?

The most reliable calculation uses two inputs: your recent open marathon time (or reasonably extrapolated half marathon time) and your 70.3 run split if you have one.

• From a standalone marathon time: add 45 seconds per km for well-paced well-trained athletes, 60 seconds per km for typical amateurs with good preparation, and 75 seconds per km or more for first-timers or athletes with less Ironman-specific training. For a 3:45 open marathoner (5:20/km), a first Ironman might target 6:35/km — a 4:38 Ironman marathon.
• From a 70.3 run split: double the 70.3 marathon pace and add 15 to 30 seconds per km. A 1:45 70.3 run split (about 5:00/km) suggests an Ironman marathon target around 5:15 to 5:30/km — a 3:42 to 3:52 marathon. This is usually a more accurate prediction than the open-marathon extrapolation for experienced long-course athletes, because the 70.3 run already captures some of the bike-induced fatigue pattern.
• From an FTP-based projection: not directly useful for marathon pace (FTP is a cycling metric), but can be used as a cross-check on whether the bike pacing plan is sustainable. If the bike IF plan would consume too much glycogen to support the projected marathon, the bike plan needs to come down.
• Adjustments for course and conditions: subtract 15 to 30 seconds per km for hilly courses, subtract 20 to 40 seconds per km for hot conditions (over 28°C / 82°F), and subtract 30 to 60 seconds per km for combined hilly-and-hot courses like Kona in a bad year. These adjustments compound; a hot hilly race can legitimately add 45 to 75 seconds per km to the realistic target.
• First-timer adjustment: first-time Ironman athletes should add another 15 to 30 seconds per km to any of the above numbers as a margin. The first Ironman experience is almost always harder than the data predicts, and a conservative target gives you the psychological room to execute well.

Why do controlled negative splits beat even pacing in an Ironman marathon?

In a standalone marathon, even pacing or a small positive split is the typical execution strategy for experienced runners — the energy cost of going out at pace is roughly equal to the cost of holding it, and the race is short enough that the back-end fatigue is manageable. The Ironman marathon is different. The cumulative fatigue from 9 to 10 hours of preceding racing means that every minute of 'running too fast early' costs much more than it would in a standalone marathon.

The evidence from power-file analysis and GPS splits across thousands of Ironman races consistently shows that athletes who ran a slight negative split (first half slower than second half) or an even split finished with materially better times than athletes who ran a positive split (first half faster than second half). The catch is that running a true even split in an Ironman marathon almost always requires starting slower than the target goal pace, not at it, because the accumulated fatigue will slow you progressively unless you deliberately hold back early.

The practical structure is: first 10 km deliberately slower than target (by 10 to 20 seconds per km), middle 20 km at target, final 12 km at target or slightly faster if the fueling and pacing allowed it. Most athletes will not actually run the final 12 km faster — they'll slow down anyway because of accumulated fatigue. But the deliberate slowness of the first 10 km is what keeps the slowing from becoming a collapse.

Why should you walk through every aid station?

Walking every aid station in an Ironman marathon is standard practice at all amateur levels and even among many professionals. It is not a sign of weakness or failure — it is a deliberate pacing and fueling strategy that almost universally produces faster overall marathon splits than running through stations.

The math is straightforward. A typical Ironman marathon has aid stations every 1 to 2 km, which means roughly 25 to 35 stations over 42.2 km. Walking a station for 15 to 20 seconds costs you about 6 to 12 minutes of cumulative walk-time across the whole marathon. But walking stations gives you three things: clean drinking (running and drinking at the same time produces reliable choking, spilling, and incomplete hydration), a brief heart rate dip that acts as a micro-recovery, and the ability to take gels or real food without gagging. In practice, athletes who walk stations consistently run faster splits between stations because they're better fueled and more recovered.

The rule that emerges from thousands of race files is: walking every station costs about 6 to 12 minutes of pure walking time across the marathon and saves about 15 to 40 minutes of avoidable blow-up in the back half. It is one of the cleanest positive trades in triathlon race execution, and first-time Ironman athletes should treat it as non-negotiable.

Walk into the station, grab fluid, walk while drinking, walk while taking a gel if needed, then resume running pace as you exit the station. The total walk is usually 15 to 30 meters per station. Do not slow-jog through stations — it combines the cost of running with the ineffectiveness of trying to drink while moving.

What is the run-walk strategy and when should you use it?

The run-walk strategy is associated with Jeff Galloway, a former Olympic-level distance runner who spent decades developing and validating structured walk breaks for marathon runners. The core idea is that inserting planned walk breaks into a running pace actually produces faster overall marathon times for many athletes than trying to run the whole distance, because the walk breaks reduce cumulative fatigue and maintain muscular freshness long enough to hold running pace through the second half.

In the Ironman context, the run-walk strategy has been adapted by long-course coaches for athletes who are unlikely to finish the full marathon in a continuous run. The typical protocol is 9 minutes running, 1 minute walking, repeated throughout the marathon. More conservative versions use 5:1 or even 4:1 ratios. The walk breaks are shorter than the aid-station walks (usually 30 to 60 seconds) and happen on a clock rather than at specific points on the course.

The run-walk strategy works especially well for three populations: first-time Ironman athletes whose marathon fitness is borderline, athletes with a history of back-half marathon collapses in previous races, and athletes racing in hot conditions where continuous running becomes cardiovascularly unsustainable regardless of leg fitness. For these athletes, a 9:1 or 5:1 run-walk protocol often produces a finish 20 to 60 minutes faster than attempting to run continuously.

The run-walk strategy does not work well for experienced, well-trained Ironman athletes who can run continuously at their target pace — for them, forced walk breaks interrupt rhythm and slow the overall split. It's a tool for a specific athlete profile, not a universal recommendation.

What is the Ironman shuffle and what does it mean?

The Ironman shuffle is the characteristic gait that many amateur Ironman athletes adopt in the second half of the marathon. The stride shortens from 1.2 to 1.4 meters to 0.8 to 1.0 meters. The cadence drops from 170 to 180 steps per minute to 150 to 160. The vertical oscillation collapses. The knees barely lift. The shoulders slump forward. The pace drops to 7:00 to 9:00 per km. And crucially, the athlete is still moving — just very, very inefficiently.

The shuffle is not a failure of run fitness. It is the physiological signature of severe cumulative fatigue combined with glycogen depletion, muscle damage from the bike, and neuromuscular exhaustion. An athlete in the shuffle state is essentially running on the last scraps of available energy, with the gait degrading to the minimum-cost shuffle that the body can still produce. It is the end state of a poorly-paced Ironman — the bike was too hard, the fueling was inadequate, or both.

When the shuffle appears, the correct response is usually to walk for 3 to 5 minutes, take in concentrated carbs (a gel plus water, or even a real food option like chicken broth at an aid station), and then attempt to resume a controlled run-walk rhythm. Trying to push harder through the shuffle rarely works — the limiter is fuel and neuromuscular state, not willpower. Walking, eating, and resetting the cadence produces faster overall finishing times than fighting through.

The more important lesson of the shuffle is preventative. Athletes who appear in the shuffle in mile 18 almost always made a pacing or fueling mistake in the preceding hours. The next race's plan should address that mistake — usually by riding the bike 10 to 15 watts easier, eating more consistently in the first half of the marathon, or both.

An experienced Ironman coach can usually watch an athlete run past at mile 20 of the marathon and diagnose their race to within 5 to 10 minutes of finish time by the shape of their gait. The shuffle is that diagnostic. It is the body's honest report that the plan went wrong several hours ago.

How do you tell the difference between a pacing problem and a fueling problem?

When an Ironman marathon starts going badly, the athlete usually cannot tell in the moment whether the issue is pacing, fueling, both, or something external like heat. But the shape of the collapse is diagnostic, and the right mid-race correction depends on identifying the right problem.

• A pacing problem looks like this: the legs feel heavy and dead from early in the marathon, the cadence drops quickly, and the heart rate stays high for the given pace or drops as the legs give out. The athlete feels muscularly exhausted more than metabolically empty. This is usually the signature of an overcooked bike — the muscular glycogen and neuromuscular state are depleted before the marathon even starts.
• A fueling problem looks like this: the legs feel fine through the first 15 to 20 km, then the athlete experiences a distinct 'bonk' — dizziness, cold sweats, inability to hold pace, strong hunger, mental fogginess. The pace drop is sudden rather than gradual. This is classic glycogen depletion from inadequate in-race fueling, and it responds to aggressive sugar intake in the next 15 to 20 minutes.
• A combined problem looks like the worst of both: early heaviness (pacing) plus sudden bonk later (fueling). These are the Ironman days where the athlete walks the last 15 km. The correction for next time is both — ease the bike by 10 watts and add 15 grams of carbs per hour across the whole race.
• A heat problem looks different: the pace drops but the athlete doesn't feel muscularly destroyed, they feel overheated and nauseous. The fix in-race is aggressive cooling (ice in the hat, cold water over the head at every aid station, walk breaks in shade where possible) and often a temporary pace reduction until the core temperature comes down. The mistake is assuming heat problems are fueling problems and eating more — excess fuel on an overheated gut causes its own distress.

The mid-race correction decision is not always clear, and the best strategy is usually conservative: walk an aid station, take in fluid and some sugar, cool the body if it's hot, and resume at a deliberately slower pace. These three actions address most of the common failure modes simultaneously, and they're rarely the wrong move.

What are the five most common Ironman marathon pacing mistakes?

Five mistakes catch most amateur Ironman athletes.

• Running the first 5 km too fast because the legs feel fresh. The most common mistake in Ironman marathon pacing. The first 5 km should feel suspiciously easy and be 15 to 30 seconds per km slower than target pace. Athletes who hit target pace at 5 km are almost certainly going too fast for the state of their body.
• Refusing to walk aid stations. Many first-time Ironman athletes try to run through aid stations because 'walking feels like failing'. It isn't — walking aid stations is a standard execution technique that loses a few minutes of pure walk time and saves 15 to 40 minutes of back-half collapse. The athletes who finish their first Ironman well almost universally walk aid stations.
• Chasing the watch at the expense of the body. GPS pace is noisy, inaccurate in built-up sections, and often 10 to 20 seconds per km off the athlete's real pace. Chasing a specific GPS number through cramping, heat, or fatigue creates a feedback loop where the athlete pushes harder on degraded data and accelerates the collapse. The right approach is to feel the effort and accept that the watch pace will fluctuate.
• Not adjusting for heat or weather. A hot Ironman marathon requires a 20 to 40 seconds per km target adjustment and aggressive cooling at every aid station. Athletes who treat a 32°C Ironman the same as a 20°C Ironman consistently blow up in the second half regardless of their fitness.
• Blaming the run when the bike was the real problem. The most common misdiagnosis in Ironman. The run feels terrible because the bike was too hard, not because the run was mispaced. Ironman athletes who want a better marathon next year should almost always look to the bike power file first, not to their running training.