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


The establishment of a new restricted, dangerous, prohibited, etc. area or navigation warning, which did not exist as a published (static data) airspace.


  • the term "special activity area" is used in order to encompass P, D, R and other areas of similar nature;

  • this scenario does not include the establishment of temporary ATS airspace (such as a temporary CTR or airspace with a specified class); see the dedicated scenario “Ad-hoc ATS airspace - creation [ATSA.NEW]”;

  • the creation of a permanent D or R area by NOTAM shall be an exceptional situation, as such events are expected to be managed as static data amendments. However, this is supported in this scenario as the same data requirements and rules apply and it helps ensuring that all the airspace created by NOTAM are made available digitally, not only the temporary ones;

  • this scenario does not cover the encoding of mobile airspace reservations, such as for aerial refuelling areas that move along a specified trajectory. See also the dedicated AR.NEW dealing with the establishment of ad-hoc area refuelling routes.

  • this scenario does not support the creation of airspace with conditional lower/upper limit, such as “6000 FT AMSL, but at least 1000 FT AGL”.

On this page

Event data

The following diagram identifies the information items that are usually provided by a data originator for this kind of event.


input = [type] [designator] [name] [activity] ["location note"] \n
"start time" "end time" [schedule] \n
"horizontal limits" {"excluded airspace"} "lower limit" "upper limit" \n
[note] {"affected aerodrome"} {"affected FIR"}.

The table below provides more details about each information item contained in the diagram. It also provided the mapping of each information item within the AIXM 5.1 structure. The name of the variable (first column) is recommended for use as label of the data field in human-machine interfaces (HMI).

Data item


AIXM mapping


The type of area, although this is not always explicit; it may be implicit, due to the kind of activity taking place. Typical examples are D (danger), R (restricted), P (prohibited), D-OTHER (other activity of dangerous nature).

Airspace.type with the list of values CodeAirspaceType. To be consistent with the scenario scope and purpose, only the following types shall be used: P, D, R, TSA, TRA, W, A, D-OTHER, PROTECT, OTHER


A designator allocated to the area. It is unlikely that such designators are provided by the data originator. It is more likely that the designator will be allocated by the publication office.



The name of a geographical feature or location, which is also used for identifying the area


The kind of activity that takes place in the area

Airspace/AirspaceActivation.activity with the limitations on the list of values CodeAirspaceActivityType defined further below.

start time

The effective date & time when the area becomes established and active. This might be further detailed in a "schedule".

Airspace/AirspaceTimeSlice.featureLifetime/beginPosition, Airspace/AirspaceTimeSlice/validTime/beginPosition, Event/EventTimeSlice.validTime/beginPosition and Event/EventTimeSlice.featureLifetime/beginPosition

end time

The end date & time when the area ceases to exist. It might be an estimated value, if the exact end of activation is unknown. It may also be indeterminate for a permanent area.

Airspace/AirspaceTimeSlice.featureLifetime/endPosition, Airspace/AirspaceTimeSlice/validTime/endPosition, Event/EventTimeSlice.validTime/endPosition and Event/EventTimeSlice.featureLifetime/endPosition also following the rules for Events with estimated end time, if applicable


A schedule might be provided in case the area is only active according to a regular timetable, within the overall period when it exists.

Airspace/AirspaceActivation/Timesheet/... according to the rules for Schedules

location note

A free text note that indicates the location of the area in relation with relevant geographical or aeronautical features, such as "North of SJAELLANDS", "10NM east Kirn VOR KIR", "Inside Donlon TMA", etc.

Airspace.annotation with propertyName='geometryComponent' and purpose='REMARK'

horizontal limit

The horizontal shape of the area or of one of its composing volumes (if the area is an aggregation of different volumes with different vertical limits).

Airspace/AirspaceVolume.horizontalProjection following the rules for encoding for encoding Geometrical and geographical data. Only geometries of type Polygon, Circle or Corridor are allowed in this scenario.

excluded airspace

A reference (type, designator, name) to one or more airspace that are excluded (subtracted) from the volume described by the aggregation of the horizontal limits specified for the area; for example: "Excluding the Heathrow CTR".


lower limit

The lower limit (value, unit of measurement and vertical reference) of the area.

Airspace/AirspaceVolume.lowerLimit and Airspace/AirspaceVolume.lowerLimitReference

upper limit

The upper limit (value, unit of measurement and vertical reference) of the area.

Airspace/AirspaceVolume.upperLimit and Airspace/AirspaceVolume.upperLimitReference


A free text note that provides information about the unit or service that controls the area or that can authorize the penetration of the area or indicating further instructions concerning the special activity area, such as about possible future changes to the area, detailed description of the reason that led to the area establishment, etc.

Airspace/AirspaceActivation.annotation with purpose='REMARK', according to the rules for encoding annotations

affected aerodromeA reference (name, designator) to one or more airports/heliports that for which the establishment of the area has an operational relevance and needs to be notified to the users thereof.Event.concernedAirportHeliport
affected FIR

A reference (type, designator) to one or more airspace of type FIR, for which the establishment of the area has an operational relevance and needs to be notified.

Note: this needs to be specified only if the geometry of the area is not physically intersecting the geometry of all the FIR(s) concerned. In that case, all FIR(s) concerned, including the ones physically intersected by the event geometry shall be coded for completeness sake.



  • It is recommended that data input applications allow the operator to visualise graphically the horizontal shape and the vertical extent of the special activity area. If a schedule is used, the graphical interface should also have a "time slider" that allows the operator to see when the area is actually active.

Assumptions for baseline data

It is assumed that no baseline data exists for this area.

Data encoding rules

The applicable AIP Data Set coding rules for Airspace shall be followed in order to ensure the harmonisation of the digital encodings provided by different sources. In addition, the following coding rules are specified for this particular scenario:


Data encoding rule


The special activity area shall be encoded as:

  • a new Event with a BASELINE TimeSlice (scenario='SAA.NEW', version='2.0'), for which a PERMDELTA TimeSlice may also be provided; and

  • a new Airspace BASELINE TimeSlice for which a PERMDELTA TimeSlice may also be provided; the property "event:theEvent" of the Airspace TimeSlices shall refer to the Event mentioned above.


The Airspace BASELINE shall contain one AirspaceActivation object with status='ACTIVE', 'IN_USE' or 'INTERMITTENT' (as appropriate) which shall also include the "activity" data and the values 'FLOOR', uom='OTHER' for lowerLimit and 'CEILING', uom='OTHER' for the upperLimit of the associated AirspaceLayer.


If the area activity is limited to a discrete schedule within the overall time period between the "start time" and the "end time", then this shall be encoded using as many as necessary timeInterval/Timesheet properties for the AirspaceActivation with status ACTIVE/IN_USE/INTERMITTENT of the BASELINE Timeslice. See also the rules for Event Schedules.


If a schedule is provided, then the Airspace BASELINE shall contain a second AirspaceActivation object with status='INACTIVE', which shall explicitly specify the times not covered by the activity schedule.

This could be done automatically by the system and should not be visible to the operator. 

It is recommended that the HMI of a data provider application allows to provide a schedule only in relation with active times, because only these will be translated into NOTAM text.


If one or more "exclude airspace" are specified, each shall be encoded as an AirspaceGeometryComponent with operation=SUBTR, operationSequence as dictated by the order of the element, contributorAirspace/AirspaceVolumeDependency.dependency=FULL_GEOMETRY and pointing to the airspace concerned. In addition, when the AIXM 5.1 encoded data is provided to a client, the data corresponding to the AirspaceVolume(s) of the contributorAirspace (lowerLimit, lowerLimitReference, upperLimit, upperLimitReference, horizontalProjection, etc.) shall be copied in the AirspaceVolume(s) of the current Airspace. This will provide a complete description of the current Airspace, eliminating the need to traverse the xlink:href in order to get the full geometrical information.


Following coded values should not be used for airspace activity encoding (as they are expected to be removed from AIXM):

  • AIR_DROP (use PARACHUTE instead)

  • ANTI_HAIL (use MISSILES instead)

  • BIRD_MIGRATION (use BIRD instead)

  • CROP_DUSTING (use AERIAL_WORK instead)


  • JET_CLIMBING (use EXERCISE instead)



  • OIL


  • RADIOSONDE (use BALLOON instead)

  • REFINERY (use CHEMICAL instead)

  • SHOOTING (use AIR_GUN or ARTILLERY instead)

  • TECHNICAL (use AERIAL_WORK instead)

  • ULM

  • VIP_PRES (use VIP instead)

  • VIP_VICE (use VIP instead)



The activity types that do not match a pre-defined value in the CodeAirspaceActivityType shall be encoded as follows:

  • captive balloon → activity=OTHER:CAPTIVE_BALLOON

  • kite → activity=OTHER:KITE

  • demolition using explosives → activity=OTHER:DEMOLITION

  • mass movement of aircraft → activity=OTHER:ACFT_MASS_MOVEMENT

  • formation flight → activity=OTHER:ACFT_FORMATION

  • significant volcanic activity → activity=OTHER:VOLCANO

  • model flying → activity=OTHER:MODEL

  • search and rescue → activity=OTHER: SAR

  • ascent of sky lanterns → activity=OTHER:SKY_LANTERN

All other hazards should be encoded as activity=OTHER or a relatively similar coded value (for example BALLOON for high balloon, etc.) plus a Note with purpose=DESCRIPTION and propertyName="the activity" which not covered by this specification.


If the type is not provided by the data originator, then the following encoding rules shall be applied in order to give a value to "type" attribute of the Airspace BASELINE TimeSlice:

  • if the notes encoded for the area indicate that the area is "prohibited", "compulsory bypass", "no fly zone" or equivalent for certain flights or aircraft, partially or totally, then the type "P" shall be allocated;

  • if the notes encoded for the area indicate that the area may be crossed following approval from a specified authority, then type "R" shall be allocated;


  • if the activity encoded is one of the following, then the type "PROTECT" shall be allocated: ACCIDENT, VIP.


It is recommended that an alphanumeric designator is allocated to a temporary area, in order to facilitate its identification on graphical representations (such as airspace activity maps) and verbal communication. The composition rule is derived from the rules for P, D, R area designators: CCLnnnn-yy, where:

  • CC is the Country Code; this could be expanded into a full FIR identifier if necessary to have a finer granularity of the airspace reference;

  • L is a letter that corresponds to the area type;

  • nnnn is a number, unduplicated during the same year, within the State or territory concerned;

  • yy are the last two digits of the year date when the area becomes effective.


Following coding examples can be found on GitHub (links attached):

  • No labels