Showing posts with label VA Run Turkey Trot. Show all posts
Showing posts with label VA Run Turkey Trot. Show all posts

Saturday, November 25, 2023

Turkey Trot- I Winged It!

I did not have any goals or this year's Turkey Trot due to its proximity to the Richmond Marathon, just 12 days prior. I knew that I would still have my marathon fitness, but my legs were still recovering.

I took 8 days off after the marathon and resumed the Monday before Thanksgiving, with a very short run of only 15 minutes. In addition to recovering from the marathon, I had caught a cold two days post race. By Monday it had been a full week since I got sick and I had all of my energy back. The congestion lingered, however. I ran short and easy runs on Tuesday and Wednesday and both of those runs confirmed that my legs were still in recovery mode.

My plan for the race was to "wing it" with no goals or pacing strategy. I had run this course 13 times in the past, so I knew what I was getting myself into. This is NOT the course I ran last year that holds my 19:41 PR. It is the course where I ran my first sub-20:00 back in 2018. The elevation profile is gently rolling hills with a larger hill at around the halfway point. 

I had not run this course since 2018 because they did not hold the race in 2019, 202, or 2021. It came back in 2022 but I was not aware of it. Instead I ran a different Turkey Trot.

Before the Race
I had a super casual attitude about this race, which meant I didn't have my normal digestive system clean-out when I woke up. I ate half of a Maurten solid and drank some water, and that got things going a bit!

The weather gets a 9 out of 10 on my personal weather scale. It was 43 degrees, mostly sunny with 8-9 mph winds. It would have been a 10 out of 10 without the wind. I wore fitted shorts, a tank top, arm sleeves, sunglasses and lightweight gloves. I wore the Saucony Endorphin Pro 2 shoes, which makes this my very first time ever racing in Saucony. I had run a few speedy workouts in them during training, and my adidas Adios Pro shoes remained too big, so Saucony it was!

I met up with my friend Meredith at the start line 30 minutes before race start. We warmed up with another friend, Nancy for nearly two miles. I had a caffeinated Maurten gel 15 minutes prior to race start. I didn't have the chance to use the porta potty, but that ended up being ok.

Greg, who is still recovering from his injury, moved to his cheering spot during our warm up. I would see him twice during the race. 

Mile 1
I didn't want to limit myself by looking at my Garmin, so I decided I would only look at it when it beeped for each mile split. After the first few minutes of runners getting out on the course, I settled into a groove. Meredith was in my sights and I figured I would roughly pace off of her. The first mile is gently rolling hills with a net uphill. I saw Greg about 2/3 the way into mile 1. Things felt hard, but I didn't feel like I was running at 5K effort; it felt more like 10K effort during the first mile. The Garmin clocked me in at 6:43. I would have guessed something closer to 7:00, especially since it felt like 10K effort, so I was happy with that.

Mile 2
The first mile has no turns; it's a straight road. The first turn is around mile 1.3. At the turn I found myself closing in on Meredith. This was not intentional, but I was simply "rolling with it" and that's where I found myself. Not that I am usually super-focused on my watch, but the fact that I didn't look at my watch at all allowed me to really be present and focus on my surroundings and effort level. 

The big hill came and it was not as steep as I had remembered it. The hills in the first mile were steeper than I had remembered, but this one seemed more tame. I caught up with Meredith and ran with her for about a minute. Then I started to really open it up on the downhill and told myself it was time to hammer it home at 100% effort with whatever my legs had. Mile 2 clocked in at 6:37.

Mile 3
I was pleasantly surprised with my mile 2 split, given that it contains the big hill. I could tell my legs were really starting to hate me. At that point, I realized I could be drawing power from my arms. I
decided to engage them more and really use them to propel me forward. I focused on my arm swing and forward lean. From an energy standpoint, I had plenty of it - the limiting factor was definitely my legs. If I had 4-5 more days to recover from the marathon I probably would have tried for sub 20:00. But the legs were still cranky. 

I was expecting to see Greg as I ran it in, but he was standing much closer to the finish line than expected. At that point I was too focused on sprinting to see him, but he saw me and snapped some photos. Mile 3 clocked in at 6:23.

The finish and beyond
My final kick was a pace of 6:12 for 0.14 miles, make this a Thanksgiving Pie run at 3.14 miles. 

My official time was 20:34, which earned me second place in my age group (out of 76) and 8th overall female (out of 392).

Meredith finished shortly after looking very strong. I had to sit down because that final kick really knocked the wind out of me! My legs were extremely tired and my body was not happy with me for running so hard!

I ran a half-mile cool down just to get some blood flowing to my muscles. Then I chatted with Meredith and her family before heading out. 

Final Thoughts and Key Takeaways
Probably the best takeaway is that I run really well when I have a super casual attitude. I know that I am going to focus and push hard once the race starts, so there is no need to overthink things before hand. I also enjoy running so much more when I am not glancing at my Garmin to monitor my pace. That's necessary at the beginning of a long distance race, but not during a 5K. 

I really had no predictions or expectations for this race. At best, I thought I could break 20:00 if my legs were fully recovered. At worst, I thought I could injure myself and end up walking it in. I had no idea what was going to happen. The fact that I ran so well 12 days post marathon and 10 days post getting a cold says a lot about my fitness!

Most of all, I am always thankful for any year I am healthy enough to run a Turkey Trot.


Thursday, November 22, 2018

I PR'ed My First Masters Race

I really don't like to give away the punchline in the blog post title, but yes, I set a PR in my first race in my 40's.

I ran my 13th consecutive Virginia Run Turkey Trot this morning. I know this course like the back of my hand, and I think that knowing it is the key to running a fast race. The course profile is gently rolling hills, but if you know how to tackle it, it can be faster than many flat courses.

Up until today, I wasn't particularly happy with my fall racing season. The ten-miler I ran in October was well off my goal, and the Richmond half marathon was a struggle. In fact, I hadn't set a PR in any distance since January of this year, when I ran the Houston Half Marathon. Although, in many ways, I consider the Boston Marathon to be my PR because running a 3:26 in intense rain, wind, and cold on a difficult course is definitely a more impressive performance than running a 3:21 on a flat course in ideal conditions.

When the forecast came out for this turkey trot, I was admittedly frustrated. 12-14 mph sustained winds, which meant running directly into the wind for the first half of the race. And at 25 degrees, it would feel biting. As I mentioned in my last blog post, the weather has been my enemy this year. But when I woke up, I was pleasantly surprised that it was 30 degrees! Those 5 degrees of extra warmth meant I could wear a lighter top and be more comfortable. The wind, however, would still be a factor.

I figured I would go for a PR, but not necessarily sub-20. I wasn't going to rule it out, but I have learned that "going for sub-20" puts too much pressure on me, so that wasn't really the goal today. Plus, I am in the midst of marathon training, and ran 79 miles last week. I knew my legs wouldn't be fresh, however I still believed I could PR.

Before the Race
I'm going to include some details here that are mainly for my own benefit, so when I come back and read this post next year, I will know what worked. I had salmon, asparagus, and plain pasta for dinner last night. I ate a turkey/avocado sandwich for lunch and had a cookie for dessert. I slept for about 7 hours, and woke up once for 30 minutes. In the morning, I had an english muffin with peanut butter at 5:45, along with about 8 oz of water.

Since it was going to be a little warmer than forecast, I spent some time figuring out what shirt I would wear and ultimately settled on a t-shirt that was made of slightly thicker material than the standard running t-shirt. It was the Slim Sleeves shirt by rabbit. I likes that the sleeves were tightly fitted and the material seemed to be the right weight.

Greg and I left the house at 7:03 (yes, I remember this) and we arrived at the church parking lot at 7:15. At that point, I drank half a serving of Generation UCAN. We then used the church bathroom (they are always so generous letting us use it) and began the warm up at 7:30. My Garmin shut down and re-started during the warm-up, which was concerning. So I reminded myself that if it did that in the race it was okay. I do not need a functioning Garmin to race a 5K. We warmed up for 17 minutes (2.1 miles) and then I stashed my jacket on a fence near the start line.

We lined up toward the front, since there are always so many kids at the very front that I have to weave through during the first half mile. About 1200 people run this race. It's a neighborhood Turkey Trot, which has been going on for 30 years now. There are typically a lot of fast high school and college students who you wouldn't see at most other local races. We lined up at 7:52 and the time ticked by so slowly. I jogged in place a bit to stay warm. The start was really weird. The announcer gave a speech about the charity and the sponsors, but didn't say "ready set go". Instead, this weird ambulance sounding thing went off (which hadn't been used in any of the previous 12 races) and everyone was confused for a second, but then we were off.

Mile 1
I had a pacing strategy and a mental strategy for this race. I was going to run a strong first mile, but without worrying too much about the pace on my watch. It was an uphill mile directly into the headwind so I focused on relaxing and easing into a rhythm. I wasn't trying to hit any particular pace. My goal was to relax, run strong, not spend too much effort weaving, and get to the first mile marker feeling good. Given that it was somewhat crowded at the beginning, I tried drafting briefly, but people's paces kept changing so there wasn't really a pack to stay behind. Finally, my watch beeped 6:33 for the first mile.

Mile 2
Mentally, I had achieved my first goal, so now the next goal was to continue on in that same fashion, and make it about a quarter mile to the first turn into a neighborhood. I knew once we turned, I would be done with the headwind for good. Sure enough, the turn came, and there was still a bit of a headwind, until we made another turn and the wind was gone. But now it was time for the biggest hill of the race. Every year this hill seems to get less and less steep, which is awesome. I don't even think I slowed down at all on it this year. Possibly because I had a tailwind assisting me. My plan was for this mile to be about 4-5 seconds faster than the first mile, and without really trying to hit a particular pace, I naturally logged 6:26 for mile 2. I noticed that the mile markers were misplaced this year. I auto-lap my Garmin during races so I don't have to worry about it, and it's a good thing too because the markers were misplaced by about a tenth of a mile.

Mile 3
I think this course is mentally easier than a flat out-and-back like the Hains Point courses. If you know the course well, you can break it up into small bits and take them on one at a time. I reached the top of the hill and then focused on really fast turnover to take advantage of the downhill. Now it was time for the quarter-mile stretch that always seems longer than it should to get back out onto the main road. This little portion of the course is uphill and it's annoying because I just want to be back on the main road with the finish line straight ahead. So I told myself to just get through that short part, and then the turn would come. I glanced down at my Garmin as I made the final turn onto the main road with about 0.7 left to go. It read 6:21, so I knew I was executing well, and I could make that last mile sub 6:20, which is what I had planned. I gunned it really, really hard, and logged 6:18 for the final mile.

The Last 0.13
As I approached the finish line, I saw the clock and thought I might be able to squeak under 20. With that in mind I ran as fast as I could, at a pace of 5:35.

After the Race
I finished, and I knew Greg would be a few minutes behind me because he was running it at an easy pace. My watch read 20:01, and I was dying to know if I had officially broken 20, because I always stop my watch a few seconds after crossing. I kept walking until I reached a nearby neighborhood. And then, it was time for. . . ANOTHER WORKOUT! Even though I had just PR'ed my 5K, there was still marathon training to be done! My coach wanted me to recover from the race for about five minutes and then run 4 x 400m with 3-minute recoveries.

Greg knew where I would be and he planned to meet me there with my jacket. So, I started doing these intervals and the first one felt pretty good. I hadn't allowed myself to become stiff, so I ran 1:35 (6:21 pace). The next one came in at 1:33 (6:12 pace), and then I saw Greg on my recovery jog. I ran the third one in 1:30 (6:03 pace) and was really ready to be done at that point. All I could think about was my time and if I had broken 20. I was going to stop out of impatience but I told myself I'd have better Karma if I did the last one. I did so in 1:31, and then my final recovery jog.

There was a line to check the computers for the results. And the computers weren't functioning properly at first. I was in so much suspense. At last, we were able to pull up the results and I found my name and it said 19:58! I screamed! I couldn't believe it. I was sure it would be 20:00 since that's just my luck, but I was elated. I think the people around me thought I was a freak.

I shed a few tears of joy, as this has been a goal of mine for two years and I have worked so hard and run so many 5Ks in pursuit of this goal. And to do it as my first race in my 40's makes it extra special. And to do it during marathon training makes it even more impressive to me! We will have PR cake tomorrow night.

This is a PR by 19 seconds, from my previous best of 20:17, set in May 2017.

I think my key to success today was having a really solid race plan for pacing and for how I would break the race into chunks. And also not pressuring myself to run sub-20. The windy forecast actually relieved some of the pressure, because if the conditions had been perfect, then I would have expected more out of myself. As for placing, I came in as the 4th female.

I'm so happy! I remember always thinking how fast those 19:xx people were. And now, I am one of them.

Turkey Trot history for the years I have data

 Year   Mile 1   Mile 2   Mile 3  Final Kick  Time
 2009  7:25  7:44  7:37 7:1323:40
 2010  7:19 7:197:07  6:1322:33
2011  7:00 7:05 6:42 5:5721:29
 2012 7:127:157:056:1022:18
 2013  7:26 7:30  7:03 6:3822:46
2014  7:01 6:54 6:45 6:1521:30
 2015  6:43 6:43 6:35  6:0320:51
  2016     6:38    6:49   6:38  5:49 20:50 
  2017   6:366:346:275:37 20:21 
  2018   6:336:266:18 5:35 19:58 


Friday, November 24, 2017

Turkey Trot Magic

Yesterday I ran my 12th consecutive Virginia Run Turkey Trot. I first ran this race in 2006 in a time of 23:32. It was my second ever 5K. It is now my longest standing running tradition together with Greg, who ran his 9th consecutive trot.

This race fell at an inopportune time. I had taken two full weeks off from running post-marathon to let my Achilles tendonitis heal, and when I resumed, my legs felt extremely stiff and heavy. I went pool running and swimming four times during those two weeks in an effort to maintain my cardiovascular fitness. Plus, I simply enjoy exercising and this was the most Achilles-friendly exercise I could think of.

I also continued to do my rehab exercises, which are simply heel drops using as much weight as tolerated. I discovered that I could add even more weight using the Smith machine at my office gym, and once I started doing that, I saw rapid improvement. In fact, I was 100% pain-free before, during and after my run on Monday. I wish I had discovered this machine months ago! I'll write another post soon about my Achilles tendonitis experience including what helped, and what set me back.

By the time Thanksgiving rolled around I was no longer worried about my Achilles tendonitis. Instead, I thought that my heavy legs might make it impossible for me to run fast, and there would be huge "bonk" potential. My legs felt like they were at mile 21 of a marathon during Tuesday's easy 4-miler, and I'm not exaggerating. I foam rolled and took Epsom salt baths after Tuesday's run in an effort to revitalize my legs, and hoped that they were just heavy from not having been used in so long.

Race Goals
Race morning arrived and I was excited to be racing. Given how horribly my marathon turned out, I wanted another shot at running hard, pushing myself, and staying mentally strong. Over the summer when I was doing specific 5K workouts, my goal was to be able to break 20:00 in the Turkey Trot. It was simply too hot to do that in the summer, but I thought that if I increased my 5K fitness in the summer months, it would stick with me during marathon training.

Many marathon training plans focus primarily on Lactate Threshold work and endurance, but my coach throws a healthy amount of short, high-intensity intervals as well. For example, I ran 15 x 1 minute hard, 1 minute easy, followed by 15 x 30 seconds hard, 30 seconds easy. And then a few weeks later I did that same workout but with 20 sets. Which comes out to a solid hour of constant on-and-off sprinting. With workouts like these frequenting my marathon training schedule, I thought that I had not only maintained my 5K fitness, but increased it.

I knew that I was in the best shape of my life in the weeks leading up to the marathon, and if I had raced a cool 5K back then, I think sub-20:00 would have been highly likely. So, on the one hand, I knew I was in excellent shape. On the other hand, I had taken two weeks off, and my legs had felt like bricks just 48 hours prior.

Ultimately, I decided I would run the race by feel, with a stretch goal of sub-20:00, but a more realistic goal of simply setting a course PR (under 20:50). If I had to predict my time, I would have guessed 20:30 if things went well, and closer to 21:00 if they didn't go well.

Before the Race
Greg and I have our "before the race" down pat! We know exactly when to leave the house, where to park, where to go to the bathroom, where to warm up, etc. We ran the warm up at a pace of around
Virginia Run Turkey Trot Start Line
8:35 and it felt more like 8:00. I actually felt really good, but I wondered if I was in for a slap in the face given that my easy pace felt "harder than easy"!

It was 32 degrees and sunny, so we warmed up with an extra layer over our long-sleeved racing shirts and then hung those clothes on a fence near the start/finish This was perfect racing weather for me, particularly since there was no wind whatsoever. What a contrast to all the crappy weather we had all fall!

Greg and I both planned to go out at around 6:30, but I knew that was highly subject to change based on how I felt. This course can be very fast if you know how to pace it. The first two miles are net uphill, and the last mile is net downhill. However, the first mile is gently rolling hills (starting with a downhill), whereas the second mile has a single large hill. And even though the third mile is mostly downhill, there are a few ups to keep you on your toes! In an ideal world, I like to run the first two miles at around the same pace, and then really hammer it home on the last mile.

Mile 1: 6:36
During this mile, I focused on just staying relaxed. Running so fast was definitely a shock to my system. I hadn't run at this pace in over four weeks, so my objective was to try and get into a groove that felt natural. Being a turkey trot, I had to pass a lot of kids during the first half mile-- the ones that go out at a pace of 6:00 for the first minute and then blow up. I'm so used to this now that I don't even see it as an obstacle.

Mile 2: 6:34
I was pleased with my pace for the first mile and feeling good, so I resolved to run the second mile at the same pace or faster. I was on track for this until the big hill came at the end of the mile. I told myself that a slow down on the hill was NOT inevitable, and I was going to maintain my pace no matter what. I decided to make myself hurt as much as possible, and do whatever it took to not slow down on that hill. Typically, my strategy is to run an even effort in races, not an even pace, but at this point, I wanted to push myself up the hill because I knew I'd be able to recover on the downhill. Plus, I was highly confident in my endurance. If I could just not lose any time up the hill, I'd be golden. And voila! I did it! It really hurt like hell the closer I got to the top, but I refused to back off the pace and it paid off.

Mile 3: 6:27
Now it was time to really gun it. I knew that I'd have to conquer two small pesky inclines, but aside from that, everything would be flat or downhill. When I was about 3/4 of the way through the mile, I glanced at my Garmin and it read a 6:34 average pace for that mile. This was not acceptable to me so I pushed even harder. I know that many people race better when they don't look at their watches, but for me, when a race is almost over, I find that looking at my pace can be a huge motivator.

The Last 0.14: (5:37 pace)
With the realization that I was going to run a really strong time, I gave it all I had to make it as strong as possible.

I finished in an official time of 20:21.

Usually during races, I am aware of the other runners and where I am relative to other women. But during this race, I was solely focused on myself. I had Greg in my sights the entire time (he ran 20:03) but otherwise, I wasn't overly aware of who I was passing or the people passing me. Because I was initially so uncertain about what would happen, I wasn't viewing this as a competition.

Anyway, even though I didn't break 20:00 I was pretty excited. My course PR was significant and I was delighted that I managed to maintain so much fitness. I titled this post "Turkey Trot Magic" because on Tuesday I felt ridiculously sluggish and heavy, but then I went out an ran a 5K at very close to my overall PR (20:17). It just goes to show you that running is truly dynamic-- some days you have it, other days you don't. It was also "magic" in that my Achilles were completely pain free before, during, and after the race. And running fast is pretty much the worst thing you can do with this injury. After the Leesburg 5K in August, I was in a lot of pain shortly after the race.

In terms of overall results, I placed 4th out of 989 women. This was a large turkey trot, so I was very happy with my placing.

Final Thoughts and Stats
I learned a lot from this race. From a physical standpoint, I think that running Monday-Wednesday really helped my legs get back into the groove of running. I'm at my best when I run 7 days a week, and take long breaks in between cycles. If I miss a day of running, I feel stale the next day. I run 30 minutes at a recovery pace every Sunday, which is enough to give my legs a rest, while keeping them used to moving. I also learned that even if my legs feel like garbage one day, they can bounce back quickly, provided I get enough sleep and do things like foam roll. Other thoughts and stats:
  • I was 1st place in the 30-39 year age group, and I am 39 years old. During the past 8 years that I've been in this age group, I have been slower. 
  • This is a course PR by 29 seconds. My previous fastest was last year in 20:50
  • I ran 4 seconds slower than my overall PR of 20:17
  • I think I paced this race perfectly
  • Given that I ran a pace of 5:37 for the final stretch, I do think I could have run the entire race slightly faster, but trust me- I was pushing really hard the whole way!
Within the course of just two days, I went from being discouraged about my running to very optimistic about kick starting the new cycle. My next race is a 5K on New Year's day, and I am now confident that I will be able to start training again without my Achilles plaguing me, and with my marathon fitness mainly intact. 

More Stats!
If you don't care about data, you can stop reading here. But I geek out on this stuff, and one of the best things about having an annual racing tradition is to compare the splits year over year. Here's a fun chart:

 Year   Mile 1   Mile 2   Mile 3  Final Kick  Time
 2009  7:25  7:44  7:37 7:1323:40
 2010  7:19 7:197:07  6:1322:33
2011  7:00 7:05 6:42 5:5721:29
 2012 7:127:157:056:1022:18
 2013  7:26 7:30  7:03 6:3822:46
2014  7:01 6:54 6:45 6:1521:30
 2015  6:43 6:43 6:35  6:0320:51
  2016     6:38    6:49   6:38  5:49 20:50 
 2017  6:36 6:34 6:27  5:3720:21

Splits from 2006-2008 are unknown because I didn't have a Garmin back then.

Thursday, November 24, 2016

Every Second Counts: Turkey Trot 5K Report

This morning I ran my 11th consecutive Virginia Run Turkey Trot 5K. That's right, I have an eleven-year streak, which is impressive, considering I have never been ill or injured on Thanksgiving. Knock on wood! I discovered the race in 2006, and have been back every year since. I met Greg in 2009, so this was Turkey Trot #7 for him.

Background
Virginia Run Turkey Trot 5K

If you've been reading this blog, you know that I spent 12 weeks over the summer with mono. Zero running, zero exercise. I started running again on September 20, but I didn't resume speed work until about four weeks ago. And even at that, it wasn't very intense.

On November 13, I ran the Veteran's Day 5K, where I smashed by goal by nearly a full minute, finishing in 21:31 on a hilly course. There wasn't too much time for speed work between that race and this one, but on Thursday, I ran road intervals of 2 x (1:00, 2:00, 3:00, 2:00, 1:00), all with 90-second recovery jogs. I was pleased with how the run felt, and it seemed as if I was getting close to hitting the paces I was last spring. The follow Saturday (last Saturday) I ran for 80 minutes, with the first 70 minutes being easy, and the last 10 minutes "hard." The hard minutes averaged a pace of 6:51, which helped boost my confidence. And then on Monday of this week, I did a little tune-up workout with 4:00, 3:00, 2:00, 1:00, 1:00. So now that I think about it, my coach was able to squeeze in a decent amount of speed between the Veteran's Day race and today.

Plan
Going into this race, I made the following assumptions:
  • I would be fitter than I was for Veteran's Day, because when you are coming back, you make gains quickly
  • The course would be slightly easier, with the last mile being a net downhill instead of up a huge hill
  • The course would measure shorter on my Garmin
Garmin distance is important because when I am trying to project a finish time, I know that my Garmin will read something longer than the official race distance. I like comparing apples to apples, and I use my Garmin to pace myself when running. For Veteran's Day, my Garmin showed an average pace of 6:46. I knew that if I ran the exact same pace today, I'd end up with a 21:14 (or thereabouts) instead of a 21:31. I also got a FitBit for my birthday that tracks my resting heart rate, and in the past 10 days, my resting heart rate had gone down from 51 to 47. Not surprising, given that you make gains quickly when coming back from downtime.

So given these three elements of being fitter, having an easier course and having a shorter course, I thought I would land somewhere around 20:55. And that got me thinking. My all-time 5K PR was 20:51, set on this course last year. So, why not try to push it a little and go for a modest PR this morning? Which is exactly what I did.

My pacing strategy was to take the first mile at 6:38, which was 4 seconds faster than last year, and then try to run around the same paces I did last year for the rest of the race. Another important aspect of my plan was the tangents. Usually when I run this course, my Garmin measures 3.13. But last year it was 3.14. I know I am thinking about seemingly insignificant things here, but hey-- when you are trying to PR by a matter of seconds, it all matters! So this year, I told myself to pay very close attention to the tangents and to not waste energy weaving around kids during the first mile.

Before the Race
Greg and I arrived at the race, parked in our usual spot at a nearby church, and went to the bathroom in the church. There was a man standing outside the church who seemed very happy to let us in and use the bathroom. He kept emphasizing to us where the bathrooms were and he gave us a huge smile. I think he was literally there that day for the sole purpose of letting use the bathroom. He even said "that's what I'm here for." It was really awesome.

We warmed up, with a plan to be in the start corral about 5 minutes before the race started. A little bit of panic set in when the course marshal told us we couldn't cross the street to get into the corral-- we had to walk all the way around, which meant weaving through a huge crowd. And when we finally crossed the street, we were at the very back of the corral, so we had to weave through another crowd to get up to the front. This happened to other people who wanted to be close to the front and they were annoyed as well. This race has over 2,000 people, and many of them are small children, so getting stuck in the back was not an attractive option!

The weather was perfect. Low 40's and overcast with just a very slight breeze. I had actually debated between wearing CW-X compression capris and shorts. I feel like the compression helps my legs move quickly when it's cold out. But ultimately I settled on shorts because they weighed less! I needed every possible advantage if I wanted a shot at a PR.

Mile 1: 6:38
Unlike most years, there were not a ton of 8-years olds lined up right at the front. This meant I didn't have to do a lot of weaving like I usually have to do in the first mile. I got pulled out pretty quickly on a slight downhill and when I looked at my pace halfway through the mile, it said 6:20. Oops! Time to slow down a bit, which was easy because the rest of the mile was a slight incline. I also noticed a tangent in the first mile that I had never noticed before, so I made sure to run to the inside of the curve. When I hit the first mile marker, I was pleased that I had executed according to plan, but I did not feel good. I was already tired. 

Mile 2: 6:49
I didn't have the same "pep in my step" that I did at the Veteran's Day race. I felt tired and a little sluggish. There's a sizable hill in this mile. It's not terribly long, but it's on the steep side, so getting up it is always a challenge. It wasn't this hill, however, that slowed me down. It was the first part of the mile, which was flat-ish. I was just tired and not able to maintain that 6:38 pace. During this mile, someone yelled "Go Elizabeth!" at me and I wondered who it was.

Mile 3: 6:38
As I continued on, people kept yelling "Go Elizabeth" at me, at which point I realized that the girl next to me must have been named Elizabeth. Whatever- I'll take it! I knew this mile was a net downhill, but that it ended on an incline-- the same incline that was a decline and pulled me out too fast. I was hoping to really kill it during the mile like I typically do on this course. Usually my last mile is significantly faster than the first two. But today, I was pushing as hard as possible, but my Garmin pace was stubbornly refusing to budge. During the last half mile, I started to think that I wouldn't get my PR. It would be close, but likely wouldn't happen at this rate. Regardless, I still pushed with everything I had.

Last 0.13: 5:49 pace
Amazingly, I did have another gear in me, which I hit as I passed mile marker 3. I revved and revved and revved. Someone passed me at lightening speed and it motivated me to kick even harder. I saw the clock as I crossed and I stopped my Garmin: 20:50.

I knew this feeling. It was like being at the Columbus Marathon with a Garmin time of 3:40:00 and hoping the official time matched, which would mean a BQ. Greg and I made our way to the results area and typed our bib numbers in the computer. I held my breath. And the official time was. . . 20:50!  I did it! I PR'ed by one second!

Back in 2014, I ran this race in 21:30. I had missed my then-PR of 21:29 by one second. I wasn't terribly disappointed, but it's much better when it goes the other way!

As for Greg, I knew he was in great shape and I had predicted a huge PR for him. Well, he got a 44-
First place AG award: a hat!
second PR, which is massive for the 5K. He clocked in at 20:09, which means sub-20:00 is clearly within his grasp.

I won first place in my age group, which earned me a hat identical to the one I won in 2014.  I was the 13th female out of 1164, which I was thrilled with. Not to look a Gift Turkey in the mouth, but they were giving away Ninja blenders and restaurant gift cards as raffle prizes, but the winners only walked away with hats! That's okay. I'll be back again next year and hopefully keep adding to the hat collection.


Key takeaways
Even though you don't want to over-think things, the small things matter. If I hadn't been as diligent about the tangents, it could have cost me a second or two, and I would not have PR'ed. According to Strava, both this race and last year's race had a 5K effort of 20:41. I was able to run a faster "official" time this year because of the tangents.

I am running yet another 5K next weekend. I think all of these 5K's now will set me up with a nice base speed to begin marathon training. Next weekend we are back to a longer, hillier course, so I don't anticipate a PR. But you never know!

And for fun, here is my Turkey Trot history for the past 7 years:


 Year   Mile 1   Mile 2   Mile 3  Final Kick  Time
 2009  7:25  7:44  7:37 7:1323:40
 2010  7:19 7:197:07  6:1322:33
2011  7:00 7:05 6:42 5:5721:29
 2012 7:127:157:056:1022:18
 2013  7:26 7:30  7:03 6:3822:46
2014  7:01 6:54 6:45 6:1521:30
 2015  6:43 6:43 6:35  6:0320:51
  2016     6:38    6:49   6:38  5:49 20:50 


Happy Thanksgiving to all my blog readers!

Thursday, November 26, 2015

Turkey Trotting: Massive 5K PR

This morning I ran my 10th consecutive Virginia Run Turkey Trot 5K. That's right- my 10th year in a row! I'm thankful that I have never been injured on Thanksgiving and I have always been able to participate in this race since I discovered it.

After running the Richmond Half Marathon 12 days ago, I took a full week off from running. I made the mistake of not stretching or foam rolling during that time. After two days, my legs felt fine just walking around, but I didn't realize how tight my left IT band and calf were. When I returned to running, my entire left leg was tight and and everything felt like it was pulling on everything else. I started foam rolling twice a day and eventually my hip/hamstring/IT band felt better, but my calf was still an issue. It had seized up and was tender to the touch. I was actually worried that I wouldn't be able to run this race, but I went for it anyway.

I aggressively treated my calf by having Greg massage it twice a day, foam rolling it, stretching it three times a day, using Salonpas patches, taking Aleve, and wearing a compression sleeve. Instead of running yesterday as originally prescribed by my coach, I took the day off entirely.

Strategy
Compression socks for my calf, and matching shoes!
I had this race planned down to the second. Since I had 9 of these Turkey Trots under my belt, I knew the course profile like the back of my hand. Last year, I ran the first two miles at the same pace, and then the third mile was about 10 seconds faster. The first two miles are a net uphill, with a significant hill in the second mile, and the last mile is a net downhill.

The McMillan calculator predicted a pace of 6:37 for my 5K. I wasn't sure I wanted to go for that, though, given I had taken a full week off of running and I was optimally trained for the half marathon, not the 5K. My plan was to run the first mile at a pace of 6:43-6:45, and then run the second mile at the same pace as the first. My plan for the last mile was a 6:35, and then an even faster final kick for the last 0.1. This would give me an average pace of about 6:40, putting me comfortably below 21 minutes.

My previous PR was a 21:29, and I was hoping to smash it, just as I had done to my half marathon PR just 12 days prior.

Before the Race
I think I set a PR for the most amount of quality sleep the night before a race. I slept for a full eight hours, and then woke up extremely gradually. I was so relaxed and rested that it took me about 45 minutes from coming into consciousness to actually feeling awake. I also slept insanely well two nights before the race. I think I have this no-anxiety thing down pat!

Greg and I did our normal pre-race routine: bagels, bathroom, and bib affixing! We arrived at the race 35 minutes before the start, with just enough time to warm up and then line up. We warmed up for 20 minutes, and I felt ready.

The weather was absolutely perfect. 40 degrees, mostly sunny, with 0 mph winds. Usually this race is in the low 30's, so it's rather chilly at the start. But this year, I was rather comfortable at the start line in my shorts and short-sleeves after having warmed up.

Mile 1: 6:43
I hate the first mile of this race. There are so many slower runners who start at the front, go out at a pace of 6:30, and then slow down to an 8:00 mile shortly thereafter. This equates to quite a bit of passing and weaving. I knew to expect it, so I managed as best I could. At one point, there was a group of 3 people running side-by-side and it was difficult to pass them. I tried to not let it fluster me. When I saw my Garmin beep at 6:43, I was pleased. I was executing on the faster end of my narrow 3-second window!

Mile 2: 6:43
This mile features a significant hill. I've gotten much better at hills over the past year, and was able to pass quite a few runners on this hill. Regardless, I was happy to be over it and running down the hill on the other side. I stayed focused, and tried my best to run the tangents. The good thing about mile 2 is that the course opens up with a wider road, so it's easier to pass people. I was pleased to see that I logged another 6:43, exactly as planned.

Mile 3: 6:35
I knew my PR and sub-21 was in the bag if I just continued to execute the plan. The last mile is a net downhill, but of course I was getting tired, so I had to really work for this. Since I've never run a 1-mile race, this 6:35 is also a 1-mile PR for me.

The last 0.14: (6:03 pace)
I gunned it to the finish and was happy to see the clock was still in the 20's.

My official finish time was a 20:51. This is a PR by 38 seconds from my 21:29 that I ran at the 2011 Turkey Trot. Last year, I ran a 21:30, missing my PR by just one second.

I was slightly annoyed that even though I was trying to run the tangents, my Garmin measured 3.14 miles. Greg's Garmin was closer to 3.1, and in the past mine has been closer to 3.1 as well, but I think all of the weaving during the first mile was the culprit. Anyway, according to Garmin, it was an average pace of 6:39 for 3.14 miles, which is very close to what the McMillan calculator had predicted.

Even though Greg hadn't done any speed work since the Columbus half marathon nearly six weeks ago, he ran a 22:01, which pleasantly surprised us both.

After the race, we found one of our friends and cooled down with him for about 15 minutes. The cool down was really important. When I first started running, my left leg was extremely tight. I was worried I had done some serious damage. But after a few minutes, it started to feel better, and by the end of the cool down, my left leg felt semi-normal again.

Final Thoughts
I think that having a well-defined plan was critical to my success. I knew exactly how I wanted to race this one, and my execution matched my expectations perfectly. Could I have run it faster if I set a more aggressive goal? I think maybe by just a few seconds. I was feeling really exhausted by the end of it, so I don't think I could have squeezed out more than 2-3 seconds extra. I'm trying to move away from "playing it safe" in races so I can run at my full potential. I don't think I played it safe here, but on the other hand, I wasn't quite as risky as I was in Richmond. There was also my tight calf to consider, and I definitely didn't want to pull it or tear it.

In any event, a 38-second PR in the 5K is HUGE, and I am super excited that I have reached a new level of fitness and I can run a race without anxiety.

Thursday, November 27, 2014

Every Second Counts: Turkey Trot Race Report

When I qualified for Boston last month with not a second to spare, I realized the importance of seconds while racing. Things like running the tangents, avoiding weaving, and being quick about water stations all really matter, no matter how short or long the race.

This morning, I ran my 9th consecutive Virginia Run Turkey Trot 5K. I'm very thankful that I've been able to run this race since 2006 without injury. My fitness for this race usually depends on what fall marathon I ran, how well I recovered from it, and how much time I had afterwards to knock out some fast workouts.

This year, I was pretty confident in my ability to PR. I took 9 days off after the Columbus marathon, but then had nearly 4 weeks of training that included some interval work.Two weeks prior to the marathon, I shaved over a minute off of my 10K PR from 2011, so I figured I could probably take at least 10 seconds off of my 5K PR, which was also set in the fall of 2011.

Before the Race
Greg and I parked in our normal spot and did our normal warm up, just under two miles. The weather was perfect. Overcast and 33. I wore my CWX capri pants and a light weight long-sleeved shirt. The pavement was still wet with a few icy patches from yesterday's snow event, but safe enough to run on.

I know this course very well, and my splits are always very similar. The second mile has a large hill, so that's always the slowest mile. The last mile is slightly downhill, so that's usually the fastest mile, if I can hold onto my effort level.

When I PR'ed at this race in 2011, my splits were 7:00, 7:05, 6:42 with a time of 21:29. I wanted to run a similar pattern today, but with everything about 5 seconds per mile faster.

Mile 1
This race is notorious for being very crowded with kids and slower runners lined up at the front. Greg and I lined up close to the front, but the problem was that the people behind us went out at like a 6:30 pace for the first quarter mile and then slowed down, which meant a lot of people to pass. I didn't want to waste energy on weaving, so I wasn't as aggressive pace-wise as I could have been. I felt like I was putting out a hard effort and I didn't worry that I was slightly slower than planned.

My first mile clocked in at 7:01 and it felt tough. I was a little surprised that it felt as hard as it did. When I ran my 10K six weeks ago I ran some 7:03 miles that didn't feel nearly as hard, but I guess that course was flat and this one has hills. The thought crossed my mind that a PR wasn't likely but I immediately dismissed it and told myself that it was definitely still possible.

Mile 2
This is the mile with the big hill. One of my goals for the race was to stay strong on this hill and to not let it slow me down. This mile has always been my slowest of the race, but with a 7:01 first mile, I really wanted to speed up and not slow down.

Before the hill I developed a strong rhythm and cadence that was keeping me at about a 6:55 pace. I told myself to keep up the pace, and increase the effort. Typically my strategy is to run an even effort level, which means slowing down on hills. But today I told myself to run a steady pace, and just be mentally tough up the hill.

It worked, and for the first time ever, mile 2 was faster than mile 1 at 6:54.

Mile 3
I wanted to really drive it home here, but things were getting hard. 5Ks hurt. They hurt a lot. It's a
constant mental struggle to tell yourself to endure that kind of pain and not slow down.

Tights are never flattering in race photos.
I had a few women in my sights that I wanted to pass during this mile. I think I passed two of them and I'm not sure about the other one because the finish line is a bit of a blur. I had remembered this mile being mainly downhill, but there were some inclines that really hurt. I clocked a 6:45.

The last 0.13 + Finish
I usually have a very strong final kick and regret not starting it sooner. But that was not the case today. I stayed strong, with a 6:15 pace for that last bit, but there is no way I could have started it sooner. I know I gave 100% and no less.

My Garmin credits me with a 6:52 average pace and my official race time was 21:30. That's just one second off of my PR.

I placed 3rd in my age group out of 242
I was the 15th female out of 1,351

My first age group win at this race!  And with 10-year age groups too!!!  I wanted to stay for my award, but it was just too cold to hang around in such a lightweight shirt. Hopefully they will mail me whatever it is won.

Even though I didn't PR, I wasn't disappointed. My immediate reaction was I qualified for Boston by one second, so if I miss a 5K PR by one second, it's really not that big of a deal. In other words, I am so thankful for that one second in my marathon, that I'm not going to get upset about not having that second today.

Plus, I ran this race hard. I don't think I could have found an extra second. I guess I'm a little surprised that I wasn't faster, given how much time I shaved off of my 10K. But I know I gave it my all.

Final thoughts & takeaways

  • I finally won an age group award at this race, after 9 years!
  • This was also the first time that the hill in mile 2 didn't slow me down
  • Next year, I will be more aggressive on that first mile and not afraid to weave if necessary.
  • Every second counts, and I need to remember that when things get tough
Now it's time to enjoy Thanksgiving!






Friday, November 29, 2013

Nike LunarGlide, San Francisco, Turkey Trot

I haven't been able to blog as much as I would like lately, so this post covers three separate topics.

Nike LunarGlide 5
In May, I decided to re-visit my running shoe situation. Thanks to the 90-day return policy of RoadRunner Sports, I was able to experiment with quite a few different shoes:

  • New Balance 870: I liked the shoe, but I my arches started to hurt after running just one mile.
  • Saucony Mirage: Low heel-to-toe ratio. This shoe bugged my Achilles area
  • Brooks Ravenna: Felt way too bulky. Like running with bricks.
  • Asics 2000: I liked this shoe, but it gave me blisters after 4 miles. 
  • Mizuno Wave Inspire: Too stiff, started to give me a bad pain after 10 miles
  • Brooks Adrenaline: Had been my go-to shoe for years, but the new model made my feet hurt after about 8 miles
With all these changes and experiments, I ultimately ended up getting injured. As I started running again, I posted on the Runner's World forum and asked for advice. I am a mid-foot striker with a narrow foot and mild pronation, looking for a shoe that won't hurt the bottoms of my feet. I was worried that I would not have a shoe to run the Chicago marathon in and I was starting to get nervous. Someone recommended the Nike LunarGlide 5, so I went to RoadRunner Sports and asked to try it.

I ran around the store and immediately fell in love. My feet felt like they were getting a massage. The fit was good, and I absolutely loved the way they felt. I bought them and started wearing them for my long runs. I
I designed these shoes on Nike.com.
was absolutely amazed. When the runs were over, I didn't feel a need to immediately take my shoes off. My feet felt great! I ran the Chicago marathon in them and my feet felt great, and I didn't get injured. 

Best of all, if you go to the Nike.com website, you can customize this shoe and get it in whatever color combination you want. You can even customize the words on the tongue. My shoes say "Zebra" on one foot and "Power" on the other. They are red, white, and black to match my Capital Area Runners gear. It only costs about $35 extra, so I figured it was worth it to get the shoes to look exactly how I wanted.

I will still wear the Mizuno Wave Elixir for speed work and races that are half marathons and shorter. Don't get me wrong, the Nike would probably serve this purpose fine, but I have been a faithful Elixir wearer for years and I like having two types of shoes I rotate between. The Elixir is actually being discontinued so I purchased a fairly large stock that should last me about 3-4 years.

San Francisco
I went to San Francisco for business in the middle of November. I was there for almost two weeks, so Greg flew out and joined me over the weekend. I'd run in San Francisco a few times before, so I knew exactly how to run to the flattest area of the city-- the Embarcadero. 

The Palace of Fine Arts. We ran through this!
For my birthday, Greg had reserved us a semi-private wine tour of Napa Valley. On the way there, the driver showed us a few of San Francisco's key landmarks. We were blown away by the Palace of Fine Arts, which I had never seen or heard of, even though I had been to San Francisco a number of times in the past. Greg, being more adventurous than I am, was determined to find a way for us to run there the next day. I told him it would be impossible for us to get there without running on some very steep hills (so steep, you can't even run on them) or taking this long route that would be 10 miles. 

He insisted that we could and found a way for us to get there in just over 3 miles. Minimal hills. It was so thrilling to run through this dome. It was almost like being in the Disney World half marathon again. It was also fun running around that general marina area. I had always stuck to the Embarcadero, because it was what I knew. 

I was also lucky to be in San Francisco while we were having unseasonably cold weather back home. It felt good to be running consistently again, after about two months of no training. I tapered for Chicago, recovered from Chicago, ran New York City, and then recovered from that. While in San Francisco, I ran a two-mile tempo run, and it was tough. It was definitely an indicator that I hadn't done speed in a long time!

Turkey Trot 5K
I ran my 8th consecutive Virginia Run Turkey Trot 5K yesterday morning. I suspected that this would be my slowest Turkey Trot in a long time because I was so out of shape. I did a short track workout on Monday, but aside from that, I hadn't run intervals since the end of September. And my overall mileage had been low. 

But this didn't stop me from giving it everything I had!  

It was 25 degrees with a light breeze. The forecast the night before had been for 22 degrees, 16 mph winds, which equated to a "real feel" of only 8 degrees. So I was actually quite thankful that it wasn't as cold or windy as it could have been. And with the sun, I actually felt warm in parts of the race!

Greg and I parked, and warmed up for 1.5 miles. I was worried that we parked my new car in too tight of a spot, and that the two mini vans next to me would certainly ding my car. Greg told me that we'd just have to run really fast and get back to our car before they did! 

We got to the start line, where, as usual, a ton of kids were lined up right at the front. One of the challenges of this race is that so many kids and slower runners start at the very front, and it's annoying trying to pass them all. This race had over 3,000 runners, so it was definitely sizable. I felt very relaxed going into this race, probably because I didn't have any expectations or self-imposed pressures to run a specific time. I was hoping to get sub-23:00, but I just didn't know what I was in shape for.

Greg was also out of shape, and he predicted that I would beat him because I had two short tempo runs and a track workout under my belt, whereas he didn't have anything. He got ahead of me as we started, and I remained about 5 seconds behind him for the whole first mile. I wondered if I would be able to pass him, but I didn't make it a focus. Mile 1: 7:26

Due to the nature of the course, I know that the second mile is always the slowest. I didn't look at my Garmin during this mile and just kept the effort level the same. It felt so hard, and I didn't feel like I was running fast. Yup. Out of shape! I still passed a few people in the second mile, but it's amazing how that
crowded race totally clears out after mile 1. Mile 2: 7:30.

At the start of the third mile, I still had Greg in my sights. But by this time, he was about 15 seconds ahead of me. He turned a corner and really sped up, so I didn't see him again until I finished.  In my head, I briefly wondered if I would be able to go under 23:00 with these paces. I wasn't sure, but I know that the last mile of this race is always my fastest. This is where knowing the course and having run it 7 times in the past comes in handy. I gunned it. It hurt, but I told myself I it would be over soon. I pushed and pushed and passed a few people during the last stretch, netting a zippy 7:03 mile.  Mile 3: 7:03.

I kicked it into my highest gear for the last 0.12. It took me 45 seconds.  6:25 pace.

My overall finish was 22:46

Last year, I ran this race in 22:18. However, this year, my last mile was faster.  Last year's splits were 7:12, 7:15, 7:05.

It's interesting to experiment with different pacing strategies. Last year I knew what kind of shape I was in, whereas this year I didn't. I therefore started far more conservatively this year for fear of not being able to sustain a fast pace. 


I am pretty happy with these results.

I'm definitely glad I did this race, and the plan is to spend the next five weeks building my speed back so I can be more competitive at the New Year's Eve 10K. I was noticing that even though it hurt a lot during that final push, it also felt really good and empowering to be running so strong. It felt "bad ass" as Greg says. (His last mile was in the 6:40's). Most importantly, I was thankful to be un-injured and healthy enough to race.

Thursday, November 24, 2011

My First Sub-7:00 Race

The title of this blog says it all. Well, most of it (otherwise I wouldn't need to blog). I was fairly confident in my ability to run a sub-7:00 average pace this morning in my 5K, but I if I did, it would be by the skin of my teeth. Maybe one of those annoying things when your Garmin says you rain a 6:59 average pace, but the official pace is 7:01.

This morning, my husband Greg and I ran the Virginia Run Turkey Trot 5K. This was my 6th consecutive year running this race.

Goals
My main goal for this race was to run sub-22:00, but I thought that if I was having a really good day, I could run around 21:45, for a sub-7:00 pace. I had just ran my fastest 5K ever as the second half of a 10K race, so I was fairly certain I could PR at the very least. I actually couldn't really imagine a sub-7:00 average, but the McMillan Calculator indicated that it was possible based on my recent 8K and 10K races. However, those two races were flat and this course has a huge hill in the second mile and a lot of other rollers.

Other goals were to not look at my Garmin after the first mile and to push as hard as I could during the last mile.

Pre-Race
The weather was 40 degrees and sunny, which usually means short sleeves and shorts for me. However, I had just purchased new CWX capri tights that felt awesome to run in, so I figured I would give those a try. Yesterday was ridiculously windy, so I chose long sleeves, a decision I would later regret. If it were any other race distance I would have certainly gone with short sleeves, but I figured, "how hot can you really get in 22 minutes?"

Greg and I parked, warmed up for 2.4 miles and then lined up. This race is notorious for slower runners and kids starting at the very front. As I was walking towards the start line, I saw a 12-year-old girl wearing the race t-shirt at the very front. Not one row back-- but at the absolute front. I later saw her walking halfway through the first mile. Every year I lose time in the first mile because of weaving and being blocked by slower runners, so I lined up in the 3rd row back. Next to me were two teenage sisters who looked to be about 12 and 15, both wearing the race-shirt. I figured that if they were going to be that close, so could I.

I was actually warm standing at the start line after having warmed up. I really wished I had gone with short sleeves but it was too late now. I rolled up my sleeves and kept them like that the whole race.

Greg and I were next to each other, and he said he was going to try and keep me in his sight the entire time. He hasn't been training very much lately so he didn't have high expectations for this race.

Mile 1: 7:00
Because of the course profile, you really have to run this race strategically. The first mile is rolling hills, with what seems to be a net downhill. So you have to go out faster than your goal pace, but not too much faster. You also need to do this while weaving around slower runners, who I inevitably found myself behind. (I'm not just talking about people running in the 8:00's, but people who were doing a very slow jog.) I was also entertained by people bonking in the first mile (mainly teenagers) because they completely ran out of breath by going out too fast. Anyway, I was planning for this mile to be around 6:55, but wasn't too discouraged when I logged a 7:00.

Mile 2: 7:05
I didn't look at my Garmin at all this mile, but I did look at it to see my split. I was sooo tempted to look at it during the long hill, but I forced myself to focus on nailing that hill. I imagined I was at a hill workout with my coach telling me to lean forward and pump the arms. I pictured him in my mind watching me and my form, and I wanted to make sure I was doing it correctly. Instead of looking at the Garmin and thinking about how this hill was slowing my pace as I have in years past, I focused on my form and using my arms and I was at the top before I even knew it!

Mile 3: 6:42
I did sneak a quick glance at the Garmin once during this mile and that reminded me exactly why I wasn't supposed to be doing that. This pace was extremely fast. I told myself to ignore that pace and keep putting out a strong effort. Just run! With about 0.3 miles left to go my stomach started to hurt. It was a good hurt though, like I was about to vomit. I think you're supposed to feel this way at the end of a 5K, otherwise you aren't pushing hard enough.

Last 0.1: (6:08 pace)
I kept my eyes on the finish line, got energized by the people cheering me in and gunned it.

Official time: 21:29 with an average pace of  6:56.

This is a PR by 49 seconds, which is very significant for a 5K. I still cannot believe I ran it that fast. And with hills. This is a course PR by 1:04 from my race last year in 22:33.

I placed 15 out of 1983 women
I placed 4 out of 369 women ages 30-39

I am just thrilled with how I raced this. I guess being a little slower than expected in the first mile really paid off in the last mile.

Greg finished shortly after me in 21:44. Not a PR for him, but considering his very light training over the past two months, it's fantastic.

Here is a fun Turkey Trot history grid:

Date  Mile 1 Mile 2 Mile 3 Finish Time 
 2008   Unknown Unknown  Unknown   23:22
 2009    7:25 7:44 7:37   23:40
 2010  7:19 7:19 7:07   22:33
 2011  7:00 7:05 6:42   21:29

The irony of all of this is that my fall training has been the lowest mileage of nearly all of my training cycles. My weekly mileage has been in the mid 30's for the most part, with some weeks in the 40's when I was training for Milwaukee Lakefront.

I can't pinpoint exactly what has caused this sudden speediness and massive PRs in the 8K, 10K, and 5K, but I'm guessing it's a combination of my core strengthening (which I do religiously), my swimming and my pool intervals. (I get my HR up higher in pool intervals than on a track). Of course, my coach has been encouraging these types of activities and the actual track workouts have contributed as well. But that is a topic for another blog post.

Right now, I am going to enjoy Thanksgiving with my family and be super excited about my massive PR!!!!

Thursday, November 25, 2010

Virginia Run Turkey Trot 5K

I ran the Virginia Run Turkey Trot 5K this morning. It was my 5th consecutive year at this race. Here is a recap of previous races:

2006: My second 5K ever in 23:32
2007: Hot, humid weather, still recovering from a marathon in 24:19
2008: Nice cool day, set a distance PR in 23:22
2009: Just got engaged, 2 nights with no sleep in 23:40

So, there hadn't been much improvement over the four years of doing this race and I was getting frustrated with the 5K distance. But then in April of this year, I set a massive PR in 22:21, so it made up for everything.

Going into this morning's race, I was pretty laid back. I'm just coming off or the NYC marathon, so I am not 100% recovered. I haven't done any speedwork since the marathon, and my last "fast" run was the Army 10-miler, over a month ago. I didn't think I'd be able to PR, or even come close, so I decided to play it conservatively.

The weather was about 40 degrees and overcast. I was wearing a short-sleeved shirt, tights and a running skirt. I probably could have done without the tights, but I never feel like they slow me down. My plan was to go out at a pace of 7:20 and then try to see if I could push harder. I was thinking I would be happy with a 7:20 average. Greg and I did a 1.4 mile warmup and then found ourselves in the starting area. It was shorter than we had planned, but there were so many people mulling around that there was no clear path to run through.

Mile 1: 7:19
There was a great deal of weaving this mile, which I expected. But there was no way to avoid it. Even though I started fairly close to the start line, this is a family race with a lot of children who like to be at the front, 2300 runners total. Because of the weaving, I expected that this would be the slowest mile. In terms of elevation, it was gently rolling hills. Greg passed me about 1/3 of the way into the mile.

Mile 2: 7:19
There are two significant hills in this mile, so even though I ran it at the same pace as the first mile, I put in greater effort here. I eased up on the uphills and flew on the downhills. I told myself that even if I averaged a 7:19, it would be a huge course PR and a time I'd be happy with.

Mile 3: 7:07
I decided to give it all I had in the final mile. I was back to the gently rolling hills and I told myself that I could tolerate the pain for just one more mile. It still didn't hurt as much as it had in previous 5Ks, so I didn't think I was running at full effort, but I still pushed really hard. I think that in previous 5Ks, I had gone out faster than I should have so I was bonking at this point. However, I felt really strong during this last mile, due to a conservative start.

Last 0.1: 6:25 pace
I told myself that I run intervals on the track that are much longer than this 0.1, so I was going to push hard. I did push, and I ran faster than my interval pace (typically 6:35). The guy who I was trying to beat (a friend of mine who beats me every year at this race) finished about 4 seconds ahead of me. I just couldn't catch him!

My official time was 22:33 (7:16 pace). This is faster than I expected, and according to McMillian, predicts a 3:40 marathon. My recent half marathon and 10-miler time predict well under 3:40, so this was a relatively "slower" race. But considering that I don't think I'm fully recovered from NYC, I'm very pleased. I also think I could have pushed harder, but maybe only by about 5-10 seconds.

I placed 6 out of 372 in my age group (30-39), beating 98.4% of them
I placed 31 out of 1686 overall women, beating 98.2% of them

My next race is the St. Jude Memphis marathon on December 4. It's hard to believe I am doing another marathon so soon! My company is a gold sponsor of the race, and we have a booth at the expo. So I go down there and man the expo and organize our employee team of runners. (I work for a software company that has nothing to do with running, but they donate a great deal of money to St. Jude, so I suggested the marathon sponsorship). But I think I am jumping ahead to the next blog post!

Now it's time to celebrate Thanksgiving with my new husband and other family members!

Thursday, November 22, 2007

Too Hot to Trot

Okay, so not really too hot, but it was a lot warmer than expected. And it made a cute title.

Today I ran a Turkey Trot 5K. It was 60 degrees, with 75% humidly and some winds. I ran this same course last year, and it was in the low 30's with misting rain. Last year, I wore three layers on top, pants, two pairs of gloves and a hat. This year, I wore just my running skirt and a tank top. 

A year ago, I would have LOVED this weather. But as other runners have told me, I would learn to appreciate colder temperatures because they make you run faster. However, I don't blame the weather for my poor performance today. I blame the fact that I am still recovering (cardio-wise) from my marathon. I didn't expect a PR, but I also didn't expect to be this slow.

I'll cut to the chase. I ran my slowest 5K ever. Here is a history of my 5Ks:
  • 24:17 in September 2006
  • 23:32 in November 2006 (same course I just ran)
  • 23:30 in June 2007 (first place in age group!)
  • 24:07 in July 2007 (lots of hills here)
  • 24:19 in November 2007
I got faster the first few times, and then I started to get slower. I am not sweating this too much because I know that my body is still recovering from the marathon and I know that I did give 100% of myself today. It's not like in the MCM 10K where I just gave up halfway through. I pushed as hard as I could all the way to the end, but my body simply couldn't go any faster.

I came across the first mile marker at 7:27. I knew I was in trouble because I felt like I had just run a7:15. I knew there was no way I would be able to keep this pace up, but I decided I was going to try my hardest. There was a big hill in mile 2. I'm much better at hills now than I was last year, but it still took a lot out of me. I passed mile 2 at a pace of 8:07. I was a bit disheartened by this, but I didn't let it affect me.

I knew that a PR was probably not possible, but I still planned to give the race my all. I felt this huge knot in my chest. I feel this pain whenever I run fast. I felt it at the beginning of the MCM 10K, and at the Cherry Blossom 10-miler. It's this sharp pain, but I always tell myself that it's not a big deal-- I can run through it. So, I had this knot the entire time. I just didn't feel good.

When I was getting close to the finish line, I ran as fast as I could to try to get in under 24 minutes, but the finish line was simply not close enough! I ended up running my slowest 5K ever, but I did push as hard as I could, so I am not disappointed with myself. I know I am in better shape now than I was last year at the time. However, I am better trained for longer distances, and not the short ones.

I placed 102 out of 1257 women
I placed 14 out of 185 in my age group.

I'm okay with this-- but I can't help but figure out how I would have placed if I ran the 23:32 from last year. I had planned on going to the gym afterwards and running some additional miles, but I wasn't in the mood. I did about a 1.5 mile warmup and a good stretch beforehand. I'm already satisfied with my 5K PR so I didn't have a huge desire to set one. However, I am not at all happy with my 10K PR, so I need to change that on December 9. Time to go enjoy Thanksgiving.