...
The reason is primarily related to how NOTAM are currently selected for inclusion in Pre-flight Information Bulletins (PIB), based on the item A (airport code or FIR code). It has to be assured that the NOTAM appear correctly in the relevant en-route and airport PIB and that duplication in PIB (e.g. in the FIR) are avoided. Depending on the number of affected airports and FIR, NOTAM format limitations such as the limitation of Item A (maximum 7 FIR or 1 airport), NOTAM series allocation or other national requirements, different options exists exist to assure correct PIB inclusion. The NOTAM for the en-route and airport part of the PIB may also be combined, provided NOTAM rules are respected. This is often done to reduce the number of NOTAM issued.
...
Each "decoding" scenario that may be affected by this situation includes a section with the title "Several NOTAM possible", which provides specific rules for that scenario. Each scenario contains the detailed NOTAM generation rules for the “first NOTAM”. This section contains rules that are applied when issuing the additional airport (scope A) NOTAM:
| Q-line | FIR |
|---|
...
| Insert the designator of the overlying FIR of the airport indicated in Item A | |
| Q code |
...
| Insert the Q codes as indicated in the dedicated scenario. |
...
| Traffic | Pre-filled according to ICAO doc 8126 NSC for the selected Q-code |
...
| Purpose | Pre-filled according to ICAO doc 8126 NSC for the selected Q-code | |
| scope |
...
A
lower limit: 000
upper limit: 999
Geo reference: Insert the coordinations of the ARP (aerodrome reference point) of the airport indicated in Item A
Item A: Insert the airport affected
Item E: Insert the text as indicated in the dedicated scenarios.
As a pure aerodrome NOTAM (scope A) does not allow the use of items F and G and appears for an aerodrome only in PIB,
information about the vertical extend may be added to Item E as follows for those scenarios with an Item F and G:
...