Menu

AIP
Aeronautical Information Publication

Slovak Republic

CONSULT NOTAM AND AIP SUP FOR LATEST INFORMATION

LPS SR, š. p.


ENR 1.10  FLIGHT PLANNING

1.10.1  Submission of a flight plan

1.10.1.1 Information relative to an intended flight or portion of a flight, to be provided to air traffic services unit, shall be in the form of a flight plan.
1.10.1.1.1 A flight plan, except of repetitive flight plans, shall be submitted before departure to an air traffic services reporting office or, may be submitted during flight to the appropriate air traffic services unit.
1.10.1.1.2 Submission of a flight plan is used to mean variously, full information on all items comprised in the flight plan description, covering the whole route of a flight, or limited information required, inter alia, when the purpose is to obtain a clearance for a minor portion of a flight (e.g. landing at a controlled aerodrome or take-off from a controlled aerodrome, overflight of CTR/TMA).
1.10.1.1.3 A flight plan shall be submitted prior to operating:
  1. any flight or portion thereof to be provided with air traffic control service,

  2. any flight crossing the state boundary except VFR flight crossing the state boundary in airspace class G between:

    1. the Slovak Republic and the Czech Republic or the Slovak Republic and the Republic of Poland or

    2. the Slovak Republic and the Republic of Austria and the flight is carried out by glider,

  3. any flight planned to operate at night, if leaving the vicinity of an aerodrome, except for flights of helicopters of AIR-TRANSPORT EUROPE, spol. s r.o. and Air Department of the Ministry of Interior of the Slovak Republic.

Note: Vicinity of an aerodrome - an aircraft operating in the vicinity of an aerodrome includes but is not limited to aircraft entering or leaving an aerodrome traffic circuit.

1.10.1.1.3.1 When a flight plan for a flight in uncontrolled airspace is filed, procedures according to para. ENR 1.10.1.2 - ENR 1.10.1.4 shall be followed. Flights with filed flight plan in uncontrolled airspace shall follow procedures according to para. ENR 1.10.4 and ENR 1.10.5.
1.10.1.1.4 For each formation flight conducted fully or partly in controlled airspace a flight plan shall be submitted. For formation flight it is mandatory to list full information in all items of a flight plan form for the flight leader’s flight. When submitting flight plan, registration marks of other aircraft in formation shall be filled in item 18 FPL after abbreviation REG.
1.10.1.1.5 Limited information of a flight plan

Submission of a flight plan using limited information of a flight plan may be used only for VFR flights within CTR/TMA, except for formation flights and night flights. For VFR flight of helicopters of AIR-TRANSPORT EUROPE, spol. s r.o. and Air Department of the Ministry of Interior of the Slovak Republic this procedure of a flight plan submission may be used also at night.

Arriving flights and overflights:

  1. aircraft identification,

  2. aircraft type,

  3. wake turbulence category (if different than L),

  4. name of the operator,

  5. departure aerodrome or operating site,

  6. CTR/TMA entry point with estimated time,

  7. CTR/TMA exit point (when overflying) or destination aerodrome/operating site in CTR,

  8. requested flight track/area, level and character of activity with expected time in controlled airspace (as appropriate),

  9. number of persons on board.

Departing flights:

  1. aircraft identification,

  2. aircraft type,

  3. wake turbulence category (if different than L),

  4. name of the operator,

  5. destination aerodrome or operating site,

  6. CTR/TMA exit point,

  7. requested level, flight track/area and character of activity with expected time in controlled airspace (as appropriate),

  8. number of persons on board.

1.10.1.1.6 The levels at which a flight is to be conducted shall be specified in item 15 FPL:
  1. in terms of flight levels (F) when the flight is to be conducted at or above the transition level,

  2. in terms of altitudes (A) if the flight is to be conducted at or below the transition altitude,

  3. using letters “VFR” - may be used when a VFR flight is conducted within uncontrolled airspace. This means that the flight may not be conducted over the highest limit of uncontrolled airspace, except when an entry clearance is obtained to enter controlled airspace.

1.10.1.1.7 No IFR flights flight plans shall be filed via the airspace of BRATISLAVA FIR deviating from the State restrictions defined within the Route Availability Document (RAD). This common European reference document contains all airspace utilization rules and availability for BRATISLAVA FIR and any reference to them shall be made via https://www.nm.eurocontrol.int/RAD/index.html.
1.10.1.1.8 If an aircraft operator is not listed in ICAO Doc 8585 for the flight plan submitter it is requested to fill in designation/name, telephone and postal address in item 18 FPL under abbreviation OPR.
1.10.1.1.9 General aviation flight plan submitters are recommended to indicate pilot-in-command’s telephone number in item 18 FPL under abbreviation RMK.
1.10.1.1.10 In the flight plan filed for flights to/from abroad intended to be conducted out of controlled airspace, the pilot shall indicate in item 18 FPL an entry/exit significant point of crossing the FIR boundary with estimated elapsed flying time to the boundary from the place of departure. When entering the airspace of the Slovak Republic, the pilot shall adhere to the estimated time of crossing of the FIR boundary according to the flight plan, with an accuracy of +/- 10 minutes. If there are no designated significant points on FIR boundary VFR flights shall indicate entry/exit point by geographical place or the direction and distance from geographical place depicted on the Aeronautical Chart - ICAO 1 : 500 000.

Example: EET/LZBB0050 MALBE
EET/MALBE0050

Note: These points are specified for VFR flights: LVIV FIR - LASOT, MALBE, WIEN FIR - DEVIN, KITTSEE, REKLU.

1.10.1.2 Time of submission
1.10.1.2.1 Flight plan shall be submitted at least 60 minutes before departure (3 hours before departure if IFR flight is subject of ATFM measures) or if submitted during the flight, it shall be submitted at the time which will ensure its receipt by the appropriate ATS unit at least 10 minutes before the aircraft is estimated to reach the intended point of entry into controlled airspace.

Note: If an IFR flight plan is submitted during the flight, pilots are advised to submit flight plan at least 20 minutes before entering controlled airspace to ensure its early acceptance by appropriate ATS units. ATC unit is not authorized to issue flight clearance in case of absent flight plan.

1.10.1.2.2 Flight plan may be submitted 5 days (120 hours) before estimated off-block time (EOBT) at the earliest.
1.10.1.2.3 Flight plan submitted in form of limited information of a flight plan may be also filed in shorter time than stated in para. ENR 1.10.1.2.1. For departure the flight plan may be submitted before departure at the latest, for arrival 3 minutes before entering CTR/TMA at the latest. When using this procedure, pilot has to take into account that the flight clearance for entering controlled airspace may be delayed.

Note: Request for time of submission is not applicable in case of meteorological conditions deterioration or in emergency situations when there is not possible to comply with given timeframe, as well as in case of flights of helicopters of AIR-TRANSPORT EUROPE, spol. s r.o. and Air Department of the Ministry of Interior of the Slovak Republic.

1.10.1.3 Place of submission
1.10.1.3.1 A flight plan shall be submitted before departure to a Central Air Traffic Services Reporting Office Bratislava (CARO) or direct to the IFPS (IFR-GAT flights) or during the flight (AFIL) via RTF to appropriate ATS unit.

Note 1: Pre-flight information service at aerodromes, see para. GEN 3.1.5.

Note 2: Repetitive flight plan system is only applicable for IFR flights, see para. ENR 1.10.2.

1.10.1.3.2 When aircraft operators submit the flight plans for IFR-GAT flights directly to the IFPS and when they communicate independently themselves with IFPS and TACT systems in NMOC, then they are obliged to comply with the procedures introduced in EUROCONTROL document - Network Operations Handbook.
1.10.1.4 Method of the flight plan submission
1.10.1.4.1 Personal submission

In case of personal submission the flight plan form reception will be acknowledged to the submitter. When the flight plan for IFR-GAT flight is submitted the submitter must prearrange with CARO/manned ARO workstation the way of timely verification whether the flight plan is accepted by IFPS (for example leave the telephone or FAX number, e-mail), any ORM (ACK, MAN, REJ) or more precisely ETFMS/TACT messages received by appropriate CARO/ARO unit where the flight plan was submitted will be kept available.

1.10.1.4.2 Submission of the flight plan by phone

The flight plan submitted by phone shall be addressed to:

  1. CARO, TEL number: +421/2/48 57 22 80 or +421/2/43 42 21 02. In case of IFR-GAT flights it is mandatory to verify whether the flight plan is accepted by IFPS by submitter or

  2. APP/TWR units in case of flight plan submission in form of limited information of a flight plan if it is not possible to submit via RTF.

1.10.1.4.3 Submission of the flight plan using IBAF terminal

Flight plan may be submitted using self-service IBAF terminal (see para. GEN 3.1.5). In case of IFR-GAT flights is submitter mandatory to wait for verification whether the flight plan was accepted by IFPS (IBAF terminal send acceptation retroactively). Submitter is also able to verify it by telephone.

Note: For more information on IBAF terminal see AIC A 4/11.

1.10.1.4.4 Submission by FAX

Flight plan submitted by FAX to CARO (FAX number: +421/2/48 57 22 85 or +421/2/43 42 33 90) must be confirmed by telephone by submitter (TEL number: +421/2/48 57 22 80 or +421/2/43 42 21 02) immediately after submission. Flight plan not confirmed by telephone will not be processed for distribution by CARO personnel.

1.10.1.4.5 Submission of the flight plan by RTF

Flight plan submitted by RTF shall be submitted on appropriate ATS unit frequency. In case of IFR-GAT flight it is mandatory to verify by pilot in due time whether the flight plan is accepted by IFPS.

Note 1: To avoid ATS units frequency overload or in case of weak radio signal coverage it is recommended for pilots to use other methods of the flight plan submission according to para. ENR 1.10.1.4 particularly if they plan to enter controlled airspace.

Note 2: Submission of the flight plan by RTF is only recommended in exceptional circumstances (e.g. in case of meteorological conditions deterioration or in emergency situations), except submission of the flight plan submitted in form of limited information.

1.10.1.4.6 Any other method of submission of the flight plan must be subject of agreement between aircraft operator and ATS provider (Letové prevádzkové služby Slovenskej republiky, štátny podnik).
1.10.1.4.7 Irrespective of the method of the flight plan submission, the submitter for IFR-GAT flight is obliged to verify whether the relevant flight did not obtain a slot from NMOC.

1.10.2  Repetitive flight plan system

1.10.2.1 General

Repetitive flight plans shall be delivered to the address mentioned below so as to reach the address at least 14 days prior to the date of the first flight of the respective series. Permanent amendments of RPL (RLST) shall be sent to the address referred to in para. ENR 1.10.2.2 below, so that:

  1. there is a minimum of 7 working days between reception of the file by EUROCONTROL and activation of the first affected by the amendment and

  2. there must be two Mondays between reception of the file and activation of the first flight affected by the amendment.

Detailed procedure for RPL submission to the EUROCONTROL will be found in the IFPS User’s Manual, Network Operations Handbook.

1.10.2.2 Repetitive flight plans for flights within the airspace of the Slovak Republic shall be submitted to the following address:
Postal address:

EUROCONTROL - NMD
NMD - RPL Team
Rue de la Fusée, 96
B - 1130, BRUSSELS
Belgium

TEL:+32/2/745 19 56 (RPL Data Reception)

TEL:+32/2/745 19 57 (RPL Supervisor)

FAX:+32/2/729 90 42

e-mail:rpl@eurocontrol.int

1.10.2.3 All operators filling repetitive flight plans (RPLs) shall include in Item "Q" of the RPL all equipment and capability information in conformity with Item 10 of the ICAO flight plan form.
1.10.2.4 Operators of RVSM approved aircraft shall also include the letter "W" in Item "Q" of the RPL, regardless of the requested flight level. If a change of aircraft operated in accordance with a repetitive flight plan results in a modification of the RVSM approval status as stated In Item "Q", a modification message (CHG) shall be submitted by the operator.

1.10.3  Changes to the submitted flight plan

1.10.3.1 General
1.10.3.1.1 All changes to a flight plan submitted for an IFR flight or a VFR flight operated as a controlled flight, shall be reported as soon as practicable to the appropriate ATS unit. For uncontrolled VFR flight, significant changes to a flight plan shall be reported as soon as practicable to the appropriate ATS unit.

Note: Information submitted prior to departure regarding flight endurance, time estimates changes of more than 30 minutes or total number of persons carried on board, if incorrect at time of departure, constitutes a significant change to the flight plan and as such shall be reported.

1.10.3.1.2 A DLA message or a CHG message containing new EOBT shall be transmitted when the departure of an aircraft is delayed by more than 15 minutes in case of controlled flight or 60 minutes in case of uncontrolled flight, after the estimated off-block time contained in the basic flight plan data.

Note: If a delay in departure of a controlled flight is not properly reported, the relevant flight plan data may no longer be readily available to the appropriate ATS unit when a clearance is ultimately requested, which will consequently result in extra delay for the flight.

1.10.3.1.3 Whenever a flight, for which a flight plan has been submitted, is cancelled, the appropriate ATS unit shall be informed immediately.
1.10.3.2 Changes to the submitted flight plan - controlled flights

Except for inadvertent changes and meteorological conditions deterioration below the VMC, pilot-in-command shall adhere to the current flight plan or the applicable portion of a current flight plan submitted for a controlled flight unless a request for a change has been made and clearance obtained from the appropriate ATC unit or unless an emergency situation arises which necessitates immediate action by the aircraft, in which event as soon as circumstances permit, after such emergency authority is exercised, the appropriate ATS unit shall be notified of the action taken and that this action has been taken under emergency authority.

1.10.4  Flight plan activation/Reports of departure

1.10.4.1 Alerting service related to a flight plan is provided to flight for which the flight plan has been submitted and which has been planned to be executed from other than controlled aerodrome, only when the departure report is delivered to the proper ATS unit.

Immediately after departure the departure report shall be transferred by pilot-in-command to Bratislava FIC unit or to the nearest ATC unit via:

  1. RTF or

  2. telephone by a commissioned person.

1.10.4.2 Departure report shall contain the following data:
  1. aircraft identification,

  2. rules of flight,

  3. departure aerodrome or operating site,

  4. destination aerodrome or operating site,

  5. time of departure.

1.10.5  Closing a flight plan / Reports of arrival

Note: If pilot will not report an arrival, a state of emergency according to Chapter 5, ICAO Annex 11 will be declared.

1.10.5.1 An arrival report shall be made in person, by radiotelephony, via data link at the earliest possible moment after landing, to the appropriate ATS unit at the arrival aerodrome, by any flight for which a flight plan has been submitted covering the entire flight or the remaining portion of a flight to the destination aerodrome.
1.10.5.1.1 Submission of an arrival report is not required after landing on an aerodrome where ATS are provided on condition that radio communication or visual signals indicate that the landing has been observed.
1.10.5.2 When no ATS unit exists at the arrival aerodrome or operating site, the arrival report shall be made as soon as practicable after landing and by the quickest means available to the nearest ATS unit.
1.10.5.3 When communication facilities at the arrival aerodrome or operating site are known to be inadequate and alternate arrangements for the handling of arrival reports on the ground are not available, the following action shall be taken. Immediately prior to landing a pilot shall, if practicable, transmit to the appropriate ATS unit, a message comparable to an arrival report.
1.10.5.4 Arrival reports made by aircraft shall contain the following data:
  1. aircraft identification,

  2. arrival aerodrome or operating site,

  3. departure aerodrome or operating site,

  4. destination aerodrome or operating site (only in the case of an alternate aerodrome landing),

  5. time of arrival.

1.10.5.5 When a flight plan has been submitted only in respect of a portion of a flight, other than the remaining portion of a flight to destination, it shall, when required, be closed by an appropriate report to the relevant ATS unit. In case of VFR flights within the CTR/TMA according to para. ENR 1.10.1.1.5, the flight plan closes automatically when leaving the CTR/TMA.
1.10.5.6 Pilot-in-command may close a valid flight plan during the flight:
  1. in uncontrolled airspace,

  2. in controlled airspace immediately before entering uncontrolled airspace (in such case the flight plan will be valid until leaving controlled airspace).

Report of arrival is not required in such a case.

The recommended phrase to close the flight plan in flight:
“(call sign), CLOSING FLIGHT PLAN TO … (arrival aerodrome) AT … (time)”.

1.10.6  Procedure for identification of replacement flight plans

1.10.6.1 Application of procedure

The procedure is applicable to flights on routes subject to Air Traffic Flow Management, when it is decided during the pre-flight stage to re-route because there will be less delay on an alternative route to that in the previous flight plan.

To avoid excessive use of the procedure, the pre-flight stage is defined as Estimated Off Block Time (EOBT) minus 4 hours.

1.10.6.2 Description of procedure

When a repetitive flight plan (RPL) or an individual flight plan (FPL) has been filed and, in the pre-flight stage, an alternative routing is selected between the same aerodromes of departure and designation, the operator or pilot shall:

  1. originate a cancellation message (CNL), which shall immediately be transmitted with the priority ”DD” to all addresses concerned by the previous flight plan,

  2. file a replacement flight plan in the form of an FPL which shall be transmitted after the CNL with a slight delay (e.g. 5 minutes).

Note: It is recommended to wait until receipt of an ACK for the CNL message before sending the replacement FPL.

1.10.6.3 The replacement flight plan shall contain inter alia the original identification (call sign) without addition of a suffix ”Q” in item 7, the complete new route in item 15 and as the first element in item 18, the indication ”RFP/Qn”, whereas:
  1. ”RFP” signifies ”Replacement Flight Plan”,

  2. ”n” corresponds to the sequence number relating to the replacement flight plan for that particular flight.

Example:

  1. 1st replacement Flight Plan:”RFP/Q1”

  2. 2nd replacement Flight Plan:”RFP/Q2” etc.

In RTF communication the original flight identification must be used without a suffix ”Q”. The pilot may inform an ATC unit that the aircraft is operating on a replacement flight plan if any doubt exists regarding the route to be flown.

1.10.6.4 Overflight authorization

For operators having obtained scheduled overflight authorization for the airspace of the Slovak Republic by operating on RPL/FPL and which intend to overfly the airspace of the Slovak Republic also on their replacement flight plan, prepared in accordance with the procedure described in para. ENR 1.10.1, this overflight authorization remains also valid for the intended new routing.

Operators having not obtained scheduled overflight authorization for the airspace of the Slovak Republic and their flight according to their original RPL/FPL would not have entered the airspace of the Slovak Republic but intend to do so are required to file the flight plan.

Non-scheduled flights, which according to their original FPL would not have entered the airspace of the Slovak Republic but intend to do so, are required to file the flight plan.