...
For a MLS PANS-AIM requires some specific properties as part of the minimum AIP data set. These are
... identification, name, ... hours of operation, ..., channel..., position, ..., magnetic bearing, true bearing, ...
In addtion PANS-AIM AD2.19/AD 3.18 require
...type of supported operation for ILS/MLS, ... and for VOR/ILS/MLS also station declination ...used for technical line-up of the aid;
...If the operating authority of the facility is other than the designated governmental agency, the name of the operating authority shall be indicated in the remarks column. Facility coverage shall be indicated in the remarks column.
The diagram below shows the AIXM classes, including the relevant data types, needed to encode that information The main classes are Azimuth and Elevation which is a specialisation of the NavaidEquipment.
Designator & Name
The Azimuth will be have designator coded.
In general, the Elevation will not have a value for the designator attribute. If yes, it shall be identical to the designator of the localizer.
In general, neither the Azimuth nor the Elevation will have a name.
Hours of Operation
See topic Hours of Operation for Navaid.
Azimuth Channel
The Azimuth.channel attribute is used to code indicating the channel on which the Microwave Landing System is operating.
The corresponding data type class CodeMLSChannelType provides a list of values in a range from '500' to '699'.
Position
For mor edetails see topic Navaid Position & Elevation.
Glide Path Angle
For the minimum/conditional AIP data set the normal glide path angle of an MLS is actually not required by PANS-AIM (it is only listed in the PANS-AIM Appendix 1).
The angle of the glide path is coded using the Elevation.angleNominal and the Elevation.angleAccuracy attributes.
Station Declination
...
In AIXM 5 the type of supported operation (e.g. CAT IIIA) is coded using the Navaid.signalPerformance attribute. Hence, the signal performance level indicating the precision of an MLS is not encoded for a particular component but the whole MLS system.
| Note | ||
|---|---|---|
| ||
| In AIXM 5 the degree to which navigation aids provide accurate approach guidance for a runway direction will be encoded using the precisionApproachGuidance attribue of the RunwayDirection class. In case data is provided for both attributes it has to be ensured that it is not contradictory, i.e. the ILS category defined for the runway direction can not be higher that the one of the ILS sytsem serving the runway firection. |
...
For more information about the coding of an MLSsystem, see topic Navaid Component & Navaid Colocation.
Operating Authority
See topic Operating Authority for Navaid.
Facility Coverage
See topic Facility coverage.
Served Runway Direction
In AIXM 5 the runway direction the MLS is provided for has to be coded using the Navaid.runwayDirection property. The corresponding relationship isInstalledAt indicates that the navaid (i.e. the MLS system) is installed at a particular landing area. Hence, not a component of the MLS but the whole MLS system will be related to a particular runway direction. For more information about the coding of an MLS system, see topic Navaid Component & Navaid Colocation.
Coding Rules for MLS
| Identifier | Data Encoding Rule | Justification | Data Verification Rule (UID) | Remarks |
|---|---|---|---|---|
| MLS-101 | The Azimuth.designator attribute is mandatory. | Minimum AIP data set | TBD | |
| ILZ-105 | The Azimuth.channel attribute is mandatory. | Minimum AIP data set | TBD | |
| ILZ-106 | The Azimuth.location property is mandatory. | Minimum AIP data set | TBD | |
| IGP-102 | The Elevation.location property is mandatory. | Minimum AIP data set | TBD | |
| IGP-103 | The Glidepath.angleNominal atribute 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 | 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 | 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 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). | EAD | TBD | |
| ILZ-116 | The value of the Localizer.frequency has to lie between '108' 'MHz' and '111.975' 'MHz' | EAD/ ICAO Annex 10, Vol. 1 | TBD | |
| IGP-107 | The Glidepath.location must be plausibly close (less than 1 KM) to that of the threshold of the related (through Navaid.runwayDirection) RunwayDirection. | EAD | TBD | |
| IGP-108 | The value of the Glidepath.frequency has to lie between '328.6' 'MHz' and '335.4' 'MHz'. | EAD/ ICAO Annex 10, Vol. 1 | TBD | |
| IGP-109 | The value of the Glidepath.slope has to lie between '1' and '5' degrees. | EAD/ ICAO Annex 10, Vol. 1 | TBD | |
| IGP-110 | The value of the Glidepath.rdh has to lie between '10' and '25' 'M' (metres). | EAD/ ICAO Annex 10, Vol. 1 | TBD |
Coding Examples
The figure below shows an outdated publication of an MLS in an AIP.
...