My first 70.3 race was a life experience that feels almost too complex to sum up in mere words. I’ve been trying to find my way to describing all of the different things it was for over two months now, and I haven’t gotten very far. I’m not sure it’s something that can be put into words at all, at least not the true core nature of it. It’s an experience, and experiencing it is probably the only real way to know it. Words, as much as I love them, are sometimes just a pale facsimile of the truth they attempt to describe.
So with that in mind, here at last is a basic run-down of how the race went. I also cut together a video that gets at my outlook and emotions surrounding the event a little bit, but probably doesn’t do much better than the words, in the end. (You can watch the video on YouTube here, or embedded below at the end of this post)
Swim 0:37:52 – 1st in Division (Clydesdale)
Perfect. Honestly my favorite part of the day, which surprised me. I missed the warmup in the water because I chose to use the bathroom (successfully, so a good choice I think). The lake was so shallow, though, that everyone walked for at least 100 yards, with resistance from the water it was a good warmup. But I had fun, swam strong the whole way, and finished in the range I knew from practice would mean I wasn’t slow and didn’t blow up. I had 1:40/100 on my watch, official time pace was 1:48, probably due to the swim exit to the mat and the standing around during the wave start. No anxiety once i got going, no issues, just ground it out and watched the fish. I felt most prepared for the swim out of all three, when all was said and done. I was not expecting the swim to be the most enjoyable part of the race, but I really did have a lot of fun with it. I also didn’t expect to win my division in the swim, so that was a nice bonus.
Bike 2:49:40 – 2nd in Division (Clydesdale)
My first significant plan deviation happened on the bike, but I didn’t realize it until later. For some reason I had it in my head that my coach said 250 average watts as my target, but it was 250 normalized power. Oops. For what it was worth, I ended with 256 AP on my computer so I felt good about hitting my number, even if it turned out to be the wrong one. Overall I was about 15 watts over the intended plan. I put down two bottles of water and two bottles of Gatorade Endurance, plus two 5-oz squeeze bottles of maple syrup. All of which I brought with me. Every aid station I grabbed water and doused myself. All in all fairly uneventful. Big headwinds on some roads, went from one lake to another and back. 2 miles of gravel. Only one hill I would call a ‘climb,’ but 2,000 ft of accumulated elevation. I felt good on the bike, working but not pushing super hard. The last 5 miles or so started to feel a bit uncomfortable, and I was just ready to get off the bike.
Run 2:10:00 – 2nd in Division (Clydesdale)
Here, of course, is where things got ‘interesting.’ I felt surprisingly good going out. Smiled and waved to my family and wasn’t even faking it. I was having fun! After I cleared the greater transition area, I looked at my watch and realized I was doing like 8:00/mile out of the gate, so I slowed that roll pretty quick and settled into around 8:50-9:30 for the first 4 miles. Then the hills started and I got slower, which was normal and fine. But then mile 7 was upon me and I got massive, massive intestinal cramping. Like really bad. It stopped me dead for maybe 30 seconds. Then I was walking, not wanting to give up. Happened to be on the biggest climb of the course where a lot of people walked anyway, so that was sort of a blessing in disguise I guess. I was eyeing the bushes and trying to decide if I needed to try a pit stop, but eventually ripped a massive…shall we say…’flatulent expulsion.’ Just gas, no soiled britches. And then I was running again! Got back up to around 9’s here and there, especially on the descents back into town. I still had minor cramping happening but it was small enough to ignore. But the whole ordeal took a lot out of me. I tried to pick it up at mile ten, knowing there was just a 5K left, but it didn’t last. I had almost nothing left for the last mile. Just slogged it in. The one bright spot at that point, besides the finish and my family, was that I passed a superstar aero guy who had passed me on the bike at mile 42 on the gravel. I guess he bonked harder than me. He was walking. I felt bad for him but it was also confirmation of what my coach said — a pass on the bike is momentary. A pass on the run is final.
Finish and Post-Race 5:43:24 – 2nd in Division (Clydesdale), 72/208 Gender, 96/343 Overall
I was pleased as punch to discover I had made my way to the podium in my division. The Clydesdale division, when it exists, is something of a dilemma, because weight is the only criterion for entering. But there’s a big difference between 250 pounds of muscle and 250 pounds of fat, for example. So it’s not always necessarily the equalizer it’s intended to be. The competition in this division was strong at this race; the winner completed it in under 5:30:00. I would have needed to be 10 minutes faster on the bike and at least 5 minutes faster on the run to win, not to mention faster transitions. I was very happy with what I accomplished and felt that I did the best I possibly could have, considering the challenges I faced (both this year and during the race itself).
Having my family, both close and extended, there to support me along with some close friends really made all the difference, though. For the last two miles, they were all I thought about. I hugged my kids just before the finish and felt a great sense of relief crossing the final threshold.
While waiting for the awards, I had the opportunity to meet and chat briefly with Jennie and David Hansen, two of my Ironman heroes. They were as friendly and open as could be. They both crushed their races. Jennie did the combination race, which was the sprint on Saturday and the 70.3 on Sunday, and won everything.
I made a video about the race, attempting to summarize it from another sort of approach. You can watch that here:
My first triathlon of 2019 was a sprint distance race held in southern New Hampshire, called the Greater Nashua Sprint Triathlon. I settled on this race in particular after several months of research, trying to find a race that was both within driving distance and lined up with my training schedule for my 70.3 race. I didn’t know anything about it other than what I found on the website and Facebook page, but it was the 10th annual running of the event, so it seemed likely to be a well-organized race.
An added bonus to this race was that my wife’s parents and brother live just an hour away from the race location, so we were all able to stay with them and combine it into a family visit. It’s a huge benefit to race day preparations to be in a comfortable location with family before an event, so I’m grateful we were able to have that opportunity. I went to bed at the same time as my kids, and actually managed to sleep through most of the night. I only woke up once, at about 3 AM, and then drifted in and out until about 5, when I got up.
Breakfast was my customary bowl of oatmeal flavored with maple syrup with a coffee. While I had the syrup out, I took the opportunity to fill my gel bottle. I still wasn’t sure if I would even use fuel during the race, because it was so short, but I figured it couldn’t hurt to have it along.
I had everything pretty much ready to go the night before, so all I had to do in the morning was load my bike, put my transition bag in the car, and head out. The drive was uneventful. As I got close to Nashua, I started to see more and more cars carrying bikes. It wasn’t long before I saw a fully decked out Quintana Roo on the back of a pickup. Welcome to New Hampshire.
Parking was an absolute nightmare. There was a lot designated for racers, which was the entire area around a local school, but it was already packed to the gills by the time I arrived. I ended up having to park underneath a swing set. I checked the air in my tires at my car, put my transition bag on my bag and rode to the transition area.
Transition was pretty well organized, with everyone having a marked spot on the racks. Once again my bike was too tall to fit very well on the rack. The saddle was too high to easily get it under the bar, and then there wasn’t enough of a hang to keep it on there securely. Not much I could do about it, so I set up my transition stuff and went to get body-marked, check out the transition routes, and wander down to the water.
There were about 15 minutes of announcements before the race, which felt like they took forever. I tried to keep my arms moving, doing some arm circles and such, but mostly just stood around feeling my springs coil. Finally, they started calling waves. Everyone had an assigned wave number, and when your wave was called, you went down to a dock area to check-in and queue up for the start.
This was my first race wearing a wetsuit. It was also my first race with a wave start. It cheated everyone out of some time, because the timing mat was on the dock and the waves treaded water for a minute or two before actually starting. But at least everyone lost the same amount of time, so it didn’t really matter.
I put some water on the back of my neck just before jumping in, but it felt like a warm bath. I was prepared for a cold shock when stepped off the dock, but it was just balmy. I grabbed the start line rope and floated until the starter gave us the go signal, then I was off.
Almost immediately, I felt like something was wrong. I wasn’t more than 30 seconds into it and I felt absolutely awful. I thought I might be getting sick. Was I even moving? I couldn’t really tell. My line was way off, too, and I kept veering to the right. I tried to focus on my technique and things got a little better. I decided that whatever I was feeling, it wasn’t getting any worse, so I would just push through it. I had done enough swim training to know that I wouldn’t suddenly drown or anything, especially while wearing a buoyant wetsuit. The worst case was that my arm strength would just give out, and it hadn’t yet. So there was no reason to stop. On I went.
About halfway through the loop, I started catching some people. I have no idea if they were in my wave or the wave before mine, or possibly the wave after mine, having gotten ahead of me at the start. I didn’t try to swim over anyone but I didn’t really seem them coming, either, so some contact was inevitable.
I hadn’t set a goal time for the swim, but from experience I expected something between 10-15 minutes in the back of my mind. When I finally stood up to exit, it felt like it had been twice that, but I figured realistically it was maybe 12 minutes.
I looked at my watch and saw an 8. Suddenly things made a little more sense. I had been going faster — much faster — than I thought. No wonder I felt like my chest was going to explode.
Official Swim Time:8:49 (.3 mi) – 1:41/100 yd 7/32 in age group; 34/414 overall
T1 sent us up a sandy path through the woods to the grassy area where the bikes were. There were wetsuit strippers waiting for us, which was awesome. I pulled my wetsuit down below my waist, slid into home on the tarp, and my suit was popped off before I even knew what was happening. I thanked the volunteers and headed to my bike.
I had toyed a bit with leaving my shoes on my bike with rubber bands, but ultimately couldn’t really figure out how to do it so it worked properly, and I was worried about the rubber bands getting caught in my gears, so I decided to just put my shoes on in transition, run the bike out, and clip in. I certainly wasn’t going to try a flying mount, so this was a reasonable option for me. At the last second I grabbed my maple syrup bottle and slid it into my tri suit pocket.
Official T1 time:3:13 – 91/414 overall
The bike route was very short, and very flat. I’d only done three previous races before this one, but this was the shortest and flattest by far. I had been doing a lot of mental gymnastics about the bike leg in the days leading up to the race, debating my approach. Overall, I wanted this race to be something of a practice session for my 70.3 — transition logistics, using a wetsuit, etc. I thought about also extending that to pacing, to practice the mental and emotional control required to slow myself down at the start of the bike leg so that I would be able to hold the right pace throughout, and then have enough left over for the run. But as soon as I was clipped in, that decision was made. It was go time.
Because I didn’t have any pacing or power targets, I ended up watching my heart rate most of all while out on the course, followed by my speed. My heart rate was shockingly high compared to the levels I was used to seeing during my training, which is predominantly spent in zone 2. But I knew that wasn’t necessarily a problem. The race was short enough that I could work at or above threshold for the whole thing. They call it a sprint for a reason, after all.
The other fun thing about a sprint is that passing someone on the bike leg is usually permanent. In a longer race, it can often be just the first of two meetings, the second of which being when they come back and smoke you on the run. But in a sprint, they are more likely to run out of road if you go full throttle on the bike. Since it was a wave start, I knew that passing people was not an entirely accurate representation of my place in the field. But it was motivating anyway. So I reeled in as many people as I could, and made sure that nobody passed me. The best part was passing those $6,000 tri bikes on my gravel bike with regular old drop bars.
As it turned out, I was glad to have my maple syrup on board. I took a couple hits, one partway through and one just before T2. It felt helpful, and made me realize that I would probably need more fuel than I had been thinking during my longer race in July.
The bike course covered, I had a clean dismount just at the line, and ran my bike in to the transition area again.
Official Bike Time: 25:45 (9.6 mi) – 22.4/mph 4/32 in age group; 18/414 overall
T2 was my slowest performance on the day, relative to the field. I didn’t deliberately go slow, but I wasn’t rushing, either. I’m pretty particular about how my shoe lace-up feels, and that combined with the socks I use (which are not super easy to get on) probably accounted for my slow time. But I made it out on the run with everything I needed and feeling pretty good, so I wasn’t too worried about blitzing through T2.
Official time: 1:51 – 313/414 overall
I expected to be running fast out of transition, having experienced that phenomenon before. Adrenaline is high and you are excited to just get going, and before you know it you’re running way faster than you expected. I checked my watch after a couple hundred yards and saw I was running close to 7:30 min/mi, which is very fast for me. For reference, I ran all of my sprints last year at around 9:00 min/mi. My first reaction was to feel like I needed to back off, slow down and find a more conservative pace, but then I remembered it was only 3.1 miles. I was able to hold a strong pace through the swim and bike, why not the run? Might as well go for it, and see how long I could hold it before I slowed down. The worst case was that my pace would slow for the back half of the race, but I knew I would finish no matter what. Go time continued.
I focused on my cadence through most of the run, trying to keep the rhythm even and high. That seems to be my key to running fast (such that “fast” is, for me), when I need to. If I think about ‘running fast,’ it’s harder to do, but if I just focus on my cadence, it’s easier for some reason.
The run was also a very flat course, with only a couple slight inclines, when my pace dipped closer to 8:00 min/mi. I was able to hold my cadence pretty well throughout. Two or three people passed me, including a 60+ year old woman and a kid, wearing the race t-shirt. Sigh. But overall I held my pace and I felt strong throughout.
By the time the last half-mile came around, I was starting to feel it, particularly in my hips and my abdominals. I was definitely on the edge, pushing to maintain the pace. There wasn’t much of anything left for a late surge, all I could do was hold what I had through the chute and over the finish line.
Official Run Time: 24:19 (3.1 mi) – 7:50/mi 11/32 in age group; 65/414 overall
Overall Results: Time:1:03:55 5/32 in age group; 34/219 by gender; 36/414 overall
Post Race & Summary
The race venue had a lot of activities for kids, which was great for when my family arrived. There were at least three bouncy houses, plus a clown making balloon animals, and kid-friendly food. The food was great, and there was tons of it, all of it free as far as I could tell, at least for racers. It wasn’t just bananas and bagels, there was an entire sandwich buffet, flatbread pizza, Italian ice, all kinds of things. The only real negatives for me about the race organization and venue were parking and the lack of a professional race photographer (there were only official volunteers, who took substandard photos and whose coverage was incomplete). Otherwise, it was a well-organized and fun race on a decent course.
As far as my performance goes, I came away a little surprised and with a lot to think about. I had definitely underestimated my potential in the water and on the run. I really didn’t have any idea that I could swim or run that fast over any distance. Almost immediately, I started thinking ahead to July, and trying to sort out what that means for my 70.3. Obviously I won’t be racing at these speeds at that distance. But my personal bar has been raised, there’s no getting around that. Now I have the task of handling that knowledge without it infiltrating my head in a negative way. Expectations for a race are not usually helpful.
I tried to examine whether I could have gone any faster, any harder, improved in any area in order to jump to the 1st-3rd place podium from my 5th place spot. I would have had to be about 6 mins faster to do that. Certainly I was maxed on the swim. I don’t think I was at maximum capacity on the bike, but I was fairly close. The run didn’t have a whole lot of room to give, either. When I look at the actual times between 5th (me) and 3rd, here’s what I find:
Clearly the majority of time lost was on the run. That isn’t surprising to me, since I’ve never been a fast runner. But I’m encouraged, because I’m way faster than I used to be. The next biggest deficit was T2, followed relatively closely by T1. The differences on the swim and the bike combined could be easily surmounted by improving just my transitions alone. Or I could have pushed a bit harder on the climbs (such as they were) on the bike and probably wiped out a lot of that time. But most of the improvement work to be done is clearly in my run.
Is this a microcosm of what I can expect at longer distance? It will be interesting to see how the ratios play out there. I’d also be interested in comparing these relative results to my results from last year’s sprints. That is, how much slower — relative to the field — was I in transition vs. the bike leg, or run leg. Maybe that will be a good subject for a future post. You can’t compare races 1:1, but I think you can get a sense of how the relative balance of everything plays out, and what that means for your skill set and fitness level. If nothing else, it’s an interesting diversion.
Signing up for the 18th Annual Whiteface Mountain Uphill Bike Race wasn’t my idea. I’ll own the choice, of course, but I wouldn’t have even heard about it if my friend Phil hadn’t asked me to do it. I was in the midst of concussion recovery at the time, and I’d be lying if I said I didn’t sign up in part in order to give myself a temporary feeling of hope. Surely I’d be better by May 31st. If I sign up for a race, then it’ll make sure that comes true! Magical thinking, to be sure. Luckily it worked out okay this time.
We had a drive of about 3 hours to get to Wilmington, NY, where Whiteface Mountain rises above the surrounding ridge lines at the eastern edge of the Adirondacks. Lake Champlain was on the way, so we treated ourselves to a ferry ride while we tried to pick the mountain out from the landscape across the water. We never did quite determine which one it was.
A couple of guys from Burlington wandered by and chatted with us briefly.
“You racing?” one asked.
“Yeah,” Phil answered, “Whiteface. You?”
The guy nodded, because obviously there was only one race all of us were thinking about. He looked up at my bike on top of the car, an Orbea Terra gravel road bike with 28 mm slick tires. Phil’s was a Trek Checkpoint, a similar machine, with slightly wider gravel tires. “You riding on those?”
“Yeah,” I said, a little unsure about the pointedness of his question.
“Wow,” he answered.
“What are you guys riding?” Phil asked.
“Mountain bikes,” the guy answered, as if it were obvious, and he and his flat-brimmed hat bid us good luck and wandered off.
For the next hour, as we completed our drive to the base of the mountain, Phil had something close to a minor meltdown as he parsed the conversation and tried to decipher what the guy had meant by his line of questioning, his clearly loaded, Owen Wilson-like remark of “Wow” and his utterly straightforward statement that he and his friend were riding MTBs. Did he think we were idiots for our bike choices? Or did he think he was the idiot, now seeing what we were riding? What did it mean, and what would possess a person to convey such apparent passive aggression directed solely to a person’s choice of ride? Were we idiots for riding these bikes? Were we even going to the right race? What day was it? Why were their brims so incredibly flat?
We arrived in Wilmington quite early, with hours to spare before the race was to start. We walked over the bridge spanning the Ausable River and found our way into the ski lodge, where we picked up our race packets, which included helmet stickers, bike stickers with timing chips in them, the largest number bibs I’d ever seen, t-shirts and exactly zero snacks. Good thing we brought our own. Phil had all kinds of goodies from home to choose from for on-the-bike nutrition, including some special power cookies his wife baked. I had opted for a singular choice item: a refillable energy gel bottle containing 100% pure maple syrup. That, combined with water and endurance formula in my bottles, was what I hoped would keep life in my legs as I scaled the mountain in a few hours.
After I gathered my race accouterments from the helpful check-in folks, I asked them a question which had occurred to me.
“Is there another race here soon?”
“Yes,” one said, “a 50 or 100-km qualifier for Leadville.”
And suddenly, it all made sense. Those guys on the ferry thought we were doing Wilmington Whiteface. They thought we were going to be riding single track for 60 miles, on slick 28-mm tires! “Wow,” indeed. We had a good laugh about that, and “Wowwww” became an instant catch-phrase for the rest of the day.
We decided to cruise down the course a bit, just to check out the opening three mile prologue, and see what interesting things we could find in town. We saw a bunch of guys fishing the river, and watched one of them pull a sizable fish out. We stopped in a local shop and got some chocolate for the kids and wives. We saw a giant metal bike statue and debated climbing on top of it, but ultimately left such shenanigans to the presumed local youth to get arrested for. A gaunt man with a beard was lost and tried to get into a locked building nearby. I said to Phil, “That’s either a hardcore cyclist or a meth addict.” Not a minute later, he asked us where to check in for the bike race. #nailedit
Finally, it got close to race time. We changed into our kits and took a little warm-up spin up the hill behind the parking lot. Phil had a little trouble with his cadence sensor, but we got it sorted. A lot of folks were really clamoring to start near the front of the pack, which surprised us considering it was a chip-timed race and drafting wasn’t going to be a major factor, so it didn’t really seem to matter when you actually started. Phil had a theory that the best strategy (if you were racing to win) might be to hammer the first 3-mile downhill section, though, so maybe the draft was a bigger player than it seemed. In any case, we opted to start comfortably from the back.
The national anthem was sung, the Canadian national anthem was played, we got the most anti-climactic count-down in history, and the race was underway!
As I mentioned, the first three miles were essentially downhill. I deliberately played it cool here, trying to spin up the legs in a relatively high cadence and to really back off the power. There was enough of a descent that I was clipping along basically without working. Then we hit the corner, and the climb began.
Once I settled in, I kept an eye on my numbers and found that an average of 340 watts felt about right. I was working, but I wasn’t hammering, and my heart rate was staying below threshold. I found my most comfortable gear and got to work.
There was the slightest of reprieves while passing the tool booth, and then it was nothing but up, for a section of about 4 miles that featured the steepest sections of the climb. Partway through this section, I took my first hit of maple syrup. It went down smooth and quick, and much easier than energy gel. I also didn’t feel like I had to wash it down with water to clear it out of my mouth. So far so good.
Because of how the road is laid out, I could see the switchbacks quite a ways before I got to them. They were laid out high above me on the side of the mountain. I knew that they were only a couple of short miles away, so it was a bit daunting to consider how high I had to climb in order to reach them, especially knowing the gradient it would take.
My legs were doing okay, but started to get a little crampy and uncomfortable at around mile 8 or so. Originally I had intended to ride a bit easier until this point, and then put the power down. As it turned out, I rode a rather more consistent power output, so I didn’t have a whole lot of reserves to draw from. I was going steady, though, so I figured I’d just keep on with my 340 watts and see how that worked out.
By the time I reached the first switchback, I had enjoyed some amazing views, passed two unicyclists, hit my second dose of maple syrup (so good), seen a guy riding deliberately crosswise across the road repeatedly (to rest his legs, I guess?), gotten slightly annoyed by someone with a squeaky bike that I couldn’t drop, and been told “I like that gear you’re in.” As in, complimenting me on my specific choice of gearing. At that moment. I guess? I still haven’t figured that one out.
I knew from simulating the ride indoors that the switchbacks provided some measure of relief, and were the time to drop the hammer for sure, if there was any hammer left to drop. I latched on to the wheel of a guy about my size, who I had noticed from his bib that he was also in the Clydesdale division like me, and followed him up and around the second switchback. Then I went by him and made for the finish.
I had enough legs left to put down a sprint for the finish of about 0:20. It was completely unnecessary, and nobody was sprinting with me, but I don’t get to race in bike races very often, so it felt right. It was an experience I had never had, and I wanted to go for it.
After I got through the chute and received my finisher’s medal, I pedaled around the courtyard of the little castle-like structure that is at the summit to behold a magnificent view of the surrounding landscape. It was a great reward for doing the work to climb to the top. I took a couple of quick photos and then went back to the finish line to cheer on Phil, who was only minutes behind me. I managed to get a decent video of him crossing the line. We took a few more shots and drank some Gatorade, then put on our sleeves and started the ride back down. It was getting cold quickly so we didn’t spend a lot of time up top.
The ride down was at once fun, beautiful, exciting and harrowing. We were cruising at 40 mph with our brakes engaged. If we had been alone on the mountain, we probably would have let it rip a little more, but there were still people climbing the hill, cars driving up and down both ways, and other cyclists heading down. With a lot of blind corners, it didn’t seem prudent to be going full speed with no chance to stop suddenly if necessary. It was also really cold, and I had to adjust my hands and arms periodically just to make sure that I could, in fact, still feel them.
We made it down safe and sound, and then cruised back to the ski area for food and to check out the results. I ended up in 7th out of 26th in the Clydesdale division (190 lbs+), with an official recorded time of 1:19:25. I was pretty darn happy with that effort. I don’t know that I could have done it much faster if I had changed anything, and I don’t know what I could have changed. It was pretty close to the best execution I could manage on the day. You can’t ask for much more than that.
The drive home was long and dark, but still a good time and there was plenty to recount and reflect on from the day.
I was very glad to be able to do this race. It’s one that I don’t think I will ever forget.
My “A-Race” this year is the Musselman Triathlon, which will be my first 70.3-distance race. I’ve been looking for a smaller, shorter race I could do in advance of that one that would time up well with my training and is close enough to me to not be a logistical headache. There are lots of running races in northern New England and a fair number of cycling events too (though mostly fun rides, not races), but triathlons are harder to come by. It’s even harder still to find one that takes place on the specific weekends that work within a larger training plan for the year.
Most triathlons are pretty flat, and I suspect that has a lot to do with their scarcity in this region. Vermont in particular doesn’t really do flat.
The race I found that fits the bill for my training and schedule is the Greater Nashua Sprint Triathlon. I’ll be going a little further afield for this one, but not terribly far. It’ll be a couple of hours in the car to get there; less if we stay with family who live closer to the venue.
Even as sprints go, it’s a short one. Here’s a preview of the three legs:
The swim clocks in at less than 600 yards according to the website, but still manages to pack in three turns. The turns are the worst part of the swim, for my money (apart from the mosh pit) so that’s a little disappointing, but it’s probably due to the geography of Lake Naticook and for safety reasons. It looks like the waves are staged on a dock.
The bike course currently shown on the website is amusingly just a screenshot of someone’s browser tab displaying Google Maps, which has been converted into a pdf. I converted that to a Strava Route so I could get a sense of the details, and it’s a ripper. Very short and very flat.
The bike leg climbs only about 430 ft over a distance of 9.5 miles. That’s less than half the elevation per mile that I’m used to in training around where I live, and the total distance will be the shortest bike leg I’ve raced so far.
The run leg is a good match for the bike, keeping things flat and fast.
The exact location of the transition/finish area is unclear, but it looks like the total distance will be just over a 5k, at around 3.2 miles, with about 80 feet of elevation gain.
So what do these details mean for me?
This race will primarily be a training tool for me, an opportunity to practice organization, transitions and race-environment stress management. So in that sense, the details don’t actually matter all that much. I’ll be there to practice triathloning and to have a good time.
That being said, I wouldn’t say the race particularly caters to my strengths. I do better in a swim when I can establish and hold a groove; 3 turns means a lot more buoy sighting and thinking about things other than swimming ahead at my own pace. Cycling is my strongest discipline, but the relatively shortest opportunity here, which means that there will be less time to make up for deficits from a slow swim, and more complications in terms of pacing because I’ll be tempted to really drop the hammer on a <10 mile ride (but thereby risking leaving less in the tank for the run). The run looks like a fairly standard 5k route, but running is probably my most challenging discipline, so that’s really no help. So at the end of the day, this could prove to be a pretty tough race for me, if all of these factors stack up in the right (or wrong) way.
My aim then will be to mostly forget about all of that, and to focus instead on managing my pre-race anxieties, race day strategies and transition performance. After all, those are really the only things from a sprint-distance race that will meaningfully translate to a 70.3.