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).With AIRAC 2404, the runway designators in Köln/Bonn were changed from 14/32 to 13/31. This can cause issues for pilots using MSFS if they are using AIRAC 2404 or later but have a scenery with the old designators as **they will not be able to select certain runway-specific procedures such as the SID** in their FMS. If a pilot reports this issue, **please refer them to [this addon](https://dms.vatsim-germany.org/s/PXXa3gKYbb2Exkx "EDDK compatibility fix")** which will allow them to select runway-specific procedures even with an outdated scenery. Whenever possible, **controllers should find workarounds that do not require pilots to restart their simulator**, e.g. using a conventional SID to NVO or WYP, potentially followed by radar vectors.
### 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](https://moodle.vatsim-germany.org/course/view.php?id=79 "Course EDDK (VATGER moodle)") |
| **Ground** | DKG | EDDK\_GND | 121.730 | -- | unrestricted: [EDDK CBT Delivery & EDDK CBT Ground](https://moodle.vatsim-germany.org/course/view.php?id=79 "Course EDDK (VATGER moodle)") |
| Apron | DKGP | EDDK\_P\_GND | staffing forbidden | staffing forbidden | |
| **Tower** | DKT | EDDK\_TWR | 124.980 | -- | Tier 1: [EDDK\_TWR](https://core.vateud.net/my/endorsements "Your endorsements (VATEUD Core)") |
| **Approach** (Pickup) | DKA | EDDK\_APP | 135.350 | -- | Tier 1: [EDDK\_APP](https://core.vateud.net/my/endorsements "Your endorsements (VATEUD Core)") |
| Arrival (Feeder) | DKAT | EDDK\_F\_APP | 121.055 | -- | Tier 1: [EDDK\_APP](https://core.vateud.net/my/endorsements "Your endorsements (VATEUD Core)") |
| Nörvenich sector | NOR | EDDK\_NOR\_APP | 127.365 | Tier 1: [EDDK\_APP](https://core.vateud.net/my/endorsements "Your endorsements (VATEUD Core)") |
Staffing of Apron (DKGP/EDDK\_P\_GND) is **currently prohibited**.
### Controlzone [](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2022-10/eddk-ctr.png)*Cologne-Bonn Controlzone (D-CTR) - © [openflightmaps.org](https://www.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. [](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2022-09/wLxgrafik.png)*Departure 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 31L:** - Designators **K** (RWY 06), **D** (RWY 24) and **M** (RWY 31L) are the available RNAV departures. **Runway 13L:** - **Designator F** is prefered for all RNAV departures. - **Designator Q** requires RNAV and RF-Legs capability and should be used only if filed by the pilot or on request. - **Designator X** is only used for 3-engines heavies (e.g. MD11). - **NVO#P** is used for departures unable to comply with the climb restriction on the F or Q SID. - **NVO#W** by ATC only and requires prior coordination with Radar as the SID will cross 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 13R:** - **Designator E** is prefered for all RNAV departures. - **NVO#C** is used for departures unable to comply with the climb restriction on the E SID. - **NVO#V** by ATC only and requires prior coordination with Radar as the SID will cross 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 31R:** - **Designator B** is prefered for RNAV departures **above 98t MTOW** (e.g. B757). - **Designator R** is used for all RNAV capable outbounds with **MTOW below 98t** as well 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 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 [](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-04/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). ### Datalink Clearance (PDC/DCL) At Cologne-Bonn Airport we offer Datalink Clearance to the pilots throughout the **[Hoppie System](https://www.hoppie.nl/acars/)** 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. Due to plugin limitations, the current default setting is "startup approved"; the **Startup option in the DCL window shall be set to "No" for every DCL** as pilots need to request startup separately on frequency. Other DCL messages can be enabled within the Topsky CPDLC settings file manually.CLD 1051 240418 EDDK PDC 012 EWG6TG CLRD TO LEPA OFF 13L VIA KUMIK2Q SQUAWK 1000 ADT MDI NEXT FREQ 121.855 ATIS R REPORT READY ON 121.855
### vSID Rules The following alias commands (.command**<space><enter>**) can be used to toogle vSID rules.| **Alias** | **vSID Command** | **Description** |
| **.high** | .vsid rule eddk high | all L/M outbounds will get runway 13R/31L for departure. |
Staffing of Apron (DKGP/EDDK\_P\_GND) is **currently prohibited**.
### Airport layout Cologne-Bonn airport has three crossing runways. [](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2022-09/eddk-overview.png)*airport 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. [](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2022-09/eddk-apr.png)*Apron 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. [](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2022-09/eddk-aor.png)Area 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. [](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2022-09/eddk-twy.png)Taxiways 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. - During 31-Operations, A3 is the first suitable highspeed-turnoff for landing traffic. Due to the speed of landing and vacating aircraft, they often fail to stop short off E and continue through to A. - Another critical situation occurs, in the case of 24-departures. 24-departures need to cross RWY 31R at A3. Whenever traffic is instructed to taxi in the direction of the A3 holdingpoint, Ground needs to coordinate with Tower and inform him about the traffic, as TWR needs to inform landing pilots, that A3 is unavailable to vacate the RWY. **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. [](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2022-09/eddk-risk.png)*Potential 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. [](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2022-09/eddk-ctr.png)*Controlzone 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*](https://aip.dfs.de/BasicVFR/pages/P0034A.html) **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 |
**Example:** Departing traffic runway 31R has passed the runway cross before the inbound reaches 1 NM final for runway 24.
### Nörvenich sector A If the military approach sector for Nörvenich (ETNN) has activated sector A, **NVO SIDs out of runways 24 and 31 may no longer depart**. Usually, this sector will only be active for short periods of time to allow TNNA to vector arriving traffic to final approach during 24 operations at ETNN; however, when there is local IFR traffic at ETNN, the sector may be activated for longer periods and NVO outbounds should be recleared to runway 13 or, after coordination with DKA, on a different SID (e.g. WYP) to expect vectors to NVO after departure. **DKA** (or TNNA, if DKA is offline) **will inform Tower when sector A is activated and deactivated**. ### 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.| [](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2022-09/dka.png) | [](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2022-09/dkf.png) |
| *Area of Responsibility Arrival* | *"Area of Responsibility" Feeder (dark yellow)* |
| [](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2022-09/nor.png) | [](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2022-09/norup.png) |
| *Area of Responsibility Sector Nörvenich* | *Area of Responsibility Sector Nörvenich* |