Training for the Columbus Half Marathon begins for me today. The race is in 110 days, or three months and 18 days. Or in 16 weeks. Any way you look at it, it’s time to get out and start training.
But apparently not at 5:30 this morning.
When I looked at the weather last night, the AccuWeather app informed me that heavy storms would move through the area in the afternoon today. So I set my alarm for 5:00am as my husband’s 24-hour shift day falls today. I needed to run three miles before he left for work. The alarm went off, I rolled around and tried to go back to sleep, and eventually rolled myself out of bed.
Only to hear thunder.
I opened the app, looked at the radar, and sighed. I walked to the window to watch as Mother Nature treated me to quite the light show in the form of constant, crazy lightning. I got back in bed and waited for it to pass, which didn’t happen until my husband left for work. Figures. I now need to text our teenage babysitter to see if she’ll come “watch” the boys after they go to bed so I can run three miles in the neighborhood in the not-sweltering-midday-heat. I also hate running more than one mile back and forth on our half block like I do sometimes to get my mile in when my husband is at work; three miles of back and forth would be torturous. Hopefully she’s available, or you can watch me run repeats this evening. Yay?
Not exactly how I imagined my training for this half marathon starting out. Whatever the case, I’ll get my run in at some point in time today.
As far as training plans go, I’m using a simple “beginner’s” training plan offered by RunKeeper as I’m training my husband through his first half marathon. Yes, he’s officially registered. Yes, we’re running the whole thing together. Yes, it will be the most awesome thing since sliced (rye!) bread. He started running with me every now and then after the Pittsburgh Marathon, and even ran two days with me during our beach vacation.
While our training plan doesn’t offer anything in the way of speedwork, I know we both have a goal in mind. I’d like to shave a few minutes off of my PR, set at Columbus last October. Then again, I shaved 9 minutes off at Columbus last year, and if I manage to do that this year, well, I’d be shocked and thrilled. I’ll talk more about our time goal after we get through the sweltering summer running season. Running in this heat does slow your pace, so I’m not going to fret too much if I’m not hitting my pace goals on my runs until the temps drop a little… or a lot.
And now let’s talk about running in June a little bit, shall we?
As you know, I’ve been participating in the Runner’s World Summer RunStreak. It’s almost over, ending on the 4th of July. (Of course, my training plan has me running on the 5th and 6th, so I’ll have 42 straight days of running, not just 40!) That means I ran every single day in June.
Every. Single. Day.
Even when my grandmother passed away. Even on vacation. Even when I didn’t want to run.
When I finished up my 2.5 mile run yesterday morning and looked at my mileage in comparison to May, I laughed out loud. What’s the difference between 78.7 miles (May) and 52.5 miles (June)? Oh, you know. Just 26.2 miles. Or a marathon.
So the difference in mileage between May and June was that little, itty-bitty Pittsburgh Marathon that I ran. Oh. And pace? My pace average in May was nearly 11 minutes because of the marathon. In June? 9:37. Yes! As you can tell, I spent a lot of June focusing on pace and speeding up. In order to do that at all in July, I’m going to have to continue waking up early—and pray the thunderstorms cooperate.
Here’s to the Columbus Half, to the end of the RunStreak, and to running with my husband! Let’s go, July!