ENR 1.10 FLIGHT PLANNING

 

ENR 1.10.1 Introduction

Iceland is a participating State in the Initial Flight Plan Processing System (IFPS), which is an integral part of the EUROCONTROL centralized Air Traffic Flow Management (ATFM) system. 
IFPS is the sole source for the distribution of IFR FPL information to ATSUs within the participating States, which collectively comprise the IFPS Zone.
IFPS does not process VFR flight plans. 
Isavia ANS processes VFR flight plans and State Operational  Air Traffic (OAT) flight plans.

ENR 1.10.1.1 IFPS

Flight plan and associated messages for flight rules I, Y and Z, that is all flight rules except VFR, intending to operate within the Reykjavik CTA shall now be addressed to the two IFPS Units at Haren (Brussels) and Bretigny (Paris), see ENR 1.11. 
 
Network IFPS Unit Addresses
IFPU1
Haren, Belgium  		IFPU2
Brétigny, France
AFTN EUCHZMFP EUCBZMFP
SITA BRUEP7X PAREP7X
 
When submitting flight plans to IFPS, pilots and operators shall comply with the procedures introduced in Eurocontrol IFPS Users Manual.
Pilots and operators are ultimately responsible for the complete filing of their flight plans and all associated messages. This encompasses compilation (including addressing), accuracy and submission of flight plan messages and also for the reception of the operational reply messages from IFPS.
Operational reply messages delivered by IFPS are the following:
  1. The FPL Acceptance Acknowledgement Message (ACK);
  2. Referred for Manual Treatment (MAN);
  3. Message Rejected (REJ).
IFPS is the responsible unit for accepting and distributing IFR/GAT flight plans for flights conducted within the IFPS Zone. The originator of a flight plan message will be informed of the successful processing of flight plans and flight plan associated messages within IFPS by an ACK message. Flight plans, which cannot be processed by IFPS, will be passed on to the IFPS correction unit to be corrected manually (MAN). If flight plan and associated messages can be corrected manually, the originator will be informed of this by a Long ACK message. If not, they will be returned to the originator to be corrected (REJ).
A flight plan is considered as filed only if the flight plan message originator has received Acknowledge message (ACK).

ENR 1.10.1.2 Web Portal - Cronos

Isavia ANS maintains a web portal intended for VFR FPLs. It is possible to use web portal for submitting flight plans.
For access to the web portal, see further information at:
https://ans.isavia.is/en/c-preflight-information 
If the web portal is used, a contact must be established to confirm approval of the FPL.
Operational reply messages delivered by Cronos web portal are the following:
1.    The FPL Acceptance Acknowledgement Message (ACK);
2.    Message Rejected (REJ).
A flight plan is considered as filed only if the flight plan message originator has received Acknowledge message (ACK).

ENR 1.10.2 Procedures for the submission of a flight plan

A flight plan shall be submitted in accordance with regulation 770/2010 prior to operating:
  1. any flight or portion thereof to be provided with air traffic control service;
  2. every IFR flight;
  3. any flight across international borders;
  4. any flight requesting alerting service.
(for supplementary information regarding FPL see ENR 1.8.3).

ENR 1.10.2.1 Time of submission

Flight plans shall not be submitted more than 120 hours before the estimated off-block time of a flight. If the flight plan is submitted earlier than 24 hours before the EOBT, insert the date of flight in item 18 preceded by DOF/. 
The flight plans shall be submitted with minimum prior notice:
  1. Domestic VFR flights (V);
    1. 30 minutes if the Web Portal is used or submitted via AFTN, but
    2. 60 minutes if submitted via telephone.
  2. International VFR flights (VFR) shall be submitted no later than 60 minutes before the EOBT.
  3. IFR flights (I, Y and Z) shall be submitted no later than 60 minutes before the EOBT.
  4. IFR flights (I, Y and Z) which may be subject to air traffic flow and capacity management (ATFCM) shall be submitted no later than 3 hours before EOBT.
  5. Urgent flight (e.g., a rescue mission, or an urgent hospital flight), the flight plan may be submitted later. However, if practicable, the flight plan should be submitted at least 30 minutes before the EOBT. 

ENR 1.10.2.2 Place of submission

The flight plan shall be submitted according to ENR 1.11. 

ENR 1.10.2.3 Alerting service

Alerting service is provided:
  1. for all aircraft provided with air traffic control service;
  1. in so far as practicable, to all other aircraft having filed a flight plan or otherwise known to the air traffic services, however as far as a VFR-flight is concerned only in case of overdue arrival at destination; and
  1. to any aircraft known or believed to be the subject of unlawful interference.

ENR 1.10.2.4 Closing a flight plan

A report of arrival shall be made in person, by radiotelephony or via data link 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.
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.
When no air traffic services unit exists at the arrival aerodrome, 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.
When communication facilities at the arrival aerodrome 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, transmit to the appropriate air traffic services unit, a message comparable to an arrival report. 
Arrival reports made by aircraft shall contain the following elements of information:
  1. aircraft identification;
  2. departure aerodrome;
  3. destination aerodrome (only in the case of a diversionary landing);
  4. arrival aerodrome;
  5. time of arrival.

ENR 1.10.2.5 Contents and form of a flight plan

Flight plan shall be in accordance with an ICAO Flight Plan. 
See contents of the ICAO Flight Plan in ENR 1.8.3.

ENR 1.10.2.6 Adherence to ATS route structure

Unless otherwise authorized by the appropriate ATS 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 centre line of that route; or
  2. when on any other route, operate directly between the navigation facilities and/or points defining that route.

ENR 1.10.2.6.1 Changeover point

Subject to the overriding requirement in 1.10.2.6 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.

ENR 1.10.2.6.2 Reporting of deviations

Deviation from the requirements in 1.10.2.6 shall be notified to the appropriate air traffic services unit.

ENR 1.10.2.6.3 Deviations from the current flight plan

In the event that a controlled flight 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. Deviation from speed: 
    1. Deviation from Mach number/true airspeed: if the sustained Mach number/true airspeed at cruising level varies by plus or minus Mach 0.02 or more, or plus or minus 10 kt. true airspeed or more from the current flight plan, the appropriate air traffic services unit shall be so informed. 
    2. Within the Reykjavik Domestic Area: If the indicated airspeed enroute between waypoints changes or is expected to change by 5% of the speed, in the ICAO FPL submitted, the appropriate air traffic services unit shall be informed immediately.
    3. Outside the Reykjavik Domestic Area: Deviation from ATC assigned Mach number/indicated airspeed: the appropriate air traffic services unit shall be informed immediately.
  3. Change in time estimate: except where ADS-C is activated and serviceable in airspace where ADS-C services are provided, if the time estimate for the next applicable reporting point, flight information region boundary or destination aerodrome, whichever comes first, changes in excess of 2 minutes from that previously notified to air traffic services, the flight crew shall notify the appropriate air traffic services unit as soon as possible.

ENR 1.10.2.7 Authorisation for special flights

Requests for special flights shall be sent to ICETRA to the email  icetra@icetra.is.

ENR 1.10.3 Repetitive flight plan system

Reykjavik FIR Repetitive flight plans (RPL) are no longer used due to unique equipment requirements in flight plans. 

ENR 1.10.4 Changes to a submitted flight plan

Subject to the provisions of ENR 1.10.2.6 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.
 
Note: If the flight plan is submitted for the purpose of obtaining air traffic control service, the aircraft is required to wait for an air traffic control clearance prior to proceeding in accordance with the amended FPL. If the flight plan is submitted for the purpose of obtaining flight information service, the aircraft is required to wait for acknowledgment of receipt by the unit providing the service.