The workout that raises my anxiety level the most in my training plan is the "13.1 mile spec test." Okay, so the "10K time trial" also fills me with dread, but the specificity of the spec test for what I am trying to accomplish is what really gets me wired. The workout calls for, "2 mile warm up, 13.1 miles at marathon pace, 2 mile cool down." Intuitively if you have a marathon goal pace in mind, it should be pretty easy to hold it for 13.1 miles, right? Because really, if you can't run a half marathon at that pace you have no shot at holding it for a full marathon.
And this is what makes me so nervous.
What if the pace I've had in mind for months turns out to be totally unrealistic? What if I totally bomb this run? How will I ever mentally recover for the marathon?
I ran a strong spec test run before the Modesto Marathon earlier this year and I credit that workout for giving me the confidence to know I had a good marathon time in me. I needed this same boost for Two Cities. I've struggled a little more on the harder long runs this training cycle that called for extended miles at MP+10 or MP+20. I needed a run to tell me that I wasn't way in over my head.
This training cycle, the 13.1 spec test ended up falling the week after the Air Force Marathon. This was the main reason I quibbled over participating. In the end, the draw of honoring my dad won and I decided I would make this work. My fifteen day running streak taught me that my body can recover without true recovery and that I could still hit hard paces. Surely if I could do all that, I could run an easy marathon sandwiched by rest days and get back into my training plan.
I took Sunday, the day after Air Force, off from running (also a travel day to get back home). I could tell I had run long the day before when I walked down or up stairs, but just regular walking -- I was totally pain free. I figured this was a good sign and was proud I had kept the effort easy during the race. Monday I ran 12 miles, Tuesday 8 miles, Wednesday 4 miles with some fartlek work. Thursday I took a true rest day. I went to Bikram yoga Wednesday night after work instead of my usual Thursday night class. I was going to give my body every advantage I could to get my Friday run done right.
I got an early start Friday and after a two mile warm up, I reset Garfield and started my half marathon. For Modesto, I was able to schedule the spec test to fall during an actual half which was really awesome. One, you have that race atmosphere to give you that extra edge. And two, you can earn yourself a bona fide PR. I haven't truly raced a half marathon since 2009 so my half PR is definitely outdated. I earned a PR during my Modesto spec test, but it wasn't a true half effort. If things went right, I knew I should be beating my PR during this run.
I don't think I've mentioned it before, but my goal pace for Two Cities is something in the 8:20's. I've been using 8:20 as my rough marker for MP+X runs. I decided I wanted to keep my pace today in the 8:20-8:25 range.
The miles started ticking away and I felt good. For me, a good marathon goal pace is a pace that isn't always easy but isn't always hard. I figure if you're racing and pushing yourself it should be a little tough, but at the same time if you want to run 26.2 miles at that pace it can't be that rough every single step. This easy/hard thing can flip rather quickly. I can have a tenth of a mile stretch where I'm cruising along feeling like I could run forever at that pace, and the next tenth of a mile I'm suddenly digging deeper to keep on track. But so long as it keeps flipping back and forth I'm comfortable saying I'm in the right zone.
The last few miles I felt good and allowed myself to dig a little deeper than my goal pace. My Modesto spec test ended up being faster than my goal pace which gave me a good mental boost. Since I felt good I decided to try to bring it down below goal pace to allow myself that advantage again. I kept the pace strong, but wasn't pushing my limits.
I have no clue what half marathon times equal what paces below 1:59 (9:09 = sub-two is forever ingrained in me). I knew I'd be faster than 1:52 (my Modesto spec test time), but I figured it would be 1:51 or so. I stopped Garfield at 13.1 miles, switched over to the time screen, and saw this:
1:47:53
I couldn't believe it. My eyes welled up at the idea that I had gone sub-1:50 and was running at marathon effort for the majority of the run. I was so proud I was able to do this less than a week after running a marathon. I've made breaking 1:45 in the half a goal for next year, and it seemed a little ludicrous until this run.
I stood there on the Great Highway totally in awe of what you can accomplish with some dedication and training.
Could I have run this pace (8:14) for another 13.1 miles? Probably not. But you know, it makes running 8:25 or so for 26.2 much more palatable. And that was the whole point of this workout. The spec test 13.1 mile stretch of marathon pace is the longest continuous mileage I do at marathon pace in my training plan. I'm sure there are lots of physical benefits, but for me the mental benefit of pulling this off is where the money is at. So my Air Force Marathon gamble ended up playing out swimmingly. Just a smidgen over a month to go...
Friday, September 28, 2012
Friday, September 21, 2012
Air Force Marathon
The Mario Recap, Marathon #35:
Great race. So glad I went. This is going to sound totally strange, but this race reminded me a lot of the Disney Marathon. Except... Well, red-white-and-blue and airplane themed instead of cartoons and a mouse.
The Full Recap, Marathon #35:
I left my hotel 1.5 hours before the gun time. I had read there had been some parking traffic issues the year before and the race was recommending arriving that amount of time early. Parking was very quick and efficient and with over an hour to go before the race I found myself parked in a huge field in the dark.
Race day temps were forecast to be in the high 70's. I knew the low was going to be 49 but somehow that didn't translate into my skull that it would actually be chilly at the start. Last minute I threw a garbage bag into my backpack when I left home as a wimpy cover-up but I didn't pack any truly warm throwaway items. I was reluctant to leave my warm rental car (hello, seat warmers!) armed with only a little garbage bag to ward off the cold. So I decided to wait until half an hour 'til the start to leave my car.
I didn't take into account that I was parked at the outskirts of a huge field. And this huge field was a bit of a walk to the Air Force Museum. And the start was actually a bit of walk on the other side of said museum. When I finally left my car I snapped a photo of a banner they had put out to help me remember where my car was parked. I am pretty bad at remembering what a rental car looks like. I imagined I would be awful at finding a rental car that is parked in a huge field the size of a Disney parking lot. My searching skills would be especially impaired since I parked the car in the dark and would be returning 5+ hours and 26.2 miles later in sunlight.
I joined up with a crowd of people walking. We passed a line of portapotties right by the parking area. The lines there looked to be about 15 minutes long. I remembered reading that there were going to be tons of portapotties at the actual start so opted to keep walking and take my chances at those.
As the long walk continued I started to realize that I was cutting it really, really close to the start. In retrospect the walk from my car to the start was probably over a mile long. I had given myself 30 minutes to walk and use the restroom. Not smart. I silently cursed the seat warmers.
I turned Garfield Garmin on during the walk to let him get a satellite signal. He immediately threw up one of the known glitches I have with my unit. He got stuck on the "Garmin" home screen. From past experience I know that if I continue to turn him on and off or reset him, or possibly plug him into the wall for a second (not an option in a grass field pre-race) he will eventually get with the program. But it often takes many, many resets. I started resetting him and turning him off and on hoping he'd unglitch before the race started.
Right as I was reaching the race area you could hear the National Anthem being sung. I will say, it is only at the Air Force Marathon when you are walking in a crowd of runners trying to get to a race that people will actually stop moving and stand still to hear this song. Once it was over, I put my walk into high gear to find the portapotties.
I stumbled upon the most beautiful sight: Two long rows of portapotties, each over a tenth of a mile long with absolutely NO lines. I guess I was the only one running late. I hopped into one quickly. As I was in there, I heard the announcer say that the flyover was about to happen. Every year the race picks an aircraft to highlight on the medal and they have a flyover by that aircraft at the start. I raced out of the portapotty in time to catch the B-2 flyover:
I heard men talking about how this gave them chills. None of that for me, but it was sort of cool. The B-2 is a stealth bomber whose primary function, according to its write-up is, "Multi-role heavy bomber." Definitely don't want to see one of those flying over me ever again.
Hightailed it from there over to the start area and joined up with the crowd to cross the start line. I literally got there right in time to not start at the very back of the pack. Garfield was still being a putz and I resigned myself to possibly not having him for the race.
My only goal for this race was to finish in a way which allowed me to reenter my training plan the week after. I was thinking I'd probably finish around a 4:20 (got a 4:21 with a portapotty break so pretty spot on there). I consider one of my greatest strengths as a runner the fact that I can run easy when I decide that running easy is the agenda for the day. I dialed in "easy long run pace" and went with it.
About half a mile or so into the race Garfield came back to life! I decided to turn him on at the mile 1 marker so that he would be beeping at appropriate intervals the rest of the race.
The race starts with a nice little climb which has the added benefit of separating out the different paces a little quicker. If you recall, I was originally going to run Air Force as my A-race of the year. I read lots of conflicting opinions about whether the course was fast or hilly. Hills are all relative but here is my take: I would not describe this sucker as flat and fast. It is overall fairly fast but there is a nice climb in the beginning and that climb at mile 21 is MUCH bigger than it looks when you're on the 21st mile of the day. There are also little rollers that don't register on the elevation chart. However, since I train on lots of hills it wasn't too terrible. If you're going to race this one, definitely do some hill training. It isn't a terribly difficult course, though, and I can definitely see how people think it is PR-friendly. At the end of the day, I think my new A-race (Two Cities) is a faster course.
I carried my camera during the race but took a dismal amount of photos. This is partly because I was having a good time soaking up the experience and partly because I wanted to keep moving. So I don't have tons of photos to share. But really, if you've see one Air Force base, you've seen them all.
I was really surprised at all the bands they had out on the course. Most of the race is run on an active military base so crowd support is minimal. I thought the bands came at nice intervals. Band support seemed to peter out a little in the latter miles, and this would be my main suggestion to the race to liven things up.
There was one small loopy-out-and-back section of the race around mile 10. This part of the race is off-base and has an enormous amount of crowd support. It totally reminded me of running through the Magic Kingdom at Disney. As I entered the area the 3:45 pace group was just leaving and I thought about how I'd like to be running with them at Two Cities. They had two bands in the area. One was an accordion group and the other was what I can only describe as Hoedown music. The stuff they were playing was so idyllic small-town USA. We ran through a residential street that had red, white, and blue streamers hanging from all the trees. It was incredibly cute and a great pick-up. I could have run that 1+ mile loop over and over and been totally thrilled. I suppose that is why it reminded me of running through the Magic Kingdom at Disney because I always think that when I am there, too.
Like Disney, Air Force had some of the best volunteers and amazingly frequent aid stations. I ran with just a 6 oz water bottle. For goal races I do tons of reconnaissance work pre-race. I slack a bit on this when I'm running for fun and had no clue how often the aid stations were. I assumed they would be about 2 miles apart so started drinking water at the very beginning since I knew it was going to warm up and I wasn't carrying much on me. Surprisingly, they had aid stations almost every mile. I had to start skipping some of them. They had themed aid stations. I shot this in the luau-themed station:
Great race. So glad I went. This is going to sound totally strange, but this race reminded me a lot of the Disney Marathon. Except... Well, red-white-and-blue and airplane themed instead of cartoons and a mouse.
 |
| Who plunked this metal thing on my new shreddy paper toy?! |
The Full Recap, Marathon #35:
I left my hotel 1.5 hours before the gun time. I had read there had been some parking traffic issues the year before and the race was recommending arriving that amount of time early. Parking was very quick and efficient and with over an hour to go before the race I found myself parked in a huge field in the dark.
Race day temps were forecast to be in the high 70's. I knew the low was going to be 49 but somehow that didn't translate into my skull that it would actually be chilly at the start. Last minute I threw a garbage bag into my backpack when I left home as a wimpy cover-up but I didn't pack any truly warm throwaway items. I was reluctant to leave my warm rental car (hello, seat warmers!) armed with only a little garbage bag to ward off the cold. So I decided to wait until half an hour 'til the start to leave my car.
I didn't take into account that I was parked at the outskirts of a huge field. And this huge field was a bit of a walk to the Air Force Museum. And the start was actually a bit of walk on the other side of said museum. When I finally left my car I snapped a photo of a banner they had put out to help me remember where my car was parked. I am pretty bad at remembering what a rental car looks like. I imagined I would be awful at finding a rental car that is parked in a huge field the size of a Disney parking lot. My searching skills would be especially impaired since I parked the car in the dark and would be returning 5+ hours and 26.2 miles later in sunlight.
 |
| I took this as a visual reminder of where I was parked. Good thing they had them because if you had asked me where I had parked my car when I returned I would have told you a totally different area of the giant field. |
I joined up with a crowd of people walking. We passed a line of portapotties right by the parking area. The lines there looked to be about 15 minutes long. I remembered reading that there were going to be tons of portapotties at the actual start so opted to keep walking and take my chances at those.
As the long walk continued I started to realize that I was cutting it really, really close to the start. In retrospect the walk from my car to the start was probably over a mile long. I had given myself 30 minutes to walk and use the restroom. Not smart. I silently cursed the seat warmers.
 |
| The scene on the way towards the start. That's actually mist on the field. Yes, it was chilly. |
I turned Garfield Garmin on during the walk to let him get a satellite signal. He immediately threw up one of the known glitches I have with my unit. He got stuck on the "Garmin" home screen. From past experience I know that if I continue to turn him on and off or reset him, or possibly plug him into the wall for a second (not an option in a grass field pre-race) he will eventually get with the program. But it often takes many, many resets. I started resetting him and turning him off and on hoping he'd unglitch before the race started.
Right as I was reaching the race area you could hear the National Anthem being sung. I will say, it is only at the Air Force Marathon when you are walking in a crowd of runners trying to get to a race that people will actually stop moving and stand still to hear this song. Once it was over, I put my walk into high gear to find the portapotties.
I stumbled upon the most beautiful sight: Two long rows of portapotties, each over a tenth of a mile long with absolutely NO lines. I guess I was the only one running late. I hopped into one quickly. As I was in there, I heard the announcer say that the flyover was about to happen. Every year the race picks an aircraft to highlight on the medal and they have a flyover by that aircraft at the start. I raced out of the portapotty in time to catch the B-2 flyover:
I heard men talking about how this gave them chills. None of that for me, but it was sort of cool. The B-2 is a stealth bomber whose primary function, according to its write-up is, "Multi-role heavy bomber." Definitely don't want to see one of those flying over me ever again.
Hightailed it from there over to the start area and joined up with the crowd to cross the start line. I literally got there right in time to not start at the very back of the pack. Garfield was still being a putz and I resigned myself to possibly not having him for the race.
My only goal for this race was to finish in a way which allowed me to reenter my training plan the week after. I was thinking I'd probably finish around a 4:20 (got a 4:21 with a portapotty break so pretty spot on there). I consider one of my greatest strengths as a runner the fact that I can run easy when I decide that running easy is the agenda for the day. I dialed in "easy long run pace" and went with it.
About half a mile or so into the race Garfield came back to life! I decided to turn him on at the mile 1 marker so that he would be beeping at appropriate intervals the rest of the race.
The race starts with a nice little climb which has the added benefit of separating out the different paces a little quicker. If you recall, I was originally going to run Air Force as my A-race of the year. I read lots of conflicting opinions about whether the course was fast or hilly. Hills are all relative but here is my take: I would not describe this sucker as flat and fast. It is overall fairly fast but there is a nice climb in the beginning and that climb at mile 21 is MUCH bigger than it looks when you're on the 21st mile of the day. There are also little rollers that don't register on the elevation chart. However, since I train on lots of hills it wasn't too terrible. If you're going to race this one, definitely do some hill training. It isn't a terribly difficult course, though, and I can definitely see how people think it is PR-friendly. At the end of the day, I think my new A-race (Two Cities) is a faster course.
I carried my camera during the race but took a dismal amount of photos. This is partly because I was having a good time soaking up the experience and partly because I wanted to keep moving. So I don't have tons of photos to share. But really, if you've see one Air Force base, you've seen them all.
I was really surprised at all the bands they had out on the course. Most of the race is run on an active military base so crowd support is minimal. I thought the bands came at nice intervals. Band support seemed to peter out a little in the latter miles, and this would be my main suggestion to the race to liven things up.
There was one small loopy-out-and-back section of the race around mile 10. This part of the race is off-base and has an enormous amount of crowd support. It totally reminded me of running through the Magic Kingdom at Disney. As I entered the area the 3:45 pace group was just leaving and I thought about how I'd like to be running with them at Two Cities. They had two bands in the area. One was an accordion group and the other was what I can only describe as Hoedown music. The stuff they were playing was so idyllic small-town USA. We ran through a residential street that had red, white, and blue streamers hanging from all the trees. It was incredibly cute and a great pick-up. I could have run that 1+ mile loop over and over and been totally thrilled. I suppose that is why it reminded me of running through the Magic Kingdom at Disney because I always think that when I am there, too.
Like Disney, Air Force had some of the best volunteers and amazingly frequent aid stations. I ran with just a 6 oz water bottle. For goal races I do tons of reconnaissance work pre-race. I slack a bit on this when I'm running for fun and had no clue how often the aid stations were. I assumed they would be about 2 miles apart so started drinking water at the very beginning since I knew it was going to warm up and I wasn't carrying much on me. Surprisingly, they had aid stations almost every mile. I had to start skipping some of them. They had themed aid stations. I shot this in the luau-themed station:
 |
| So, so clever. If I ever run an aid station I am doing this! |
My personal favorite aid station was at mile 18. They had a guy dressed as Elvis talking on a microphone saying, "Welcome to Aid Station 'O,' your rock 'n roll water hole! We have water on the right and Gatorade on your left. If you need anything at all please let us know!" over and over as new people came through.
I started feeling good around the half and my pace quickened a little. I was tempted to see how fast I could go at an "easy effort" pace. But I reminded myself there was no glory in running faster at what was supposed to be a training run and slowed myself down.
Unbeknownst to me at the time, we ran by Huffman Prairie Flying Field where the Wright brothers flew their aircraft. I would have snapped a photo of the recreated Wright brother hangar but had no idea what I was looking at during the race (I didn't go to the Air Force Museum until after the race).
Not all the race was hum-drum military base roads. We were on a nicely shaded path for a bit which was a nice respite from the sun. Things stopped being chilly about an hour into the race. Things started feeling warm at about the half mark. Luckily things didn't get hot until the last few miles. I really thought the weather was going to be a bigger factor so that worked out nicely.
Running on a military base is a lot like running backstage at Disney or on the roads between theme-parks. The signage is sort of the same. There aren't a lot of people. It was a really, really odd parallel. At one point some people were cheering on the outside of the barbed wire fence. Now that is something I hadn't seen at a race yet.
We hit mile 20 and I thought about how that was all the miles that my training plan called for this day. "If I were home, I could stop right now," I thought. "If I could stop right now, I actually still feel pretty good," was my next thought. I had gone in with the strategy of running my easy long run pace the first 20 miles and taking occasional walk breaks the last 6.2 if needed. I even told myself I could do some walking up that monster hill. But I got to the hill and decided to just keep trucking. In the end I walked through aid stations but just kept plugging away the rest of the time.
The full merged with half marathon walkers in the latter miles which caused a bit of weaving and dodging. You can tell who the half marathon walkers are from dejected full marathon walkers from the back. I have to say, I was passing a lot of marathoners at the end of this race. That was a little surprising. The heat, maybe? The hill? Who knows.
I want to mention something I found really odd here, and if anyone has an explanation, please share. The entire race, my Garmin was remarkably spot-on with the mile makers. I was never more than 20 or so feet from one when it would beep. I took a quick portapotty stop at one aid station which added a little distance onto my day, but even then my Garmin was synced up with the mile markers pretty well all the way up until mile 25. I was amazed. The last "1.2 miles" was measured as 1.4 miles by Garfield. I thought perhaps mile 1 had been "long" and I had missed measuring that mile, but everyone else's Garmin seemed to beep when mine did throughout the race so I don't think this was the case. I do think 26.4 miles measured by your Garmin is totally within reason of what a 26.2 mile course yields. However, I found it totally insane that an entire "extra" 0.2 miles got added on in that final mile. I'm just putting this out there in case anyone plans on racing this sucker. You will end up with a "long" reading so adjust your pace accordingly.
I passed a woman holding a sign I loved but have never seen at a race before. It said: "26.2 puts the F-U in Fun!" Ha ha.
I got my medal from an USAF officer (Looks like a Colonel? I'd say the guy to the right is a two-star General. Maybe that is why his line was longer).
I collected some food and had a seat on the grass and downed my (in retrospect, sadly small) pizza, a banana, a bottle of Gatorade and half a bottle of water. Then I started my loooong walk back to the car.
The swag was plentiful but does not live up to my XS women's specific shirt standard.
This race meant something to me since my father is retired from the USAF. There was a snafu on the half marathon course, but the full marathon was very well organized. The aid stations were plentiful and the volunteers were awesome. Crowd support is nothing like NYC but it was decent and the volunteers every mile or so cheer for you loudly. I would definitely recommend this race. I have to give props to the state of Ohio. I never thought I'd run one, let alone two (Akron) Ohio marathons in my life. And both of them have been surprising standout favorites in my marathon history.
I'm very happy I decided to make the trip out to Ohio and to make some allowances in my training plan so that I could participate. I wore a photo on my back of my dad in his dress uniform with me when I was a kid and am planning on giving him the picture and my medal later.
 |
| Sweet shade! |
Running on a military base is a lot like running backstage at Disney or on the roads between theme-parks. The signage is sort of the same. There aren't a lot of people. It was a really, really odd parallel. At one point some people were cheering on the outside of the barbed wire fence. Now that is something I hadn't seen at a race yet.
We hit mile 20 and I thought about how that was all the miles that my training plan called for this day. "If I were home, I could stop right now," I thought. "If I could stop right now, I actually still feel pretty good," was my next thought. I had gone in with the strategy of running my easy long run pace the first 20 miles and taking occasional walk breaks the last 6.2 if needed. I even told myself I could do some walking up that monster hill. But I got to the hill and decided to just keep trucking. In the end I walked through aid stations but just kept plugging away the rest of the time.
The full merged with half marathon walkers in the latter miles which caused a bit of weaving and dodging. You can tell who the half marathon walkers are from dejected full marathon walkers from the back. I have to say, I was passing a lot of marathoners at the end of this race. That was a little surprising. The heat, maybe? The hill? Who knows.
 |
| Coming towards the finish area. That is the museum straight ahead and the planes to the right mark the home stretch. |
I want to mention something I found really odd here, and if anyone has an explanation, please share. The entire race, my Garmin was remarkably spot-on with the mile makers. I was never more than 20 or so feet from one when it would beep. I took a quick portapotty stop at one aid station which added a little distance onto my day, but even then my Garmin was synced up with the mile markers pretty well all the way up until mile 25. I was amazed. The last "1.2 miles" was measured as 1.4 miles by Garfield. I thought perhaps mile 1 had been "long" and I had missed measuring that mile, but everyone else's Garmin seemed to beep when mine did throughout the race so I don't think this was the case. I do think 26.4 miles measured by your Garmin is totally within reason of what a 26.2 mile course yields. However, I found it totally insane that an entire "extra" 0.2 miles got added on in that final mile. I'm just putting this out there in case anyone plans on racing this sucker. You will end up with a "long" reading so adjust your pace accordingly.
I passed a woman holding a sign I loved but have never seen at a race before. It said: "26.2 puts the F-U in Fun!" Ha ha.
 |
| Towards the finish. That wing we are about to run under belongs to the plane that brought the POWs home from Vietnam (lots of cool plane shots to come!) |
I got my medal from an USAF officer (Looks like a Colonel? I'd say the guy to the right is a two-star General. Maybe that is why his line was longer).
 |
| The officer that gave me my medal. My dad went to work every day in a uniform that looked just like this. |
 |
| Get in my belly! |
I collected some food and had a seat on the grass and downed my (in retrospect, sadly small) pizza, a banana, a bottle of Gatorade and half a bottle of water. Then I started my loooong walk back to the car.
The swag was plentiful but does not live up to my XS women's specific shirt standard.
 |
| Decent shirt, but it doesn't fit, so big deal. |
 |
| I love the medal. Two-sided, heavy, all the pertinent information, and a pretty ribbon. Definitely one of my favorite medals. |
 |
I'm very happy I decided to make the trip out to Ohio and to make some allowances in my training plan so that I could participate. I wore a photo on my back of my dad in his dress uniform with me when I was a kid and am planning on giving him the picture and my medal later.
Tuesday, September 11, 2012
Feel Lucky
The other week Boyfriend and I suffered through watching "What's Your Number." It was a highly craptastic movie I recommend staying far, far away from if you want to keep your brain cells intact.
It wasn't a total waste of my life, though, because I heard a song during the movie which I tracked down.
There is that question that hangs over every runner, usually posed by non-runners: Why do you run?
I can never really put it into words, but this song summed up the best answer I have ever heard and describes exactly the way I feel when I'm running:
"I feel lucky, I feel free, I feel everything's a possibility. I feel lovely, I feel me, I feel everything I see is differently."
It wasn't a total waste of my life, though, because I heard a song during the movie which I tracked down.
There is that question that hangs over every runner, usually posed by non-runners: Why do you run?
I can never really put it into words, but this song summed up the best answer I have ever heard and describes exactly the way I feel when I'm running:
"I feel lucky, I feel free, I feel everything's a possibility. I feel lovely, I feel me, I feel everything I see is differently."
I've added the song to my regular rotation and usually play it at the end of my runs. It makes me happy and always lifts my spirits. If the run went well it puts a zip in my step. If the run has been hard or hasn't gone the way I hoped it reminds me what the important things in my running life are all about.
August closed out with another monthly mileage PR of 253 miles. I don't think I'll beat that mark again this training cycle and I'm definitely fine with that. My long runs are about to get more challenging, but I feel like I've already gotten over the hardest weeks in my training plan.
I will be running my 35th marathon this Saturday. I waffled quite a bit about whether or not I wanted to participate in the Air Force Marathon this year. I signed up on January 1st and was originally planning for it to be my A-race of the year. My legs felt like they needed some extra time to get back into real training early this summer so I made the decision to target Two Cities instead and either run Air Force as a training run or possibly scrap it all together.
There were a lot of factors I was considering when I decided to run Air Force. The main reason my heart wasn't into it was that I have a very key long run workout to do the week after and I wasn't sure if I would be properly recovered in time. I've done lots of these 26.2 mile "training runs" before, but I've decided they take more out of me than I'd like to think and they always seem to disrupt my training flow a little.
In the end I decided to just go for it for three main reasons: 1) I've always intended to run this for my dad who is retired USAF. This is the main reason I'm still going to run it this year. If it were any other race I'd definitely bow out. 2) When I bought my plane ticket and committed to seeing this through I was feeling a little burnt out by all the miles. I've gotten over this hurdle already but I thought the trip and subsequent break from the training plan would be a nice mental boost. 3) I have goals for Two Cities but no live-or-die hard ones to really pinpoint. I feel like my main goal I'll still be able to reach even if this race takes more out of me than I'd like or if that key long run doesn't go so swell. My super reach goal may be jeopardized, but it isn't so crucial this go-around.
That said, I'm taking Air Force easy and am hoping to seamlessly reenter my plan after. This week I'm supposed to run 20 miles Friday, 5 miles Saturday, and 10+ miles with speed work Sunday. I'm swapping all of these runs out for 26.2 easy. Sounds like a fair swap, right? I'm hoping so. I haven't gone farther than 18 miles in one go since the end of May so we'll see how I fair. But I've been maintaining weekly mileage for months now that exceeds what my peak mileage used to be a year ago for marathons so I'm hoping that will translate over a bit.
I'm still debating whether I want to just run the whole thing easy or perhaps force myself to take walk breaks every mile from the very beginning. I'm not entirely sure which would take less out of me. The weather is looking sort of crummy (thank goodness it isn't an A-race) so hopefully I won't be out there too long.
I've heard rave reviews about this race and am definitely excited to see what it is all about. I'm looking forward to the race vibe and using it as a nice reward for all my hard work thus far. See you on the flip side!
August closed out with another monthly mileage PR of 253 miles. I don't think I'll beat that mark again this training cycle and I'm definitely fine with that. My long runs are about to get more challenging, but I feel like I've already gotten over the hardest weeks in my training plan.
I will be running my 35th marathon this Saturday. I waffled quite a bit about whether or not I wanted to participate in the Air Force Marathon this year. I signed up on January 1st and was originally planning for it to be my A-race of the year. My legs felt like they needed some extra time to get back into real training early this summer so I made the decision to target Two Cities instead and either run Air Force as a training run or possibly scrap it all together.
There were a lot of factors I was considering when I decided to run Air Force. The main reason my heart wasn't into it was that I have a very key long run workout to do the week after and I wasn't sure if I would be properly recovered in time. I've done lots of these 26.2 mile "training runs" before, but I've decided they take more out of me than I'd like to think and they always seem to disrupt my training flow a little.
In the end I decided to just go for it for three main reasons: 1) I've always intended to run this for my dad who is retired USAF. This is the main reason I'm still going to run it this year. If it were any other race I'd definitely bow out. 2) When I bought my plane ticket and committed to seeing this through I was feeling a little burnt out by all the miles. I've gotten over this hurdle already but I thought the trip and subsequent break from the training plan would be a nice mental boost. 3) I have goals for Two Cities but no live-or-die hard ones to really pinpoint. I feel like my main goal I'll still be able to reach even if this race takes more out of me than I'd like or if that key long run doesn't go so swell. My super reach goal may be jeopardized, but it isn't so crucial this go-around.
That said, I'm taking Air Force easy and am hoping to seamlessly reenter my plan after. This week I'm supposed to run 20 miles Friday, 5 miles Saturday, and 10+ miles with speed work Sunday. I'm swapping all of these runs out for 26.2 easy. Sounds like a fair swap, right? I'm hoping so. I haven't gone farther than 18 miles in one go since the end of May so we'll see how I fair. But I've been maintaining weekly mileage for months now that exceeds what my peak mileage used to be a year ago for marathons so I'm hoping that will translate over a bit.
I'm still debating whether I want to just run the whole thing easy or perhaps force myself to take walk breaks every mile from the very beginning. I'm not entirely sure which would take less out of me. The weather is looking sort of crummy (thank goodness it isn't an A-race) so hopefully I won't be out there too long.
I've heard rave reviews about this race and am definitely excited to see what it is all about. I'm looking forward to the race vibe and using it as a nice reward for all my hard work thus far. See you on the flip side!
Monday, September 10, 2012
Monday, September 3, 2012
Monday Mario
I almost forgot it was Monday today. Blast from the past:
My parents actually have this photo framed in their house. I may or may not be guilty of taking it into my room and puttting it by my bed when I'm home visiting. Such a dapper fellow.
 |
| c. 2005 |
Subscribe to:
Posts (Atom)
