Cycling knee pain: the mistake that cost me a race
Early knee-pain warning, a saddle set 1 cm too high and a race I couldn't start. What caused my cycling knee pain and how I fixed it in five weeks.
It always starts the same. Small itch on the inside of my left kneecap, ten minutes into the ride. Not pain yet.
I know what comes next if I ignore it: inflamed knee, can’t load it, weeks off the bike. I’ve had cycling knee pain enough times. This year I ignored it anyway. It cost me my A race.
The itch is an early warning
Pain at the front of the knee, around and behind the kneecap, is the most common overuse complaint in cycling. It does not come from one moment, it builds up. So it also warns you early. Most riders just ride through that small itch.
I knew the signal and still did not stop. My rule now: if I feel the itch around the kneecap, the ride ends that minute. A skipped session costs a day. Riding through it costs a month.
How I dug the hole
Two weeks before my A race, the local XCM marathon championship, I was training hard and tipped into overtraining. Then a family holiday added several days of heavy hiking. The knee was already overloaded before I did anything obviously wrong.
Then the stupid part. After cleaning the bike I saw my saddle height marker tape had slipped. I reset it and put the saddle about 1 cm too high. Saddle height changes how the knee tracks on every pedal stroke. Even a few millimetres change the load on the joint. A fresh knee might handle it. Mine was already irritated.
I rode out to recon the race course. The itch came early, 2 out of 10. I thought it would settle. It did not. I finished at 8 out of 10, with a knee I could not load.
Rest, test, rest: the mistake that cost the race
For the next two weeks I did the worst possible thing:
- rest a few days
- feel better
- test it with a ride
- irritate it again
- repeat
I was afraid to lose form so close to the race. So I kept checking if the knee was ready. It only kept the inflammation alive. In the end I could not even start the race.
Once a joint is inflamed, testing it is not recovery. Full rest and then a controlled return is faster. The form came back in a couple of weeks anyway.
What actually fixed it
Five weeks after the first itch it was resolved:
- Five days of complete rest from the bike. No testing.
- Easy spinning only, well below any load that provoked the knee.
- Resistance band work for glutes and hip stabilisers.
- Physio visit with ultrasound. Nothing structural: no tear, no tendon damage. Just inflammation, the kneecap pressed into its groove because the muscles around it were imbalanced.
- A personal program to build the weak muscles, plus activation and stretching for the tendons.
The diagnosis is the main lesson. My quads were strong, years of intervals will do that. My glutes were weak. When the glutes don’t do their share, the quads take the load and pull the kneecap harder into its groove. For patellofemoral pain the usual weak links are quads, glute medius, glute max and hamstrings. I had trained none of them directly. Only cycling, only intervals. It bit me.
The 44/56 split I couldn’t see
While rebuilding I finally bought the second pedal for my power meter. Before that I measured only the left side and doubled it. Dual-sided reading: 44% left, 56% right. My weak, painful leg was also my lazy leg.
Some imbalance is normal, and small differences are not worth chasing. Mine was not small. I put the balance number on the head unit and focused on single-leg work. Four weeks later it was between 51/49 and 49/51. Faster than I expected, maybe I got lucky. But you can only fix what you measure.
Strength is not optional
Superfly is built on hard days hard, easy days easy. Strength work was the part I quietly skipped. Intervals and volume make you fitter, but not balanced. Knee and hip stabilisers need direct, progressive loading. Tendons respond to slow, heavy, controlled work, not more pedalling.
That last part I took from Scott Hogan’s Built from Broken. Written for lifters, but it maps to cycling well. Best thing I read while I was injured.
Two short glute and stabiliser sessions a week would cost almost nothing. Skipping them cost me my target race.
FAQ
Why does cycling cause pain around the kneecap?
Usually it is patellofemoral pain: the kneecap pressed into its groove under repeated load. Common cause is muscle imbalance, strong quads and weak glutes. Bike fit and sudden jumps in training load make it worse.
Should I keep riding through cycling knee pain?
No. If you feel the early itch around the kneecap, end the ride. A skipped session costs a day, riding through it can cost weeks.
Can a saddle 1 cm too high cause knee pain?
Yes. Saddle height changes how the knee tracks on every pedal stroke. A healthy knee may handle it, an irritated one will not. Check your saddle height after any maintenance.
What strength exercises help cyclist’s knee?
Work on quads, glute medius, glute max and hamstrings. Resistance band work for glutes and hips, plus single-leg exercises like split squats and bridges. Two short sessions a week is enough to see a change in a few weeks.
How long does patellofemoral knee pain take to recover in cyclists?
Mine took five weeks, and most of it was self-inflicted by testing too often. With real rest, a graded return and strength work, a mild case can settle in one to two weeks.