PANS-AIM requires some as part of the minimum AIP data set the hours of operation for radio navigation aids (for both enroute and terminal radio navigation and landing aids).
...
It is possible to code the availability of a Navaid and also of a NavaidEquipment.
As a general rule, the availability of a NavaidEquipment should only be coded in case of a navaid is composed of more than one navaid equipment, whereas at least one of them has a different availability than the others. If for one navaid equipment the availbility is coded, the availability has to be coded for all other navaid equipments of that navaid. For the navaid itself no availability will be coded. E.g. for a VOR/DME, in case the DME and VOR have different working hours, the availability will be ecoded encoded for both navaid equipments separately, but not for the navaid).
In case of a navaid composed of one single navaid equipment or a navaid composed of more navaid equipments all having the same working hours, the availability will only be coded for the Navaid, it . It is not necessary to copy it for the individual navaid equipment(s) (e.g. in case of a an ILS, where all components (LOC, GP, Markers) have the same working hours, the availability will only be coded for the navaid).
Info | ||
---|---|---|
| ||
Are this rule these rules ok (see also below), or shall the availability also , if it is the same, always be copied to all navaid equipments the navaid is composed of? If the working ours hours of the navaid equipment is different, shall also the availability of the navaid be coded with "PARTIAL" an dno 'PARTIAL' and no timesheet? |
The NavaidOperationalStatus class carries two attributes:
The signalType attribute indicated indicates the type of information transmitted by a navaid or other radio emission source (e.g. azimuth or distance) .
Info | ||
---|---|---|
| ||
How shall this attribute be used? Does it make sense to define tham them at all, ? A DME per see has a signattype Distancesignaltype distance, etc. How can this be coded by using timesheet? |
The operationalStatus indicates the state of the navaid:
'OPERATIONAL' | Operating normally. | |||||
'UNSERVICEABLE' | Not available. | |||||
'ONTEST' | On test, do not use. | |||||
'INTERRUPT' | Expect interruptions of the signal. | |||||
'PARTIAL' | Operating with limited capabilities. For example, used when just the DME part of a VOR/DME is working.
| |||||
'CONDITIONAL' | Operative subject to published limitations or conditions. | |||||
'FALSE_INDICATION' | Giving false indication, do not use. | |||||
'FALSE_POSSIBLE' | False indication possible, use with caution. | |||||
'DISPLACED' | Displaced | |||||
'IN_CONSTRUCTION' | In Construction | |||||
'OTHER' | Other |
For the AIP data set the default value for the hours of operation for a navaid will be 'OPERATIONAL'. Most of the others status are only relevant for an application of the Digital NOTAM concept.
Info | ||
---|---|---|
| ||
In case a navaid is not operational H24, the rest of the time it shall be coded as unservicable? Rule to be added? |
In addition, altough although not required by PANS-AIM for the minimum AIP data set, the NavaidEquipmentMonitoring class is used to define if the navaid equipment is monitored ('YES') or not ('NO'). Corresponding Timesheet may be used to define the corresponding time constraints.
For details of how to encode the Timesheet see topic Schedule [TSH]).
Coding Rules for Hours of Operation for Navaid
...