RAD RADAN EB: RADAN ED: RADAN EE: - Network operations

Updated on 10/01/13 RAD
Valid from 07/03/13 APPENDIX 5 - Airport connectivity Page 36 of 40
RADAN LK:
The use of SID/STARs is mandatory where published.
For AD’s where SID/STARs are published:
- the last RP of the SID shall be filed as the first RP of the route
- the first RP of the STAR shall be filed as the last RP of the route
SIDs/STARs shall be completely followed within LK**, leaving or joining at an intermediate point is not permitted.
DCT Departures/Arrivals LKNA/PO = 70nms to the first significant en-route point
DCT Departures/Arrivals other airfields = 0nms
(exceptions: Training and Photographic Flights/NAV Aid tests/Prior permission of Praha ACC is required – see AIP CR ENR 1.1.11)
Arrivals
DCT LKCV = 0nms - One of the first reporting points of the STARs published in the MIL AIP shall be filed as the last reporting point of the route:
BEKVI/BODAL/ELPON/GOSEK/VLM
DCT LKKB = 0nms - One of the first reporting points of the STARs published in the MIL AIP shall be filed as the last reporting point of the route:
GOLOP/GOSEK/LOMKI/VLM
Departures
DCT LKCV = 0nms - One of the last reporting points of the SIDs published in the MIL AIP shall be filed as the first reporting point of the route:
BEKVI/BODAL/RAK/VOZ
DCT LKKB = 0nms
DCT LKVO = 0nms
Connecting points for DEP from airfields
LKKB : ARTUP/BALTU/DOBEN/VENOX/VOZ
LKVO : ARTUP/BALTU/DOBEN/VENOX/VOZ
DCT City Pair = Allowed in the following cases :
Prague group DCT BEKVI LKPD (and return) (LK5503)
Prague group DCT BEKVI LKCV (and return) (LK5503)
Prague group DCT BEKVI DCT Prague group (LK5503)
Prague group DCT VO DCT Prague group (LK5508)
Prague group DCT OKL DCT Prague group (LK5505)
RADAN LM:
DCT Departures/Arrivals LMML DCT = 0nms
SIDs shall be completely followed within LM**, leaving or joining at an intermediate point is not permitted.
Connecting points for ARR. to airfields
LMML = GZO/MLT
- 36 -