Basic Data for Navaid

For Radio navigation aid, PANS-AIM requires some basic properties as part of the minimum AIP data set. These are

type. identification, name, aerodrome served, hours of operation, magnetic variation, frequency/channel, position, elevation, magnetic bearing, true bearing, zero bearing direction

The diagram below shows the AIXM classes, including the relevant data types, needed to encode that information:

Navaid Type

AIXM 5 defines the Navaid class as follows:

A service providing guidance information or position data for the efficient and safe operation of aircraft supported by one or more radio navigation aids.

In PANS-AIM this is actually the definition for "Radio navigation service".

However, in AIXM 5 a Navaid is composed of one or more NavaidEquipment.

The navaid.type attribute is used to code the type of the navaid (actually the service provided by one or more radio navigation aids).

Some examples:

A Navaid.type equal-to 'VOR' is composed of one NavaidEquipment which is a VOR.

A Navaid.type equal-to 'VOR_DME' is composed of two NavaidEquipment one which is the VOR and another one which is the DME.

A Navaid.type equal-to 'ILS' may be composed of  e.g. four NavaidEquipment, a Localizer, a Glidepath and two MarkerBeacon (one middle and one outer Marker).

Navaid Purpose

This information is also not required by PANS-AIM to be provided. However, for the scope of a data set content and publication reasons it may be relevant to code that information.

The Navaid.purpose attribute is used to indicate the intended usage of the navaid i.e. 'ENROUTE' (E) or 'TERMINAL'  (A) or 'BOTH' (AE i.e. dual purpose).

In an AIP the purpose of a navaid is publishe in section GEN 2.5  List of Radio Navigation Aids.

In addition navaids published in ENR 4.1 Radio navigation aids — en-route will be used 'ENROUTE' per definition. On the other hand navaids published in AD 2.19/AD 3.18 Radio navigation and landing aids are per definition of 'TERMINAL' usage.

Navaid Designator & Name

A Navaid.designator is used to provide the coded identifier given to the navaid system.

It is limited to 4 characters, which may be upper case alpha and/or digit characters.

Depending on the specialised NavaidEquipment different concepts and rules for the navaid designator may be applied (see also specialised navaid equipment topics).

The Navaid.name is used for the long name given to the composite navaid. For the name of the navaid maximum 60 upper case alpha and/or numerical characters and also some special characters may be used.

Aerodrome Served

Navaids of type VOR, DME, NDB, TACAN and Marker with purpose Aerodrome (A or AE) will be assigned to one (or more) Airport/Heliport.

For instance, a VOR that is serving two different approaches for two different Aerodromes.

This association is established via the Navaid.servedAirport property, i.e. not the individual navaid equipment is related to the airport/heliport but the whole navaid system (e.g. the VOR/DME and not the VOR and the DME).

ILS and MLS are associated to a certain runway/FATO direction of an airport/heliport (see topics Localizer, Glidepath and MLS).

Navaid Position

Coding Rules for Basic Data for Navaid

TBD

Coding Examples

See topic Navaid [NAV]