Cyprus Airspace Management Cell - Airspace Use Plan

DESCRIPTION OF THE AIRSPACE USE PLAN

The AUP
The "Airspace Use Plan" (AUP) is the official medium for the daily notification by an AMC of the national airspace allocation for the following day. An AMC shall release only ONE AUP per day.

Preparation, Publication & Distribution of the AUP

The AUP shall be prepared by the AMC and distributed to the NM via CIAM.
During the pre-AUP coordination procedure, draft AUPs will be used and identified as “Draft AUP”. Draft AUPs will be available to each AMC. At any time, there will be only ONE stored AUP per day and per AMC in “Airspace Use Plan” or "Draft" form identified in the first line of the header as "Draft AUP" or "Airspace Use Plan" respectively. The “Airspace Use Plan” form will be decided by the AMC itself at D-1 1400 UTC at the very latest or if none, automatically by the NM system, unless the AMC informed the NM of a late release of the AUP.
The NM collects, consolidates the AUP and publishes the EAUP on the NOP portal and produces eAMI messages for the B2B service.

Description of the AUP
The elements included in the AUP are described below and summarised in table form in the next pages.

Header

- First Line: Identification of the Type of Message [e.g. Airspace Use Plan or Draft AUP]
- Second Line: Identification of the Sending Unit [e.g. AMC: EDDAZAMC - GERMANY -]
- Third Line: Definition of the Validity Period of the Message [e.g. 06/06/2008 06:00 - 07/06/2008 06:00] The validity period shall cover the 24 hours time period between 0600 UTC the next day to 0600 UTC the day after. This time period has to be considered for continuity purposes as a semiopen interval with the first limit included and the last one not.  Fourth Line: Date and Time of Transmission of the AUP [e.g. 05/06/2008 13:53] In addition to the type of message defined in the first line, the AUP is identified by the day and time of its transmission.

Lists ALPHA to ECHO

For each allocated airspace structure listed in the AUP in the following sequence, the different columns will contain:
- ALPHA List of Available CDRs2;
- BRAVO List of Temporary Closed Permanent ATS Routes and CDRs1;
- CHARLIE List of Active TRAs/TSAs and AMC-manageable R and D areas (AMA);
- DELTA List of Non AMC-manageable areas (NAM) for which changed use has been notified to AMC;
- ECHO List of RCAs, as appropriate.

First Column: Number [e.g. 1] Each airspace structure shall be listed with a sequence number and shall contain only one “Validity Period” and one “Flight Level Block” per number element. For each list ALPHA to ECHO, the sequence number shall start with [1] for the first item of the list in alphanumeric order. Upper and lower ATS routes having the same generic name shall be placed one above the other. In order to meet requirements of various readers of the AUP, the different lists ALPHA to ECHO can be divided by FIR/UIR, but in keeping their unique sequence number of the alphanumeric order to allow their identification in the UUP in case of cancellation or reallocation.
Second Column: Designator [e.g. UR 80 PERDU TBO or LF-D 31 CAZAUX or UF REIMS] Each airspace structure shall be identified as follows: For Lists ALPHA & BRAVO, with the AIP ENR 3-2 route designator followed by the two ICAO identifiers of the first and last points of the portion of the ATS route concerned; For Lists CHARLIE & DELTA, with the AIP ENR 5 designator followed, if needed, by the name of the airspace or portion thereof concerned; For List ECHO, with the LoA designator of the RCA concerned.
Third Column: Flight Level Block [e.g. F110 - F240 or F250 - UNL or GND or SFC - 900M AGL] Each airspace structure shall be described vertically as follows: For List ALPHA, with the upper and lower limits of the ATS route or portion thereof available inclusive of the IFR flight levels given; For List BRAVO, with the upper and lower limits of the ATS route or portion thereof closed inclusive of the IFR flight levels given; For Lists CHARLIE to ECHO, with the upper and lower limits of the affected airspace expressed either in flight levels, altitudes or heights inclusive of the figures given. Note: due to the technology used by NM system, the EAUP published on the NOP portal will use intermediate FL as described in 6.1.3
Fourth Column: Validity Period [e.g. 12:05 - 06:00] For each allocated airspace structure listed in ALPHA to ECHO, the “Validity Period” shall not exceed the 24 hours period of the AUP. The AUP shall repeat daily all data affecting more than one day. The “Validity Period” expressed with date/time groups indicating the start and the end of the period means variously: For List ALPHA, the “Period of Use”; For List BRAVO, the “Period of Closure”; For List CHARLIE, the “Period of Use”; For List DELTA, the “Period of Changed Use”; For List ECHO, the “Period of Use”. This time period has to be considered for continuity purposes as a semiopen interval with the first limit included and the last one not. Date will be referred to the day only and time will be expressed in hours and minutes.
Fifth/Sixth Columns: Responsible Unit and/or Remarks Field. For each allocated airspace structure listed in ALPHA to ECHO, the “Remarks Field” may be used to input any specific comments. For List ALPHA, when continuation of the ATS route has been coordinated with (a) neighbouring State(s) in (an) adjacent FIR/UIR(s), [ the following information shall be given "For continuation see AUP + country name + FIR/UIR designator"] or [the information on the consolidated CDR2 portion commonly accessible shall be given only once in the AUP of the designated Lead AMC]; For List BRAVO, when the ATS route closure information needs to be repeated in the EAUP for safety repetition, the word "NOTAM" shall be included without any reference; For Lists CHARLIE & DELTA, the unit responsible may be indicated for the concerned airspace during the time specified by the Validity Period; then the remarks field may be divided into two parts separated by a tab to indicate additional information such as the type of activity and the number and type of aircraft concerned.
Additional Information Finally, any additional information may be added in plain language at the end of the message.

No documents found