...
However, as a TACAN may be used for navigation purposes for civil aviation, and in some states it is also published in the civil AIP, and is defined in ARINC 424
(VHF Navaid Section (D) and TACAN-Only NAVAID Record (DT)), it is also covered by this coding guidelines.
...
Identifier | Data Encoding Rule | Justification | Data Verification Rule (UID) | Remarks |
---|---|---|---|---|
TCN-101 | The TACAN.designator attribute is mandatory. | Minimum AIP data set | AIXM-5.1_RULE-1A33CB | |
TCN-102 | The TACAN.name attribute is mandatory. | Minimum AIP data set | TBD | |
TCN-103 | The TACAN.channel attribute is mandatory. | Minimum AIP data set | AIXM-5.1_RULE-1A3356 | |
TCN-104 | The TACAN.location property is mandatory. | Minimum AIP data set | AIXM-5.1_RULE-1A3389 | |
TCN-105 | For TACAN ElevatedPoint.elevation is mandatory. | Minimum AIP data set | TBD | |
TCN-106 | For TACAN ElevatedPoint.accuracy should be provided. | PANS-AIM | TBD | |
TCN-107 | For TACAN ElevatedPoint.verticalDatum should be provided. | PANS-AIM | TBD | |
TCN-108 | TACAN.designator shall not be duplicated within 600 NM of the location of the TACAN (see Annex 11, Appendix 2, paragraph 2.2.2). | EAD / ICAO Annex 11 | TBD | |
TCN-109 | No more than one TACAN may be co-located with same VOR. | EAD / Data consistency | TBD | |
TCN-110 | The value of the TACAN.channel must be paired with the VOR.frequency of the related VOR; the channel-frequency pairing table is identical to the one for DME-VOR, as contained in Table A, ICAO Annex 10, Vol.1. | EAD / Data consistency | TBD |
Coding Examples
TBD in the scope of the DONLON AIXM 5.1.1 AIP data set file.Coding examples can also be found in the Sample AIP Data Set (DONLON).
No. | Description | XPath Expression |
---|---|---|
NAV-EX-01 TCN-EX-01 | VOR/DME | //aixm:NavaidTimeSlice [@gml:id ='NAVTSOSTO'] | //aixm:TACANTimeSlice [@gml:id ='TACANOSTO'] |