how downhills? wrote:
I'm in the same boat as plenty of people posting here, having bonked way earlier than I'd expected (despite the fact I came in in much better shape than when I ran 2:51 in Philadelphia in November).
I train on lots of rolling hills, did some tempos on rolling hills, did some long runs that involved lots of uphills and downhills and made sure to go out merely at goal pace through the first half on Monday (very even 5k splits through that point) rather than faster than goal pace.
Still, I was left with the sense that the downhills ripped up my calves and quads, leading to lots of cramps, etc. How, exactly, DOES one "train for the downhills" -- or "properly run on downhills," as people keep saying -- beyond what I've described? Am I missing something obvious?
Should I have taken the first 5k (which is net downhill) significantly SLOWER than my goal pace? I figured that just by running EVEN splits through the downhill, that I was holding myself back.
I would actually get out faster in the first 5K so that you're not fighting gravity the whole way. I know that's against the conventional wisdom, but it worked for me (the heat not withstanding).
The best way I can describe to run downhill is not to fight it. Let gravity pull you along. The more you fight it, the more you end up braking and eccentrically loading your quads. That's what ends up blowing them out at the end of the race.
At Boston you need to run an even effort, not an even pace. It is a fast course if it is run correctly. But most people don't run it correctly. They listen to the same stuff about "don't go out too fast," blah, blah, blah. That's not really good advice there. Because now you're holding back and breaking on the downhills and trashing your quads. So the right way to approach it is to go out fast on the downhills, and slow down on the uphills (not only in Newton, but on every one of them on the course) and run an even physical effort throughout the first 20-21 miles. Then it's give it all you have left for the last 5-6.