Access Keys:
Skip to content (Access Key - 0)
All CIMA spaces

CIMA

This space

36 = Logging frequency

Proposal from

Richard Meredith-Hardy, CIMA President

Proposal title

Logging frenquency

Existing text

S10 Annex 6, 8.4

...

When crossing time is to be checked against an estimation given by the pilot or calculated by the scoring team, a margin equivalent to the logging period (P) must be applied. If a pilot crosses the gate up to P seconds too early or too late, he gets a zero (0) time error in the gate. If a pilot crosses the gate one more second too early or too late, he gets 1 second error in the gate.

The logging period (P) applied above must be the maximum allowed, regardless of the specific logging period used by an individual competitor, to avoid random advantage of some pilots over others. P is currently 5 seconds (A6 2.1.1.3)

New text

S10 Annex 6, 8.4

...
When crossing time is to be checked against an estimation given by the pilot or calculated by the scoring team, a margin equivalent to the logging period (P) must be applied. If a pilot crosses the gate up to P seconds too early or too late, he gets a zero (0) time error in the gate. If a pilot crosses the gate one more second too early or too late, he gets 1 second error in the gate.

The logging period (P) applied above must be the maximum allowed, regardless of the specific logging period used by an individual competitor, to avoid random advantage of some pilots over others. P is currently 5 seconds (A6 2.1.1.3)

Reason

The fact that someone chooses to use an old-fashioned logger which can only manage 5 second fixes is not 'random', it is a choice. CIMA rules should encourage pilots to acquire or develop improved loggers (which besides anything else are inexpensive, much easier to manage, and faster to download) but this margin of error means the default timing is equivalent to the worst loggers we allow, and removes all incentive for improvement. 

This provision also adds a whole layer of complication to the analysis and scoring which is quite unnecessary.

We could just amend An6 2.1.1.3 to make 1 sec. logging mandatory, but for the time being this seem a bit of an overkill especially while quite a lot of people are still using older loggers as their secondary, but we should have a means of encouraging the use of loggers which record at 1 sec intervals by making it in the pilots' interest to have one.  Deletion of this provision does that.


Added by Richard Meredith-Hardy Last edited by Robert HUGHES on 26 Sep, 2012 19:31. Quick links: http://wiki.fai.org/x/jADk or 36 = Logging frequency
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
Adaptavist Theme Builder Powered by Atlassian Confluence