EDDL - Delivery

Düsseldorf Delivery is responsible for enroute and startup clearances for all departing IFR aircraft. VFR aircraftaircraft, except Police Helicopters, which call Tower directly, have to call Delivery for departure information.

ForStartup: allStartup departureswill (IFRnormally be given when the pilot is ready for pusback and VFR)startup Düsseldorfand 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 isfrequency until he receives startup clearance. If an expected startup time (TSAT) exists, the firstpilot 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 todepending contact,on exceptthe forcurrent police helicopters, which may also contact Tower initially.stand.

Enroute Clearance

Standard Instrument Departures

Runway 23L/05R (SID Designator T and Z) is primary used for all departures. Delivery has to make sure that all SID restrictions are adhered toto. (Euroscope will display if a route is not correct).

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). 

(subjectavailable at night between 2200LT and 0600LT and during weekends and holidays due

SID	Route	Restrictions
Waypoint	Restriction	Climb
COL Cola	--T911	climbFlights to Frankfurt (EDDF) via COL must file a Requested Flight Level between FL150 and FL230 to ensure a correct sector order
DODEN	Y853 Y852	min. RFL 260 flightsFlights unable forto climbcomply with restrictions (see charts) shall refilefile via KUMIK	climb via
GMH Germinghausen	max. RFL 140Z841 L603	climbRFL 140-
KUMIK	min. RFL 150Y854 L603	climbRFL via150+
LMA Lima	DESTZ282	Only for flights to EDLN only or local IFR flights	climbto coordination)
MEVEL	--Z44 L179 Y850	23L/R: 23Max. Ops:190kt climbIAS via until 05on Ops:NOR climb Radial 001°
MODRU	min. RFL Z717 210 Z283	climbCross viaMODRU FL 210 or above
NETEX	OnlyZ282 Z283	Not to be used if military airspace in the north of the EBBU FIR.FIR is active. Information about the activation of the military areas can be obtained from the EBBU controller.	#U, #K: climb via all other: climb
NVO	M170 NörvenichQ760	max. RFL 9090- flightsFlights with RFL at or above FL100100+ shall refilefile via MODRU	climb
NUDGO	max. RFL 240Z858	climbRFL 245-
SONEB	--P55 P64	climb via

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. Alternatively the LMA SID can be used with vectors/direct to the first waypoint. 

Usually runway heading and an initial climb of 5000ft shouldwill be used. Other coordinations are always possible. SelectIn 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 startupevery alwaysoutbound needshas to becall approvedDelivery separately.for startup.

CLD 2042 220117 EDDL PDC 026 SAS461L CLRD TO EKCH OFF 23L VIA MEVEL3TMEVEL4T CLIMB 5000 SQUAWK 2055 ADT MDI NEXT FREQ 121.780 ATIS H REPORT READY ON 121.780

Startup

When startup clearance cannot be given immediately or the pilot is not ready for startup within the next 5 minutes, the pilot needs to stay on Delivery frequency until they receive their startup clearance.

Runway Capacity: To ensure smooth operations and an acceptable level of workload for following stations, Delivery has to ensure an appropriate startup rate. This can either be achieved by use of the vACDM plugin, or by adhering to a number of maximum startup clerances.

Delivery should ensure that not too much outbounds in the same area receive startup at the same time.

Maximim active Startup Approvals at the same time (status SUG until DEP) per active runway (use the vSID startup counter):
One active runway: 10
Two active runways: 13

Outbound Taxi Times: The average time between startup approval and takeoff clearance is 10 - 15 minutes during 05 operations and 15 - 20 minutes during 23 operations. 

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 usefulluseful 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.