By Richard Meredith-Hardy, Chairman
CIMA Flight Recorder Approval Committee
Draft 1,
Words in italics
display existing (2003) text
Words in normal type indicate the
proposed amendments for 2004
*************************************************************************************************
The case must have
a tamper-proof physical seal across a joint or screw, so that the seal will be
broken if it is opened.
The case should have a tamper-proof physical seal across a joint or screw, so that the seal will be broken if it is opened.
*************************************************************************************************
Transfer data must
include all this information.
Transfer data must include at least the serial number.
*************************************************************************************************
It must be shown
that it is not possible to alter the firmware of the GNSS receiver or the memory
of the FR by connection to an outside source e.g. a PC except for specific
items such as input of pilot name or competition number.
It must be shown that it is not possible to alter the firmware of the GNSS receiver or the memory of the FR by connection to an outside source e.g. a PC without the entire memory being wiped clean in the process or to load specific items such as pilot name or competition number.
*************************************************************************************************
4.9.3.3 The operator must be offered the option
to insert a previously saved task (in IGC “C” record format) into the data file
in the correct place (see IGC-FR-TS) and a note of the inserted file-name made
in a LCMAOTIN record (see below)
4.9.3.3 The operator should be offered the option to insert a previously saved task (in IGC “C” record format) into the data file in the correct place (see IGC-FR-TS) and a note of the inserted file-name made in a LCMAOTIN record (see below)
*************************************************************************************************
4.9.3.4 If the FR only records GPS altitude, the
operator must be offered the option to fill the pressure altitude field of ‘B’
records with the GPS altitude data from the same record. A note of this must be made in a LCMAOPRS
record (see below).
4.9.3.4 If the FR only records GPS altitude, the operator should be offered the option to fill the pressure altitude field of ‘B’ records with the GPS altitude data from the same record. A note of this must be made in a LCMAOPRS record (see below).
*************************************************************************************************
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 the characters A-Z and 0-9 only (ascii
65-90 and 48-57). Accented characters etc. must be replaced with their nearest
match from within this selection.
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 the 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.
*************************************************************************************************
is
almost completely deleted and replaced with:
The I record defines any extensions to the fix (B) Record in the form of a list of the appropriate TLC’s, data for which will appear at the end of subsequent B Records. Only one I Record line is included in each file, There are no CIMA mandatory I record extensions but any optional elements allowable in the IGC specification are permitted. See the general specification IGC-FR-TS.
*************************************************************************************************
|
Fix validity |
1 byte. |
A or V |
Use A in the .IGC file to denote a 3-D fix and V for a 2-D fix. Where data
in NMEA format is used within the FR, in the GSA sentence (DOP and active
satellites), put A in the IGC file for GSA mode 3, and V for GSA mode 2. |
|
Fix validity |
1 byte. |
A or V or X |
Use A file to denote a 3-D fix V for
a 2-D fix and X for unknown. Where data in NMEA format is used
within the FR, in the GSA sentence (DOP and active satellites), put A in the
IGC file for GSA mode 3, and V for GSA mode 2. |
*************************************************************************************************
is
deleted
Is renamed 5.8.1
*************************************************************************************************
6.4.1 The ownership of the copyright to any flight recorder trace submitted by a pilot to the organizers of a FAI Category 1 or 2 championship for the purposes of flight analysis and scoring is deemed to be relinquished in favour of the FAI.
*************************************************************************************************
7.1 The observer must be sure that every condition in a FR’s approval document is complied with.
7.2 In the case of type 3 FR’s see the conditions of use above.
*************************************************************************************************
7.3 The ownership of the copyright to any flight recorder trace submitted by a pilot to the FAI for the purposes of substantiating a record claim is deemed to be relinquished in favour of the FAI.
*************************************************************************************************