You Bonked at Mile 22 Despite a Fueling Plan — Here's What Went Wrong

In Summary

A fueling plan on paper isn't a fueling plan that works — execution gaps are where most marathoners fail.
Starting fueling late by even 15 minutes creates a glycogen debt you can't repay mid-race.
Your plan needs to match YOUR pace, weight, and conditions — not a generic guide's assumptions.
Sweatr builds a fueling plan from your actual wearable data so the numbers fit your body, not someone else's.

You did everything right. You had a gel schedule written on your arm. You carried your own bottles. You practised in training. And then somewhere between mile 20 and mile 22, your legs turned to concrete, your brain went foggy, and you watched your goal time disappear.

The wall hit you anyway.

Here's the thing: having a fueling plan and having the right fueling plan are two different things. Most marathoners who bonk aren't under-prepared — they're mis-prepared. The plan looked reasonable on paper, but it had a flaw they couldn't see until it was too late.

Let's diagnose the five most common reasons a fueling plan fails on race day — so you never have to feel that particular brand of defeat again.

1. You Started Fueling Too Late

This is the single most common mistake. You felt fine at mile 5, so you skipped the first gel. By the time you felt the first dip at mile 12, you were already behind — and glycogen debt compounds.

Your muscles burn through glycogen at a roughly constant rate from the gun. If you delay your first intake by 20 minutes, you're not 20 minutes behind — you're creating a deficit that takes progressively more carbohydrate to close. By mile 18, the hole is too deep.

The fix: Take your first fuel at 20–25 minutes, not when you feel tired. Fueling is prevention, not treatment. If you wait until you feel like you need it, you needed it 15 minutes ago.

2. Your Carb Target Was Too Low for Your Finishing Time

Most fueling guides target 60 grams of carbohydrate per hour. That's a solid number for a 3:00–3:30 marathoner. But if you're finishing in 4:15 or 4:45, the maths changes in two ways:

You're out there longer, so total carbohydrate demand is higher
Your glycogen depletion rate is slightly lower per hour but the total duration means you deplete further overall

A 4:30 marathoner needs approximately 240–270g of total race carbohydrate. At 60g/hr, you'd need to fuel for 4+ hours flawlessly. Many runners plan for 3 hours of fueling and assume the last hour will just... work out. It won't.

The fix: Calculate your total carb need based on your realistic finishing time, not your goal time. Then map backwards: total grams divided by hours on course equals your hourly target. Add a 10% buffer for the final quarter.

3. You Didn't Account for Conditions

Your plan worked on a 10°C training run. Race day was 18°C with humidity. That single variable changes everything:

Sweat rate increases 20–40% in warm conditions
Blood is redirected to the skin for cooling, away from the gut
Gut absorption efficiency drops — the same gel hits harder on your stomach
Perceived effort rises, which makes eating feel worse

A plan calibrated for cool conditions will over-fuel your gut and under-fuel your fluid needs in the heat. The result: nausea, skipped gels, glycogen crash.

The fix: Have a warm-weather variant of your plan. In temperatures above 15°C, shift 10–15% of your carbs from gels to liquid carbohydrate (sports drink), reduce gel frequency slightly, and increase fluid intake by 150–200ml per hour. Your total carb target stays the same — the delivery method changes.

4. Your Gut Wasn't Trained for Your Plan's Demands

You can write "90g carbs per hour" on a spreadsheet. Whether your gut can actually absorb 90g per hour on tired legs at race pace is a completely different question.

Gut training is a physiological adaptation. The transporters in your intestinal wall (SGLT1 for glucose, GLUT5 for fructose) upregulate with repeated exposure. If your longest training run had you taking 45g/hr and race day asked for 75g/hr, your gut wasn't ready for the jump.

The result: nausea, bloating, or outright rejection of fuel from mile 15 onwards. You skip one gel because you feel sick, then another, and by mile 20 the calorie deficit catches you.

The fix: Your race-day carb target should never exceed what you've successfully practised on at least three long runs. Increase your training intake by 10–15g per week over an 8-week build. If your gut can handle 60g/hr reliably in training, that's your race ceiling — not 90g/hr because a guide said so.

5. You Fueled by Time but Ran by Feel

Many plans say "take a gel every 30 minutes." But if you went out 15 seconds per mile faster than planned — common in the excitement of race day — your per-mile energy cost increased and your glycogen depletion accelerated. The clock-based schedule didn't account for the effort increase.

Meanwhile, your total time on course might be shorter, meaning fewer fueling windows. The mismatch: higher burn rate plus fewer gels equals a net shortfall by mile 20.

The fix: Anchor your fueling to both time and effort. If you're running harder than planned, pull your next gel forward by 5 minutes. Your body doesn't care what the clock says — it cares about work rate. Heart rate data from your watch can tell you when you've drifted above plan.

The Common Thread: Your Plan Wasn't Personal Enough

Every one of these failures has the same root cause: the plan was based on generic assumptions rather than your actual data. Your weight, your sweat rate, your gut tolerance, your finishing pace, the day's conditions — these are all individual variables that change the numbers.

A fueling plan that works is one built from your data:

Your body weight determines baseline carb needs per hour
Your sweat rate (which varies with fitness and heat) determines fluid and sodium targets
Your trained gut capacity sets the upper limit on what you can absorb
Your actual pace on the day — tracked in real time by your watch — tells you when to adjust

This is exactly what Sweatr does. It pulls your training data from your Apple Watch, Garmin, or Strava, calculates your individual carbohydrate and fluid needs, and builds a race-day plan calibrated to your body — not a generic table. If conditions change, the plan adapts. If your pace drifts, the targets update.

The Post-Race Audit: 4 Questions to Ask Yourself

If you've already bonked, use these questions to diagnose what went wrong:

When did I take my first fuel? If it was after 30 minutes, timing was likely a factor.
What was my total carb intake vs. my total carb need? Calculate: finishing time (hours) × target g/hr = what you needed. Then count what you actually took.
Were conditions warmer than my training runs? If yes, fluid competition likely reduced gut efficiency.
Had I ever taken this much fuel at this intensity in training? If no, your gut wasn't prepared.

Most runners find the answer is a combination of two or three of these — rarely just one.

Build a Plan That Matches Your Body

The difference between a plan that works and one that falls apart at mile 22 isn't willpower or toughness. It's precision. Your fueling needs are as individual as your VO2 max — and they deserve the same data-driven approach.

Sweatr calculates your personal carbohydrate ceiling, adjusts for conditions, and gives you a gel-by-gel schedule built from your wearable data. No guessing, no generic tables, no finding out your plan was wrong at mile 22.

Download Sweatr and build your race-day plan from your actual data — so your next marathon ends with a finish line photo, not a bonk story.