# Delivery **Initial climb clearance:** The initial climb clearance at Hanover is 4000ft on all published departure procedures. The altitude shall be entered as cleared altitude (CFL) in an appropriate list or tag. **PDC:** The use of PDC (Pre Departure Clearance) is permitted in Hannover, but not mandatory. The code "EDDV" shall be used. Pilots are advised to enter the requested departure runway in the Optional Free Text field of the DCL dialogue. When using startup times, keep in mind not giving “startup approved” in the PDC clearance. ### SIDs
**SID** | **27L** | **27R** | **09L** | **09R** |
---|---|---|---|---|
**CEL** *Celle* | 8F | 6S | 6Y | 9G |
**MULDO** | 8F | 6S | 5Y | 6G |
**NIE** *NIENBURG* | 7F | 9S | 1Y | 7G |
**POVEL** | 3F | 3S | 2Y | 2H |
**VAXEV** | 1F | 1S | 1Y | 1G |
**WRB** *WARBURG (\*)* | 8F | 3S | 3Y | 1G |
**WERRA** | 3F | 3S | 3Y | 3G |
(\*) Note: For traffic with destination EDDF all WRB SIDs will end at TOLTA.
### Runway Assignment The departure runway mainly depends on the aircraft type and the pilots preference. - Heavy aircraft (e.g. A332, B748, B763) shall depart from runway 09L/27R - *avoid* crossing departures: northbound departures should depart from 09L/27R - RWY Config 09: VAXEV departures should depart from runway 09L - RWY Config 27: MULDO departures should depart from runway 27R Delivery is responsible for an appropriate runway assignment, so each runway has an equal workload. ### Low Visibility Operations (LVO) At Hannover, the following runway configuration is to be used during LVO: - Departures 09R/27L\*, Arrivals 09L/27R Departures may request runway 09L/27R for performance reasons. In this case, a larger arrival spacing shall be by Tower requested to accommodate the departing traffic in between.\* Note: Runway 09R/27L can only used for departing traffic if the RVR is not less than 350 m. If the RVR is below 350 m, runway 09L/27R shall be the only runway in use for both departing and arriving traffic.
### Delays and Startup **Delay of traffic:** In high traffic situations, it may be necessary for departing traffic to be held back. In addition, Delivery shall make arrangements to comply with restrictions imposed by other airports through notice on the ECFMP Discord, coordination, etc. **Startup:** A startup shall be granted if no major traffic delays are expected. When allocating startups linked to times, the airport specific rate of 40 departures per hour can be used as a basis. ### Specials **Vectored departures:** The use of vectored departures requires prior coordination with the responsible radar station. An initial altitude to climb shall be provided. **IFR local flights:** IFR local flights are coordinated with the responsible radar controller, who may instruct a different departure procedure, possibly vectored departures. ### vSID Plugin Commands The following plugin commands for vSID are available at EDDV:**Command** | **Explanation** |
.vsid rule eddv low (disabled by default) | When enabled, runway 09R/27L will be preferred for all medium and light aircraft (disregarding the standard runway assignment). |
.vsid area eddv gat | This will clear all aircraft at the GA-Aprons according to the standard runway assignment (09L/27R will not be preferred anymore). |