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

Note: this scenario corresponds to two NOTAM Templates: "Ad-hoc PRD and TSA creation” and “Ad-hoc Navigation Warnings ”. Therefore, two production rules are included in this scenario.

Text NOTAM production rules

This section provides rules for the automated production of the text NOTAM message items, based on the AIXM 5.1 data encoding of the Event. Therefore, AIXM specific terms are used, such as names of features and properties, types of TimeSlices, etc:

  • the abbreviation ASE.BL. indicates that the corresponding data item must be taken from the Airspace BASELINE that is created by the Event;

Several NOTAMs 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, there are special provision in the OPADD (v4.0, 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).

In order to facilitate the work of the operator, the Digital NOTAM data provider interface should include the following functionality:

  • automatically identify the FIR(s) in which the area is located and propose that a single NOTAM is issued for these FIR(s);

  • automatically identify CTR and TMA that are intersected by the area; then identify the AirportHeliport that are located in those CTR/TMA and that also have a value for their locationIndicatorICAO attribute; propose that a separate NOTAM is issued for each of these airports;

  • if the area does not intersect any TMA or CTR but it's lowerLimit is equal or less than 1000 FT from SFC, then automatically identify the AirportHeliport that have their ARP (reference point) located within 5 NM (this might need to be a configurable parameter) and also have a value for their locationIndicatorICAO attribute; propose that a separate NOTAM is issued for each of these airports;

  • In all situations, the operator shall be allowed to take the final decision by selecting the airports/FIR for which a NOTAM is really generated. This might include additional ones, which have not been identified automatically by the spatial checks but have an operationally significant relation with the area.

The rules for the “first NOTAM” and the NOTAM containing one or more FIR in Item A are indicated below. For any additional NOTAM with scope A, refer to “several NOTAM possible” section.

Item A

The item A shall be generated according to the geographical location of the Airspace as follows:

  • if no AirportHeliport NOTAM are issued, then item A shall contain the Airspace.designator of the FIR(s) for which the NOTAM is issued;

  • if one or more airports NOTAM are issued, then each such NOTAM shall contain the AirportHeliport.locationIndicatorCAO of the airports for which the NOTAM is issued.

    • if AirportHeliport.locationIndicatorICAO is empty, then CXXX or CCXX shall be used, where C/CC are the country code. In this case, the AirportHeliport.name shall be added at the beginning of item E (see OPADD 2.3.14). Note that this element does not appear in the item E pattern diagram further down.

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” and for the NOTAM containing one or more FIR in item A:

ASE.BL.type

ASE.BL.AirspaceActivation.activity

Corresponding Q code(s)

P

any (except MILOPS)

QRPCA

R

any (except MILOPS)

QRRCA

D

any (except MILOPS)

QRDCA

TSA

any (except MILOPS)

QRRCA or QRTCA

TRA

any (except MILOPS)

QRRCA or QRTCA

any

MILOPS

QRMLP

W

any

QRRCA

D-OTHER, A or OTHER

AERIAL_WORK, FIRE_FIGHTING, LASER, HI_RADIO

QRDCA

D-OTHER, A or OTHER

none specified

QRDCA

D-OTHER, A or OTHER

AIRSHOW

QWALW

D-OTHER, A or OTHER

SPORT, AEROBATICS

QWBLW

D-OTHER, A or OTHER

EXERCISE, NAVAL_EXER, TRAINING

QWELW

D-OTHER, A or OTHER

REFUEL

QWFLW

D-OTHER, A or OTHER

GLIDING

QWGLW

D-OTHER, A or OTHER

BLASTING

QWHLW

D-OTHER, A or OTHER

BALLOON

QWLLW

D-OTHER, A or OTHER

TOWING

QWJLW

D-OTHER, A or OTHER

MISSILES, AIR_GUN, ARTILLERY, FIREWORK,

QWMLW

D-OTHER, A or OTHER

PARACHUTE, PARAGLIDER, HANGGLIDING

QWPLW

D-OTHER, A or OTHER

CHEMICAL, NUCLEAR

QWRLW

D-OTHER, A or OTHER

GAS

QWSLW

D-OTHER, A or OTHER

UAV

QWULW

D-OTHER, A or OTHER

BIRD

QAFHX

D-OTHER, A or OTHER

OTHER:DEMOLITION

QWDLW

D-OTHER, A or OTHER

OTHER:CAPTIVE_BALLOON, OTHER:KITE

QWCLW

D-OTHER, A or OTHER

OTHER:ACFT_MASS_MOVEMENT

QWTLW

D-OTHER, A or OTHER

OTHER:ACFT_FORMATION

QWVLW

D-OTHER, A or OTHER

OTHER:VOLCANO

QWWLW

D-OTHER, A or OTHER

OTHER:MODEL

QWZLW

PROTECT

ACCIDENT, VIP

QROLP

OTHER

OTHER

QRACA or QWELW

For every affected AirportHeliport, a separate NOTAM with scope ‘A’ only is issued in order to provide correct information in all PIB sections for all concerned FIR and AD and to avoid duplications (See OPADD 2.3.9.3,AW). All scope ‘A’ NOTAM to contain ARP as the geographical reference and NOTAM Code QFALT (aerodrome limited) without Item F) and G). If required, the vertical limits are inserted in Item E).

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

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 airport, 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

Apply the common rules for {{Lower limit / Upper limit}}.

Geographical reference

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.

Items B, C and D

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

If at least one ASE.BL.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.

  • Important Note: timeInterval(s) that appear as child of ASE.BL.activation.AirspaceActivation with status=INACTIVE shall not be translated (because they were encoded for the completeness of the digital data encoding, see rule ER-04).

Item E

Two patterns are possible for automatically generating the item E text from the AIXM data.

Item E for ad-hoc PRD, TSA area

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

EBNF Code
template_area = ["Temporary(1)"] "ASE.BL.type(2)" ["(" "ASE.BL.designator" ")"] ["ASE.BL.name"] established \n
[for "ASE.BL.AirspaceActivation.activity(3)"]  ["(" "ASE.BL.annotation(4)" ")"] "within:" "\n" \n
"ASE.BL.geometryComponent.horizontalProjection(5)" {excluding "ASE.BL.geometryComponent(6)"} "." \n
["\n" "ASE.BL.AirspaceActivation.annotation(7)" "." ] \n
{"\n" "ASE.BL.annotation(8)" "." }.

Item E for ad-hoc navigation warnings

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

EBNF Code
template_nav_warning = ["Temporary(1)"] "ASE.BL.AirspaceActivation.activity(3)" "will take place within:" "\n" \n
"ASE.BL.geometryComponent.horizontalProjection(5)" {excluding "ASE.BL.geometryComponent(6)"}  ["(" "ASE.BL.annotation(4)" ")"] "." \n
["\n" "ASE.BL.AirspaceActivation.annotation(7)" "."] \n
{"\n" "ASE.BL.annotation(8)" "."}.

Reference

Rule

(1)

If ASE.BL.type is different than TSA and TRA insert the word "Temporary". Otherwise, ignore this branch.

(2)

The area type shall be included according to the following decoding table:

ASE.BL.type

Text to be inserted in Item E

P

"Prohibited Area"

R

"Restricted Area"

D

"Danger Area"

TSA

"Temporary Segregated Area"

TRA

"Temporary Reserved Area"

W

"Warning Area"

A

"Alert Area"

PROTECT

"Protection Area"

(3)

The activity code shall be translated into readable text, as indicated below.

  • ACCIDENT => "flight accident site"

  • AERIAL_WORK => "aerial work"

  • AEROBATICS => "aerobatics"

  • AIR_DROP* => "air dropping"

  • AIR_GUN => "firing"

  • AIRSHOW => "air display"

  • ANTI_HAIL* => "anti hail missiles launch"

  • ARTILLERY => "artillery firing"

  • BALLOON => "ascent of balloon"

  • BIRD => "bird presence"

  • BIRD_MIGRATION* => "bird migration"

  • BLASTING => "explosives blasting"

  • CHEMICAL => "chemical hazard"

  • CROP_DUSTING => "crop spraying"

  • EXERCISE => "military exercise"

  • FAUNA* => "fauna protection"

  • FIRE_FIGHTING => "fire fighting"

  • FIREWORK => "fireworks"

  • GAS => "gas hazard"

  • GLIDING => "glider flying"

  • HANGGLIDING => "hang gliding"

  • HI_RADIO => "high power radio transmissions"

  • JET_CLIMBING* => "jet climbing"

  • LASER => "laser hazard"

  • MILOPS => "military operations"

  • MISSILES => "missile firing"

  • NATURE* => "nature protection"

  • NAVAL_EXER => "naval exercise”

  • NO_NOISE* => "noise prevention reasons"

  • NUCLEAR => "nuclear hazard"

  • OIL* => "oil hazard"

  • OTHER => "activity"

  • OTHER:ACFT_FORMATION => "formation flight"

  • OTHER:ACFT_MASS_MOVEMENT => "mass movement of acft"

  • OTHER:CAPTIVE_BALLOON => "captive balloon"

  • OTHER:DEMOLITION => "demolition with explosives"

  • OTHER:KITE => "kite activities"

  • OTHER:MODEL → "model flying"

  • OTHER:SAR → "SAR"

  • OTHER:SKY_LANTERN → "ascent of sky lanterns"

  • OTHER:VOLCANO => "significant volcanic activity"

  • PARACHUTE => "parachute jumping exercise”

  • PARAGLIDER => "paragliding"

  • POPULATION* => "population protection"

  • RADIOSONDE* => "radiosonde launching"

  • REFINERY* => "refinery hazard"

  • REFUEL => "air refueling"

  • SHOOTING* => "firing"

  • SPACE_FLIGHT => "space flight"

  • SPORT => "sporting activities"

  • TECHNICAL* => "technical activities"

  • TOWING => "banner/target towing"     

  • TRAINING => "training activities"

  • UAV => "unmanned acft system activities"

  • ULM => "ultralight motorized acft activities"

  • VIP => "VIP protection"

  • VIP_PRES* => "head of state protection"

  • VIP_VICE* => "vice-head of state protection"

  • WATER_BLASTING* => "water blasting"

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

(4)

If specified, insert here only the ASE.BL.annotation that has propertyName="geometryComponent", which represents the encoding of the "location note" information. Annotations shall be translated into free text according to the decoding rules for annotations.

(5)

The GML encoding of the horizontalProjection (gml:Surface) shall be translated into human readable text, using latitude/longitude values.

(6)

If specified as a ASE.BL.geometryComponent with operation="SUBTR", insert here the designator and the type of the ASE.BL.geometryComponent.contributorAirspace. This requires interpreting the xlink:href value in order to recuperate the relevant data from the contributorAirspace BASELINE. If more than one airspace is excluded from the preceding horizontalProjection, then the word "and" shall be included before the second, third, etc. exclusion.

(7)

This is the “controlling unit” annotation, according to the coding rules. Annotations shall be translated into free text according to the common rules for annotations decoding.

(8)

This is used in case there are other annotations associated with the Airspace. Annotations shall be translated into free text according to the common rules for annotations decoding.

Note: The objective is to 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).

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 text indicated in the dedicated scenario up to ASE.BL.geometryComponent(6) including full stop,
  2. insert 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.

Items F & G

The values in items F and G shall be formatted according to decoding rules for {{Item E, F, G - Vertical Limits}}:

  • insert in item F the value (including its reference and unit of measurement) of the ASE.BL.geometryComponent.lowerLimit;

  • insert in item G the value (including its reference and unit of measurement) of the ASE.BL.geometryComponent.upperLimit.

Event Update

The eventual update of this type of event shall be encoded following the general rules for {{Event updates 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.

Two patterns are possible for automatically generating the item E text from the AIXM data.

Cancellation of ad-hoc PRD, TSA area

EBNF Code
template_cancel_area = "ASE.BL.type(2)" ["(" "ASE.BL.designator" ")"] ["ASE.BL.name"] "cancelled." \n
["New NOTAM to follow.(8)"].
Cancellation of ad-hoc navigation warning

EBNF Code
template_cancel_nav_warning = "ASE.BL.AirspaceActivation.activity(3)" "cancelled." \n
["New NOTAM to follow.(8)"].

Reference

Rule

(9)

If the NOTAM will be followed by a new NOTAM concerning the same situation, then the operator shall have the possibility to specify "New NOTAM to follow." and this text shall be appended at the end of item E of the NOTAM C.

Note: in this case, the 4th and 5th letters of the Q code shall also be changed into “XX”.

On this page

  • No labels