Skip to main content

Tower

Dresden Tower is responsible for the runway and traffic within the Dresden CTR.

Also check the ARR SOP to familiarize yourself with arrival procedures relevant for tower operations to enable the necessary coordination with Sachsen.

Control zone

The Dresden control zone extends approximately north of the city of Dresden. The vertical boundary of the CTR is 2500 ft MSL. Entries into and exits from the control zone are made via the mandatory reporting points:

  • West: November, Mike, Charlie
  • East: Echo, Tango

EDDC_CTR.pngCTR Dresden - © openflightmaps.org

Arriving traffic

Dresden Tower is responsibil for the runway. As the pilot leaves the runway, the tower transfers the pilots to the apron frequency at A, B, and C, and to the ground frequency at D and E.

  • Generally, the responsibility for separation of flights subject to separation in CTR Dresden (Airspace D) lies with Tower.
  • The responsibility for separation of IFR-Arrivals on Final (not Visual Approach) lies with Sachsen.
    After Transfer of Communication, Dresden Tower shall monitor separation and (if necessary) shall take appropriate measures to maintain separation. Suitable measures are for example speed reductions (requires coordination with Sachsen) or GA procedures. 

Opposite landings

Sachsen may request that aircraft be allowed to land against the direction of operation in order to shorten flight and taxiing times. Departing traffic and VFR traffic may object to this, idividual coordination and consulting are helpful.

If this occurs, all taxiways must be kept clear to the runway!

Low visibility procedures (LVP)

Dresden Airport has CAT III only on runway 22. This means that runway 22 must be used for low visibility procedures. In addition, pilots always leave the runway at the end via taxiway A.

Departing traffic

Auto-Handoff

Dresend utilizes an auto-handoff procedure for IFR departures where tower will not hand off outbounds to the approach controller. Make sure to set the correct departure frequency in the ATIS.

Outbounds should contact APP immediately when airborne unless explicitly told to remain on tower frequency.

Opposite departures 

Departures against the current operating direction always require a departure release by Sachsen (EDDC_SAS_APP), if online, and otherwise by Thüringen (EDDP_TRS_APP). A rule of thumb for when such a release can usually be expected is when the next inbound is at least 20 NM from touchdown. 

Back to top