| Panel | ||
|---|---|---|
| ||
|
Introduction & Background
This topic contains only those PANS-AIM requirements relevant for a DME. For general PANS-AIM requirements valid for all kind of Radio navigation aids see topic Navaid [NAV] and subordinated pages.
...
...elevation of the transmitting antenna of DME to the nearest 30 m (100 ft);...
...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.
| Warninginfo | ||
|---|---|---|
| ||
In PANS-AIM Appendix 1 the accuracy depends on the type of DME, for DME/P it is 3 meters. |
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.
...
| Tip | ||
|---|---|---|
| ||
The example below shows this information may be published in the Remarks of AD 2.19 / AD 3.18.
|
| Warning | ||
|---|---|---|
| ||
It is just a distance value without a reference (e.g. to the THR) . The. Workaround AIXM 5.1(.1): The reference shall be coded by an annotationa Note for the displace attribute if needed. Status AIXM 5.2: to be reported to CCB. |
Ghost Frequency
Although not required by PANS-AIM, a "ghost frequency" will be coded in case of a stand-alone DME.
...
| Identifier | Data Encoding Rule | Justification | Data Verification Rule (UID) | Remarks |
|---|---|---|---|---|
| DME-101 | The DME.designator attribute is mandatory. | Minimum AIP data set | AIXM-5.1_RULE-1A3350 | |
| 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-115 | The DME.location property is mandatory. | Minimum AIP data set | AIXM-5.1_RULE-1A3321 | |
| 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| Info | |
| ||||
| 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.servedAirport) and has VOR.type equal-to 'DVOR'; b) less than 80 metres if the VOR is located at an aerodrome/heliport (connected through Navaid.servedAirport) 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.servedAirport). | EAD | TBD |
...
Coding examples can also be found in the DONLON AIXM 5.1.1 AIP data set file Sample AIP Data Set (DONLON):
| No. | Description | XPath Expression |
|---|---|---|
NAV-EX-01 VOR-EX-01 DME-EX-01 | VOR/DME | //aixm:NavaidTimeSlice [@gml:id ='NAV_BOR'] | //aixm:VORTimeSlice [@gml:id ='VOR_BOR'] | //aixm:DMETimeSlice [@gml:id ='DME_BOR'] |
...