...
| 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. |
| 'INACTIVE' | The airspace is not active. |
| 'INTERMITTENT' | The Airspace is active but with periods of no real usage. |
| 'OTHER' | Other. |
For the AIP data set the status should be coded with 'IN_USE' for ATS airspaces'.
For the AIP data set the status should be coded with 'ACTIVE for special activity airspaces'.
In case of "announced by NOTAM", the status shall be 'AVBL_FOR_ACTIVATION'.
In both the latter two cases a digital NOTAM issued, will override that status e.g. to 'ACTIVE' or 'IN_USE'.
...
| Identifier | Data Encoding Rule | Justification | Data Verification Rule (UID) | Remarks | |||||
|---|---|---|---|---|---|---|---|---|---|
ASE-501 | The AirspaceActivation.activity attribute is mandatory for special activity airspaces and other regulated airspaces. | Minimum data | TBD | PANS-AIM requires the class of airspace as part of the minimum AIP data set only for special activity airspaces other regulated airspaces, not for ATS airspaces. | ASE-501 | The AirspaceActivation.status attribute shall carry either the value 'ACTIVE' or 'AVBL_FOR_ACTIVATION'. | Digital NOTAM Event Specification | TBD | A digital NOTAM issued, will override that status. |
Coding Example
The figure below gives a simple example of an airspace activation for BERTRIX AREA.
...