...
| 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 | |
| Item F/G | Do not exist for scope A NOTAM | |
...
For the SAA.ACT scenario, complete the text indicated in the dedicated scenario upto completing TD.AirspaceActivation.status(3) or BL.name(2)including comma,
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 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.
: