...
The diagram below shows the AIXM classes, including the relevant data types and code lists, needed to encode that information. The main class is the DME which is a specialisation of the NavaidEquipment.
DME Designator & Name
In general, a DME will carry a three-letter character identifier. The DME.designator attribute is used to code that data.
...
PANS-AIM does not require the type of the DME to be provided. However, PANS-AIM requires different accuracy values for the elevation of a DME depending on its type. As elevation for the DME is part of the minimum AIP data set the type has to be known. In AIXM, the tye type is coded using the DME.type attribute. The type defines the particular spectrum characteristics or accuracy of the DME. The list of values for the CodeDMEType class contains:
...
In case a DME is collocated with a VOR, certain requirements have to be taken in into account regarding the frequency pairing. The DME operating channel shall be paired with the VHF channel and/or MLS angle frequency as given in ICAO Annex 10, chapter 3, Table A
...
In case a DME collocated with a VOR is physically located at the same position as the VOR, the geographic position (latitude and longitude) of the VOR is also the geographic position of the DME.
In case a DME is collocated with a VOR and the position of the DME is different from the position of the VOR, some restrictions have to be taken into account (see Coding Rules below).
In case a DME is collocated with a VOR, unless otherwise specified, the published elevation (if any) refers to the DME. Thus, the elevation should be specified for the DME only.
...
Depending on the type of DME, different accuracy is required. In AIXM, the ElevatedPoint.verticalAccuracy attribute is provided for that purpose . (According according to PANS-AIM Appendix 1, Table A1-5, for DME.type equal-to 'PRECISION' 3m accuracy is required; for all other types it is 30m (100ft)).
...
This information is not required by PANS-AIM for the AIP data set, but often published in State AIPs. Also, ARINC 424 contains a data filed for the VHF NAVAID record type for "ILS/DME" Bias.
The DME.displace attribute is used to code the distance from the DME antenna to the position where the zero-range indication occurs in the DME receiver.
...
| Warning | ||
|---|---|---|
| ||
| It is just a distance value without a reference (e.g. to the THR). The reference shall the reference be coded by a Note. |
Ghost Frequency
Altough Although not required by PANS-AIM, a "ghost frequency" will be coded in case of a stand-alone DME not collocated with a VOR.
...
A DME may be co-located with one and only one VOR or NDB.
In the AIP, collocated VOR and DME Navaids are usually referred to as VOR/DME or DVOR/DME.
There are certain ICAO rules with regard to regarding the relative distance between the VOR and the DME, frequency pairing and coded identifier. They are mentioned as coding rules.
...
A particular DME may also be defined as a part (NavaidEquipment) of an a Navaid of type 'ILS' or 'MLS'. A single DME can be part of more than one ILS/MLS, but each ILS can have just one assigned DME.
...
| Identifier | Data Encoding Rule | Justification | Data Verification Rule (UID) | Remarks | |||||
|---|---|---|---|---|---|---|---|---|---|
| DME-101 | The DME.designator attribute is mandatory. | Minimum AIP data set | TBD | ||||||
| DME-102 | The DME.name attribute is mandatory. | Minimum AIP data set | TBD | ||||||
| DME-103 | The DME.channel attribute is mandatory. | Minimum AIP data set | TBD | ||||||
| DME-104 | For DME ElevatedPoint.elevation is mandatory. | Minimum AIP data set | TBD | ||||||
| DME-105 | For DME ElevatedPoint.accuracy should be provided. | PANS-AIM | TBD | ||||||
| DME-106 | For DME ElevatedPoint.verticalDatum should be provided. | PANS-AIM | TBD | ||||||
| DME-107 | No more than one DME may be co-located with same VOR. | EAD / Data consistency | TBD |
| |||||
| DME-108 | A DME and a TACAN cannot be collocated to the same VOR. | EAD / Data consistency | TBD | ||||||
| DME-109 | The DME.designator shall not be duplicated within 600 NM of the location of the DME. | EAD / ICAO Annex 11 | TBD | ||||||
| DME-110 | If DME.channel is not specified, then DME.ghostFrequency must be specified. | EAD | TBD | ||||||
| DME-111 | DME.ghostFrequency cannot be specified if the DME is collocated with a VOR or is part of an ILS or MLS system. | EAD / ICAO Annex 11 | TBD | ||||||
| DME-112 | DME.ghostFrequency must be consistent with the DME.channel value, according to Table A, ICAO Annex 10, Vol. 1. | EAD / ICAO Annex 11 | TBD | ||||||
| DME-113 | The value of the DME.channel must be paired with the VOR.frequency of the related VOR, as described by Table A, ICAO Annex 10, Vol.1. | EAD / ICAO Annex 10 | TBD | ||||||
| DME-114 | The geographical distance between the DME.location and the VOR.location which are used to compose the same Navaid must be: a) less than 30 metres if the VOR is located at an aerodrome/heliport (connected through Navaid.servedAiportservedAirport) and has VOR.type equal-to 'DVOR';; b) less than 80 metres if the VOR is located at an aerodrome/heliport (connected through Navaid.servedAiportservedAirport) and has VOR.type equal-to 'DVOR'; c) less than 600 metres if the VOR is not located at an aerodrome/heliport (not through Navaid.servedAiportservedAirport). | EAD | TBD |
Coding Examples
TBD