LOA LHCC
Overview
This is a copy of the original LoA, printed as PDF, Version 1.0 from 1st January 2007 by Daniel Gruber (FIR Wien) and Péter Selmeci (VACCHUN). The sectors of Austria are not included here, because of other articles in this wiki.
General regulations
Handoffs (transfer of communication) shall be made latest 10 NM prior the respective
boundary (FIR border, TMA border, delegated airspace). After handoff, traffic is NOT
released for climb, descent or turns unless otherwise specified in the regulations below or
otherwise coordinated between the two concerned sectors.
Traffic overflying LOVV and/or LHCC shall be handed off on a valid ATS route at RFL
(requested flight level) using the semicircular cruising level system (even/odd). Direct
routings shall be coordinated.
Spacing between two aircraft on same level and same routing shall be at least 10 NM if the
speed of the succeeding traffic is equal or less than the speed of the preceding traffic,
otherwise at least 15 NM. Spacings deviating from this regulation shall be coordinated.
Traffic shall be handed off at the levels defined in the regulations below. If a specified level
restriction cannot be met due to a lower RFL, traffic shall be handed off AT RFL, if this does
not cause a conflict with any other traffic. Otherwise traffic shall be coordinated.
If a traffic situation is not covered herein, individual coordination between the concerned
sectors shall be made.
Areas of Responsibility and Delegation of the Responsibility for the Provision of ATS LESMO area (LOWW arrivals)
- In LESMO area ATS will be provided primarily by LOWW_APP if present, otherwise by LOVV_CTR.
- Traffic shall be cleared GIGOR1W arrival by Budapest ACC unless otherwise requested.
- Transfer of control and communication of LOWW arrivals will always be initiated before entering LESMO area.
- Vertical limits of LESMO area: 5500’ AMSL – FL240
LHBP arrivals via Slovakian airspace
For LHBP arrivals via ABLOM or MAREG (entering Slovakian airspace)
- if LZBB FIR is uncontrolled (i.e. none of LZBB_CTR, LKAA_CTR, LKAA_E_CTR is online), traffic is to be handed off to LHCC_CTR at the FIR border of LOVV/LZBB.
- if LZBB_CTR is online, traffic shall be transferred to LZBB_CTR.
- if LKAA_E_CTR is online, traffic shall be transferred to LKAA_E_CTR.
- if LKAA_CTR is online, information will be available in the controller’s ATIS about the coverage of LZBB FIR. The following cases are possible:
- if LKAA_CTR is not covering LZBB FIR, traffic shall be transferred to LHCC_CTR or LHBP_APP according to the first example
- if LKAA_CTR is covering LZBB FIR, traffic shall be transferred to LKAA_CTR
- Descend clearance is to be issued in time to ensure crossing MAREG at FL290 or below.
Sectorisation in BUDAPEST FIR
Normal operation (single sector operation):
| ATS unit: | Budapest ACC |
| Radio c/s: | Budapest Radar / Budapest Control |
| Frequency: | 133.200 MHz |
| Login name: | LHCC_CTR |
Sector splitting (multiple sector operation):
For domestic events:
| ATS unit: | Budapest FIC |
| Radio c/s: | Budapest Information |
| Frequency: | 128.950 MHz |
| Login name: | LHCC_I_CTR |
| Comments: | BELOW 9500’ AMSL |
If sectors are split horizontally:
| ATS unit: | Budapest ACC – LOWER |
| Radio c/s: | Budapest Radar / Budapest Control |
| Frequency: | 128.100 MHz |
| Login name: | LHCC_CTR or LHCC_L_CTR |
| Comments: | BETWEEN FL100 – FL295 |
| ATS unit: | Budapest ACC – UPPER |
| Radio c/s: | Budapest Radar / Budapest Control |
| Frequency: | 133.200 MHz |
| Login name: | LHCC_U_CTR |
| Comments: | ABOVE FL295 |
If sectors are split vertically:
| ATS unit: | Budapest ACC – EAST |
| Radio c/s: | Budapest Radar / Budapest Control |
| Frequency: | 130.570 MHz |
| Login name: | LHCC_E_CTR |
| ATS unit: | Budapest ACC – WEST |
| Radio c/s: | Budapest Radar / Budapest Control |
| Frequency: | 133.200 MHz |
| Login name: | LHCC_CTR or LHCC_W_CTR |
Co-ordination Points and Flight Level Allocation
Departures shall be cleared:
| From | CFL/ max FL | Entry conditions |
| LHBP via SUNIS | 280 | at FL |
| LHBP via TEKNO – BEGLA | 300 | climbing / at FL250 or above |
| LHBP via all other COPs | 300 | climbing / at FL250 or above |
| LHPP via SUNIS | 260 | climbing |
| LHPP via all other COPs | 280 | climbing |
| LHSM via DIMLO, GOTAR, SUNIS | 160 | climbing |
| LOWW via STEIN and SASAL | 270 | climbing / at FL110 or above |
| LOWW via DIMLO | 310 | climbing / at FL250 or above |
| LOWK via GOTAR, DIMLO | 190 | at FL |
| LOWG via GOTAR, DIMLO | 150 | climbing / at FL130 or above |
| FIR Ljubljana | 250 | Climbing |
| LHPR | 8000’ AMSL | climbing |
The assignment of higher levels rests primarily with the accepting unit !
Arrivals shall be cleared:
| Destination | CFL/ max FL | Entry conditions |
| LOWW via GIGOR 1W STAR | 140 | cross GIGOR at FL160 or below |
| LOWW via DIMLO | 260 | at FL |
| LHBP via GOTAR | 290 | cross FIR border at FL290 |
| LHBP via STO UL175 ANEXA | 170 | cross ANEXA if runway in use 31 |
| 130 | cross ANEXA if runway in use 13 | |
| LHSM | 230 | cross FIR border at FL250 or below |
| LHTA, LHPP | 290 | at FL |
| LOWL, LOWS | 340 | at FL |
| LOWK | 200 | at FL |
| LOWG via GOTAR, DIMLO | 140 | cross FIR border at FL180 or below |
| within FIR Ljubljana | 260 | at FL |