RCS2015#12 – Handles driver who is late starting Section A

2015 RCS #
Addresses how to handle drivers who are late starting Section A of the marathon
Date Received
Terry Merritt
Change Date
Open for comments – 06May14
Initial Posting: 06May14

Current Wording – Article CD963.4.2.1

None. This is a new article associated with 963 4.2.

Suggested Wording

An athlete who is not ready to start section A within 2 minutes of the start time of the next athlete may be assigned a later start time, schedule permitting and will incur 40 penalties for failing to start on time, or may be eliminated at the discretion of the head of jury.

Reason for change

963 4.2 does not address what to do with an athlete who shows up late to start of A within 2 minutes of the next athlete. This penalty is equal to 3 min. 20 sec. time penalties as a strong deterrent, but at least allows the athlete to compete in marathon if scheduling will allow. This would also need to be added to the table in article 969, summary of penalties in marathon.

3 Response(s)

  1. Zantke says :

    May 16, 2014

    While I can agree with the intend of the suggestion, I believe we really should not make any changes to any of the FEI rules. Accordingly such changes would need to be proposed to the FEI and come from them if they agree. We should only make ADS amendments where absolutely necessary. I don’t see this as one that would fall into that need, as I believe we can handle this situation sufficiently under the current rules.

  2. keithy says :

    October 4, 2014

    The allowing to start within 2 minutes of the next competitor may work at an FEI/USEF level but it does not always work at the ADS levels. Example – If the next competitor after a Prelim Horse is a Prelim VSE than allowing the Prelim Horse to start within 2 minutes of the VSE will create holds and/or passing. This rule really should be changed to 2 or 3 minutes after their original start time. A RCS for the 2016 time frame?

  3. Kail Palmer Miller says :

    October 5, 2014

    I agree with Keith, I was run into this problem. And with allowing drivers to drive several entries. Is causing this to happen allot.

Comments are closed.