Come join NER and your fellow riders in the Fall for a weekend of Team Events!
RUSA version of the classic 24 Hour / 360+ kilometer team ride. Teams of 3-5 bikes pick start date, time, and their own route to Brattleboro, VT. Maximum stop time is 2 hours. Teams may start anytime between Thursday, Sept 22nd @ Noon and Saturday Sept 24th @ 10am. Once started, teams ride for exactly 24 hours.
200km+ / 13.5 hour Team ride. Teams of 3-5 bikes pick start date, time, and their own route to Brattleboro, VT. Maximum stop time is 2 hours. Teams may start anytime between Thursday, Sept 22nd @ Noon and Saturday Sept 24rd @ 10am. Once started, teams ride for exactly 13.5 hours.
RUSA Dart Populaire:
120km+ / 8 hour Team ride. Teams of 3-5 bikes pick start date, time, and their own route to Brattleboro, VT. No Maximum stop time. Teams may start anytime between Thursday, Sept 22nd @ Noon and Saturday Sept 24th @ 10am. Once started, teams ride for exactly 8 hours.
Bunch Info: Teams and friends are invited to meet for an informal Brunch in Brattleboro on Sunday, Sept 25th. Details to be announced.
Team Captain: Please complete this Google Form. Team captains can start the from and resuming editing if they need to make changes. The form should be completed and finalized no later than Sep 18th, 2022.
All Team Members: Register on BikeReg for the Arrow/Dart. There is no cost. Make sure to note the team name or captain name in the box provided to do so. (Note: The team name is separate from the “Team” you can declare on BikeReg.)
Note: In 2022 there is a Spring and Fall team weekend. The below refers to the Fall (Sept 24th) events:
Teams may choose to participate in an Arrow, Dart, or Dart Populaire Event.
Rules in brief: Teams of 3-5 vehicles (tandems count as one) collectively ride to Brattleboro, VT together using a route and start point of their choosing. The route must be at least 360km+ (Arrow), 200km+ (Dart), or 120km+ (Dart Pop) and conform to standard brevet requirements of using the shortest distance been checkpoints (controls). Irrespective of chosen route, teams must complete the event in specified time for the distance.
Distances count toward RUSA awards. These events are not sanctioned by ACP.
These team events offer many unique and enjoyable challenges: Plotting a route, helping one another during times of difficulty, and feeling the reward of accomplishing a monumental ride together. Many riders feel the team rides are the most enjoyable Randonneuring events.
Team Event Cards: Riders may use traditional paper cards and have them marked by stores along the route. Teams may also choose to submit GPS/GPX files showing the time of day and position. If teams ride together, one route file is sufficient for the team. Photos (preferred) should clearly show all the team members or their bikes and a recognizable location (store sign, etc) that indicates the control.
- See above for deadline to submit completed application..
- The RBA & Team coordinator has final say in approving routes. Routes must be ridden as submitted.
- A designated team leader is the single contact person for the entire team.
- Credit is only given to those finishing together. Failure for at least three vehicles to finish together result in no finishing credit for the entire team.
- Riders must follow all traffic laws. While paceline style riding is allowed it is not required.
- Teams may not receive assistance (including drafting and follow support) from any other team or person while on route.
- At least 25 Kilometers must be completed within the last two hours of the event. A control location must be selected which is 25k+ beyond the finish and teams must be at this point 2 hours before the finish of the event. (Not applicable for the Dart Populaire.)
Arrow & Dart 2h Max Stop Rule: Teams must not stop for more then 2 hours at any location including any overnight locations.
- Teams determine their own route which terminates in Brattleboro, VT.
- The route must meet brevet guidelines and represent the shortest point between control locations.
- Teams receive credit for the shortest distance between controls.
- A point-to-point and loop routes are allowed; out-and-back style routes are prohibited.
- Passage through control locations can be certified by: A clear timestamped (smartphone) Photo, a receipt from a store or ATM, a GPX track. (Links to a website not acceptable.)
Here are the official rules for the Arrow, Dart, and Dart Populare.
More information is listed in the Q & A below or by reading the Rules on the RUSA website.
- How to plan a Route?
- May different teams use the same route?
- May we alter the route once submitted?
- What makes for a Control? Do you need to select a 24 hour store for overnights?
- How do we deal with unmanned controls?
- How do we need to submit the route?
- How do we know we’re registered?
- What do we need to submit to register?
- Why do we need to register more then a month before the event?
- What defines a team?
- Does the team have to ride together?
- What support is possible along the ride?
- What must the team do 22 hours into the ride?
- Do you need to complete the ride in 24 hours? Can you go faster or slower?
- Can we ride fast and sleep at night?
- Are there other RUSA Team events in New England?
- Who should I contract with additional questions?
Q: What are acceptable routes and how to plan?
A:Routes may be point-to-point or circular. No road may count towards the distance twice and out and back segments are not allowed. Teams may use parts of Brevet routes if desired.
Routes are similar to Brevet routes in that they must have control locations at the outer edges of the route; the shortest distance between control points using public roads and paths must add up to the minimum for the route to be validated. RUSA requires us to be strict so add additional control points if you’re unsure.
The RBA has final approval on all routes and may ask for changes to be made. The RBA will determine the shortest distance between control points which may be shorter then route the team has selected.
Example 1: A minor highway directly connects two control towns with a distance of 50k. A team selects a route using backroads which is 55k. The team will only receive 50k of credit for this leg BUT must still follow their backroad route if this is what was submitted.
Example 2: A major highway directly connects two control towns with a distance of 50k. The team and RBA agree this highway is prohibitive for cycling. (Bikes are outright banned or high speeds make it overly dangerous.) The team selects a backroad alternative which is 55k; they will receive credit for this distance.
Example 3: Small roads connecting two control locations with a distance of 50k. A team nevertheless selects a route of 60k between these points. The RBA will reject the 60k leg and ask the team to add an additional control location or use the shorter route.
Good team routes are those which can be successfully navigated by the team. Some teams will prefer to keep things simple and use only numbered state roads while others teams will try to pick little-used dirt roads and bike paths. Being able to select the roads which are best for the team is part of the fun of a Team Event.
Read the guide to creating a NER route for more advice and regulations.
Tip: Historically the more control locations, the more likely a team is to DNF. Teams using 10+ controls often report they regret using so many stops. It is good practice to not plan on more then a single control every 40-50k.
Q: Can the route be longer then 360 Kilometers?
A: There is no length limit to any route. The more ambitious the route, the more likely the team will finish outside the time limit. It is recommended that team events do not considerably exceed the minimum distance for the event chosen.
Q: May different teams use the same route?
A: Yes, however the start times must differ by at least one hour. Teams may not ride with one another at any point.
Q: May we alter the route once submitted?
A: Once validated, the route is final and may not be changed without re-verification and approval. The RBA may not have the time to re-validate a route once approved.
Q: What makes for a Control? Do you need to select a 24 hour store for overnights?
A: Control points can be anywhere within a small geographic region in a town (eg. Main Street) — we don’t need exact store names. You can be creative with control locations — Park ranger stations, landmarks, police stations, and ATMs all make fine controls. Many teams will try to select 24 stores on the overnight so they have a place to refuel however a staffed control is not required.
We highly recommend teams do some scouting before submitting a route to verify there will be something in town that can act as a control location. Not all towns have stores or post offices! (Tip: Don’t trust google! The gas station it lists as being 24 hour might not still be around or have changed hours.)
Q: How do we need to submit the route?
A: When you send in your registration you’ll need to include a map with your general route highlighted and control locations indicated. You’ll also need to include a rough cue sheet which lists control locations and distances. Remember, we’ll only consider the shortest possible milage between controls even if your team decides to take long way around.
A link to a RideWithGPS or other online mapping service is strongly preferred.
Q: How do we know we’re registered?
A: You’ll first be contacted via email or phone upon receipt of your registration packet and again if your route needs modification. About a week before the event you’ll receive pre-printed Brevet cards for each member of the team. If you need to change team members after submitting your registration forms, you may do so at least two weeks prior to the event by sending the organizer a signed waiver and a note of the change.
Q: What do we need to submit to register?
A: Read the registration form! You’ll need to include the route statement, signed waivers for all team members, and payment for event plus brunch if you’re planning on joining us on Sunday.
Q: Why do we need to register so far in advance?
A: It will take us time to verify your route and give you time to tweak your route if it doesn’t meet our requirements. The Dart cards need to be mailed to the team leader unless the team ops to use GPS certification.
A: Teams consist of three to five vehicles with a vehicle defined as an entirely human powered device. A tandem (two riders or more) counts as a single vehicle.
Q: Does the team have to ride together?
A: The team doesn’t need to ride close to one another but at least three vehicles must finish the last 25k within the last 2 hours together in order for the team’s ride to be certified. Team members not completing the ride with the group will not be considered to have finished the event.
The spirit of the event is to have the team ride in formation and not spread out over miles.
Q: What support is possible along the ride?
A: The team members may help one another but no outside help (follow support, etc) nor help from other teams is allowed. Riders may not have support crews meet them at controls but they are allowed to stop at motels, buy snacks, etc.
Q: What must the team do 22 hours into an Arrow, 13.5 hours into a Dart, or 6 hours into a Dart Populaire?
A: In order for the team to be certified the team MUST get their control cards signed 2 hours before the end of the event. (22 hours after the start of a Arrow, 11.5 hours after the start of a Dart, 6 hours after the start of a Dart Populaire.) Furthermore, this 2 hour location must be at least 25k from the end point of ride as listed on the verified route. Keep in mind the time, not location, is what dictates this control. Even if your team is running behind or ahead of schedule, you must stop and get certified at the exact time.
The below examples assume a finish location in Portland, Maine.
Example 1: Arrow Team “Pointy Arrows” starts at noon on Friday and plans to be at a store in Saco, Maine (~28k from Portland) at 10am on Saturday. They arrive at 9:50am so they wait until 10am to have their cards signed then depart for Portland. This is ideal.
Example 2: Arrow Team “European Ramblers” also starts at noon on Friday and plans to be at a store in Saco, Maine at 10am on Saturday. However, at 10am Saturday they have fallen behind in their schedule and are only in Kennebunkport, ME (~40k from Portland). While not a previously planned stop, they go to the LL Bean store to have their cards signed. They gain time in the last two hours and arrive in Portland at Noon on schedule. This is acceptable.
Example 3: Arrow Team “Broken Chain” also starts at noon on Friday and plans to stop at Saco, Maine at 10am on Saturday. However, at 10am they are behind schedule and do not stop until 11:20am when they are in Saco. By not stopping at 10am they have disqualified themselves and do not receive credit, even if they sprint to Portland and arrive at noon.
Example 4: Arrow Team “Way-2-Fast” rides fast and arrives at Saco, Maine at 7:45am — 2.25 hours ahead of schedule! They should have slowed down earlier as they must either wait in Saco for more then 2 hours OR arrive in Portland well before 24 hours have elapsed. They do not receive credit.
Q: Do you need to complete the Arrow in 24 hours? Can you go faster or slower?
A: You need to attempt to finish the Arrow exactly 24 hours after starting. Early finishes are not acceptable so pace yourselves accordingly. Teams finishing considerably outside the 24 hour window will not be certified.
Q: Can we ride fast and sleep at night?
A: For the Arrow & Dart, Nope. No stop may be longer then 2 hours. Since this includes nighttime riding, all vehicles MUST have full lighting and reflective equipment as if they were on a solo brevet.
On the Trace and Dart events a longer stop is allowed. It is theoretically possible to sprint for six hours @ 16Mph, sleep for four hours, and ride at 10 Mph two more hours in order to arrive in Portland in 12 hours and 180k completed.
Q: Are there other Team Events in New England?
A: The Berkshire Brevet Series occasionally runs the New England Fleche out of Westfield, MA.
Q: Who should I contract with additional questions?
A: Contact NER Team Coordinator Jake Kassen