My 16-week trail marathon training plan is for a runner with a stable base and a specific course in mind. I build consistent easy running, add climbing and descending gradually, rehearse hiking, fueling, and gear, then taper over the final two weeks. The week-by-week table is an example progression; I adjust it to the course and to how the runner recovers.
I do not train for 26.2 miles in the abstract. I train for the specific surface, vertical gain, weather, altitude, aid gaps, technicality, and likely hours on my feet. Two trail marathons can share a distance and require very different preparation.
This plan is written for a healthy intermediate runner who already runs consistently. It is not a return-from-injury schedule or a promise that one weekly mileage number fits everyone. I use readiness gates and adjustment rules so the plan follows the runner rather than forcing the runner to serve the spreadsheet.
At a glance: I use four or five running days per week, anchored by one focused workout and one long trail-specific run. The example table starts at 22–30 miles (35–48 km) per week, peaks at 36–48 miles (58–77 km) in week 13, and tapers through weeks 15–16. Those are example ranges for a prepared runner, not targets to jump into from a smaller base.
Who should start this 16-week plan?
Before week 1, I want eight reasonably consistent weeks, four running days most weeks, a comfortable 90-minute long run, and no recent mileage spike. I also want normal recovery: easy effort feels easy, sleep and appetite are stable, and ordinary soreness does not change my gait.
| Readiness check | My minimum starting point | If it is not there yet |
|---|---|---|
| Consistency | About eight uninterrupted weeks | Build routine before adding specificity |
| Weekly frequency | Four runs on most weeks | Stabilize four days before considering five |
| Long-run durability | 90 easy minutes without a recovery hangover | Extend gradually on forgiving terrain |
| Trail skill | Controlled movement on basic uneven ground | Learn at low speed before adding fatigue |
| Health | No pain that changes gait or worsens across runs | Pause progression and seek appropriate help |
| Schedule | Time for one workout, one long run, and recovery | Choose a later race or a shorter course |
If I am returning after illness, injury, or a long layoff, I first use my return-to-running framework. I do not compress missed foundation work into the opening weeks of this plan.
Persistent focal pain, swelling, pain at rest, fainting, chest symptoms, neurological signs, or severe unusual breathlessness is not a training-plan puzzle. I stop and seek qualified medical evaluation.
I map the course before assigning miles
The Race-Demand Map is the center of my plan. I write what the course will ask, where it will ask it, and what failure would cost. Only then do I choose workouts.
| Race demand | What I record | What I train |
|---|---|---|
| Vertical profile | Total gain/loss and climb distribution | Hill duration, hiking, descent exposure |
| Surface | Smooth dirt, gravel, roots, rock, mud, sand | Skill venue, shoe, and pace control |
| Technical concentration | Early, late, or continuous | Where I place skill under fatigue |
| Aid gaps | Expected elapsed time between stations | Carry capacity, fuel, and fluid rehearsal |
| Exposure | Heat, cold, wind, altitude, darkness | Timing, clothing, and contingency practice |
| Cutoffs | Location and realistic arrival window | Hiking speed and segment planning |
| Rules | Mandatory kit, poles, crew, headphones | Equipment practice and logistics |
I measure surface and vertical by time as well as distance. A steep technical mile can take longer and cost more attention than several smooth miles. I also mark where descents occur, because a runnable downhill after three hours is a different demand from the same slope near the start.
If I cannot visit the course, I assemble its profile, maps, organizer notes, and reliable race descriptions into a short demand statement. Mine might read: “Five-hour effort, repeated 10–15-minute climbs, 4,500 feet of gain, rocky final descent, warm exposed middle section, 75-minute aid gap.”
That sentence decides more than the word marathon.
My five training gears
Trail pace changes with grade, footing, heat, altitude, and pack weight. I therefore prescribe most work by effort and purpose.
- Easy — RPE 3–4: I can speak in full sentences and finish with plenty in reserve.
- Steady — RPE 5–6: I am purposeful but controlled, with short sentences available.
- Threshold — RPE 7: I can speak only brief phrases, but effort stays even rather than desperate.
- Purposeful hike: I move efficiently uphill while keeping breathing sustainable.
- Strides — fast and relaxed: I run 15–25 seconds with full recovery and no straining.
I use my RPE scale for runners to calibrate these gears and my guide to trail effort versus road pace when terrain makes watch pace misleading.
Easy means easy even on a climb. I shorten my stride, slow down, or hike before I turn an aerobic day into an unplanned threshold session. That discipline protects the quality of the workouts that actually need quality.
How I arrange four or five runs each week
I organize the week around two load-bearing sessions: one focused workout and one long trail-specific run. I treat a technical long run as quality even when heart rate looks moderate, because descending and continuous foot placement add muscular and attention load.
| Day | My default five-day structure | Four-day adjustment |
|---|---|---|
| Monday | Rest; optional gentle mobility | Same |
| Tuesday | Hills, threshold, or steady work | Same |
| Wednesday | Easy run | Same |
| Thursday | Easy run plus strength or strides | Easy run plus short strength |
| Friday | Rest | Rest |
| Saturday | Long course-specific run | Same |
| Sunday | Easy run or purposeful hike when recovered | Rest or an easy hike; no fifth run |
I keep hard days hard enough to matter and easy days easy enough to absorb them. I place strength after a quality run or later on the same day when practical, preserving a real recovery day rather than spreading moderate fatigue across the week.
Tuesday, Wednesday, Thursday, and Saturday are the four running days in the reduced version. A recovered runner may add Sunday as the fifth run; a hike remains optional movement, not another required workout. The exact weekdays can move, but I avoid placing a demanding descent beside heavy lower-body strength or another hard run. I use my method for balancing running and strength training when life forces rearrangement.
My 16-week trail marathon training plan
The volume ranges are examples, not entry fees. The table uses miles; multiply by about 1.6 for kilometers. I start near the level my recent training already supports. If the low end is still a jump, I am not ready to begin this version of the plan. Race-week mileage is intentionally not prescribed because the race itself dominates that week.
| Week | Weekly volume | Long run | Key job and completion gate |
|---|---|---|---|
| 1 | 22–30 mi | 1:45 | Establish easy rhythm; finish able to train normally in 48 hours |
| 2 | 24–32 mi | 2:00 | 6 × 2-minute controlled hills; keep the final rep composed |
| 3 | 26–34 mi | 2:10 | Low-speed technical practice; quiet, timely foot placement |
| 4 | 20–27 mi | 1:35 | Cutback; restore energy rather than prove fitness |
| 5 | 27–36 mi | 2:20 | 3 × 8-minute uphill steady; repeatable effort |
| 6 | 29–38 mi | 2:35 | Small downhill dose plus first complete fuel trial |
| 7 | 31–40 mi | 2:45 | 25-minute steady block; no late mechanical fade |
| 8 | 24–32 mi | 1:50 | Cutback and equipment audit; resolve pressure or carry issues |
| 9 | 32–42 mi | 3:00 | Course-like terrain and planned hiking transitions |
| 10 | 34–44 mi | 3:15 | 4 × 8-minute uphill threshold; controlled descent home |
| 11 | 35–46 mi | 3:30 | Full fueling and carry rehearsal; stable stomach and energy |
| 12 | 27–36 mi | 2:15 | Cutback; absorb the specific block |
| 13 | 36–48 mi | 3:30–4:00 | Peak simulation; finish coordinated and recover on schedule |
| 14 | 31–41 mi | 2:45 | Race-effort segments without chasing fatigue |
| 15 | 22–30 mi | 1:40 | Taper; retain frequency and brief intensity |
| 16 | Race week | Race | Arrive fresh, execute the demand map |
For a slower runner, I prioritize elapsed time over distance. I cap this example’s peak simulation at four hours and shorten it if past recovery says that is too much. I do not need to complete the marathon distance in training to be prepared.
I also do not chase the top of every range. My body does not award extra credit for turning 38 planned miles into 43. I choose the amount that lets me complete the next important session with normal mechanics.
What one training week actually looks like
Week 10 is a useful example. I rest Monday. On Tuesday I warm up, run 4 × 8 minutes uphill at controlled threshold effort with easy returns, then cool down. Wednesday and Thursday are 45–60 minutes easy; I add short familiar strength after Thursday if I am recovering well. Friday is rest. Saturday is the 3:15 course-like long run with planned hiking, fueling, and a controlled descent. Sunday is 40–60 easy minutes only if Saturday has not changed my gait or ordinary easy effort.
For four run days, I omit Sunday rather than squeezing those minutes into the workout or long run. For five, Sunday adds easy volume, never another quality session. The listed mileage range helps me check the overall load, but I do not run extra loops just to meet it when terrain makes time on feet more demanding.
Block 1, weeks 1–4: make consistency boring
My first block establishes repeatable easy running, basic trail rhythm, short hills, and a sustainable strength routine. I am not trying to feel race-ready. I am trying to make the next twelve weeks possible.
I keep most terrain forgiving. I add six relaxed strides after one easy run in week 1, then short controlled hill repetitions in week 2. In week 3, I practice technical foot placement at low speed while fresh enough to learn.
Week 4 is a deliberate cutback. I reduce volume and long-run duration before fatigue demands it. My cutback-week method explains why planned absorption is part of progression rather than evidence that training has stalled.
The block passes when my easy effort is stable, no soreness changes my gait, and the 2:10 long run does not erase the following days. If it does not pass, I repeat or reduce; I do not advance because the calendar says week 5.
Block 2, weeks 5–8: add force and controlled descent
In the second block, I extend uphill work, introduce a small downhill dose, and begin fueling as a skill. I change one major load at a time.
For the uphill steady session, I choose a grade that lets me maintain posture and repeat effort. If my course uses long climbs, I favor continuous work. If it uses repeated short climbs, I use repetitions with easy return. My hill-repeat guide helps me control purpose rather than sprint every incline.
I add downhill exposure conservatively: four to six descents of 30–60 seconds on smooth ground, controlled enough that my feet remain quiet. I progress duration, technicality, speed, or total descent—never all four together.
Week 8 cuts load again and audits equipment. I want shoes, socks, vest fit, bottle access, and anti-chafe choices moving toward settled. If gear creates pressure or changes my gait, I solve it now, not during taper.
Block 3, weeks 9–12: train the course decisions
This is where my Race-Demand Map becomes visible in the week. I bring long runs onto course-like terrain, practice purposeful hiking before exhaustion, and place selected descents later in the outing.
I do not chase an exact vertical-gain ratio every week. I first increase exposure frequency, then total gain, then the duration of sustained climbs. During selected weeks, I approach the event’s gain per hour or per mile without forcing a number my terrain cannot support safely.
If I live somewhere flat, I use stairs, treadmill incline, bridges, or repeated small hills for propulsion and hiking. I still seek outdoor uneven-ground practice for line choice and descending because uphill fitness cannot substitute for trail skill.
Week 11 is my complete fueling and carry rehearsal. Week 12 reduces load so I absorb the block. If week 11 leaves me flat for most of week 12, I record that cost and reduce the peak simulation rather than pretending the fatigue is fitness.
Block 4, weeks 13–16: rehearse, sharpen, taper
Week 13 is my peak simulation, not a secret race. I reproduce the course’s important decisions without reproducing the entire distance.
I wear intended shoes, socks, pack, layers, and poles if permitted. I start at a relevant time of day, use representative climb density, practice every fuel interval, refill, hiking trigger, and late descent decision.
The simulation passes when I finish coordinated, can explain my pacing, tolerate my equipment, and recover in time for the next planned week. Average pace does not rescue a session that destroys my descending or costs four days of normal movement.
Week 14 includes controlled race-effort blocks but less total load. Weeks 15–16 reduce volume while preserving familiar frequency and brief intensity. I do not introduce new shoes, foods, strength movements, or aggressive mobility during taper.
I build vertical gain without stacking stressors
Vertical is load, not decoration. Climbing raises metabolic demand; descending adds eccentric and neuromuscular cost. I count both.
My safest progression changes one major variable per week: mileage, vertical gain, intensity, technicality, or long-run duration. If I raise vertical substantially, I hold another lever steady. I use my safe mileage progression rules rather than treating a ten-percent formula as a command.
I also distinguish climbing from hiking. Hiking is not a failed run; on steep grades it can preserve energy while maintaining strong vertical progress. I choose a breathing cue, grade, or course landmark that triggers the transition before my legs are flooded.
I practice the mechanics in my guide to climbing steep trails: short steps, useful arm drive, tall-enough posture, and a prompt return to running when the grade eases.
Downhill skill gets a dose, not a dare
I train descending through repeatable control. I scan several steps ahead, keep peripheral awareness near my feet, use quick adaptable steps, and avoid sitting far behind my heels while braking continuously.
I stop a descent set when placement becomes late, loud, or reactive. Mild fatigue can teach useful transfer. Collapsed coordination teaches the wrong movement and adds risk.
My technical instruction lives in how I descend technical trails, while my downhill-running progression builds tissue and neuromuscular tolerance over time. In this plan, I schedule those skills; I do not relearn them from scratch inside every long run.
Strength supports the trail, not my ego
I use two short strength sessions during the first half and one maintenance session during the most specific weeks. I keep repetitions controlled and leave technical reserve.
My menu includes a split squat or step-up, straight- and bent-knee calf raise, hip hinge, lateral step-down, trunk carry or anti-rotation movement, and a row or pulldown when poles matter. I choose movements I can execute consistently rather than collecting exercises.
Strength passes when it improves capacity without changing my mechanics in the next run. If soreness compromises descending, I reduce sets, load, or proximity to the key session. In the final two weeks, I reduce volume sharply and retain only familiar light work.
Fueling is a workout objective
A trail marathon may take far longer than a road marathon, so I practice eating and drinking by elapsed time. I begin early during long runs rather than waiting for hunger or an energy crash.
I record the product, carbohydrate amount, interval, fluid, sodium source, temperature, carry method, and stomach response. I change one item at a time. My fueling-by-duration guide helps me build the starting schedule; the long runs determine what my stomach and course logistics can execute. I do not adopt a new fuel target on race morning.
I carry enough to bridge the longest expected aid gap plus a reasonable delay. I test race-provided foods only after confirming what the organizer actually supplies.
I do not force a universal drinking volume. I use a practiced plan informed by thirst, conditions, sweat behavior, access, and duration. Both inadequate intake and excessive fluid intake can create serious problems.
Gear must disappear during the run
By week 11, I want gear choices to feel routine. A vest should stay stable when full and remain accessible as it empties. My hydration-vest fit checklist helps me solve bounce, pressure, and access before the peak simulation rather than accepting an uncomfortable carry system for race day.
I choose shoes for the course’s most consequential surface, then make sure they remain tolerable for the entire event. If training involves paved connectors, my road-to-trail shoe method helps me balance grip, ride, and wear.
I test mandatory kit, lighting, anti-chafe, socks, carrying load, phone protection, and pole storage in motion. The goal is not owning equipment. The goal is removing avoidable decisions when I am tired.
My weekly decision rules
Every Sunday, I review mechanics, easy effort, sleep, appetite, motivation, soreness, and the recovery cost of the long run. I use trends, not one strange number.
I proceed when easy effort feels normal, my gait is unchanged, and I can absorb key sessions on schedule. I repeat a week when the training was useful but not yet absorbed. I reduce when fatigue accumulates across several signals.
I do not repay missed sessions. If I miss Tuesday, I do not squeeze the workout beside Saturday’s long run. If I lose more than a week to illness or disruption, I remove intensity and rebuild from current capacity.
I also schedule rest intentionally. My guide to rest days for running helps me decide whether rest, easy movement, or a rearranged week best protects the next important session.
My adjustment matrix
| What I observe | My first adjustment | What I do not do |
|---|---|---|
| Long run changes gait for days | Reduce duration, vertical, or technicality | Add recovery miles to “flush it out” |
| Easy effort stays unusually high | Remove intensity and inspect sleep, illness, heat, fuel | Force target pace |
| Downhill coordination deteriorates | End the skill dose and return on easier terrain | Chase one final fast descent |
| Stomach fails late | Simplify and change one fueling variable | Replace the whole plan at once |
| Life stress spikes | Keep frequency if useful, reduce load | Treat missed mileage as debt |
| Pain localizes or worsens | Stop the provoking load and assess appropriately | Hide it inside altered mechanics |
This matrix is why I prefer a framework to a rigid schedule. The best adjustment is often small and early. Waiting until the plan breaks usually costs more training than removing one session.
Three rehearsals, three different questions
My first rehearsal asks: can I carry the gear, fuel early, and remain genuinely easy on trail? I keep terrain moderate so equipment and routine are visible.
My second asks: can I climb and hike according to plan, then resume running without a large effort spike? I use course-like vertical but do not maximize technicality.
My third is the week-13 simulation. It asks: can I execute the combined system—gear, fuel, climbing, hiking, late descending, and judgment—while finishing coordinated?
I write no more than three changes after each rehearsal. Endless adjustments create noise. A short ranked list produces action.
Race-week execution begins slower than excitement wants
I start below the effort that feels available. Cool air, fresh legs, and other runners make an opening climb deceptive. I let people go if matching them would spend energy outside my plan.
I hike at the chosen cue, fuel before appetite fades, and refill before the long gap begins. I descend with enough control to protect my quadriceps and attention for the final third.
I judge progress by segments, aid stations, and cutoffs—not by road-marathon splits. A slow mile can be excellent execution on a steep technical climb.
If weather, footing, or my body changes, I change pace, layers, line choice, or goal. The course always has a vote. For remote training and race preparation, I use my trail-running-alone safety system even when an organized event will later provide support.
Mistakes I refuse to build into the plan
I do not turn every climb into a race
Hard climbing is useful when scheduled. Unplanned threshold work on easy days slowly removes the recovery margin that lets my long run succeed.
I do not save hiking for exhaustion
I practice hiking while coordinated and choose the trigger in advance. That makes it a performance tool rather than an emergency response.
I do not measure preparation by one heroic long run
The best long run is one I absorb. A four-hour outing that destroys the next week is less valuable than a shorter simulation that supports the full block.
I do not add mileage, vertical, intensity, and technicality together
When several variables rise at once, I lose the ability to identify what exceeded capacity. I progress one major lever and observe the response.
I do not arrive at taper with unresolved equipment
Week 13 should confirm my system, not begin a shopping cycle. New gear during taper adds uncertainty without enough time to validate it.
I do not copy another runner’s fuel or pace
Finish time, body size, heat, stomach tolerance, terrain, and access differ. I borrow ideas, then test my own execution.
Frequently asked questions
How many miles per week do I need for a trail marathon?
In this plan, many prepared recreational runners peak around 36–48 miles, but I care more about training history, course demands, time on feet, and recovery. I start near proven volume rather than jumping to the range.
What should my longest trail marathon training run be?
I use 3:30–4:00 for the peak simulation in this example, then shorten it when recovery history calls for less. I want course-specific durability and a complete rehearsal, not a training-day marathon that removes the next week.
Do I need to run five days per week?
No. Four well-placed runs can work when they include consistent easy volume, one purposeful workout, and one long course-specific run. I add a fifth day only when it improves durability without weakening recovery.
Are back-to-back long runs required?
No. I may add 45–75 easy minutes or a purposeful hike after selected long runs, but only when it teaches movement on tired legs without compromising the following week.
How much elevation gain should I train each week?
I begin with vertical I already tolerate, then increase frequency, total gain, and sustained-climb duration one step at a time. In specific weeks, I approach the race’s gain density without forcing an exact match.
Can I train for a trail marathon without mountains?
Yes, if I use treadmill incline, stairs, bridges, or repeated hills for climbing and seek some outdoor uneven-ground practice for line choice and descending. Extremely technical or mountainous races still require honest skill preparation.
When should I start tapering?
I reduce volume after the week-13 peak simulation, use week 14 as a controlled bridge, and taper more clearly during weeks 15–16. I maintain familiar frequency and brief intensity while removing fatigue.
Can a road runner use this trail marathon plan?
Yes, after building trail skill progressively. Aerobic fitness transfers, but hiking, descending, technical footing, equipment, elapsed-time fueling, and course-specific judgment need deliberate practice.
My bottom line
My 16-week trail marathon training plan begins with a Race-Demand Map, not a generic mileage target. I build consistency, add vertical and descending in controlled doses, practice hiking before fatigue, rehearse fueling and gear, then peak with one complete simulation.
I keep one workout and one long run as the week’s anchors. I let recovery evidence decide whether to progress, repeat, or reduce. I never treat missed training as debt.
Distance matters, but the finish is decided by how well I prepare for the surface, slope, elapsed time, equipment, and decisions of the actual course.
Written by Ken — the runner behind NextGait. Across 12 years of running, I have learned to build a trail-marathon plan around the actual course, then let recovery decide when to progress, repeat, or reduce. More about me →