ENR 1.9  Air traffic flow management (ATFM) and airspace management

ENR 1.9.1.   Air traffic flow management

ENR 1.9.1.1   Air traffic flow and capacity management structure, area of responsibility, service provided, location of units and hours of operation
ENR 1.9.1.1.1   General (introduction)

Air Traffic Flow Management is a service established with the objective of contributing to a safe, orderly and expeditious flow of air traffic by ensuring ACC capacity is utilised to the maximum extent possible and the traffic volume is compatible with the capacities declared by the appropriate ATC authority. The Air Traffic Flow Management service is based on ICAO CTMO concept as a service complementary to Air Traffic control.

A Centralized Air Traffic Flow Management (ATFM) service is established within the ECAC (EUR) Region to optimize the use of air traffic system capacity. Capacity Management is described in the EC IR 255/2010 as one of the major parts of ATM. Various documents on this subject use two different abbreviations, ATFM and ATFCM, which in this context have the same meaning. Operational documents more often use ATFCM as capacities are directly managed at operational level, while strategic and most of NM documentation use ATFM.

The overall authority for the provision of Air Traffic Flow Management in Zagreb FIR is delegated to NM, and is conducted in close cooperation with Zagreb FMP, as part of a CDM process.

This CDM process is a key enabler of the ATFM strategy allowing the sharing of all relevant information between the parties involved in making decisions and supporting a permanent dialogue between the various partners throughout all phases of flight.

ENR 1.9.1.1.2   Structure and responsibilities

The structure of the Network Manager encompasses:

  1. the Flow Management Division (FMD), responsible for the planning co-ordination and implementation of ATFM measures within the FMD ATFM area
  2. the Flight Data Operations Division (FDOD), which is responsible for collecting, maintaining and providing data on all flight operations and the air navigation infrastructure. FDOD includes the Integrated Flight Planning System (IFPS), as well as the ENV database where all operational airspace and network entities are defined.

NM is responsible for:

  1. ensuring that traffic flows correspond to the stated capacities of the sectors through which they pass
  2. ensuring that, when necessary, ATFM measures are applied in an equitable manner and in such a way as to reduce as far as possible the penalties to Aircraft Operators
    Post:

    Eurocontrol/DNM
    Rue de la Fusée 96
    1130 Brussels
    Belgium

    Tel:+322 729 9011

    Fax:+322 729 9043

The provision of the ATFM service in Croatia is carried out in accordance with the national Regulations stated in the Rules of the Air and ATS and other relevant publications.

All flights subject to ATFM will be treated equally, except for the flights with special status, which are either excluded or entitled priority. The ATFM measures will only be imposed if the number of notified flights exceeds available ATC capacity. Whenever ATFM measures are in force they are published by FMD in form of an ANM (ATFM Notification Message), ANM Flash and AIM (ATFM Information Message), which are all available in Central ARO Split.

A description of the ATFM area and information on the Network Operations Systems can be found in the Network Operations Handbook.

ENR 1.9.1.1.3   Responsibilities of Zagreb FMP

Zagreb FMP is responsible for coordination with NMOC on optimal use of ATFM measures, and as liaison between ATC, Aircraft Operators and the NM. Zagreb FMP is located in Zagreb ACC and is operational H24

Zagreb FMP address is:

Zagreb FMP
Croatia Control, Croatian Air Navigation Services, Ltd.
Rudolfa Fizira 2
10410 Velika Gorica, P.O.B. 103, Croatia

Phone: +385 1 6259 260

Fax: +385 1 6259 242

AFTN/AFS: LDZOZDFM

Zagreb FMP is responsible for the day to day monitoring, planning and co-ordination of all ATFM measures affecting air traffic which is entering, leaving, overflying or remaining within Croatia. The FMP is responsible for all co-ordination between ATC and the FMD and for providing ATFM support to Aircraft Operators.

Central ARO Split is responsible for the exchange of information between NMOC and Aircraft Operators who do not have a direct connection with Network Manager.

Furthermore, Central ARO Split is tasked to provide support to Aircraft Operators in the ATFM message interpretation and the routine message dialogue with NM, if required.

Full addresses and contact details of Central ARO Split is provided in AIP Croatia, GEN 3.3.6 ATS units address list.

ENR 1.9.1.1.4   Responsibilities of ATS

ATC have the following responsibilities:

  1. ATC is responsible for departure slot monitoring at departure aerodromes. The exact procedures to be followed will depend on the way that ATS is organized at each aerodrome;
  2. ATC units responsible for departure slot monitoring shall be provided with the necessary information concerning the restrictions in force and slots allocated;
  3. ATC shall ensure that an ATFM slot, if applicable, is included as part of the ATC clearance;
  4. ATC shall take account of an applicable slot or flight suspension when a clearance is issued;
  5. ATC shall provide all possible assistance to Aircraft Operators to meet a CTOT or to co-ordinate a revised CTOT;
  6. ATC may deny start up clearance to flights unable to meet their slots until co-ordination with the FMP/FMD has been effected and a revised CTOT issued.

ATC is also responsible for monitoring flights compliance with departure slots (CTOTs) issued by the FMD as detailed in the ATFM Handbook. A slot window of -5 to +10 minutes is available for ATC to optimize the departure sequence.

In accordance with the provision of the Regional Supplementary Procedures, Europe (ICAO Doc 7030), flights which do not adhere to their slot shall be denied start-up clearance. However, ATC shall make all efforts to enable departing flights to comply with the slot. ATC shall liaise with Zagreb FMP to co-ordinate extensions to CTOTs, in line with the procedure described in the NM Handbook, part ATFCM Users Manual.

With the progressive introduction of the Enhanced Tactical Flight Management System (ETFMS) and Flight Activation Monitoring (FAM), flights that are not notified as being airborne within 15 minutes of the notified ETOT or CTOT will receive a Flight Suspension (FLS) message. If a flight is suspended during the taxiing phase, then ATC is responsible for sending a DLA message.

For flights having already received their SLOT and being in a ready situation, the AO may ask the local ATC to send a ready message (REA). The flight will be considered as having a new EOBT at the time the REA message is received by the NM and may receive improvements accordingly

ENR 1.9.1.1.5   Responsibilities of Aircraft operators

Aircraft Operators shall inform themselves of and adhere to:

  1. General ATFM procedures including flight plan filing and message exchange requirements;
  2. Strategic ATFM measures (including Route Availability Document (RAD);
  3. Current ATFM measures (including specific measures applicable on the day of operation, as promulgated by ANM or Flight Suspension (FLS) messages);
  4. Departure slots (CTOTs) issued by the FMD and procedures related to changes to CTOTs;
  5. the NM requirement for the modification or delay of EOBT. This is particularly important with the progressive implementation of Flight Activation Monitoring (FAM) whereby flights not notified as being airborne within 15 minutes of the notified ETOT or CTOT will receive a flight suspension message;
  6. the sole responsibility to obtain a new CTOT if there is no RTF contact with the TWR at CTOT;
  7. the correct procedure to be followed to obtain approval for the use of STS/ATFMX.

In order to comply with a CTOT, Aircraft Operators need to plan the departure of a flight so that the aircraft will be ready for start up in sufficient time to comply with a CTOT taking into account the taxi time shown in the Slot Allocation Message (SAM). A slot window is available to ATC to optimize the departure sequence.

Where a flight departs from an aerodrome with an ATSU, the Aircraft Operator or pilot shall obtain information, prior to start up from ATS as to whether a CTOT or FLS affects their flight.

Where a flight departs from an aerodrome without an ATSU it is the Aircraft Operator or pilot's responsibility to determine whether a CTOT or FLS affects their flight. In this case, the Aircraft Operator or pilot should contact the NM or the local FMP before the aircraft departs. For uncontrolled aerodromes within Croatia this information can also be obtained from Zagreb FIS on the address below:

Zagreb FIC
Phone: +385 1 6259503
FREQ: 135.050 MHZ
Callsign: Zagreb information

ENR 1.9.1.2   ATFM documentation

The general ATFM procedures, which apply throughout the ICAO European Region, are published in ICAO Doc 7030, Regional Supplementary Procedures (Europe) and EU regulation IR EU 2017/373 Annex IX.

Detailed NM procedures will be found in the NM Handbook obtainable at:

https://www.public.nm.eurocontrol.int/PUBPORTAL/gateway/spec/

or

Post:

Eurocontrol library
Rue de la Fusee, 96
B-1130 Brussels
BELGIUM
EUCHZMTA – TACT

ENR 1.9.1.3   ATFM processes
ENR 1.9.1.3.1   Rules for flight planning

The most important ATFM rules for flight planning, as defined in ICAO Doc 7030, are:

  1. For flights likely to be subject to ATFM measures Aircraft Operators shall submit Flight Plans to IFPS at least 3 hours before the EOBT;
  2. AOs filing flight plans for flights within the Network Management ATFM area or from within the ATFM adjacent area and entering the ATFM area shall assume their flight is subject to ATFM measures and subject to the requirement to submit a flight plan at least 3 hours before EOBT;
  3. AOs should be aware that late filing of a flight plan may lead to a disproportionate delay;
  4. Full details of flight planning requirements within the Network Management ATFM area are included in the Network Operations ATFM Users Manual;
  5. It is also important that the EOBT of a flight is as accurate as possible. It is a European requirement that all controlled flights departing, arriving or overflying Europe subject to a change in an EOBT of more than +15 or -15 minutes shall notify the change to the NM through the IFPS. Modification procedures to enable Aircraft Operators to meet this requirement are described below.

In all cases, it is in the best interest of Aircraft Operators to initiate prompt revisions or cancellations, thus permitting the system to maximize use of available capacity and minimize delay. The later the revision is made the greater the probability of a delay. The correct application of the STS/ATFMX procedure will ensure that approved flights are not unnecessarily delayed.

ENR 1.9.1.3.2   Slot allocation process

When no other option is available, a regulation will be applied by NM and departure times will be issued in the form of a Calculated Take Off Time (CTOT). This is facilitated by Computer Assisted Slot Allocation (CASA) algorithm within the Enhanced Tactical Flow Management Systems (ETFMS).

Pre-planned or strategic ATFM regulations are promulgated by the NM one day in advance by ATFM Notification Messages (ANM). All changes and tactical additions are promulgated by ANM revision messages.

For flights subject to a regulation, ETFMS will send a Slot Allocation Message (SAM) containing a CTOT 2 hours prior to the original at Estimated Off-Block Time (EOBT). This will be sent to the Central ARO Split as well as the Aircraft Operator via AFTN or SITA. Revisions to, or cancellations of, the last issued CTOT may be initiated by FMD, the Aircraft Operator, or the FMP/ATC unit on behalf of the AO. AOs requiring assistance should contact either the Central ARO Split, FMD Central Flow HELPDESK or the Zagreb FMP.

Full details of the Slot Allocation Process are published in the Network Operations Handbook.

ENR 1.9.1.3.3   Modification of Estimated Off Block Time (EOBT)

It is a requirement for both ATC and ATFM that the EOBT of a flight shall be an accurate EOBT. Any change to the EOBT of more than 15 minutes (+ or -) for any IFR flight within the NM Initial Flight Planning Zone (IFPZ) shall be communicated to IFPS.

An Aircraft Operator (AO) should not modify the EOBT to a later time simply as a result of an ATFM delay. When an AO submits an amendment message (eg DLA or CHG) to IFPS, they must always give as an EOBT the earliest EOBT they may comply with. This time is not directly related to the CTOT provided in the Slot Allocation Message (SAM) or Slot Revision Message (SRM). The EOBT should always reflect the time the AO wants to be off-blocks. The EOBT should always be changed if the original EOBT established by the AO cannot be met by the AO for reasons other than ATFM delay.

There are two categories of controlled flights covered by this procedure.

The procedure to be followed to modify the EOBT of a flight that has not received an ATFM CTOT is as follows:

  1. To amend the EOBT to a later time, a DLA or CHG message shall be sent to IFPS;
  2. To amend the EOBT to an earlier time, a CNL message must be sent to IFPS followed five minutes later by a new flight plan with new EOBT indicated.
    The replacement flight plan procedure shall not be used.

The procedure to be followed to modify the EOBT of a flight that has received an ATFM CTOT is as follows:

  1. If the EOBT established by the AO has changed or is no longer realistic for reasons other than ATFM then the following procedure shall be used:
    1. If a flight has a CTOT that cannot be met, then the AO shall send a DLA message to IFPS with the new EOBT of the flight. This may trigger a revised CTOT;
    2. If a flight has a CTOT with some delay and the AO is aware that the original EOBT cannot be met but the existing CTOT is acceptable, then a message shall be sent to IFPS with the new EOBT of the flight. However, in order not to trigger a new CTOT, the following formula must be used:
      Take the current CTOT minus the taxi-time, minus 10 minutes. The new EOBT must not be after this time.
      However, as Network Operations Systems are continuously seeking to give zero delay, the CTOT of the flight will never be earlier than the new EOBT plus the taxi-time.
  2. If a flight has had a CTOT and now receives a Slot Cancellation Message (SLC), but the original EOBT can no longer be met, then the AO shall communicate the new EOBT by use of a DLA message. ATC/ATFM will now have the 'true' EOBT of the flight.

Some states outside the Network Management ATFM area of responsibility still require AOs to update the EOBT, regardless of why the flight's original EOBT may have changed. AOs should bear in mind the formula explained above when doing this. Where it is known that ATC send Departure messages (DEP) for all flights, then this DEP message will suffice. It is not possible to amend (via CHG or DLA) the EOBT to an earlier time than the EOBT given in the flight plan. However, if a flight is ready to go off blocks earlier than the current EOBT the AOs may ask the local ATC Unit (TWR), or the FMP, to send a Ready (REA) message. In this case, the flight is considered as 'ready to depart' from the filing time of the REA message.

ENR 1.9.1.3.4   ATFCM measures

A number of ATFM measures are available for aligning Traffic Demand (TD) with available ATC capacity. These include Re-routing or Flight Level Capping of particular flights or flows, Cherry-picking particular flights to keep them out of a particular ATC sector, and ultimately ATFM regulation. Routing ‘scenarios’ may be applied by the NM to help resolve particular problems on particular days. These involve recommended or mandatory routes for particular groups of flights or selected individual flights. Re-routes for groups of flights will be published by the NM in an AIM (Air Traffic Flow and Capacity Management Information Message) or ANM (ATFM Notification Message).

Aircraft Operators (AOs) complying with a re-route or level capping requirement shall cancel any existing flight plan and re-file on the new route in accordance with the Replacement Flight Plan procedure published in the IFPS Users Manual.

ENR 1.9.1.4   ATFM messages exchange

CASA Subsystem concept is based on the principle of direct dialogue whenever possible among the TACT database, the AO, and the ATS. This dialogue uses a series of ATFM messages which allows that the ATFM slots may be notified, corrected, cancelled, etc., and also to deal with rerouteing.

This exchange is made by means of a new message format named ADEXP (ATS Data Xchange Protocol). The ADEXP format is based on a sequence of fields each of which is identified by a hyphen (-), followed by a code, a space and the appropriate data.

Each ATFM message comprises a number of fields, some of which are mandatory and some optional. The sequence of the fields in a message is not mandatory, except for the first field (corresponding to title of message) which determines the subsequent fields.

The AO may interchange ATFM messages, by means of:

  1. A remote computer terminal of NM.
  2. Through AFTN or SITA using ADEXP format and sent to the following addresses:
    AFTN: EUCHZMTA
    SITA: BRUEA7X
  3. If the above means are not available, AO must communicate with the Central ARO Split for handling of messages which affect them, or with the regional FMP or ATM Central Unit which will contact the NM. NM will send the ATFM messages to those addresses previously specified by AOs. In cases where AO has not been identified or the has found neither a centralised nor a local address for an AO, messages will be sent to the Central ARO Split, and if different, to the address of the flight plan originator. NM will also send ATFM messages to the TWR and Central ARO Split, to the appropriate ACC, to the FMP and/or to the ATM Central Unit.
ATFM messages transmitted by TACT/CASA to users
The ATFM messages trasmitted by TACT/CASA to users regarding ATFM slots, are the following:
SAMSlot Allocation Message.
SRMSlot Revision Message.
SLCSlot Cancellation Message.
SIPSlot Improvement Proposal Message.
FLSFlight Suspension Message.
DESDe-suspension Message.
RRPRerouteing Proposal Message.
ERRError Message.
RRNRerouteing Notification Message.
ATFM messages trasmitted by the users to TACT/CASA
Users may establish a direct dialogue with the TACT/CASA system in regard to the incidents to the allocated slot for its flight, by means of the following messages:
SPASlot Proposal Acceptance Message.
SRJSlot Proposal Rejection Message.
SMMSlot Missed Message.
SRMSlot Revision Message
FCMFlight Confirmation Message.
RJTRerouteing Rejection Message.
RFIReady for improvement.
SWMSIP wanted message.
ATFM messages sent by ATC units to NM
REAReady message.
Of course, there are many other message types that are exchanged between the ATC and NM systems, like:
FSAFirst System Activation
CPRCorrelated Position Report
AFPATC Flight Plan Proposal
and others, which are not directly linked to ATFM.

SAM: SLOT allocation message
The SAM is sent by TACT/CASA to inform AO/ATS of the Calculated Take-off Time (CTOT) computed by CASA for an individual flight, to which AOs and ATC must adhere. This message is sent to AOs/ATS 2 hours before the last received EOBT.

-TITLE SAM
-ARCID AMB101
-IFPLID AA12345678
-ADEP EGLL
-ADES LMML
-EOBT 0945
-CTOT 1030
-REGUL UZZU11
-TAXITIME 0020
-EOBD 080901
-REGCAUSE CE 81

The REGUL field indicates the name of the regulation affecting the flight.

A SAM message is sent by the NM when a problem occurs on the flight path requiring a modification of the take off time e.g. non-availability of aerodrome for a short period, or low visibility conditions. The flight is delayed to arrive when RVR requirement is met.

SRM: SLOT revision message
This message is sent automatically by TACT to AO/ATS to notify a significant change of CTOT previously allocated. This kind of message could be as a consequence of a CHG or DLA message or a modification of CASA parameters. It may also follow a SRR, SPA, FCM or REA message; also it is used to improve a flight with RFI status.

-TITLE SRM
-ARCID AMB101
-IFPLID AA12345678
-ADEP EGLL
-ADES LMML
-EOBD 080901
-EOBT 0020
-NEWCTOT 0050
-REGUL UZZU12
-TAXITIME 0020
-REGCAUSE CE 81

The field REGCAUSE is the reason for regulation code: the first letter corresponds to the reason assigned by the FMD, the second could be: D: departures, E: enroute or A: arrivals. The numeric code corresponds to the IATA Delay Code: See table of delay codes, Appendix 1.

SLC: SLOT requirement cancellation message
This message is sent by TACT to AO/ATS when a flight, which previously had a SAM, is no longer subject to any flow regulation, or when TACT receives a flight plan cancellation message (CNL).

-TITLE SLC
-ARCID AMB101
-IFPLID AA12345678
-ADEP EGLL
-ADES LMML
-EOBD 080901
-EOBT 0945
-REASON OUTREG
-TAXITIME 0020

SIP: SLOT improvement proposal message
This message is sent by TACT/CASA to AO to propose an improvement of the CTOT previously allocated. The AO accepts the proposal with an SPA message or refuses it with a SRJ message. The message SIP is void if no reply has been received at the time out parameter RESPBY.

-TITLE SIP
-ARCID AMB101
-IFPLID AA12345678
-ADEP EGLL
-ADES LMML
-EOBD 080901
-EOBT 0945
-CTOT 1030
-NEWCTOT 1010
-REGUL UZZU11
-RESPBY 0930
-TAXITIME 0020

FLS: Flight suspension message
When exceptional conditions and low visibility operations exist, NM could trigger the suspension of the flights which are to land at the aerodrome with those conditions and restrict the landing traffic to those able to land according to a specified RVR. The RVR may be provided by the AO in the FPL or CHG messages (item 18) or via an FCM message after the reception of the suspension message. If the RVR minimum doesn’t satisfy the minimum required or if the RVR minimum of the flight is not known, NM will send a flight suspension message FLS indicating the minimum RVR required. FLS is also sent to suspend flight plans subject to Flight Activation Monitoring (FAM):

-TITLE FLS
-ARCID AMB101
-IFPLID AA12345678
-ADEP EGLL
-ADES LMML
-EOBD 080901
-EOBT 0945
-REGUL LMMLA01
-COMMENT CLOSURE
-TAXITIME 0020
-REGCAUSE AA 83

After an AO receives a FLS message, he will send a flight confirmation message FCM to confirm the flight is taking place, which includes the RVR minima and a NEWEOBT. NM will send FLS messages in other cases, eg. after receiving a SMM, when a flight neds to be suspended due to special circumstances and in cases when FAM suspends the flight.

DES: De-suspension message
This message indicates that a flight which was previously suspended is now de-suspended. The flight is de-suspended by TACT and is no longer subject to ATFM measures. AO/ATS must send a DLA message in the event of a delay in excess of 15 minutes of the EOBT included in the FPL.

-TITLE DES
-ARCID AMB101
-IFPLID AA12345678
-ADEP EGLL
-ADES LMML
-EOBD 080901
-EOBT 0945
-TAXITIME 0020

RRP: Rerouteing proposal messages
This message is sent by TACT to an AO to offer a different CTOT or to avoid the need for a slot for a new route. A “respond by time” (RESPBY) is also added. TACT will send a RRP to an AO in the following cases:

  1. The flight had already received a CTOT corresponding to its original route (ORGRTE). A new CTOT is offered provided the flight is refilled along the proposed new route (NEWRTE).

    -TITLE RRP
    -ARCID AMB101
    -IFPLID AA12345678
    -ADEP EGLL
    -ADES LMML
    -EOBD 080901
    -EOBT 1030
    -ORGRTE MID UA1 RBT UG32 TOP UA1 ELB UA12 PAL UA18 EKOLA A18 MLQ
    -CTOT 1230
    -RRTEREF EGLLLMML1
    -NEWRTE MID UA1 RBT UG32 BAJKO UA21 NIZ UA2 AJO UA9 CAR UB21 PANTA B21 MLQ
    -NEWCTOT 1105
    -RESPBY 0900
    -TAXITIME 0020

    The AO who wishes to benefit from the offer shall consequently modify his flight plan (either with a CHG or using the procedure RFP). These messages should be received before the RESPBY time. At the reception of the new route in the flight plan TACT will merge it to the proposal. Then SLC, SAM or SRM messages will be transmitted to AO as appropriate.
  2. This flight is rerouted from a route which is crossing a regulated area(s) to a new route without a regulation. The REASON OUTREG indicates that there is no slot required, for that route.
  3. This flight has not yet received its slot, only aprovisional take-off (PTOT) time was calculated. A new provisional take-off (NEWPTOT) time is calculated which corresponds to the new proposed route. This value may be modified until the final slot is issued.
  4. Same as above. The flight has not yet received a slot and is proposed a route with no regulation active at the time of the proposal.

ERR: Error message
This message is sent by TACT when an error has been found in a message previously received and cannot be processed.

-TITLE ERR
-ARCID AMB101
-FILTIM 0915
-ORGMSG SMM
-REASON SYNTAX ERROR

RRN: Rerouteing notification message
The TACT/CASA sends this message to an AO to notify a new route previously triggered through a CHMI terminal. The RRN message is issued in case of an acceptance of the rerouting with option “CNL” of the function AOWIR (“What-if-reroute”) which allows an operator to display and select alternative routes via CHMI terminal. The operator is required to file a new flight plan with a route fully consistent with the one provided within the RRN message. TACT will send a RRN in the following cases:

  1. The flight had already received a CTOT corresponding to its original route (ORGRTE). A new CTOT is offered provided that the flight is refiled along the proposed new route (NEWRTE).

    -TITLE RRN
    -ARCID AMB101
    -IFPLID AA12345678
    -ADEP EGLL
    -ADES LMML
    -EOBD 080901
    -EOBT 1030
    -ORGRTE MID UA1 RBT UG32 TOP UA1 ELB UA12 PAL UA18 EKOLA A18 MLQ
    -CTOT 1230
    -RRTEREF EGLLLMML1
    -NEWRTE MID UA1 RBT UG32 BAJKO UA21 NIZ UA2 AJO UA9 CAR UB21 PANTA B21 MLQ
    -NEWCTOT 1105
    -RESPBY 0900
    -TAXITIME 0020
  2. This flight is rerouted from a route which is crossing a regulated area(s) to a new route without a regulation. The REASON OUTREG indicates that there is no slot required, for that route.

SPA: SLOT proposal acceptance message
This message is originated by an AO as a positive response to a SIP message. If the SPA message has been transmitted before the time established in RESPBY, TACT shall confirm the new CTOT with a SRM.

-TITLE SPA
-ARCID AMB101
-ADEP EGLL
-ADES LMML
-EOBT 0945
-NEWCTOT 1010

SRJ: SLOT proposal rejection message
This message is originated by an AO as a negative response to a Slot Improvement Proposal message (SIP). The AO keeps the original CTOT received before the SIP.

-TITLE SRJ
-ARCID AMB101
-ADEP EGLL
-ADES LMML
-EOBT 0945
-REJCTOT 1010

SMM: SLOT missed message
This message is originated by an AO when the CTOT allocated in the SAM cannot be achieved and the NEWEOBT is unknown. TACT will cancel the SAM, confirm suspension with a FLS message, and take no further action on the flight until a NEWEOBT is sent by the AO either via an SRR, CHG, DLA or a replacement flight plan (RFP).

-TITLE SMM
-ARCID AMB101
-ADEP EGLL
-ADES LMML
-EOBD 080901
-EOBT 0945
-CTOT 1020

SRM: SLOT revision message
After CASA has issued an initial SAM, subsequent updates may be notified via the Slot Revision Message (SRM). This message may be used to indicate a delay increase or decrease. The SRM notifies a significant change of slot. It is issued not earlier than 2 hours before the last received EOBT.

-TITLE SRM (1)
-ARCID AMB101
-IFPLID AA12345678
-ADEP EGLL
-ADES LMML
-EOBD 080901
-EOBT 0020
-NEWCTOT 0050
-REGUL UZZU12
-TAXITIME 0020
-REGCAUSE CE 81

An SRM message is sent by the NM when a problem occurs on the flight path requiring a modification of the take-off time e.g. non-availability of aerodrome.

An SRM message is sent by the NM when a problem occurs at or around aerodromes requiring modification of the take-off time e.g. low visibility conditions which affect ATC capacity. The flight is delayed to arrive when RVR requirement is met.

FCM: Flight confirmation message
An AO indicates to TACT that a flight previously suspended is now confirmed and can be reactivated at a time given in the message (EOBT or NEWEOBT). An AO may send also an FCM in response to an FLS message or a selective ANM.

-TITLE FCM
-ARCID AMB101
-ADEP EGLL
-ADES LMML
-EOBT 0945
-RVR 200

RJT: Rerouting Rejection Message
Used by an AO to reject an RRP message. The use of the RJT will enable the slot potentially associated with the RRP to be released back into the system for possible use elsewhere.

-TITLE RJT
-ARCID AMB101
-ADEP EGLL
-EOBT 0945
-ADES LMML
-RRTEREF EGLLLMML1

RFI: Ready for improvement
The flights can be set to a status called RFI (ready for improvement); when a flight has a such a status, it will receive improvements to its CTOT via an SRM. If the flight is not in such a status it may receive a SIP message. This procedure replaces the RDY message procedure. The AO can ask for the RFI status to NM for all the flights they operate or for each individual flight, in this case, by sending an RFI message.

-TITLE RFI
-ARCID AMB101
-ADEP EGLL
-ADES LMML
-EOBD 080901
-EOBT 1030

The AO operating a flight in RFI status will receive SRM if any improvement is possible. AO and ATC shall comply with the NEWCTOT.

SWM: SIP wanted message
When an airline set the status for RFI for all its flights, it can suppress the status of one particular flight by sending a SWM message to NM. The RFI status of the flight will be deactivated. The SWM message is used by the AO to indicate that it cannot accept SRM when an improvement is possible but wants to be in a position to refuse an improvement. The RFI status of the flight will be set to NO.

-TITLE SWM
-ARCID AMB101
-ADEP EGLL
-ADES LMML
-EOBD 080901
-EOBT 1030

From then on the flight may receive any possible improvement by a SIP message.

REA: Ready message
For flights having already received their slot and being in a situation to depart before their CTOT (doors closed and ready to depart), the AO may ask local ATC to send a Ready (REA) message. In the REA local ATC may also include a MINLINEUP time, to indicate the minimum time needed for that flight to get from its position to take-off. The REA message can only be sent by the ATC, although ATC may authorize to the ARO or FMP to send it. The REA message shall not be sent more than 15 minutes before the EOBT.

-TITLE REA
-ARCID ABC101
-ADEP EGLL
-ADES LMML
-EOBD 080901
-EOBT 1030
-MINLINEUP 0005

The MINLINEUP field is optional. If not present NM will use the local TAXITIME. NM will consider the filing time as a new EOBT and will try to improve the flight accordingly. If an improvement is possible AO and ATC will receive an SRM.

ENR 1.9.1.5   Enhanced Tactical Flow Management System (ETFMS) and Flight Activation Monitoring (FAM)

The development of the Enhanced Tactical Flow Management System (ETFMS), enables the NM to receive real-time data on departing flights using Flight Activation Monitoring (FAM). This data is provided by the ATC systems and is derived from ATC radar information and flight plan messaging.

There are advantages with improved knowledge of the traffic situation and this further assists ATFM tactical planning. FAM is being progressively introduced across the FMD ATFM area.

Flight Activation Monitoring:

  1. monitors flights which should have departed;
  2. takes action on these flights (through internal messaging to NM) to update the take-off time in order to improve the forecast of traffic demand;
  3. suspends flights after the designated time parameter (15 minutes after CTOT or ETOT), unless a message is received to confirm that the flight is airborne or delayed and;
  4. informs AOs and ATC at the departure aerodrome of any flight suspensions enabling these agencies to react accordingly.

The expected benefits of FAM are:

  1. to provide a better forecast of the actual and expected traffic situation;
  2. to release slots 'occupied' by flights that have not yet departed;
  3. to create an incentive for the AOs to update their flights promptly;
  4. to improve traffic load assessment; and
  5. to enable a more efficient use of the available and projected airspace capacity.

ETFMS expects flights to be airborne, based on the filed EOBT or the ATFM slot departure time. Those flights that are not notified as being airborne through ATC update messages within 15 minutes of the notified ETOT or CTOT time will receive a Flight Suspension (FLS) message from ETFMS and will remain suspended until signal action is taken. The comment ‘NOT REPORTED AS AIRBORNE’ will be identified in the text.

Unless an aircraft is taxiing it is the responsibility of the AO to send a DLA message (Central ARO Split). If a flight is suspended during the taxiing phase then ATC will be responsible for sending a DLA message.

A flight is considered to be active in ETFMS (TACT) following reception of any of the following messages:

DEP - Departure Message
FSA - Flight System Activation Message
CPR - Correlated Position Report
APL - ATC Flight Plan
ACH - ATC Flight Plan Change
APR - Aircraft Operator Position Report
ARR - Arrival Message

Flights that have been suspended by FAM, will receive a FLS message with the comment ‘Not reported as airborne’. An example of FLS message sent due to FAM

-TITLE FLS
-ARCID AMB101
-IFPLID AA12345678
-ADEP EGLL
-ADES LMML
-EOBD 080901
-EOBT 0945
-COMMENT NOT REPORTED AS AIRBORNE
-TAXITIME 0020

ENR 1.9.1.5.1   Flight Suspension – Procedures

When the AO and ATC at the aerodrome of departure receive an FLS due to the process, as described earlier, the following cases may occur:

  1. The flight is still effectively on the ground either on stand or already taxiing:
    1. The AO (aircraft on stand) or ATC (aircraft already taxiing) should ensure that the flight plan is re-initiated by sending a DLA message with a correct EOBT. ETFMS (TACT) will then respond with a De-Suspension Message (DES) or Slot Revision Message (SRM) depending whether the flight is non-regulated or regulated, respectively.
    2. ATC should not let the aircraft start-up/depart before such a message (DES or SRM) is received.

      Note: All effort shall be made by ATC to ensure that all flights, regulated or not, comply with their ETOT/CTOTs, taking into account the respective taxiing/holding/sequencing requirements. Any exception to permit aircraft to continue for departure, following taxi delays caused by airfield congestion, is not applicable unless the aircraft can depart and be airborne within the time frame ETOT/CTOT + 15 minutes.
  2. The flight is already flying:
    1. No action is needed from the AO or from the Tower of departure. The flight will automatically be de-suspended at the reception of one of the above messages (DEP, CPR, FSA etc).

      Note: The continuous re-occurrence of the above may mean a lack of proper information sent to NM. One possible solution would be a requirement to initiate DEP messages sent by the departure aerodrome but this will be determined by the NM through the national flow management office.
ENR 1.9.1.5.2   Area of Application

All users will be notified by NM/FMD by means of Air Traffic Flow and Capacity Management Information Message (AIM) whenever an area becomes FAM enabled. The effect of these areas being FAM-enabled means that all flights that are departing from or arriving at these areas will be affected by Flight Activation Monitoring. For flights departing from these areas and going to any other area, FAM will start at ETOT/CTOT.

For flights departing from non FAM-enabled and landing at aerodromes in FAM-enabled areas, the process will rely on the entry point of the first safely covered CPR-covered area. FLS may be sent to these flights landing inside, although departing outside.

ENR 1.9.1.6   Flights entitled to priority over other flights

It should be noted that the use of STS/ATFMX does not itself afford the flight any additional flight priority status for special handling by ATS. It is the other STS/indicators that indicate the need for special handling by ATS

A STS/STATE flight may be afforded appropriate ATS handling priority because of the importance of the mission, or the person on board the flight.

The combined use of STS/HOSP with STS/ATFMX will indicate to ATS that the flight is required to operate without delay and so justify exemption from ATFCM. Such flights may be afforded additional priority if the traffic situation allows.

Non-urgent flights will continue to use STS/HOSP indicating that special handling is required. Additional information may be included in item 18 of the FPL using RMK/ or the pilot may advise ATS exactly what special handling is required.

However, if any STS/HOSP flight experiences a medical emergency in flight, then the appropriate radiotelephony message(s) should be used to express the urgency of the condition to ATS.

It should be noted that the procedures detailed here are for Air Traffic Flow and Capacity Management purposes.

ENR 1.9.1.7   ATFM exemption procedures

Since the introduction of the NM it has been possible for Flight Plan (FPL) originators to obtain exemptions from ATFCM restrictions for certain flights through the use of STS/indicators in FPLs.

The following principles apply:

  1. The insertion of a STS/… indicator in Field 18 of a Flight Plan will identify that a flight may require special handling. This indicator is for use by all parties that may have to handle the flight;
  2. STS designators have a defined content to indicate particular conditions for that flight, some of which shall have an impact on any flow regulations that may apply to that flight;
  3. Multiple STS indicators in Item 18 are not allowed. Where multiple STS descriptors are necessary, STS descriptors shall be indicated in only one sub-field STS indicator separated by a space. Example: STS/HEAD MARSA;
  4. STS/ATFMX indicator can be used if the flight conforms to the criteria described below.

It should be noted that:
Only STS/FFR; STS/MEDEVAC; STS/SAR; STS/HEAD; and STS/ATFMX qualify for automatic exemption from ATFM measures;
The indicator STS/ATFMX is only used for ATFM purposes. It is subject to strict application of the rules of usage and is additional to any other special handling notification that may be required to be shown for ATC purposes.

These flights are automatically exempted from ATFM measures:
STS/FFR - Only those flights that are operated for Fire fighting reasons
STS/MEDEVAC - Only those flights that are engaged in Medical Evacuation missions
STS/SAR - Only those flights that are engaged in Search and Rescue missions
STS/HEAD - Only those flights that are with Head of State status
STS/ATFMX - Flights exempted from ATFM measures and flights with STATUS HUM and HOSP, although they do not require special handling but which are specifically authorized by the relevant national authority are exempted from any ATFM measures and may use the sub-field STS/ATFMX indicator.

These flights are not automatically exempted from ATFM measures:
The following specific STS indicators shall not have a direct influence on any exemption on flow measures, they simply provide information to the ATCO about the possibility of special requests arising during the flight.

STS/ALTRV - The sub-field STS/ALTRV may be used for those flights that are operated in accordance with an altitude reservation (QNE).
STS/FLTCK - The sub-field STS/FLTCK may be used for those flights that engaged in check for calibration of navaids.
STS/HAZMAT - The sub-field STS/HAZMAT may be used for those flights that are carried hazardous material.
STS/HOSP - The sub-field STS/HOSP may be used for those flights categorised as a medical flight specifically declared by the relevant medical authorities.
STS/HUM - Only those flights that are undertaken for humanitarian reasons .
STS/MARSA - The sub-field STS/MARSA may be used for those flights for which a military entity assumes responsibility for separation of military aircraft.
STS/NONRVSM - Only those State flights (military, police or customs) which do not indicate RVSM equipment in the message.
STS/STATE - Only those flights that are other than Head of State, and that are specifically required by the State Authorities, e.g. military or civil registered aircraft used in military, customs and police services.
EUR/PROTECTED shall be used only for military flights within Europe for which the details should only be available to a restricted audience (e.g. security sensitive flight).

Further information on the use of STS/indicators for ATFCM purposes may be found in the Network Operations Manual.

ENR 1.9.1.7.1   Rules of Application for the use of STS/ATFMX

The following Rules shall be applicable to all flights seeking to gain exemption from ATFM measures within the area of responsibility of the NM. It is intended to ensure priority for flights which by the nature of their mission cannot under any circumstances be delayed due to ATFCM.

It should be noted by all users that any flight which obtains exemption, and which may have otherwise been delayed, will have that delay passed on to other flights. It is essential, therefore, that use of the exemption facility shall be properly controlled and monitored so that genuine flight priorities may continue to operate without ATFCM delay.

Croatian Civil Aviation Agency reserves the right to request evidence to determine the justification for the use of ATFMX status by operators.

ENR 1.9.1.8   Provision of Information on Events Affecting Air Traffic Movements

Airport Operators at all Croatian airports (including military airfields) are to provide, at the earliest opportunity, but at least 14 days in advance, details of any event that may lead to a significant increase in traffic demand, eg.a large football match, international trade fair, European Ministerial meeting, etc.

The following information is required:

  1. name of airport;
  2. airport contact;
  3. ATC contact;
  4. nature of the event;
  5. the expected nature of increase in demand

Information about the event should be sent to:

HKZP d.o.o.
Airspace Management Department
Rudolfa Fizira 2
10410 Velika Gorica, P.O.B. 103
Croatia

Following the provision of the notice of an event, Zagreb FMP Manager will assess the impact and co-ordinate any necessary ATFCM response.

Appendix 1 

ENR 1.9.2.   Airspace management of the Republic of Croatia

ENR 1.9.2.1   Introduction

The Flexible Use of Airspace, as an airspace management concept described by the International Civil Aviation Organization (ICAO) and developed by the European Organization for the Safety of Air Navigation (EUROCONTROL), is carried out in the Republic of Croatia in compliance with the Air Traffic Act (Official Gazette of the Republic of Croatia, issue No. 69/2009, 84/2011, 54/2013, 127/2013 and 92/2014), Commission Regulation (EC) No. 2150/2005 of 23 December 2005 laying down common rules for the flexible use of airspace and the Ordinance on Airspace Management (Official Gazette, issue No. 20/2023).

ENR 1.9.2.2   Terms

Terms related to Airspace Management and the operation of Unmanned Aircraft Systems (UAS) are published in the Ordinance on Airspace Management (Official Gazette, issue No. 20/2023).

ENR 1.9.2.3   Organization of Airspace Management in the Republic of Croatia

Airspace Management (ASM) is performed in accordance with the legal framework referred to above and in accordance with the strategy of ECAC states and the FUA Concept.

ASM is applied on three levels:

  • Strategic ASM 1;
  • Pre-tactical ASM 2;
  • Tactical ASM 3.

Strategic Level - ASM 1

The National Airspace Management Committee represents the strategic ASM 1 level of ASM in the Republic of Croatia. This Committee is the national High-Level Airspace Policy Body (HLAPB) according to the Air Traffic Act (Official Gazette, issue No. 69/2009, 84/2011, 54/2013, 127/2013 and 92/2014) and Commission Regulation (EC) No. 2150/2005 of 23 December 2005 laying down common rules for the flexible use of airspace.

ASM 1 performs tasks in accordance with the EUROCONTROL ASM Handbook and Ordinance on Airspace Management (Official Gazette, issue No. 20/2023).

Contact:

Republic of Croatia
Ministry of the Sea, Transport and Infrastructure
Directorate for Air Traffic, Electronic Communications and Postal Services
National Airspace Management Committee
Mr. Dinko Staničić – Chairman of the Committee

Post:

Ministry of the Sea, Transport and Infrastructure
Prisavlje 14
HR-10000 Zagreb
Croatia

Tel:+385 1 6169156

Fax:+385 1 6196393

Pre-Tactical Level - ASM 2

ASM 2 tasks in the Republic of Croatia are performed by the Airspace Management Cell (AMC) Croatia in accordance with the Air Traffic Act (Official Gazette, issue No. 69/2009, 84/2011, 54/2013, 127/2013 and 92/2014), Commission Regulation (EC) No. 2150/2005 of 23 December 2005 laying down common rules for the flexible use of airspace and the Ordinance on Airspace Management (Official Gazette, issue No. 20/2023) and the EUROCONTROL ASM Handbook.

A joint civil and military AMC in the Republic of Croatia manages the airspace of the Republic of Croatia and airspace over the high seas within Zagreb FIR on a daily basis. Authorized approved agencies make requests for airspace allocations to the AMC, participate in the negotiation and coordination process initiated by the AMC, and utilize allocated flexible structures of airspace in accordance with the AMC airspace allocation.

For the use of airspace, all civil and military users shall contact the relevant approved agency.

Contact:

Airspace Management Cell (AMC) Croatia

AMC Military Part

Tel:+385 1 6259 660

AMC Civil Part

Tel:+385 1 6259 309

AFS:LDZOAMCX

Email:amc.ldzo@crocontrol.hr

URL:https://www.crocontrol.hr/, https://amc.crocontrol.hr/

Post:

Croatia Control Ltd.
Airspace Management Cell (AMC) Croatia
P.O.B. 103
Rudolfa Fizira 2
HR-10410 Velika Gorica
Croatia

Working hours: Monday -Friday 0700 UTC (0600 UTC) - 1900 UTC (1800 UTC), except for Croatian national holidays.

Civil Approved Agency

Croatia Control Ltd.
Air Traffic Management Sector (ATM Sector)
Operations Support Center (COP)
Civil Approved Agency (CIV AA)

Tel:+385 1 6259592, +385 1 6259568, +385 1 6259492

Fax:+385 1 6259552

Email:civaa@crocontrol.hr

URL:https://amc.crocontrol.hr/

Post:

Croatia Control Ltd.
Civil Approved Agency (CIV AA)
P.O.B. 103
Rudolfa Fizira 2
HR-10410 Velika Gorica
Croatia

Working hours: Monday -Friday 0630 UTC (0530 UTC) - 1430 UTC (1330 UTC), except for Croatian national holidays.

Military Approved Agency

Republic of Croatia
Ministry of Defense
Armed Forces of the Republic of Croatia
Croatian Air Force
Croatian Air Force Operations Center

Tel:+385 1 6228 337
+385 1 6228 338

Tactical Level - ASM 3

This level is performed by the competent ATC units and an appropriate military units in accordance with the Commission Regulation (EC) No. 2150/2005 of 23 December 2005 laying down common rules for the flexible use of airspace.

FIC ZAGREB is responsible unit for ASM Level 3 coordination (Activation, De-Activation, or Suspension of Reserved Airspace).
Contact:
Phone: +385 1 6259 333

ENR 1.9.2.4   Airspace Use Plan (AUP) and Updated Airspace Use Plan (UUP)

The allocation of Croatian airspace is published by the AMC Croatia in the daily Airspace Use Plan (AUP). This AUP will be published by the Centralized Airspace Data Function (CADF) on the EUROCONTROL Network Operations Portal (NOP) at https://www.public.nm.eurocontrol.int/PUBPORTAL/gateway/spec/ in the European AUP/UUP (EAUP/EUUP) section.

The validity period of the AUP is from 0600 UTC D until 0600 UTC D+1.

Since updates to the AUP are possible, up to 31 UUPs can be released and published in accordance with the UUP procedure laid down in the AMC/CADF Operations Manual.

AMC Croatia also publishes the national AUP/UUP (National Airspace Use Plan - NUP) on the dedicated AMC Portal website at https://amc.crocontrol.hr/.

The validity period of the national AUP is from 0600 UTC D until 0600 UTC D+1.

Since updates to the national AUP are possible, all national UUPs will be released and published in accordance with the national UUP procedure laid down in the AMC Croatia Operations Manual (see the AMC Portal website at https://amc.crocontrol.hr/).

ENR 1.9.2.5   Priority Rules for Airspace Reservations and Negotiation Procedures at Pre-tactical and Tactical Levels (ASM Level 2 and Level 3)
ENR 1.9.2.5.1   Introduction

The Flexible Use of Airspace is an airspace management concept described by the International Civil Aviation Organization (ICAO) and developed by the European Organization for the Safety of Air Navigation (Eurocontrol), based on the principle that airspace should not be designated as purely civil or military, but rather as a continuum in which all user requirements are accommodated to the greatest extent possible.

The described airspace availability principle should be based on the efficiency of its usage and clearly defined airspace allocation priority rules, having regard to defense, public, economic, commercial, and private users’ needs.

Airspace Management (ASM) at Levels 2 and 3 is conducted by clear rules, procedures, and standards, to ensure a high level of airspace availability and usage efficiency, as well as all users’ safety.

The Collaborative Decision Making (CDM) process at ASM Levels 2 and 3 aims to ensure efficient airspace usage based on the priority rules criteria, which are made at the strategic ASM level. At Levels 2 and 3, airspace users, Approved Agencies, the Airspace Management Cell (AMC), the Flow Management Position, and the competent Air Traffic Control participate in the CDM process, whereas the decision on airspace allocation is made by the AMC after completing the CDM process.

During the planning and allocation process, priority rules for the reservation of airspace are applied, and in the negotiation procedures, reducing the negative impact of airspace reservations on air traffic should be taken into account.

On the day of activity, during the ASM Level 3 procedures (activation, deactivation, reservation cancellation, and urgent activity discontinuation request), special emphasis is placed on the complexity of weather conditions and real operational conditions in air traffic and airspace, to keep all airspace users safe.

For activities demanding airspace reservation in special circumstances, due to the nature of their occurrence and need for quick airspace access, airspace has to be ensured as soon as possible for the activities to be conducted, applying measures for the safety of other airspace users.

These priority rules are used by the AMC (Level 2) and air traffic controllers (Level 3) to properly allocate previously reserved airspace as well as to set priorities in special circumstances (at Level 3).

ENR 1.9.2.5.2   Priority Rules for Planned Activities at ASM Levels 2 and 3

Having regard to the national interests of the Republic of Croatia and users’ needs, the following priority list is laid down for planned activities requiring the reservation of airspace:

  1. Control and protection of the state border of the Republic of Croatia and the Exclusive Economic Zone in the Adriatic Sea;
  2. Aerial surveillance in the domain of police and customs tasks;
  3. Protection of state authorities, critical infrastructure, and important persons;
  4. Securing the area struck by a natural or technological disaster and/or catastrophe;
  5. Celebrating state anniversaries, parades, and events organized by state administration bodies;
  6. International military exercises and international exercises of other state administration bodies;
  7. National military exercises and national exercises of other state administration bodies;
  8. International air shows;
  9. International aviation championships;
  10. National aviation championships;
  11. Military test flights;
  12. Public interest activities (e.g. aerial work) conducted at the request of a competent state administration body;
  13. Military and police training;
  14. Training at the request of other state bodies;
  15. Civil training flights;
  16. Commercial manned aircraft aerial work operations;
  17. Commercial unmanned aircraft aerial work operations;
  18. Sports and recreational activities of manned aircraft and parachute jumps;
  19. Sports and recreational activities of unmanned aircraft;
  20. Releasing and launching objects into the atmosphere (e.g. unmanned free balloons, children’s balloons, sky lanterns, fireworks, lighting effects...);
  21. Experimental activities for educational purposes.

If more users submit a request for the same portion of airspace for an activity to be conducted at the same time and of the same priority level, the requested airspace will be allocated to the user whose request was submitted first. Alternatively, two or more users can agree to work together in the same airspace at the same time if they clearly designate the user responsible for the allocated airspace.

In case of unforeseen events, the AMC can decide to discontinue activities in reserved airspace in the following situations:

  • Emergency flights;
  • Flights of Croatian military aircraft for the protection of sovereignty of the Republic of Croatia (STS/PROTECTED);
  • Search and rescue flights and humanitarian flights (STS/SAR/HUM);
  • Medical flights transporting sick or injured persons requiring emergency medical assistance, including the flights for the purpose of providing emergency medical assistance to sick or injured persons, as well as flights transporting transplants, blood, and medication, including the flights for boarding patients, medication, transplants or blood at the destination (STS/HOSP);
  • Flights for heads of states (STS/HEAD) and flights for prime ministers and other state officials with the established preferential status (STS/STATE);
  • Interception training flights of Croatian military aircraft;
  • Securing the area struck by a natural or technological disaster and/or catastrophe;
  • Urgent police and customs operations.

For this purpose, all airspace users reserving airspace structures shall submit to the Airspace Management Cell the contact details of the person responsible/head of activities who shall be available for the Airspace Management Cell via a means of communication (mobile or fixed line) for the whole duration of the activity.
Observation flights according to international agreements binding on the Republic of Croatia are prioritized pursuant to the agreement in force.

ENR 1.9.2.5.3   Priority Rules in Special Circumstances

The AMC must, by establishing an ad hoc structure, in the most suitable way for the given airspace situation, restrict or prohibit flights and activities in a specific volume of airspace for all except the approved users in the following cases:

  1. At the written request of competent state administration bodies, if necessary for the safety of air traffic and other airspace users’ activities, due to the defense needs of the Republic of Croatia, military and police operations, search and rescue operations, fire control, the protection of state institutions, critical infrastructure and important persons, the protection from the emissions of hazardous and/or harmful substances, gases and phenomena, the Croatian state border control and protection, and the celebration of state anniversaries, parades and events organized by state administration bodies,
  2. Due to real operational requirements for a period not longer than 48 hours, if necessary for the safety of air traffic and other airspace users’ activities, due to the defense needs of the Republic of Croatia, military and police operations, search and rescue operations, fire control, the protection of state institutions, critical infrastructure and important persons, the protection from the emissions of hazardous and/or harmful substances, gases and phenomena, the Croatian state border control and protection, and the celebration of state anniversaries, parades and events organized by state administration bodies.

At the request of the AMC, and for the purpose of informing all airspace users, the air navigation service provider shall publish all relevant information in the manner customary in air traffic.

The air navigation service provider shall, at the written request of competent state administration bodies or the Croatian Civil Aviation Agency, temporarily prohibit or restrict flights in a specific portion of airspace or at a specific aerodrome, by issuing a navigational warning, if necessary for defense or national security needs or the safety of (an) aircraft or in case of major natural disasters, according to the international agreements binding on the Republic of Croatia or immediately if necessary due to special circumstances, and publish it in the manner customary in air traffic.
Activities conducted in special circumstances are prioritized over all other airspace activities.

When establishing Ad-hoc structures in special circumstances, the AMC shall follow this priority list for allocating reserved airspace:

  1. Protection of sovereignty of the Republic of Croatia,
  2. Protection of state authorities, critical infrastructure, and important persons,
  3. Securing, inspecting, and controlling an area struck by a natural or technological disaster and/or catastrophe,
  4. Search and rescue at the request of a competent state administration body,
  5. Police and customs operations,
  6. Control of the state border and the Exclusive Economic Zone,
  7. Unforeseeable operations by a competent state administration body.
ENR 1.9.2.6   Operational and Equipment Requirements for the Reservation, Definition of Areas and Rules of Conduct in Areas Published in ENR 5.1 and ENR 5.2
  • Danger Area - D: An airspace structure of defined dimensions within which activities dangerous to the flight of aircraft may exist at specific times. In the context of the FUA concept, some D areas subject to management and allocation at Level 2 are established at Level 1 as “AMC-Manageable Areas” and identified as such in the AIP.
    • Danger Area AMC Manageable - D-AMA: A defined volume of airspace temporarily exempted from controlled airspace and inside which rules of the air for VFR flights in uncontrolled airspace are applied (G-class airspace).
      - The equipment requirements are the same as for the use of uncontrolled airspace (G-class airspace).
      - The operational requirement for airspace users is to register on the web AMC Portal (ENR 1.9.2.7.1) and follow the rules and procedures laid down in the Rules and Procedures published on the AMC Portal.
  • Temporary Reserved Area - TRA: A defined volume of airspace under the jurisdiction of a user authorized by the National Airspace Management Committee, which is temporarily reserved for a specific use by a specific authority or user, through which other traffic may be allowed to transit, with an ATC clearance.
    • The equipment requirements are two-way radio communication and a transponder.
    • The operational requirements for airspace users are to file a flight plan in accordance with valid regulations, to register on the web AMC Portal and to follow the rules and procedures laid down in the Rules and Procedures published on the AMC Portal.
  • Temporary Segregated Area - TSA: A defined volume of airspace under the jurisdiction of a user authorized by the National Airspace Management Committee, which is temporarily segregated for the exclusive use by a specific authority or user, through which other traffic will not be allowed to transit.
    • There are no equipment requirements.
    • The operational requirements for airspace users are to file a flight plan in accordance with valid regulations, to register on the web AMC Portal and follow the rules and procedures laid down in the Rules and Procedures for Reservations and Use of Airspace via AMC Portal System that are published on the AMC Portal.

Procedures for Operating Within the Areas

The procedures are laid down in the Rules and Procedures for Reservations and Use of Airspace via AMC Portal System that are published on the AMC Portal (ENR 1.9.2.7.1).

ENR 1.9.2.7   Tools for Managing Airspace of the Republic of Croatia and Informing Users
ENR 1.9.2.7.1   AMC Portal System

The AMC Portal System is a centralized Airspace Management (ASM) tool, serving as an ASM system for publishing information as a publicly available IT system through which the provider of ASM services publishes information to its users on the restrictions and prohibitions in airspace. To utilize all the functions of the AMC Portal System, users are required to register on the Portal’s website.
The details on airspace reservations will be available to registered users only.

ENR 1.9.2.7.2   Informing of Users

Airspace users are informed about restrictions and prohibitions in airspace via Aeronautical Information Products and via the AMC Portal System. The AMC Portal System displays the actual occupancy of airspace in real time as well as the approved Airspace Use Plan and its amendments for the following period (AUP - Airspace Use Plan / UUP - Updated Airspace Use Plan / NUP - National Airspace Use Plan). The reservation of permanent structures published in the AIP of the Republic of Croatia is published by the AUP, UUP and/or NUP messages via the AMC Portal. For Zagreb FIR, detailed national AUPs and UUPs (NUPs) are issued via the ASM system for publishing information (the AMC Portal System).
The AMC publishes information regarding the flight operations of Unmanned Aircraft Systems via the AMC Portal, which serves as a publicly available system with the function of providing the Common Information Service.

ENR 1.9.2.7.3   Automatized Procedure for Establishing Ad-hoc Structures

This procedure is conducted via the AMC Portal Mobile application in real time on the day of activity of UAS flight operations if those operations are conducted within the UAS Approved Geographical Zone (UAG).

ENR 1.9.2.8   UAS Operations

In the context of Airspace Management, abiding by the principles laid down by the Regulation 2150/2005, with the aim to integrate Unmanned Aircraft Systems (UAS) into airspace pursuant to the regulations of the European Union (EU), UAS Geographical Zones are defined pursuant to the Commission Implementing Regulation (EU) 2019/947 of 24 MAY 2019 on the rules and procedures for the operation of unmanned aircraft and the Ordinance on Airspace Management (Official Gazette, issue No. 20/2023).
UAS operations are conducted in airspace of defined dimensions that is temporarily reserved exclusively for UAS flights, which is named UAS Temporary Reserved Area (UTR). Other manned aircraft are prohibited from flying through UTR areas and as such, they should be avoided by pilots. ASM service providers can prohibit other UASs from entering UTR areas at all times.

ENR 1.9.2.8.1   UAS Geographical Zones

UAS Geographical Zones are zones determined by a competent body to facilitate, restrict or prohibit UAS operations, in order to take into account the risks related to safety, privacy, personal data protection, security or the environment that stem from those operations. To enable and facilitate the informing of airspace users on the status of UAS Geographical Zones, the following airspace structures are introduced:

  1. UAS Restricted Geographical Zone (URG): A part of airspace above a geographical zone determined by a competent body that is conditionally prohibited for UAS operations, but not for other aircraft and flight activities. UAS flight activities in this zone can be approved as an exception, in line with the laid down ASM procedures. In the context of the FUA concept, URG zones are established through the laid down ASM procedure, and, depending on the nature of the request, can be established temporarily or permanently at an appropriate ASM level.
  2. UAS Limited Geographical Zone (ULG): A part of airspace above a geographical zone determined by a competent body that is restricted for UAS operations, depending on the characteristics of the UAS, type of allowed operations and/or the procedure for the approval of flight operations itself. Within this zone, an approval for conducting flight operations can be granted in line with the laid down ASM procedures. In the context of the FUA concept, ULG zones are established through the laid down ASM procedure, and depending on the nature of the request, can be established temporarily or permanently at an appropriate ASM level.
  3. UAS Approved Geographical Zone (UAG): A part of airspace above a geographical zone determined by a competent body within which UAS operations can be conducted by the shortened procedure for the approval of flight operations. Within this zone, an approval for conducting UAS flight operations can be granted through the automatized procedure by a competent authority or service provider.

The following geographical zones are established in the control zone (CTR):

  1. URG Zone – Within airspace bounded by the distance of 1500 M from the security fence of controlled aerodromes and 500 M laterally along the approach surface axis to the distance of 3500 M from the runway threshold;
  2. ULG Zone – Within controlled airspace, higher than 50 M above ground or the surface of water outside of the URG zone;
  3. UAG Zone – Within controlled airspace, MAX up to 50 M from ground level or the surface of water outside of the URG zone.

The following geographical zones are established outside of the control zone (CTR) and within Croatian airspace:

  1. ULG Zone – Typically, higher than 120 M above ground level, and
  2. UAG Zone – From ground level or the surface of water up to 120 M.

To conduct UAS operations in the vicinity of uncontrolled aerodromes, at distances shorter than 1500 M from the edges and 500 M laterally along the approach surface axis up to the distance of 2500 M from the runway threshold, prior consent of the operator of the uncontrolled aerodrome has to be obtained.
By the method of their publication, UAS Geographical Zones can be permanent or temporary, and they are shown on the AMC Portal. Permanent geographical zones are published in the AIP, ENR 6 “En-route charts”.

ENR 1.9.2.8.2   Establishing U-space

U-space airspace is a geographical zone established for conducting UAS flight operations, in which operations are permitted only with the support of U-space services.
U-space airspace can be established for security, safety, privacy or ecological reasons, and to propose its establishment, an airspace risk assessment has to be made.