Skip to main content

Delivery

VFR traffic, in contrast to real procedures, does not have to request startup at Delivery, but can report ready for taxi directly to the ground control.

Startup: When startup clearance cannot be given immediately or the pilot is not ready for startup within the next 5 minutes during high traffic situations, the pilot needs to stay on Delivery frequency until he receives startup clearance. If an expected startup time (TSAT) exists, the pilot should be informed about it. This procedure might be necessary during events with a lot of outbound traffic.

Capacity: Due to a limited capacity for outbound traffic on ground, there should not be more than 12 active startup clearances at the same time (including SUG, PBG, TXG).

Euroscope: Delivery shall ensure that the initial climb is set and the correct SID is coded into the flightplan (very important for Center!). When issuing startup the corresponding ground state "SUG" (Startup Given) and the clearance received flag need to be set.

Departure Routes

The standard intrument departure procedures from Cologne-Bonn lead to the waypoints NVO, WYP, COL, PODIP and KUMIK. The initial climb for all departures is 5000 ft MSL. All SIDs except three non-RNAV departures have speed or altitude restrictions, the phrase "climb via SID" need to be used.

grafik.pngDeparture Routes out of Cologne-Bonn

General Restrictions:

  • The standard departure routes via COL are only used for local training flights or for flights to Frankfurt/Main EDDF.

Runway 06, 24 and 32L:31L:

  • noDesignators specialK procedures(RWY 06), D (RWY 24) and M (RWY 31L) are the available RNAV departures. 

Runway 14L:13L:

  • Designator F is prefered for all RNAV Departuredepartures.
    • Routes with
  • Designator Q arerequires prefered.RNAV and RF-Legs capability and should be used only if filed by the pilot or on request.
  • Designator X is only used for aircraft3-engines withheavies WTC(e.g. heavy and 3 enginesMD11).
  • DeparturesNVO#P via NVO#P should beis used for aircraft that aredepartures unable to fullfillcomply with the climb restrictionsrestriction on NVO#Qthe F or NVO#FQ (need to be reported by the pilot).
    SID.
  • NVO#W mayby ATC only beand assignedrequires afterprior coordination with the responsible arrival controller,Radar as itthe crossesSID throughwill approachingcross traffic.the inbound stream. It is only used, if certain glider-areas are active (which are not simulated on VATSIM). Appropriate flights must be announced to the approach controller by the tower before take-off.
  • Designator F should be used for non-RNAV capable aircraft!

Runway 14R:13R:

  • Departure Routes with Designator E areis prefered.prefered for all RNAV departures.
  • DeparturesNVO#C via NVO#C should beis used for aircraft that aredepartures unable to fullfillcomply with the climb restrictionsrestriction on NVO #F (need to be reported by the pilot).
    E SID.
  • NVO#V mayby ATC only beand assignedrequires afterprior coordination with the responsible arrival controller,Radar as itthe crossesSID throughwill approachingcross traffic.the inbound stream. It is only used, if certain glider-areas are active (which are not simulated on VATSIM). Appropriate flights must be announced to the approach controller by the tower before take-off.

Runway 32R:31R:

  • Departure Routes with Designator B areis prefered.
    • prefered
  • Aircraftfor withRNAV less thendepartures 98above t98t MTOW (e.g. B739,B757).
    • A321)
  • Designator shouldR useis SIDsused for all RNAV capable outbounds with DesignatorMTOW Cbelow 98t (noiseas abatementwell procedure).as for A300 and A330.
  • NVO#R requires RNAV and RF-Legs capability and should be used only if filed by the pilot or on request.

Non-RNAV Departures are only available via NVO and WYP out of runway 13L (Y), 31R (N), 06 (U) and 24 (T).

RWY13R / RWY31L departures can be assigned on a daily basis to small general aviation aircraft, as well as aircraft up to the category of A320/B738 if required. After coordination with Tower, RWY 13R can be used for RNAVall capablelight and medium aircraft only!during high traffic situations. 

With westerly winds, outbounds should be asked if they prefere runway 24 (when active) or runway 13L/31R for departure.

Quicksheet - Standard Instrument Departures

SIDs_EDDK.pngEDDK_SIDs_2404.png

Vectored Departures

If pilots are unable to fly a standard instrument departure (even an older version of the current SID) a vectored departure can be coordinated between Delivery and Arrival.

Primary runway heading and an initial climb of 4000ft should be used. Other coordinations are always possible. At Euroscope the SID with RVxxxxx should be selected (xxxxx = first waypoint).

At Cologne-Bonn Airport we offer Datalink Clearance to the pilots throughout the Hoppie System and the Topsky Plugin. The airport code EDDK should be used (already preselected).

An example of the DCL message the pilot will receive can be seen below. It's important that the current ATIS Designator is entered in the remarks field. By default startup always needs to be approved seperately.

CLD 1051 220621240418 EDDK PDC 012 EWG6TG CLRD TO LEPA OFF 32R13L VIA KUMIK1CKUMIK2Q CLIMB 5000 SQUAWK 1000 ADT MDI NEXT FREQ 121.855 ATIS R REQUEST STARTUP ON 121.855

Back to top