3.1   Taxi clearances

Crossing of the active RWY 13R/31L is only permitted with specific clearance. In the absence of a specific clearance to cross the active runway ahead, the aircraft shall not proceed beyond the relevant taxi holding point. Clearance for crossing the active runway is issued by Budapest Tower on 118.100 MHZ frequency.

3.2   Taxi procedures general

See TWY segments on chart AD2-LHBP-ADC

When low visibility procedures are in force, the same holding points shall be used.

Terminal 1:

Terminal 2:

Cargo Apron:

See TWY segments on Chart AD-2-LHBP PDC-1 and PDC-2

3.3   Taxi procedures for arriving aircraft

ATC expects arriving ACFT to vacate runways via the rapid exit TWYs. If unable to do so, notify Budapest Tower on 118.100 MHZ in advance or immediately after landing. Arrivals on RWY 13R to T1, use TWY B1 or A1. Restrictions on rapid exit TWYs J4, Y and Z will be provided by Budapest Tower with landing clearance. During Low Visibility Operations, pilots shall report RWY vacation to Budapest Tower on 118.100 MHZ.

After vacating the RWY, without further notice, pilots shall immediately contact Budapest Ground on 121.910 CH for detailed taxi instructions, if not otherwise instructed by ATC. Further taxiing to the designated stand is only allowed when cleared by Budapest Ground or Budapest Tower.

3.4   Taxi procedures for departing aircraft

At the stand, taxi clearance to the designated holding point of the runway will be given by Budapest Ground.

3.5   Operation of Mode S transponders when the aircraft is on the ground

A surface movement guidance and control system (ASMGCS), using Mode S multilateration operates at Budapest Liszt Ferenc International Airport.

Aircraft operators intending to use Budapest Liszt Ferenc International Airport shall ensure that the Mode S transponders are able to operate when the aircraft is on the ground.

Select “STBY”, when fully parked on the stand.

Whenever the aircraft is capable of reporting Aircraft Identification (i.e. callsign used in flight), the Aircraft Identification should also be entered from the request for push-back or taxi, whichever is earlier, through the FMS or the Transponder Control Panel.

Flight crew shall use the Aircraft Identification format, as defined by ICAO (e.g. SAS589, BAW869).

To ensure that the performance of systems based on SSR frequencies (including airborne TCAS units and SSR radars) is not compromised:

• When the aircraft is departing, TCAS should not be selected before receiving the clearance to line up
• When the aircraft is arriving, TCAS should be deselected after vacating the runway.

For aircraft taxiing without flight plan, Mode A code 2000 should be selected.

4.1   System description

The SAFEDOCK T2 system is a microprocessor controlled laser scanning device which directs an approaching aircraft to the terminal gate stopping position with the assistance of a real time display unit that is clearly visible from the cockpit.

../graphics/eAIP/LHBP_Docking_T2A.pdf

4.2   Docking procedure

1. Follow the taxi line to gate 31-36, 37-39 or 42-45.
2. Check correct aircraft type, the flashing arrows of direction and floating arrows (the system is activated and ready for the docking procedure).
3. When the aircraft has been detected by the system the floating arrows are replaced by the closing rate indicator.
   • Watch the yellow centre line indicator, the flashing arrow indicates the correct azimuth guidance.
   • Watch the flashing red arrows for required direction of turn.
4. When the aircraft is 12 M from the stop position, the closing rate indicating the remaining distance to the stop position is indicated by turning off one row per half metre.
5. If the docking speed of the aircraft is more than 4 KT, SLOW DOWN is displayed to allow for correct docking.
6. At the correct stop position all yellow closing rate indicator bars are switched off, the STOP sign is displayed and 2 red lights will be lit.
7. When the aircraft has parked correctly, the OK sign is displayed.
8. When the aircraft has overshot the stop position, the TOO FAR sign is displayed.

5.1   General

The functional testing of aircraft engines on the ground is subject to permission. The selection of the location and the time for the activity is dependent on the size category of the aircraft and the power of the engine test.

Engine power tests (on power levels higher than idle power) for up to ICAO code C aircraft must be performed at the engine test stand constructed for this purpose. Deviations from this are only permitted as detailed in section 5.4.

Engine power tests for aircraft larger than ICAO Code C may be performed at the location and with the conditions described in section 5.4.

The obstacle-free nature (FOD) and cleanliness of the area must be verified in all cases. In case of any issues, the Airport Operations Control Centre (AOCC airside controller: phone: (+361) 296-6914) must be notified.

The appropriate brake blocks must be provided for engine tests, and the presence of the hand-held fire extinguishers must be checked at the site.

Any surface pollution generated during engine testing must be reported to the AOCC.

Continuous two-way radio contact must be maintained with the unit competent in the area during engine testing.

The time periods specified in this section shall be interpreted as follows: all periods include the starting time of the period, but not its closing time.

5.2   Permitting procedure

Requests for engine power tests must be sent to the AOCC in advance, at least 24 hours prior to the planned time of the engine test. The AOCC confirms the approval of the request to the applicant.

Permission for actual engine start-up must be requested from the unit responsible for traffic management in the given area, by DRR radio (or air-to-air radio on the frequency of the competent unit in the given area), and the completion of the engine test must be reported to the same unit.

• Budapest APRON (122.440 MHZ): Terminal 1 and Terminal 2 Apron, Cargo Apron, Engine test stand, Apron AA, AL;
• Budapest GROUND (121.910 MHZ): B5 holding bay, taxiways outside of the terminal and technical aprons, runways.

The AOO service records the most important specifics of engine tests (e.g. beginning and end of test, aircraft type, name of the company performing the test, location, etc.) using the form “Engine test voucher”.

5.3   Engine tests at idle power

Engine tests at idle power may be performed at the following locations, with a maximum of one engine, for a maximum of 5 minutes, :

• On the stands of the Terminal 1 apron, with no exception of stands between 0600 - 2200 (0500-2100);
• On the stands of the Terminal 2 apron, and Cargo apron with no exception of stands without restriction in terms of the time of day;
• On the AA, AG, AL apron section, on the marked taxi lane, at the starting position marked at the apron exit point, between 0600 - 2200 (0500-2100);
• At the engine test stand (maximum wingspan 36 m) without restriction in terms of the duration of the test and number of engines are running between 0600 - 2200 (0500-2100).

5.4   Engine power tests

Engine power tests may only be performed at the following locations:

1. At the engine test stand established for aircraft up to ICAO code C, without restriction in terms of power, and duration of the test is between 0600 - 2200 (0500-2100);
2. If the engine test stand is not suitable for the performance of the test for whatever reason, the B5 holding bay or taxiway A9 may also be designated as a power test area, between 0800 - 1800 (0700-1700).

If engine power testing is necessary between 1800 - 2200 (1700-2100) or between 0600 - 0800 (0500-0700) at the locations listed in point 2 above, the prior written permission of the Ministry for Innovation and Technology, Civil Aviation Authority (CAA) must also be obtained separately at least 24 hours prior to the planned time of the engine test, and must be attached to the request, to be submitted to the AOCC. The compliance of the engine test with the contents of the authority permission is overseen and checked by the duty airside manager (DAM).

It is prohibited to perform engine power test between 2200 - 0600 (2100-0500) at the airport.

5.5   The operational rules of the engine test stand

The procedural rules for the operation of the engine test stand are outlined in Chapter XII. of the Airport Manual Volume II.

5.6   The fee payable for functional engine testing

Budapest Airport Zrt. may levy an area usage fee for testing in the areas where engine power testing may be performed.

6.1   Planning and authorisation of training flights

• On workdays between 2100 - 0500 (2000-0400);
• SAT, SUN and Public holidays between 1700 - 0700 (1600-0600).

Calibration flights may be executed on workdays and bank holidays between 0500 - 2100 (0400-2000).

providing the following data:

• Aircraft registration marks and call sign,
• Aircraft type,
• The nature and the planned time of the exercise,
• Contact details of pilot in command (preferably mobile phone number).

When requesting consent, the following information shall be provided to the AOCC:

• Aircraft registration marks and call sign,
• Aircraft type,
• The nature, the planned time and duration of the demonstration flight,
• Contact details of pilot in command (preferably mobile phone number).

In case of runway direction 31
Training or certification flights may be authorised for RWY 31R. Such flights (with the exception of police training flights) may only be authorized for RWY 31L if RWY 13L/31R is not available.

In case of runway direction 13
Training flights may not be authorised for RWY 13. Certification flights may be authorized for RWY 13R. If RWY 13R/31L is not available, certification flights may be authorised for RWY 13L.

6.2    Execution of training, demonstration or certification flights

During training flights, with the exception of emergency cases, English RTF phraseologies shall be used.

Note: The English expressions of the different manoeuvres which can be made after the approaches are listed in See 6.2.1 c) below.

1. For heavy and medium wake turbulence category aircraft:

   Demonstration or certification flight
   RWY	Route	Altitude	Flight rule
   31R/L	RWY HDG or RADAR VECTOR	4 000 FT AMSL	VFR/IFR
   13R/L

   Training flights
   31R/L	RWY HDG or RADAR VECTOR	4 000 FT AMSL	VFR/IFR

   Note: Deviation from the prescribed track and altitude is only allowed by ATC clearance.

2. For light wake turbulence category prop and turboprop aircraft:

   Training flight
   RWY	Traffic circuit	Altitude	Flight rule
   31R	RIGHT	min. 1 500 FT AMSL max. 2 500 FT AMSL	VFR
   31L	LEFT		VFR

   Note: Deviation from the prescribed track and altitude is only allowed by ATC clearance.

3. The pilot shall report the requested manoeuvre after approach to the air traffic controller when flying downwind, before turning on to the base leg, at the latest, and to the tower controller during final approach when radio contact is established. The following expressions can be usedThe pilot shall report the requested manoeuvre to the air traffic controller when flying downwind, before turning on to the base leg, and to the tower controller at the latest, during final approach if radio contact is established only there. The following expression can be used:
   • continue on traffic circuit;
   • full stop;
   • touch-and-go;
   • low approach.

2.1   Noise preferential use of Runway System

Times of RWY changeover are subject to flexibility in order to ensure transition in safe conditions. ATC will operate the changeover as close as possible from the indicated time, taking into account the traffic conditions.

2.2   Nighttime (between 2100 - 0500 (2000-0400)) – Operational regulations which differ from daytime

For noise protection reasons, primarily RWY 31R or RWY 13R are to be used by arriving traffic during the night, in compliance with the authority resolution on the designation of noise protection zones. Light turbulence category aircraft arriving for the Terminal 1 apron may also use RWY 31L for landing between 2100 - 2300 (2000-2200) and between 0400 - 0500 (0300-0400).

For noise protection reasons, between 2300 - 0400 (2200-0300), RWY 13L is to be used for take-off and RWY 31R is to be used for landing (reciprocal runway operation). In the case of RWY 13L/31R being closed during this period, RWY 13R is to be used for take-off and RWY 31L is to be used for landing.

Reciprocal runway operations are to be conducted with a tailwind component greater than 5 KT, up to a maximum 10 KT tailwind, or 15 KT crosswind component (including gusts) if the following conditions are met:

• May only be conducted on RWY 13L/31R
• Runway must be dry, and estimated surface braking action must be goodThe runway surface is dry and reported Runway Condition Code 6 (GOOD)
• Authorized only for ICAO WTC L and M aircraft
• For departure from RWY 13L take-off shall be planned from taxiway intersection B5 (full length)
• Authorized in VMC conditions only
• All CNS and AGL systems must be fully operational for the instrument approach in use, to the extent required by the prevailing weather conditions
• All runway end and rapid exit taxiways must be available for the runway in use.

Holding of arriving or departing aircraft can be expected occasionally up to 30 minutes between 2300 - 0400 (2200-0300).

2.3   Exceptions

Other than the cases specified in section 7, deviation from the basic rules on RWY use is only possible under the following circumstances:

• during the closure of one of the two RWYs due to maintenance works, or another unexpected event;
• in case of calibration flights;
• if no ILS approach is available on the runway selected on the basis of standard regulations.
• when the crosswind component exceeds 15 KT or more (gusts included);
• when the tailwind component exceeds 5 KT or more (gusts included);
• when wind shear has been reported or forecast, or when thunderstorms are expected to affect arriving or departing traffic;
• when pilots report excessive wind at higher altitudes resulting in go-arounds;
• when the runways are contaminated or when estimated surface friction is less than goodthe reported Runway Condition Code is less than 6 (GOOD);
• for landing, when the ceiling is lower than 500 FT or the visibility is less than 1900 M;
• for departure, when the visibility is less than 1900 M;
• when alternative runways are successively requested by pilots for safety reasons.

Gust components are derived from the maximum three second average wind speed which occurred during the last ten minutes (or a shorter period in case of a marked discontinuity).

3.1   ILS operations

Note: A change in operational status, if caused by a failure expected to last more than one hour, will be promulgated by NOTAM and accordingly by ATIS. Pilots will be notified of shorter term deficiencies by ATC (ATIS and/or radiotelephony).

3.2   ATC Procedures for Low Visibility Conditions

3.3   Practice ILS approaches

Pilots who wish to practice CAT II or III approaches are requested to use the phrase:

“Request practice category II (or III) approach”

on initial contact with Budapest Approach. Practice ILS approaches will be allowed only when traffic conditions permit. Pilots will be informed if the requested approach may be carried out.

3.4   Precision Approach Terrain Charts

Precision Approach Terrain Charts are published as AD 2-LHBP-PATC.

3.5   Obstacle clearance

OCA/H are published on the relevant IACs.

3.6   Instrument approaches

The IAPs are published on IACs listed in LHBP AD 2.24.

3.7   Visual Approach

Visual approach is not permitted at LHBP, except in VMC for:

• VFR traffic
• IFR traffic, only when no instrument approach available for the relevant runway direction.

3.8   Aerodrome Operating minima

3.9    Initiation of an approach to land

It is assumed that an operator will formulate rules for the operations personnel concerned, regarding the initiation of an instrument approach depending on the weather conditions.

3.10   ATC procedures

4.1   General

Note 1: The SID procedures comprise the noise abatement procedures and clearance for climbing up to 7 000 FT altitude, when the requested cruising altitude given in the flight plan equal to 7 000 FT QNH or higher.

Note 2: Airspace restrictions in force are broadcast by ATIS.

5.1   General

All VFR flights flying 120 KIAS or less shall plan their flights below Budapest TMA and plan their entry/exit to/from Budapest CTR via designated entry/exit points (See 5.2.1) below 3 500 FT AMSL (expect 1 500 FT AMSL).

All VFR flights flying more than 120 KIAS shall plan their arrivals via Budapest TMA (entry/cruising altitude 2 500 FT AMSL or above).

ATC clearance for VFR flights within Budapest TMA and in Budapest CTR will be given on the following conditions:

1. Valid flight plan has been filed;
2. VMC are adequate (visibility 5 KM or more, ceiling 1 500 FT or more) and there is vertical visual reference to the ground;
3. Two-way radio communication is possible. Information about the appropriate frequency may be obtained from Budapest Information;
4. The aircraft is power-driven;
5. The aircraft is equipped with transponder mode C, in case of landing at Budapest Liszt Ferenc Airport mode S. Exemption from this requirement may be granted by the appropriate ATC unit.

5.2   VFR procedures at Budapest Liszt Ferenc International Airport and within Budapest CTR (See VAC)

DUNAMO: 472216N 0190534E

(Eastern arm of river Duna and M0 highway cross - the bridge)

KEREPES: 473314N 0191619E

(Commuter train station KEREPES – it is where the railway track divides from the highway.)

TAPIOSAP: 472936N 0192646E

(TPS VOR)

For flights operating in the NW part of the CTR, outside the final approach area, the following points are designated for entry/exit:

TSEPEL: 472740N 0190419E

(Csepel bridge – The N end of Csepel island)

MIKLOS: 473244N 0190239E

(Miklós square in Óbuda)

SIKATOR: 473426N 0190929E

(Sikátorpuszta – at the crossing of motorway M3 and motor-road 2/B.)

Departing VFR flights from Budapest Liszt Ferenc International Airport - except special flights - shall plan via KEREPES, TAPIOSAP or DUNAMO exit points only.

Arriving VFR flights to Budapest Liszt Ferenc International Airport, except special flights, shall plan via DUNAMO entry point only.

3.1   The content of ATIS broadcasts:

1. Name of aerodrome
2. Designator
3. Time of observation
4. Type of approach to be expected and runway(s) in use
5. Significant runway surface conditions and, if appropriate, braking action; conditions of other movement areasauthoritative RWYCC, conditions of other movement areas
6. Expected delay, if appropriate
7. Transition level
8. Other essential operational information
9. Meteorological report
10. ATFM information

4.2   Reporting a Bird Strike

Operators using Budapest Liszt Ferenc International Airport are requested to report events of bird strike by filling in the ICAO standard “BIRD STRIKE REPORTING FORM” (BSRF). The form can be obtained and filed at the ARO.

If the event occurs after take-off and the crew do not consider it necessary to interrupt their flight, then they should notify the TWR via radio, then fill in the BSRF at their destination airport and send it to the following address:

Airside Management

BUD International Airport Zrt.