Watercolor view of the empty Queen K highway crossing Kona lava toward the ocean

Kona Cutoff Times and Age-Group Pacing Math

Turn one finish clock into discipline budgets, effort ceilings, and decision rules that still work when heat and fatigue change the speed.

The short answer
  • Every cutoff is cumulative.Swim, transitions, bike, run, and stopped time all spend the same 17-hour budget; intermediate gates can close earlier.
  • Power should be scaled to expected duration.A longer bike split demands a lower IF, while a VI near 1.00–1.05 limits the hidden cost of surging into wind and over rollers.
  • Buffer comes from durability, not borrowed time.A patient bike and pre-planned run-walk can protect more finish margin than an early push that turns the Energy Lab into a walk.

Kona cutoff times are not three independent deadlines. They are one running ledger. The useful calculation starts with your own swim and transitions, subtracts them from the cumulative gates, then asks what bike power and marathon strategy can preserve that schedule without spending the legs needed to finish it.

Swim2:20from your start
Bike10:30cumulative
Finish17:00total elapsed
Principle 01 · One energy budget

Why does conservative early pacing beat banking time?

Time gained above sustainable intensity is small and fragile; fatigue, carbohydrate demand, and thermal load rise faster than speed. The best early pace is the one that leaves the planned bike power and run gait available later.

Kona makes early effort feel cheaper than it is. The swim carries race-day adrenaline, town crowds reward acceleration, and bike airflow masks heat. Yet every surge increases oxygen demand and heat production while the athlete is still many hours from Aliʻi Drive. The clock shows the seconds gained immediately; it does not show the reduced cooling, fueling, and muscular reserve that must pay for them.

A 2022 professional Kona pacing analysis found relatively consistent bike pacing across the leading groups, while larger speed decline distinguished lower-placed men on the run. A separateobservational study of Kona athletes linked relative success to better speed preservation on downhill segments and smaller heart-rate changes around the Hawi climb and descent. Neither study proves one universal split; both support regulating the whole day instead of winning an isolated section.

CSSSwim below the pace that creates accumulating strain
IF + VISet bike intensity, then control how smoothly it is delivered
HR + GAPCap run effort while grade, heat, and speed change
Framework 02 · Bike intensity and variability

What IF and power distribution fit each age-group tier?

The longer the expected bike split, the lower the sustainable IF should be. Start with a duration-matched band, keep VI near 1.00–1.05, then lower the ceiling when heat, heart rate, or durability testing says the model is too ambitious.

Intensity FactorIF = Normalized Power ÷ FTP
Variability IndexVI = Normalized Power ÷ Average Power
Planning tierExpected dayStarting IF bandExecution priority
Professional / eliteUnder ~9 hours0.75–0.82High output over shorter exposure
Competitive age-groupAbout 9–11 hours0.68–0.73Protect a continuous marathon
Mid-pack age-groupAbout 11–13 hours0.60–0.67Hold aerobic metabolism and aero form
Back-of-pack / seniorAbout 14–17 hours0.52–0.60Preserve forward progress for the run

Planning bands synthesized from the source report and coaching practice, not validated prescriptions for every athlete. FTP accuracy, duration, heat, wind, body size, fueling, and training history change the result.

Watercolor aerial of the Queen K contrasting one smooth pacing line with a broken surging rhythm
One line keeps its rhythm; the other spends itself in spikes. Ground speed can move with wind and grade while physiological cost stays controlled.

VI exposes expensive smooth-looking averages. A ride averaging 170 W can still carry a much higher Normalized Power if it was built from repeated spikes and coasting. Palani and Hawi are where discipline matters: choose gearing that keeps cadence available, cap short climbs, and let the speed fall into a headwind. A practical ceiling is often well below threshold; the exact percentage must be rehearsed rather than invented on race day.

Calculation 03 · The five-point IF error

Can riding 0.75 instead of 0.70 really ruin the run?

It can change the day substantially, but no honest equation guarantees a fixed 20–30% pace collapse. The certain math is a 7.1% rise in Normalized Power; the run cost depends on duration, heat, fueling, durability, and the athlete.

FTP280 W
0.70 IF196 W NP
0.75 IF210 W NP
Change+14 W · +7.1%

Those 14 watts look small because speed does not rise in direct proportion to power, especially against aerodynamic drag. Physiological cost also does not rise in a simple straight line. Moving closer to aerobic threshold can increase carbohydrate use, core-temperature production, and motor-unit recruitment while reducing the athlete's ability to absorb food and cool. The time saved on the bike therefore cannot be calculated from IF alone, and the time lost on the run cannot be guaranteed from a generic glycogen model.

The power equation can prove that the bike effort changed. Only race-like training can show whether your marathon survives the change.

Treat the higher target as a hypothesis. Compare matched long bricks in similar conditions: total ride time, VI, heart-rate drift, carbohydrate tolerance, cooling, postural comfort, and 45–60 minutes of controlled running. A faster bike that produces a slower or unstable brick has failed the whole-race test.

Execution 04 · Marathon heart rate and run-walk

How should you pace the marathon as heart rate drifts?

Cap effort at or below the tested aerobic threshold and allow pace to slow as thermal strain rises. Use GAP to interpret hills and a rehearsed run-walk structure to prevent aid-station walking from becoming open-ended.

On Aliʻi Drive, cool-course marathon pace can feel available. That pace is not the relevant target after a 112-mile bike. As skin blood flow rises and plasma volume falls, heart rate increases at the same mechanical output. Forcing the original pace turns ordinary cardiovascular drift into an intensity escalation. The response is to hold the physiological ceiling, not to negotiate with the watch.

SignalWhat it tells youRace response
HR rises, GAP stableThermal or cardiovascular drift is growingReduce pace before crossing the cap
Actual pace slows uphillGrade changed, not necessarily effortUse GAP, breathing, and HR; walk steep Palani
HR falls with rising RPEFatigue, fueling, or cooling may be limiting outputAssess symptoms and aid-station plan; do not force pace
Run breaks expandThe schedule has lost boundariesReturn to a timed ratio or landmark-based restart

Run-walk works best when it begins as strategy rather than rescue. Walking each aid station or using 4 minutes running and 1 minute walking can create regular cooling, drinking, and form-reset windows. The running portion must remain truly aerobic, and every walk needs a defined end. Athletes near the cutoff should model the average pace of the complete cycle, not quote only the faster running minutes.

Calculation 05 · Cumulative cutoff ledger

What pace does each Kona cutoff actually require?

A historical Kona schedule used 2:20 for the swim, 10:30 cumulative for the bike, and 17:00 total. Your required bike speed and run pace depend on the time already spent, including transitions and stops.

Swim · 2:203:38 / 100 m

140 minutes ÷ 38.62 hundred-meter units

Bike · 10:30 cumulative14.15 mph

112 miles ÷ 7:55 after a 2:20 swim + 0:15 T1

Finish · 17:00 cumulative14:19 / mile

26.2 miles in 6:15 after reaching T2 at 10:30 + 0:15 T2

These are zero-buffer edge calculations, not targets. The swim conversion uses 2.4 miles, approximately 3,862 meters; an athlete who swims farther through imperfect sighting needs a faster watch pace. The bike example correctly leaves 475 minutes after a 140-minute swim and 15-minute T1: 112 ÷ 7.9167 = 14.15 mph, or about 22.77 km/h. The run example leaves 375 minutes after the 10:30 bike gate and a 15-minute T2: 375 ÷ 26.2 = 14:19 per mile, or roughly 8:53 per kilometer.

Build your own ledger
  1. Bike minutes available = bike gate − actual swim − actual T1.
  2. Required bike speed = 112 miles ÷ bike hours available.
  3. Run minutes available = 17:00 − actual T2 exit time.
  4. Required total run pace = run minutes available ÷ 26.2 miles.
  5. Usable buffer = gate time − planned arrival, after realistic stops.

Historical 2019 Kona course guidance also listed fixed intermediate bike gates at Hawi, Kawaihae, and Kaupulehu, plus run gates at Palani and the Energy Lab exit. Those clock times depended on that edition's wave schedule. A mathematically legal 17-hour projection can still fail if it misses a current intermediate gate.

Framework 06 · Whole-day pacing profiles

How do realistic splits change across finisher tiers?

Faster athletes can hold higher relative bike intensity because exposure is shorter. As finish time lengthens, the plan shifts from maximizing speed to minimizing stoppage, surging, muscle damage, and late-race pace decay.

ProfileSwimBikeRunTransitionsBike IF
Sub-9 elite0:50–0:554:30–4:452:50–3:15~0:050.75–0.82
Sub-11 competitive AG1:05–1:155:30–5:503:45–4:15~0:100.68–0.73
Sub-13 age-group1:15–1:256:15–6:454:30–5:00~0:150.60–0.67
Sub-16 senior / BOP1:40–1:557:15–7:455:45–6:15~0:240.52–0.60
Inada 20181:51:258:02:406:28:170:31:27Not published

Ranges are planning profiles, not qualifying standards or predictions. Inada's row reports a documented historical performance; weather, rules, course details, and athlete capability differ by year.

Blue-hour watercolor of an empty Aliʻi Drive with footprints continuing toward warm finish lights
Near the cutoff, the useful unit is not one fast mile. It is uninterrupted forward progress through every remaining pool of light.
A seven-minute margin16:53:49 at age 85

Hiromu Inada's 2018 finish combined a 1:51:25 swim, 12:08 T1, 8:02:40 bike, 19:19 T2, and 6:28:17 marathon. The lesson is not that every athlete can copy those paces. It is that a cutoff finish is built from continuous forward progress and honest accounting for transitions.

Guinness World Records documents Inada's age and 16:53:49 finish, while apublished case study of his performance examines the training and pacing behind it. With only 6:11 remaining, the day also shows why a cutoff survivor cannot depend on a large rescue effort after a long stop or an overpaced bike.

Execution 07 · Masters and 15–17 hour racing

What changes when the race lasts fifteen to seventeen hours?

Small inefficiencies compound: low-cadence torque, open-ended stops, forgotten fueling, and repeated pace decisions become larger threats than one missing peak-fitness metric. The plan must reduce physical and cognitive variability.

A long day asks the athlete to make hundreds of decisions while heat, darkness, discomfort, and fatigue raise perceived effort. Cognitive offloading is therefore part of pacing. Divide the course into landmarks, attach one task to each segment, and write triggers in advance: maximum climb power, minimum comfortable cadence, when to leave aero, when to walk, what to do at each aid station, and how long any stop may last.

ClimbsCap power; shift before cadence collapses.
Aid stationsCool, fuel, assess, and restart on a fixed cue.
Run-walkBegin by schedule, not by breakdown.
AttentionSolve the next landmark, not the remaining race.

Cadence should stay individual. Excessively low cadence raises pedal force and local muscular load; excessively high cadence can raise cardiovascular cost. For many older long-course athletes, a rehearsed middle range near 80–85 rpm and easier gearing protects both sides of that trade-off. The number is useful only if it can be sustained in aero, into wind, after feeding, and late in a long ride without knee pain or power spikes.

The complete pacing plan

How does the math become a course-specific race plan?

Start with current gates, subtract honest transitions and stops, then pair each remaining pace with an intensity ceiling and a fallback rule. A schedule is credible only after it survives race-like heat, wind, and brick training.

Use the Kona course overview to place each decision geographically, the segment-by-segment guide to train the terrain, and the heat-acclimation guide to prepare for the heart-rate drift that forces speed away from cool-condition predictions.

Personal preparation

Build the clock around your tested pace.

Recent swim pace, FTP, long-ride durability, transitions, heat response, run-walk execution, and current race rules determine the useful schedule.

Plan my Kona pacing

Kona cutoff and pacing questions

What are the Kona swim, bike, and finish cutoff times?

A commonly published Kona schedule allows 2:20 for the swim, 10:30 cumulative to finish the bike, and 17:00 total to finish. Intermediate course gates and transition closures also apply, and rules can change by edition. Verify every time and location in the current athlete guide rather than planning from historical values alone.

What swim pace reaches a 2:20 Kona cutoff?

Across 2.4 miles, or about 3,862 meters, 140 minutes averages approximately 3:38 per 100 meters or 3:19 per 100 yards. That is a zero-buffer calculation. Current, sighting, contact, and the distance actually swum can all make the watch pace slower than a pool conversion predicts.

What bike speed is needed to reach T2 by 10:30?

It depends on the actual swim and T1. If the swim takes the full 2:20 and T1 takes 15 minutes, 7:55 remains for 112 miles, requiring about 14.15 mph or 22.77 km/h before stops. A faster swim creates more bike time; missed intermediate gates can still end the race before T2.

What Intensity Factor should an age-group athlete ride at Kona?

Useful planning bands are roughly 0.68–0.73 for a competitive age-grouper, 0.60–0.67 for an 11–13 hour athlete, and 0.52–0.60 for a 14–17 hour or senior athlete. These are starting ranges, not prescriptions. Heat durability, FTP accuracy, bike duration, fueling, medical context, and training evidence decide the individual cap.

What Variability Index should I target on the Kona bike course?

Aim to keep VI, calculated as Normalized Power divided by Average Power, near 1.00 and generally below 1.05. Wind, safe descending, traffic, and short climbs prevent perfectly flat power. The purpose is to limit avoidable surges, not to chase a tidy file at the expense of control.

Should I bank time early to protect against the Kona cutoff?

No. Build buffer by improving sustainable speed and reducing preventable stop time in training, not by racing the opening hours above your metabolic ceiling. An early surge can save minutes while causing a much larger slowdown once heat, glycogen demand, and muscular fatigue converge on the run.

Is run-walk pacing too slow for the Kona marathon?

A rehearsed run-walk plan can be faster than unplanned walking after an aggressive start. Walking aid stations or using a fixed ratio such as 4:1 lowers peak effort, creates cooling and fueling windows, and preserves mechanics. It only works if the running portions remain controlled and stops do not expand.

How should masters athletes pace Kona differently?

Masters athletes usually benefit from lower climb-power caps, gearing that protects cadence, earlier scheduled walk breaks, and more decision rules written before fatigue. Monitor heart rate, RPE, coordination, cooling, and forward progress together; age alone does not set the pace, but a 15–17 hour day leaves little room for repeated surges or long stops.

IRONMAN® is a registered trademark of World Triathlon Corporation. Pallie is independent and is not affiliated with or endorsed by World Triathlon Corporation or the race organizer. Historical cutoff examples are not a substitute for the current athlete guide; verify every rule and gate for your race edition.