The first time I trained for a full marathon (the 2015 Pittsburgh Marathon), I swore I would never train for a spring marathon again. That winter was awful, with numerous snow storms and ice storms and brutally cold temperatures. My now-husband and I were forced to run three long runs on the treadmill — a 10-miler, a 14-miler and a 16-miler (my God, it was brutal.) Nope, nope, nope, I said to myself. If I ever do a marathon again, it will be a fall marathon. Screw this.
Then I ran the marathon that May and loved it. And the next month, I signed up for the 2016 Rock ‘N Roll D.C. Marathon, held the following March. And now I’m spending my fifth consecutive winter training for a marathon and I truly can’t imagine a winter without having a marathon to look forward to! Honestly, I wouldn’t say I’ve become a fan of winter, but having a goal to train and work toward during the darkest, coldest months of the year helps me get through a time of year that I’d always dreaded. Plus, I warm up a lot when I run (and I maintain that I’d rather train in 25 or 30 degree weather than 80 or 85 degree weather, especially with how humid and gross Maryland summers can be!)
And last weekend, I got a true taste of winter running when I ran in Rip It Events’ 3rd annual Little Patuxent River Run Half Marathon and 10K. This race, held every year on Super Bowl Sunday, takes place on the Patuxent Branch Trail in Howard County. I had run the half marathon the past two years, but opted for the 10K this year. Why? Honestly, I was paranoid about falling and injuring myself with less than three months to go until Boston. I’ve fallen off the treadmill and also while running in downtown Annapolis on the cobblestone streets, so yeah, it’s safe to say that I am not always the most graceful. Wasn’t worth the risk this year. (You can read my recaps of the 2017 and 2018 Little Patuxent halfs here and here!)
That turned out to be the right decision, because this is what the trail looked like at the start of the race:
Yikes. Because it was only in the 20s that morning, there was no chance any of that was melting any time soon. My only goal was not to fall and hurt myself — I knew I wouldn’t be setting any PRs (which would have been extremely unlikely at a trail race in the very best of conditions anyway!)
Because I had run this race twice in the past, I was familiar with the trail, and I remembered how beautiful the surrounding woods and river were — especially with the snow. So I tried to enjoy the scenery while also paying close attention to my footing. For the first mile or so, there were a lot of icy patches that we had to dodge around, and because the race is an out-and-back, I knew I’d have to watch out for the ice at mile 5, too!
The course is a challenge even when there isn’t snow and ice on the ground. There are two rather steep climbs, at miles 2.5ish and mile 4, that force even the speediest runners to slow wayyyyy down or even walk. There are some long declines, too, which can be equally scary if you trip over a rock or a root or something. And when packed snow covers the trail and you can’t even see any tripping hazards, well, it’s really tough!
But I never once fell, so mission accomplished! My finish time was 56:32, by far my slowest ever 10K time. Somehow, that was fast enough to get me 3rd in my age group, which surprised me!
As a Rip It Events ambassador, I ran this race for free. Opinions are entirely my own! A full list of 2019 Rip It events can be found here. If you’re interested in running any of them, let me know and I’ll share my 15 percent discount code with you!
Annapolis Striders’ Valentine’s 5K
Wow, that was a cold one. My husband and I ran the Valentine’s 5K at Kinder Farm Park in Millersville yesterday with a bunch of friends, but it was so frigid I couldn’t bear to take my gloves off to take out my phone and get some pictures at the race start/finish. 16 degree windchill, ughhhhh! This is the two of us thawing off in the car afterwards:
I had hoped for an age group award, and even looked at last year’s winners to see how fast I needed to run to be a contender. It appeared that I needed to run sub-23, which I thought was doable. And I did, finishing in 22:43, but it wasn’t fast enough. There were some SPEEDY runners out there, and I finished 6th in the 30-39 age group. (Although, Tammi, who finished a few seconds ahead of me, pointed out that if there had been a 35-39 age group, she would have finished first and I would have been second. And then her husband said, “Well, if my aunt had nuts she’d be my uncle.” So. Yeah.)
The run was OK. As I’ve said before, 5Ks are my nemesis and I often execute them poorly. This race reminded me of the Turkey Trot 5K that I ran on Thanksgiving Day. You know, that time I ran the first mile in a blazing 6:34 and then blew up during the rest of the race?? That basically happened again, except this time I ran the first mile in 6:46 (such restraint), then the second mile in 7:32 and the third in 7:35. At least those miles were consistent? But just think if I hadn’t busted out a sub-7 mile right out of the gate! Stupid! At least this 5K was faster than the Turkey Trot.
I would like to get better at 5Ks, but it’ll take some specific 5K training (i.e., not running them as part of marathon training.) I think I’m going to run another 5K on March 16, just about a month before Boston, so we’ll see what I can do then and if the speed work I am doing as part of my plan might actually help me run a good 5K.
Boston 2019 training
Nine weeks until Boston 2019! Having BQ’d in December 2017, I’ve been waiting SO long to run this race and I can’t even believe it’s almost here! I’m following Hal Higdon’s Boston Bound 12-week plan, and so far, it’s going well. He has me alternating hill repeats with speed work (Yasso 800s) every week, similar to what I did when I followed his Advanced plan to get my qualifying time. The long runs also alternate by mileage and time. For example, last weekend I had to run an easy 14 miles. This weekend, my long run was an hour and a half, with the first three-quarters run at an easy pace and the last quarter run at marathon pace. I’ve never done a long run by time before now, and I have to say I am liking it a lot. The time passes quickly, and it’s fun to finish a long run strong!
So what marathon pace am I shooting for in Boston? Good question. In a perfect world, I’d BQ again, but with the tighter standards for 2020, I’ll have to run 3:35 or better. And Boston is known to be a tough course, and my last two marathons were 3:53 (Baltimore) and 3:47 (B&A). I think continuing to work on my speed will get me back closer to where I was when I ran Rehoboth and qualified with a 3:35:00, but I’ve got a long way to go. That said, I believe a finishing time somewhere in the 3:40s is feasible.
And if I don’t meet that goal — it’s Boston! It’ll be awesome no matter what.
Have you run Boston? What advice do you have for me?