At Budapest Liszt Ferenc International Airport Category 9 rescue and fire fighting vehicles, equipment and personnel are provided. Full service on a 24 hour basis is provided.
For Budapest Liszt Ferenc International Airport the following snow plan is established:
Budapest Airport Zrt. is responsible for snow removal and for measuring, improving and reporting the conditions of pavement of the movement areas.
For clearing of snow, ice, slush and associated standing water, the following methods are used:
At times of moderate snowfall and for routine maintenance of the movement areas highspeed sweepers are used. If heavy snowfall occurs, the following equipment group is used as necessary: highspeed sweepers, snow ploughs and blowers.
At temperatures between 0 and -7 C Carbamid/Urea, and between -7 and -15C Clearway is used.
For measuring the depth of snow, slush and associated standing water on the movement areas an ordinary measuring rod will be used. On runways the measurement will be made normally approximately at 600 m intervals along the runway, 5-10 m on each side of the centre line and an average value will be calculated for each third of the runway and will be reported in millimetres.
The surface friction on the runways, taxiways and apron will be measured by use of a SAAB Friction Tester (SFT). The friction coefficient is measured continuously.
The assessment of braking action may be made by use of Mu-meter or an ordinary vehicle (jeep) too, if it is appropriate.
The inspection of the movement area is made at regular intervals. In Summer conditions normally at 12 hour intervals and in Winter season usually in every 6 hours or more frequently when a significant change in conditions occurs.
The following changes, relating to runway conditions, are considered as significant:
When measuring devices (SFT or MUM) are used for the assessment of runway braking action, the results will be reported in accordance with the following:
ICE AND DRY SNOW | |
Estimated Surface Friction | CODE |
GOOD | 5 |
MEDIUM/GOOD | 4 |
MEDIUM | 3 |
MEDIUM/POOR | 2 |
POOR | 1 |
During the Winter season information about snow, ice, slush and associated standing water on the movement areas at Budapest Liszt Ferenc International Airport will be published by using the SNOWTAM format according to the provisions of ICAO Annex 15. SNOWTAM series are numbered from S0001 and are issued as necessary.
The distribution list of SNOWTAM series will be published every year prior to 15th of November, by NOTAM.
All incoming SNOWTAMs should be addressed to LHBPYNYS. The requests concerning amendments to the distribution list should be addressed to LHBPYNYN.
Supplementary to the issue of the appropriate SNOWTAM, the temporary closure of the aerodrome in order to permit removal of snow and/or ice and its subsequent re-opening will be made the subject of a separate NOTAM, issued with the priority prefix “DD”.
Runway braking action will be reported in SNOWTAMs as follows:
Estimated surface friction (one digit) for each third of the runway measured will be entered in item H of SNOWTAM format, the abbreviation of the measuring equipment used is indicated in item T
If the braking action assessment is made by use of a normal car or jeep, this will be indicated by suitable plain language in item T of the SNOWTAM format.
Information on runway conditions will also be disseminated in an eight-figure code group over the MOTNE system following the routine meteorological message.
Information of runway condition will be expressed by means of the figure group DRDRERCReReRBRBR where:
The following instructions govern the composition and use of this eight-figure group:
Runway designator (DRDR)
This will be expressed as two digits corresponding to runway designator, e.g. 13, 31. “left” runways will be shown as already expressed e.g. 13 or 31; “right” runways will be expressed by adding numerically 50 to these figures, e.g. 63 or 81. For example 31L is shown as 31; 13R is shown as 63. When it is intended to indicate “all runways” the figure 88 will be used.
Note A: The digits 99 are used under certain circumstances as described in paragraph 2.7.2.
Note B: The information to be included in runway state messages will be for the main instrument runway in use. When parallel runways are in use, information on both runways will be included or, where this is not possible, the information given will not alternate between the two runways, but will be given for the runway with the best surface conditions.
Runway deposits (ER)
This will be expressed as a single digit as follows:
0 | Clear and dry |
1 | Damp |
2 | Wet or water patches |
3 | Rime or frost covered (depth normally less than 1 mm) |
4 | Dry snow |
5 | Wet snow |
6 | Slush |
7 | Ice |
8 | Compacted or rolled snow |
9 | Frozen ruts or ridges |
/ | Type of deposit not reported (e.g. due to runway clearance in progress |
Extent of runway contamination (CR)
This will be expressed as a single digit in accordance with the following scale:
1 | Less than 10% of runway contaminated (covered) |
2 | 11% to 25% of runway contaminated (covered) |
5 | 26 to 50% of runway contaminated (covered) |
9 | 51% to 100% of runway contaminated (covered) |
/ | not reported (e.g. due to runway clearance in progress) |
Depth of deposit (eR eR)
This will be denoted by two digits in accordance with the following scale:
00 | Less than 1 mm |
01 | 1 mm |
02 | 2 mm etc. |
10 | 10 mm etc. |
15 | 15 mm etc. |
20 | 20 mm etc.up to 90 mm |
90 | 90 mm |
thereafter:
92 | 10 cm |
93 | 15 cm |
94 | 20 cm |
95 | 25 cm |
96 | 30 cm |
97 | 35 cm |
98 | 40 cm or more |
99 | runway or runways are non-operational due to snow, slush, ice, drift of snow or runway clearance but depth not reported |
// | depth of deposit operationally not significant or not measurable |
Note A: This does not necessarily require depth to be measured to a millimetre unit. Larger intervals up to 90 can be expressed by using the scale above.
Note B: Where depth is measured at a number of points along a runway the average value will be transmitted or, if operationally significant, the highest value.
Note C: Code Figure 91 is not used. Code Figures 92 to 98 permit the depth of deposit (cm) to be derived by multiplying the last digit by 5 (e.g. 94=4x5=20).
Note D: If deposits of the type reported by the code figures 3, 7, 8 and 9 of code ER are reported, the depth of deposits is normally not significant and two oblique strokes (//) will be reported. Similarly, the depth of standing water will only be reported if an accurate and representative measurement is guaranteed.
Friction coefficient or braking action (BRBR)
This will be denoted by two digits corresponding to the friction coefficient or, if not available, the estimated braking action, in accordance with the following:
Friction coefficient
The reported values are used:
28 | friction coefficient 0.28 |
35 | friction coefficient 0.35 etc. |
Braking action
The following figures are used:
95 | good |
94 | medium/good |
93 | medium |
92 | medium/poor |
91 | poor |
99 | unreliable |
// | braking action not reported, runway not operational |
Note A: When in exceptional cases the braking action is assessed at a number of points along a runway, the mean value will be transmitted or, if operationally significant, the lowest value.
Note B: If measuring equipment does not allow measurement of friction with satisfactory reliability, which may be the case when a runway is contaminated by wet snow, slush or loose snow, the figures 99 will be reported.
Note C: If the braking conditions cannot be reported (e.g. due to runway clearance in progress, runway not operational, runway conditions not watched during airport closure, etc.) two oblique strokes (//) will be entered.
The occasion may arise when a new report or a valid report is not available in time for dissemination over MOTNE with the appropriate METAR message. In this case, the previous runway state report will be repeated; this should be indicated by inserting 99 in place of the runway designator (DRDR). This procedure, however, should be an exceptional occurrence. Consecutive use of group 99 should be avoided as much as possible.
Example: 99421594 means dry snow covering 11% to 25% of runway, depth 15 mm, braking action medium to good; this is a repetition of the previous report since no new report or valid report was available in time for transmission on the MOTNE.
If a runway is being cleared from ice, snow, slush, etc. this will be reported as follows: DRDR//99//.
Example: 63//99// = RWY 13R non-operational due to runway clearance in progress.
If runway are contaminated but runway reports are not available or, due to aerodrome closure or curfew, etc. are not updated, a group consisting of the figure 88 instead of the runway designator DRDR and 6 oblique strokes (88//////) will be sent. Example: 88//////.
If contamination conditions on a single runway or on both runways at the aerodrome have ceased to exist, a group consisting of the runway designator and the abbreviation “CLRD//” should be sent.
Examples: 63CLRD//; 88CLRD
If the cessation of contamination conditions on both runways at the aerodrome is reported by 88CLRD//, this group indicates that no further eight-figure groups will be sent in MOTNE unless contamination conditions recur.
In the case when the aerodrome is closed due to snow on the runway(s) the runway state group will be replaced by the code word SNOCLO. This information will be transmitted also in VOLMET.
The following priorities have been established for the clearance of movement areas at Budapest Liszt Ferenc International Airport:
Duty Airside manager is responsible for reporting changes in the state of the movement areas to:
For dissemination of the above information the ICAO SNOWTAM format is used.
If the runway is affected by standing water not associated with snow, slush or ice at any time during the approach for landing of an aircraft the depth and location on which standing water is notified by the aerodrome supervisor direct to ATS for transmission to the aircraft. If the duration of the phenomena is likely to persist, and the information requires a wider distribution, a NOTAM is issued.