...
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
.
Position
...
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.
For more details see topic Navaid Position & Elevation.
...
| 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.servedAiport) and has VOR.type equal-to 'DVOR';; b) less than 80 metres if the VOR is located at an aerodrome/heliport (connected through Navaid.servedAiport) 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.servedAiport). | EAD | TBD |
Coding Examples
TBD