This was my second time running downtown San Diego’s 10K Turkey Trot. The 2011 race was my second race ever, and I finished in 45:25 (7:19 average pace). This year, I beat my 2011 time by 6 minutes because I trained like a MOFO in 2012!
My strategy going into the race was to run it as a tempo run at 6:50, and I was convinced that I wouldn’t be able to do it. My legs were extremely tender. Not just sore/stiff. But aching and angry from last week’s 38 miles and this week’s leg workout and speed session. I didn’t sleep well Wednesday night because I kept waking myself up by flexing my leg muscles as hard as I could. It wasn’t quite a cramp because once I was awake, I could stop contracting the muscles. (And now it’s continued for a second night in a row. It’s official, the legs have revolted.)
The pre-race logistics were a breeze. Races downtown are easy because there is plenty of parking and no traffic bottlenecks. The race’s start was at scenic Horton Plaza. It was a little bit cramped picking up the bib, shirt, and race packet. But this is barely worth mentioning. Importantly, there were plenty of porta-potties and no lines. Weather was nice. The sun was only out for the last few minutes of my race, and the temperature was about 60-65. I raced in tights and a long sleeve shirt because, despite my Norwegian ancestry, I am a complete wuss when it comes to cold. (And heat for that matter. I’ve “gone native” living in San Diego for 6 years and am only comfortable when the temperature is 70-73.) But most of the gals were in shorts and tanks.
I “decided” not to use my Garmin for this race when the watch had not acquired satellites by the countdown to the start (after searching for over 10 minutes). I was also not able to start my RunKeeper app in time because there was only a 10 second warning that we were going to start! (Yes, I use a GPS watch and a running app on my phone. In fact, I own two GPS watches if you must know.)
So I timed my race the old fashioned way, using the stop watch feature of the Garmin. I’ve never done it this way before. But the race had markers at each mile interval, which in my experience is pretty rare for a 10K/5K race. It wouldn't have mattered if those markers were not there because I always knew where the miles were based on the familiar Garmin mile beeps of the runners who somehow were able to pick up a signal.
In a third technology fail of the day, my chip did not work. The timing guys said they had to look for "backup data" to get my time.
My mile splits that I can remember looked something like this:
1.0 – 6:08
Holy crapoly, this is going to cost me.
2.0 – 12:30
When is the other shoe going to drop?
3.0 – 19:11
Ahead of anticipated pace by 100 seconds.
4.0 – 25:40
When am I going to experience that tough race moment where I have to choose whether to push on or pull back? (I never did.)
And I crossed the finish line at 39:24 (6:20 average pace).
Ummm, how was this possible?
Answer 1: The course was short. By about 0.2, according the GPS watch-wearing runners I polled. This is a pretty big fail for a race director in my book. So let’s call it a 6 miler, which makes my average pace more accurately 6:33. Still a massive PR over my next best 10K average pace (7:06).
Answer 2: Without GPS, I could not check in on my pace, which I normally do (i) every time I pass another runner, (ii) every time I get passed, (iii) every mile, (iv) every time my effort feels hard, and (v) every time my effort feels easy. So I was not making judgments about how I felt at particular pace moments in the race. I was running by feel because I could only calculate split times a few times during the entire race. I ended up surprising myself with my pace. Not sure I would have run this fast had I been able to use my watch. But I am not giving up GPS technology just yet. I’ve learned from this race to keep an open mind about how easy a fast pace might feel.
two little runners (Kristen)