1.1   Purpose and Types of the Flight Plan

1.2   Flights subject to submission of a Flight Plan

• Any flight in uncontrolled airspace between 4000 FT (1200 M) AMSL and 9500 FT (2900 M) AMSL, except non-power driven aircraft;
• International Flights, except as specified in 1.2.2;
• Any flight in controlled airspace;
• Any flight to, from and crossing a TIZ airspace with the exception of non-power driven aircraft;
• The following VFR flights:
  1. VFR flights above FL 195, with the exception of those planned in ad-hoc segregated airspace;
  2. Night VFR;
  3. Glider flights in cloud.
• Special cases:
  1. State aircraft flying outside MCTR, MTMA and TRAs;
  2. Civil aircraft flying inside and MCTR not within published operational hours;
  3. Flights in civil aerodrome control zones (CTR) outside the published operational hours of ATC service (LHSM, LHDC);
  4. For multiple landings a flight plan shall be filed for every flight segment;
  5. For flights flying the same route multiple times, separate flight plans shall be filed for each segment.

1.3   Completion of a Flight Plan form

A Flight Plan form shall be completed in accordance with the provisions contained in PANS-ATM (Doc 4444/501) Appendix 2.

Where STAR procedures are published, RNAV capable aircraft, shall insert the first way-point of the STAR as the last point of the filed FPL route.

In case of LHBP arrival, non-RNAV capable aircraft should insert TPS as the last point of the filed FPL route.

Aircraft operators are requested not to indicate SID/STAR information in the filed route of FPLs.

1.4   Addressing of a Flight Plan and Flight Plan associated messages.

Flight plan and flight plan associated messages shall be addressed for the purpose of transmission to units concerned and shall be forwarded to the addressees via the existing communication facilities. The units concerned are the ATS units of a departure and destination aerodrome, and also the ATS and ATFCM units along the planned route of a flight. In addition in cases of certain flights originators shall add special addressees prescribed by appropriate authorities, AOs or aerodromes for which FPLs and associated messages should be forwarded.

1.5   Submission of a Flight Plan

1.6   Acceptance of a Flight Plan

1.7   Time for Filing a Flight Plan

Unless special circumstances require a flight plan shall be submitted prior to taxi for taking off not earlier than 24 hours and not later than 60 minutes before Estimated off Block Time (EOBT). For flights subject to ATFCM measures FPLs shall be submitted at least 3 hours prior to EOBT.

Note: ATFCM measures may be applied for IFR/GAT (or mixed) flights operating in Budapest FIR. In this case pilots are responsible to inquire if their flights are subject to ATFCM measures. Relevant information can be obtained from ARO at departure aerodrome or from other relevant ATS unit as well as from Flow Management Position at Budapest Area Control Centre (ACC):

If FPLs are filed more than 24 hours in advance of EOBT insert the date of flight (DOF) in FPLs.

FPLs may not be filed earlier than 5 days before operation.

AFIL can be filed in the following cases:

• at least 10 minutes before the aircraft is estimated to reach the boundary of controlled airspace if FPLs are submitted for the purpose of obtaining air traffic control clearance for operation in controlled airspace,
• after departure
  1. in case of search and rescue flights for the purpose of averting the consequences of damage caused by forces of nature, serious disaster and air accident, of police mission as well as of flights for urgent ambulance and medical assistance,
  2. in case of departure from field other than aerodrome

  as early as possible.

1.8   Cancellation and change of FPL

FPL shall be cancelled by operator to the ATS unit for which FPL has originally been submitted if:

• flight will not operate,
• aircraft wishes to depart before the time indicated in the filed FPL, or
• any changes are required in respect of aerodrome of departure or destination or aircraft identification,

In the latter cases a new FPL, including the modified data, shall be submitted.

For flights subject to ATFCM measures the following procedures shall be applied:

• when an FPL or an RPL has been filed by an AO but it is decided, within 4 hours of EOBT, to use an alternative routing between the same aerodromes of departure and destination, a cancellation message with priority “DD” shall be transmitted to all addressees of the previous flight plan, and
• a replacement flight plan (RFP) in the form of the FPL with identical call sign shall be transmitted after the CNL message and with a delay of not less than 5 minutes.
• The replacement flight plan shall contain as the first element of item 18. the indication ”RFP/An”, where RFP signifies “Replacement Flight Plan” and “n” is the sequence number of RFP.

Operator shall inform the unit for which FPL has previously been submitted if:

• a flight is expected to delay for more than 30 minutes (for flight subject to ATFCM measure it is 15 minutes), or

FPL will be cancelled by the competent ATS unit, unless information is received for taxiing, departure or revision for EOBT within 60 minutes after the EOBT.

• any necessary changes in the other items of the previously filed FPL (e.g. cruising speed, cruising level etc.).

FPLs submitted to ARO via telephone shall be modified via telephone. FPLs submitted to ARO via www.netbriefing.hu shall be modified via www.netbriefing.hu. The EOBT of FPLs submitted via www.netbriefing.hu can be modified via telephone.

Notes:

1. Should the cruising level be changed only, it can be done when radio contact is established with ATS units.
2. Information for cancellation or change must be initiated not more than 12 hours in advance of EOBT.
3. Receiving units will notify other units to whom the origin FPLs have been forwarded about cancellation and changes.

1.9   Special handling requirement

The insertion of a STS/… indicator in Field 18 of a Flight Plan will identify that a flight may require special handling.

The following status indicators can be used in Budapest FIR:

• ALTRV - Flight operated in accordance with an altitude reservation
• ATFMX - Flight approved for exemption from ATFCM measures by the appropriate ATS authority
• FFR - Fire fighting
• FLTCK - Flight check for calibration of NAVAIDs
• HAZMAT - Flight carrying hazardous material
• HEAD - Flight with Head of State status
• HOSP - Medical flight declared by medical authorities
• HUM - Flight operating on a humanitarian mission
• MARSA - Flight for which a military entity assumes responsibility for separation of military aircraft
• MEDEVAC - Life critical medical emergency evacuation
• NONRVSM - Non-RVSM capable flight intending to operate in RVSM airspace
• SAR - Flight engaged in a search and rescue mission
• STATE - Flight engaged in military, customs, or police services

STS indicators recognized for ATFCM purposes comprises of STS/HEAD; STS/SAR; STS/MEDEVAC; STS/FFR; STS/STATE; STS/HUM; STS/HOSP. See ENR 1.9 para 5.

Unjustified use of keywords (abbreviations) for special handling requirement is disciplinable.

1.10   General information about Non-standard Planning Zones

To manage the operationally sensitive areas, Non-standard Planning Zones (NPZ-s) are published. An NPZ is a defined airspace volume within which the planning of FRA DCT trajectories is either not allowed or allowed only for exceptions as described.

Airspace users can avoid these areas by planning via appropriate FRA Points or according to described conditions. Planning a DCT through the published NPZ will cause a reject message (REJ) by IFPS except where the set conditions are met. For complete NPZ source information see RAD.

2.1   General

Note: List of FIRs participating in IFPS zone: See ENR 1.10 para 1.9See ENR 1.10 para 1.9

2.2   Types of submission

2.3   RPL submission criteria

1. there is a minimum of 7 working days (see 2.6.2 below) between reception of the file by EUROCONTROL and the activation of the first flight affected by the amendment, and
2. there must be two Mondays between reception of the file and the activation of the first flight affected by the amendment.

2.4   RPL submission procedure

• IFPS RPL format (former DBO/DBE format) - via diskette, SITATEX or electronic file transfer
• ICAO format (hard copy) - on paper (ICAO Doc 4444)

2.5   Specific EUROCONTROL requirements for RPL operation

2.6   General information

EUROCONTROL CFMU FDO/RPL Team

2.7   Suspension of RPLs

Please suspend the following flights with effect from ddmm until ddmm.

Note:

1. Flights can not be suspended for periods of less than 3 days
2. A suspension message shall be received by not less than 48 hours before the EOBT of the earliest affected flight/s. When sufficient notice cannot be given, individual CNL messages must be filed.
3. If the UNTIL is not filled in, then a Recovery message will have to be send.

2.8   Recovery of RPLs

Please recover the following flights with effect from ddmm.

Note: A recovery message shall be received by not less than 48 hours before the EOBT of the earliest affected flight/s. When sufficient notice cannot be given, individual FPL messages must be filed.