Menu

AIP
Aeronautical Information Publication

Armenia

eAIP 1st Edition

Consult Notam for Latest Information

ARMATS of ARMENIA

ENR 1.10  Flight planning (Restriction, limitation or advisory information)

1  Procedures for the submission of a flight plan

A flight plan shall be submitted in accordance with ICAO Annex 2, 3.3.1, prior to operating:
  1. any IFR/VFR flight or portion thereof to be provided with air traffic control service,
  2. any IFR flight outside of controlled airspace;
  3. any flight within or into designated areas, or along designated routes, when so required by the appropriate ATS authority to facilitate the provision of information, alerting and search and rescue services;
  4. any flight within or into designated areas or along designated routes, when so required by the appropriate ATS authority to facilitate co-ordination with appropriate military units or with air traffic services units in adjacent States in order to avoid the possible need for interception for the purpose of identification;
  5. any flights across national borders.
  Time of submission
The flight plan for the flights subject to ATFM (IFPZ etc.) measures shall be submitted at least 3 hours before EOBT.
The flight plan for the flights that are not subject to ATFM measures shall be submitted at least 60 minutes before EOBT.
  Place of submission
  1. Flight plans shall by submitted at the Air Traffic Services Reporting Office (ARO) at the departure aerodrome.
  2. In the absence of such an office at the departure aerodrome, a flight plan shall be submitted Aerodrome control tower.

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

  Contents and form of a flight plan
ICAO flight plan forms is used.
A flight plan shall comprise information regarding the following items and considered relevant by the appropriate ATS authority.
  1. Aircraft identification
  2. Flight rules and type of flight
  3. Number and type (s) of aircraft and wake turbulence category
  4. Equipment
  5. Departure aerodrome
  6. Estimated off-block time
  7. Cruising speed (s)
  8. Cruising level (s)
  9. Route to be followed
  10. Destination aerodrome and total estimated elapsed time
  11. Alternate aerodrome (s)
  12. Fuel endurance
  13. Total number persons on board
  14. Emergency and survival equipment
  15. Other information
  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 the Armenian ATC authorities.
  Authorization for special flights
To be developed.
  Item 18 of Flight Plan
In item 18 of Flight Plan indicate name of the flight operator.

2  Repetitive flight plan system

  General
The procedures concerning the use of Repetitive Flight Plans (RPL) conform to ICAO Doc 7030
RPL lists relating to flights in and to flights overflying the Yerevan FIR shall be submitted at least 15 days in advance, in duplicate, to the following addresses:
  1. by airmail: ATC ARMATS
    Airport “Zvartnots” Yerevan-42
    Republic of Armenia
  2. via AFS: UDDDZRZX
  3. by e-mail: rplteam@armats.am
  4. with landing:
    - Airport Yerevan UDYZZTZX
    - Airport Gyumri UDSGZTZX
    - Airport Stepanavan UDLSZTZX
    - Airport Yerevan/Erebuni UDYEYXYX
  Changes and cancellations of RPL
Permanent changes of approved RPL shall be submitted at least 7 working days prior the operation of flights to the following addresses:
  1. by airmail: ATC ARMATS
    Airport “Zvartnots” Yerevan-42
    Republic of Armenia
  2. via AFS: UDDDZRZX
  3. by e-mail: rplteam@armats.am
  4. with landing:
    - Airport Yerevan UDYZZTZX
    - Airport Gyumri UDSGZTZX
    - Airport Stepanavan UDLSZTZX
    - Airport Yerevan/Erebuni UDYEYXYX

A single change of an approved RPL shall be submitted as early as possible and not later than 60 minutes before departure in the form of the flight plan.

  Delay
Delay messages of an approved RPL shall be submitted as early as possible and not later than 30 minutes before departure.
   ATS messages
For a flight operated on a RPL no flight plan message is transmitted. All ATS messages relating to such flights will be transmitted to ATS units outside the YEREVAN FIR.

3  Changes to the submitted flight plan

All changes to a submitted flight plan shall be reported as soon as possible to the appropriate ATS unit. 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.

  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 within 30 minutes via any channel of communication.
Arrival reports shall contain the following elements of information:
  • aircraft identification
  • departure aerodrome
  • destination aerodrome
  • time of arrival.
In the case of diversion, insert the “arrival aerodrome” between “destination aerodrome” and “time of arrival”.