EDDL - Delivery
Düsseldorf Delivery is responsible for enroute and startup clearances for all departing IFR aircraft. VFR aircraft, except Police Helicopters, which call Tower directly, have to call Delivery for departure information.
Startup: Startup will normally be given when the pilot is ready for pusback and startup and not together with the IFR clearance. 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. If Delivery notices the holding point getting too crowded startup intervals shall also be increased.
Maximum active Startup Approvals at the same time (status SUG until DEP) per runway (use the vSID startup counter):
Single RWY OPS: 10
Parallel RWY OPS: 13
Depending on the traffic situation, only for a short time more startup approvals shall be used.
With startup Delivery transfers the aircraft to the responsible Ground station depending on the current stand.
Enroute Clearance
Runway 23L/05R is primary used for all departures. Delivery has to make sure that all SID restrictions are adhered to.
The SID MODRU #K shall only be assigned on pilots request when able to comply with climb restriction (9.5%) and RF-Legs. Prior coordination with Tower is mandatory. Decision on short notice to the pilot by Ground or Tower is possible, depending on the preceding traffic (see Tower section).
The SID NETEX #K, #Y, #X, #U are mandatory for flights to continue via NETEX DCT RASCA or NETEX DCT DELOM.
To ensure an efficient operation within the upper and lower airspace several restrictions should be met (check FPC column in Euroscope). To solve an invalid route, the pilot usually has to file a completely new route (valid routes for many destinations can be found on grd.aero-nav.com).
| SID | Route | Restrictions |
| COL | T911 |
Flights to Frankfurt (EDDF) via COL must file a Requested Flight Level between FL150 and FL230 to ensure a correct sector order |
| DODEN | Y853 Y852 |
Flights unable to comply with restrictions shall file via KUMIK |
| GMH | Z841 L603 |
RFL 140- |
| KUMIK | Y854 L603 |
RFL 150+ |
| LMA | Z282 | Only for flights to EDLN or local IFR (subject to coordination) |
| MEVEL | Z44 L179 Y850 |
23L/R: Max. 190kt IAS until on NOR Radial 001° |
| MODRU |
Z717 Z283 |
Cross MODRU FL 210 or above |
| NETEX | Z282 Z283 |
Not to be used if military airspace in the north of the EBBU FIR is active. Information about the activation of the military areas can be obtained from the EBBU controller. |
| NVO |
M170 Q760 |
RFL 90- Flights with RFL 100+ shall file via MODRU |
| NUDGO | Z858 | RFL 245- |
| SONEB | P55 P64 |
Visual Departure
Visual departures can be requested by pilots or offered by ATC when weather and visibility conditions permit. Visual departures are only permitted during daytime operations and require coordination between Delivery, Tower and Arrival. Reasons for the pilot to request a visual departure include weather avoidance or shorter routing for efficiency. Further information can be found here
Vectored Departure
Usually all RNAV capable aircraft that are available for flight simulators are able to fly a SID and most likely are looking for the wrong runway! If pilots nevertheless are unable to fly any SID (even an older version of the current SID or the LMA SID) a vectored departure can be coordinated between Delivery and Arrival. Usually runway heading and an initial climb of 5000ft will be used. Other coordinations are always possible. In the Departure/Startup List select the corresponding "RV" SID for this departure.
However, there is rarely a proper reason to fly a vectored departure, thus if a pilot requests this due to inability to fly any SID, question their capability to conduct IFR flight properly.
Local IFR
Local IFR flights are prefered via LMA SID (radar vector departure on request possible). Coordination with Arrival (DLA) prior enroute clearance as well as a startup release is required.
Local departures need to be advised to contact DLA on 128.555 immediately after departure.
Datalink Clearance (DCL/PDC)
At Düsseldorf Airport we offer Datalink Clearance to the pilots via the Hoppie System and the Topsky Plugin. The airport code EDDL 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 separately.
CLD 2042 220117 EDDL PDC 026 SAS461L CLRD TO EKCH OFF 23L VIA MEVEL4T CLIMB 5000 SQUAWK 2055 ADT MDI NEXT FREQ 121.780 ATIS H REPORT READY ON 121.780
High Traffic at EDDK
During high inbound peaks into Cologne with 13 operations, Cologne Approach may use the Düsseldorf Approach sector. Therefore traffic departing Düsseldorf out of runway 23L/R to the south (COL, DODEN, NUDGO, GMH, KUMIK, NVO) require a startup release by Düsseldorf Approach.
In case of startup delays, it might be useful to clear outbounds to the south via MEVEL SID and radar vectors to the filed first waypoint (no clearance via datalink for that). Additional coordination with APP required when this procedure should be used!
... cleared XXXX via MEVEL4T, expect radar vectors to DODEN/KUMIK/NUDGO/COL/NVO, flight planned route...
When the MEVEL SID is used, the flightplan need to be amended accordingly (e.g. "MEVEL DCT DODEN")
vSID: Use the alias command ".nosouth<space><enter>" to disable the automatic vSID assignment for outbounds to the south.
SIDs via "MEVEL DCT XXXXX" are highlighted.