[2.0] [ATSA.ACT] Published ATS airspace - activation or deactivation (NOTAM)

Several NOTAM possible

Some ATS airspace are established in order to protect flights to/from airports. Depending on size and/or purpose, they serve one or more airports. In exceptional cases, they may impact more than one FIR. Explicit associations between the Event and one or more AirportHeliport or Airspace may be coded. Then, there exist dedicated provision in the OPADD (v4.1, section 2.3.9.3) with regard to the NOTAM that need to be issued in order to ensure that the NOTAM appear correctly in the relevant en-route and airport Pre-Flight Information Bulletins (PIB). Further details are provided in the “several NOTAM possible” section.

The NOTAM production rules provided on this page, unless specified otherwise, are applicable to the “first NOTAM” and the NOTAM containing one or more FIR in Item A. 

Item A

The item A shall be generated according to the general production rules for item A using the concernedAirspace(s) or the concernedAirportHeliport, according to the rules specified in table above.

Item Q

Apply the common NOTAM production rules for item Q, complemented by the following specific rules for this particular scenario:

Q code

The following mapping shall be used:

Scope

For each NOTAM  that is generated:

• If Item A contains the designator of one (or more) FIR, insert E.
• If item A contains the ICAO code of an airport, then insert AE for the first such NOTAM and value A for the rest of the NOTAM.

Lower limit / Upper limit

Apply the common NOTAM production rules for Lower limit / Upper limit.

In case of multiple sectors affected by activation/deactivation, the lowest and highest values shall be considered. 

Geographical reference

Calculate the centre and the radius (in NM) of a circle that encompasses the whole ATS airspace (in the case of multiple sectors, encompass all these sectors, taken together). Insert these values in the geographical reference item, formatted as follows:

• the set of coordinates comprises 11 characters rounded up or down to the nearest minute; i.e. Latitude (N/S) in 5 characters; Longitude (E/W) in 6 characters. The radius consists of 3 figures rounded up to the next higher whole Nautical Mile; e.g. 10.2NM shall be indicated as 011.

See also the Note with regard to the risk that the circle/radius does not encompass the whole area, as discussed in the Location and radius}} common rules for the NOTAM text generation.

Items B, C and D

Items B and C shall be decoded following the common production rules.

Item D shall be left empty. If at least one ASE.TD.activation.AirspaceActivation.timeInterval exists (the Event has an associated schedule), it shall be decoded in item E.

Item E

One of the following patterns should be used for automatically generating the E field text from the AIXM data:

De-activation

If the ASE.TD associated with the Event contains a single ASE.TD.AirspaceActivation and this one has status='INACTIVE'

template_deactivation = "ASE.BL.type(1)" "ASE.BL.name(2)" ["ASE.BL.designator"] ["(" "class" "ASE.BL.classification(3)" ")"] {"(4)" "ASE.BL.name(2)" ["ASE.BL.designator"] ["(" "class" "ASE.BL.classification(3)" ")"]}  "deactivated" "\n" ["ASE.TD.annotation(8)"].

Activation (eventually with schedule)

If the ASE.TD associated with the Event contains at least one ASE.TD.AirspaceActivation with status='ACTIVE'

template_activation = "ASE.BL.type(1)" "ASE.BL.name(2)" ["ASE.BL.designator"] ["(" "class" "ASE.BL.classification(3)" ")"] {"(4)" "ASE.BL.name(2)" ["ASE.BL.designator"] ["(" "class" "ASE.BL.classification(3)" ")"]} ("activated(5)" "\n" | "activated as follows(6):" "\n" "schedule(7)" "." "\n") \n
 ["ASE.TD.annotation(8)"]. 

Note: The objective is the full automatic generation, without human intervention. However, the implementers of the specification might consider reducing the cost of a fully automated generation by allowing the operator to fine-tune the text in order to improve its readability (with the inherent risk for human error, when re-typing is allowed).

Items F & G

Item F and item G shall be left empty.

Note: Values for item F & G are only required for Navigation Warnings (QW) and Airspace Reservations (QR). Inclusion of applicable vertical limits in Item E) for changes of Airspace organisation (QA) can be considered, but is not applicable for this scenario as it does not cover modification of vertical limits.

Event Update

The eventual update of this type of event shall be encoded following the general rules for Event update or cancellation, which provide instructions for all NOTAM fields, except for item E and the condition part of the Q code, in the case of a NOTAM C

If a NOTAM C is produced, then the 4th and 5th letters (the "condition") of the Q code shall be "CN", except for the situation of a “new NOTAM to follow", in which case “XX”shall be used. 

The following pattern should be used for automatically generating the E field text from the AIXM data:

• De-activation cancelled: If ASE.TD contains a single ASE.TD.AirspaceActivation and this one has status='INACTIVE'

template_deactivation_cancel = "ASE.BL.type(1)" "ASE.BL.name(2)" ["ASE.BL.designator"] ["(" "class" "ASE.BL.classification(3)" ")"] {"(4)" "ASE.BL.name(2)" ["ASE.BL.designator"] ["(" "class" "ASE.BL.classification(3)" ")"]}  ("deactivation cancelled." | " : New NOTAM to follow.(9)").

• Activation cancelled: If ASE.TD contains at least one ASE.TD.AirspaceActivation with status='ACTIVE'

template_activation_cancel = "ASE.BL.type(1)" "ASE.BL.name(2)" ["ASE.BL.designator"] ["(" "class" "ASE.BL.classification(3)" ")"] {"(4)" "ASE.BL.name(2)" ["ASE.BL.designator"] ["(" "class" "ASE.BL.classification(3)" ")"]} ("activation cancelled." | " : New NOTAM to follow.(9)").