...
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 coordinates of the ARP (aerodrome reference point) of the airport indicated in Item A | |
| Radius | 005 | |
| Item A | If available, insert the ICAO code of the airport affected. Otherwise, insert the nationality letter(s) as defined in ICAO Doc 7910 followed by “XX” or “XXX”. | |
| Item E | If Item A has no ICAO code, the AirportHeliport.name shall be added at the beginning of Item E (see OPADD 2.3.14). 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 | |
| Item F/G | Do not exist for scope A NOTAM | |