...
For a VOR, PANS-AIM requires some specific properties as part of the minimum AIP data set. These are
...identification, name, ..., hours of operation, ..., frequency..., position, ..., zero bearing direction
In addtion PANS-AIM ENR 4.1. and also AD2.19/AD 3.18 require
...for VOR, station declination to the nearest degree used for technical line-up of the aid, ...
...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.
The diagram below shows the AIXM classes, including the relevant data types, needed to encode that information The main class is the VOR which is a specialisation of the NavaidEquipment.
VOR Designator & Name
In general a VOR will carry a three letter character identifier. The NavaidEquipment.designator attribute is used to code that data.
The long name given to the VOR is coded using the NavaidEquipment.name attribute.
VOR Type
In is not required by PANS-AIM to provide the type of a VOR. Because in some State AIPs this informtion is published it is also coverd covered by this guidelines.
The VOR.type attriute may be used to code that information. The list of values of the CodeVORType class contains:
...
The corresponding data type ValFrequencyType contains a uom attribute. For a VOR only the value equal-to 'MHZ' shall be used.
...
In some AIPs also the date (year) when the station declination was measured is published. Unlike for magnetic variation there is no dedicated attribute for station declination contained in AIXM 5. Corresponding information can only be recorded using a Note.
According to PANS-AIM for VOR the specific station declination should be provided rather than the local magnetic variation. However, in many AIPs the magnetic variation is published instead.
Coding Rules for VOR
TBD
Coding Examples
Example 1
In this Example In example 1 below the station declination of the VOR is published.
Example 2
In this example 2 below both the station declination and the magnetic variation of for the VOR is published and the year when it was measured.
For more examples see topic Navaid [NAV].
Hours of Operation
See topic Hours of Operation for Navaid.
Position
See topic Navaid Position & Elevation.
Operating Authority
See topic Operating Authority.
Facility Coverage
See topic Facility coverage.
Navaid Collocation
See topic Landing Systems & Navaid Collocation.
Coding Rules for VOR
| Identifier | Data Encoding Rule | Justification | Data Verification Rule (UID) | Remarks |
|---|---|---|---|---|
| VOR-101 | The VOR.designator attribute is mandatory. | Minimum AIP data set | TBD | |
| VOR-102 | The VOR.name attribute is mandatory. | Minimum AIP data set | ||
| VOR-102 | The VOR.designator shall not be duplicated within 600 NM of the location of the VOR (see Annex 11, Appendix 2, paragraph 2.2.2). | EAD / ICAO Annex 11 | TBD | |
| VOR-102 | The value of the VOR.frequency must be in the interval 108.000 to 117.975 MHz. | EAD / ICAO Annex 10 | TBD | |
| If a value for VOR.magneticVarition is provided it has to be identical with the Airport/Heliport.magneticVariation (if coded) of the AiportHeliport related to Navaid the VOR is a NavaidEquipment of. | Data consistency | TBD |
Coding Examples
TBD