1.1.1   Purpose of the Flight Plan

The purpose of the flight plan is to inform the competent ATS units of the intended flight and 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 and Area Navigation (RNAV) specifications are provided in the ICAO EUR Regional Supplementary Procedures (Doc 7030).

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

   A flight plan related to a series of frequently recurring, regularly operated individual flights with identical basic features, submitted by an operator for retention and repetitive use by ATS units.

3. Air filed Flight Plan

   Flight plan submitted by airborne aircraft to the relevant ATS unit.

1.3.1   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.3.2   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.3.3   Submission of a Flight Plan

1.3.4   Acceptance of a Flight Plan

1.3.5   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.3.6   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.3.7   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
• 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

RMK/OAT or STS/OAT shall be used in the FPL, if the whole duration of the flight is planned as OAT flight.

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.4.1   Definitions

1. Flight and flow — information for a collaborative environment (FF-ICE): Information necessary for planning, coordination, and notification of flights, exchanged in a standardized format between members of the ATM community, including those involved in flight operations and aerodrome operations.
2. Flight and flow — information for a collaborative environment (FF-ICE) services. A set of services established for the purposes of facilitating the exchange of FF-ICE, accurate assessment of demands, appropriate resource planning, and optimizing flight planning and execution.
3. Flight and flow — information for a collaborative environment (FF-ICE) services unit. A unit designated by the appropriate ATS authority for the provision of FF-ICE services.
4. Filed flight plan (FPL or eFPL). The latest flight plan as submitted by the pilot, an operator or a designated representative for use by ATS units. Note.— The FPL denotes a filed flight plan exchanged using aeronautical fixed service while eFPL denotes a filed flight plan exchanged using FF-ICE services. The eFPL allows for the exchange of additional information not contained within the FPL.
5. Globally unique flight identifier (GUFI). An unchangeable data element associated with a flight that allows all eligible members of the ATM community to unambiguously refer to information pertaining to the flight.

1.4.2   FF-ICE Services

1. FF-ICE operates within a system-wide information management (SWIM) operational environment in which the main procedures and processes are described in terms of services.
2. EUROCONTROL Network Manager (NM) is the designated FF-ICE services unit for the IFPS Zone and provides the following FF-ICE services:
   1. filing service: the evaluation of a filed flight plan (eFPL) for the provision of air traffic services and indication of flight plan acceptability;
   2. trial service: the evaluation of a trial request with respect to flight plan acceptability and, where practicable, the indication of applicable restrictions and resultant constraints on the flight; Note: The trial service offers an opportunity for an operator or designated representative to submit “what-if” scenarios and to receive feedback from an FF-ICE services unit, prior to submitting an eFPL or flight plan update.
   3. flight data request service: the provision of data regarding a specific flight such as the latest version of a filed flight plan or search and rescue data upon request by an eligible recipient;
   4. notification service: the provision of data regarding a certain flight event such as departure and arrival to required recipients; and
   5. publication service: the publication of FF-ICE data for access by authorized subscribers.
3. Detailed descriptions of the NM FF-ICE services are available in the European SWIM registry.An NM B2B certificate is required to make use of the FF-ICE services provided by NM via their B2B (Business to Business) Services.
4. NM provides a translation service whereby all eFPL messages are translated to the FPL message format. Operators may make use of the FF-ICE translation and delivery service provided by NM to address translated FPL messages to ATS units outside of the IFPZ.

1.4.3   FF-ICE Messages

1. FF-ICE messages are used to exchange FF-ICE information and are described in the following table:

   Message	Description
   Submission Response	A response message indicating whether a submitted FF-ICE message is valid or not. In case of rejection, it also indicates the reason.
   Trial Request	A query to evaluate a flight plan under consideration for an intended flight.
   Trial Response	A response to a validated Trial Request message indicating the expected flight plan acceptability and, where practicable, applicable restrictions and constraints.
   Filed Flight Plan (eFPL)	A flight plan (to be) submitted as a request for air traffic services.
   Filing Status	A response to a validated eFPL message indicating the flight plan acceptability.
   Flight Plan Update	An update to the information contained in a previously submitted flight plan.
   Flight Cancellation	An instruction to cancel and remove a previously submitted flight plan.
   Flight Data Request	A query for flight plan or search and rescue information for a particular flight.
   Flight Data Response	A response to a validated Flight Data Request message, which includes the requested data.
   Flight Departure	A notification that a flight has departed.
   Flight Arrival	A notification that a flight has landed.

2. The Flight Information Exchange Model (FIXM) provides individual exchange schema for each of the FF-ICE messages.
3. Further details on the format, fields and content are provided in the NM B2B Reference Manual and the FIXM User Manual.

1.4.4   FF-ICE Requirements

1. General air traffic, operating under IFR must submit eFPLs using the FF-ICE services provided by NM, instead of FPL messages.
2. For all operators an eFPL message shall include, as a minimum (civil aircraft operating as general air traffic fully under IFR have additional requirements):
   1. the GUFI
   2. the operator flight plan version
   3. the flight data items required for FPLs as prescribed by the provisions in ICAO Annex 2 Section 3.3.2, ICAO Doc 4444 PANS-ATM Appendix 2 and this AIP Section XXX(States to amend as necessary).
3. Civil aircraft operating as general air traffic fully under IFR are additionally required to include the following in their eFPL:
   1. Expanded route and 4D trajectory
   2. Flight specific performance data consisting of performance climb and descent profiles and climb and descent speed schedules.
   3. Estimated aircraft take-off mass
4. For state aircraft operating as general air traffic fully under IFR and general air traffic operating under mixed IFR and VFR, the inclusion of items 3) a., b. and c. in eFPLs is optional.
5. Details on the expression of route/trajectory information in an FF-ICE flight plan are provided in the EUROCONTROL Network Manager IFPS Users Manual. When providing a trajectory in an FF-ICE flight plan, the full trajectory from aerodrome of departure to aerodrome of destination must be provided.
6. The operator, or its designated representative, is required to generate and allocate a GUFI to its FF-ICE flight plan. The provision of the GUFI is mandatory when using the filing service and the notification service.
7. The operator flight plan version number is a mandatory element when submitting eFPLs and any subsequent updates. The version number shall be incremented by the operator or their designated representative with every update to the flight plan.

1.4.5   FF-ICE Flight Planning Procedures

1. Submission, update and cancellation of FF-ICE Flight Plans:
   1. FF-ICE flight plans are submitted, updated and cancelled using the FF-ICE filing service.
   2. Upon processing of an FF-ICE flight plan submission or update, NM provides feedback via a submission response and filing status. In the case of an FF-ICE flight plan cancellation, NM provides feedback via a submission response only.
2. Use of the FF-ICE Trial Service:
   1. The trial service is initiated through the submission of a trial request.
   2. Upon processing of an FF-ICE trial request, NM provides feedback via a submission response and a trial response.
3. Use of the FF-ICE Flight Data Request Service:
   1. The use of the FF-ICE flight data request service enables users to request:
   1. A copy of accepted eFPLs
   2. A copy of supplementary flight plan data
   3. A copy of the latest filing status for the flight
   4. The submission response status
4. The notification service is used to enable users to transmit departure and arrival notification information to NM.
5. The data publication service is used to enable subscribers to obtain information about flights relevant to their operations.
6. FF-ICE flight plan re-evaluation:
   1. NM performs re-evaluation of FF-ICE flight plans to determine whether flight plans remain in compliance with published restrictions or ATM measures that that may have been applied or modified since the flight plan was last evaluated.
   2. The IFPS performs re-evaluation of eFPLs in the same way that it revalidates FPLs/IFPLs, with all valid flight plans subjected to the same process, same criteria and same possible outcome.
   3. The re-evaluation process applies to all processed eFPLs that received an ACK submission status and ACCEPTABLE filing status.
   4. Operators should make use of the NM B2B Publish/Subscribe services that will provide updates to the eFPL’s filing status, to maintain awareness of the re-evaluation results.
7. Further details on the NM implementation and provision of FF-ICE services and related procedures are provided in the NM IFPS Users Manual.

1.4.6   Further Information

1. Further information on FF-ICE, the NM implementation and associated procedures can be found in the following:
   1. EUROCONTROL FF-ICE webpage https://eurocontrol.int/ffice
   2. EUROCONTROL Network Manager IFPS Users Manual https://www.eurocontrol.int/publication/ifps-users-manual
   3. EUROCONTROL NM B2B Reference Manual
   4. European SWIM Registry https://eur-registry.swim.aero/home
   5. FIXM User Manual https://docs.fixm.aero/#/
2. The EUROCONTROL Network Manager will provide a flight plan translation service for the FIRs/UIRs in the IFPZ where FF-ICE/R1 is not mandated and as transition arrangements until full implementation by the concerned states.