Haha, look at what my Garmin data shows for the bike route. There are two such detours in my route from the Beach2Battleship bike. Except I really ducked into the woods, rather than used a porta potty! (I totally stole the idea for this graphic from David Carr, a guy I met at the parking lot at Special needs dropoff, and later connected with on Facebook!)
Swim data:
I wore the Garmin 310xt during the swim on the inside of my left wrist. The Garmin 310XT is waterproof. However, it is not accurate in the water. It shows I swam in a very zigzag pattern and went over 4 miles! Fun to see the path, anyway. In retrospect, I wish I had not worn it for the swim. It annoyed me on my wrist. And, when the wetsuit stripper pulled my sleeve off, the Garmin wriststrap broke (even tho I told the guy to please be careful of my watch!). That left me dealing with how to carry it the rest of the race!
Swim data at Garmin site here: http://connect.garmin.com/activity/18343451
Bike Splits:
I used the Garmin on the bike, too. I had stuffed it into my back pocket, since the strap had broken. It was set to beep every 15 minutes to remind me to eat my nutrition. That was great! I didn’t realize it was also set to autolap every 10 miles. I’m glad, because this data is fun to see.
Split
|
Time
|
Distance
|
Elevation Gain
|
Elevation Loss
|
Avg Speed
|
Max Speed
|
Avg HR
|
Max HR
|
Calories
|
---|---|---|---|---|---|---|---|---|---|
Summary | 06:11:02 | 111.57 | 11,423 | 11,428 | 18.0 | 40.9 | 139 | 164 | 2,620 |
1 | 00:31:12 | 10.00 | 757 | 733 | 19.2 | 24.9 | 150 | 164 | 254 |
2 | 00:29:57 | 10.00 | 495 | 447 | 20.0 | 28.3 | 147 | 158 | 275 |
3 | 00:29:46 | 10.00 | 615 | 533 | 20.2 | 27.7 | 150 | 157 | 222 |
4 | 00:31:05 | 10.00 | 1,765 | 1,365 | 19.3 | 33.7 | 145 | 154 | 182 |
5 | 00:33:53 | 10.00 | 2,024 | 2,520 | 17.7 | 40.9 | 137 | 148 | 152 |
6 | 00:31:57 | 10.00 | 1,131 | 1,149 | 18.8 | 23.6 | 134 | 144 | 232 |
7 | 00:35:31 | 10.00 | 3,223 | 3,094 | 16.9 | 24.2 | 135 | 150 | 332 |
8 | 00:32:58 | 10.00 | 522 | 642 | 18.2 | 23.7 | 137 | 145 | 219 |
9 | 00:33:28 | 10.00 | 331 | 351 | 17.9 | 22.2 | 138 | 149 | 281 |
10 | 00:34:04 | 10.00 | 287 | 299 | 17.6 | 20.7 | 137 | 146 | 216 |
11 | 00:34:31 | 10.00 | 174 | 215 | 17.4 | 24.5 | 138 | 150 | 211 |
12 | 00:12:35 | 1.57 | 100 | 79 | 7.5 | 25.5 | 122 | 153 | 44 |
You can see how my average speed went down in the last 30 or so miles due to a strong headwind. Actually, I fared very well here compared to alot of folks. I am good at hunkering down into a tight shape when going against the wind. My arms were sore for days afterwards simply due to pulling them in tightly toward the centerline of my body. Also, I was wearing a brand new Rudy Project Wingspan helmet. The Wingspan’s designer, John Cobb, is a blog reader and he kindly loaned it to me. They are not yet available for purchase, but will be soon! More about that later!
Full bike data here: http://connect.garmin.com/activity/18343455 (click the Play button, soooo cool!)
Run Splits:
I carried the Garmin in a ziploc bag filled with things like Rolaids and Advil with me on the run. It was set to autolap and beep every mile. That reminded me to drink some water from my own water bottle. That worked great too, tho, I guess I was not drinking enough since I ended up dehydrated. Luckily, that did not affect my race performance.
You can see that I went out too fast in the first mile – then realized it, and backed off a little. I really was feeling great for the first 6 miles. I didn’t feel like I was going too hard, and I was stopping at each aid station drinking and eating an orange slice. Those orange slices really got me through the marathon.
Split
|
Time
|
Distance
|
Elevation Gain
|
Elevation Loss
|
Avg Speed
|
Max Speed
|
Avg HR
|
Max HR
|
Calories
|
---|---|---|---|---|---|---|---|---|---|
Summary | 04:34:36 | 26.59 | 7,782 | 7,780 | 10:19 | 06:07 | 153 | 162 | 1,908 |
1 | 00:09:08 | 1.00 | 218 | 100 | 09:08 | 07:29 | 154 | 161 | 75 |
2 | 00:10:27 | 1.00 | 172 | 239 | 10:27 | 07:45 | 150 | 158 | 83 |
3 | 00:09:25 | 1.00 | 241 | 302 | 09:25 | 06:55 | 153 | 157 | 77 |
4 | 00:09:51 | 1.00 | 225 | 249 | 09:52 | 07:26 | 156 | 160 | 82 |
5 | 00:09:57 | 1.00 | 215 | 203 | 09:57 | 08:10 | 153 | 157 | 80 |
6 | 00:09:55 | 1.00 | 356 | 299 | 09:55 | 06:46 | 154 | 157 | 81 |
7 | 00:10:17 | 1.00 | 426 | 469 | 10:18 | 06:07 | 153 | 156 | 81 |
8 | 00:10:38 | 1.00 | 469 | 461 | 10:38 | 07:44 | 151 | 155 | 76 |
9 | 00:10:07 | 1.00 | 392 | 371 | 10:07 | 07:22 | 152 | 155 | 69 |
10 | 00:09:56 | 1.00 | 240 | 238 | 09:56 | 08:34 | 152 | 157 | 69 |
11 | 00:10:35 | 1.00 | 398 | 340 | 10:35 | 07:45 | 152 | 160 | 73 |
12 | 00:09:46 | 1.00 | 139 | 243 | 09:46 | 07:53 | 152 | 156 | 68 |
13 | 00:10:27 | 1.00 | 128 | 140 | 10:27 | 08:19 | 153 | 159 | 72 |
14 | 00:11:45 | 1.00 | 224 | 136 | 11:45 | 08:06 | 151 | 159 | 72 |
15 | 00:10:03 | 1.00 | 181 | 179 | 10:04 | 08:33 | 155 | 159 | 72 |
16 | 00:10:29 | 1.00 | 230 | 290 | 10:29 | 08:09 | 153 | 158 | 70 |
17 | 00:10:44 | 1.00 | 364 | 381 | 10:45 | 06:55 | 154 | 160 | 72 |
18 | 00:10:19 | 1.00 | 327 | 262 | 10:19 | 08:02 | 154 | 157 | 69 |
19 | 00:10:28 | 1.00 | 403 | 442 | 10:28 | 07:38 | 152 | 156 | 63 |
20 | 00:10:52 | 1.00 | 363 | 375 | 10:52 | 07:40 | 152 | 156 | 65 |
21 | 00:10:18 | 1.00 | 432 | 472 | 10:18 | 07:23 | 155 | 158 | 72 |
22 | 00:10:30 | 1.00 | 366 | 348 | 10:31 | 08:08 | 154 | 157 | 66 |
23 | 00:10:39 | 1.00 | 243 | 215 | 10:39 | 07:56 | 154 | 156 | 68 |
24 | 00:10:39 | 1.00 | 521 | 512 | 10:39 | 07:04 | 153 | 158 | 61 |
25 | 00:10:17 | 1.00 | 323 | 331 | 10:18 | 08:35 | 154 | 158 | 65 |
26 | 00:10:48 | 1.00 | 106 | 94 | 10:49 | 08:20 | 154 | 158 | 67 |
27 | 00:05:59 | 0.59 | 81 | 86 | 10:05 | 08:09 | 157 | 162 | 40 |
Can anyone guess why my run pace slowed after mile 7????? Mile 14 included stopping at run special needs. I did not pee at all during the run. My goal for the race was to do the marathon in 4:35. I can’t complain about this run at all (well, except for the pain part, but the memory of that is beginning to fade.)
As you can see above, my Garmin is showing that the run course was 26.59 miles. A BT buddy said his Garmin agreed with that! So I ran an extra 0.39 miles in agony. Yay. Not. Garmin shows a pace of 10:19 for the entire run. Given that I was stopping every 1/2 mile to grab an orange slice and sometimes also a cup of water, this is really great. I had not originally planned on stopping every aid station the whole run, but my pain made me need it. Whatever works to keep you going in relentless forward motion. It’s all good. Or maybe I should say it’s all bad. hahahaha!
Full run data here: http://connect.garmin.com/activity/18343464
Misc Notes:
When I tripped at mile 17 in the dark, my knee was not the only thing injured. The lens of my new Garmin 310xt cracked. I have sent it back to Garmin for repair. I do have to pay a small repair fee since a cracked lens is not covered under warranty. And I am taking two weeks off working out, so I don’t really need it for a little while. I was so glad that I was at least able to get this data!
I don’t think the waterproof feature is worth buying a 310xt over a 305. However, the 305 only stores 10 hours worth of data. So, if you are doing an Ironman race, you really need the 310xt, which stores 20 hours of data. Even if you just want it for the bike and run, 10 hours is not really enough unless you are blazing fast! I want to get a quick release kit: https://buy.garmin.com/shop/shop.do?pID=8544
I did not look at my heart rate much at all during my race. I originally planned to. However, I was using the Tylenol Severe Sinus medications, which artificially raises the heart rate. So, I really could not trust the heart rate data, so I just went by breathing and feel of my body. If I ever do another Ironman, I will use the Garmin 310xt again, only during the bike and run. And, I will look at heart rate data. But remember, if heart rate data looks off, go by the feel of your body and your breathing. Lots of things can impact heart rate during a race!
There is an awesome review of the Garmin 310xt here: http://dcrainmaker.blogspot.com/2009/09/garmin-forerunner-310xt-in-depth-review.html
Congrats Carol, awesome job!
Some day I hope I´ll finish an Ironman
I liked seeing the splits. Too bad about the watch. It seems cursed. Other than the swim, do you find it good and accurate? Any problems with the heart rate not be accurate or going wonky at times?
B
Very interesting! the port o potty graphic is great 🙂
Rock star! You did really well in all three sports, Carol!
I like how you swam 200 feet below the water level. That’s one way to avoid all the “traffic”! ;-). Congratulation on a great accomplishment and time!