...
| Include Page | ||||
|---|---|---|---|---|
|
| Info | ||
|---|---|---|
| ||
| What in case more than one activity is applicable? Code OTHER with all activities? |
The status might carry the following values:
...
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'.
Unless, the actual activation of the time intervals coded in the Timesheet :
- 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.
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:
| activity | coded value |
|---|---|
| rocket launch | 'OTHER:ROCKET_FIRING' |
| gun firing | 'OTHER:GUN_FIRING' |
| hot air balloon | 'OTHER:HOT_AIR_BALLOON' |
| MET balloon | 'OTHER:MET_BALLOON' |
| free balloon | 'OTHER:FREE_BALLOON' |
| Lights out night vision Goggle training | 'OTHER:LGT_OUT_NVG' |
| Info | ||
|---|---|---|
| ||
| What in case more than one activity is applicable? Code OTHER with all activities? |
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 .
...