...
Coding Rules for ILS/Localizer systems
| Identifier | Data Encoding Rule | Justification | Data Verification Rule (UID) | Remarks |
|---|
| ILZ-101 | The Localizer.designator attribute is mandatory. | Minimum AIP data set | TBD |
|
| ILZ-102 | The Localizer.magneticVariation attribute is mandatory. | Minimum AIP data set | TBD |
|
| ILZ-103 | The Localizer.dateMagneticVariation attribute should be provided. | PANS-AIM | TBD |
|
| ILZ-104 | The Localizer.magneticVariationAccuracy attribute should be provided. | PANS-AIM | TBD |
|
| ILZ-105 | The Localizer.frequency attribute is mandatory. | Minimum AIP data set | TBD |
|
| IGP-101 | The Glidepath.frequency attribute is mandatory. | Minimum AIP data set | TBD |
|
| ILZ- |
104| 106 | The Localiser.location property is mandatory. | Minimum AIP data set | TBD |
|
| IGP-102 | The Glidepath.location property is mandatory. | Minimum AIP data set | TBD |
|
| IGP-103 | The Glidepath.slope property is mandatory. | PANS-AIM | TBD |
|
| IGP-104 | The Glidepath.angleAccuracy property should be provided. | PANS-AIM | TBD |
|
| IGP-105 | The Glidepath.rdh property sis mandatory. | PANS-AIM | TBD |
|
| IGP-106 | The Glidepath.rdhAccuracy property should be provided. | PANS-AIM | TBD |
|
| ILZ-107 | Either the Localizer.magneticBearing or the Localizer.magneticBearing attribute shall be provided. | Minimum AIP data set | TBD |
|
| ILZ-108 | If the Localizer.magneticBearing |
| is provided than the Localizer.magneticBearingAccuray should be provided. | PANS-AIM |
If | TBD |
|
| ILZ-109 | If the Localizer.trueBearing |
| is provided than also the Localizer.trueBearingAccuray should be provided. | PANS-AIM | TBD |
|
| ILZ-110 | The Localizer.declination attribute should be provided. | PANS-AIM | TBD |
|
| NAV-901 | If Navaid.type equal-to 'ILS' or 'ILS_DME' or 'LOC' or 'LOC_DME' the Navaid.signalPerformance shall be provided. | PANS-AIM | TBD |
|
| NAV-902 | The Navaid.signalPerformance and the related RunwayDirection.precisionAppraochGuidance shall be consistent. | Data consistancy | TBD | For example if signalPerformance is CAT IIIA also the precisionAppraochGuidance shall be CAT IIIA. |
| ILZ-111 | The Localizer.backCourseUsable attribute should be provided. | PANS-AIM |
There must exist exactly one ILS Localizer for each Instrument landing system [ILS]. | The position given by GEO_LAT, GEO_LONG | TBD |
|
| ILZ-112 | If Navaid.type equal-to 'ILS' or 'ILS_DME' or 'LOC' or 'LOC_DME' it must have exactly one NavaidEquipment which is a Localizer. | EAD / Data consistancy | TBD |
|
| NAV-903 | If Navaid.type equal-to 'ILS' or 'ILS_DME' it must have exactly one NavaidEquipment which is a Glidepath. | Data consistancy | TBD |
|
| NAV-904 | If Navaid.type equal-to 'ILS_DME' or 'LOC_DME' it must have exactly one NavaidEquipment which is a DME. | Data consistancy | TBD |
|
| ILZ-113 | The Localizer.location must be plausibly close (less than 1 KM) to that of the end |
of the related (through ILS_M) RWY_DIRECTION.As a plausibility rule, the difference between VAL_MAG_BRG of the ILS_LLZ and VAL_MAG_BRG of the related RWY_DIRECTION cannot exceed 10 degrees (see ICAO Doc 8168, PANS OPS, Chapter 23, 'Offset Localizer'). | The difference between VAL_TRUE_BRG and VAL_MAG_BRG | of the related (through Navaid.runwayDirection) RunwayDirection. | EAD / Data consistancy | TBD |
|
| ILZ-114 | The difference between Localizer.magneticBearing and the related RunwayDirection.magneticBearing (through Navaid.runwayDirection) cannot exceed 10 degrees. | EAD / ICAO Doc 8168, PANS OPS | TBD |
|
| ILZ-115 | The difference between Localizer.trueBearing and Localizer.magneticBearing has to be consistent with the value VAL_MAG_VAR in the referred AD_HP, taking in consideration the current date and the annual rate of change (VAL_MAG_VAR_CHG in the referred AD_HP). |
As a plausibility rule, the | EAD | TBD |
|
| ILZ-116 | The value of the |
VAL_FREQ | Localizer.frequency has to lie between '108' 'MHz' and '111.975 |
MHz (see | ' 'MHz' | EAD/ ICAO Annex 10, Vol. 1 |
, section 3.1.3.2.).GP | The position given by GEO_LAT, GEO_LONG | TBD |
|
| IGP-107 | The Glidepath.location must be plausibly close (less than 1 KM) to that of the threshold of the |
related As a plausibility rule, the value of the VAL_FREQ ILS_M) RWY_DIRECTION.| Navaid.runwayDirection) RunwayDirection. | EAD | TBD |
|
| IGP-108 | The value of the Glidepath.frequency has to lie between '328.6' 'MHz' and '335.4' 'MHz'. |
(see | EAD/ ICAO Annex 10, Vol. 1 |
, section 3.1.5.2).As a plausibility rule, the value of the VAL_SLOPE | TBD |
|
| IGP-109 | The value of the Glidepath.slope has to lie between '1' and '5' degrees. |
As a plausibility rule, the value of the VAL_RDH | EAD/ ICAO Annex 10, Vol. 1 | TBD |
|
| IGP-110 | The value of the Glidepath.rdh has to lie between '10' and '25 |
metres (see | ' 'M' (metres). | EAD/ ICAO Annex 10, Vol. 1 |
, section 3.1.5.1.4).Coding Examples
TBD