RunColo Blog

The McMillan Calculator had me running a 36:12 10k, which seemed hard for me to comprehend, especially since my 10k PR is 37:29 which was run last year in Longmont on a much easier/faster course. I knew a PR was a given and the race temperature of 50 degrees was ideal.

Mile Splits:

1 = 5:57 (should have gone out faster)
2 = 5:56
3 = 6:01
4 = 5:57
5 = 5:29
6 = 5:39

36:19

The splits are from my watch and what's odd is the results do not have my mile splits for mile 1, 2 or 6. My watch had my final time in 36:17 and I was surprised that my official time was 36:19, since I started and stopped my watch right at the start and finish. I'm sort of thinking that I may have had a defective timing chip, because at each mile marker they had two rows of mats a primary and backup, which means that I went over six different mats and my time was not read.

Regardless, 5:50 pace for the BB10k was a great showing for me. It's truly a tough course and with the finish having a slightly higher elevation than the start, I'm confident that I could have run a 5:48 pace or perhaps <36:00 on a flat/fast course. My pace at mile six was 5:49, but that steep hill going into Folsom killed my pace.

I'm sure most people would say that it's not a smart move to race a 10k six days before a marathon, but it's a great confidence booster going in to San Diego.

Goal for San Diego is <2:45, temps are supposed to be in the low to mid 60's, thus not ideal but at least they won't be super hot, the kind of heat that destroys any chance of a good race.

I'm pumped.