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, and Commission Regulation (EU) No 965/2012 of 5 October 2012 laying down technical requirements and administrative procedures related to air operations pursuant to Regulation (EC) No 216/2008 of the European Parliament and of the Council.
Aircraft, other than State aircraft, operating within the Budapest FIR under IFR shall be equipped with, as a minimum, RNAV equipment meeting RNAV 5 (B-RNAV) 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 and EASA AMC 20-4, Airworthiness Approval and Operational Criteria for the Use of Navigation Systems in European Airspace Designated for Basic RNAV Operations.
Requirements for VFR flights related to VHF 8.33 KHZ channel spacing radio equipage are stated in GEN 1.5.
The AMAs 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:
above the highest obstacle located within 8 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.
The minimum flight altitude for IFR flights in uncontrolled airspace is 4 000 FT (1 200 M) AMSL.
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 by including the statement „CANCELLING MY IFR FLIGHT” within the radio message and communicate thereto the changes to be made to its flight plan.
When an aircraft operating under IFR is flown in or encounters visual meteorological conditions it shall not cancel its IFR flight unless it is anticipated, and intended, that the flight will be continued for a reasonable period of time in uninterrupted visual meteorological conditions.
As specified in the ICAO EUR Regional Supplementary Procedures (Doc 7030/5 - EUR), Chapter 1, paragraph 1.2.1.2, flights shall be conducted in accordance with IFR when operated within or above the EUR RVSM airspace. RVSM shall be applicable in the volume of airspace between FL 290 and FL 410 (ICAO EUR Supplementary Procedures (Doc 7030/5 – EUR), Chapter 4, paragraph 4.2.1).
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. (See also ENR 1.4.)
In case the route of a non-RVSM approved aircraft is planned within the lateral limits of RVSM airspace the flight shall be cleared to a flight level below FL 290.
Formation flights shall not be performed by civil aircraft in RVSM airspace. Operators of formation flights with either State aircraft operating as GAT, or non-RVSM approved aircraft, shall acquire ATS clearance for special operations in case the requested flight level is FL 290 or above.
Aircraft in EUR RVSM airspace shall report to ATC as soon as possible:
Prior to and during RNAV or Free Route flights operators shall verify the correct functioning of the aircraft RNAV systems. This includes:
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.
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” or „R” in Item 10 of the flight plan. Since such flights require special ATC handling, Item 10 shall contain the designator „Z” and Item 18 of the flight plan shall contain „NAV/RNAVINOP”.
For such aircraft experiencing a failure or degradation of the RNAV system below RNAV 5, 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.
During the en route portion of the flight, the cruising levels selected as prescribed in point 2 above, shall be maintained.
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.
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:
The SEENFRA encompasses the FRAs within Budapest CTA, București CTA, Sofia CTA and Bratislava CTA. For cross-border operations planning within SEENFRA see ENR 1.3 section 4.4 Flight Planning (Item 15).
Direction of Cruising levels within HUFRA / SEENFRA | ||
FLs over FRA entry point | FLs over FRA exit point | FLs inside HUFRA / SEENFRA |
EVEN | EVEN | FLs for all DCT segments |
ODD | ODD | FLs for all DCT segments |
EVEN | ODD | A change from EVEN to ODD FLs must be planned inside HUFRA / SEENFRA |
ODD | EVEN | A change from ODD to EVEN FLs must be planned inside HUFRA / SEENFRA |
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.
Airport | Working time | Mandatory Segment / Point | Mandatory Exit point (X) | Flight Plan examples (Item 15) | Remark |
---|---|---|---|---|---|
LHBP | 0500-2300 (0400-2200) | NALAG - RIGSA | KEKED, LONLA, GEMTO, KARIL, BADOR | NALAG DCT RIGSA DCT BADOR | |
LHBP | 2300-0500 (2200-0400) | NALAG - RIGSA | See ENR 1.3 section 4.4 Flight Planning (Item 15) | ||
LHBP | 0500-2300 (0400-2200) | NORAH | NARKA, BUDOP | NORAH DCT BUDOP | |
LHBP | 2300-0500 (2200-0400) | NORAH | See ENR 1.3 section 4.4 Flight Planning (Item 15) | ||
LHBP | 0500-2300 (0400-2200) | ERLOS - MAVIR | TEGRI, INVED | ERLOS DCT MAVIR DCT INVED | Above FL 135 |
LHBP | 2300-0500 (2200-0400) | ERLOS - MAVIR | Above FL 135 See ENR 1.3 section 4.4 Flight Planning (Item 15) | ||
LHBP | H24 | PUSTA | KEROP, VEBAL | PUSTA DCT KEROP | |
LHBP | H24 | GILEP - ZOLKU | SUNIS, ARSIN, ABETI, BEGLA | GILEP DCT ZOLKU DCT BEGLA | |
LHBP | H24 | TORNO | NATEX | TORNO DCT NATEX | Only for city pair LHBP - LOWW |
LHBP | H24 | TORNO | XOMBA | TORNO DCT XOMBA | Only for city pair LHBP - LZIB |
LOWW | 0500-2300 (0400-2200) | ALAMU - EPARI | KEKED, LONLA, GEMTO | ALAMU DCT EPARI DCT KEKED | |
LOWW | 0500-2300 (0400-2200) | ALAMU - EPARI | KARIL, BADOR, NARKA, BUDOP, TEGRI, GEMTO, LONLA, KENIN, KEKED | ALAMU DCT EPARI DCT KEKED | |
LOWW | H24 | STEIN - NOHAT | VEBAL, KOPRY, NEKIN | STEIN DCT NOHAT DCT KORPY | |
LOWW | H24 | STEIN | DIMLO | STEIN DCT DIMLO | |
LOWW | H24 | ARSIN - NALOX | BABIT, BAREB | ARSIN DCT NALOX DCT BABIT | |
LZIB | H24 | VAMOG - SIRDU | KOPRY, BABIT, NEKIN | VAMOG DCT SIRDU DCT KOPRY | |
LZIB | 0500-2300 (0400-2200) | ERGOM | LONLA, GEMTO | ERGOM DCT GEMTO | |
LZIB | 0500-2300 (0400-2200) | ERGOM | KARIL, BADOR, NARKA, BUDOP, TEGRI | ERGOM DCT BADOR |
Working time | Mandatory Entry point (E) | Mandatory Segment / Point | Airport | Flight Plan examples (Item 15) | Remark |
---|---|---|---|---|---|
H24 | KARIL | RIGSA - GELKA - JBR | LHBP | KARIL DCT RIGSA DCT GELKA DCT JBR | |
H24 | PITOK | GELKA - JBR | LHBP | PITOK DCT GELKA DCT JBR | |
0500-2300 (0400-2200) | KEKED, LONLA, KARIL | RIGSA - GELKA - JBR | LHBP | KEKED DCT RIGSA DCT GELKA DCT JBR | |
2300-0500 (2200-0400) | RIGSA - GELKA - JBR | LHBP | See ENR 1.3 section 4.4 Flight Planning (Item 15) | ||
H24 | DEMOP | JBR | LHBP | DEMOP DCT JBR | |
H24 | NARKA, MEGIK, BUDOP, DEGET, MOPUG, | ABONY | LHBP | NARKA DCT ABONY | |
2300-0500 (2200-0400) | ABONY | LHBP | See ENR 1.3 section 4.4 Flight Planning (Item 15) | ||
H24 | PARAK | ABONY | LHBP | PARAK DCT ABONY | |
H24 | DIMLO, GOTAR | SIRDU - OGVUN - VAJDI - VEBOS | LHBP | DIMLO DCT SIRDU DCT OGVUN DCT VAJDI DCT VEBOS | |
H24 | KOPRY | RAKFA - VEBOS | LHBP | KOPRY DCT RAKFA DCT VEBOS | |
H24 | KEKED (and for DEP LHBP via TORNO SID) | TORNO - NATEX | LOWW | KEKED DCT TORNO DCT NATEX | |
H24 | KARIL, NARKA, MEGIK, BUDOP, DEGET, MOPUG | BALUX - TORNO - NATEX | LOWW | KARIL DCT BALUX DCT TORNO DCT NATEX | |
0500-2300 (0400-2200) | LONLA, PARAK | BALUX - TORNO - NATEX | LOWW | LONLA DCT BALUX DCT TORNO DCT NATEX | |
2300-0500 (2200-0400) | BALUX - TORNO - NATEX | LOWW | See ENR 1.3 section 4.4 Flight Planning (Item 15) | ||
H24 | LONLA, PARAK | BALUX - XOMBA | LZIB | LONLA DCT BALUX DCT XOMBA | |
H24 | TONDO, KOPRY | VEBOS - XOMBA | LZIB | VEBAL DCT VEBOS DCT XOMBA | |
0500-2300 (0400-2200) | KEKED, KARIL, BADOR, NARKA, MEGIK, BUDOP, DEGET, MOPUG | BALUX - XOMBA | LZIB | NARKA DCT BALUX DCT XOMBA | |
2300-0500 (2200-0400) | BALUX - XOMBA | LZIB | See ENR 1.3 section 4.4 Flight Planning (Item 15) |