Versions Compared

Version Old Version 7 New Version 8
Changes made by

POROSNICU Eduard

POROSNICU Eduard

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Note: this scenario corresponds to two NOTAM Templates:"Published PRD, TSA - area - activation” and “Published Navigation Warning Areas – activity”. Therefore, two item E production rules are included in this scenario.

Text NOTAM production rules

...

For the activation of a special activity area, it is assumed that the FIR(s) and eventually the airport(s) for which a NOTAM is required to be issued have already been predefined in the application. It is recommended that the application suggests the list of airports for which a NOTAM is required, but the operator is allowed to take a final decision.

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. See also the discussion about several NOTAM possible and the further details in the Scope section further down.

Item A

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

...

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):

...

  • 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:

...

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

...

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

  • Upper limit: use the highest value between BL.AirspaceVolume.upperLimit and 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:

...

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 BL.type has one of the values P, R, D, TSA, TRA, W.


Published Navigation Warning Areas - activity

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

Image Modified


Reference

Rule

(1)

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


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"

MTR

“Military training route”

OTHER:MOA

“Military operations area”

OTHER:AAR

“Air-to-air refuelling area”

(2)

The designator and the name of the area shall be included if present in the BASELINE data.

(3)

The activation status code shall be translated into readable text, as follows:

  • ACTIVE => "activated"

  • IN_USE* => "in use"

  • INTERMITTENT => “activated (intermittent use)”

The values marked with an asterisk (*) are unlikely to occur in practice.

(4)

The activity code shall be translated into readable text, as indicated below. The values marked with an asterisk (*) are unlikely to occur in practice. However, a decoding is also provided for completeness sake.

  • ACCIDENT* => "flight accident site"

  • AERIAL_WORK* => "aerial work"

  • AEROBATICS => "aerobatics"

  • AIR_DROP => "air dropping"

  • AIR_GUN* => "firing in the air taking place"

  • 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"

  • FIREWORKS* => "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 => "unspecified hazard"

  • OTHER:GUN_FIRING =>”gun firing”

  • OTHER:HOT_AIR_BALLOON => "hot air balloon”

  • OTHER:MET_BALLOON => "met balloon”

  • OTHER:FREE_BALLOON => "free balloon”

  • OTHER:ROCKET_FIRING => “rocket firing”

  • OTHER:LGT_OUT_NVG => “Lights out night vision goggle training”

  • PARACHUTE => "PJE"

  • PARAGLIDER => "paragliding"

  • POPULATION* => "population protection"

  • RADIOSONDE* => "radiosonde launching"

  • REFINERY* => "refinery hazard"

  • REFUEL => "air refuelling"

  • SHOOTING => "firing"

  • SPACE_FLIGHT* => "space flight"

  • SPORT* => "sport flights"

  • 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"

(5)

If the TD.AirspaceActivation includes an AirspaceLayer that has:

  • upperLimit not equal to CEILING and different from any (if more than one present) BL.AirspaceGeometryComponent.upperLimit

  • or, lowerLimit not equal to FLOOR and different from any (if more than one present) BL.AirspaceGeometryComponent.lowerLimit

then the text "vertical limits changed during activation" or “vertical limits changed during activity”, as appropriate, shall be inserted here.

(6)

Annotations shall be translated into free text according to the common rules for annotations decoding.


...