Marathon Training Without Getting Hurt: A Realistic Prevention Plan

The shape of a marathon injury

Marathon injuries rarely come from one bad run. They come from accumulation: the long run grows, weekly mileage grows, and recovery stays the same. The danger zone is predictable — roughly weeks 10–14 of a 16–18 week block, when volume peaks and you're running every session on tired legs. Training load research is blunt: most running injuries follow a spike in load the tissues weren't prepared for.

That timing matters for planning. Training for the San Francisco Marathon in July means your highest-risk weeks land in May and June; a CIM build puts them in October and November; Big Sur in April means February and March. If you're going to book a gait analysis or get a lingering niggle assessed, do it before those weeks, not during.

Structure the block so it protects you

• Long run progression: add no more than 2–3 miles to the long run at a time, and never grow the long run and total weekly mileage sharply in the same week. One variable at a time — the same rule as increasing mileage safely.
• Down weeks: every third or fourth week, cut volume 20–30%. This is where tissues actually adapt. Plans that climb for ten straight weeks read as ambitious and perform as injury generators.
• The long run is not a race: most of it belongs at conversational pace. Racing your long runs is the classic way experienced runners break themselves in week 12.
• Sleep is training: the weeks you can't protect sleep are the weeks to trim intensity, not push through.

Keep the strength work — especially when tired

The strongest injury-prevention evidence in sports medicine is for strength training: it roughly halves overuse injury risk. It's also the first thing runners drop when mileage climbs, which is exactly backward — the peak weeks are when you need it. The fix is to shrink it, not skip it: two 20-minute sessions a week of the runner's big five, kept light during peak weeks. Maintenance, not progress.