ENR 1.10  Flight planning

(Restriction, Limitation or advisory Information)

1.10.1  PROCEDURES FOR THE SUBMISSION OF A FLIGHT PLAN

A flight plan shall be submitted in accordance with Annex 2, para 3.3.1 prior to operating:

  1. any IFR flight,

  2. any VFR flight.

    1. departing from or destined for an aerodrome within a CTR;

    2. crossing any CTR within BAHRAIN FIR;

    3. across any International State Boundary or the FIR / UIR boundary.

Time of submission

Except for repetitive flight plans, a flight plan shall be submitted at least 60 minutes prior to departure, taking into account requirements for timely information of ATS units in airspace along the route to be flown, including requirements for early submission for ATS Air Traffic Flow Management (ATFM) purposes.

Place of submission

  1. Flight plans shall be submitted at the Air Traffic Services Reporting Office (ARO) at the departure aerodrome.

  2. In absence of such office at the departure aerodrome, a flight plan shall be submitted by telephone, telefax or teletype to the nearest ARO as listed below, (except as indicated under c.). An acknowledgement of receipt must be obtained prior to departure when using telefax or teletype.

    Post:

    BAHRAIN ARO

    Tel:+973 17321181 / +973 17321182

    Fax:+973 17323876

  3. For domestic flights from an uncontrolled to a controlled aerodrome a flight plan shall be submitted by telephone to the ARO at destination.

VFR flight plan for alerting service only

Alerting service in principle provided to flights for which a flight plan has been submitted.

Contents and form of flight plan

  1. ICAO flight plan forms are available at ARO‘s and airport offices at uncontrolled aerodromes. The instructions for completing those forms shall be complied with.

  2. Flight plans concerning IFR flights and international VFR flights shall include FIR / UIR boundary estimates.

  3. When a flight plan is submitted by telephone, teletype or telefax, the sequence of items of the flight plan - form shall be strictly adhered to.

Adherence to ATS route structure

No flight plans shall be filed for routes deviating from the published ATS route structure, unless prior permission has been obtained from BAHRAIN ACC.

Authorization for special flights

Flights of a specific character such as survey flights, scientific research flights etc. may be exempted from the restriction specified above.

Request for exemption shall be mailed so as to be received at least one week before the intended day of operation to:

Post:

Undersecretary for Civil Aviation
Bahrain Civil Aviation Affairs

1.10.2  REPETITIVE FLIGHT PLAN SYSTEM

General

The procedures concerning the use of Repetitive Flight Plans (RPL) conform to ICAO Document 7030 and PANS RAC 12th edition. Except where indicated hereunder.

REPETITIVE FLIGHT PLANS / FLIGHT SCHEDULE DATA LISTS

Pending full implementation of the RPL concept, RPLs are transmitted on the AFTN as if they were Filed Flight Plans.

1.10.2.1 Operators are required to provide advance details of Season Scheduled Services operating within the BAHRAIN FIR / BAHRAIN UIR at least 14 days in advance of implementation or change, to the Flight Data Processing Unit (FDPU).
Post:

The Flight Data Processing Unit
Aeronautical Information Services Office

Note: The submission of such details to Air Traffic Control does not constitute a request for approval of flight schedules.

1.10.2.1.1 This Data is required to be presented, on separate sheet for each 12 hours UTC of each day, in the format shown in the "REPETITIVE FLIGHT PLAN LISTING".

Note: There is a requirement to indicate in Column Q for all flights the Entry point Designator for BAHRAIN FIR / BAHRAIN UIR with EST (UTC).

1.10.2.1.2 Incidental changes and cancellations of RPL

Incidental changes to and cancellations of RPL relating to departures from BAHRAIN INTERNATIONAL airport shall be notified as early as possible and not later than 30 minutes before departure to:

Post:

BAHRAIN ARO

Tel:+973 17321181 / +973 17321182 for departures from BAHRAIN INTERNATIONAL airport.

RPL Lists shall be replaced in their entirety by new lists prior to the instruction of the summer and winter schedules.

1.10.2.1.3 Delay

When a specific flight is likely to encounter a delay of one hour or more in excess of the departure time stated in the RPL, the ATS unit serving the departure aerodrome shall be notified immediately.

Note: Failure to comply with this procedure may result in the automatic cancellation of the RPL for that specific at one or more of the ATS unit concerned.

1.10.2.1.4 ATS messages

For a flight operated on a RPL, a flight plan message (FPL) will be transmitted pending full implementation of the RPL concept in the region. Departure messages (DEP) or Delay messages (DLA) relating to such flights will also be transmitted to appropriate ATS units.

1.10.2.2  FLIGHT PLANS
1.10.2.2.1  Scheduled Flights departing from airfields in the FIR
1.10.2.2.2 Standard Flight Plans for flights must be filed with the Aerodrome / Heliport AIS Unit at the aerodrome of departure, or
1.10.2.2.3 Alternatively, by direct arrangement between the operator and the local ATC Unit involved, a Standard ICAO Flight Plan may be stored at the aerodrome of departure and activated by that unit at 0001 UTC on the day of operation.
1.10.2.3  CHANGES TO FLIGHT DETAILS
1.10.2.3.1  Permanent Changes

Changes of permanent nature to any of the details previously supplied (under ENR 1.10.2.2.1 and ENR 1.10.2.2.2 above) require that complete details must be advised, both to the FDPU at Bahrain and to any other aerodrome concerned within the FIR, either by a completely new replacement plan, or by clear "insert / delete" editing instructions.

1.10.2.3.2  Temporary Changes
1.10.2.3.2.1 Extra flights require submission of both

  1. a standard Flight Plan, and

  2. Flight Data details to BAHRAIN FDPU.

1.10.2.3.2.2 Replacement flights, (i.e. Flights with temporary changes to details which have been submitted under ENR 1.10.2.1.1 and ENR 1.10.2.2.2 above) require a Standard Flight Plan clearly annotated in item 12 "Replacement of Scheduled Flight (c / s) of ... (date)";

Note: Flight Schedule Data Lists are required by ATSUs to prepare Air Traffic Control Data Systems in advance, thus reducing the possibility of traffic delay resulting from work - load in peak periods. Timely provision of Scheduled Flight Data, preferably more than the prescribed 14 days in advance, is therefore in the best interests of operators of scheduled air transport.

1.10.2.4  FLIGHT PLAN FORM
1.10.2.4.1 The Flight Plan Form must be completed according to the instructions contained in Doc 4444 - ATM 501, Appendix 2.
1.10.2.4.2 The following options are REQUIRED by the ATS authority for all flight operating within the BAHRAIN FIR / BAHRAIN UIR:
1.10.2.4.2.1 Flight Plan ITEM 8 - The second field letter denoting the TYPE OF FLIGHT.
1.10.2.4.2.2 Flight Plan ITEM 18 - The indicator "EET / " followed by FIR / UIR boundary designators and accumulated elapsed times as follows:

  1. Flight entering the BAHRAIN FIR: The location indicator for the BAHRAIN FIR together with the accumulated estimated time since departure (e.g. EET / OBBB 0345).

  2. Flights departing from the BAHRAIN FIR: All boundary designators together with the corresponding estimated elapsed times to those points (e.g. for a flight from OBBI to EGLL, EET / OEJD 0005, OJAC 0125, OSTT 0145, LCCC 0210, LGGG 0245, LTBB 0300, LYBA 0420, LOVV 0450, EDDU 0510, EBUR 0545, EHAA 0600, EGTT 0615).

1.10.2.4.2.3 Flight Plan ITEM 18 - The indicator "SEL / " followed by the SELCAL code.
1.10.2.4.2.4 Flight Plan ITEM 19 - To be completed in full.

1.10.3  CHANGE TO THE SUBMITTED FLIGHT PLAN

All changes to a flight plan submitted for an IFR flight or a controlled VFR flight and significant changes to a flight plan submitted for an uncontrolled VFR flight shall be reported as soon as possible to the appropriate ATS unit.

1.10.3.1 In the event of a delay in departure 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.

Note 1: If a delay in departure of a controlled flight is not properly reported, the relevant flight plan date 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 current ETA.

1.10.3.2 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 Annex 2.3.6.2 (Adherence to flight plan).

Significant changes to a flight plan for an uncontrolled VFR flight include changes in endurance, or total number of persons on board and changes in time estimates of 30 minutes or more.

1.10.3.3  Arrival report (Closing a flight plan)

A report of arrival shall be made at the earliest possible moment after landing to the airport office of the arrival aerodrome by any flight for which a flight plan has been submitted except when the arrival has been acknowledged by the local ATS unit.

After landing at an aerodrome which is not the destination aerodrome (diversionary landing) the local ATS unit shall be specifically informed accordingly.

In the absence of a local ATS unit at the aerodrome of diversionary landing the pilot is responsible for passing the arrival report to the destination aerodrome.

  1. aircraft identification

  2. departure aerodrome

  3. destination aerodrome

  4. time of arrival

In the case of diversion, insert between "destination aerodrome" an "time of arrival":

  1. the "arrival aerodrome"


1.10.4  ADDITIONAL REQUIREMENTS RELATED TO RVSM AIRSPACE

Note: Flights will not be given access to BAHRAIN RVSM airspace when:

  1. No flight plan has been received, or

  2. A flight plan has been received but the required RVSM data has not been included in the flight plan.

1.10.4.1 Except as indicated in ENR 1.10.4.3 flight between FL 290 to FL 410 is for exclusive use of RVSM approved aircraft. Non - RVSM certified aircraft shall flight plan accordingly.
1.10.4.2 Operators of RVSM certified aircraft shall insert the letter "W" in item 10 of the flight plan regardless of the requested level.
1.10.4.3 Acceptance of non - RVSM certified State aircraft for flight at RVSM levels is subject to prevailling traffic conditions. RVSM certified aircraft will be offered priority in order to make maximum use of airspace capacity.

Note: Consequently, operators of State aircraft intending to navigate within BAHRAIN FIR / BAHRAIN UIR are advised to dispatch RVSM certified aircraft or flight plan at non - RVSM levels.

1.10.4.4 Operators of non - RVSM certified State aircraft requesting a flight level within RVSM airspace shall insert the phrase "STS / NONRVSM" in item 18 of the flight plan.
1.10.4.5 In addition to the requirements of ENR 1.10.4.4 operators of non - RVSM certified State aircraft requesting to operate in RVSM airspace shall include the letter "M" in item 8 of the flight plan.
1.10.4.6 The flight plan for an aircraft intending to operate across or within the lateral limits of RVSM airspace shall include:

  1. The entry point and requested flight level for that portion of the route commencing immediately after the entry point.

  2. The exit point and requested flight level for that portion of the route commencing immediately after the exit point.