ENR 1.10 FLIGHT PLANNING

1 Procedures for the Submission of a Flight Plan

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):
A flight plan shall be submitted prior to following flights:
  1. any flight or portion thereof to be provided with air traffic control service;

  2. any flight in areas or routes prescribed by the appropriate authority to facilitate the provision of flight information, alerting and search and rescue services;

  3. any flight in areas or routes prescribed by the appropriate authority to facilitate cooperation 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: Flight plan is to be submitted for domestic flights within uncontrolled airspace when flying closer than 2.7 NM (5 km) to the dividing line between Estonia and Russia or mainland part of the border line between Estonia and Latvia.


  4. any flight across national borders;
  5. any flight intended to operate at night if they are bound to fly away from the airfield.
1.1 Place of Submission

Aircraft operators may file their IFR or IFR/VFR (mixed) flight plans and associated messages (e.g CHG, DLA, CNL) directly with IFPS using an own AFTN or SITA access point. If those means are not available, flight plan and associated messages may be submitted at the Air Traffic Services Reporting Office (ARO) at the departure aerodrome.

In absence of such office at the departure aerodrome, a flight plan shall be submitted by telephone or AFS to:

ARO TALLINN
Tel:+372 625 8293, +372 605 8905, +372 625 8282 (helpdesk)
Fax:+372 601 6096, +372 625 8280
E-mail:fpl.tugi@eans.ee
1.2 VFR Flight Plan for Alerting Service
An alerting service is provided to flights for which a flight plan has been submitted.
1.3 Contents and Form of a Flight Plan:
  1. If flight plan is filed on ICAO Flight plan form, the instructions for completing those forms shall be followed.

  2. When a flight plan is submitted by telephone or telefax, the sequence of items in the flight plan form shall be strictly followed.

  3. To conduct a glider operation in controlled airspace, a flight plan shall be submitted to an appropriate ATS unit. This flight plan shall contain detailed information on entire route or area employed for the flight, ETO and the vertical layer of operation (lowest and highest level).

  4. A flight plan submitted for a flight across the Estonian territorial border shall contain information for the entire flight up to the aerodrome of intended landing.

  5. A flight plan submitted to conduct a flight along the Estonian territorial border or any ad hoc flight shall include detailed information on route, times to be over and flight levels.

  6. For the flight within or via restricted and danger areas estimated times of entry and exit of areas concerned shall be inserted in the flight plan. The permission reference number shall be inserted in item 18 preceded by the abbreviation RMK.

  7. SID/STAR routes are not to be inserted:
    1. Last point of the flight plan shall be the first waypoint of standard arrival route (STAR) at aerodromes with established STAR procedure. If aerodrome has not established STAR procedure or flight is not following published ATS route, “DCT” shall be inserted.
    2. First point of the flight plan shall be the LAST published waypoint on SID procedure or if no suitable SID is available or there is no requirement for a connecting point, a waypoint within a required distance from the aerodrome according to the RAD, Appendix 5.
1.4 Adherence to ATS Route Structure and FRA Principles

Airspace users are permitted to follow published ATS routes or to flight plan according to published FRA principles, as described in ENR 1.3, between any of the 5 letter waypoints published in ENR 4.4 within Tallinn FIR above FL95.

Airspace users operating according to FRA principles are permitted to cross Tallinn FIR BDRY between Riga FIR and Tampere FIR according to published FRA principles of Estonia, Latvia and Finland.

Airspace users may disconnect from the ATS route by flight planning “DCT” from any significant point on that network to the 5 letter waypoints published in ENR 4.4 according to FRA principles.

Airspace users may connect to the ATS route network by flight planning “DCT” to any significant point published in ENR 4.4.

Filing of Flight Plans for flights in Bodø OFIR shall be in accordance with the flight planning rules in ICAO Doc 7030, NAT section.

1.5 Authorisation for Special Flights

A single permit shall be obtained from the Civil Aviation Administration to organise air races or public aviation events and to conduct flights where it is impossible to follow the rules of the air, or other extraordinary flights.

A request for authorisation shall be mailed so as to be received at least one week before the intended day of operation to:

Post:Estonian Civil Aviation Administration
Lõõtsa 5
11415 Tallinn, ESTONIA
Tel:+372 610 3500
Fax:+372 610 3501
E-mail:ecaa@ecaa.ee
1.6 Adherence to Airspace Utilization Rules and Availability

No flight plans shall be filed via the airspace of Tallinn 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 Tallinn FIR and any reference to them shall be made via https://www.nm.eurocontrol.int/RAD/index.html.

2 Repetitive Flight Plan System

2.1 General

Aircraft Operators who make use of Repetitive Flight Plans (RPLs) shall ensure that RPL data for flights into, departing from or overflying the Tallinn FIR are submitted to the NMD-RPL Team.

RPL Files shall be submitted in electronic format that is described in IFPS Manual to the following address:

Aircraft operators for clarifications or other questions could contact RPL Supervisor at:

E-mail:fdorplsup@eurocontrol.int
Tel:+322 745 1957
The IFPS Manual can be obtained from EUROCONTROL Internet site: https://www.eurocontrol.int/publications/ifps-users-manual.
2.2 ATS Messages
Messages about departure (DEP), arrival (ARR) and others (DLA, CHG, CNL) are submitted to:
  • for IFR flights departing from Tallinn FIR into IFPS Zone only to IFPS;
  • for IFR flights departing from Tallinn FIR and exiting the IFPS Zone to IFPS and for ATS units outside the IFPS Zone;
  • for VFR flights to corresponding ATS units which are in the Tallinn FIR and beyond its limits.

3 Changes to the Submitted Flight Plan

When a specific IFR flight is likely to encounter a delay of 15 minutes or VFR flight 30 minutes in excess of the departure time stated in the FPL it shall be announced as early as possible before departure to:

Note 1: 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.

Note 2: 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 a flight, for which a flight plan has been submitted, is cancelled, the appropriate ATS unit shall be informed immediately.

Changes to a current flight plan for a controlled flight during flight shall be reported or requested, subject to the provisions in ICAO Annex 2, para. 3.6.2. Significant changes to a flight plan for an uncontrolled VFR flight include changes in endurance or in the total number of persons on board and changes in time estimates of 30 minutes or more.
3.1 Arrival Report (Closing a Flight Plan)

At an aerodrome where air traffic service is not provided, a report of arrival shall be made at the earliest possible moment after landing to Tallinn ACC:

AFS:EETTZQZX
Tel:+372 625 8256; +372 625 8254; +372 621 4428.

When communication facilities at the arrival aerodrome are known to be inadequate, immediately prior to landing the aircraft shall, if practicable, transmit by radio directly to an appropriate ATS unit or via other aircraft, a message comparable to an arrival report, where such a report is required.

Arrival reports made by aircraft shall contain the following elements of information:
  • aircraft identification;
  • departure aerodrome;
  • destination aerodrome (only in the case of diversionary landing);
  • arrival aerodrome;
  • time of arrival.

If it is expected that the arrival report will not reach the appropriate ATS unit within 30 minutes after the ETA, a notification shall be made in item 18 of the flight plan, concerning the time when the arrival report may be expected (e.g RMK/EXPECT ARR 1835).

Note: Whenever an arrival report is required, a failure to comply with the provisions as listed above may cause serious disruption in the ATS and incur great expenses in carrying out unnecessary search and rescue operations.