AIP for ISRAEL(section ENR-1.10)valid from 18 MAY 2023

ENR 1.10 FLIGHT PLANNING

(RESTRICTION, LIMITATION OR ADVISORY INFORMATION)

1. Procedures for submission of a flight plan

(a) The State of Israel is a participant in the Integrated 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/GAT flight plan information to ATS units within the participating European states, which collectively comprise the IFPS zone. IFPS will not handle CVFR flight plans or military OAT flights within Tel-Aviv FIR, but will process the GAT portions of a mixed OAT/GAT flight plan and the IFR portions of a CVFR/IFR flight plan, as well as military flights departing outside Tel-Aviv FIR.

(b) For contingency purposes, IFPS comprises two units sited within the EUROCONTROL facilities in Brussels, Belgium, and Paris, France. Consequently all IFR/GAT flight plans and associated messages must be addressed to both IFPS units (see ENR 1.11 - addressing of FPL messages). Following successful processing, the FPL will be delivered, at the appropriate time, to all the ATS units' addresses on the flight-profiled route within the IFPS zone.

When submitted flight plans for IFR/GAT flights directly to IFPS, pilots and aircraft operators shall comply with the procedures published in the EUROCONTROL Network Manager Handbook.

Pilots and aircraft 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:

(b1) The FPL Acceptance Acknowledgement Message (ACK);
(b2) Referred for Manual Treatment (MAN);
(b3) 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 flight plan associated messages can be corrected manually, the originator will be informed by IFPS. If not, they will be returned to the originator to be corrected (REJ message).

Unless a flight plan has been received and accepted by IFPS (an ACK message has been received), the requirement to submit a flight plan for an IFR/GAT flight intending to operate within the IFPS zone will not have been satisfied and no ATC clearance will be issued for such a flight. A corrected flight plan must be refiled, without delay, to IFPS without the detected errors mentioned on the REJ message by IFPS.

Procedures for submission of a flight plan

A flight plan shall be submitted prior to operating:

any IFR flight;
any CVFR flight

Time of submission

Flight plan shall be submitted at least 60 minutes prior to departure, taking into account the requirements of ATS units in the airspace along the route to be flown for timely information, including requirements for early submission for Air Traffic Flow Management (AFTM) purposes which should be filed a minimum of 3 hours before EOBT.

The IFPS always calculates the DOF if none is given in the FPL. In doing so will assume the EOBT to be within the next 24 hours after the filing time. If a FPL is filed more than 24 hours in advance of the EOBT, the DOF must be indicated in item 18 of the FPL.

Note: The IFPS will not accept FPL's submitted more than 120 minutes (5 days) in advance of the flight taking place.

Place of submission:

FPLs shall be submitted at the Aeronautical information Services Office (AIS) at the departure aerodrome.
In the absence of such an office at the departure aerodrome, a flight plan shall be submitted via Email to: Tel-Aviv/Ben-Gurion AIS office, AIS@iaa.gov.il or by TEL. 972-3-9756216/7
Pilots or operators that have access to AFTN/AMHS can submit a flight plan to those systems.

Contents and form of an ATS flight plan

ATS flight plan forms are available at AIS offices.
Flight plans concerning IFR flights along ATS routes need not include FIR-boundary estimates. Inclusion of FIR-boundary estimates is, however, required for off-route IFR flights and international VFR flights. Flight plans concerning flights intended to operate off ATS routes shall be submitted in a special form, in accordance with the DOM AIP, part B, chapter B-08.
When a flight plan is submitted by telephone, the sequence of items in the flight plan form shall be strictly followed.

Adherence to ATS route structure and Route Availability Document (RAD)

No flight plans shall be filed via “Tel-Aviv “ 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 “Tel-Aviv” FIR and any reference to it shall be made via: Http://www.nm.eurocontrol.int/RAD/index.html

Adherence to flight plan

Except as provided for in Para. e), 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.
Unless otherwise directed by the appropriate air traffic control unit, controlled flights shall, in so far as practicable:
1. When on an 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.
Subject to the overriding requirement in Para. b), an aircraft operating along an ATS route segment defined by reference to very high frequency omnidirectional radio (VOR) 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.
Deviation from the requirements in Para, b) shall be notified to the appropriate air traffic services unit.
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 2 minutes from that notified to air traffic services, a revised estimated time shall be notified as soon as possible to the appropriate air traffic services unit.
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 (when applicable).
2. Change of route:
  1. Destination unchanged: aircraft identification; description of new route of flight beginning with the position from which requested change of route is to commence; and any other pertinent information.
  2. Destination changed: aircraft identification; 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; and any other pertinent information.

Authorization for special flights

Flights of a specific character, such as survey flights, scientific research flights, etc., may be exempted from the restrictions specified above. A request for exemption shall be E-mailed to the Operation Division of the CAA (golane@mot.gov.il) at least one week before the intended day of the flight.

Maximum cruising levels for flights within Tel-Aviv FIR

Traffic from the Tel-Aviv/Ben-Gurion TMA with a destination in the southern sector should file MAX 29 000 FT.

2. Changes to the submitted flight plan

All changes to a flight plan submitted for an IFR flight or a controlled VFR flight shall be reported as soon as possible to the appropriate ATS unit or directly to IFPS. In the event of a delay in departure of 15 minutes (for international flights westbound) or 30 minutes (for domestic, and international flights east and southbound), 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 flight plan has been canceled.

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.

Whenever a flight, for which a flight plan has been submitted, is canceled, the appropriate ATS unit or IFPS shall be informed immediately.

3. Termination of a flight plan

With reference to Art. 78 to the air navigation regulation. In the following aerodromes the termination of a flight plan in not required:

Tel-Aviv/Ben Gurion
Eilat/Ilan and Asaf Ramon
Haifa