How to Train for Your First 50K: A Coach's 16-Week Framework

The 50K is the friendliest door into ultrarunning. It is close enough to a marathon that your existing fitness transfers, and far enough past it that the race asks a genuinely different question - can you keep moving well when the terrain, the fueling, and the clock all stop cooperating at the same time.

I coach a lot of first 50Ks. The runners who finish well almost never have the biggest engine in the field. They have the most boring training log.

Before week one: the base that makes the plan work

A 16-week plan assumes a starting point. Mine assumes this:

• 40-50 km (25-31 miles) per week, held consistently for at least four weeks
• A comfortable 90-minute long run, on any surface
• Four running days per week you can hit without negotiating with yourself
• No unresolved injury - a niggle you are "managing" will not survive a 50K build

If that is not you yet, do not start the 16 weeks. Spend 8-12 weeks building to it instead, adding no more than 10% to your weekly volume at a time and taking every fourth week easy. This is not a delay. Base is the part of ultra training that actually produces the aerobic adaptations, and a rushed base is the reason most first-ultra builds end in the physio's office in week eleven.

The people who get hurt in ultra training are almost never the ones who trained too slowly. They are the ones who arrived at week one already behind, and spent sixteen weeks catching up.

The shape of the 16 weeks

Four blocks, four weeks each. Three weeks building, one week recovering, every time.

Weekly volume moves roughly like this: 50 km in block 1, 60-65 km in block 2, 70-80 km in block 3, back down through block 4. Those numbers are a shape, not a prescription. If your race has 2,500 m of climbing, the hours matter far more than the kilometres, and you should be reading the next section instead.

Train by time, not distance

This is the single biggest mental shift from road to trail.

A 25 km road long run takes most runners a little over two hours. A 25 km mountain long run with 1,500 m of gain takes the same runner four hours or more, and costs considerably more. If you plan by distance, you will accidentally double the training load the first time you take a plan into real terrain.

So: plan long runs in hours. For a 50K, the long run progression I use looks like this.

Note what is missing: a 50 km training run. You do not need one. The longest run in a 50K build should land somewhere around 4:30-5:00, which for most first-timers is 28-35 km depending on terrain. The last 15 km of your race is bought with the accumulated fatigue of the whole block, not with one heroic Sunday.

Vertical gain is a separate budget

Track weekly elevation gain as its own number, alongside volume. It responds to training the way mileage does, and it is the thing road runners most consistently under-train.

Work out the race's total gain, then build toward 1.5 times that figure in your biggest week. For a 50K with 2,000 m of climbing, that means peaking around 3,000 m in week eleven. Get there gradually - adding more than about 15% of vertical per week is how you find out your calves have opinions.

Two sessions per week carry most of that load:

• A climb-focused midweek run. 45-75 minutes with 400-800 m of gain, climbed at an easy, sustainable effort. Power hiking counts, and above roughly 15% gradient it should be the default - hiking a steep grade is usually faster and always cheaper than running it.
• The long run, which naturally accumulates gain if you choose the route honestly.

If you live somewhere flat, treadmill incline work and repeats on the longest hill you have both work. They are not identical to a real mountain, but the cardiovascular and muscular adaptations transfer well. What does not transfer is descending, and that is the harder problem.

Do not skip the downhills

Every first-ultra runner worries about the climbs. Almost all of them are wrecked by the descents.

Downhill running is eccentric loading - your quadriceps lengthen under tension, over and over, for hours. It causes real muscle damage, it is the main driver of that stiff-legged shuffle in the last 10 km, and it has an unusually long adaptation window. The good news is it adapts fast once you start, and the protection lasts for weeks.

From block 2 onward, include deliberate descending every week. Start with 15-20 minutes of cumulative downhill at a controlled effort, and build to 45-60 minutes in your biggest weeks. Take short steps, land under your hips, let your cadence rise, and stop braking with your heels.

Intensity: 80% easy, and mean it

Across the week, roughly 80% of your running time should be at an effort where you could hold a conversation, and about 20% should be genuinely hard. The failure mode is not too much hard work - it is the enormous grey middle, where every run is moderately uncomfortable and nothing gets a real adaptation.

For a 50K build, the 20% does not need to be sophisticated:

• Weeks 1-8: one session of 6-10 x 2 minutes uphill at hard-but-repeatable effort, jog down to recover.
• Weeks 9-13: one session of 3-4 x 8-10 minutes at threshold effort, ideally on a runnable climb or rolling terrain.

That is it. Ultra performance is overwhelmingly an aerobic and durability problem. Speedwork earns its place by keeping you efficient, not by being the centrepiece.

A caution on heart rate: on climbs, heart rate lags the effort badly and drifts upward through a long run regardless of what you are doing. Use it as a ceiling, not a target, and let perceived effort and breathing lead.

Strength: two sessions, thirty minutes, non-negotiable

Two short sessions a week, all block long. Heavy-ish, low reps, full recovery between sets - this is not a circuit class. Split squats, step-ups, deadlifts or hip hinges, calf raises (both straight and bent knee), and something for the trunk that involves resisting rotation rather than crunching.

The research here is unusually consistent: adding maximal-strength and plyometric work to endurance training improves running economy, and the 2025 work on economy durability suggests the benefit is largest exactly where ultra runners need it - late in a long effort, when you are already tired. Thirty minutes twice a week is a very good return.

Fueling is a trained skill, not a race-day decision

From week five, every long run over 2:30 is a fueling rehearsal. Same products, same timing, same bottles you plan to race with.

Start at 45-60 g of carbohydrate per hour and work upward across the block toward 60-90 g/h. Your gut adapts to this the way your legs adapt to hills - by being asked, repeatedly. Runners who arrive at a 50K having only ever taken a gel or two on their long runs are running an experiment on race day, and it usually fails somewhere around hour four.

Fluid: roughly 400-600 ml per hour in moderate conditions, more in heat, with sodium in it rather than plain water. There is a fuller treatment of the numbers in the fueling guides, but the training principle is simple - if you have not practised it, it is not your plan.

Back-to-back long runs, used sparingly

Two long runs on consecutive days teach your body to work on tired legs, which is the actual skill of an ultra. They are also a reliable way to get injured if you take them too far.

For a first 50K, three or four back-to-back weekends across the whole build is plenty. Keep the second day at 40-50% of the first day's duration and run it easy - 3:00 Saturday, 1:15-1:30 Sunday. The purpose is fatigue exposure, not more volume.

The taper

Three weeks out, your fitness is set. What remains is arriving fresh.

• Week 14: volume down about 20%, keep one short intensity session, long run 2:30.
• Week 15: volume down about 40%, long run 1:45, one brief session of 4-5 x 2 minutes at race effort to stay sharp.
• Week 16: volume down 60%, nothing over 45 minutes after Wednesday, complete rest two days before.

You will feel flat, then twitchy, then convinced you have lost fitness. All three are normal and none of them are information.

What goes wrong, in order of frequency

1. Starting the plan without the base. Sixteen weeks cannot manufacture an aerobic system. Build the base first.
2. Planning by distance in the mountains. Time is the honest unit.
3. Never descending on purpose. Then wondering why the last hour hurt.
4. The grey middle. Every run at 75% effort produces a tired runner with no adaptations.
5. Untrained gut. Practice fueling from week five, every single long run.
6. Skipping recovery weeks because you feel good. Feeling good in week seven of a build is precisely when the recovery week is doing its job.
7. New shoes, new pack, new anything on race day. Everything should have at least 100 km on it.

A realistic week in block 3

For a runner peaking around 75 km with 2,000 m of gain:

Seven lines. Nothing clever. That is the point.

If you want this built around your life

The framework above is what I would give any capable runner with a reasonable schedule. What it cannot do is account for your training history, the shift pattern you work, the knee that complains in week nine, or the specific course you have entered.

That is the part I do in 1:1 coaching - the same structure, bent around a real week. If you would rather start on your own, the free training plan generator will build a terrain-aware draft from this framework in about a minute.