Tuesday 24 June 2014

Rules and Information for the Precision Flying Event 2014

1.  Teams must enter as a crew of one or two persons.


Not permitted                                   

2.  Each team must fly the same aircraft for both events.

3.  A team may use the same aircraft that is being used by another team.

4.  No person may enter as a member of more than one team.

5.  All teams will be required to sign an indemnity waiver against the organisers and marshals, in the event of an accident.

6.  The judges' decisions will be final. Appeals against the results may be made to the judges. Every effort will be made to satisfy all appeals.

7.  Ignoring/flouting the rules/ATC such as to compromise flight safety will result in disqualification from the flying events.

8. Scoring:  The team with the highest score will be deemed winners of the 2014 P.F.E.  Total scores for each team will consist of their Navigation Event Score (maximum 200 points) and their Spot-Landing Event score (maximum of 20 points or, 15 points for Early Launchers - see definition of Early Launchers below).

9. Any delays that necessitate a re-ordering of teams' departures caused by aircraft mechanical problems may result in disqualification, but will remain at the discretion of the judges.

10. In the event of adverse weather conditions, the judges will make a decision on whether to delay/cancel the P.F.E. in total or in part.

11. No part of the P.F.E. requires crews to carry life-vests.


Flotation devices not required
12. Trikes, Gyros, Quiksilvers will be permitted to request a launch during the early morning in order to reduce the effects turbulence - such aircraft will be known as Early Launchers. If a trike/Quiksilver/gyro does not request an early launch, it will be treated the same as any other aircraft in terms of scoring.

13.  All teams will be required to attend the flight briefing on Saturday 29th November at Eastern.

14.  Non-competitive entries will be permitted for those who would like to fly the course for fun, but without a data-logger.

No comments:

Post a Comment