| 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.
...
PANS-AIM requires for the DME an elevation to be coded. The DME.location will be coded with the ElevatedPoint.elevation attribute.
...
| title | Open question elevation for Navaid feature |
|---|
...
.
...
Depending on the type of DME, different accuracy is required. In AIXM, the ElevatedPoint.verticalAccuracy attribute is provided for that purpose (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)).
...
| 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.
...
| Tip | ||
|---|---|---|
| ||
The example below shows the publication of a "ghost frequency" of a DME in ENR 4.1
|
| Info | ||
|---|---|---|
| ||
A change proposal (AIXM-543) for the next AIXM 5.2 version has been approved by the AIXM Change Control Board, where the DME ghostFrequency attribute is tuningFrequencyVHF. The coding guidelines provided here are aligned with forward/backward conversion rules contained in the AIXM-543 Change Proposal. |
Navaid Collocation
A DME may be co-located with one and only one VOR or NDB. In this case the corresponding Navaid feature will reference the DME as navaidEquipment.
...
For more details see Landing Systems & Navaid Collocation.
Coding Rules for DME
...
| Info | ||
|---|---|---|
| ||
| Shall there be the same rule for DME and NDB? |
...
.
...
...
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).
...
Coding Examples
Coding examples can also be found in the DONLON AIXM 5.1.1 AIP data set file AIP Data Set - Specimen (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'] |
...