Armenia Overflight Permit Regulations

Armenia Overflight Permits Procedures

Armenia 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 Armenia CAA AIP any aircraft owner/operator intent to fly in Armenia airspace request has to submit for Armenia 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 Armenia.

Planning to make a passenger flight landing or technical stop, Armenia Airports Authority have their own regulations regarding the issuance of flight Armenia 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.

Armenia 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 Armenia 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


- Armenia 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 Armenia Overflight Permits Procedures. Our fee is straight and direct without any additional fees in Armenia 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.

Armenia Flight Information Region :


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

1 - Yerwvan Zvartnots (UDDD) FIR


Armenia FIRs ( Entry / Exit Points ) :



West Bound Entry PointWest Bound Exit PointEast Bound Entry PointEast Bound Exit Point
MAGRIMAGRITISOTTISOT
IRLANIRLANMATALMATAL
NEGANNEGANELSIVELSIV
INDURINDURPEMANPEMAN
REBLOREBLOVETENVETEN
OGEVIOGEVI  
TAVROTAVRO  

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 Armenia along with their expertise, our permit2fly team can arrange Armenia Overflight Permits for Ad-hoc Charter Flights, Scheduled Airline Seasonal Block Permits from Civil Aviation Authority of Armenia according to their legal time frame.

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

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 Turkey.

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.

Armenia Overflight Permits Procedures

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.

General

Effected 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 Addressing

Flights 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 FIR

For 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 Zone

For 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 Function

Any 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".