Grand Columbian Ironman 2007
- Ironman
- Sep 15, 2007
- Where
- Electric City, WA
- Grand Columbian Ironman140.6 mi12:38
- Swim2.4 mi1:20:4778th of 103
- T12:53
- RunMarathon5:08:02
Second Ironman, third Marathon… The bike course was 5 miles long, the run course was 1 mile long… all in all it was a brutal day… but I don’t regret a thing.
Race week
We arrived in Electric City on Thursday and checked into the Coulee Playland Resort, the swim start, so we had a front row seat for all the festivities. My Dad came along for support, and since he’s Mr. Camping we had a great big four-man tent, comfy camp chairs, a gas stove, and even a drip coffee maker that works on a camp stove. True luxury! Our campsite was at the far end of the resort, right next to the highway, but our house is on a busy Seattle street, so the white noise probably helped me sleep.
I took my Cervelo out for a quick ride on the first 7 miles of the course. Out of T1 you ride the flat for about three quarters of a mile, then head up an 800 ft climb over about 3 miles. It is an ugly climb, painted with messages for racers of years past: “You’re almost there”, “Go Ken!” I’ll admit I was a little worried about this race. I bought the new bike only a month before, I had switched to a more aggressive cassette, and my hamstrings and quads had been feeling weak even after two weeks of powering down. So I wanted to convince myself I could make that climb. The good news: I made it, no problem. It’s a hard climb, but I knew I could do it.
The OK news: it was really smoky. A massive wildfire about 20 miles away over the ridge had over 700 firefighters battling it, and the air was hazy and smelled of smoke. It didn’t seem to affect my ride. The bad news: my Garmin freaked out on me again. On a bumpy section of road it just shut off, the same problem my last unit had. I turned it back on but forgot to restart the timer. If that happened on race day, I was going to be MAD.
The run course had changed too: still an out-and-back done twice, but on asphalt instead of gravel, with some rollers and no shade. The race director promised a nice breeze off the lake, where the old course was down in a canyon.
The day before the race I swam the course. One lap took only 30 minutes, which would have been an all-new personal speed record; at the athlete meeting I learned the corner buoys weren’t in place yet when I swam it. But the swim felt good, straight and mellow. Race number 59, race start at 7:00am. Time for sleep!
Swim and T1
I had a really great swim this year: 1:20:47, almost 7 minutes faster than last year. I felt comfortable the entire way. I swam straight, I stayed calm, I even gave another swimmer a chance to draft off me. I finished the swim 78th of 103, almost 30 minutes behind the first swimmer, but that’s OK.
And to prove the swim was easy and comfortable: my T1 was 2:53 (9th best), and I passed 19 people in T1 to start the bike in 59th place. So far the race was going really well, everything I could hope for.
One lesson learned: I really can improve my swim, and to do that I need to swim more. If I hate swimming in a pool, I need to find a way to swim more in open water.
Swim log: 3,862 m in 1:20:47, 2:06/100m.
Bike
My bike post never made it into the archive. What I know from the run post: the course was hard and long, I felt like I’d done pretty well on fueling and pacing, and I started the run in 13th place overall at about 2:30pm. (A year later I wrote that this race took me 12:38 in all.)
Run: hubris
When I jumped off my bike and headed into T2, I got a small hint that I wasn’t at 100%. My legs felt a little funny. Last year we handed our bikes to volunteers; this year we had to re-rack them ourselves, and although I’d painted a mental map of the bike area that morning, I ran down the wrong row and had trouble finding my stall. In the T2 tent I saw the Masters racer I’d been trading places with on the bike. He had dropped me 5 miles earlier, and he looked like he was hurting. That probably should have been a sign to calm down and take a short mental break before heading out.
The problem was I had a checklist of goals in my head. Finish? A no-brainer, it was only 2:30pm. Beat last year’s time? A lay-up. No, I was worried about my big goal: finish in 11 hours. By my calculation I had exactly 3.5 hours, and I’d just run a half marathon a couple of weeks earlier at 7:37 pace. OK, the truth is I was skeptical as hell. I was going to have to run hard. Coming out of the tent my Dad said something like “Looking good!” and I think I barked back “Feeling bad!”
Then my Forerunner didn’t pick up a satellite signal. A quarter mile in it found one, and a tenth of a mile later it lost it again. Without it I had no sense of how fast or how far I was running, and that started messing with my head fast. I felt bloated, my fuel belt was too tight and too heavy, so I took a quick bio-break at the first aid station. At the first mile marker the watch said 13 minutes. Mile 2: 24 minutes. At that rate I wouldn’t even match last year’s time. So there I was, 2.5 miles into my Ironman run, and I had given up on every goal except the one that seemed like a gimme.
Ironman will force you to see your deepest inner truth, and the truth I was faced with that day was hubris. I had just assumed I was going to run 8-minute miles: I did all my run training at that pace or faster, and I thought it would be hard but totally doable. Ironman wasn’t going to let me get away that easily. It was going to make the next 25 miles unbearable, and make me earn my finish.
I dropped my fuel belt at the second aid station, about mile 2.5. It was bouncing against my back and hips, and it was clear I wasn’t in control of my run anymore. From there on I was in survival mode. The crowds were wonderful: “You’re doing great!”, “Looking good!” A couple of times I answered “Thanks, but I don’t feel so good,” and every time I thought that, Ironman made a point to hit me a little harder.
I never even considered that, at that point, I was first in my age group. If I’d just said “OK, I’m not making 8-minute miles, so go run the same run you ran last year,” 10:24 a mile, a very reasonable pace, I would have finished 2nd in my age group, on the podium, and about 14th overall. At a more modest 9-minute pace from the start, I’d have broken 12 hours and won my age group.
I don’t want to sound like I’m beating myself up. My wonderful wife told me not to dwell on it and over-analyze it, and I thank her for that. I’m simply admitting my mistake. I’m not willing to admit that a sub-11-hour Ironman is out of my reach; if anything I’m more convinced than ever that I can do it. But I need to be more thoughtful and respectful in how I approach it. Jeff thinks I was under-trained on long efforts: last year I did several sessions longer than 8 hours, and this year I did none. Maybe he’s right.
Run log: 5:08:02 (the Garmin said 27.25 miles after losing its signal), started at 2:40pm.