Page Comparison

Several NOTAM possible

Note that if an ad-hoc special activity area is located in the vicinity of one or more airports or affects 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 for the first NOTAM (the values marked with an asterisk * are unlikely to occur in practice, they are provided for completeness sake and to prevent undefined situations for the automatic creation of NOTAM):

Note:

• In the situations where two or more Q code alternatives are provided in the table above, the first one should be used as default in a data provider interface. The operator shall have the possibility to select an alternative one or even to change it completely (for example, by using "XX").

Scope

As general rules, for each NOTAM  that is generated:

• If Item A contains the designator of one (or more) FIR, insert W.

• If Item A contains the ICAO code of an AirportHeliport, insert AW, for the first such NOTAM and value A for the rest of the NOTAM.

However, more specific rules may be applied, depending on the split in NOTAM series, actual configuration of the FIR, etc. These have to be taken into consideration for each implementation.

Lower limit / Upper limit

For the first NOTAM, for activation with baseline limits, apply the common rules for {{Lower limit / Upper limit}}

For the activations with changed limits, the same procedures apply as for activations within normal limits, with the only difference that not always the value indicated in Items F or G is used as basis but the one relevant for PIB inclusion/exclusion:

• Lower limit: use the lowest value between ASE.BL.AirspaceVolume.lowerLimit and ASE.TD.AirspaceActivation.AirspaceLayer.lowerLimit as basis for entry in lower limit of Q line.

• Upper limit: use the highest value between ASE.BL.AirspaceVolume.upperLimit and ASE.TD.AirspaceActivation.AirspaceLayer.upperLimit as basis for entry in lower limit of Q line.

Geographical reference

For the first NOTAM, calculate the centre and the radius (in NM) of a circle that encompasses the whole special activity area. 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.

Item B, C and D

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

If at least one ASE.TD.activation.AirspaceActivation.timeInterval exists (meaning that the Event has an associated schedule), then it shall be represented in Item D according to the common NOTAM production rules for {{Item D, E - Schedules}}. Otherwise, Item D shall be left empty.

Item E

Two patterns are possible for automatically generating the E field text from the AIXM data:

Published PRD, TSA - area activation

This template shall be used when the ASE.BL.type has one of the values P, R, D, TSA, TRA, W, MTR, OTHER:MOA, OTHER:AAR.

template_1 = "ASE.BL.type(1)" ["ASE.BL.designator(2)"] ["ASE.BL.name(2)"] "ASE.TD.AirspaceActivation.status(3)" \n["," "ASE.TD.AirspaceActivation.activity(5)"] "." "\n" \n
["Vertical limits changed during activation(6)" "." "\n"]  \n
{"\n" "ASE.TD.annotation(7)" "."}.

Published Navigation Warning Areas - activity

This template shall be used when the ASE.BL.type has a value different from P, R, D, TSA, TRA, W.

template_2 = "ASE.TD.AirspaceActivation.activity(5)" "will take place (4) within area" "ASE.BL.name(2)" "." "\n" \n
["Vertical limits changed during activation(6)" "." "\n"]  \n
{"\n" "ASE.TD.annotation(7)" "."}.

Note: The objective is the full automatic generation of the NOTAM text, 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).

Rules for additional airport NOTAM

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:

1. complete the text indicated in the dedicated scenario up to completing ASE.TD.AirspaceActivation.status(3) in template_1 or ASE.BL.name(2) including comma in template_2,

2. insert "from", followed by the value contained in Item F of the first NOTAM including unit of measurement, 

3. insert "to", followed by value contained in Item G of the first NOTAM including unit of measurement,  

4. full stop

template_scope_A =  "from" "ASE.BL.geometryComponent.lowerLimit" "to" "ASE.BL.geometryComponent.upperLimit" ".".

Items F & G

The values to be inserted in Item F and G depend on the values of the ASE.TD.activation.AirspaceActivation.levels.

• If lowerLimit="FLOOR" then Item F shall get the lowest value between all ASE.BL.geometryComponent.lowerLimit of the parent Airspace;

• If lowerLimit has any other value, then Item F shall get that value (including its reference and unit of measurement);

• If upperLimit="CEILING" then Item G shall get the highest value between all ASE.BL.geometryComponent.upperLimit of the parent Airspace;

• If upperLimit has any other value, then Item G shall get that value (including its reference and unit of measurement).

In all situations, the values in Items F and G shall be formatted according to common decoding rules for {{Item E, F, G - 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 some 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.

Two patterns are possible for automatically generating the E field text from the AIXM data:

Cancellation of Published PRD, TSA - area activation

This template shall be used when the ASE.BL.type has one of the values P, R, D, TSA, TRA, W.

template_cancel_1 = "ASE.BL.type(1)" ["ASE.BL.designator(2)"] ["ASE.BL.name(2)"] ("activation cancelled." | " : New NOTAM to follow.(8)").

Cancellation of Published Navigation Warning Areas - activity

This template shall be used when the ASE.BL.type has a value different from P, R, D, TSA, TRA, W.

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

template_cancel_2 = "ASE.TD.AirspaceActivation.activity(5)" "within area" "ASE.BL.name(2)" ("cancelled." | " : New NOTAM to follow.(8)").