EDDK - Köln/Bonn Airport

Overview

Köln/Bonn is a complex airport with crossing runways and very little space on the ground and in the TMA. On VATSIM, it usually has a medium amount of traffic but will regularly operate at or even above capacity during events.

Köln/Bonn is an unrestricted airport. DEL and GND are unrestricted and can be staffed by all controllers with an S1 rating or higher who have passed the required moodle courses. TWR position requires the EDDK_TWR Tier 1 endorsement which can be acquired by all controllers with an S2 rating or higher. All radar positions require the EDDK_APP Tier 1 endorsement which can be acquired by all controllers with an S3 rating or higher.

Due to the high amount of complexity of the airport, it is highly recommended that S1-rated controllers have gained a great deal of experience at other unrestricted airports before staffing positions at Köln/Bonn.

Training: Controllers with the S1 rating can staff TWR during their training (active EDDK_TWR solo endorsement required). Controllers with the S2 rating can staff APP positions during their training (active EDDK_APP solo endorsement required - sector NOR not included).

Köln/Bonn ATC Stations

Station
 Station ID
 Login
 Frequency
 Remarks
 Endorsement
ATIS
 ADK
 EDDK_ATIS
 132.130
 --
 --
Delivery
 DKC
 EDDK_DEL
 121.855
 --
 unrestricted: EDDK CBT Delivery
Ground
 DKG
 EDDK_GND
 121.730
 --
 unrestricted: EDDK CBT Delivery & EDDK CBT Ground
Apron
 DKGP
 EDDK_P_GND
   staffing forbidden
 staffing forbidden
Tower
 DKT
 EDDK_TWR
 124.980
 --
 Tier 1: EDDK_TWR
Arrival
 DKA
 EDDK_APP
 135.350
 --
 Tier 1: EDDK_APP
Director
 DKAT
 EDDK_F_APP
 121.055
 --
 Tier 1: EDDK_APP
Nörvenich sector
 NOR
 EDDK_NOR_APP
 127.365
   Tier 1: EDDK_APP

Staffing of Apron (DKGP/EDDK_P_GND) is currently prohibited.

Controlzone

EDDK_CTR.pngCologne-Bonn Controlzone (D-CTR) - © openflightmaps.org

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:

Runway 06, 24 and 31L:

Runway 13L:

Runway 13R:

Runway 31R:

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 all light and medium aircraft 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

EDDK_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. By default startup always needs to be approved seperately.

CLD 1051 240418 EDDK PDC 012 EWG6TG CLRD TO LEPA OFF 13L VIA KUMIK2Q CLIMB 5000 SQUAWK 1000 NEXT FREQ 121.855 ATIS R REQUEST STARTUP ON 121.855

Ground

Staffing of Apron (DKGP/EDDK_P_GND) is currently prohibited.

Airport layout

Cologne-Bonn airport has three crossing runways.

EDDK_Overview.pngairport layout

The airport has two passenger terminals. Terminal 1 with its two distinctive stars accommodates aprons A, B and C, and Terminal 2 with the apron area D. 

EDDK_APR.pngApron areas

The cargo area is used by several airlines and is located in the middle of the airport between the runways. It contains the apron areas E, F and W.

Apron V close to the cargo area is used for general aviation and business jets.

The military part of the airport is located west of runway 13R/31L at apron U. The military part of the apron is the home of the german Flugbereitschaft.

Area of Responsiblility

The area of responsibility of Ground is located between the three runways and includes all aprons except the military apron U (see image below). If RWY 24/06 is closed (not in use), the runway crossing can be delegated to the Ground controller.

EDDK_AoR.pngArea of Responsibility -  Cologne-Bonn Ground

Staffing of Apron (DKGP/EDDK_P_GND) is currently prohibited.

Runway Crossing: The crossing of all runways is within the responsibility of Tower, but can be delegated to Ground if the appropriate runway is not in use.

Parking Positions

Parking positions are assigned by the Ground Radar Plugin based on airline and aircrafttyp according real world usage. It is recommended to use the assigned stands. The maximum aircraft size for all parking positions can be displayed in Euroscope (Tower) with shortcut ALT + B.

Aprons A - D: These aprons are the passenger terminal aprons. Aprons A-C are used for Terminal 1, while Apron D is located at Terminal 2. 

Aprons E, F, V, W: All of these aprons are home to the big cargo-city at Cologne airport. Most of the heavy lifting cargo fleet (e.g. B747), are parked on aprons E and F, while aprons Vand W are home to the small feeder fleet (e.g. B737, ATR and B757/B767).

Apron U: Apron U is used by two maintenance companies for customers' aircraft. Parking positions U10 - U14 can be used up to code C (A321/B739) and parking positions U16 - U26 only for code A (wingspan < 15m).

Apron V: Apron V is used for business jets and general aviation. Depending on the position, aircraft up to the size of a B737-BBJ can be parked.

GAT: The GAT has no real permanent home. Previously it was located as shown on the map below, northeast of the RWY14R threshold. Nowaday, general aviation is parking mostly on the aprons V and U (partially civil, partially military). The original GAT as shown on the map, is home to the helipad of the Christoph 3 rescue helicopter.

Military: Cologne/Bonn is a double purpose airport. While it mostly handles civilian aviation (either pax or cargo), it's also home to the Köln-Wahn Airbase, of the Luftwaffe. On the western part of the airport (west of 13R/31L), the so called "white fleet" (A350, 340, GLEX) is stationed. To complete the fleet stationed at EDDK, the MRTTs (Multi-Role-Tanker-Transport) A321 and A330 are also located there.

Antonov AN225 special parking procedure: Parking parallel to taxiway A on Stands E09 to E15, main gear on E12, facing north-west.

Taxiway Usage

The primary used taxiway is A, running parallel to runway 13L/31R.

EDDK_TWY.pngTaxiways at Cologne-Bonn

31-Operations: During 31-Operations, traffic from the terminals taxiing southbound will be using TWY-A, while inbound traffic vacating the runway continues on TWY-E, to A5. If there is traffic requesting pushback on the E and F stands, outbound traffic can be rerouted via TWY-E. However, this may be blocking inbound aircraft vacating from RWY 31R. 

13-Operations: During 13-operations, inbound traffic vacating RWY 13L, heading for the terminals, will be taxiing northbound on TWY-A primarily. However, if there is traffic on aprons E and F asking for pushback, the parallel TWY-E can be used as alternative, so that the traffic on those aprons is able to push.

Runway 24/06 for taxi: It is possible for in- and outbound traffic to use runway 06/24 for taxi.

GAF1GH, taxi to holding point runway 31R via Bravo, enter runway 06 and Alpha, cross runway 31L.
DAFHK, taxi right via runway 24 and continue T.

After landing or before takeoff, the word "backtrack" has to be used.

EWG1PC, backtrack runway 24, vacate T.
RYR7AF, backtrack and lineup runway 24.

Taxiway Restrictions

Taxiway B and T can only be used up to Code E aircraft. Taxiway C is limited to Code C aircraft. Taxiway D between A and T can only be used by max. Code E aircraft. The part of D east of runway 13L/31R can also be used by a B748.

Parallel taxi on A and E with Code F aircraft: If an Airbus A380 is on taxiway A, taxiway E is limited to Code D aircraft. If a B748 or an AN124 is on taxiway A, taxiway E is limited to Code E (in case of a B748 limited to Code E + B748).

Colored lines: In front of Terminal 2 aircraft up to code C can use the orange and blue line simultaneously up to position D51.

On taxiway B between L and T (marked with (!)) only aircraft with a wingspan of max. 52 m (Code D) and max. weight of 200t are allowed to taxi on it's own. Aircraft up to 234t may be towed over or taxi on their own power over the bridge if guided by a marshaller.

Potential conflicts at the ground

Due to it's layout and placement of aprons, there are several critical areas at Cologne/Bonn Airport, which can either lead to congestion or taxi conflicts.

1. The holdingpoint dilemma:

The number one area marked on the map, is the area around the holdingpoint A5/A7, the northern ends of TWYs A and E, as well es TWYs B and M, around the C-Star (Terminal 1). Especially during 13-Ops, this area heavily suffers from congestion. Departing traffic will be queuing mostly at A7, some at A5, while inbound traffic will be taxiing northbound, via TWY A, B and M, to get to Apron D. Possibilities to solve at least some of the congestion issues, will be described on the following pages.

2. A3-Area:

Number two on the map, is the A3-Area. This areas is critical in different scenarios.

3. Taxiway B-Bridge

The third critical area is placed on TWY-B. Between Taxilane-L and the GAT (marked with (!)) taxiway B leads over a bridge where only aircraft with a wingspan of max. 52 m (Codeletter D) and max. actual weight of 200 t are allowed to taxi on it's own. A332/A333 and A343 with an actual weight of up to 234 t may be towed or can taxi with a marshaller on ther own power over the bridge.

4. Taxiway D

On taxiway D only Code E aircraft and below are allowed, except the part east of runway 13L/31R where also a B748 is allowed.


EDDK_Risk.pngPotential conflicts on ground

Tower

Runways

The airport has three runways, two of which run parallel and one of which crosses two runways.

Runway 13L / 31R

Runway 13L/31R is the longest runway at 3815 x 60m and is primary used for all inbound and outbound traffic. Runway 31R and 13L are both equiped with ILS CAT III.

Runway 13R / 31L

At a distance of about 1km southwest of runway 13L/31R is the much shorter parallel runway 13R/31L, which is 1863 x 45m long.

Due to its length and technical equipment, this runway is preferably used for VFR traffic. Because of its proximity to the military section, it is also frequently used by military aircraft. Runway 13R/31L is only approved for aircraft up to code C (e.g. B739, A321). During high traffic situations, this runway can be used for all light and medium traffic that is able (TORA 1863 m).

For non-precision approaches to runway 13R, a flight and ground visibility of at least 2.1 km must be provided due to the shortened approach lighting.

Runway 06 / 24

Across runways 13/31 is the intersecting runway 06/24, measuring 2459 x 45m. Only landing direction 24 is equipped with an ILS (CAT I). For RWY 06 only non-precision approaches are available.

Runway 06/24 is only approved for aircraft up to code letter E, including the B748.

For non-precision approaches to runway 24, a flight and ground visibility of at least 1.5 km must be provided due to the obstacle situation.

RWY24 can be used to taxi aircraft as well. Either because of wingspan limitations on TWY D or to the military apron, as well as for aircraft landing RWY13L to vacate the runway and to avoid the sharp turn into A3.

Control Zone

The control zone of Cologne-Bonn Airport is airspace type D and extends from the ground to 2500ft MSL.

EDDK_CTR.pngControlzone Cologne-Bonn

Airfields: South of the control zone there is the airfield Bonn-Hangelar EDKB, which, including its traffic circuit, is located outside the control zone.

To the north, also outside the control zone, is Leverkusen EDKL airfield. Its traffic circuit, however, extends into the control zone at an altitude of 1100ft on its southern side.

Please note the following: "From SR-30 until SS+30, the control zone in the depicted Dünnwald sector is not active. The general airspace classifications G (up to 1000ft AGL) and E (above 1000ft AGL) apply."
Source: AIP VFR Germany VOC EDKL

Hospitals: Several hospitals with helipads are located in the urban area of Cologne.

In the extended centerline of runway 13L, approx. 1.5 km north of the NDB LJ, is the hospital Merheim. Approaches to runway 13L fly over the hospital at approx. 1500ft. Helicopters may approach the landing area below the approaching traffic. Appropriate traffic information must then be provided to avoid missed approaches.

On the north-western edge of the control zone in Cologne-Nippes, on the CTR boundary, is the rather seldom approached St. Vinzenz Hospital.

On the west side in the Lindenthal district, just outside the control zone, is the University Hospital of Cologne.

To the west of the control zone is the Nörvenich ETNN airbase. Despite their proximity, the control zones of the two airports do not border directly on each other, but are separated by a narrow strip of type C airspace.

VFR-Traffic

There are 7 mandatory reporting points and 1 optional reporting point available for VFR traffic at Cologne.

Reporting Point
 Location
NOVEMBER 1 BAB 4, exit Bergisch Gladbach-Bensberg
NOVEMBER 2 BAB 3, motorway service station Königsforst-Ost
ECHO 1 Church in the middle of Neunkirchen

ECHO 2

(Optional)

 BAB 3, service area Sülztal
SIERRA 1 Marina at the mouth of the Sieg River into the Rhine
SIERRA 2 Sports facilities north of the village of Troisdorf-Spich
KILO 1 BAB 1 / BAB 57, motorway interchange Köln-Nord
KILO 2 BAB 4, rhine bridge Rodenkirchen

Just as popular for flights from / to the Bergisches Land are take-offs or landings in Bonn-Hangelar combined with a flight through the control zone via the S and N routes.

VFR Squawk: All VFR traffic inside the controlzone of Cologne will get the transpondercode 7003.

Helicopter traffic: The airport has frequent helicopter traffic. On the one hand, this is due to the fact that a helicopter squadron of the Federal Police is located at Bonn-Hangelar Airport and training traffic also takes place there. On the other hand, two rescue helicopters are stationed at the airport. "Christoph 3" (CHX3) has its landing pad at the GAT, while the intensive care transport helicopter "Christoph Rheinland" (CHX75) of the ADAC has its base at the north-western edge of the V- Apron towards Taxiway B. Only "Christoph 3" though, is allowed to land and depart directly from it's helipad. Every other helicopter has to either land on the runway or the runway threshold (e.g. 13R) and has to air-taxi to it's final position afterwards.

Direction of Operation

Up to a tailwind component of 5kt, operations will be handled via runways 31R and 31L. Runway 24 is also used if necessary up to a tailwind component of 5kt.

Operating direction 06 is used extremely rarely because the wind through the Cologne Bay preferably blows from a northerly to northwesterly direction.

In order to accelerate the taxiing of traffic and after prior coordination with ground control, the tower may give taxiing traffic (taxiways A3-A4) an initial taxi instruction into taxiway A or taxiway E (depending on the take-off direction) and then hand it over to ground control.

Parallel Operations

Due to the distance of only approx. 1150 m between the runway centrelines of 13L/31R and 13R/31L, independent parallel runway operations between these runways for IFR and/or SVFR traffic are not permitted.

Radar and runway seperation need to be applied, wake turbulence separation is not required.

Crossing Runway Operations

Combined operation of runways 13L/31R and 24 has the highest capacity. When runway 13R/31L is used as well, runway 24 is blocked for significantly longer.

It is important during crossing runway operations that the preceeding traffic (landing or departing) has crossed the runway cross before the succeeding traffic (landing) for the other runway has reached the 1 NM final. Otherwise the succeeding traffic has to go around.

Example: Departing traffic runway 31R has passed the runway cross before the inbound reaches 1 NM final for runway 24.

Missed Approaches

Without further coordination, the standard missed approach procedures published in the AIP shall be used.

Should a conflict arise due to an aborted approach in combination with a departing aircraft, the tower may issue immediate instructions to resolve the conflict. The arrival controller shall then be informed immediately of the action taken.

Auto-Handoff

Köln/Bonn utilizes an auto-handoff procedure for IFR departures where Tower will not hand off outbounds to the arrival controller. Make sure to set the correct departure frequency in the ATIS.

Outbounds should contact APP when passing 2.000 ft MSL unless explicitly told to remain on Tower frequency.

Arrival

The area around Cologne is divided into several sectors and areas, which can be staffed by four ATC stations. All radar stations, with the exception of Nörvenich Radar, take over the tasks of the other stations if they are not online.

With AIRAC 2403 DKA will not cover NOR anymore!

Arrival: Cologne Arrival DKA is responsible for the area around Cologne/Bonn Airport up to the Belgian border. The sector handles all departures from Cologne and presequence the inbound flights for the feeder. If arrivals or departures from Nörvenich (ETNN) take place without another station being staffed, this traffic is also handled by Arrival.

Feeder: The Feeder (Director) DKF works within the sector of Arrival. Especially during 13 operations the small area between FAF and the Düsseldorf Arrival sector border might require closer coordination between DKA and DKF.

DKA.png DKF.png
Area of Responsibility Arrival
 "Area of Responsibility" Feeder (dark yellow)

Military station Norvenich Radar: For arrivals and departures to the military airbase Nörvenich ETNN, the station Norvenich Radar (ETNN_APP) can be staffed. This station does not have its own sector as such, but is delegated an area of its sector by the arrival. This is staggered from GND over 3500ft to 5000ft MSL. The exact range can be seen in the following diagram. Coordination between all stations involved is essential.

ETNN_AoR.png Delegated sector to Nörvenich Radar

Langen Radar Sector Nörvenich: Langen Sector Nörvenich NOR is located west of the airport above the arrival area and is primarily responsible for the pre-sequencing of inbound flights to Düsseldorf from IBESA via ELDAR and BIKMU. In addition, the sector is responsible for all departures from Cologne to Belgium via NVO.

Frankfurt Outbounds via DITAM - OBOKA also pass through the sector, as do inbound flights to Brussels via UMUPU - GEBSO and NEREL - AGENI.

NOR will cover DKA if not staffed.

NOR.png NORup.png
Area of Responsibility Sector Nörvenich
 Area of Responsibility Sector Nörvenich

Airspace Structure

One of the most complex airspace structures in Germany is located around Cologne and Düsseldorf airports, because several airports are located next to each other in a very small area.

EDDK_Airspaces.pngAirspace structure Cologne-Bonn

Aircraft in C/D airspace around Cologne are the responsibility of Cologne Arrival. Airspace crossings through the active approach sector are to be coordinated with the Feeder depending on the situation.

Minimum Vectoring Altitude (MVA)

The MVA around Cologne-Bonn Airport is shown in the following map:

EDDK_MRVA.pngMVA Cologne-Bonn

Altitudes are in 100ft (20 = 2000ft). Figures in brackets are corrected for winter (NOV-MAR) for cold temperatures.

Standard Arrivals

The standard arrival routes for Cologne-Bonn start at five waypoints: KOPAG, ERNEP, GULKO in the east and DEPOK and NVO in the west.

EDDK_KOPAG.pngSTARs into Cologne/Bonn

For approaches via NVO (Nörvenich), this VOR is also the IAF from which various final approaches lead to the runways.

STARs for Runways 06 and 31L/R are routed from KOPAG, ERNEP and GULKO to COL (Cola). When operating Runways 13L/R and 24, the routes lead to WYP (Wyper).

Transitions: RNAV transitions to the final approach are published for all runways. Their use depends on the current traffic situation and should be flexible accordingly.

S-Transitions: An exception are the transitions with Designator S to Runway 13L. These extend deep into the approach airspace of Dusseldorf and are only used in real terms at night on the instruction of the controller. On VATSIM, these transitions should only be used in close coordination with the controller responsible for Düsseldorf in order to avoid conflicts with approaches and departures from Düsseldorf.

N-Transitions: The transitions with Designator N to runway 31R reaches with the base part into the sector Taunus TAU, which is usually served by Kitzingen KTG or Gießen GIN. The transition is also only used at night in real terms and its use on VATSIM should be coordinated with the controller responsible for TAU.

Potential Conflicts

Due to its size and the close proximity of approach and departure routes, the Cologne Arrival sector in the east of Cologne/Bonn has the greatest potential for conflict. Especially between the points KOPAG and COL near PODIP, several routes cross, so that special attention must be paid to the altitude separation there.

In the west, when using the STARs from DEPOK, care must be taken that they intersect with the departure routes to NVO between DEPOK and the airport. However, this point of conflict can be easily avoided by guiding approaching traffic early with vectors in the direction of the active runway and allowing departing traffic to fly out the SIDs.

EDDK_SIDSTARconflict.png

Crossing Runway Operations

It is important during crossing runway operations that the preceeding traffic (landing or departing) has crossed the runway cross before the succeeding traffic (landing) for the other runway has reached the 1 NM final. Otherwise the succeeding traffic has to go around.

Director has to ensure, that traffic cleared on the approach of crossing runways is separated in a way, that the preceeding traffic has passed the runway crossing point, before the succeeding traffic reached it's 1 NM final. Therefore it is necessary, that both aircraft are cleared on the approach, with at least 1 NM separation between each other, on the way to the runway crossing point.

Runway 13L/31R + Runway 24 Operations: Due to the shorter distance from the FAF (Final Approach Fix) to the crossing point between RWY13L/31R and RWY 06/24, arrivals on RWY 24 shall be declared as the preceeding aircraft whenever possible.