I’ve always been interested in numbers and running goes right along with that interest. When I first started running, I kept a running log in a spreadsheet on Google Docs. I initially kept track of just the daily mileage, but that quickly turned into tracking mileage, pace and shoe. Just a few months ago, I made the transition from Google Docs to dailymile. Combining dailymile with my Garmin data (I wear a 405), I’m pretty sure I have all the data I need.
So, I often go back and look at the numbers. One topic which is often discussed is how many miles certain runners put in on a weekly basis. For me, it’s really a matter of how many miles I can put in without affecting my time with my family. My weekday runs are mostly done in the morning before the family wakes up. For the days which I run twice, the first run is in the morning and the second run is done during lunch at work. The weekends are a different story, as I run with a local running group every other Saturday and they meet between 7:30 and 8:00 a.m. On Sunday (my long run day), I’m usually out the door around 7:00 a.m. As I get closer to Boston, I’ll move that time later in the morning to get used to the Boston starting time of 10:00 a.m.
With that said, I really believe an increase in weekly mileage has a direct effect on the results. Here are some of my numbers from the past few years. The average and peak are based on the 16 weeks prior to my taper:
Baltimore ‘06; Avg 23; Peak 35; 3:39
Flying Pig ‘07; Avg 27; Peak 44; 3:28
Flying Pig ‘08; Avg 39; Peak 54; 3:10
Columbus ‘08; Avg 48; Peak 65; 3:06
Boston ‘09; Avg 59; Peak 75; 3:09
Air Force ‘09; Avg 53; Peak 67; 2:59
It’s not just the total mileage that counts though. You also need to consider pace. With an increase in mileage, I’ve also reduced my overall pace, as it compares to my goal pace. For example, for my first two marathons, I ran every single mile at my goal pace. I simply didn’t know any better and the mileage was “small” enough to allow my legs to recover on my off days. For my last three marathons, my average pace is much slower than my goal pace. Most of my runs now are around my goal pace + 30 to 60 seconds. Running a slower pace allows my legs to recover from the increased mileage and allows them to still perform on those hard workout days.
So, what will I average and peak for my next 26.2? Unfortunately, my current hamstring issue will probably prevent me from getting the mileage I was hoping for Boston ‘10. Ideally, I was hoping to have an average in the low 60s with a peak around 75. I have a Sports Med Dr appointment next week and I’m hoping to come out of the appointment with a recovery plan. I can then put together a training plan for my next 16 training cycle.
