Stuttgart Delivery is responsible for enroute and startup clearances for all departing IFR aircraft. VFR aircraft have to call Delivery for departure information. For all departures (IFR and VFR) Stuttgart Delivery is the first station to contact, except for police helicopters, which may also contact Ground initially.
The initial climb out of Stuttgart is always 5000ft!
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.
Both Arrivals are staffed: If both Arrivals are staffed, Delivery needs to inform all south departures (via ROTWE, SUL and KUNOD) to contact 119.200 immediately after departure with the enroute clearance. For all other departures the ATIS remark remains valid and no additional information is required.
Local IFR: Local IFR flights are possible via TEDGO and STG but need to be coordinated and require a startup release by Arrival or Feeder, if online. When Feeder is online, local departures need to be advised with enroute clearance to contact 119.850 immediately after departure. Departures intending to fly local IFR at EDTY also require a startup release by Arrival (STG).
A Quicksheet with SID and climb restrictions is available here.
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.
If pilots are not able to fullfill the required climb restrictions for their SID or to save taxi time and shorten the departure (especially during 25 operations for outbound flying to the east), opposite departures against the operating direction are possible. These departures always have to be coordinated with Tower and Arrival and need a startup and departure release by Arrival.
Datalink Clearance (PDC/DCL)
At Stuttgart Airport we offer Datalink Clearance to the pilots via the Hoppie System and the Topsky Plugin. The airport code EDDS should be used (already preselected).
An example of the DCL message the pilot will receive can be seen below. It's important that the current ATIS Designator will be entered via the remarks. By default startup always needs to be approved separately.
CLD 2042 220117 EDDS PDC 026 SAS461L CLRD TO EKCH OFF 25 VIA OKIBA4B CLIMB 5000 SQUAWK 2037 ADT MDI NEXT FREQ 121.900 ATIS H REQUEST STARTUP ON 121.900
Stuttgart has a maximum capacity of 35 departures or arrivals per hour. In total 48 movements per hour are possible. If startup needs to be delayed due to runway capacity (e.g. during events), one startup clearance can be issued every 2 minutes. Average taxi time (incl. pushback) to runway 25 is 15 minutes, while only 10 minutes are required for runway 07.
Due to a lot of different route planning tools, some non valid routes out of Stuttgart exist. To ensure an efficient operation within the upper and lower airspace several restrictions should be met if workload permits. To solve the issue, usually a completely new route has to be filed! Therefore grd.aero-nav.com can be used. All restrictions can be found in the table below.
|DKB||only via N869 or DEST EDDN, EDTY, EDQ*|
|ETASA||only DEST EDDF, EDFC, ETOU, EDFE|
|GEBNO||only via Z76, max. RFL FL180|
|KRH||only DEST EDDR, EDRZ, EDSB, ETAR, max. RFL FL80 (Mo - Fri)||other DEST via VESID [...]|
|OKIBA||min. RFL FL200|
|ROTWE||if jet: only via N850 NATOR||reroute Prop via SUL Y125 NATOR|
|STG||only local IFR|
|SUL||if jet: only DEST EDTL, EDNY, LSZH, LSZR||reroute Jet via ROTWE [...] N850 NATOR|
|TAGIK||only via ABUMO/ASKIK, max. RFL FL240|
|TEDGO||only local IFR + DEST ETHL|