...
See topic Landing Systems & Navaid Collocation.
Coding Rules for TACAN
| Identifier | Data Encoding Rule | Justification | Data Verification Rule (UID) | Remarks |
|---|
| TCN-101 | The TACAN.designator attribute is mandatory. | Minimum AIP data set | TBD |
|
| 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 | TBD |
|
| TCN-104 | The TACAN.location property is mandatory. | Minimum AIP data set |
|
|
| TCN-105 | For TACAN ElevatedPoint.elevation is mandatory. | Minimum AIP data set | TBD |
|
| TCN- |
105| 106 | For TACAN ElevatedPoint.accuracy should be provided. | PANS-AIM | TBD |
|
| TCN- |
106| 107 | For TACAN ElevatedPoint.verticalDatum should be provided. | PANS-AIM | TBD |
|
| TCN- |
107| 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- |
108| 109 | No more than one TACAN may be co-located with same VOR. | EAD / Data consistency | TBD |
|
| TCN- |
109| 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