Text NOTAM production rules
...
There are several situations that can trigger the need to issue several NOTAM to ensure that the information appears in the relevant en-route and airport Pre-Flight Information Bulletins (PIB). The Event has can have an explicit associationEvent to AirportHeliport as defined in ER-12. If the Event has an associationEvent to an AirportHeliport, a "navaid unserviceable" NOTAM for each airport that is affected needs to be published, with the corresponding airport designator in item A.
More than one Navaid affected - a separate NOTAM shall be created for each NAV.TD associated with the Event for which at least one of its primary component NavaidEquipment also has a (E)TD associated with the same Event;
The rules for the “first NOTAM” and the NOTAM containing the FIR in Item A are indicated below, for . For any additional NOTAM with scope A, refer to “several NOTAM possible” section.
Note: A better solution would be that such navaid outages are translated into one NOTAM with the FIR in item A. Then, separate Events and separate NOTAM should be published for the affected Procedures, having the airport identifier in item A. This approach will be considered for the further development of this Specification, when the scenario for Procedures unavailability will be included.
Item A
The item A shall be generated according to the geographical location of the Airspace and shall contain the Airspace.designator of the predefined FIR(s) for which a NOTAM has to be issued. In addition, if one or more airports are predefined in the application as requiring a NOTAM during the activation of the area, then each such NOTAM shall contain in Item A the AirportHeliport.locationIndicatorICAO of the predefined airports for which a NOTAM has to be issued. If AirportHeliport. locationIndicatorICAO is empty, then CXXX or CCXX shall be used, where C/CC are the country code. In this case, the AirportHeliport.name shall be added at the beginning of Item E (see OPADD 2.3.14). Note that this element does not appear in the Item E pattern diagram further down.
Item Q
Apply the common NOTAM production rules for item Q, complemented by the following specific rules for this particular scenario:
...
The mapping provided in the tables below shall be used.
(N)NAV.BL.type | Corresponding Q codes (2nd and 3rd letters) |
ILS or ILS_DME | QIC - if both the Localizer and the Glidepath components have a (E)TD associated with the Event QID - if only its DME component has (E)TD associated with the Event QIG - if only its Glidepath component has (E)TD associated with the Event QIL - if only its Localizer component has (E)TD associated with the Event QII - if only its MKR component has (E)TD associated with the Event and its (N)BL.NavaidComponent.markerPosition=INNER QIM - if only its MKR component has (E)TD associated with the Event and its (N)BL.NavaidComponent.markerPosition=MIDDLE QIO - if only its MKR component has (E)TD associated with the Event and its (N)BL.NavaidComponent.markerPosition=OUTER QIY - if only its NDB component has (E)TD associated with the Event and its (N)BL.NavaidComponent.markerPosition=MIDDLE QIX - if only its NDB component has (E)TD associated with the Event and its (N)BL.NavaidComponent.markerPosition=OUTER |
MLS or MLS_DME | QIW |
NDB or NDB_MKR | QNB - if NDB component (E)BL.class=ENR QNL - if NDB component (E)BL.class=L |
LOC or LOC_DME | QIN |
DME | QND |
MKR | QNF |
VOR_DME | QNM |
TACAN | QNN |
VORTAC | QNT |
VOR | QNV |
DF | QNX |
NDB_DME, TLS or OTHER | QXX |
and
(N)NAV.TD.operationalStatus | Corresponding Q codes (4th and 5th letters) |
UNSERVICEABLE | AS |
ONTEST | CT |
INTERRUPT | LS |
PARTIAL | AS |
FALSE_INDICATION | XX |
DISPLACED | CM |
IN_CONSTRUCTION | XX |
OTHER | XX |
Scope
Insert here AE.
Items B, C and D
Items B and C shall be decoded from the values of (N) NAV.TD.validTime following the common production rules.
If at least one (N) NAV.TD.NavaidOperationalStatus.timeInterval exists (the Event has an associated schedule), then the associated Timesheets(s) shall be decoded in item D according to the common NOTAM production rules for {{Item D, E - Schedules}}. Otherwise, item D shall be left empty.
Item E
The following pattern should be used for automatically generating the E field text from the AIXM data:
...
Reference | Rule | ||||||||||||||||||||||||||||||||||||||||
(1) | The name of the Navaid shall be included if present in the (N)NAV.BL data | ||||||||||||||||||||||||||||||||||||||||
(2) | Insert the type from the Navaid baseline, according to the following decoding rule:
| ||||||||||||||||||||||||||||||||||||||||
(3) | If the Navaid Baseline has several Navaid components and only one of its primary component NavaidEquipment has a (E)NEQ.TD associated with the Event, then insert the type of that equipment, according to the following decoding rule:
| ||||||||||||||||||||||||||||||||||||||||
(4) | If (N)NAV.BL is TACAN or VORTAC and its (TACAN)TD.availability.signalType is specified, then insert its value here. | ||||||||||||||||||||||||||||||||||||||||
(5) | The following rules apply:
| ||||||||||||||||||||||||||||||||||||||||
(6) | Apply the following rules:
| ||||||||||||||||||||||||||||||||||||||||
(7) | Apply the following rules:
| ||||||||||||||||||||||||||||||||||||||||
(8) | Insert the (E)NEQ.TD.operationalStatus decoded as follows:
| ||||||||||||||||||||||||||||||||||||||||
(9) | If specified, insert here only the (E)NEQ.TD.NavaidOperationalStatus.annotation that has propertyName="operationalStatus" and purpose="REMARK", translated into free text according to the following encoding rules. | ||||||||||||||||||||||||||||||||||||||||
(10) | Annotations shall be translated into free text according to the rules for annotations decoding. |
...
Reference | Rule |
(11) | If the NOTAM will be followed by a new NOTAM concerning the same situation, then the operator shall have the possibility to specify "NEW New NOTAM TO FOLLOWto follow" and this text shall be appended at the end of item E of the NOTAM C. Note: in this case, the 4th and 5th letters of the Q code shall also be changed into “XX” |