Page Comparison

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

...

...

• outages of navigation aids affecting serving several airports and/or FIR

...

• ;

...

• establishment of ATS

...

• airspace serving more than one airport;

...

• obstacles

...

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

...

• 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 ( which may contain one airport code or up to seven FIR codes). It has to be assured that the NOTAM appear correctly in the relevant en-route and airport Pre-Flight Information Bulletins ( PIB ) and that duplications 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 item A content limitations (maximum 7 FIR or 1 airport), NOTAM series allocation or other national requirements, different options exists exist to assure correct PIB appearancesinclusion.  The 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.Most frequently done in practice is serving

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 or completely separating FIR from airport NOTAM and issuing . When more than one FIR is affected, the typical solution is to issue one NOTAM for the FIR or FIR(s) all the affected FIRs and one NOTAM for each affected airport/heliport. This practice is explained in the OPADD version 4.1, item 2.3.9.3. 

Airport PIB is served by qQ-line qualifier scope A, the airport affected is indicated in Item A. En-route PIB is served by qQ-line qualifier scope E or W (depending on the event), the FIR(s) affected is indicated in Item A or in . In the case of NOTAM combining scope AE or AW, the FIR can be derived from the qQ-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.

The dedicated scenarios provide the rules for NOTAM containing the designator of one (or more) FIR (scope W or E) in Item A and those for a combined NOTAM (scope AW or AE) containing the designator of the affected airport in Item A. This NOTAM is referred to as “first NOTAM” in the dedicated scenarios.

If the issuance of additional airport (scope A) NOTAM are required (or for any other airport NOTAM if not combined with the en-route one), each airport NOTAM is issued separately in accordance with the following rules and is referred to as “additional NOTAM” or “for the rest of the NOTAM”:

...

Rules for additional airport NOTAM

The Event association with airports and/or FIR allows for explicitly identifying the aerodromes and/or FIR affected by the Event Also, an Event can have several NOTAM associated.

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:

...

...

...

...

...

...

...

...

...

                          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.                        

...