Proposals for amendments to FAI Section 10.
This year, 2007, Richard Meredith-Hardy is the coordinating editor for Section 10 and its annexes.
How to submit amendments
Only CIMA delegates may submit proposals for inclusion here. Anyone else should submit their proposal to their delegate first. The full list of delegates is on the FAI website.
The amendment scheme will operate as it was done last year, all proposals from CIMA delegates should be sent to Richard Meredith-Hardy with:
1) The number of the affected paragraph (or where it should go, if it is something new).
2) The reason for the proposed change.
He will then assemble this into the document below, along with:
a) Comment from the S10 Sub-Committee
b) Comments any other CIMA delegates wish to make on the proposal.
Each proposal will be put to the vote in its exact wording at the CIMA Plenary meeting 16 -18 November 2007 on the basis of a YES or a NO. It is not usual for the wording of proposals to be amended at the meeting itself.
The deadline for proposals for amendments is 23:59:59 UTC THURSDAY 27 SEPTEMBER 2007. After that, you will have to wait until next year....
Comment from the S10 Sub-Committee will be inserted before Wednesday 3 October when it will be passed to the CIMA Secretary for inclusion in the CIMA Plenary agenda.
Changes
- This is NOT the latest draft. Draft 4 18 September 2007 Addition of proposals 8 & 9
- Draft 3, 14 September 2007 Addition of proposal 7
- Draft 2, 13 September 2007 Addition of proposals 5 and 6
- Draft 1, 11 September 2007
Contents
|
No. |
Title |
From |
Affects |
|
Clarification of minimum leg lengths in closed circuit records. |
Richard Meredith-Hardy CIMA S10 Editor. |
All |
|
|
Clarification of altitude tolerance in speed records over a straight course |
Richard Meredith-Hardy CIMA S10 Editor |
All |
|
|
Clarification of laps in closed circuit records |
Richard Meredith-Hardy CIMA S10 Editor |
All |
|
|
Exceptional units of measurement in timing |
Richard Meredith-Hardy GBR Delegate |
All |
|
|
Clarification of units of time in S10 and Annex 3 |
Richard Meredith-Hardy CIMA S10 Editor |
All |
|
|
Rules for team scoring in paramotor classes |
José Luis Esteban, Spanish alternate delegate |
Paramotors |
|
|
Limited fuel championship records in Class PF2 |
Richard Meredith-Hardy CIMA S10 Editor |
PF2 |
|
|
Delete the two 'without engine power' records |
Richard Meredith-Hardy CIMA S10 Editor |
All |
|
|
Improvement of the FR track file naming protocol |
Richard Meredith-Hardy, CIMA FRAC chairman |
All |
Clarification of minimum leg lengths in closed circuit records.
from Richard Meredith-Hardy CIMA S10 Editor.
Affects
All microlight classes
Existing text
S10 3.8.3 All legs of closed circuits must be of equal length but a deviation of up to ± 5% per leg is permitted in circuits of three or more legs.
New text
S10, 3.8.3 All legs of closed circuits must be of equal length with the following permitted deviation:
- 3 legs: all legs must be between 28% and 38% of the total length.
- 4 legs: all legs must be between 20% and 30% of the total length.
- 5 legs: all legs must be between 15% and 25% of the total length.
- 6 legs: all legs must be between 11% and 27% of the total length.
Reasons
When the rules for records were re-written in 2006, the purpose was to clarify and simplify without substantially altering the principle objectives of any record.
Pre 2007 rules said a closed circuit can be an out and return or a triangle, and triangles must be quite equal in as much as no leg can be less than 28% of the total distance. The 2007 rules allowed more turnpoints for closed circuits longer than 100 Km. (up to 6), but leg length must still be more or less equal but with a permitted deviation of up to ± 5% per leg which was intended to be an insignificant 0.33% more severe than the existing 28% rule.
In the current S10 3.8.3 there are several interpretations of how this deviation should be calculated, in other words the phraseology of the provision is unsatisfactory. For people attempting records in 2007, guidance of how FAI / CIMA has chosen to interpret the rule was inserted in the notes at the beginning of the record claim form on the FAI web site.
This proposal is therefore not a change but intended to formalize the guidance currently being used and which can be removed from the notes in the claim form.
Comments from S10 Sub Committee or CIMA delegates
None at this time
CIMA decision
Proposal 1 ACCEPTED DENIED
Clarification of altitude tolerance in speed records over a straight course
from Richard Meredith-Hardy CIMA S10 Editor.
Affects
All microlight classes
Existing text
None
New text
INSERT: S10 3.14.5
The altitude at which the aircraft crosses the start line on the second run must be within 100m of the altitude at which it crossed the start line on the first run.
Reason
The amendments to S10 which came into effect 1 Jan 2007 inadvertently forgot that there are 2 runs associated with this record and to be like the pre 2007 rules, both runs must done at approximately the same altitude. Guidance of how FAI / CIMA has chosen to maintain this for people attempting records in 2007 was inserted in the notes at the beginning of the record claim form on the FAI web site and says that they will interpret S10 3.14.2 to mean the SAME tolerance of 100 metres on the 1000m run-up applies to BOTH runs, not each run separately.
This amendment returns the record to what it was before 1 Jan 2007 in a clearer form. The current guidance can be removed from the notes in the claim form.
Comments from S10 Sub Committee or CIMA delegates
None at this time
CIMA decision
Clarification of laps in closed circuit records
From Richard Meredith-Hardy, S10 Editor
Affects
All microlight classes
Existing text
None
New text
INSERT: S10 3.8.6
A closed circuit may only be flown once.
Reason
The amendments to S10 which came into effect 1 Jan 2007 inadvertently omitted that the pre-2007 rules did not allow multiple laps of closed circuits in closed circuit record claims.
Interpretive guidance was placed in the claim form notes early 2007 making it clear that adding together the combined distance of multiple laps of a closed circuit is not acceptable in a closed circuit record claim.
This amendment returns the record to what it was before 1 Jan 2007 in a clearer form. The current guidance can be removed from the notes in the claim form.
Comments from S10 Sub Committee or CIMA delegates
None at this time
CIMA decision
Exceptional units of measurement in timing.
From Richard Meredith-Hardy, GBR Delegate
Affects
In principle, all microlight classes, in current practice; only the paramotor classes.
Existing text
None
New text
INSERT: S10 5.2.7
Exceptional units of measurement.
Timed precision tasks in championships shall be rounded down to an accuracy of 1/10th of a second if manual timing is used, or rounded down to an accuracy of 1/100th of a second if an approved electronic timing system is used.
Reason
A problem arose about this at WPC 2007.
Normal units of measurement as stated in S10 5.2.6 are HH:MM:SS. Increments of less than a second do not exist in S10. This is adequate for all purposes except some paramotor precision tasks where more accurate timing is desirable.
1/10th of a second is considered about as accurate as can be done by manually timing with a stopwatch whereas electronic timing systems may provide greater accuracy. In the absence of any approval system, "approved" is intended to mean "Approved by the International Jury", in other words if an electronic timing system appears to work to their satisfaction for the intended purpose then timing may be done to an accuracy of 1/100th of a second.
"Rounded down" is intended to mean the time which is taken is the time which is displayed on the time piece rather than it being artificially rounded later to a precision greater than permitted. Thus if a manual time of 0:0:45.5655 is taken, the time recorded shall be 0:0:45.5 as was displayed on the stopwatch to the required precision and NOT rounded in 1/100ths of a second to 0:0:45.6
Comments from S10 Sub Committee or CIMA delegates
None at this time
CIMA decision
Clarification of units of time in S10 and Annex 3
From Richard Meredith-Hardy, S10 Editor
Affects
All microlight classes
Proposal 5a existing text
4.29.6 All distances not obtained from GNSS shall be calculated from the official map and rounded up to the next 0.5 km. All times are taken to hours, minutes and seconds.
Proposal 5a new text
4.29.6
All distances not obtained from GNSS shall be calculated from the official map
and rounded up to the next 0.5 km. All times are taken to hours, minutes and
seconds.
Note: The same thing should be deleted from S10 An 3 1.14.1
Proposal 5b existing text
An 3, 1.12.1 TIMING All times are given, taken and calculated in local time to the nearest second.
Proposal 5b new text
An 3, 1.12.1 TIMING All times are given, taken and calculated in local time or simple elapsed time, rounded down to the most accurate permitted precision. (see S10 5.2.6 and 5.2.7)
Reason
5a: S10 5.2.6 adequately describes units of measure that should always be used. When mixed in with a reference to distances measured off maps and instances when sub-second timings may be used, (see proposal 4) this reference to hours minutes and seconds is confusing and should be deleted.
5b: A problem arose about this at WPC 2007. The phrase 'nearest second' in this context implies that some sort of rounding in sub-second increments should be applied even though the notion of sub-one second timing increments does not exist in the main body of S10. (ref S10 5.2.6)
5b therefore seeks to delete this inadequate description of S10 requirements as stated in S10 5.2.6 (and additionally Proposal 4 for sub-second intervals in certain cases)
By stating 'rounded down' 5b seeks to establish that a time taken or given is the time as displayed on a timing device and no artificial rounding is applied in increments smaller than those permitted.
5b also establishes that elapsed time may be used (as it is in fact more convenient and commonly used in certain tasks, but nothing to say it can be used).
Comments from S10 Sub Committee or CIMA delegates
None at this time
CIMA decision
Proposal 5a ACCEPTED DENIED
Rules for team scoring in paramotor classes.
From José Luis Esteban, Spanish alternate delegate.
Affects
Only the paramotor classes
Existing text
4.29.3 The team score shall be computed from the sum of the scores of the top three pilots of each country in each class in each task grouped together in:
- Classes AL1, AL2, WL1, and WL2
- Classes PL1 and PL2
- Class PF
Proposal 6a new text
4.29.3 The team score shall be computed from the sum of the scores of the top three pilots of each country in each class in each task grouped together in:
- Classes AL1, AL2, WL1, and WL2
- Classes PF1, PF2, PL1 and PL2
Proposal 6b new text
4.29.3 The team score shall be computed from the sum of the scores of the top three pilots of each country in each class in each task grouped together in:
- Classes AL1, AL2, WL1, and WL2
- Class PF1
- Class PF2
- Class PL1
- Class PL2
If there are less than 4 countries in a class, it will not be included in any team scoring.
If there are less than 8 competitors in either PF1 or PF2, they will be combined into PF team prize.
If there are less than 8 competitors in either PL1 or PL2, they will be combined into PL team prize.
If there are less than 8 competitors in either PF or PL, they will be combined in a common team prize.
If there are less than 8 competitors or less than 4 countries in either PF or PL, they will be combined in a common team prize.
Reason
During the last World championship in China, PF2 was an official class for the first time. However, there was no agreement on how to incorporate this class in team scoring. Mixing PF2 with PF1 seemed like a contamination to PF1. On the other hand, mixing PF2 with PL did not make much sense. In any case
Option A is consistent with the classic classes approach and it encourages countries to enter competitors in all classes.
Option B allows one team prize per class, but provides a method to mix related classes in the team prize so that a reasonable number of competitors and countries is achieved.
Comments from S10 Sub Committee or CIMA delegates
None at this time
CIMA decision
Proposal 6a ACCEPTED DENIED
Proposal 6b ACCEPTED DENIED
Limited fuel championship records in Class PF2
From Richard Meredith-Hardy, CIMA S10 Editor
Affects
Only class PF2
Existing text
3.17.8.1 DISTANCE WITH LIMITED FUEL ..... Classes WL1, AL1 & PL2: 4 Kg .....
3.17.8.2 ENDURANCE WITH LIMITED FUEL ..... Classes WL1, AL1 & PL2: 4 Kg .....
New text
3.17.8.1 DISTANCE WITH LIMITED FUEL ..... Classes WL1, AL1, PF2 & PL2: 4 Kg .....
3.17.8.2 ENDURANCE WITH LIMITED FUEL ..... Classes WL1, AL1, PF2 & PL2: 4 Kg ......
Reason
PF2 competed in 2007 for the first time in China, but they could not qualify for either of the above two championship records because nothing is said in S10 about what the maximum permitted fuel quantity is for this class.
This proposal seeks to include PF2 in the max 4Kg fuel bracket along with WL1, AL1 and PL2
The endurance task was done in China. If this proposal is accepted and the International Jury has ratified that the winner of the PF2 class in the endurance task satisfied all the conditions, then the Jury may ask the plenary (in another agenda item) to accept the performance done in China as a new Championship record.
Comments from S10 Sub Committee or CIMA delegates
None at this time
CIMA decision
Proposal 7 ACCEPTED DENIED
Delete the two 'without engine power' records
From Richard Meredith-Hardy, S10 Editor
Affects
All microlight classes
Existing text
3.2 RECORD CATEGORIES IN EACH CLASS
....
3.2.2 DISTANCE IN A STRAIGHT LINE WITHOUT ENGINE POWER
3.2.5 DISTANCE IN A CLOSED CIRCUIT WITHOUT ENGINE POWER
....
3.6 Special rules for distance in a straight line without engine power.
3.6.1 A barograph or GNSS flight recorder shall be carried which records any use of engine.
3.6.2 The aircraft must have its engine stopped prior to crossing the start line and it must not be re-started until after crossing the finish line.
3.6.3 The altitude of the aircraft at the finish line shall not be less than the altitude of the aircraft at the start line.
3.6.4 The distance shall be measured as the geodesic joining the point the start line was crossed and the point the finish line was crossed.
3.10 Special rules for distance in a closed circuit without engine power.
3.10.1 The barograph or GNSS flight recorder used must be capable of recording any use of engine. 3.10.2 The aircraft must have its engine stopped prior to crossing the start line and it must not be re-started until after crossing the finish line.
3.10.3 The altitude of the aircraft at the finish line shall not be less than the altitude of the aircraft at the start line.
New text
Delete all of the above
Renumber S10 chapter 3 to account for the deleted paragraphs.
Reason
In the 25 years since these records were created there has been NOT ONE World record claim for either of these two records in any of the 18 microlight classes.
This clearly demonstrates that microlight pilots consider these two records to be irrelevant and it is time they were deleted from the catalogue of possible records.
Comments from S10 Sub Committee or CIMA delegates
None at this time
CIMA decision
Proposal 8 ACCEPTED DENIED
Improvement of the FR track file naming protocol
From Richard Meredith-Hardy, CIMA FRAC chairman
Affects
All microlight classes.
Existing text
S10 Annex 6
4.9.4.1 The default ‘short’ file name presented to the operator should be as follows: 000T00V0.IGC Where:
- Characters 1 – 3 are the pilot’s competition number, with leading zeros as necessary. (e.g. number 4 must be 004, this way all files will sort correctly in alphanumeric order.)
- Character 4 is fixed as T (for Task)
- Characters 5 & 6 are the task number, with leading zeros as necessary.
- Character 7 is fixed as V (for Version)
- Character 8 is the version number of the file, (ie this will be 1 the first time the file is created in the directory, but it will be 2 if the same data is transferred from the FR a second time. This makes it difficult for the operator to overwrite existing data.)
- Characters 9 to 12: fixed as .IGC This file suffix is the IGC standard and allows the file to be readily opened in many different flight analysis programs.
4.9.4.2 The preferred ‘long’ file name presented to the operator must be as above but include the pilot’s name: 000T00V0_PILOT_NAME.IGC
- The pilot name must be separated from the first 8 characters of the ‘short format’ name with the underscore ‘_’ character and all spaces in the pilot name must be replaced with the underscore ‘_’ character.- Pilot name must be in upper case characters A-Z, a-z and 0-9 only (ascii 65-90, 97-122 and 48-57). Accented characters etc. must be replaced with their nearest match from within this selection.
New text
S10 Annex 6
4.9.4.1 The file name presented to the operator should be as follows:
001T01V1R1_PILOT_name.IGC
Where:
- Characters 1 – 3 are the pilot’s competition number, with leading zeros as necessary. (e.g. number 4 must be 004, this way all files will sort correctly by competition number in alphanumeric order.)
- Character 4 is fixed as T (for Task)
- Characters 5 & 6 are the task number, with leading zeros as necessary.
- Character 7 is fixed as V (for Version)
- Character 8 is the version number of the file, (ie this will be 1 the first time the file is created in the directory, but it will be 2 if the same data is transferred from the FR a second time. This makes it difficult for the operator to overwrite existing data.)
- Character 9 is fixed as R (for Recorder). Note that for full backwards compatibility, analysis programs should appreciate that an underscore ‘_’ (ascii 95) may appear in this position.
- Character 10 is a number 1 to 9 indicating the status of the FR as declared by the pilot; 1 = Primary, 2 = first secondary, 3 = second secondary, Etc. Note that for full backwards compatibility, analysis programs should appreciate that if any other character appears in this position then the status of the FR is unknown.
- Character 11 is an underscore ‘_’ (ascii 95).
- Characters 12 to n is the pilot's name where n may not be more than 150. Pilot name must be in characters A-Z, a-z and 0-9 only (ascii 65-90, 97-122 and 48-57), accented characters etc. must be replaced with their nearest match from within this selection. All spaces in the pilot name must be replaced with the underscore ‘_’ (ascii 95).
- Characters n to n+4 are fixed as .IGC This file suffix is the IGC standard and allows the file to be readily opened in many different flight analysis programs.
Existing 4.9.4.2 is deleted.
Reason
Now that pilots are frequently using secondary FR's in championships it is desirable to include the distinction between primaries and secondaries in each saved FR track file name. In practice this has been done for some years by championship organizers to their own protocol, this proposal simply formalizes an amended file naming protocol in Annex 6 so that it can be exploited by flight analysis programs (eg by being able to open a primary track by default).
This proposed protocol is designed to be backwards compatible with existing FR download software. By definition it extends the mandatory file name beyond the original dos 8.3 'short' file format which for our purposes is now considered obsolete anyway.
This proposal therefore deletes the concept of a mandatory 'short' file name and a 'desirable' long file name and makes the 'long' file name mandatory with the added inclusion of a clause indicating FR status.
Note that although in practice pilot names are unlikely to be anything like as long as 138 characters, the total maximum length is set at 150 (rather than 255) to ensure compatibility with ISO 9960 which is used by many CD Rom mastering systems.
Comments from S10 Sub Committee or CIMA delegates
None at this time
CIMA decision
Proposal 9 ACCEPTED DENIED