ENR 1.10  Flight planning

1   SERA.4001 Submission of a flight plan

a. Information relative to an intended flight or portion of a flight, to be provided to air traffic services units, shall be in the form of a flight plan. The term ‘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 such as to cross an airway, to take off from, or to land at a controlled aerodrome.
b. 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 IFR flight within advisory airspace;
  3. any flight within or into areas, or along routes designated by the competent authority, to facilitate the provision of flight information, alerting and search and rescue services;
  4. any flight within or into areas or along routes designated by the competent authority, to facilitate coordination with appropriate military units or with air traffic services units in adjacent States in order to avoid the possible need for interception for the purpose of identification;
  5. any flight across international borders;
  6. any flight planned to operate at night, if leaving the vicinity of an aerodrome.
d. Unless for domestic VFR flights a flight plan for any flight planned to operate across international borders or to be provided with air traffic control service or air traffic advisory service shall be submitted at least 60 minutes* before departure, or, if submitted during flight, at a time which will ensure its receipt by the appropriate ATS unit at least 10 minutes before the aircraft is estimated to reach:
  1. the intended point of entry into a control area or advisory area; or
  2. the point of crossing an airway or advisory route.
*For domestic VFR flights a shorter period of time has been prescribed by the competent authority (CAA). (Official Gazette of the Republic of Slovenia, No. 14/2020, 6.3.2020, p427). A flight plan for any domestic VFR flight provided with air traffic control service shall be submitted at least 30 minutes before departure, or if submitted during flight, at the time, which ensures that the relevant ATS unit receives the flight plan for at least 10 minutes before the aircraft is expected to reach the points 1. and 2. of the paragraph c. mentioned above.
*From requirement SERA.4001(d) exemption for special operations in accordance with Commission Implementing Regulation (EU) No 923/2012 was granted as follows:
For VFR flights, a flight plan for flight planned to operate across international borders or to be provided with air traffic control service or air traffic advisory service shall be submitted at least 5 minutes before departure, or, if submitted during flight, at a time which will ensure its receipt by the appropriate ATS unit at least 5 minutes before the aircraft is estimated to reach:
  1. the intended point of entry into a control area or advisory area; or
  2. the point of crossing an airway or advisory route.
This exemption is used for the following activities of public interest and for the training necessary to carry out those activities safely:
a. police and customs missions,
b. environmental control missions conducted by, or on behalf of public authorities;
c. search and rescue,
d. medical flights and
g. fire fighting.
1.1   International flights within Schengen area
All international flights within Schengen area departing from public registered national airports, shall submit appropriate flight plan at least one hour before the flight to ARO SLOVENIA.
Phone:+386 4 2040 420
Fax:+386 4 2023 851
AFS:LJLJZPZX
Pilots are obliged to get appropriate briefing before the flight and submit all necessary information in regards to departure, arrival, delay, cancelation and/or change to FPL to above contacts.
1.2   Place of submission
1.2.1  IFR or IFR/VFR flight plan
Flight plan shall be submitted at Centralised Air Traffic Services Reporting Office (ARO SLOVENIA). Aircraft operators may file their IFR or IFR/VFR (mixed) flight plans and associated messages (e.g. CHG, DLA, CNL) directly with the IFPS using an own AFTN or SITA access point. If those means are not available, flight plan and associated messages may be communicated to the Centralised ATS Reporting Office (ARO SLOVENIA).
In case of IFR and IFR/VFR training flights without leaving the LJUBLJANA FIR, FPL shall not be submitted directly to IFPS but to ARO SLOVENIA only.
1.2.2  VFR flight plan
  1. Flight plans shall be submitted at the Centralised ATS Reporting Office (ARO SLOVENIA).
  2. For VFR flights between uncontrolled aerodromes crossing LJUBLJANA TMA/LJUBLJANA CTR, MARIBOR or PORTOROZ, a flight plan shall be submitted to the ARO SLOVENIA.
  3. For flights from an uncontrolled to a controlled aerodrome, a flight plan shall be submitted by telephone to the ARO SLOVENIA.
  4. A flight plan may be submitted by telefax and/or via eARO (http://fpl-sloveniacontrol.ead-it.com) to the ARO SLOVENIA under condition that the flight plan is forwarded on ICAO flight plan form and confirmation for the acceptance of the flight plan is received from ARO SLOVENIA.
  5. An alerting service is provided to VFR flights for which a flight plan has been received or when aircraft is otherwise known to the air traffic services. In the reference to SERA.4015 a delay message for VFR flights shall be submitted to the ARO if the off-block time is postponed by more than 30 MIN compared to the off-block time indicated in the flight plan.
1.3   Additional requirements about submitting flight plans
This notification applies to all pilots who plan their operations within FIR Ljubljana
  1. Special arrangements about submitting flight plans for all IFR flights (including Y and Z) within FIR Ljubljana with intermediate operations in CTRs
    This paragraph describes detailed information about submitting flight plan for IFR flights (including Y and Z), starting at any aerodrome with intermediate operations in CTRs within FIR Ljubljana.
    Example: Flight from aerodrome A with intermediate operations at aerodrome B and C with return to aerodrome A. Entire flight consists of intermediate operations at two controlled aerodromes therefore three separate flight plans must be submitted, e.g.:
    FPL 1;Departure aerodrome: A
    Destination aerodrome: B
    (Field 18 - RMK): 2ILS 1VOR APCH CONS FLT
    FPL 2;Departure aerodrome: B
    Destination aerodrome: C
    (Field 18 - RMK): 2TGL CONS FLT
    FPL 3;Departure aerodrome: C
    Destination aerodrome: A
    (Field 18 - RMK): IFR TRG 35MIN
    Each flight plan shall include complete flight route (Field 15) according to the flight rules.
    Field 18 (RMK) shall include remark ''CONS FLT'' (Continuous Flight) with number and type of operations at intermediate and final destination.
  2. Special arrangements for IFR and VFR flights (ICAO Notification of difference)
    Flight plans with flight routes crossing FIR Ljubljana boundary or volumes of controlled airspace shall include officially published entry/exit reporting points. Coordinates or any other names are not allowed; therefore, such flight plans will be rejected.

2   SERA.4005 Contents of a flight plan

  1. A flight plan shall comprise the following information that has been prescribed by the CAA (Official Gazette of the Republic of Slovenia, No. 56/2017, 13. 10. 2017, article 6):
    1. Aircraft identification
    2. Flight rules and type of flight
    3. Number and type(s) of aircraft and wake turbulence category
    4. Equipment
    5. Departure aerodrome or operating site
    6. Estimated off-block time
    7. Cruising speed(s)
    8. Cruising level(s)
    9. Route to be followed
    10. Destination aerodrome or operating site and total estimated elapsed time
    11. Alternate aerodrome(s) or operating site(s)
    12. Fuel endurance
    13. Total number of persons on board
    14. Emergency and survival equipment
    15. Other information.
  2. For flight plans submitted during flight, the departure aerodrome or operating site provided shall be the location from which supplementary information concerning the flight may be obtained, if required. Additionally, the information to be provided in lieu of the estimated off-block time shall be the time over the first point of the route to which the flight plan relates.
  3. An abbreviated flight plan submitted via radiotelephony shall comprise the following information (Official Gazette of the Republic of Slovenia, No. 14/2020, 6.3.2020, p427):
    1. Aircraft identification
    2. Type of aircraft
    3. Cruising level
    4. The intended point of entry into a control area
    5. The intended point of exit from a control area
    6. Radio communcation equipment capable of 8.33 kHz channel spacing
  4. An abbreviated flight plan may comprise additional information from article SERA.4005 (a).
    Flight plan forms are available at ARO SLOVENIA. The instructions for completing those forms shall be followed.
    DCT (direct indicator) routing is not available inside airspace of MARIBOR 1 TMA, MARIBOR 2 TMA and PORTOROZ TMA.
    Insertion of SID and STAR established in LJUBLJANA FIR is compulsory in the route field of the FPL.
2.1   Adherence to Airspace Utilization Rules and Availability
No flight plans shall be filed via the airspace of LJUBLJANA FIR deviating from the State restrictions defined within the Route Availability Document (RAD). This common European reference document contains all airspace utilisation rules and availability for LJUBLJANA FIR and any reference to them shall be made via https://www.nm.eurocontrol.int/RAD/index.html.
2.2   Repetitive flight plan system
RPL lists to flights in and overflights of LJUBLJANA FIR shall be provided to the EUROCONTROL NMD RPL Team by e-mail in accordance with IFPS Users Manual (Network Operations Handbook). Any RPL submission shall conform to the IFPS RPL format. For detailed information on RPL consult IFPS Users Manual, sections 4, 5 and 6.
Contact information:
Post:EUROCONTROL - NMD
NMD - RPL Team
Rue de la Fusée 96
B-1130 Brussels
BELGIUM
Phone:RPL Data Reception: +32 2 745 1956
RPL Supervisor: +32 2 745 1957
Fax:+32 2 729 90 42
Email:rpl@eurocontrol.int

3   SERA.4010 Completion of a flight plan

  1. A flight plan shall contain information, as applicable, on relevant items up to and including ‘Alternate aerodrome(s) or operating site(s)’ regarding the whole route or the portion thereof for which the flight plan is submitted.
  2. It shall, in addition, contain information, as applicable, on all other items when otherwise deemed necessary by the person submitting the flight plan.
Note: For the completion of a flight plan or abbreviated flight plan the codes as defined by the International Civil Aviation Organization in the Procedures for Air Navigation Services - Air Traffic Management (Doc 4444) shall be used. (Official Gazette of the Republic of Slovenia, No. 56/2017, 13. 10. 2017, article 8).

4   SERA.4015 Changes to a flight plan

  1. Subject to the provisions of SERA.8020 (b) 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 air traffic services unit. For other VFR flights, significant changes to a flight plan shall be reported as soon as practicable to the appropriate air traffic services unit.
  2. Information submitted prior to departure regarding fuel endurance 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.
4.1  In the event of a delay of 30 minutes or more for a flight for which a flight plan has been submitted, the flight plan shall be amended or a new flight plan shall be submitted after the old plan has been cancelled. Whenever a flight, for which a flight plan has been submitted, is cancelled, the appropriate ATS unit shall be informed immediately.
Note: If a delay in departure or cancellation of VFR flight, for which a flight plan has been submitted, is not properly reported, alerting or search and rescue action may be unnecessarily initiated when the flight fails to arrive at the destination aerodrome within 30 minutes after its current ETA (estimated time of arrival).
4.2  For flights subject to ATFM regulations any delay of 15 minutes or more shall be immediately reported to the appropriate ATS unit.

5   SERA.4020 Closing a flight plan

  1. An arrival report shall be made in person, by radiotelephony, via data link ‘’and by telephone’’; Official Gazette of the Republic of Slovenia, No. 56/2017, 13. 10. 2017, article 9) at the earliest possible moment after landing, to the appropriate air traffic services 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. Submission of an arrival report is not required after landing on an aerodrome where air traffic services are provided on condition that radio communication or visual signals indicate that the landing has been observed.
  2. 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 air traffic services unit.
  3. When no air traffic services unit exists at the arrival aerodrome or operating site, the arrival report, when required, shall be made as soon as practicable after landing and by the quickest means available to the nearest air traffic services unit.
  4. 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 the aircraft shall, if practicable, transmit to the appropriate air traffic services unit, a message comparable to an arrival report, where such a report is required. Normally, this transmission shall be made to the aeronautical station serving the air traffic services unit in charge of the flight information region in which the aircraft is operated.
  5. Arrival reports made by aircraft shall contain the following elements of information:
    1. aircraft identification;
    2. departure aerodrome or operating site;
    3. destination aerodrome or operating site (only in the case of a diversionary landing);
    4. arrival aerodrome or operating site;
    5. time of arrival.
If a report is not properly and timely done (reported), alerting or search and rescue action may be unnecessarily initiated and the cost of that not needed action shall be imposed to the pilot.

6   SERA.8020 Adherence to flight plan

  1. Except as provided for in (b) and (d) an aircraft 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 air traffic control 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 air traffic services unit shall be notified of the action taken and that this action has been taken under emergency authority.
    1. Unless otherwise authorized by the competent authority, or directed by the appropriate air traffic control unit, controlled flights shall, in so far as practicable:
      1. when on an established ATS route, operate along the defined center line of that route; or
      2. when on any other route, operate directly between the navigation facilities and/or points defining that route.
    2. Unless otherwise authorized by the competent authority, or directed by the appropriate air traffic control unit, an aircraft operating along an ATS route segment defined by reference to very high frequency omnidirectional radio ranges shall change over for its primary navigation guidance from the facility behind the aircraft to that ahead of it at, or as close as operationally feasible to, the changeover point, where established.
    3. Deviation from the requirements in (2) shall be notified to the appropriate air traffic services unit.
  2. Inadvertent changes. In the event that a controlled flight inadvertently deviates from its current flight plan, the following action shall be taken:
    1. Deviation from track: if the aircraft is off track, action shall be taken forthwith to adjust the heading of the aircraft to regain track as soon as practicable.
    2. Variation in true airspeed: if the average true airspeed at cruising level between reporting points varies or is expected to vary by plus or minus 5 per cent of the true airspeed, from that given in the flight plan, the appropriate air traffic services unit shall be so informed.
    3. Change in time estimate: if the time estimate for the next applicable reporting point, flight information region boundary or destination aerodrome, whichever comes first, is found to be in error in excess of 3 minutes from that notified to air traffic services, or such other period of time as is prescribed by the competent authority or on the basis of ICAO regional air navigation agreements, a revised estimated time shall be notified as soon as possible to the appropriate air traffic services unit.
    4. Additionally, when an ADS-C agreement is in place, the air traffic services unit shall be informed automatically via data link whenever changes occur beyond the threshold values stipulated by the ADS-C event contract.
  3. Intended changes. Requests for flight plan changes shall include information as indicated hereunder:
    1. Change of cruising level: aircraft identification; requested new cruising level and cruising speed at this level, revised time estimates (when applicable) at subsequent flight information region boundaries.
    2. Change of route:
      1. Destination unchanged: aircraft identification; flight rules; description of new route of flight including related flight plan data beginning with the position from which requested change of route is to commence; revised time estimates; any other pertinent information.
      2. Destination changed: aircraft identification; flight rules; description of revised route of flight to revised destination aerodrome including related flight plan data, beginning with the position from which requested change of route is to commence; revised time estimates; alternate aerodrome(s); any other pertinent information.
  4. Weather deterioration below the VMC. When it becomes evident that flight in VMC in accordance with its current flight plan will not be practicable, a VFR flight operated as a controlled flight shall:
    1. request an amended clearance enabling the aircraft to continue in VMC to destination or to an alternative aerodrome, or to leave the airspace within which an ATC clearance is required; or
    2. if no clearance in accordance with a) can be obtained, continue to operate in VMC and notify the appropriate ATC unit of the action being taken either to leave the airspace concerned or to land at the nearest suitable aerodrome; or
    3. if operated within a control zone, request authorization to operate as a special VFR flight; or
    4. request clearance to operate in accordance with the instrument flight rules.

7   EUR RVSM

The EUR RVSM flight planning requirements for the completion of the ICAO Flight Plan Form and the Repetitive Flight Plan are contained in the ICAO EUR Regional Supplementary Procedures (Doc 7030/5-EUR).
Furthermore, the following requirement is in addition to the flight planning requirements contained in the ICAO EUR Regional Supplementary Procedures (Doc 7030/5-EUR):
In addition to military operations, operators of customs or police aircraft shall insert the letter M in Item 8 of the ICAO Flight Plan Form.

8   Flight Planning Procedures within SECSI FRA

8.1   Flight Procedures
8.1.1   General
All traffic shall comply with:
  • the aircraft equipment requirements of the respective state;
  • General Rules and Procedures of the respective state;
  • Current RAD.
For exemptions for State aircraft see the corresponding AIP.
Within SECSI FRA, relevant significant points are considered as FRA Horizontal Entry (E), FRA Horizontal Exit (X), FRA Intermediate (I), FRA Arrival Connecting (A) and FRA Departure Connecting (D) Points, as described in ENR 4.1/ENR 4.4 subsections.
The Flight Level Orientation Scheme (FLOS) applicable within SECSI FRA corresponds to the semi-circular rules according ICAO Annex 2 Appendix 3 a) or Appendix 3 to Standardised European Rules of the Air (SERA) Table of cruising levels and ENR 1.7.
Exceptions to this rule are published in ENR 4.1/ENR4.4 column “Remarks”.
8.1.2   Eligible flights for SECSI FRA
Eligible flights are all flights that are intending to operate within the vertical and horizontal limits of SECSI FRA as specified in ENR 2.2 and ENR 6 of the corresponding AIPs, regardless of the phase of flight (overflights, arriving or departing from local aerodromes or from aerodromes situated in close proximity of SECSI FRA).
Non-RNAV equipped flights operating in SECSI FRA airspace within LJUBLJANA FIR below altitude 9500 ft AMSL.
8.2   Airspace restrictions and airspace reservations
8.2.1   Circumnavigating areas of airspace restrictions and airspace reservations
Flights may be planned through active Military Areas published in sections ENR 2.2, ENR 5.2 or AD 2 of the corresponding AIP unless otherwise stated in RAD, Appendix 7.
Flight planning is not permitted through active danger, restricted or prohibited areas published in section ENR 5.1 of the corresponding AIP, unless otherwise stated in RAD, Appendix 7.
Airspace Users shall plan their trajectory around airspaces that are not available for civil operations as published/managed by NOTAM/AUP/UUP by using FRA relevant points as published in ENR 4.1 / ENR 4.4.
8.2.2   Promulgation of route extension
In cases, where crossing of active reserved (restricted) areas is not possible, one of the following procedures applies:
  1. A flight will be instructed tactically by ATC to proceed via FRA Intermediate points (I) published in ENR 4.1 / ENR 4.4.
  2. Tactical radar vectoring by ATC.
The average extension to be considered by airspace users is approximately 5NM.
8.3   Flight Planning within SECSI FRA area
8.3.1   General
Within SECSI FRA, airspace users are allowed to plan user preferred trajectories using significant points or radio navigation aids (see ENR 4.1 and ENR 4.4), as well as geographical coordinates under special conditions and rules laid down in AIP and RAD.
Eligible flights shall flight plan via FRA relevant points according to the table below.
FromToRemark
FRA Horizontal Entry Point (E)FRA Horizontal Exit Point (X)Flight plan direct or via one or several intermediate points.
FRA Arrival Connecting Point (A)
FRA Intermediate Point (I)
FRA Departure Connecting Point (D)FRA Horizontal Exit Point (X)
FRA Arrival Connecting Point (A)
FRA Intermediate Point (I)
FRA Intermediate Point (I)FRA Horizontal Exit Point (X)
FRA Arrival Connecting Point (A)
FRA Intermediate Point (I)
In SECSI FRA there is no limitation on the number of FRA Intermediate Points (I) and DCT used in Field 15 of FPL.
Within SECSI FRA there is no limitation on the maximum DCT distance.
In case published FRA Intermediate Points (I) or DCT segments are compulsory due ATS operational reasons, specific rules for the correct usage are described in the respective RAD. This is valid for departing, arriving and overflying traffic.
Flights shall not be planned closer than 3 NM to the published SECSI FRA border.
To manage the operationally sensitive areas, No Planning Zones (NPZ) are published. A NPZ is a defined airspace volume within which the planning of FRA DCT trajectories is either not allowed or allowed only for exceptions as described. Airspace users can avoid these areas by planning via appropriate SECSI FRA Intermediate Points (I) around the NPZ or according to described conditions. Planning a DCT through the published NPZ will cause a reject message by IFPS except where the set conditions are met. For complete NPZ source information see RAD.
For Y/Z flights changes of flight rules (IFR joining or cancelling) shall be indicated by reference to any FRA relevant point as published in ENR 4.1 and ENR 4.4 respectively.
Airspace users may use any significant FRA point published in ENR 4.1/ENR 4.4, or unpublished point defined by geographical coordinates as described in item 8.3.4, for indicating changes of level and speed.
Usage of bearing and distance from a significant point or radio navigation aid as FRA Intermediate Point (I) is not allowed in SECSI FRA.
Route portions between unpublished points defined by geographical coordinates, as well as to/from significant points or radio navigation aids shall be indicated by means of “DCT” in accordance with ICAO Doc 4444 Appendix 2 “Flight Plan, Item 15”.
8.3.2   Cross Border Application
Inside SECSI FRA, the crossing of FIR borders as well as the crossing of the Area of Responsibility (AoR) boundary between the involved ATS units is basically allowed without the usage of FRA Intermediate Points (I) published along the boundaries, except otherwise specified in RAD.
Except for DCT segments defined in RAD Appendix 4, ATS Routes and SIDs/STARs:
  • entry to and exit from SECSI FRA shall be planned using the published FRA Horizontal Entry (E) and FRA Horizontal Exit (X) Points only;
  • the planning of DCT segments that are partially outside the lateral limits of SECSI FRA (re-entry segments) is only allowed by using FRA Horizontal Entry (E) and FRA Horizontal Exit (X) Points.
8.3.3   Determination of Lowest Available Level (LAL) within SECSI FRA
For determination of lowest available level within those parts of the SECSI FRA where Free Route operations are eligible from ground to FL 660 (i.e. AoR of ACC/APP Ljubljana and ACC/APP Wien and the local APP units of LOWL, LOWS, LOWI, LOWK and LOWG), see AIP Austria and AIP Slovenia, ENR 6.8. The published values correspond to the lowest available level within controlled airspace ensuring obstacle clearance.
When determining the LAL based upon ENR 6.8 the attainable navigational accuracy for the specific segment shall be taken into account, having due regard to the navigational facilities available on the ground and on board of the aircraft.
LAL calculation ensures that there is no obstacle inducing a higher LAL value within 3NM outside the respective LAL polygon.
The lower limits of DCT segments published in RAD Appendix 4 (En-route DCTs) without explicit levels (MEA - Minimum En-route Altitude) shall equal to the LAL as derived from AIP Austria ENR 6.8 and AIP Slovenia ENR 6.8.
Flight plan filing according SECSI FRA flight planning rules below these minima will cause a reject message by IFPS.
Instrument flights intending to operate outside controlled airspace shall state this request to the respective ATS unit. Nevertheless flight plan filing shall be in accordance with AIP Austria ENR 6.8 and AIP Slovenia ENR 6.8.
8.3.4   Use of geographical coordinates in Field 15
Unpublished points defined by geographical coordinates shall in general only be inserted along the direct trajectory between two FRA relevant points (E/X/I/A/D) to indicate changes of level and speed.
8.3.5   Overflying Traffic
Overflying traffic are all flights whose aerodromes of departure and destination are located outside SECSI FRA.
Overflying traffic may be planned directly from any FRA Horizontal Entry Point (E) to any FRA Horizontal Exit Point (X) and via published and unpublished FRA Intermediate Points (I) as specified in the AIP of the States involved in SECSI FRA and RAD.
Additional allowed vertical transitions to or from SECSI FRA for traffic departing or arriving from the aerodromes in the close proximity of SECSI FRA border are described in ENR 1.10 of AIP Croatia and AIP Serbia/Montenegro.
8.3.6   Access to FRA for Departing Traffic
Departing traffic are flights whose departure aerodrome is located inside the lateral limits of SECSI FRA.
Depending on the aerodrome there are different requirements on flight planning for departing traffic. FRA flight plan filing shall be started from:
  • a FRA Departure Connecting point (D) or
  • a specific FRA Intermediate Point (I) linked to an aerodrome according to the RAD or;
  • if no SID is available or there is no requirement for a connecting point, any FRA relevant point within a required distance from the aerodrome, according to RAD, can be used
8.3.7   Access to FRA for Arriving Traffic
Arriving traffic are flights whose aerodrome of destination is located inside the lateral limits of SECSI FRA.
Depending on the aerodrome there are different requirements on flight planning for arriving traffic. FRA flight plan filing shall be finished:
  • at a FRA Arrival Connecting Point (A) or;
  • at a specific FRA Intermediate Point (I) linked to an aerodrome according to the RAD or;
  • if no STAR is available or there is no requirement for a connecting point, at any FRA relevant Point within a required distance from the aerodrome, according to RAD, can be used.