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.
A DME (Distance Measuring Equipment) is Ultra High Frequency (UHF) ground equipment that is used in conjunction with airborne equipment to determine distance between the airborne and ground equipment.
For a DME, PANS-AIM requires some specific properties as part of the minimum AIP data set. These are
identification, name, aerodrome served, hours of operation, ...channel, position, elevation, ...
In addition, PANS-AIM ENR 4.1 and AD 2.19/AD 3.18 state as requirement
...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.
PANS-AIM issue
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.
DME Designator & Name
In general a DME will carry a three letter character identifier. The DME.designator attribute is used to code that data.
The long name given to the DME is coded using the DME.name attribute.
DME Type
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 is coded using the DME.type attribute. The typr defines the particular spectrum characteristics or accuracy of the DME. The list of values for the CodeDMEType class contains:
| Value | Description |
|---|---|
| 'NARROW' | DME/N, narrow spectrum characteristics. |
| 'PRECISION' | DME/P, improved accuracy compared to DME/N |
| 'WIDE' | DME/W, wide spectrum characteristics. |
| 'OTHER' | Other. |
Aerodrome Served
See topic Basic Data for Navaid.
Hours of Operation
See topic Hours of Operation for Navaid.
DME Channel
The channel of the DME is coded using the DME.channel attribute.
The corresponding data type CodeDMEChannelType contains a list of values from '1X' to '126Y'.
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
See topic Navaid Position & Elevation.
Elevation
PANS-AIM requires for the DME an elevation to be coded. The DME.location will be coded with the ElevatedPoint.elevation attribute used.
Note
Depending on the type of DME different accuracy is required. In AIXM the ElevatedPoint.verticalAccuracy attribute is provided for that purpose. (According 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)).
Operating Authority
See topic Operating Authority for Navaid.
Facility Coverage
See topic Facility coverage.
Navaid Collocation
See topic Landing Systems & Navaid Collocation.
Coding Rules
| 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 |
Coding Examples
TBD