Need Armenia flight support urgently?
Send schedule, route, aircraft documents and passenger/cargo details for quick review.
Do You Need a Armenia Overflight Permit?
For foreign civil aircraft transiting Armenian airspace without landing, current Armenia AIP GEN 1.2 provides an important exemption: scheduled and two-or-more non-scheduled transit flights may be conducted without special permission, and a single non-scheduled transit flight may also be conducted without special permission when a flight plan is filed. Landing, State, special and other categories follow separate authorization procedures.
Required Details for Obtaining Armenia Overflight Permit Application
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]
Authorization Validity
For pure transit without landing where no special permission is required, permit validity is not applicable. A permission issued for a single non-scheduled air transportation is valid for 48 hours from the time stated in the permission. Foreign State-aircraft permissions are valid for 72 hours from the stated time.
For those intending to execute a passenger flight landing or technical stop, the Armenia Airports Authority has specific regulations overseeing the issuance of Armenia Overflight Permits, often involving associated charges. These charges typically cover Route Navigation Facility Charges for overflight, as well as landing and parking fees for aircraft making stops.
Being a signatory to the Chicago Convention, Armenia requires strict compliance with ICAO (International Civil Aviation Organization) general rules for international air traffic. This encompasses adherence to regulations concerning the transport of troops, equipment, materials, and dangerous goods. For more comprehensive information, please reach out to us.
Aviation Regulations Armenia
Armenia's aviation regulations are overseen by the Civil Aviation Committee (CAC) under the Ministry of Territorial Administration and Infrastructure. These regulations are vital for ensuring the safety, security, and efficiency of the aviation sector within the country. Here's an overview of the key components and aspects of Armenia's aviation regulations:
Key Components of Armenia's Aviation Regulations:
Civil Aviation Committee (CAC):
The CAC is the regulatory authority responsible for overseeing civil aviation regulations in Armenia. It formulates policies, issues regulations, conducts inspections, and ensures compliance with national laws and international standards.
Civil Aviation Regulations (CARs):The CARs issued by the CAC specify detailed rules and standards covering various aspects of aviation operations, including:
Airworthiness standards for aircraft design, construction, and maintenance.
Flight operations, including pilot licensing, training requirements, and operational procedures.
Air traffic management and control procedures.
Airport operations, infrastructure standards, safety measures, and environmental protection.
Airport Management:Airports in Armenia are managed and operated by the General Department of Civil Aviation under the supervision of the CAC. The CAC ensures that airports comply with safety, security, and operational standards set forth in the CARs.
International Agreements and Standards:Armenia is a member of the International Civil Aviation Organization (ICAO) and adheres to its standards and recommended practices (SARPs). The CAC works to align Armenia's aviation regulations with international standards to facilitate safe and efficient air transport operations.
Important Areas of Regulation:
Safety and Security:
Regulations ensure that aircraft operations, maintenance, and airworthiness comply with stringent safety standards to mitigate risks and ensure safe flights. Aviation security measures are enforced to protect passengers, crew, and airport facilities.
Licensing and Certification:Pilots, engineers, air traffic controllers, and other aviation professionals must obtain licenses and certifications issued by the CAC. Aircraft and airlines operating in Armenia must comply with certification requirements to ensure safe and lawful operations.
Air Traffic Management:Air traffic control services in Armenian airspace are provided according to international standards to ensure safe and efficient management of air traffic flows. Regulations cover airspace management, communication protocols, and navigation aids.
Consumer Protection:Regulations protect passengers' rights, including compensation for flight delays, cancellations, denied boarding, and mishandled baggage. They also ensure transparency in fare pricing and booking conditions.
Recent Developments:Armenia's aviation sector has undergone developments aimed at enhancing safety, infrastructure, and regulatory frameworks. Recent initiatives include:
Airport Infrastructure Development:Investments in upgrading Zvartnots International Airport in Yerevan and Shirak International Airport in Gyumri to improve operational efficiency and accommodate increasing passenger traffic.
Technological Advancements:Adoption of advanced technologies in air traffic management, airport operations, and aviation safety to enhance overall aviation capabilities.
Regulatory Updates:Implementation of new regulations and updates to existing CARs to align with international standards and improve safety and regulatory oversight.
Conclusion:Understanding and complying with Armenia's aviation regulations is essential for all stakeholders in the aviation industry, including airlines, airport operators, and aviation service providers. For specific and detailed regulatory requirements, consulting the Civil Aviation Committee (CAC) and referring to the latest legal documents and guidelines issued by Armenian authorities is recommended. These regulations play a crucial role in ensuring the safety, security, and efficiency of Armenia's aviation sector while supporting its growth and development in the region.
Overflight Permit Categories for Ad Hoc and Private Flights
1 - Overflight Permits (Charter Passenger Flights)
2 - Overflight Permits (Private Passenger Flights)
3 - Overflight Permits (Non-Schedule Cargo Flights)
Overflight Permit Categories for Block Permits
1 - Monthly Block Overflight Permits (For Scheduled and Non-schedule Airlines Flights)
2 - Seasonal Block Overflight Permits (Scheduled Commercial Airlines Flights)
Overflight Permit Charges
Armenia overflight and landing permit charges are based on aircraft type, routing, flight category and navigation fees. Operators should consider overflight navigation charges, landing and parking fees, and ground handling costs when planning operations within Armenian airspace.
Flight Information Region In Armenia
Armenian airspace is defined within one Flight Information Region (FIR):
1 - Yerevan Zvartnots (UDDD) FIR
Armenia FIRs ( Entry / Exit Points ) :
| West Bound Entry Point | West Bound Exit Point | East Bound Entry Point | East Bound Exit Point |
|---|---|---|---|
| MAGRI | MAGRI | TISOT | TISOT |
| IRLAN | IRLAN | MATAL | MATAL |
| NEGAN | NEGAN | ELSIV | ELSIV |
| INDUR | INDUR | PEMAN | PEMAN |
| REBLO | REBLO | VETEN | VETEN |
| OGEVI | OGEVI | ||
| TAVRO | TAVRO |
International Trip Support Services
We provide comprehensive and personalized flight planning and International Trip Planning 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 offers unrivalled support services across all international and domestic airports in Armenia. With extensive expertise, the Permit2Fly team arranges Armenia overflight permits for ad-hoc charter flights and scheduled airline block permits in accordance with Civil Aviation Committee regulations and approved timeframes.
Our Permit2Fly operations team provides professional coordination for overflight and landing permits, ground handling, fuel arrangements and airport services across Armenia.
Trust Permit2Fly to handle all ground support operations at Armenian airports, including overflight and landing permit coordination for your aircraft operations.
About Armenia | History - Geography
Armenia is a nation, and former Soviet republic, in the mountainous Caucasus region between Asia and Europe. Among the earliest Christian civilizations, it’s defined by religious sites including the Greco-Roman Temple of Garni and 4th-century Etchmiadzin Cathedral, headquarters of the Armenian Church. Khor Virap Monastery is a pilgrimage site near Mount Ararat, a dormant volcano just across the border in Armenia.
Between the 16th and 19th centuries, the traditional Armenian homeland composed of Eastern Armenia and Western Armenia came under the rule of the Ottoman and Iranian empires, repeatedly ruled by either of the two over the centuries. By the 19th century, Eastern Armenia had been conquered by the Russian Empire, while most of the western parts of the traditional Armenian homeland remained under Ottoman rule. During World War I, Armenians living in their ancestral lands in the Ottoman Empire were systematically exterminated in the Armenian Genocide. In 1918, following the Russian Revolution, all non-Russian countries declared their independence after the Russian Empire ceased to exist, leading to the establishment of the First Republic of Armenia. By 1920, the state was incorporated into the Transcaucasian Socialist Federative Soviet Republic, and in 1922 became a founding member of the Soviet Union. In 1936, the Transcaucasian state was dissolved, transforming its constituent states, including the Armenia Soviet Socialist Republic, into full Union republics. The modern Republic of Armenia became independent in 1991 during the dissolution of the Soviet Union.
The Given Below Information Is Extracted from the Armenia AIP
Introduction
On 21 DEC 2006 the Republic of Armenia will delegate responsibility for the provision of flight planning services within the Yerevan FIR to the Integrated Initial Flight Plan Processing System (IFPS).
The Republic of Armenia will therefore become part of the IFPS Zone on 21 DEC 2006.
The following paragraphs describe the flight plan filing procedures that will come into effect on 21 DEC 2006 for flights, which are intending to operate within the Yerevan FIR.
GeneralEffected from 21 DEC 2006 flight plan and associated messages for IFR/GAT1 flights intending to operate within the Yerevan FIR shall no longer be addressed to ATS Units within the Yerevan FIR. The only addresses, which heed to be entered for the portion of the flight within the Yerevan FIR, are those of the two IFPS Units at Haren (Brussels) and Bretigny (Paris), as detailed below.
Guidance is given below for the addressing of flight plan and associated messages in respect of flights, which proceed beyond the boundaries of the IFPS Zone.
With effect from 21 DEC 2006 Aircraft Operators may submit flight plans directly to IFPS for all IFR/GAT flights, or portions thereof, departing from within the Yerevan FIR.
Flight plans for flights departing outside the Yerevan FIR and operating into or overflying the Yerevan FIR shall be submitted in accordance with the procedures published by the State within which the aerodrome of departure is located.
With effect from 21 DEC 2006 Aircraft Operators, which make use of Repetitive Flight Plans (RPLs) are requested to ensure that RPL data for flights into, departing from or overflying the Yerevan FIR are submitted to the RPL Section of the CFMU.
RPL files should preferably be submitted in electronic format via E-Mail or alternatively as paper copy via SITA or post. Further information can be obtained by contacting the RPL Supervisor at the following telephone number: +32-2-7299847.
Flight Plan Message AddressingFlights departing an aerodrome within the Yerevan FIR and remaining wholly within the IFPS Zone.
Flight plan and associated messages need ONLY be addressed to the two IFPS Units as follows:
Note: The abbreviation GAT stands for "General Air Traffic" and is defined within Europe as "flights conducted in accordance with the regulations and procedures promulgated by State civil aviation authorities and operating under the control or authority of the civil ATS organization". The converse of GAT is "Operational Air Traffic (OAT)" which is defined as "flights conducted outside civil controlled airspace and which operate in accordance with military air traffic service procedures and which as a result do not require systematic addressing to civilian ATS Units".
For AFTN - EBBDZMFP and LFPYZMFP
For SITA - BRUEP7X and PAREP7X
Note 1:BOTH IFPUs must be addressed for all flight plan and associated messages.
Note 2:Specific addresses for any VFR or OAT portions of the flights will have to be added" by the originator preferably by using the readdressing function described in paragraph 3.4 below.
Flights Entering Or Overflying The Yerevan FIRFor that portion of the flight within the Yerevan FIR, only the two IFPUs need to be addressed as indicated in paragraph 3.1.1 above.
Flights Departing An Aerodrome Within The Yerevan FIR And Then Exiting The IFPS ZoneFor that portion of the flight within the Yerevan FIR, only the two IFPUs need to be addressed as indicated in paragraph 3.1.1 above.
For any portion of the flight outside the IFPS Zone, the flight plan message originator is responsible for having the flight plan and associated messages addressed to all appropriate ATSUs in accordance with ICAO procedures.
The procedure below describes the preferred way of addressing as it ensures consistency between messages distributed within and outside the IFPS Zone. This procedure will enable the IFPS to distribute a validated flight plan or associated message to any additional AFTN address, which is included in the address line as, described below.
The Re-addressing FunctionAny additional addresses to be included should be placed after the originator information line and immediately before the open bracket which indicates the beginning of the message. An example of an AFTN message with such additional addresses is given below:
ZCZC BOC548 250925 MB
FF EBBDZMFP LFPYZMFP
250920 LUKKZPZX
AD ADDRESS1 ADDRESS2 ADDRESS3 ADDRESS4 ADDRESS5 ADDRESS6 ADDRESS7
AD ADDRESS
(FPL-AFL83-IS-B73A/M-SXYR/C
-LUKK1430-…
The following rules apply:
(i) The extra address lines must begin with the keyword AD to distinguish them from other comment lines which may be present.
(ii) The extra address lines must be consecutive (no other comment lines between them), and they must be immediately before the line containing the open bracket.
(iii) There must be no more than 7 additional addresses per line, and each must be of 8 characters.
The IFPS Validation System (IFPUV)Flight plan originators wishing to test FPLs with the IFPUV, prior to their submission to the operational IFPS, may submit them via either AFTN or SITA to one of the following addresses:
AFTN : EBBDZMFV
SITA: BRUEY7X
Test flight plans may be submitted with a DATE OF FLIGHT (DOF) up to 120 hours (5 days) in advance by means of DOF/ in Item 18, in the format DOF/yymmdd where "yy" is the year indicator, "mm" is the month and "dd" is the date. The system will respond to flight plan submission by means of a Reply Message in the form of either an Acknowledgement (ACK), which indicates that the FPL would pass automatic processing, or a REJECT (REJ), which indicates a failure. In the case of REJ the Reply Message will contain a system generated indication of the reason for failure. The IFPUV therefore does not generate MANUAL (MAN) messages.
Every Reply Message from the IFPUV contains the phrase "This message has been sent by a test system and must not be used operationally". This message is added to ensure that there is no confusion between submissions to the test system and those to the operational IFPS.
The IFPUV is not connected to the operational IFPS and; test messages are neither distributed nor stored in the system. Since FPLs are not stored in the IFPUV, flight plan associated messages (i.e. CHG, DLA, CNL, RQP, etc.) are rejected by the IFPUV with the message:
•"ERROR: no existing filed flight plan matches this message".
Frequently Asked Questions
Is an overflight permit required for Armenia?
For foreign civil aircraft transiting Armenian airspace without landing, current Armenia AIP GEN 1.2 provides an important exemption: scheduled and two-or-more non-scheduled transit flights may be conducted without special permission, and a single non-scheduled transit flight may also be conducted without special permission when a flight plan is filed. Landing, State, special and other categories follow separate authorization procedures.
What is the lead time for Armenia overflight or landing permits?
Do not use a blanket 48-hour overflight lead time. Pure foreign civil transit without landing is flight-plan based under the current AIP. For a single non-scheduled air transportation to/from/within Armenia, the applicant generally submits the application at least 72 hours before operation. Training and special flights use a 3-working-day procedure.
What is the FIR for Armenia?
Armenian airspace is defined within the Yerevan FIR (UDDD).
What documents are required for Armenia permit applications?
Required documents include aircraft registration, airworthiness certificates, insurance, flight schedule, crew and passenger details, and purpose of flight. Additional documents may be requested depending on the operation type.
Can Permit2Fly arrange handling and fuel in Armenia?
Yes. Permit2Fly coordinates ground handling, parking, fuel uplift, and crew support at Yerevan, Gyumri and other Armenian airports.