1.1.1   Purpose of the Flight Plan

The purpose of the flight plan is to inform the competent ATS units enabling them to supervise the flight within the scope of air traffic control as well as flight information service and alerting service.

Guidance material on the completion of the ICAO Flight Plan form and the Repetitive Flight Plan (RPL) in conformance with the EUR RVSM flight planning requirements, is provided in the ICAO EUR Regional Supplementary Procedures.

Furthermore, the following requirement is in addition to the flight planning requirements contained in the ICAO EUR Regional Supplementary Procedures:

In addition to military operations, operators of customs or police aircraft shall insert the letter M in Item 8 of the ICAO flight plan form.

1.1.2   Types of Flight Plan

1. Individual Flight Plan

   For each individual flight an individual flight plan shall be filed. Flights, in which several aircraft take part in a formation, as well as every separate stage of flight for flights with intermediate stops, shall also be regarded as individual flight.

2. Repetitive Flight Plan

   For several, however, at least ten IFR flights planned by the same aircraft operator, a repetitive flight plan may be filed, provided that these flights are planned to be conducted regularly and in the same manner and at least once a week.

1.3.1   The use of the indicators GAT/OAT in a flight plan

• General Air Traffic (GAT):

  Flights conducted in accordance with the regulations and procedures promulgated by the State civil aviation authorities and operating under the control or authority of the civil ATS organisation.

• Operational Air Traffic (OAT):

  Flights, which do not comply with the provisions of GAT and are conducted under the control or authority of the military ATC organisation in most countries.

Aircraft Operators (AOs) must indicate the planned change from GAT to OAT or vice versa in the FPLs.

The indicator shall be inserted after the appropriate significant point or geographical coordinates in the route.

The IFPS always assumes that all flight plans begin GAT, unless, it finds a change to GAT indicated later in the route. In this case it is assumed that everything prior to the change was OAT.

1.3.2   VFR flights planned above FL195 (5950 m STD)

In case of flight operation above FL 195 (5950 m STD) not in ad-hoc segregated airspace, the planned task shall be inserted in Field 18 of FPL, furthermore in Field 15 (route) the geographical or other significant point where FL195 (5950 m STD) will be crossed, shall be shown.

Note: The climb out area to the route segment of the flight operation planned above FL 195 (5950 m STD) shall be shown in Field 18 defined with radius of a circle pinpointed on a geographical or other significant point where FL 195 (5950 m STD) to be crossed.

E.g. …DCT NORAH/N0160A085 DCT 4702N02120E/N0140F240 DCT NORAH/N0170A035 … (RMK/ Parachuting 4602N02135E R5NM).

Differences from ICAO standards and recommended practices can be found in the GEN 1.7

1.4.1   Flights entering or overflying the IFPS Zone

With respect to IFR/GAT flights which are intended to enter or overfly the IFPS Zone the flight plans and associated messages need only be addressed to the IFPS units in Haren (Brussels) and in Bretigny (Paris), instead of the relevant ATS units. These units will transmit the FPL and associated messages to all ATS units concerned within the IFPS Zone.

Note: The list of States participating in the IFPS distribution area See ENR 1.10.

In case of a mixed flight (IFR/VFR and/or OAT/GAT) the addressees of the ATS units which will handle the VFR and OAT part of a flight within the IFPS Zone shall also be added.

Re-addressing function shall be used for the flight plans and associated messages addressed to the IFPUs which means to add the addresses of IFPUs to the address line only and additional addressees shall be included in the message text as the first element after the originator information line.

Bodies authorized to distribute flight plans transmitted via AFTN or SITA are responsible for addressing function as follows:

1. Aircraft operators who file a FPL direct to the IFPS are responsible for the correct addressees to:
   • the IFPS units,
   • the appropriate ATS units for the portion of the flight outside the IFPS Zone, and
   • the units supervising VFR or OAT flights within the IFPS Zone in case of mixed operation, and
   • any other addressees prescribed by the appropriate authorities and the aircraft operator and the aerodromes.
2. in other cases the flight plan distributive body (ARO, FIC, a designated military unit for this task) is responsible for the addresses to all ATS units concerned. However, depending on type of a flight, transmission of a FPL may be prescribed by the appropriate authority or an aircraft operator or an aerodrome to other addressees, it is the flight plan originator's responsibility to add the special addresses.

1.4.2   AFTN addressing of Flight Plans and associated messages

See ENR 1.11

1.4.3   Adherence to Airspace Utilization Rules and Availability

No flight plans shall be filed via the airspace of Budapest FIR deviating from the State restrictions defined within the Route Availability Document (RAD). This common European reference document contains all airspace utilisation rules and availability for Budapest FIR and any reference to them shall be made via

1.5.1   Direct filing of Flight Plans to the IFPS

All foreign aircraft operators (AOs), and those national air carriers who meet the technical and FPL filing and addressing requirements are permitted to submit their IFR/GAT or mixed flight plans directly to the IFPS via AFTN, SITA or via other communication means.

1.5.2   Flight Plan filing at Budapest Liszt Ferenc International Airport

Pilots of aircraft departing from Budapest Liszt Ferenc International Airport have the possibility to send flight plans to the ATS reporting office via e-mail, fax and by phone.

1.5.3   Flight Plan filing at AFIS aerodrome.

Pilots of aircraft departing from an AFIS aerodrome shall file a flight plan form personally or via telephone to the aerodrome flight information service.

If a flight intends to operate wholly in an aerodrome traffic zone, limited information required by ATS unit can be submitted.

1.5.4   Flight Plan filing at non-AFIS aerodrome.

In case of departure planned from a non-AFIS aerodrome the pilot shall submit a flight plan via telephone or fax to the Area Flight Information Centre (FIC):

1.6.1   Flight plans submitted directly to IFPS.

FPLs will be checked by IFPS for syntax, format and content. The flight plan originator will be informed on the acceptance by an ACK message, on the necessary manual correction by a MAN message and on the rejection by a REJ message.

Note: After accepting a flight plan IFPS will determine the ATS units responsible for IFR/GAT flights within IFPS Zone for which and for other addressees indicated in the message the flight plan will be forwarded. Unless a filed flight plan has been acknowledged by IFPS via an ACK message ATS units concerned will not have the flight plan and the aircraft may not begin operation.

1.6.2   When a flight plan is not sent directly to IFPS the receiving unit of FPLs is responsible for:

• checking for format and content to the extent possible,
• calling originator’s attention to the errors and giving assistance for correct filing of FPLs,
• indicating acceptance of a flight plan to the originator and
• correct transmission and distribution of flight plans for the parties concerned.

If FPLs are forwarded to FIC or to IFPS via ATS reporting office, originators should inquire about the acceptance of FPLs.

Verbal information, if necessary, will be forwarded by the receiving unit.about the acceptance of filed FPLs by IFPS or FIC.

Note: The acceptance of FPL does not relieve the pilot of his/her responsibility for obtaining Air Traffic Control (ATC) clearance for the operation in controlled airspace or in controlled aerodromes as well as for correct preflight preparation.