Friday, August 18, 2006
2006 Ironman Lake Placid
| Event | Time | Rank OA (of 2160) | Rank AG (of 418) |
| Swim | 1:05:10 | 418 | 104 |
| T1 | 6:00 | 239 | 55 |
| Start Bike | 1:11:10 | 360 | 86 |
| Bike | 5:20:16 | 34 | 2 |
| T2 | 2:42 | 129 | 32 |
| Start Run | 6:34:08 | 57 | 10 |
| Run | 3:41:24 | 153 | 36 |
| Overall | 10:15:30 | 87 | 18 |
Warm-Up
What am I doing back in Lake Placid for the Ironman? In 2002 I thought I'd try an Ironman and intended to be "one and done" with that distance. That race didn't work out as planned, so I tried again at Lake Placid in 2004. Once again, the race didn't go as planned. Stubborn or stupid - take your pick - but here I am on the morning of July 23 having another go at it in 2006.
With respectable times of 11:27 and 11:14 under my belt it's somewhat difficult to explain to people that I'm at it again because I feel like Ironman has beaten me. While I've completed the distance, in both races I blew up on the run, with the marathon changing from a run to an exercise in survival as I fought cramps and stomach issues from the early miles on. So, although I have two Ironman finishers medals, I felt like I had not conquered Ironman, but rather, it had gotten the best of me.
With these two humbling experiences behind me, I went into the 2006 Lake Placid event with just one primary goal in mind, and that was to hold up on the run, to not have the marathon turn into a shuffle-walk battle just to get from one porta-potty to the next. I knew that if I managed to run the marathon, even if at just a slow trot, that my overall time would be solid and certainly under 11 hours. Deep down I knew that I was capable of actually running the run and that it was possible I could get down to the 10:20 ballpark which historically would put me on the bubble for a Kona spot for the 35-39 age group.
After analyzing my two prior experiences I came to a conclusion of what I had done wrong. First that I was consuming too many calories on the bike, and while it didn't create any issues for me on the bike, the symptoms were appearing early in the run after my stomach had essentially shut itself down. As a big guy with a pretty big engine on the bike I had always assumed I needed more fuel than the little guys. But, in researching the symptoms of my blow-ups and analyzing my caloric intake in those events, I concluded that the 450-500+ calories per hour I was consuming was the likely cause of my stomach distress. So, during training I experimented by decreasing my calories per hour until it was clear I was deprived and had bonked. I found that I had no energy issues until I got down to below 250 kcal/hr, so in training and racing I settled on 300-325 kcal / hr and never encountered any low energy problems.
The second conclusion that I came to was that my cramping was primarily due to dehydration. It occured to me while riding in Spain this spring that other riders needed to stop and pee frequently while riding and I virtually never felt that need. And, never during a race had I needed to go, while others were discussing whether they pull over and hit the woods or just go right on their bikes, a dilemma I'd never needed to worry myself about. I've always been a very heavy sweater, and while I've always thought I've been drinking adequate amounts of water, I now concluded that I was actually dehydrating myself and was hopeful that was the root cause of my chronic cramping problems.
Based on these conclusions I decided that in training and races in preparation for Lake Placid that I would consume a steady 300 kcal per hour of liquid fuel and augment that with however much water it took such that I felt the need to urinate during the bike leg. I tested this approach with success at the Mooseman 1/2 Ironman in June. I had no energy issues on the bike at my lower caloric intake, and had to pee during a race for the first time ever late in the bike leg. But the best part was that my running legs felt good and not once during the run did I have any stomach issues or feel any cramps coming on. This bode well for Lake Placid, but I had still had doubts whether I had my problems figured out as in 2004 I had managed a sub 4:30 1/2 IM with a 1:28 half marathon, so a successful tune-up 1/2 IM with a good half marathon proved to be no guarantee of running success at the Ironman.
Nonetheless, it was with this new approach of eat-less and drink-more that I went into Lake Placid confident that I could finally conquer this distance.
The Race
As in 2004, I went into Lake Placid healthy and fit - particularly on the bike. I'd spent a month on my bike in Europe in March, had done a week of intense training in the mountains in June, and had numerous quality, long rides under my belt. My running had gotten a late start due to calf and achilles issues through the winter and spring, but due to my solid biking fitness I had been able to step up the distances pretty quickly and was running well and had gotten in lots of long runs and bricks in the final two months leading up to the race. I even had some secret hopes for a swim near an hour as my swim workouts had been showing good progress. So, just like in 2004 I toed the starting line healthy and very fit and confident I was capable of a good day.
Swim
The swim was entirely unpleasant. For an entire 65 minutes I got hit, kicked, and never found a comfortable swimming rhythm. I don't know if it was due to the 300 additional people that started the race than in 2004 or if it was because the kayakers prevented us from going as far left of the buoys as I recall going in 2004 to find open water, but whatever the cause this swim was too crowded and never eased up, not even on the second loop. I felt fine and tried to remain calm, but I did not enjoy one second of the swim. One conclusion I've come to is that in a race this dense you have essentially determined your swim fate by 5 minutes into the swim. After that point you are pretty well stuck at the pace of the masses you are with. At times I felt like I was swimming too slowly, but there was no way to find any clear water to swim past the masses around me, and the people around me weren't swimming so much more slowly than I wanted to go that I could, or would, just swim right over and through them. This year, my mantra throughout the race was to be patient until the marathon, but I do wish I had taken it out a bit harder the first five or so minutes of the swim to put myself a bit further up the field before everyone settled in. But, after all, what's a few minutes here and there in an Ironman? Ha, I'll find that out soon enough.
I exited the swim in 65:10 for 464th overall and 104th in the age group, about 50 seconds slower than 2004.
Bike
I felt phenomenal early in the bike and had to work very hard to remain patient and not worry about the people passing me. Two years ago I had a great bike split and had thought I felt comfortable, but after considering my run blow-up and that I had the 47th fastest split of the day, I had concluded that I had biked too hard and must take it a little easier this time around.
Leaving transition I saw my always reliable bike computer had chosen this moment to cease operation, so I was going to be doing this ride completely by feel. Early on I worried I was perhaps taking it too easy as plenty of folks were passing me, but I kept repeating my mantra of taking it easy until the run. On the fast, wet, and treacherous descent into Keane I heard a thud next to me and looked over and saw one of my two bottles full of my calories skidding along on the road beside me. I didn't even hit a bump, how did I throw a bottle?!? It turns out a bolt had broken and my cage had flipped around and was now pointing down. Luckily I had a backup gel flask with me so my entire nutrition strategy was not sliding along the road at 52mph beside me in that water bottle, but the loss of a bottle cage did screw up my plan to take a bottle of water at each aid station and drink it between aid stations. No worries, I could always do like the Tour de France riders and find some space down the back of my jersey or shorts, or I could just try to swig down the entire water bottle during the length of an aid station and immediately discard it, which is mostly what I ended up doing.
The first loop was very, very easy and quite enjoyable for the most part. The amount of blatant, intentional drafting that I saw was really very disappointing. I realize that when you swim 65 minutes there are going to be lots and lots of cyclists around and it's going to be hard to avoid some unintentional drafting early in the bike leg. But, there were some large, dense packs of riders, and on one occasion I got passed by a group of 5 riders in a rotating paceline, something I had never seen in a race before. I tried not to get worked up by this and to race my own race, but I did bark a few choice words to some of the worst offenders at times, and on the 2nd loop when things had thinned out and I passed many of these riders back I voiced my opinion a few times with comments like: "A little harder when you don't have a wheel to suck, huh?" or "Awww, too bad, looks like your peloton shattered, tough to be on your own, isn't it?" Immature, yes, but it just pisses me off to see this blatant cheating. I mean, if you're going to cheat, why not just cut off part of the bike course or hand your chip to someone to do the run for you. Really, what's the difference? Ironman tried a new approach of on-the-course penalty enforcement this year, so there were four penalty boxes on the loop where you had to stop and wait for four minutes if you had been tagged by a marshall for drafting. This process is fine in theory, but I saw a lot of drafting going on, and not once did I see anyone who had been caught waiting out their penalty in the box.
Back to the race. The first loop was effortless and the day was turning into a perfect day for racing as the early rain had cleared and clear skies were starting to break through the clouds and the temperature remained cool. I checked the race time as I finished the first loop and calculated my loop time to be 2:35. Yikes, that's identical to 2004 and I was trying to ratchet it back on the bike this time around. But, I was riding by feel and I felt great, so I continued at the same effort. The 2nd loop was eventless; I felt great and I was peeing regularly, so clearly my hydration strategy was working. And, yes, I was peeing while still on the bike, can't waste any time by stopping! By the last ten mile climb I was starting to feel ready to get off the bike, but the legs were not tired, nor did they feel like cramping was imminent like in 2004. At this point there are few cyclists in sight on the road, and at one point I looked down at my rear disc wheel because it was making some godawful screeching noise and I was worried the entire wheel was going to fly apart or something tragic (in hindsight I think the noise was my broken bottle cage rubbing against my CO2 canister, though it sure sounded worse than that). Lo and behold, what do I see when I look back at my wheel, but someone elses front wheel about one inch off my rear wheel. Someone I had passed miles back had decided to latch on for a free ride back to town. Pissed off once again, I pull left, slow down and ask if he could possibly get any closer. His response: "It's alright. I'll share. You want me to pull for awhile?" "It's alright!!" He actually said that to me as he drafted off of me, acting as if he's surprised that I'm pissed off. Seriously, is this standard operating procedure for the folks racing on the Kona bubble? Infuriating.
I finished the bike in 5:20:16, 21mph, 34th fastest of the day (28 pros in race), and 2nd fastest in my age group, and 1:22 faster than 2004. I'm still in disbelief of that result as the bike felt easy all day and I had to force myself to hold back for the run. Did I go too fast? Should I have gone harder and stolen a few more minutes with what has clearly become my strength? It's so hard to know in an Ironman.
Run
I started the run in 57th overall and 10th in my age group (11 Kona slots), although I didn't know that at the time. What I did know was that I was having a virtually identical race to 2004. In 2004 I swam :64 and biked 5:21 (2:35, 2:46 loops), and now I had just swum :65 and biked 5:20 (2:35, 2:45 loops). Indeed, my transitions were nearly identical as well, and I started the run a whopping 29 seconds ahead of my time in 2004. I recollect thinking as I started the run that it was deja vu all over again, and that I would be seriously dejected if the marathon also turned out the same as 2004.
My legs felt a bit heavy, but all in all I felt pretty good starting the run. I settled into a comfortable pace and reminded myself to be patient when someone in my age group flew past me in the first mile. My marathon plan was 250 kcal/hr of gel and a few cups of water at every aid station. I made it to the first turnaround at mile 5.6 and the legs still felt good and no stomach issues brewing. A milestone! By this point in 2004 I had already cramped up and vomitted and hit the porta-potties. I was just under 41 minutes at the 5.6 turnaround, comfortable at about 7:30 per mile, a bit faster than I expected to be able to maintain, but it felt good and I was being passed more than I was passing so I proceeded running by effort and tried to not worry about time or position.
Then Mile 8 came. Maybe I had fallen behind on my gel consumption, or maybe I just needed more calories than I had expected, but I started to bonk right as we got to the hills on the return trek. Luckily too few calories is easily rectifiable whereas too many is not, so I took a large swig of gel and went on a major shopping spree at the next aid station, and before too long I had my energy back. But, I did not have my legs back. Whether it was the hills, the bonk, or it was just time to start feeling it, I realized somewhere around Mile 8-9 that the marathon wasn't going to forever remain as easy as it been the first 8 miles. Those sub-7:30 miles became 8 minutes became 8:30. I got back to town, struggled up the hill, and finished the first loop in 1:42:47.
However, I now had 13 miles yet to go and I was already in survival mode. But my feared stomach and cramping problems had not presented themselves, so I was still running, with my legs being the only limiting factor. I had always figured that even with tired legs I could manage 8 minute miles, but due to the cramping and stomach issues had never been able to test that. Well, now I was learning that I may have been a bit optimistic and my dead-leg shuffle is closer to 9 minute miles. Nonetheless, that still counts as running, and for the next 13 miles I gut-checked it at my agonizing 9 minute mile shuffle just trying to get to the next milestone: the bend in the road ahead, the next mile marker, the next aid station, the lightpost up ahead, the turnaround, catch John Mead, catch Haig, .... It was a long time to operate in survival mode, and I spent longer and longer at each aid station and walked about half of each of the two big hills, but more or less I held it together the entire second loop.
One nice thing about a two loop course with two out-and-backs per loop is that you get to see a lot of people, and I definitely got boosts during this agonizing stretch from all the folks out there I knew: Ted, Tom, Schwartz, Haig, Jenni Banks, Jeff Emmons, all the Team Zers, Laura, and great spectators: my folks, Brady, Tara, Bruce, Libby, Vaughn. And it was definitely great to wear the TeamZ colors as they had hundreds of fans cheering with endless energy! When you're struggling just to get one foot in front of the other, knowing all those other racers out on the course and having so many great spectators makes a huge difference!
I pushed it with everything I had all the way until I was on the finishing oval. Now I wanted to savor the finish and just cruise home enjoying the moment, but at 10:15 I figured I was on the bubble for a Hawaii spot so I looked back to make sure I wasn't about to be passed right before the line. Sure enough, there was someone eyeing me up and looking to make a late move past me. 140.5 miles complete and no chance to cruise in and enjoy the final 0.1; I had to hustle it around the oval and all the way through to the finish. It turns out the guy was indeed in my age group but it would have had no bearing on Kona anyway had he passed me.
I was absolutely spent when I crossed the line. I had left everything I had on the course and had finally conquered the Ironman distance. I ended up 87th overall and 18th in the age group with a 10:15:30. My run split was 3:41:24, good for 153rd overall and 36th in the AG, and a fantastic improvement over the 4:40:10 of 2004.
Post-race
I was completely wiped out, but for the first time I did not need the medical tent or an IV. I recovered pretty quickly and stuck around the finish and the TeamZ cheering area all the way until the midnight finish party, another first for me. It was great to watch so many people I knew completing the race, and for many of them it was their first Ironman. Incredible!
My 10:15 finish time would have been fast enough to get a slot in M35-39 every previous year. My age group place of 18th would have gotten a slot in every previous year except 2005. But, not so in 2006. There were only 11 slots (of 418 M35-39 starters) and these slots only went as deep as 13th place, who finished in 10:09:33, a bit less than 6 minutes ahead of me. The number of participants at Lake Placid is increasing every year, but they have decreased the total number of Kona slots for the race from 100 to 80 to 72, so it is getting harder and harder to qualify. But, that's part of the appeal; if it were easy it wouldn't be as meaningful.
While I was pleased that I held up well on the run and actually ran the marathon this time and managed a respectable 3:41, a post mortem reveals that I lost my ticket to Hawaii on the run. I started the run in 10th and fell to 18th by the finish. I passed only two who started the run ahead of me, but got passed by ten. Indeed, I remember during the rough patch I hit between miles 8 and 10 a parade of six straight in my age group rolling past. Clearly these people were racing each other and knew they were racing for Hawaii while I was focused on racing my own race.
Warm-Down
As time passes I remain thrilled with my effort. I'm ecstatic that I finally conquered the distance and figured out my stomach and cramping problems. And I still find it hard to believe that I went 10:15 on a very difficult Ironman course.
But, I'm also starting to wonder if it's more than bad luck that I always seem to be a just-missed guy. Am I chronically unlucky or just not good enough or simply not tough enough when it counts? In high school I never made the state championships in track and xc, though by all metrics I was fast enough that I should have managed it. In college I surprised myself by coming painfully close to the NCAA Championships qualifying time, but never managed to get over the barrier. And now I miss Kona by the skin of my teeth in a time that would have been good enough any other year.
Surely I could have managed six minutes faster. How did all those guys outrun me? I'm a runner and I don't have the cramping or stomach excuse this time, yet I got run down. There's no holding back on the run; couldn't I have stuck with the guys in my age group when they passed me? Did I really need to walk half of the last two big hills or spend so much time at the aid stations? Why couldn't I manage at least a 3:35 marathon like the rest of the contenders? Was I just not mentally tough enough on the run? Did I bike too hard? Did I do too much bike training and not enough running? And, just think if I could only learn to swim just a few minutes faster! Oh, so much to ponder as I watch the Kona broadcast on TV once again this year.
So I planned to be one and done with the Ironman distance. It took me three tries until I got it right, so it's time to be done with this distance. But now I find myself within spitting distance of qualifying for Kona. What to do, what to do......
My flickr photo album of the day can be accessed here. Many thanks to Dan Hicok who took many of these photos and was the official photographer for TeamZ. His entire portfolio from the long day at Lake Placid can be accessed here.
Sunday, August 13, 2006
The 0th Annual SavageMan Triathlon
RSVP here for SavageMan, please. Please specify in the RSVP comments whether you intend to participate, whether you expect to attempt the full SavageMan, the MeekMan, some combination of the two, or would like to volunteer instead.
Welcome to the information page for the 0th Annual SavageMan Triathlon, to be held on Saturday, October 7.
- Q: What do you mean by "0th Annual"?
A: 0th Annual means that the 2006 event is an invitation only "Course Preview" for what may or may not become an annual event on a larger scale. This year the event is not a race, it is an unofficial, unsponsored gathering of a few dozen invited trial participants who just happen to do a swim, bike, and run workout on the same course on the same day. If all goes well and participants in the 0th Annual running agree that the venue and course are ideal for a recurring event, I will either pursue making SavageMan a legitimate race or hand off duties to a veteran race director. - Q: There are lots of organized races that provide me schwag, awards, food, Kona slots, fast times, etc.... Why would anyone want to do an unofficial, unsupported event that provides none of these?
A: If you love swimming, biking, and running and like to challenge yourself, you will love SavageMan. The challenge in SavageMan is not to beat your PR -because you won't, or qualify for Kona -because you won't, or win your age group -because no one cares, it's to conquer a very challenging, beautiful course and enjoy an absolutely beautiful area ideal for swimming, biking, and running. All that and because it's free, that's why. - Q: Where and When is SavageMan
A: SavageMan will take place in Garrett County in the heart of the Allegheny Mountains in very western Maryland. The terrain in this region is absolutely ideal for triathlon training and the area is just begging for an event. The only other events remotely near this region are a 1/2 IM in Morgantown, WV, an hour west, and the Rocky Gap offroad triathlon in Cumberland 30 minutes east. And neither of these are truly in the heart of the Alleghenies.
The swim will take place in clear and beautiful Deep Creek Lake, a popular lake vacation destination less than 3 hours from Washington, DC (directions here). Much of the run course will take place in Deep Creek State Park. The bike course will tour through Garrett County, touch into West Virginia, and head through scenic Savage River State Forest.
The 0th Annual SavageMan will take place on Saturday 10/7. Mornings will be cool that time of year in the mountains, so start time is 9:30am, which also allows those who want to drive up morning of from DC time to do so.
Additionally, SavageMan will be held on a Saturday morning to allow people to enjoy the lake and surrounding area for the rest of the weekend if they desire. If enough people are interested, on Sunday I will lead an incredibly beautiful 70 or 105 mile ride, depending on starting/ending location, into the Monongahela Natl Forest in W. Va. Leaves should just be starting to turn, which will make a stunning ride even more so. - Q: How far is it? Will it be hard?
A: SavageMan is a road 1/2 Ironman distance triathlon. Yes, it will be hard. It will be the toughest triathlon course you have ever done. If this event ever becomes an open race it will be billed as "The World's Toughest Half Ironman" and there won't be many who complete it who disagree.
The purpose of the 0th Annual Savageman is to get people to preview a potential 1/2 IM course for future years. Many folks, however, have other fall events they are training for, or for various reasons do not want to do an entire, very difficult, 1/2 IM course in October, so MeekMan distances of 25 mile bike and 10K run will be available as well. If you are not a true savage, but still want to get a feel of SavageMan and the terrain, feel free to partake in the shorter distances. - Q: Why the name "SavageMan"?
A: A number of reasons:
First, the course is a true beast. Only a real savage can conquer this course. One driver behind the creation of SavageMan is to devise what can reasonably be advertised as "The World's Toughest Half Ironman". A few other triathlons make this claim and based on their descriptions and elevation maps it is not a stretch to claim that SavageMan is even tougher. The only race that legitimately looks tougher has the swim at the bottom of l'Alpe dHuez and the run at the top, but a point to point race up a mountain is hardly a fair comparison.
Second, the bike course crosses Big Savage Mountain twice and rides along the Savage River and through Savage River State Forest. Big Savage Mountain also happens to be the Eastern Continental Divide, and yes, it is a savage of a climb.
Third, and most importantly, SavageMan sounds cool. - Q: Cool. How do I register?
A: You don't register. But you do RSVP. Anyone interested in participating or volunteering, please RSVP to the evite here. Please specify in the RSVP comments whether you would like to participate, whether you expect to be a SavageMan, a MeekMan, some combination of the two, or would like to volunteer instead. - Q: What can I expect from the swim leg?
A: The swim will be uphill and into a current. No, the swim will be quite easy and pleasant. The lake is calm, clear, and beautiful and perfect for a triathlon. The start at the public beach at Deep Creek State Park is right at the end of a cove narrow enough to keep boat traffic out and the water calm. The swim will be 0.6 miles into the cove, around a giant inflatable turtle, and back again. This will be the most enjoyable part of your day, so swim slow and make it last. Water temps in early Oct will likely be in the upper 60s. - Q: What can I expect from the bike leg?
A: The bike is a one loop 56 mile course that will be something very similar to this loop here. The bike leg is what makes SavageMan fit only for a true savage. I make only 3 assurances about this course. 1: It is 56 miles. 2: The majority of the roads and scenery are stunning and have very little traffic, and 3: It is very hilly and very hard and includes a hill steeper and harder than the king of climbs in all of triathlon: The Beast in St. Croix. This is very likely the only road bike course with a hill so steep that it is highly probable you will fall off your bike if you attempt it. That's right, IF you attempt it. This is also very likely the only course in which you have an option to go straight up a hill or to take a longer way around to get to the top in order to avoid falling over or walking up the hill. And, unlike other races that give special prizes to fastest splits of the day, this event will give a special prize to everyone who conquers The Wall without falling off. If you like a challenge, you will like this course.
The bike course starts out with about 9 miles of good rolling hills to get you warmed up. Then you climb Backbone, as the locals call this stretch of Big Savage Mountain, from the west side which means you only have to climb about 700 feet in a bit less than 2 miles. A few miles of rollers takes you past many truck warning signs indicating that the dropoff is approaching and brings you to what is very likely the fastest long descent you will ever ride. The road descends straight ahead at a 9% grade for 4 miles, dropping 2000 feet without a twist or bend in the road to give you any reason to consider your brakes. There is a wide shoulder, but as you'll likely be exceeding the speed limit of 50mph for cars and 10mph for trucks it's best to take up your lane of traffic and enjoy the fastest 4 miles you'll ever ride. Video of the descent here (46MB, 5:40). Once at the bottom you're in West Virginia and have about 2 miles of flat road until you enter Westernport where you learn that what goes down must go up - only more steeply.
Then the fun begins. Over the next 6 miles you will climb 2100 feet, but at least 2/3 of that occurs in the first and last mile. You will climb through the town of Westernport and perhaps wonder why they built a town on a cliff. Then you can decide whether to go staight up the road so steep that it's long since been closed to traffic, or go around the block to get up slightly more gradually. Once out of town it keeps going up and up until it mercifully flattens out for you and you've climbed 800 feet in just a mile for a 15% avg. grade. Video of this first part of the climb here (94MB, 11:33). The next 3-4 miles are flat and gradually uphill, but give you a bit of a chance to recover. Then after you think maybe it's all not so bad after all the road starts to get steeper and steeper and then yet steeper still. But, while it's steep and it's hard it isn't all that long so before too long you're over the top and you've conquered Westernport Road. Video of this second part of the climb here (88MB, 10:52)
Then, it's a narrow, twisty, 3-4 mile descent down the other side and into Savage River State Forest. Video here (40MB, 4:59). Finally a bit of mercy as the next ten miles are about the only flat ten miles in all of Garrett County as you ride through the Savage River State Forest along the scenic Savage River. But lest you think you've paid your penance in suffering, you still must climb out of the Savage River valley. If you can see through the sweat in your eyes or manage to look anywhere other than 6 inches in front of your wheel, do so on this 4 mile 1500 foot climb as the road and the scenery are gorgeous. Once over the top it's just another 7-8 miles of rolling terrain until you're back at the lake.
The 25 mile MeekMan bicycle option will not take you over Big Savage Mountain or through Westernport. Which is a real shame as the Meeklings will thus miss the highlight of SavageMan. But, the MeekMan bike is far from flat and easy. You'll have rolling hills and a nice descent which drops 1500 feet into Savage River State Forest and then you get to climb back out again. A very nice, scenic, and challenging ride, but not worthy of the SavageMan moniker. - Q: What can I expect from the run leg?
A: You can expect to start with tired legs, first of all. The run, by any normal measure would be considered hard and hilly, but in comparison to the just completed bike, is actually somewhat humane. It is a one loop course that consists of about half pavement and half trails. The trail sections vary from good dirt/gravel fire road to some poorly maintained single track. Trail shoes are not necessary, but racing flats would be ill-advised.
The MeekMan run will take you along the lake for roughly one mile, and then up a gravel fire road to the fire tower and back. - Q: This sounds AWESOME, but really hardcore. I want to do it, but am worried maybe it's too much for me. Do you think I can handle it?
A: That's for you to answer. If you don't think you're up for a hardcore 1/2IM at this point in the season, or you have other events you're focusing on but still want a taste of SavageMan, there is always the more sane MeekMan option.
The SavageMan course is indeed hardcore and the Westernport climb in particular is the real deal and very likely unlike any climb you've done before. There is no sag wagon, so once you're out there there is only one way back - under your own power! That being said, if you have enough gears you can get over all hills just fine. I know of plenty of very average (and less) riders who have gotten over Westernport and loved every second of it. I also know that Westernport has, on at least two occasions, brought very capable riders to tears. So, if you like a challenge, have enough gears for steep climbs, are prepared to be self-sufficient for a very slow 1/2 IM, then, yes, it is very likely you can handle SavageMan and will absolutely love it.
And, if you don't want to do the full SavageMan, there is always the MeekMan option. - Q: Wow, sounds fun in a warped kind of way. I want in, what do you expect from me?
A: First, RSVP here ASAP.
Second, as this is a trial run for what could become a real event, I want your feedback - real feedback - not just "Water was colder than I expected" or "Wish I had a triple crankset".
Third, I want you to come with proper expectations of what the 0th Annual SavageMan is, and that's an unsupported swim, bike, run event. Be prepared to be self-sufficient for food and water and mechanical issues. Have enough knowledge of the course and the turns so that you know what to expect next. The course will be marked, but not overly so, so it helps if you are expecting to see a left turn marker and are on the lookout for it.
Finally, I may request somewhere in the ballpark of $10 to cover any supplies I need to purchase like cones, signs, road paint, ... - Q: Crikey, those hills sound tough. What kind of bike and/or gearing should I have for this?
A: Some people like climbing on tri bikes. I don't, so I say if you have the luxury of choosing between a road and tri bike, choose the road bike. There is only one technical descent (the descent from Big Savage - if participating, please watch video here before race) which will have to be taken cautiously regardless, so bike handling is not a huge issue. Make sure your brakes work well. For gearing, if you have a triple ring or compact cranks this type of terrain is exactly why you have them. If not, you will want a 12-25 or 12-27 cassette. I typically ride a 39-27 in this terrain and use the 27 liberally. The first time I discovered these climbs I had a 42-23 and could only get over them by making switchbacks across the road (not the closed road; I've only gotten over that upright once - in my 39-27) and about fell over from lack of momentum a few times. Ted Waugh once rode out here with his rear derailleur broken such that he couldn't get in a gear easier than his 39-19. He amazingly made it over Westernport but his legs paid the price. By the end of the ride we found ourselves at the side of the road trying to fix his derailleur with tweezers and nail clippers. These hills are legit. If you are strong you will be able to get over in a standard 23 but would wish you had more gearing. If you are not particularly strong and show up with standard gearing you will find yourself suffering and possibly walking. - Q: A 1/2 IM with one loop bike and run courses is an awful lot to do self-supported. What can I expect in the way of support?
A: Expect little. In all likelihood a table with water will be left at the top of the Westernport Road climb, which is roughly halfway through the bike. It will be up to you to stop and fill your bottles. It will be up to you to furnish your own calories. Hopefully on the trail that runs from mile 5.5 - 10 of the run we will have someone with water patrolling on an ATV. You can expect signs or road markings for any turns on the bike and run courses. You can expect accurate 1.2, 56, and 13.1 distances for the SavageMan. The MeekMan course will be roughly 25 mile bike and 10K run, but less concern for exact accuracy will be taken. We will make sure your bike is secure during the swim and run. We will time you and do our best to get splits of the individual legs. We will provide "prizes" to anyone who gets up the steep, closed section of Westernport Rd without falling over or dismounting, as well as to anyone who can average over 20mph on the bike or under 1:40 on the run.
There will be no course marshals. There will be no draft marshalls. There will be no one manning intersections (there are really only 2 intersections of any concern over the 56 mile bike). There will be no sag wagon. This is not a race. It is a group of people doing swim, bike, and run workouts all on the same course. It is not endorsed or supported by the communities or the State Park. Set your expectations appropriately. If ever there was an event to wear a CamelBak on the bike or run with a FuelBelt, this is it.
Expect a challenge, a beautiful course, and good times. And some beer and bbq in the state park when the suffering is complete! - Q: I only want to swim - or bike - or run. Or maybe I'll put a relay together. Can I do that?
A: I guess. That's not very savage-like, though. - Q: Deep Creek Lake is a great vacation spot, so I'd like to bring family and friends. Cool? Anything non-participants could help with?
A: You bet. Depending on how many volunteers we get, we'd like folks for a variety of tasks: timing, watching and/or locking bikes in transition, photographers (pictures and testimonials for future SavageMans is the main reason for holding the 0th Annual), man a few intersections on bike, drive ATV on the trail section of run, etc.... - Q: Where would I stay?
A: Deep Creek Lake is a major summer lake vacation destination, and WISP ski resort on the lake is a major winter destination, so hotel lodging is plentiful. Late September / early October is after the high season on the lake so prices will have dropped, so I would recommend groups of folks getting together and renting lake houses. Also, there is camping in the state park directly across from the public beach where the transition area will be located, but nights will be getting cold so beware.
Also, a few folks have access to friends or families lake houses and are in the process of arranging accomodations. If you think you may be interested in latching on with one of these people, let me know in the RSVP comments and I'll put you in touch. - Q: Anything else to do in the area to make a weekend out of it?
A: Indeed. The lake is a hub of activity, but beyond the lake there is lots to entertain the active vacationer. The Youghigheny River, which has some of the east's best kayaking and rafting is nearby. There is lots of mountain biking, hiking, and camping nearby.
Indeed, there was just a front-page article in the Washington Post on the adventure activities available in the Deep Creek region. Funny, SavageMan wasn't mentioned. Next year.... - I'm intrigued. Show me more.
OK. Knock yourself out.
Videos of the biggest climbs and descents of the bike course are here. If you think the hills don't look all that steep in these videos and pictures, keep in mind the camera is fixed to the handlebars pointed straight ahead, so if the bike is angled up or down a hill at 10%, the road ahead looks flat from that perspective. Look for level landmarks, such as houses, on the side of the road for proper perspective.
Pictures from a ride of the bike course are here.
Pictures from an earlier training camp in the area are here.
More stuff here:
http://www.deepcreektimes.com
http://www.dnr.state.md.us/publiclands/western/savageriver.html
http://areas.wildernet.com/pages/area.cfm?areaID=MDSPSR&CU_ID=1.
That's all for now. This was a quick first cut of information so I'm sure to think of more things and post them, so check back often. Send additional questions to kyleyost@gmail.com or post in the Comments section. If you are interested in participating or volunteering, RSVP here - and soon!
For those of you who have been out to this area with me before and trained on this terrain (and climbed Westernport), please add to this information by posting your thoughts on Savageman and your experiences on this terrain in the Comments section.
