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 within the Budapest FIR under IFR above 9 500 FT ALT shall be equipped with, as a minimum, RNAV equipment meeting RNAV 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 RNAV5 an aircraft is unable either to enter the airspace designated in ICAO DOC 7030/5, EUR Regional Supplementary Procedures, or continue operations in accordance with the current ATC clearance, a revised clearance shall, whenever possible, be obtained by the pilot.
  3. Subsequent ATC 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 RNAV 5, which is detected before departure from an aerodrome, and 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 the 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 ATC, Item 18 of the flight plan shall contain STS/RNAV INOP.
  5. For such aircraft experiencing a failure or degradation of the RNAV system below RNAV 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 ATC unit shall inform the receiving ATC unit by supplementing the ATC message verbally with the phrase ”RNAV UNSERVICEABLE” after the call sign of the aircraft concerned.
    • When a verbal co-ordination process is being used, the sending ATC 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 the ATC frequency is established.
1.3   Minimum flight altitudes

The MOCAs are depicted on chart ENR 6-LHCC-ERC have been determined so as to ensure at least 1 000 FT vertical clearance above the highest obstacle.

Except when necessary for take-off or landing an IFR flight shall not be flown lower than:

    • over high terrain or in mountainous areas at a level which is at least 2 000 FT (600 M) above
    • elsewhere (over a flat terrain) at a level which is at least 1 000 FT (300 M)

above the highest obstacle located within eight KM of the estimated position of the aircraft or at the 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 IFR to compliance with VFR 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 IFR when operated within or above the EUR RVSM airspace.

Therefore, flights operating as GAT within the Budapest FIR at or above FL 290, as described in ENR 2.1, shall be conducted in accordance with the IFR.

2.   Rules applicable to IFR flights 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 operations 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 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 FIC.

Identically VFR flights operating en route above 4 000 FT shall also maintain continuous listening watch on the appropriate radio frequency of the FIC.

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 by more than 5 KM;
  • if an estimated time over the FIR boundary is different by + 5 minutes from the one communicated to the FIC earlier;
  • if it 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 during period 0500 - 2300 (0400-2200) from the ground level9500 FT AMSL to FL 660 in the airspace encompassed by the lateral limits of the Budapest FIR (LHCC FIR) including the areas where responsibility for provision of ATS have been delegated for Budapest ACC.CTA.
Operations within the uncontrolled airspace of the Budapest FIR, the route planning requirements pertaining to HUFRA shall be applied. See ENR 4.4-1
During period 2300 - 0500 (2200-0400) the free route operation is extended across the border of the Budapest FIRCTA and the Bucharest FIRCTA (N-FRAB - Night Free Route Airspace between the Budapest and Bucharest FIRCTAs).
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-1 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-1. 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) during period 0500 - 2300 (0400-2200) is not allowed. Entry and exit from the HUFRA shall be planned using the published FRA entry and FRA exit points only. During period of the HUFRA and the N-FRAB cross-border operations between 2300 - 0500 (2200-0400) cross-border DCTs are allowed. See ENR-2.2.
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-1 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-1. 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 shall comply with the following procedures:
AirportWorking timeMandatory Segment / PointMandatory Exit point (X)Flight Plan examples
(Item 15)
Remark
LHBP0500-2300NALAG - RIGSAKEKED, LONLA, GEMTO, KARIL, BADORNALAG DCT RIGSA DCT HUFRA (X) 
LHBP2300-0500NALAG - RIGSAN-FRAB (X)NALAG DCT RIGSA DCT N-FRAB (X) 
LHBP0500-2300NORAHNARKA, BUDOPNORAH DCT HUFRA (X) 
LHBP2300-0500NORAHN-FRAB (X)NORAH DCT N-FRAB (X) 
LHBP0500-2300ERLOS - MAVIRTEGRI, INVEDERLOS DCT MAVIR DCT HUFRA (X)Above FL135
LHBP2300-0500ERLOS - MAVIRN-FRAB (X)ERLOS DCT MAVIR DCT N-FRAB (X)Above FL135
LHBPH24ERLOS - MAVIRKEROPERLOS DCT MAVIR DCT KEROPBelow FL135
LHBPH24PUSTAKEROP, VEBAL, KOPRY, DIMLO, GOTARPUSTA DCT (X) 
LHBPH24GILEPSUNIS, ARSIN, ABETI, BEGLAGILEP DCT (X) 
LHBPH24TORNONATEXTORNO DCT NATEXOnly for city pair LHBP - LOWW
LHBPH24TORNOXOMBATORNO DCT XOMBAOnly for city pair LHBP - LZIB
LOWWH24ALAMU - EPARIKEKED, LONLA, GEMTOALAMU DCT EPARI DCT KEKED 
LOWW0500-2300ALAMU - EPARIKARIL, BADOR, NARKA, BUDOP, TEGRIALAMU DCT EPARI DCT HUFRA (X) 
LOWW2300-0500ALAMU - EPARIN-FRAB (X)ALAMU DCT EPARI DCT N-FRAB (X) 
LOWWH24STEIN - SIRDULONLA, GEMTOSTEIN DCT SIRDU DCT LONLA 
LOWW0500-2300STEIN - SIRDUKARIL, BADOR, NARKA, BUDOP, TEGRISTEIN DCT SIRDU DCT HUFRA (X) 
LOWW2300-0500STEIN - SIRDUN-FRAB (X)STEIN DCT SIRDU DCT N-FRAB (X) 
LOWWH24SASALBABIT, VEBAL, KOPRYSASAL DCT HUFRA (X) 
LOWW0500-2300SASALINVEDSASAL DCT HUFRA (X) 
LOWW2300-0500SASALN-FRAB (X)SASAL DCT N-FRAB (X) 
LZIBH24VAMOG - SIRDUVEBAL, KOPRY, DIMLO, GOTARVAMOG DCT SIRDU DCT (X) 
LZIBH24VAMOG - GITASKEKED, LONLA, GEMTO, KEROP, BABITVAMOG DCT GITAS DCT BABIT 
LZIB0500-2300VAMOG - GITASKARIL, BADOR, NARKA, BUDOP, TEGRI, MOPUG, INVEDVAMOG DCT GITAS DCT HUFRA (X) 
LZIB2300-0500VAMOG - GITASN-FRAB (X)VAMOG DCT GITAS DCT N-FRAB (X) 
LZIBH24ERGOMLONLA, GEMTOERGOM DCT GEMTO 
AirportWorking timeMandatory Segment / PointMandatory Exit point (X)Flight Plan examples
(Item 15)
Remark
LZIB0500-2300ERGOMKARIL, BADOR, NARKA, BUDOP, TEGRIERGOM DCT HUFRA (X) 
LZIB2300-0500ERGOMN-FRAB (X)ERGOM DCT N-FRAB (X) 
4.4.4.2  Flight Planning of any arriving flights shall comply with the following procedures
Working timeMandatory Entry point (E)Mandatory Segment / PointAirportFlight Plan examples (Item 15)Remark
H24KARILRIGSA - GELKA - JBRLHBPKARIL DCT RIGSA DCT GELKA DCT JBR 
0500-2300KEKED, LONLA, KARILRIGSA - GELKA - JBRLHBPHUFRA (E) DCT RIGSA DCT GELKA DCT JBR 
2300-0500N-FRAB (E)RIGSA - GELKA - JBRLHBPN-FRAB (E) DCT RIGSA DCT GELKA DCT JBR 
H24DEMOPJBRLHBPDEMOP DCT JBR 
H24NARKA, MEGIK, BUDOP, DEGET, MOPUG,ABONYLHBPHUFRA (E) DCT ABONY 
2300-0500N-FRAB (E)ABONYLHBPN-FRAB (E) DCT ABONY 
H24PARAKABONYLHBPPARAK DCT ABONY 
H24VEBAL, KOPRY, DIMLO, GOTARVEBOSLHBP(E) DCT VEBOS 
H24KEKED (and for DEP LHBP via TORNO SID)TORNO - NATEXLOWW(E) DCT TORNO DCT NATEX 
H24KARIL, NARKA, MEGIK, BUDOP, DEGET, MOPUGBALUX - TORNO - NATEXLOWWKARIL DCT BALUX DCT TORNO DCT NATEX 
0500-2300LONLA, PARAKBALUX - TORNO - NATEXLOWWHUFRA (E) DCT BALUX DCT TORNO DCT NATEX 
2300-0500N-FRAB (E)BALUX - TORNO - NATEXLOWWN-FRAB (E) DCT BALUX DCT TORNO DCT NATEX 
H24KARIL, NARKA, MEGIK, BUDOP, DEGET, MOPUGBALUX - XOMBALZIBKARIL DCT BALUX DCT XOMBA 
0500-2300KEKED, LONLA, NARKA, MEGIK, PARAKBALUX - XOMBALZIBHUFRA (E) DCT BALUX DCT XOMBA 
2300-0500N-FRAB (E)BALUX - XOMBALZIBN-FRAB (E) DCT BALUX DCT XOMBA 
H24TONDO, VEBAL, KOPRY, DIMLOXOMBALZIB(E) DCT XOMBA 
4.4.4.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.