ENR 1.10  FLIGHT PLANNING

1  PROCEDURES FOR THE SUBMISSION OF FLIGHT PLAN

The EUR RVSM flight planning requirements for the completion of the ICAO FPL Form and flight plan submission requirements in addition to the flight planning requirements are contained in the ICAO EUR Regional Supplementary Procedures (Doc 7030).

In accordance with European Commission implementing Regulation No 923/2012 a FPL shall be submitted prior to:

  1. any flight or portion thereof to be provided with air traffic control service;
  2. any IFR flight within advisory airspace;
  3. for flight within uncontrolled air space in Vilnius FIR, in order to facilitate the provision of flight information, alerting and search and rescue services;
  4. for flight within or into prohibited and restricted areas and border area to facilitate coordination with appropriate military units or with ATS units in adjacent States in order to avoid the possible need for interception for the purpose of identification;
    Note:
    1. For flight within ATZ submission of FPL is not required.
    2. For flight within or into prohibited and restricted areas prior permission from Military Authority is required.
    3. Border area is part of the Republic of Lithuania’s uncontrolled airspace stretching out for 4 nautical miles into the territory from the Republic of Lithuania’s state border with a non-European Union state. When the internal border control is resumed, the border area is part of the Republic of Lithuania’s airspace stretching out for 4 nautical miles from the Republic of Lithuania’s state border into the territory.
    4. Recommendation for pilots: don’t plan and perform local flights in the Vilnius FIR controlled airspace, when turn points are navigation points on the border with Belarus and Russian Federation.
  5. any flight across international borders;
  6. any flight planned to operate at night, if leaving the vicinity of an aerodrome.
1.1 Time of submission

A FPL 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 as follows:

  • not more than 120 hours before EOBT;
  • at least 3 hours before EOBT for flights that may be subject to ATFM measures;
  • at least 60 minutes before departure for all other flights; 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 the intended point of entry into a control area.

For flights operated partially or entirely in accordance with IFR, entering the area of responsibility of ATS unit, for which no FPL has previously been received from the Network Manager (NM), the unit concerned shall transmit to the NM the aircraft identification, aircraft type, point of entry to its area of responsibility, time and flight level at that point, route and destination aerodrome of the flight.

1.2 Place of submission:
  1. IFR or IFR/VFR mixed FPLs and associated messages (e.g. CHG, DLA, CNL) before departure may be submitted directly to IFPS IFPS in accordance with addressing principles set in ENR 1.11.
    Direct filers take the full responsibility for compliance with all relevant IFPS procedures including complete addressing (e.g., within and outside the IFPS area, VFR part, Operational Air Traffic (OAT) part) of their messages.
  2. FPLs and associated messages (e.g. CHG, DLA, CNL) shall be submitted before departure to Vilnius ARO by email: [email protected].
    When submitting a FPL by phone the sequence of items in the FPL form shall be strictly followed.
    FPL can also be provided at selfbriefing offices located in Kaunas, Palanga, Šiauliai or Vilnius AD and on the web-site www.ans.lt. After submitting FPL it is necessary to make a call to the Vilnius ARO for confirmation that FPL has been received.
VILNIUS ARO
Tel.:+370 706 94 694
+370 706 94 618
+370 706 94 747
+370 706 94 747
  1. IFR flights are submitted to IFPS, VFR flights are submitted only to the addresses specified by the addressing rules.

No FPLs shall be filed via the airspace of Vilnius FIR/UIR deviating from the State restrictions defined within the Route Availability Document (RAD). This document contains all airspace utilization rules and availability for Vilnius FIR/UIR and any reference to them shall be made via:
https://www.nm.eurocontrol.int/RAD/index.html.

1.3 Filing of FPLs with IFPS directly

FPLs and FPL associated messages filed directly with IFPS will be checked by IFPS as regards syntax, format and route structure.

The originator will be informed of the processing of FPLs and FPL associated messages within IFPS through Operational Reply Messages (ORM).

MAN – the message is not correct and will be amended manually

REJ – the message is not correct and cannot be amended, a correct version has to be sent

ACK – the message is correct and accepted by IFPS

With respect to the 8.33 kHz channel spacing capable radio equipage requirements for IFR flights, the IFPS may send one of the following comments:

REJ message with the following comment: “This flight does not comply with 8.33 kHz radio equipment”

ACK message with the following comment: “Flight plan is not compliant with 8.33 kHz radio equipment; expect significant operational penalty”, if the flight is indicated as STS/SAR or STS/HOSP

1.4 Submission of FPLs during flight (AFIL)

AFIL is submitted during flight to obtain ATC clearance to enter controlled air space, if required by certain circumstances unknown to the pilot prior to departure.

AFIL shall be submitted to the ATS unit of flight responsibility area.

For FPLs 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 instead of the EOBT shall be the time over the first point of the route to which the FPL relates.

1.5 Contents and form of a FPL

The formats and requirements for completing the FPL Form, defined by European Commission implementing Regulation No 923/2012 Appendix 6 and ICAO Doc 4444 shall be strictly adhered to. ICAO FPL form is available at Vilnius ARO and for download or filling in a form online on the web-site:
www.ans.lt/en/flight-plan-1.

1.6 Authorization for special flights

Flights of a specific character such as survey flights, scientific research flights etc. may be exempted from the specific restrictions that are connected with airspace users limitations.

Request for exemption shall be send so as to be received at least one week before the intended day of operation by email: [email protected].

When planning to perform a technical test flight, flight information for prior coordination with Vilnius FMP must be sent by email [email protected] 48 hours before departure, it is necessary to provide the following information: aircraft type, registration mark, planned flight date and time, duration, route, altitude (altitude range), flight purpose, nature of technical tests to be performed, any other relevant information.

1.7 Closing a FPL
  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 FPL has been submitted covering the entire flight or the remaining portion of a flight to the destination aerodrome.

    Submission of an arrival report is not required after landing on an aerodrome where ATS are provided except if it was required by ATS unit.

  2. When FPL 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.
  3. 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:
VILNIUS ARO
Tel.:+370 706 94 694
+370 706 94 618
+370 706 94 747
+370 706 94 747

Note. If there is no message about the closing of the flight plan after expiry of 30 minutes, the search and rescue operation will be started.

  1. 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 ATS unit, a message comparable to an arrival report. Normally, this transmission shall be made to the aeronautical station serving the ATS unit in charge of the FIR in which the aircraft is operated.
  2. Arrival reports shall contain the following items of information:
    • aircraft identification;
    • departure aerodrome or operating site;
    • destination aerodrome or operating site (only in the case of a diversionary landing);
    • arrival aerodrome or operating site;
    • time of arrival.
1.8 Non-standard Planning Zones (NPZ)

Non-standard planning zones are published within the airspace of Baltic FRA. NPZ is a defined airspace volume within which the planning of FRA DCT trajectories is either not allowed or allowed only for exceptions if described. Airspace users can avoid these areas by planning via appropriate significant points around the NPZ. Flight planning through the relevant NPZ will cause a reject message by IFPS except where the set conditions are met. For complete NPZ source information see RAD.

1.9 Flight Plan Buffer Zones (FBZ) for restricted and danger areas and military exercise and training areas

Flight Plan Buffer Zones (FBZ) are established around AMC Manageable R, D and TSA areas for flight planning purposes. The lateral and vertical limits of zones are published in ENR 5.1 (Restricted and Danger areas) and ENR 5.2 (Temporary Segregated Areas). Activated FBZ shall be taken into account when filing an IFR flight plan having DCT routings. FBZ is activated by AUP/UUP message. NM IFPS system will not accept flight plans where great circle route (DCT) between two positions enters active FBZ area within FBZ vertical limits. Flight plans can be filed up to the boundary of the active FBZ.

2  REPETITIVE FLIGHT PLAN SYSTEM

NIL.

3  CHANGES OF THE SUBMITTED FPL

All changes to a FPL submitted for an IFR flight, or a VFR flight operated as a controlled flight, shall be reported:

  • during the pre-flight phase, to NM for flights intended to operate in accordance with IFR for a portion of or the entire route, and to Vilnius ARO as soon as practicable;
  • during the flight - to the appropriate ATS unit.

For other VFR flights, significant changes to a FPL shall be reported as soon as practicable to the appropriate ATS unit.

In the event of a delay of 30 minutes in excess of EOBT for a controlled flight or a delay of 1 hour for an uncontrolled flight for which a FPL has been submitted, the FPL shall be amended, or a new FPL submitted, and the old FPL canceled, whichever is applicable. For any flight operated in accordance with IFR, delays of more than 15 minutes shall be communicated to NM.

In the case of a change in the aircraft equipment and its capability status for a flight, aircraft operators, or the agents that act on their behalf, shall send a modification message to NM or Vilnius ARO with the appropriate indicator inserted in the relevant item of the FPL form.

Information submitted prior to departure regarding fuel endurance or total number of persons carried on board, if incorrect at the time of departure, constitutes a significant change to the FPL and as such must be reported.

If a delay in departure (or cancellation) of an uncontrolled VFR flight 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.

Whenever submitted flight FPL is canceled, the appropriate ATS unit shall be informed immediately.

4  FF-ICE (Flight & Flow Information for a Collaborative Environment)

4.1 Definitions

1. FF-ICE: Information necessary for planning, coordination, and notification of flights, exchanged in a standardized format between members of the ATM community, including those involved in flight operations and aerodrome operations.

2. FF-ICE services: A set of services established for the purposes of facilitating the exchange of FF-ICE, accurate assessment of demands, appropriate resource planning, and optimizing flight planning and execution.

3. FF-ICE services unit: A unit designated by the appropriate ATS authority for the provision of FF-ICE services.

4. Filed flight plan (FPL or eFPL): The latest flight plan as submitted by the pilot, an operator or a designated representative for use by ATS units.

5. Globally unique flight identifier (GUFI): An unchangeable data element associated with a flight that allows all eligible members of the ATM community to unambiguously refer to information pertaining to the flight.

4.2 FF-ICE Services

1. FF-ICE operates within a system-wide information management (SWIM) operational environment in which the main procedures and processes are described in terms of services.

2. EUROCONTROL Network Manager (NM) is the designated FF-ICE services unit for the IFPS zone and provides the following FF-ICE services:

  1. Filing service: the evaluation of a filed flight plan (eFPL) for the provision of air traffic services and indication of flight plan acceptability;
  2. Trial service: the evaluation of a trial request with respect to flight plan acceptability and, where practicable, the indication of applicable restrictions and resultant constraints on the flight;
    Note: The trial service offers an opportunity for an operator or designated representative to submit “what-if” scenarios and to receive feedback from an FF-ICE services unit, prior to submitting an eFPL or flight plan update.
  3. Flight data request service: the provision of data regarding a specific flight such as the latest version of a filed flight plan or search and rescue data upon request by an eligible recipient;
  4. Notification service: the provision of data regarding a certain flight event such as departure and arrival to required recipients; and
  5. Publication service: the publication of FF-ICE data for access by authorized subscribers.

3. Detailed descriptions of the NM FF-ICE services are available in the European SWIM registry.

4. An NM B2B certificate is required to make use of the FF-ICE services provided by NM via their B2B (Business to Business) Services.

5. NM provides a translation service whereby all eFPL messages are translated to the FPL message format. Operators may make use of the FF-ICE translation and delivery service provided by NM to address translated FPL messages to ATS units outside of the IFPS zone.

4.3 FF-ICE Messages

1. FF-ICE messages are used to exchange FF-ICE information:

Submission Response - a response message indicating whether a submitted FF-ICE message is valid or not. In case of rejection, it also indicates the reason.

Trial Request - a query to evaluate a flight plan under consideration for an intended flight.

Trial Response - a response to a validated Trial Request message indicating the expected flight plan acceptability and, where practicable, applicable restrictions and constraints.

Filed Flight Plan (eFPL) - a flight plan (to be) submitted as a request for air traffic services.

Filing Status - a response to a validated eFPL message indicating the flight plan acceptability.

Flight Plan Update - an update to the information contained in a previously submitted flight plan.

Flight Cancellation - an instruction to cancel and remove a previously submitted flight plan.

Flight Data Request - a query for flight plan or search and rescue information for a particular flight.

Flight Data Response - a response to a validated Trial Request message indicating the expected flight plan acceptability and, where practicable, applicable restrictions and constraints.

Flight Departure - a notification that a flight has departed.

Flight Arrival - a notification that a flight has landed.

2. The Flight Information Exchange Model (FIXM) provides individual exchange schema for each of the FF-ICE messages.

3. Further details on the format, fields and content are provided in the NM B2B Reference Manual and the FIXM User Manual.

4.4 FF-ICE Requirements

1. General air traffic, operating under IFR must submit eFPLs using the FF-ICE services provided by NM, instead of FPL messages.

2. For all operators an eFPL message shall include, as a minimum (civil aircraft operating as general air traffic fully under IFR have additional requirements):

  1. The GUFI;
  2. The operator flight plan version;
  3. The flight data items required for FPLs as prescribed by the provisions in ICAO Annex 2 Section 3.3.2, ICAO Doc 4444 PANS-ATM Appendix 2.

3. Civil aircraft operating as general air traffic fully under IFR are additionally required to include the following in their eFPL:

  1. Expanded route and 4D trajectory;
  2. Flight specific performance data consisting of performance; climb and descent profiles and climb and descent speed schedules;
  3. Estimated aircraft take-off mass.

4. For state aircraft operating as general air traffic fully under IFR and general air traffic operating under mixed IFR and VFR, the inclusion of items 3. a), b) and c) in eFPLs is optional.

5. Details on the expression of route/trajectory information in an FF-ICE flight plan are provided in the EUROCONTROL Network Manager IFPS Users Manual. When providing a trajectory in an FF-ICE flight plan, the full trajectory from aerodrome of departure to aerodrome of destination must be provided.

6. The operator, or its designated representative, is required to generate and allocate a GUFI to its FF-ICE flight plan. The provision of the GUFI is mandatory when using the filing service and the notification service.

7. The operator flight plan version number is a mandatory element when submitting eFPLs and any subsequent updates. The version number shall be incremented by the operator or their designated representative with every update to the flight plan.

4.5 FF-ICE Flight Planning Procedures

1. Submission, update and cancellation of FF-ICE Flight Plans:

  1. FF-ICE flight plans are submitted, updated and cancelled using the FF-ICE filing service;
  2. Upon processing of an FF-ICE flight plan submission or update, NM provides feedback via a submission response and filing status. In the case of an FF-ICE flight plan cancellation, NM provides feedback via a submission response only.

2. Use of the FF-ICE Trial Service:

  1. The trial service is initiated through the submission of a trial request;
  2. Upon processing of an FF-ICE trial request, NM provides feedback via a submission response and a trial response.

3. Use of the FF-ICE Flight Data Request Service. The use of the FF-ICE flight data request service enables users to request:

  • A copy of accepted eFPLs
  • A copy of supplementary flight plan data
  • A copy of the latest filing status for the flight
  • The submission response status

4. The notification service is used to enable users to transmit departure and arrival notification information to NM.

5. The data publication service is used to enable subscribers to obtain information about flights relevant to their operations.

6. FF-ICE flight plan re-evaluation:

  1. NM performs re-evaluation of FF-ICE flight plans to determine whether flight plans remain in compliance with published restrictions or ATM measures that may have been applied or modified since the flight plan was last evaluated;
  2. The IFPS performs re-evaluation of eFPLs in the same way that it revalidates FPLs/IFPLs (Initial Flight Plans), with all valid flight plans subjected to the same process, same criteria and same possible outcome;
  3. The re-evaluation process applies to all processed eFPLs that received an ACK submission status and ACCEPTABLE filing status;
  4. Operators should make use of the NM B2B Publish/Subscribe services that will provide updates to the eFPL’s filing status, to maintain awareness of the re-evaluation results.

7. Further details on the NM implementation and provision of FF-ICE services and related procedures are provided in the NM IFPS Users Manual.

4.6 Further Information

1. Further information on FF-ICE, the NM implementation and associated procedures can be found in the following:

EUROCONTROL FF-ICE webpage
https://eurocontrol.int/ffice

EUROCONTROL Network Manager IFPS Users Manual
https://www.eurocontrol.int/publication/ifps-users-manual

EUROCONTROL NM B2B Reference Manual

European SWIM Registry
https://eur-registry.swim.aero/home

FIXM User Manual https://docs.fixm.aero/#/

2. The EUROCONTROL NM will provide a flight plan translation service for the FIRs/UIRs in the IFPS zone where FF-ICE/R1 is not mandated and as transition arrangements until full implementation by the concerned states.