Long run that is. I know where you were heading.
This Sunday will be one month until marathon #2, and also marks the longest of my long runs for this training plan, 23 miles. I’ve done a 20 and a 21 as part of this plan, so I’m not worried about being able to get it done. I am wondering, however, if 23 miles is too many miles for a training run. The aftermath of 20 and 21 wasn’t terrible, but after the 26 for marathon 1, I ended up in PT for ITBand issues. My IT Band has held up pretty well, and my Plantar Fasciitis seems manageable right now. I like the idea of 23 miles as a better way to get my body ready for the race-day reality. However, I’ve read several articles questioning the marginal return of training miles beyond 20.
I know I’ll get out there and go for 23 regardless of any doubts, since I refuse to stray too far from the training plan that so far has served me well. Mostly wondering if anyone has any practical and/or scientific insight into the point at which the return on the miles doesn’t necessarily justify the abuse on the body. One bonus is that I’ll be out-of-town for this run, so some new scenery will break up some of the monotony around my usual long-run course. For those of you in the Northern Virginia area, I’m tentatively planning 5 laps around Burke Lake, which should put me just over 23 miles. I’d be open to other suggestions if anyone has any.
Decided the best way to break out of my running mini-funk last week was to throw in a tempo run targeting 7-ish minute miles for 4 miles. Was able to hit the pace goal, and break the funk:
Tempo runs have probably been the best discovery for me during this training cycle. I’ve really enjoyed the couple time I’ve been able to do track work as well, but don’t care for having to feel like I’m breaking into Fort Knox just to be able to use the local tracks. Abundantly frustrating to have to jump the fences that my tax dollars built to trespass on a track that my tax dollars built at the school my son attends that my tax dollars (and my straight-out-of-the-wallet dollars) support.
I'm with you on the track thing. It's pretty *^%#@ stupid. I like the one 23 miler I do in my training. Well 23 miles and 12".
ReplyDeleteLong runs are so dependent on the runner and coach or training plan. I'd say go for it, enjoy it, and stop if you need to.
ReplyDeleteI don't like breaking into tracks either but it is always worth it in the end. Good luck with whatever you decide on for your long run. I would offer advice but I have only done one marathon so I need more experience so I am not just bs'ing ya!
ReplyDeleteI find even a 20 miler breaks down my body a bit much, but that's just me. If you can run 23 and feel good, I think it's a great confidence booster.
ReplyDeleteI think it's a personal thing and if will do better mentally with a 23-miler, then you should do it but just give yourself a lot of rest after to recover. I've been known to use a marathon to train for a marathon but it just depends what fits into my training cycle. Good luck!!
ReplyDeleteI'm a half marathon runner, not full, so I'm not sure of the answer, but I've heard that undertraining is better than over...not that you are or will be undertrained, but in case 23 really is too much...better safe than sorry I would think...take that with a grain of salt, I'm a frequently injured runner
ReplyDeleteAnd the first sentence made me chuckle
I plant to run 25 miles as my longest training run for my first marathon in dec. I would love to do a longer distance, but I only have 5 weeks left. I'm afraid to get injured. =( What you said here is correct. If it can be avoided, I don't want to surprise my body on marathon day. So it's really a dilemma for me.=(
ReplyDeleteIt's all about listening to the body.
ReplyDeleteI personally set out to do >20 because I've had problems fading a bit at the end of marathons and wanted to work on that.
But the day I ran it, I was ready to abort if something started to go sour with the run. (Actually what I set out to do was run 4 hours, not a specific distance...turned out to be 24 miles)
I also ignored pace in this run, doing an easy pace. (10:00)
I took two days off afterwards and was then good to go for a fast 7 miles..so recovery doesn't have to be that bad, if you keep it slow.
Anyway, YMMV, but you might give it a try (carefully).
Seems like most plans I see are 20 or 22 but I'm sure it's just dependent on what your body can take. I'll definitely do one 22 miler next time.
ReplyDeleteI've heard that anything longer than 20 isn't worth it for the wear and tear it puts on your body. But then others swear by 22. I'd like to do 22 but I know I'm pretty injury prone, so I'll stay away for a while.
ReplyDeleteAnd as for jennings, he HAS to have a good week this week. All our other receivers are injured. There's no one left to throw to! But I agree... last week's performance was pretty weak. :(
I agree that this is a personal thing. Since I'm struggling with overuse injuries, I'm trying to get to the finish line with the least amount of mileage under my feet so 20 is and will be my longest run.
ReplyDeleteI do 22 miles as my longest runs for a marathon. If I had a practical route of 23 miles I would certainly do that. Go for it, but take it easy. Long runs are still the most important part of my training.
ReplyDelete23! awesome
ReplyDeleteNever in my life had I heard of a 23 mile training run for a Marathon. It's not a death march... making some pit stops or a few walking breaks will not degradate the workout.
ReplyDelete