CORRECTED: Walsh makes CO after slight setback; now ready for rest

NOTICE: There are corrections to this post, added below.

Bryce made TS 14 in Cortez, CO at 5:19a CDT this morning, rock-solid in 7th 8th place. Amazingly, he took no rest at all in Utah (as I erroneously predicted he would), and only 15 minutes rest at Cortez (CORRECTION: according to the RAAM stats, he took no rest at Cortez and 40 minutes at Mexican Hat, UT). This is all in preparation for arriving at TS 15 in Durango CO, because this is a mandatory stop (the first of five such stops) where Solo Enduro racers are required to get off the bike for two hours.

I talked to Bryce’s crew leader Thomas Bérubé a few minutes ago, and although he’s calling me back later in the morning with a more detailed account, here’s what I was able to glean from him now:

“Yesterday was a very good day. Bryce looked very strong yesterday and throughout the night, and he is now ready for a well-deserved rest in Durango.

“Unfortunately, his crew made a minor navigation mistake between 13 and 14 that cost Bryce about 15-30 minutes. Other than that, it’s been smooth sailing!”

Due to the navigation error, you would think Bryce would have lost time against the 6th man, but you’d be dead wrong. I show him now gaining time on both the 6th man and the leader, and increasing separation with the 8th man. CORRECTION: I made a mistake. Bryce was passed between 13 and 14 and has dropped to 8th. Sorry for the confusion.

NEWSFLASH: Just talked to Thomas–Bryce just got to Durango! More details and stats to come soon!

Thanks for all your comments! They are being relayed directly to the crew chief and from there to Bryce. He’s lucky to have all of you to support him. Keep up the good work!

Here’s the updated map:

As always, email carter@pundo.com with questions, comments, or any changes to the race that you know about, that haven’t been captured here.

Tags:

4 Responses to “CORRECTED: Walsh makes CO after slight setback; now ready for rest”

  1. WordPress › Error

    There has been a critical error on this website.

    Learn more about debugging in WordPress.