...
| 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' when required for for ATS airspaces'.
For the AIP data set, the status should be coded with 'ACTIVE when required for special activity airspaces'.
In case of Unless, the activation of the airspace is "announced by NOTAM", than the status shall be 'AVBL_FOR_ACTIVATION'.
In the latter two cases a digital NOTAM issued, will override that status e.g. to 'ACTIVE' or 'IN_USE'.
See also coding rules of topic Schedules for Airspace.
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 .
...