General Regulations
- Handoffs (transfer of communication) shall be made latest 10 NM prior the respective boundary (FIR border, APP airspace, delegated airspace). After handoff, traffic is NOT released for climb, descent or turns unless otherwise specified in the regulations below.
- Overflying LOVV and/or LKAA shall be handed off on a valid ATS route at RFL 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 15NM. Spacing 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.
- RFL = requested flight level
ATC Stations (Praha FIR)
| LKAA_CTR
|
Praha Radar
|
127.125
|
GND-UNL
|
| LKAA_W_CTR
|
Praha Radar East
|
120.275
|
GND-UNL
|
| LKAA_U_CTR
|
Praha Radar Upper
|
133.425
|
FL305-UNL
|
Handoff Priorities
LOVV - LKAA
Sector responsibilities in all 4 possible cases:
| Main ATC
|
Additional ATC
|
Additional ATC
|
| LKAA_CTR
|
LKAA_E_CTR
|
LKAA_U_CTR
|
| Not suitable for LOVV
|
GND – FL285
|
FL285 – UNL
|
| LKAA_CTR
|
LKAA_E_CTR
|
|
| Not suitable for LOVV
|
GND – UNL
|
|
| LKAA_CTR
|
|
LKAA_U_CTR
|
| GND – FL255
|
|
FL285 – UNL
|
| LKAA_CTR
|
|
|
| GND – UNL
|
|
|
LKAA - LOVV (outside LOWW APP airspace)
Sector responsibilities in all 4 possible cases:
| Additional ATC
|
Main ATC
|
Additional ATC
|
| LOVV_L_CTR
|
LOVV_CTR
|
LOVV_U_CTR
|
| GND – FL125
|
FL125 – FL245
|
FL245 – UNL
|
| LOVV_L_CTR
|
LOVV_CTR
|
|
| GND – FL125
|
FL125 – UNL
|
|
|
|
LOVV_CTR
|
LOVV_U_CTR
|
|
|
GND – FL245
|
FL245 – UNL
|
|
|
LOVV_CTR
|
|
|
|
GND – UNL
|
|
LKAA - LOVV (within LOWW APP airspace)
Sector responsibilities in all 2 possible cases:
| Main ATC
|
Additional ATC
|
| LOWW_APP
|
LOWW_N_APP
|
| GND – FL105
|
FL 105 – FL245
|
| LOWW_APP
|
|
| GND – FL245
|
|
IFR flights from Praha FIR to Wien FIR.
| Destination |
COP |
Level Allocation |
Special Conditions
|
| EDM*/LDZA/LOWI/LOWS/LOWK/LJMB |
MIKOV |
↓FL340 |
|
| LOWL/LOWG |
MIKOV |
↓FL300 |
|
| LOWW |
MIKOV |
↓FL130 |
Below FL170, rlsd. for right turn afer ADISU
|
| EDM*/LDZA/LJLJ/LOWI/LOWS/LOWK/LJMB |
LANUX |
↓FL330 |
|
| LOWL/LOWG |
LANUX |
↓FL310 |
|
| LZIB |
LANUX |
↓FL230 |
|
| LOWW |
LANUX |
↓FL150 |
|
| LOWL |
LUPEV |
↓FL170 |
Below FL210
|
| LOWW/LZIB |
ABUDO |
↓FL330 |
|
|
|
|
|
| Departure |
COP |
Level Allocation |
Special Conditions
|
| LKMT |
MIKOV |
↑FL300 |
FL250 or above
|
| LKTB/LKKU |
MIKOV |
↑FL100 |
|
| LKTB/LKKU to LOWW |
MIKOV |
↑FL300 |
FL250 or above
|
| LKMT |
MIKOV |
↑FL300 |
FL250 or above
|
| LKMT |
MIKOV |
↑FL300 |
FL250 or above
|
| LKMT |
MIKOV |
↑FL300 |
FL250 or above
|
| LKPR/LKKB/LKVO/LKPD |
PISAM |
↑FL310 |
|
IFR flights from Wien FIR to Praha FIR.
| Destination |
COP |
Level Allocation |
Special Conditions
|
| EPKK/EPKT/EPWR |
MIKOV |
↓FL330 |
|
| LKMT |
MIKOV |
↓FL270 |
|
| LKTB/LKKU |
MIKOV |
↓FL110 |
Below FL120
|
| LKPD/LKCV |
LANUX |
↓FL280 |
|
| LKPR/LKKB/LKVO/LKPD/LKKV/LKCV |
PISAM |
↓FL320 |
|
|
|
|
|
| Departure |
COP |
Level Allocation |
Special Conditions
|
| LOWW |
LEDVA |
↑FL210 |
above FL170
|
| LOWW to LKTB/LKKU |
LEDVA |
↑FL90 |
|
| LOWW exc. dest LKPR |
LANUX |
↑FL300 |
|
| LOWW to LKPR |
LANUX |
↑FL180 |
|
| LOWW |
LEDVA |
↑FL210 |
above FL250
|
| LZIB |
LEDVA |
↑FL340 |
above FL310
|
| LOWL |
LUPEV |
↑FL160 |
|
| LOWS |
UPEGU |
↑FL300 |
above FL250
|
|
Special Agreements
Bratislava Airspace Agreement
If Bratislava Airspace (LZBB_CTR) is not ATC-covered by it’s own FIR, LOVV controllers have to check the ATIS of LKAA_E_CTR or LKAA_CTR to see if the appropriate controller also takes over responsibility for LZBB airspace. If yes, handoffs for A/C heading to LHCC airspace via LZBB airspace should be handed off to the appropriate LHCC_CTR controller after text coordination between the appropriate units. If the A/C is heading in any other direction via LZBB airspace and LKAA_CTR controller takes over responsibility for LZBB airspace, then the handoff to LKAA_E_CTR or LKAA_CTR should be done at the border as usual. If LKAA doesn’t takes over responsibility for LZBB, A/C heading in all direction except LHCC airspace should resume own navigation.
UZ37 Flights
Traffic on UZ37 routing to LOWW via VENEN or GIMBO will be handed off. After passing VADOV or BUDEX, released for descend according to instructions.