| Panel | ||
|---|---|---|
| ||
|
Introduction
For special activity airspace, PANS-AIM requires as part of the minimum AIP data set to provide information about the type of restriction or nature of hazard. In case of an ADIZ (Air Defense Information Zone), the risk of interception in the event of penetration shall be indicated.
...
| Status | Description | |
|---|---|---|
| 'AVBL_FOR_ACTIVATION' | The feature may be activated. | |
| 'ACTIVE' | The airspace is active (but it might not be in use yet). | |
| 'IN_USE' | The airspace is actually used inside the activation period. | |
| Note | | |
| The airspace is not active. | |
| 'INTERMITTENT' | The Airspace is active but with periods of no real usage. | |
| 'OTHER' | Other. |
...
- as ACTIVE for the time and levels when the airspace is actually operating;
- as AVBL_FOR_ACTIVATION when the actual activation is "announced by NOTAM", which is a frequently encountered situation for certain D and R areas;
- as' INACTIVE' for the time and levels when the airspace is know to not be operating.
See also coding rules of topic Schedules for Airspace.
| Note | ||
|---|---|---|
| ||
The value 'IN_USE' should not be used for AIP Data Set, it is reserved for dynamic activation of Airspace processes (flexible use of airspace). |
Activity types
In addition to the list of activity types listed above, the following activities might occur in relation with certain danger areas. They should be encoded prefixed by OTHER:, as indicated below:
...
| Warning | ||
|---|---|---|
| ||
AIXM does not provide a sufficient list of values.Workaround Workaround AIXM 5.1(.1): Use 'OTHER'.Status Status AIXM 5.2: CCB issue AIXM-226 contains proposal to add more values (including the above ones) to the enumeration list for activity. |
| Info | ||
|---|---|---|
| ||
A change proposal (AIXM-401) for the next AIXM 5.2 version has been approved by the AIXM Change Control Board, adding additional values to the AIXM UML Model that use the up-to-date unmanned aviation terminology. The coding guidelines provided here are aligned with forward/backward conversion rules contained in the AIXM-401 Change Proposal. |
| Info | ||
|---|---|---|
| ||
A change proposal (AIXM-538) for the next AIXM 5.2 version has been approved by the AIXM Change Control Board, adding additional values for the types of AirspaceActivation.activity. The coding guidelines provided here are aligned with forward/backward conversion rules contained in the AIXM-538 Change Proposal. |
Vertical layer
The restriction may be limited within the airspace to a certain vertical portion of airspace by using the AirspaceLayer class. The vertical limits of the airspace concerned may be defined by a certain upper and lower limit of the AirspaceVolume, which by a digital NOTAM may be limited to the actual AirspaceLayer used, which may be just a portion of its whole vertical extent .
More details about airspace activation in regard to digital NOTAM can be found in the Digital NOTAM Event Specification
.
Schedules
For ATS airspace, Appendix 1 of PANS-AIM (Aeronautical Data Catalogue) defines the "Hours of applicability" for the airspace and in addition the "Hours of Service", which are "the operational hours of the station serving the unit".
However, in an AIP the first item is only published for ATS airspaces of section AD 2.17, whereas the latter is only published for ATS airspaces airspace listed in section ENR 2.1.
For special activity airspaces the "Time of activity" is defined as "Time interval when the special activity takes place".
In the following, only those coding rules specific to the airspace subjects will be discussed. For the For the general coding guidelines for Timesheet refer to topic Common coding patterns.
Hours of Applicability
For ATS airspaces published in "AD 2.17 Air traffic services airspace" PANS-AIM requires:
...
| Tip | ||
|---|---|---|
| ||
The example below shows that in AD 2.17 the hours of applicability are not published. in AD 2.18 however, the Hours of operation of the frequency the unit is providing the service for the airspace are published.
|
Hours of Service
This information is required for ATS airspaces airspace usually published in "ENR 2.1 FIR, UIR, TMA AND CTA":
...
In AIXM, this information will be provided via the Service.availability. The ServiceOperationalStatus class and its properties are used to code the detailed information, including the operationalStatus and the timeInterval.
An operational status has to be coded, in order to support the AIXM Digital NOTAM Event concept
.
...
| title | AIP Context |
|---|
The example below shows the Hours of service of the unit providing the service for the airspace.
...
', see ATS Unit providing Service.
Time of Activity
This information is required for special activity airspace usually published section in "ENR 5":
...
In AIXM, this information will be provided via the Airspace.activation property. The AirspaceActivation class and its properties are used to code the detailed information, including the status and the timeInterval. See also topic Restriction & Activation.
A status has to be coded, in order to support the AIXM Digital NOTAM Event concept .
| Tip | ||
|---|---|---|
| ||
The example below shows the Time of activity of a special activity airspace.
The example below shows the time Time of activity of a danger area with the note that it will be activated by NOTAM. This will be coded with corresponding Timesheet and the status 'AVBL_FOR_ACTIVATION'.
The next figure shows and example where the time of activity of a restricted area is defined by a schedule and additional hours of activity will be announced by NOTAM. In this case corresponding Timesheet will be coded and the status 'ACTIVE'. The additional activation by NOTAM will be coded as AirspaceActivation.annotation.
|
Coding Example
The figure below gives a simple example of an airspace activation for BERTRIX AREA.
...
| No. | Description | XPath Expression |
|---|---|---|
| ATC-EX-01 | AMSWELL Control providing service for AMSWELL FIR, Hours of of service: H24 | //aixm:AirspaceTimeSlice[@gml:id='ATC_AMSWELL_ACC'] |
| ASE-EX-03 | Special activity airspace, Prohibited Area, Circle, Time of activity: H24 | //aixm:AirspaceTimeSlice[@gml:id='ASE_VAARDNOR_P'] |
| ASE-EX-04 | Special activity airspace, Restricted Area, Arc segment (Arc by centrepoint) | //aixm:AirspaceTimeSlice[@gml:id='ASE_BRAVO_R'] |
| ASE-EX-05 | Special activity airspace, Restricted Area, Rectangle | //aixm:AirspaceTimeSlice[@gml:id='ASE_BURGENVALK_R'] |
| ASE-EX-06 | Special activity airspace, Restricted Area, reference to state boundary (annotation) | //aixm:AirspaceTimeSlice[@gml:id='ASE_WINSWUK_R'] |
| ASE-EX-07 | Special activity airspace, Local type, reference to state boundary (xlink:href), Time of activity: 1 OCT - 31 JUL | //aixm:AirspaceTimeSlice[@gml:id='ASE_EAMOA01_MOA'] |
| ASE-EX-08 | Special activity airspace, Danger Area, Time of activity: MON-FRI 0700-1700 (0600-1600) | //aixm:AirspaceTimeSlice[@gml:id='ASE_HORSHAM_D'] |
| ASE-EX-09 | Special activity airspace, Danger Area, within CTR | //aixm:AirspaceTimeSlice[@gml:id='ASE_DONLON_D'] |
| ASE-EX-19 | Aerial sporting activities airspace, Time of activity: 0600-SS SUN: 0900-1600 | //aixm:AirspaceTimeSlice[@gml:id='ASE_DONBURG_PARACHUTE_JUMPING_AERA'] |