View Source

h3. Proposal from

PATRICE GIRARDIN/ FRANCE

h3. Proposal title

FR Forgotten

h3. Existing text

h6. {color:#000000}4.30.3 A competitor may return to the airfield within 5 minutes of take-off for safety reasons or in the event of a FR{color}{color:#000000}failure. In this case a further start may in principle be made without penalty but equally the competitor{color}{color:#000000}must not benefit in any way from restarting. Exceptions and penalties will be specified in the task{color}{color:#000000}description.{color}

h3. New text

{panel}

h6. {color:#000000}Versus  A  4.30.3 A competitor may return to the airfield within 5 minutes of take-off for safety reasons or in the event of a FR{color}{color:#000000}failure{color} {color:#ff0000}but not{color}{color:#ff0000} forgotten{color}{color:#000000}. In this case a further start may in principle be made without penalty but equally the competitor{color} {color:#000000}must not benefit in any way from restarting. Exceptions and penalties will be specified in the task description.{color}


h6. {color:#000000}Versus B {color}{color:#000000}4.30.3 A competitor may return to the airfield within 5 minutes of take-off for safety reasons or in the event of a FR{color}{color:#000000}failure. In this case a further start may in principle be made without penalty but equally the competitor{color} {color:#000000}must not benefit in any way from restarting. Exceptions and penalties -{color} {color:#ff0000}including penalties for FR forgotten{color} {color:#000000}\-  will be specified in the task {color}{color:#000000}description{color}

{panel}

h3. Reason

To prevent any benefit from the failure in the flight preparation. To prevent interpretation about what is an FR failure as done by the previous WMC and WPC without specification in task description

To forgot a FR is a strong  fault which has to be penalised by A or B and not considered as a FR failure.