SAVE THE DATE!

Many randonneurs consider the fleche to be one of the most fun (and often challenging) events on the schedule.

What makes it fun? You’re riding with friends and team mates, all working together toward a common goal.  Plus there is the fleche breakfast, where friends and riders gather, regardless of whether they rode or finished.

What makes it challenging? It’s a 24-hour, 224+ mile ride.  You may be on a team whose route is more or less challenging.  And … the timing of the fleche is usually determined by the week after Easter, which of course is variable.  So some fleches are characterized by bitterly cold weather; for others, heat may be a challenge.  Sometimes the weather is lovely, others the weather is appalling.

Most teams will want to start riding the fleche at around 7am on April 15 so that they can finish 24 hours later at the fleche “target,” LIKELY IN ARLINGTON, and join other exhausted and elated riders for the celebration breakfast and to share stories about their adventures.

Critical deadlines for forming a team, getting a route approved, or becoming a team member are shown further below.  But first …

What is a fleche and what are (some of) its rules?

A fleche (French for “arrow”), is a team event in which each team rides different routes toward a common finish location, like arrows toward a target. Minimum distance is 360 km, which must be covered in 24 hours.  Most people who have done a fleche consider it to be one of their favorite randonneuring events since riding together as a team for 24 straight hours builds strong bonds between team members, and is great fun.

Fleche target:  the IHOP, 935 N Stafford St, Arlington, VA 22203, where on Sunday April 16, teams will meet for a hearty post-ride breakfast.  (Note that the target does not have to be the team’s final control.)  Breakfast is not included in the fleche fee.  If you would like to bring a guest, please do so.  This IHOP is a block from the Balston Metro, for an easy departure by transit.

Allowed start times:  Most teams will want to start at about 7AM on Saturday morning so that they can finish at 7AM on Sunday morning and join other exhausted and elated riders for the celebration breakfast. Team members are welcome at the fleche breakfast whether or not they successfully completed the fleche.

Fleche rules:  The fleche has its own set of rules that are somewhat different and more arcane, than those for a standard brevet. Some of them are summarized here:

• Each team must consist of three to five bicycles. (Note that a tandem counts as a single bicycle, so teams will sometimes contain more than five riders.)
• Teams can start at any time between noon on Thursday and 10AM on Saturday, and must finish 24 hours later. (However, as noted above, we encourage teams to finish around 7am (between 6AM-8AM) on Sunday morning so that they can join together for the brunch.)
• The traditional fleche route starts at some distant location and then heads for the target, but a loop route is also allowed, as long as the start location is far enough from the finish to be considered as a different postal jurisdiction.  You may not use the same road twice in the same direction.  And only small out-and-back sections are allowed, for control purposes.
• As in a standard brevet, the routes must contain control locations chosen so that the shortest bicycle-safe, bicycle-legal route through the controls is equal to at least the minimum distance of 360 km. However, the fleche has an additional requirement that one of the controls must occur exactly 22 hours after the start and be at least 25 km from wherever that team  finishes. Note that this requirement, as well as the one that states that no rest stops can be longer than 2 hours, ensures that teams take nearly the full 24 hours to complete the ride.
• The 22-hour and 24-hour control rules (Articles 10 and 11) have recently been changed to allow an exception in case you are unable to obtain on-the-spot control verification.  But … we suggest that you use this exception as a last resort, since its use requires ex-post route validation, which inherently increases the possibility of disqualification.
• For the complete fleche rules, click: here

A full understanding of the rules, especially for the 22-hour control is essential for achieving a successful finish. Team captains are welcome to contact me with questions. And many experienced captains even recommend bringing a printed copy of the rules on the ride since they can be hard to recall at 4 in the morning.

Fleche Team Deadlines

To participate in this special event, riders should start forming teams now. Each team must have a captain who is responsible for designing the route and submitting it for approval. The schedule will be:

• Monday, March 20: Applications from captains due to organizer.  See “Fleche Captain Application” below for details on what must be provided.
• Saturday, April 08: Final rosters due from team captains to Bill Beck.
• April 14 to 16: Fleche

Captains, see “Fleche Captain Application” below.

Team members, fill out the registration form and send it to your team captain! 

Captains and team members must register online at dcrand.org/, entering all of the information requested–especially phone numbers and emergency contact–and following the payment instructions there.  Note: For insurance reasons, RUSA membership is now required to ride a fleche.

Team captains are responsible for collecting applications from their team members and submitting them on time, the second deadline noted above. In other words, team members should send the forms to their captains, and then the captains should submit them as a group. Please contact Bill Beck (william.a.beck@gmail.com) with any questions. We also have many experienced fleche captains in the club who would be excellent sources of advice. If you are thinking of forming a team or looking for a team to join, the dcrand listserve is one good way to connect with other riders.  Planning and training are essential for finishing and enjoying a fleche. So I encourage all new teams to schedule at least one or two shakedown rides together, perhaps on a 200km (or even 300km) permanent route.

In case of Inclement Weather:   Because each team rides its own route, weather conditions might be acceptable for some routes while unacceptable for others.  If the weather forecast looks questionable for the region, team captains will be contacted, and they will be required in turn to contact their team members.  For this event as for all events, it is up to each individual randonneur to decide based on the best information that they have available whether they think it is safe to proceed.  Whether or not you ride (or complete) your fleche, you are welcome at the fleche breakfast, which will proceed as long as the hotel is open.

Fleche Team Captain Applications

Fleche captains will submit three items found in this folder.

1) Registration form by, March 20

2) Route application form, by March 20

3) Fleche Team Tracking Sheet, by April 08 and confirm that all team members are registered

Routes that do not include a completely-filled out DCR Fleche Route Application will not be considered.  Note that if your proposed route has been approved within the last three years, you will not need to fill out the detailed Route Justification section.  All other routes will require detailed route justification.  This is no more and no less than what is required when you submit a route to RUSA for approval.  So … if you’ve submitted a route to RUSA, you know what to do; and if you get a fleche route approved, then you’ve had good practice for submitting a route to RUSA!

It is up to prospective fleche captains to take the time to justify the route.  The organizer’s job is to review the justification — typically that can take an hour per route — not to work out the justification for you.
The route information can be submitted electronically to william.a.beck@gmail.com in PDF, MS Word, or MS Excel format. Ideally you will include a route file created in RideWithGPS; Garmin Mapsource is also acceptable; either of these will be much appreciated, but not technically required.