Iran Overflight Permits Procedures

 Iran country has its own set of rules, regulations and procedures for permits to aircraft wishing for landing or even entering their air space, whether you’re operating a private, charter flight, scheduled or non-scheduled operation, passengers or cargo trip, a technical or traffic landing, Prior Permission is mandatory required the application procedures requiring complete flight information and Aircraft documents.

According to Iran CAA AIP any aircraft owner/operator intent to fly in Iran airspace request has to submit for Iran overflight clearance to air transport department at least 48 working hours prior from flight departure schedule. Always include AFTN on your flight plan, but you’ll only need an overfly permit from Iran.

Planning to make a passenger flight landing or technical stop, Iran Airports Authority have their own regulations regarding the issuance of flight Iran Overflight permit as there is generally a payment involved. The charges normally payable would be the Route Navigation Facility Charges for overflight and also landing and parking charges in case of aircraft making halts.

Iran is a signatory to the Chicago Convention therefore the conditions of flights and crews should strictly be compliant with ICAO general rules of international air traffic and in accordance with their regulation for transport of troops, equipment, materials and dangerous goods, please write us for more detail information.

Required Details for Obtaining Iran Overflight Permit

---

1 - Flight Schedule
2 - Entry / Exit Points with ATC Route
3 - Lead Passenger Details
4 - Consignee & Consigner Details for Cargo Flights
5 - Aircraft Documents [ AOC, COA, COI, CON, COR]

Overflight Permits Category’s for Adhoc and Private

---

1 - Overflight Permits (Charter Passenger Flights)
2 - Overflight Permits (Private Passenger Flights)
3 - Overflight Permits (Non-Schedule Cargo Flights)

Overflight Permits Category’s for Block :

---

1 - Monthly Block Overflight Permits (For Scheduled and Non-schedule Airlines Flights)
2 - Seasonal Block Overflight Permits (Scheduled Commercial Airlines Flights)

Permit Validity

---

- Iran Overflight Permit is normally valid for 72 hours.

Overflight Permit Charge's

---

We do not charge any type of hidden cost in Civil Aviation Permit Processing Cost and Iran Overflight Permits Procedures. Our fee is straight and direct without any additional fees in Iran Overflight Permit We do not require large upfront deposits or commitments. We strive to develop long term relationships and we work hard to earn your referrals. Besides receiving essential financial monthly reports these very particular customers expect to entirely rely on professional teams and they offer just that. This trust is earned through our administrative and financial control, as well as our services standards of work.

Iran Flight Information Region :

---

Iran Airspace is divided into 01 Flight Information Regions (FIRs)

1 - Tehran (OIIX) FIR

International Trip Support Services

---

We provide comprehensive and personalized flight planning and trip support services to the corporate aviation industry. Our dedicated and experienced staff work together to ensure you have a smooth trip that is tailored to your particular needs. with years of international flight planning experience, the latest trip coordination technology, and a dedication to high-quality customer service, each member of our knowledgeable team is equipped with the tools to exceed your expectations.

Our proficient flight support team offering unrivalled support services to any International & Domestic Airports in Iran along with their expertise, our permit2fly team can arrange Iran Overflight Permits for Ad-hoc Charter Flights, Scheduled Airline Seasonal Block Permits from Civil Aviation Authority of Iran according to their legal time frame.

Trust Permit2fly, to handle all your ground supervisory at Iran airports and obtain Iran overflight and Landing permit for any of your aircrafts to operate in the territory of Iran.

About Iran | History - Geography

---

Iran, a mountainous, arid, and ethnically diverse country of southwestern Asia. Much of Iran consists of a central desert plateau, which is ringed on all sides by lofty mountain ranges that afford access to the interior through high passes. Most of the population lives on the edges of this forbidding, waterless waste.

The capital is Tehran, a sprawling, jumbled metropolis at the southern foot of the Elburz Mountains. Famed for its handsome architecture and verdant gardens, the city fell somewhat into disrepair in the decades following the Iranian Revolution of 1978–79, though efforts were later mounted to preserve historic buildings and expand the city’s network of parks. As with Tehran, cities such as Esfahan and Shiraz combine modern buildings with important landmarks from the past and serve as major centers of education, culture, and commerce.

The Given Below Information Is Extracted from the Iran AIP

---

Procedures For Submission a Flight Plan

A flight plan shall be submitted for all IFR/VFR flight prior to operating except as mentioned in item 1.4 c) below.

Time Of Submission

All types of operations within Tehran FIR shall not be submitted more than 120 hours and at least 60 minutes before EOBT at the departure aerodrome Except for repetitive flight plans (RPL) and item 1.2 below.

If a flight plan is filed more than 24 hours in advance of the estimated off block time of the flight to which it refers, date of flight (DOF) shall be inserted in item 18 of the flight plan..

Note: When completing flight plan, the departure time entered in field 13 must be the estimated off block time (EOBT) not the planned airborne time.

Note: All operators shall meet flight plan criteria and procedures which have been promulgated by other states or organizations, e.g. Euro control requirement is at least 3 hours before EOBT.

Authorization For Special Flights

Submission of flight plans for the following flights are exempted from time provision in paragraph 1.1 above:

a) Scramble

b) SM

c) Hospital

d) Head

e) Search and rescue (SAR) aircraft engaged in SAR mission

f) Flight check

g) Firefighting aircraft

h) Flight carrying hazardous materials

j) VFR Helicopters for military and police

k) Local flights subject to pre- arrangement with relevant ATS unit

l) Rescue flights

Place Of Submission

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

b) In absence of such office at the departure aerodrome, a flight plan shall be submitted to the ATS unit concerned.

Note: At aerodromes in which there is no AFTN station, the flight plan, after approval of the flight plan by the ATS unit of that aerodrome, shall be sent by that ATS unit to the nearest AFTN station by fax.

The mentioned ATS unit shall then after contact the receiving AFTN station to confirm the quality reception of the flight plan, to give the permission to that AFTN station for transmission of the received flight plan via AFTN.

In each case, the AFTN station bears no responsibilities for the content of the received flight plan.

c) If no ATS unit is available at the point of departure, a flight plan shall be submitted to the ATS unit at the last departure aerodrome or nearest ATS unit whichever is applicable.

Methods Of Receiving Flight Plan

Air Traffic Services Reporting Office (ARO) or relevant ATS unit shall receive flight plan via any of following methods:

• The approved RPL.

• Flight plan form submitted by pilot or designated representative.

Note: All INTL DEP flights from Tehran/Mehrabad INTL and Imam Khomeini INTL airports may send their flight plan only to Air Traffic Services Reporting Office (ARO) on designated addressee: OIIIZPZB/ OIIEZPZB. Such flight plan will be checked and forwarded by ARO to the related addresses via AFTN.

• c) In joint civil/military airport by prior local agreement via recordable CP hotline.

Note 1:Only for Rescue flights, rescue operators / designated representatives may submit a flight plan that contains the basic information of each rescue helicopter to the relevant ATS unit for repetitive rescue flights; according to the approved local coordination procedures and regarding aerodrome operational limitations, considering the following:

I. Use STS/HOSP for a medical flight and ambulance or STS/MEDEVAC: for a life critical medical emergency evacuation, as appropriate in ITEM 18: OTHER INFORMATION of flight plan.

II. The submitted basic flight plan is valid until 24 hours after EOBT.

III. The details of each specific rescue flight shall be transmitted to the relevant ATS unit before departure through the recordable telephone line or FAX and if not practicable or desirable for rescue operations, via Radiotelephone (RTF) before or immediately after being airborne by pilot indicating the nature of flight.

Note 2:Only Flight plans of Rescue flights are acceptable via radiotelephone (RTF) on ATS frequencies when there are no other facilities like recordable telephone lines or FAX.

Note 3:Rescue flights are exempted from time provisions mentioned in paragraph 1.2.

The flight plan form must be completed according to the instructions contained herein.

ICAO flight plan forms are available at AROs and ATS units at all aerodromes.

Adherence To ATS Route Structure

No flight plan shall be filed by foreign aircraft for routes other than published ATS routes within Tehran FIR unless prior permission has been obtained from the appropriate ATS authority. An ATS unit will authorize an aircraft to deviate from the ATS routes indicated in flight plan when emergency circumstances or bad weather conditions or failure of navigation aids makes the deviation necessary.

Repetitive Flight Plan

Repetitive Flight Plans (RPL) should be used for all scheduled IFR flights operated regularly on the same day(s) of consecutive weeks and at least ten occasions or every day, over a period of at least ten consecutive days.

Initial submission of complete RPL listing and any subsequent seasonal resubmission of complete listing and any changes thereto shall be made with a minimum lead time of three weeks since the reception by the Aeronautical Information Service (AIS), sufficient for permitting the data to be properly assimilated by the ATS organization.

Note: only one RPL Amendment (RMDT) is acceptable during validity time of RPL.

The element of each flight plan shall have a high degree of stability.

Repetitive Flight Plans (RPL) is acceptable for domestic IFR flights. Application of RPL procedures for international flights requires the establishment of bilateral or multilateral agreements between the States concerned.

Validation Of Flight Plan

Each flight Plan either submitted individually or based on RPL criteria has a validity time of:

i. 30 minutes after EOBT if any part of flight will be operated under the IFR.

ii. 60 minutes after EOBT for VFR flight that will be operated under the VFR.

Note: The validity time of the flight plan should be extended for deicing purposes, but for delay, more than 75 minutes of EOBT coordination between relevant ATS units is required.

Delay, Modification And Cancellation Of Flight Plan

Only one revision is acceptable up to 30 minutes after EOBT for IFR flights/60 minutes after EOBT for VFR flights. It is applicable 10 minutes after reception by ATS units via AFTN otherwise by Fax or recordable Telephone as prescribed in 1.3 (Place of submission) in the following cases:

a) A delay of 30 minutes for IFR flights/60 minutes for VFR flights, or more in excess of the EOBT; and/or (see Form F102A).

b) A change in type and/or registration mark of aircraft (If the registration mark is not used as Item 7: ACFT IDENT); (see Form F103).

Note 1:The revision mentioned above shall be received by ATS unit’s prior aircraft requesting start up.

Note 2:if combination of above is involved, a change message must be issued. (see Form F104).

Note 3:if the change in type and/or registration mark of aircraft causes any change in other information contained in flight plan, the details shall be received and sent same as the modification message.

Note 4:if the day of flight is changed over 0000 UTC, change message must be issued instead of delay message and indicating in both field 13b and 18, the EOBT and the DOF.

Note 5:It is important to note that when the DOF/ element is modified by Field Type 22(PANS ATM, Appendix 3 paragraph 2.3.2) in a CHG message, the complete Item 18 data must always be provided. If it is not, any elements omitted will be considered as modifications and they will be removed from the Item 18 content.

In case of an incidental change in the aircraft identification, the departure aerodrome, the route and/or destination aerodrome, the flight plan and RPL shall be cancelled for the day concerned and a new flight plan shall be submitted.