Text NOTAM production rules
...
- the abbreviation NAV.BL. indicates that the corresponding data item must be taken from the Navaid BASELINE, which is valid at the start time of the Event;
- the abbreviation NAV.TD. indicates that the corresponding data item must be taken from the Navaid TEMPDELTA;
- the abbreviation NEQ.BL. indicates that the corresponding data item must be taken from the NavaidEquipment BASELINE, which is valid at the start time of the Event;
- the abbreviation NEQ.TD. indicates that the corresponding data item must be taken from the NavaidEquipment TEMPDELTA;
- Important note: According to encoding rule ER-11, the TEMPDELTA might also include NavaidOperationalStatus elements that have been copied from the BASELINE data for compliance with the AIXM Temporality rules. The current practice is to not include such static information in the NOTAM text. Therefore, all NavaidOperationalStatus that have an associated annotation with purpose=REMARK and the text="Baseline data copy. Not included in the NOTAM text generation" shall be excepted from the text NOTAM generation algorithm!
Several NOTAMs possible
There are several situations that can trigger the need to issue several NOTAM to ensure that the information appears Note that if the navaid is used for instrument approach or departures from one or more airports or affects the en-route navigation in one or more FIR, explicit associations between the Event and one or more AirportHeliport and/or Airspace may be coded. Then, there exist dedicated provision in the OPADD (v4.1, section 2.3.9.3) with regard to the NOTAM that need to be issued in order to ensure that the NOTAM appear correctly in the relevant en-route and airport Pre-Flight Information Bulletins (PIB). The Event 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 with scope AE and subsequent NOTAMs for each airport that is affected needs to be published, with the corresponding airport designator in item A.
The rules for the “first NOTAM” containing the FIR in Item A are indicated below. For any additional NOTAM, refer to “several NOTAM possible” section.
...
Further details are provided in the “several NOTAM possible” section.
The NOTAM production rules provided on this page, unless specified otherwise, are applicable to the “first NOTAM” and the NOTAM containing one or more FIR in Item A.
| Event.concernedAirspace | Event.concernedAirportHeliport | NOTAM to be generated |
|---|---|---|
| 1..* | None | produce a single NOTAM with scope E for all the FIR(s) identified |
| 1..* | 1..* | Produce a "first" NOTAM with scope E for all FIR and additional (scope A) NOTAM for each airport concerned. |
| 1 | 1..* | Produce a "first" NOTAM with scope AE for the FIR and one of the aerodromes associated with the Event and additional (scope A) NOTAM for each additional airport. |
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, except if there is an association Event to an AirportHeliport case in the AirportHeliport.designator shall be used.
...
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
...
Reference | Rule | ||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
(1) | The name of the Navaid shall be included if present in the 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 NEQ.TD associated with the Event, then insert the type of that equipment, according to the following decoding rule:
| ||||||||||||||||||||||||||||||||||||||||
(4) | If 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 NEQ.TD.operationalStatus decoded as follows:
| ||||||||||||||||||||||||||||||||||||||||
(9) | If specified, insert here only the 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. |
...