ENR 1.3  INSTRUMENT FLIGHT RULES

1.   Rules applicable to all IFR flights

1.1   Aircraft equipment

Commercial air transport aircraft operating in the airspace of Hungary have to adhere to the provisions of ICAO Annex 6 - Operation of Aircraft - Part 1, Chapter 6 - Aeroplane Instruments, Equipment and Flight Documents - and Chapter 7 - aeroplane Communication and Navigation Equipment.

Aircraft, other than state aircraft, operating on the ATS routes within Budapest FIR under instrument flight rules (IFR) above 9500 FT ALT shall be equipped with, as a minimum, RNAV equipment meeting RNPRNAV 5 in accordance with the requirements set out in of ICAO Doc 7030/5 Regional Supplementary Procedures (EUR).

Acceptable means of compliance are set out in the JAA Technical Guidance Leaflet No. 2 rev. 1.

1.2   B-RNAV Contingency Procedures

For B-RNAV equipped aircraft experiencing temporary failure or degradation of the RNAV system below RNP 5, the following procedures apply:

  1. Correct operation of the aircraft RNAV system below RNP 5, the following procedures apply:
    • the routing is in accordance with the clearance; and
    • the aircraft navigation accuracy meets RNP 5
  2. If as a result of a failure or degradation of the RNAV system below RNPRNAV5 an aircraft is unable either to enter the airspace designated in ICAO DOC 7030/5, EUR Regional Supplementary Procedures, Para 15.2.1, or continue operations in accordance with the current air traffic control clearance, a revised clearance shall, whenever possible, be obtained by the pilot.
  3. Subsequent air traffic control action in respect of that aircraft will be dependent upon the nature of the reported failure and the overall traffic situation. Continued operation in accordance with the current ATC clearance may be possible in many situations. When this cannot be achieved, a revised clearance may be required to revert to VOR/DME navigation. ATC may also provide the aircraft with radar vectors until the aircraft is capable of resuming its own navigation.
  4. In case of a failure or degradation of the RNAV system below RNPRNAV 5, which is detected before departure from an aerodrome where it is not practicable to effect a repair, the aircraft concerned should be permitted to proceed, as directly as possible, to the nearest suitable aerodrome where repair can be made. When granting clearance to such aircraft, ATC should take into consideration, the existing or anticipated traffic situation and may have to modify the time of departure, flight level or route of the intended flight. Subsequent adjustments may become necessary during the course of flight. Operators of such aircraft, where a failure or degradation is detected before departure, shall not insert designators „S” ore” in Item 10 of the flight plan. Since such flights require special handling by air traffic control, Item 18 of the flight plan shall contain STS/RNAV INOP.
  5. For such aircraft experiencing a failure or degradation of RNAV system below RNPRNAV 5, the following ATC procedures are applicable:
    • In case of automated messages not containing the information provided in Item 18 of the flight plan, the sending air traffic control unit shall inform the receiving air traffic control unit supplementing the ATC message verbally with the phrase „RNAV UNSERVICABLE” after the call sign of the aircraft concerned.
    • When a verbal co-ordination process is being used, the sending air traffic control unit shall include the phrase „RNAV UNSERVICABLE” at the end of the message.
    • The phrase „UNABLE RNAV DUE EQUIPMENT” shall be included by the pilot immediately following the aircraft call sign, whenever initial contact on air traffic control frequency is established.
1.3   Minimum flight altitudes

The minimum flight altitudes on the ATS routes listed in andare depicted on chart ENR 6-LHCC-ERC have been determined so as to ensure at least 1000 feet vertical clearance above the highest obstacle. within 10 NM on each side of the centre line of the route.

Except when necessary for take-off or landing or when specifically authorized by the appropriate aeronautical authority an IFR flight shall not be flown lower than:

    • over high terrain or in mountainous areas at a level which is at least 2000 FT (600 m) above
    • elsewhere (over a flat terrain) at a level which is at least 1000 FT (300 m)

above the highest obstacle located within 8 km of the estimated position of the aircraft or at the minimum safe sector altitude (MSA) established for the area concerned.

When determining the flight altitude the navigational accuracy which can be achieved on the relevant route segment shall be taken into account, having due regard to the navigational facilities available on the ground and on board of the aircraft.

1.4   Change from IFR flight to VFR flight

An aircraft electing to change the conduct of its flight from compliance with the instrument flight rules to compliance with the visual flight rules shall notify the appropriate ATS unit that the IFR flight plan is cancelled.

1.5   RVSM operation

As specified in the ICAO EUR Regional Supplementary Procedures (Doc 7030/4 - EUR), Chapter 1, paragraph 1.1.1.2, flights shall be conducted in accordance with Instrument Flight Rules when operated within or above the EUR RVSM airspace.

Therefore, flights operating as General Air Traffic (GAT) within Budapest FIR at or above FL 290, as described in ENR 2.1, shall be conducted in accordance with the Instrument Flight Rules.

2.   Rules applicable to IFR flight within controlled airspace

3.   Rules applicable to IFR flights outside controlled airspace

3.1   Cruising levels

Flight departing from non-controlled aerodromes for en-route flights may start operation only on possession of a filed flight plan, except when a special airspace portion has been approved for the individual flight.

During the en-route portion of the flight the cruising levels selected as prescribed in para 2 above shall be maintained.

Outside controlled airspace and TRA IFR flights shall not be conducted at an indicated airspeed (IAS) exceeding 250 KTS (460 km/h).

3.2   Communications

All IFR flights leaving the CTR or TIZ shall maintain a continuous listening watch and establish two-way radio communications on the appropriate radio frequency of the Flight Information Centre (FIC).

Identically also the VFR flights operating enroute within the ADIZabove 4000 FT shall maintain radio communication continuous listening watch on the appropriate radio frequency of the FIC., except the agricultural aerial works.

3.3   Position reports

Aircraft shall make position reports at designated reporting point (if any) and at other occasions as instructed by FIC, but at least every 15 minutes.

Irrespective of the applicable rules the FIC shall be notified:

  • if an aircraft is compelled to divert from its flight plan route more than 5 km;
  • if an estimated time over the FIR boundary is different with + 5 minutes from the one communicated to FIC earlier;
  • if intends to change from IFR to VFR or vice versa;
  • if departing from a non AFIS aerodrome;
  • of an approach to land outside an aerodrome.

4.   FREE ROUTE AIRSPACE GENERAL PROCEDURES

4.1   Area of application
4.1.1  HUFRA is available H24 from the ground level to FL 660 in the airspace encompassed by the lateral limits of Budapest FIR (LHCC FIR) including the areas where responsibility for provision of ATS have been delegated for Budapest ACC.
4.2   Flight Procedures
4.2.1   General
4.2.1.1  Within HUFRA, aircraft other than State aircraft, shall comply with the aircraft equipment requirements published in GEN 1.5
4.2.1.2  Within HUFRA airspace, users will be able to plan user-preferred trajectories using significant points - five-letter name-codes - and/or en-route radio navigation aids published in ENR 4.4 and ENR 4.1, respectively. Segments between the significant points shall be defined by means of DCT (Direct) instructions.
4.2.1.3  Within HUFRA, significant points are considered as FRA entry, FRA exit, FRA intermediate, FRA arrival and FRA departure points, as described in ENR 4.4. All en-route radio navigation aids published in ENR 4.1 are considered as FRA intermediate points.
4.2.1.4  Within HUFRA, there is no restriction on the maximum DCT distance.
4.2.2   Overflying traffic
4.2.2.1  Overflight traffic shall be planned directly between FRA entry, FRA exit and FRA intermediate points.
4.2.2.2  An exception to the rule is made during the initial HUFRA implementation phase when the DCT segments which are not available are announced in accordance with paragraph 4.5 below.
4.2.2.3  Traffic proceeding inbound or outbound airports located in close vicinity of LHCC FIR shall be planned in accordance with 4.2.2.1 above and paragraph 4.4 below also using the relevant FRA arrival and FRA departure points. Airports in close vicinity of LHCC FIR are considered to be: LOWW and LZIB.
4.2.3   Access to/from airports and terminal airspace
4.2.3.1  Flights arriving at or departing from airports located within LHCC FIR are eligible for free route operations and shall be planned in accordance with the paragraphs below.
4.2.3.2  In case of departing flight from an airport where standard instrument departures procedures (SIDs) are published, RNAV-capable departing flights shall be planned directly from the SID final waypoint to the HUFRA exit point.
4.2.3.3  In case of arriving flight to an airport where standard instrument arrival procedures (STARs), or transition procedures are published, RNAV-capable arriving flights shall be planned directly from the HUFRA entry point to the STAR initial waypoint or transition procedure.
4.2.3.4  The SID/STAR or transition procedures shall not be indicated in the filed route of the FPLs.
4.2.3.5  Where SIDs are not published, the flights shall be planned DCT to the HUFRA exit point.
4.2.3.6  Where STARs are not published, the flights shall be planned DCT from the HUFRA entry point to the airport.
4.2.4   Cross-Border Applications
4.2.4.1  The planning of DCT segments across the HUFRA borders (cross border DCT) is not allowed. Entry and exit from HUFRA shall be planned using the published FRA entry and FRA exit points only.
4.2.4.2  The planning of DCT segments that are partially outside the lateral limits of HUFRA (multiple re-entry segments) is not allowed.
4.2.4.3  The planning of DCT segments closer than 3 NM to the HUFRA border is not allowed.
4.3   Airspace Reservation - Special Areas
4.3.1   Re-routing Special Areas
4.3.1.1  Flights may be planned through active TRAs or danger areas.
4.3.2   Promulgation of route extension
4.3.2.1  In the case where there is no availability to cross the active reserved area, occasionally:
  1. a flight may be instructed to proceed to one of the five significant points which are published in ENR 4.4 as an intermediate point, with the remark "in case TRA 32/33 active”;
  2. tactical radar vectoring may be applied in order to ensure an additional safety margin between active TRA boundaries and flight trajectories. It is expected that the average extension to be considered by aircraft operators will be approximately 5 NM and in exceptional circumstances, not more than 10 NM.
4.3.2.2  Restrictions on the maximum DCT distance inserted in the flight plan will not be enforced.
4.4   Flight Planning (Item 15)
4.4.1   General
4.4.1.1  In case of more than 30 minutes of flying time or 200 NM (370 KM), an intermediate point may be inserted at which a change of speed, flight level, track, or flight rules are planned. There is no restriction on the number of intermediate points that may be used.
4.4.1.2  The use of a point entered in latitude and longitude for a change of speed or flight level shall be avoided.
4.4.2   ATS Route Network
4.4.2.1  The ATS route network within LHCC FIR will be withdrawn.
4.4.2.2  Within HUFRA no reference shall be made in the flight plan to ATS routes.
4.4.3   Flight Level Orientation Scheme
4.4.3.1  Cruising levels must be planned in accordance with the information provided in the column "Remarks/Usage" in ENR 4.4. The direction of cruising levels (EVEN or ODD) must be chosen depending on the direction of the flight level required over the FRA entry and FRA exit points as described in the following table:
Direction of Cruising levels within HUFRA
FLs over FRA entry pointFLs over FRA exit pointFLs inside HUFRA
EVENEVENFLs for all DCT segments
ODDODDFLs for all DCT segments
EVENODDA change from EVEN to ODD FLs must be planned inside HUFRA
ODDEVENA change from ODD to EVEN FLs must be planned inside HUFRA

Note: ODD is the direction of IFR cruising levels with a magnetic track between 000° and 179° while EVEN is the direction of IFR cruising levels with a magnetic track between 180° and 359°, as described in the table of cruising levels in ENR 1.7.

4.4.3.2  Cruising levels must also be planned in accordance with the adjacent ATS route network Flight Level Orientation Scheme.
4.4.4   Flight Planning procedures for departing and arriving flights from/to significant airports
4.4.4.1  Flight Planning of any departing flights from LHBP shall comply with the following procedures:
AirportSID End PointHUFRA Mandatory Intermediate PointHUFRA (X) Exit PointFlight Plan (Item 15)Remark
LHBPNALAGRIGSAKEKED, LONLA, GEMTO, KARIL, BADORNALAG DCT RIGSA DCT (X)
NORAHNARKA, BUDOPNORAH DCT (X)
ERLOSMAVIRTEGRI, MOPUG, INVEDERLOS DCT MAVIR DCT (X)
KEROPERLOS DCT MAVIR DCT KEROPBelow FL135
PUSTAKEROP, VEBAL, KOPRY, DIMLO, GOTARPUSTA DCT (X)
GILEPSUNIS, ARSIN, ABETI, BEGLAGILEP DCT (X)
TORNONATEXTORNO DCT NATEXOnly for city pair LHBP - LOWW
TORNOXOMBATORNO DCT XOMBAOnly for city pair LHBP - LZIB
4.4.4.2  Flight Planning of any arriving flights to LHBP shall comply with the following procedures:
HUFRA
(E) Entry Point
HUFRA Mandatory Intermediate PointTransition Initial PointAirportFlight Plan (Item 15)Remark
KEKED, LONLA, GEMTO, KARILRIGSA - GELKAJBRLHBP(E) DCT RIGSA DCT GELKA DCT JBR
DEMOPJBRDEMOP DCT JBR
NARKA, MEGIK, BUDOP, DEGET, MOPUG, PARAKABONY(E) DCT ABONY
VEBAL, KOPRY, DIMLO, GOTARVEBOS(E) DCT VEBOS
STEINSTEIN not available for ARR LHBP
4.4.5   Flights arriving at or departing from airports located in close vicinity of LHCC FIR
4.4.5.1  Flight Planning of any departing flight shall comply with the following procedures:
AirportHUFRA
(E) Entry Point
HUFRA
Mandatory Intermediate Point
HUFRA
(X) Exit Point
Flight Plan (Item 15)Remark
LOWWALAMUEPARIKEKED, LONLA, GEMTO, KARIL, BADOR, NARKA, BUDOP, TEGRIALAMU DCT EPARI DCT (X)
STEINSIRDUKEKED, LONLA, GEMTO, KARIL, BADOR, NARKA, BUDOP, TEGRISTEIN DCT SIRDU DCT (X)
SASALINVED, BABIT, VEBAL, KOPRYSASAL DCT (X)
LZIBVAMOGSIRDUVEBAL, KOPRY, DIMLO, GOTARVAMOG DCT SIRDU DCT (X)
VAMOGGITASKEKED, LONLA, GEMTO, KARIL, BADOR, NARKA, BUDOP, TEGRI, MOPUG, INVED, KEROP, BABITVAMOG DCT GITAS DCT (X)
ERGOMLONLA, GEMTO, KARIL, BADOR, NARKA, BUDOP, TEGRIERGOM DCT (X)
4.4.5.2  Flight Planning of any arriving flight shall comply with the following procedures:
HUFRA
(E) Entry Point
HUFRA
Mandatory Intermediate Point
Transition Initial PointAirportFlight Plan (Item 15)Remark
KEKED (and for DEP LHBP via TORNO SID)TORNONATEXLOWW(E) DCT TORNO DCT NATEX
LONLA, GEMTO, KARIL, NARKA, MEGIK, BUDOP, DEGET, MOPUG, PARAKBALUXNATEX(E) DCT BALUX DCT NATEX
KEKED, LONLA, GEMTO, KARIL, NARKA, MEGIK, BUDOP, DEGET, MOPUG, PARAKBALUXXOMBALZIB(E) DCT BALUX DCT XOMBA
TONDO, VEBAL, KOPRY, DIMLOXOMBA(E) DCT XOMBA
4.4.5.3  The other flights arriving at or departing from other airports located in close vicinity of LHCC FIR are considered as overflying traffic (see para 4.2.2.3 above).
4.5   Route Availability Document
4.5.1  All HUFRA constrains, exceptions and restrictions, if any will be published via the RAD and promulgated in accordance with ENR 1.10.