Sorry for the delay in a race report - I know it just ruined your weekend waiting to hear more details.
Just a perfect 55-degree morning, and a small race with just a couple hundred runners on a course that ran along a river and through farmland on Maryland's Eastern Shore.
My plan was to do the first 4 miles at 7:45 pace, then do 3 at 7:30, then another 3 at around 7:30, and then go 7:20 or faster for the last 3.1. I had a sense that I might be able to go around 7:00 for the last 3 if I stuck to those earlier paces, but I didn't want to set myself up for disappointment if that turned out not to be the case.
The gun goes off, and I find myself right near the front. About 6 people took off sprinting and I never saw them again, and then I was at the front of the rest of the field. Felt pretty good, cruised along, hit the 1-mile mark and saw that I had quickly gone spinning out of control, running my projected 7:45 first mile in 7:06. At that moment, I thought of someone here and coined a new phrase - Sand-blasting: the act of running the first mile of your race at a speed wildly above your intended pace.
So I made myself slow down. I've come to realize that distance running is about discipline - not just the discipline of going out and running even though you're tired, or it's 5 a.m. and your bed is so comfy, but also the discipline of not running too fast too soon. I tell myself all the time: what you do in the first mile can't guarantee you'll have a good run, but it can guarantee you'll have a bad one.
My main goal for the next few miles was to get my HR back under control. Times for those miles were: 7:43, 7:55, 7:48. As soon as I slowed down for the second mile, about 10 people streamed on by. I just focused on running with as minimal effort as possible. After 4 miles, I knew I was still about 30 seconds faster than I had planned. So instead of speeding up to 7:30 like I had planned, I shot for 7:40 for this mile - I knew that would be slow enough to have me feeling pretty good and complete my recovery from the over-exertion of Mile 1.
So I did Mile 5 in 7:37, then decided it was time to get back on schedule. Then Mile 6 in 7:25, and Mile 7 in 7:33. I was starting to feel good in Mile 6 and pressed the pace up a hill, which enabled me to catch about 4 of the people who had passed me in Mile 2. From this point on (actually from Mile 2 on, I think, nobody would catch me from behind).
Now I knew I was past the halfway point, and I was feeling really good. Late last week someone, maybe Workhorse, talked about how on the Pfitz plan he didn't start feeling good until about 5 miles in. I'm beginning to feel the same way. It's like my body has gotten conditioned to the point that once I get to 5 miles or so, it realizes "Oh, we're in long distance mode now, so it's time to start burning more fat and doing it as aerobically as possible" or something. So I decided to stop holding myself back - not pushing myself, but letting my legs go as fast as they felt like running. Suddenly, it felt like I was running at the same effort level, but covering the distance much faster.
Mile 8: 7:14
Mile 9: 7:25 (stopped to half-walk through a water stop)
Mile 10: 7:12
Shortly before the 10 mile mark, we had returned to the main road we started out on, and now the sun was shining higher in the sky and there was a faint but definite headwind (funny, I didn't notice it when it was behind me). At Mile 10, I looked at my watch and I was almost at exactly 1:15:00 (just 5 seconds ahead of that). So I knew if I could average 7:00 miles for the last 5k, I would break 1:37:00. I wanted to drop the hammer right away, but felt with the sun and wind that if I went for it now, I would be out of gas before the finish.
So I surged for a quarter-mile, doing what I call my "easy sprint" speed - it's basically the effort I would use to run quarter intervals, back when I ran quarter intervals (for a short and painful period late this spring). Then I eased off for a quarter, then surged for another quarter, then eased off for the rest of Mile 11. I finished it in 7:08 and passed about 4 or 5 more people. They were the last ones I would catch.
At Mile 11, it was time to go for it and I started running as fast as I still could. 6:51 for Mile 12. Mile 13, I felt like maybe I could crank it up just a little faster, but twice I tried to "get up on my toes" to really give my stride a little more power and both times my right calf sent an immediate signal that it would cramp instantly and completely if I tried that for more than one step. I didn't want to blow all my hard work with an incapcitating cramp in the final mile, so I backed off and focused on keeping my footfalls and stride exactly as they had been for the previous 12 non-cramping miles, and I was fine.
Got to the 13-mile mark at the entrance to the waterfront park and noted kind of hazily that my split was under 7 (turned out to be 6:56). Turned toward the finish and there were my wife and kids. I think they were surprised to see me quite so soon and my 7-year-old yelled out as I went past, "Dad, 13th place. Not bad!" I gave her a thumbs up and then picked up the clock at the finish line and knew I was under 1:37:00 - 1:36:41. Ended up 3rd in my AG. I'm psyched to have run 10 miles at 7:30 pace, and then run a 5K at 7:00 pace to finish it off. I averaged 7:08 for the final 6 miles, which is a lot faster than I thought I could have done.
Going to take a couple of days and think about my Marathon goal. I know all the calculators will tell me I can't get a BQ (3:20:59), but I'm still tempted. It's a matter of deciding whether I want to be reasonably sure of running a good marathon (like 3:30:00 or something) or take a chance of running a great marathon (for me) knowing that it might cause me to blow up and run a terrible marathon.
As always, thanks to you all for your support and insight and encouragement and inspiration. I absolutely wouldn't be accomplishing the things I am without the people here.