Nearly Half of First-Time Marathoners Get Injured. Here’s How to Stay Off That List

Full disclosure: Some links in this article are affiliate links. We may earn a small commission at no extra cost to you if you make a purchase through them. Our recommendations are based on what real users report, not on commission size.

Why Nearly Half of First-Timers Get Hurt (And Why It’s Rarely the Shoes)

If you are midway through your first marathon block and something in your body already feels off, you are not the unlucky one. You are the typical one.

Runner’s World reported on September 16, 2026 that close to half of first-time marathoners deal with an injury during their training block. Half. That is not a fringe outcome reserved for the stubborn few who ignore every signal their body sends. It sits much closer to the default result for anyone who picks up a generic 18-week plan and follows it exactly as printed.

Sit with that number for a second, because it changes what your training log should look like. If injuries were rare and random, you would shrug and hope for luck. At roughly 50 percent, the smarter read is that the plan as written carries real risk. That makes your job editing it instead of obeying it.

Running more isn’t the problem. Running suddenly is.

A September 23, 2026 report from Health Chosun framed the question cleanly: running more versus running suddenly, and which of those behaviors carries the higher injury risk. The answer lands on the second one.

Your tendons, bones, and connective tissue do not adapt on the same timeline as your lungs and your confidence. Aerobic fitness can climb noticeably in two or three weeks. A tendon remodeling under new load takes closer to six to twelve weeks to catch up. That leaves a gap, sometimes a wide one, between what your cardiovascular system can handle and what your structure can absorb.

Mileage jumps land right in that gap. Going from 12 miles a week to 30 in a single month is the classic version. So are the sneakier ones: three straight weeks of increases with no down week, a long run that grows by four miles because you felt great that morning, or a Tuesday tempo dropped into a week that already had hills and a race-pace session. None of those look reckless written on paper. Stacked together they form a slope, and your tissue does not care about your intent.

Runner’s World ran a companion piece on September 21, 2026 about the training mistakes that send new runners to the physio. The thread through it will sound familiar to anyone mid-block: too much intensity crammed into weeks that were supposed to be easy, and long runs treated as a test instead of a rehearsal.

Your shoes are fine (probably)

A fresh pair of trainers is a reasonable purchase. If yours are past the 300 to 400 mile mark, checking current prices on Amazon is a cheap, sensible move, and worn-out foam does change how impact feels underfoot.

What no shoe does is fix a plan that doubles weekly volume in four weeks. Cushioning softens the sensation of impact. It does not speed up how quickly your Achilles, tibia, or plantar fascia adapt to new stress. I have watched running friends spend $180 on a new pair and then head out for 20 miles they had no business running. The shoes handled it beautifully. Their left calf did not.

Gear is a small lever. Load progression is the big one, and it stays invisible in every product review you read because there is nothing to photograph.

The filter to use for the rest of this article

Not all discomfort means damage, and treating every twinge like a stress fracture will make you miserable for 18 weeks. Use this instead:

• Soreness that eases as you warm up and fades within a day or two: normal training response, keep going.
• The same spot hurting at the same intensity for more than a week without improving: worth watching, so cut intensity and see what changes.
• Pain that sharpens as you run, changes your stride, or wakes you up at night: stop and get it assessed. That is information, not weakness.

That last category is the one people ignore, mostly because stopping feels like quitting on the race. It isn’t. A week of reduced load in week nine costs you far less than eight weeks off starting in week fifteen.

It is motivation, not carelessness

Here is the part most injury articles skip. First-timers do not get hurt because they are reckless. They get hurt because they are invested. They claimed a charity bib or a bucket-list race, told their family, bought the watch, and now they are doing pace math on a treadmill at 5:40 a.m. in February.

That motivation is the asset. It just needs to point at the parts of training that never show up on a watch face: the full rest day, the easy pace that feels embarrassingly slow, the ten minutes of cooldown, the strength session you would rather skip, and eight hours of sleep on a Saturday instead of a third beer.

Those are the levers that actually move injury risk, and everything that follows builds on that idea. Hold onto it as you read.

The Five Training Mistakes That Send New Marathoners to the Physio

Ask a physio what walks through the door in the months before a first marathon, and you won’t hear about one dramatic blowout. You’ll hear about a steady drip of overload. The September 21, 2026 Runner’s World roundup of the mistakes that send new runners to the physio makes that plain. Two days later, a report out of Korea framed the same idea from another angle: running suddenly carries more injury risk than running more. If you’re sitting in the middle of a marathon block right now, that distinction is most of the story.

Runner’s World had already reported on September 16 that close to half of first-time marathoners get hurt during training. Read those pieces side by side and the lesson lands less on total mileage than on how quickly the load changes. Five errors come up again and again. Here is each one, plus the single adjustment to make this week.

1. Moving distance and intensity in the same week

Your long run climbs from 16 to 19 miles, and your Tuesday tempo gets longer or faster in the same seven days. Two stressors land at once. Tendon, bone, and fascia only have so much adaptation available in a week, and stacking both asks for more than that window can give.

This week: pick one variable and park the other. If the long run is growing, the tempo stays exactly where it was. Or swap the tempo for 20 to 30 minutes easy plus four to six strides at the end. Write the number down before the week starts so you aren’t negotiating with yourself on Tuesday morning.

2. Making up missed runs by stacking them

Life happens and Thursday disappears. The instinct is to run Friday and Saturday to get back on schedule, which puts two quality efforts back to back and runs the second one on legs that never finished recovering from the first. That is the sudden-load pattern the September reporting keeps pointing at.

This week: drop the missed run. It’s gone. Run the sessions you have planned and let the week be what it is. If skipping it genuinely bothers you, convert it to 30 easy minutes and nothing more. Three easy days in a row cost far less than two hard ones stacked.

3. Racing the long run

If every Sunday effort sits at or near goal marathon pace, you’re running a weekly time trial on legs that already carry a full week of training. It feels productive. It also means your hardest day is your longest day, which is a reliable way to build fatigue you never clear.

This week: keep the long run conversational for the bulk of it. Save pace work for a defined slice, like the final few miles of one or two key sessions in the whole block, not all of them. If you can’t hold a chatty sentence through the first two-thirds, you’re going too fast. I’ve caught myself doing exactly this, and the giveaway is always the same: the Monday easy run feels like work.

4. Skipping the cutback week

Three weeks of building, one week lighter. That shape exists for a reason, and it’s how most coached marathon plans are actually built. A straight line upward for sixteen weeks isn’t a plan. It’s a stress test with a bib number attached.

This week: if your plan has no down week, build one in. Cut total volume by a noticeable margin, roughly a quarter off your recent weekly average, and keep intensity light. Resist the urge to make up the difference later. The lighter week is the training, not a break from it.

5. Grinding through the same niggle for three weeks

Some soreness is just training. A spot that hurts in the first mile and fades by the third is usually fine. A spot that is still there next week, and the week after that, is a different conversation.

This week: set a rule for yourself now. If a niggle hasn’t improved after two easy weeks, or it’s getting worse, or it’s changing how you run, book an assessment. Getting it looked at isn’t a character failure. A physio visit in week eight costs you far less than a stress fracture in week fourteen.

That last part deserves its own beat, because it’s the one people miss. If you’re limping, favoring a side, or shortening your stride without deciding to, that’s information, not weakness. Pull the easy days forward and get eyes on it.

Tonight’s five-minute audit

Open your training log, whatever app or notebook you use, and pull up your last four weekly totals. Line them up next to each other, then ask two questions about each week:

• Did total volume jump more than about 10 percent over the previous week?
• Did intensity climb in that same week?

Two yes answers mark that week as your warning light. It doesn’t mean you’re injured. It means the next three weeks need to be boring: hold volume steady, keep most running genuinely easy, and let adaptation catch up to ambition. Reaching the start line healthy is the point of this block, and it’s much easier to protect than to rebuild.

Building a Body That Can Absorb 26.2 Miles

I have watched runners pour everything into the mileage column and almost nothing into the rest of the week. When the Runner’s World reporting landed in mid-September 2026 with that figure about nearly half of first-time marathoners getting hurt during training, my first thought was not about weekly volume. It was about what those runners skipped on the days they did not run.

A training block is a stress-and-absorb equation. Mid-block, you are adding load almost every week, and your job is making sure the tissue can take it. Four things do most of that work: strength, sleep, fueling, and a small stride adjustment. None of them eats your week.

Two strength sessions a week. That is the dose.

Twenty to thirty minutes, twice a week, for someone already running 35 to 45 miles a week. Not four sessions. Not ninety minutes of barbell work that leaves you limping through Tuesday’s easy run. Past a certain point, extra lifting stops helping recovery and starts eating it.

A session I have used with runners in your position:

• Split squats, rear foot elevated if you like them – 3 sets of 8 per leg
• Step-ups onto a bench or box – 3 sets of 8 per leg
• Single-leg calf raises – 3 sets of 10 to 12 per leg
• Romanian deadlift or a single-leg hip hinge – 3 sets of 8
• Side plank with a leg lift – 2 sets of 30 seconds per side

That runs about 30 minutes once you know the movements. Cut it to the split squats, the step-ups, and the calf raises and you are in and out in 20. Do it after an easy run or on a rest day, and keep the weights moderate enough that you are not wrecked the next morning.

Notice how much of that list is one leg at a time. Running is a single-leg sport. Every stride is a controlled fall onto one foot, and most overuse injuries in marathoners show up exactly where one leg cannot manage its own landing.

The calf deserves its own paragraph

This is the part most runners skip. The calf and the Achilles take a huge share of the load in the final third of a marathon, when you are tired, your form has drifted, and you are still asking those tissues to push you forward. They respond well to direct, fairly heavy strength work. Most runners never give it to them.

Two or three sets a week is enough. Load them until the last two reps are real work, not until you cannot walk the next day. Add a slow three-second lower and you get the eccentric part too, which is where a lot of Achilles trouble starts. Calf raises also happen to be one of the few things you can do in a hotel room on a work trip, so there is no good excuse to skip them.

Sleep is training

Seven to nine hours is the window where your body actually adapts to what you did that day. A runner sleeping five or six hours a night while adding mileage is stacking two stressors with no recovery between them, then wondering why the knee is cranky in week nine.

I am not going to pretend that fixing sleep is easy, especially with kids or a shift schedule. But if you are choosing between a fifth easy run and an extra hour in bed, take the bed. The miles will still be there next week.

Fuel the long runs

Underfueling does more than slow you down. When you run low on carbohydrate late in a long run, your form changes. You land harder, your stride gets sloppy, and connective tissue that was holding up fine at mile 12 is suddenly absorbing impacts it was not built for at mile 20.

The practical version: start taking in carbs early in any run over 90 minutes, not at the hour mark when you already feel the drop. Practice with what you plan to use on race day. Eat something with carbs and protein within an hour or so of finishing a long run. If you are running a deliberate calorie deficit during a marathon block, that is a conversation for a sports dietitian rather than something to wing.

One stride cue you can feel on your next easy run

Cadence gets overcomplicated. I do not want you chasing a specific number, because the right number is different for every body and chasing someone else’s will just make you feel like you are failing at running.

What you can play with: a slightly shorter stride, with the foot landing closer under your hips instead of out in front. That cuts down the braking force each step sends up through your shin, knee, and hip. Try it for two or three minutes on an easy run. Count your steps for 30 seconds, then see if you can take slightly quicker, shorter steps without actually speeding up. Most runners feel the difference inside a single run, usually as lighter feet and less pounding.

The cross-training rule

Biking and swimming replace a run. They do not get added on top of one. This is the mistake I see most mid-block, when someone feels good and decides to tack a spin class onto their normal week. That is not cross-training. That is a mileage increase wearing a disguise.

The health reporting out of Korea in late September 2026 made the point cleanly: injury risk sits more in how suddenly load changes than in how much you run overall. So keep it simple. If you bike for 45 minutes, you drop a run. If you are healthy, you probably do not need much cross-training at all. If something is niggling, swapping one easy run for a bike session keeps the engine working while the leg calms down.

What the week looks like

• Two strength sessions, 20 to 30 minutes, on easy or rest days
• Sleep of seven to nine hours, treated as a real training target and not a bonus
• Carbs during any run over 90 minutes
• One or two short stride-cue experiments inside easy runs
• Cross-training only in place of a run, never stacked on top

None of this is dramatic, and that is the point. The runners who reach the start line healthy are rarely doing anything exotic. They are just doing the boring things often enough that their legs stop being the limiting factor.

If you are due for a new pair of shoes, it takes two minutes to check current prices on Amazon before your next long run, though the strength work and the sleep will do more for you than any shoe on the shelf. If you have already added the calf raises or the split squats to your week, drop a note in the comments and tell the rest of us how it is going.

Red Flags, Recovery Weeks, and What to Do When Something Hurts

Every first marathon block has a moment like this. You’re three miles into an easy Tuesday run and something in your shin, heel, or knee pipes up. Not sharp enough to stop you. Just… there. Now you have about thirty seconds to make a call that shapes the next six weeks.

Most runners get that call wrong, and not because they’re reckless. Nobody ever handed them a decision tree. Here’s one.

Red flags that end the conversation

A few symptoms mean stop and get looked at. Not wait-and-see, not ice-and-advance. Treat these as a hard stop:

• Pain that changes your gait. You’re limping, shortening stride on one side, favoring a leg without meaning to. If you can spot the asymmetry in a storefront window as you pass it, that’s not a niggle.
• Pinpoint pain on a bone. A spot you can cover with one fingertip along the shin, the top of the foot, or the outer edge of the foot. Bone pain that’s worse the morning after a run, or that wakes you up, behaves nothing like muscle soreness.
• Swelling, warmth, or redness around a joint or along a tendon, especially when it showed up over a day or two.
• A spot that hurts when you press it and keeps hurting after you let go. Tender for a second is fine. Tender for a minute is not.
• Anything trending worse week over week. Same spot, but now it starts earlier in the run and lingers longer after. That trajectory matters more than the intensity on any single day.

Runner’s World reported in September 2026 that close to half of first-time marathoners deal with an injury during their training block. Read enough of those cases and one pattern shows up: runners push through the early version of a symptom that was still reversible. The stress reaction that would have cost two weeks becomes the stress fracture that costs a season.

Use the 24-hour rule for everything else

Not every ache is a red flag. For the gray-zone stuff, use a 24-hour window.

Twelve to twenty-four hours after a run, is the spot gone or clearly better? Keep training. Log it, watch it, run on softer surfaces for a few days if that helps, but you don’t need to change the plan. Same or worse? Change something before your next session. Volume, pace, terrain, or a day or two off.

What you don’t do is rerun the exact session that lit it up and hope for a different result. That’s how a blip turns into a diagnosis.

Cut the run, not the block

This is where newer marathoners get themselves in trouble. A warning sign shows up in week eight of an eighteen-week plan. They’re already behind on mileage from a rough few weeks. So they decide they can’t afford to lose a long run, run it anyway, and miss the next three weeks entirely.

Do the math. Dropping two easy runs and a long run costs maybe eighteen to twenty miles. Six weeks off with a bone injury costs you the race. Those numbers aren’t close.

The reporting on first-timer injury rates keeps pointing at the same mechanism: it isn’t how many miles you run, it’s how fast the load changes. Running suddenly carries more risk than running more. So when a warning sign shows up, smooth the curve instead of protecting a specific week’s number in your log. That number doesn’t matter. Your start line does.

Recovery weeks are part of the plan

Most marathon plans build three weeks up and one week down. The down week feels like dead space, especially early when you still feel good. It isn’t. That’s when your tendons, bones, and connective tissue catch up to the fitness your cardiovascular system already banked.

Runners who skip down weeks usually feel fantastic for about ten days. Then they don’t. If you feel great during a recovery week, resist the urge to bank those miles back. Take the easy week. Fifteen more hard weeks are coming.

Get the assessment early, not after it’s obvious

A physio appointment in week two of a nagging issue is cheap. A stress fracture that costs you the season is not, in money or time or the mood you’ll be in for three months.

Physical therapists who work with runners tend to be good at keeping you running while you fix the driver. That might be cadence, hip strength, a shoe that’s past its useful life, or a training surface you’ve been ignoring. Plenty of runners leave a first appointment with a modified week and a green light, not a boot.

Two sessions now beats a bone scan later.

Coming back: the return-to-run progression

When you do take time off, don’t jump back to where you left off. Fitness hangs around longer than tissue tolerance does.

Start with two easy runs at roughly half your normal volume. Same pace or slower. Wait twenty-four hours and reassess. If both came and went clean, add a little time the following week. If the symptom came back, you moved too fast, and you go back a step instead of pushing through.

Two half-volume runs tell you something real, and they’re short enough that they cost you nothing if the answer is no.

Keep one thing straight

The training block is a means to an end, not the point. A slightly undertrained runner standing in a start corral finishes far more often than an overtrained one watching the livestream from the couch with a bag of frozen peas. Every time.

So if you’re weighing whether to push through or pull back this week, pull back. You’ll almost never regret it on race day.

And if a piece of gear is genuinely part of the fix, whether that’s a fresh pair of shoes with some life left in the foam, a roller, or a calf sleeve your PT actually recommended, check current prices on Amazon before you commit instead of grabbing the first search result. If you’ve already been through a first marathon block, leave a comment with what got you to the line. Someone reading this in week nine with a sore shin needs your answer more than they need mine.