Page tree
Skip to end of metadata
Go to start of metadata

Introduction

Some events may require the issuance of several NOTAM from one Digital NOTAM encoding. Typical events are:

  • airspace activities in the vicinity of airports;
  • airspace activities affecting more than one FIR;
  • outages of navigation aids affecting serving several airports and/or FIR;
  • establishment of ATS airspace serving more than one airport;
  • obstacles in the vicinity of several airports
  • etc.

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 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.

The most frequent practical solution is to identify one airport and its associated FIR by one NOTAM (with scope AE) and issue any additional airport (or FIR) NOTAM separately. An alternative is to completely separate FIR from airport NOTAM and issuing one NOTAM for the FIR or FIR(s) and one NOTAM for each airport.

Airport PIB is served by Q-line qualifier scope A, the airport affected is indicated in Item A. En-route PIB is served by Q-line qualifier scope E or W (depending on the event), the FIR(s) affected is indicated in Item A. In the case of NOTAM combining scope AE or AW, the FIR can be derived from the Q-line FIR or more frequently by database association of the airport indicated in Item A.

Correlation of NOTAM scope and Item A:
Scope A     →  Item A: 1 airport
Scope W    →  Item A: 1 or several FIR (max 7)
Scope E     →  Item A: 1 or several FIR (max 7)
Scope AW  →  Item A: 1 airport
Scope AE   →  Item A: 1 airport
For further details refer to OPADD document.

Rules for additional airport NOTAM

From a Digital NOTAM point of view, this requires that an Event can have several NOTAM associated, which is supported by the Event model.

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



FIRInsert the designator of the overlying FIR of the airport indicated in Item A
Q codeInsert the Q codes as indicated in the dedicated scenario.
TrafficPre-filled according to ICAO doc 8126 NSC for the selected Q-code
PurposePre-filled according to ICAO doc 8126 NSC for the selected Q-code
ScopeA
Lower limit000
Upper limit999
Geo referenceInsert the coordinations of the ARP (aerodrome reference point) of the airport indicated in Item A
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/GDo not exist for scope A NOTAM
  • No labels