Actually, TACAN is not covered by PANS-AIM as it is considerd as military facility which is not under civil autority (and thus also not covered by ICAO Annex 10, Aeronautical Telecommunications).
However, as a TACAN may also be used for navigation purposes for civil aviation and in some states is also published in the civil AIP it is covered by the coding guidelines.
For general PANS-AIM requirements valid for all kind of Radio navigation aids see topic Navaid [NAV] and subordinated pages.
A UHF Tactical Air Navigation beacon (TACAN) is a navigation system developed by military and naval forces providing, as far as the navigating pilot is concerned and for suitably equipped aircraft, the same indication as a VOR/DME system (i.e. provides bearing and range information).
Henc, for a TACAN the following additional properties defined in PANS-AIM for the minimum AIP dat aset for radio navigation aids are relevant:
...channel, ...elevation,...
The diagram below shows the AIXM classes, including the relevant data types, needed to encode that information The main class is the TACAN which is a specialisation of the NavaidEquipment.
TACAN Channel
The channel of the TACAN system is coded using the TACAN.channel attribute.
In case a TACAN is collocated with a VOR (i.e. for a VORTAC), certain requirements have to be taken into account regarding frequency pairing.
Elevation
PANS-AIM requires for the DME an elevation to be coded. For the TACAN.location the ElevatedPoint.elevation will be coded.
Note
Depending on the type of DME different accuracy is required (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).
Navaid Component
A TACAN may be co-located with VOR. Such a VORTAC will be coded as a Navaid with two correspondning NavaidEquipment instances, a VOR and a TACAN.
The NavaidComponent.collocationGroup for both navaidEquipment will be coded with equal-to '1'.
Coding Rules
TBD
Coding Examples
See topic Navaid [NAV].