It’s the last week of taper here and I got in a nice four mile run on Monday morning — two easy and two at marathon pace. And it was a good thing I wore my new Garmin 220 to pace myself because I realized that when I originally set the data screens, I chose “average pace” (average pace for the entire four miles) instead of “average lap pace” (average pace for the mile you are currently running). For marathons I like to keep an eye on my average lap pace, and that will be particularly important for this downhill marathon, REVEL Canyon City, because I expect the pace to be faster in the first half than the second. In fact I used the pace band feature at FindMyMarathon.com to create a free pace band that is specific to the REVEL Canyon City course. Other marathons I’ve generally tried to run an even pace, but that doesn’t make sense for this course. It’s nice to see what the predicted adjustments to pace are for the hills — both up and down — for this specific marathon.
Yesterday I did an easy three-miler that nearly undid six months of marathon training when I got distracted and rolled my ankle on this sucker:
In the instant my left foot rolled on the pod, pain shot up my left ankle and the marathon flashed before my eyes. My run came to a screeching halt. I quickly took a tentative step and tried to walk off the injury. By some miracle it felt a million times better after a minute of walking and I was able to finish the run. Throughout the rest of the day it stiffened up and became sore, but I iced it before bed and this morning it’s almost back to normal. Every taper has its aches and pains and this one is no exception. Now I just need to do one more easy three miler (including three strides and not including magnolia seed pods of doom) on Thursday and I’ll be ready for the race on Saturday.
While I ran on Monday I listened to an inspiring Runners Connect podcast interview with Olympic medalist Deena Kastor. Usually before a marathon I watch the movie Spirit of the Marathon again to see Deena race at the Chicago Marathon, but this time it was nice to listen to her advice for getting ready for a big race. She suggested that a runner list five reasons why the upcoming race should be successful. That helps calm your nerves and gives you things to draw upon during the race if and when your confidence falters.
So, here are five reasons my sixth marathon could/should/will go well:
1. With my switch to a traditional training plan that had me running five days a week, I managed to hit my highest mileage week ever (40.5 miles) and highest mileage month ever (156.3 miles in October). Not exactly numbers to write home about but pretty darn good for a 44-year-old mother of three.
2. I had that successful and joyful practice 20-miler on the course in the San Gabriel mountains.
3. I looked back over my training log (I keep one on my paper training plan and one on MapMyRun) and reminded myself that I kept consistent with the training. I didn’t miss a single run. Several times when the plan called for cross-training or rest, I rested, but I did every prescribed run. One 16-miler I cut short at 10.6 miles because I felt dehydrated and under-fueled and it was more important to set my ego aside and call it a day than continue and risk injury just to hit that 16 mile number. Sure enough I went on to have several confidence-boosting long runs after learning from my mistakes on that one “bad” run.
4. I made sure to keep up with the strength training at least twice a week. If you asked me the one thing I would recommend to other runners to improve their marathon performance, it would be to add strength training if it’s not already a part of their regimen. As little as 20 minutes twice a week can pay off tremendously in better running form and ability to hold pace in the final miles of a race when your primary running muscles are tired.
5. I nailed down my carbohydrate loading plan and race day plan. It’s not easy to consume over 600 grams of carbohydrates a day but I’m doing my best. I didn’t mind the whole wheat pancakes with maple syrup for breakfast this morning!
So, if you want to see if my ankle cooperates for the race, if my training plays off, if the carbo-loading prevents me from hitting the wall, you can track me on race day (Saturday November 7 starting at 7 a.m. PST) through my participant tracking link. The tracking registers my time at the half marathon point, 5K to go (mile 23.1), and the finish. I expect the first half to be significantly faster than the second given the 4,000+ foot elevation drop in the first half, so don’t be surprised if it takes me a while to pop back up at the 23.1 mark. Cross your fingers for a sub-3:55 (BQ) and better yet a sub-3:36:58 (PR)!