...
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.
Normally this is the code referring to the event. For events where the normal code cannot be used (SAA.ACT and SAA.NEW), QFALT is used instead.
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:
For the SAA.ACT scenario, complete the text indicated in the dedicated scenario upto completing completing TD.AirspaceActivation.status(3) or BL.name(2)including comma, followed by "from", followed by the value contained in Item F
followed by "from", followed by the value contained in Item F of the first NOTAM including unit of measurement, followed by "to", followed by value contained in Item G of the first NOTAM
Item G of the first NOTAM including unit of measurement, followed by full stop.
For the SAA.NEW scenario, complete text indicated in the dedicated scenario upto BL.geometryComponent(6) including fullstop,
followed by the value contained in Item F of the first NOTAM including unit of measurement,
followed by "to" followed by value contained in Item G of the first NOTAM including unit of measurement, followed by a full stop.
Examples:
Aerobatics will take place:
2NM radius centred on 483052N 0092008E. From 2000FT AMSL to FL100.
...