Skip to main content


All sectors for Berlin Departure are dependent on the runway configuration at Berlin-Brandenburg Airport (BER/EDDB).

  • If there is only one Arrival online, all other stations (incl. Departure and Director) will also be covered.
  • A second Director shall only be manned and booked with the approval of the person already staffing the main Director station.

DBA 07.pngDBA 25.png

Runway Assignment

Runways are assigned on initial contact with Berlin Arrival according to the procedures below:

"Standard Runway Assignment Procedure"


Runway 07L/25R:

  • All aircraft parking north of gates B05 and D08 
  • All aircraft parking on apron Echo

Runway 07R/25L:

  • All aircraft parking south of gates B04 and D07
  • All aircraft with a wingspan of 65 m or more (A388, B748, A225)

"Alternative Runway Assignment Procedure"

Might be useful during Independent Parallel Operations. Before using this procedure coordinate with all surrounding stations.

Runway 07L/25R:

  • All aircraft with parking positions north of VM
  • All aircraft parking on apron Echo

Runway 07R/25L:

  • All aircraft with parking positions south of VM
  • All aircraft with a wingspan of 65 m or more (A388, B748, A225)


  • Transitions are assigned only when necessary. The transition designator depends on the assigned arrival runway.
  • Sequencing of arriving aircraft is not done by Center. It's the responsibility of Berlin Arrival to sequence all aircraft on downwind.
  • Early coordination with Center might be helpful (Headings, Speeds, Directs)

Airspace Procedures

  • All aircraft shall stay inside protected airspace (airspace C or D) at any time.
  • ED-R 146 and ED-R 4 are active 24h
  • Arrivals and departures are separated at all times as long as they stay inside the corresponding arrival or departure airspace
  • Any approved/requested DCT for arrivals EDDB, given by DBAN/DBAS to MAR/FLG, shall include the approval to cross the airspace of sectors DBDN/DBDS!
  • Arrivals EDDB via RODEP-T280-KETAP are also released for descent and turn from sector MRZ to sector DBAN.

Noise Abatement

  • Arrivals to EDDB shall not be cleared to descend below FL70, (or below the cruising level, if lower than FL70) before passing a position abeam EDDB if guided north of the aerodrome but south of the direct line between OGBER and KETAP, unless required for separation or other safety-related reasons. 
  • For all arrivals, the distances flown below FL70 shall be kept as short as required for ensuring a safe, orderly and efficient operation. All surroundings of the airport are to be considered noise sensitive. 
  • Vectored approaches to RWYs 07L/R shall be guided in a way that the aircraft is established on the final approach track 13 NM from the touchdown between 22:00 local time and 06:00 local time. Aircraft in an emergency or distress situation or an urgent exceptional situation (e.g. meteorological reasons) as well as visual approaches shall be exempted from this provision.
  • Whenever issuing a clearance for a visual approach to RWYs 07L/R or 25L/R the pilot shall be instructed to conduct the approach in such a way that the final approach is not less than 6 NM and descent below 2000 ft MSL will not be performed prior to reaching final approach.


  • ATGUP and KLF Holdings are not independent and have to be separated
    • It is useful to only use one Holding for both waypoints (coordination with ACC Sector FLG)
  • Aircraft are always handed over vertically by Center (FL120 to BerlinArrival)

Modes of Operation

  • Standard Operation Mode: Dependent Parallel Approaches (3 NM diagonal)
  • Medium-High Traffic Operations Mode: Dependent Parallel Approaches (1,5 NM diagonal)
    • Reduction of diagonal separation to 1,5 NM needs to be coordinated with Tower prior to applying
  • Very High Traffic Operations Mode: Independent Parallel Approaches
    • Independent Parallel Approaches Operations are only permitted when N_TWR and S_TWR are staffed, in addition, F_APP and D_APP need to be controlled by different controllers
    • Coordination with Berlin Tower is necessary when switching to Independent Parallel Approaches

Further information here: EDDB/EDDP - Airport Betriebsmodus

Reduced diagonal separation

A reduced diagonal separation of at least 1,5 NM may be used during dependent parallel approaches.  

  • Prior coordination between APP and TWR of reduced separation is necessary
  • Pilots need to be informed via the ATIS (&pda)
  • Both aircraft have to be established 
  • Reduced separation is only allowed between the threshold and 10 NM final

Two Feeder Operation

The following rules apply when two Director stations are online:

  • Independent Parallel Approaches shall be used
  • Feeder North (F_APP) is responsible for aircraft approaching runway 07L/25R
  • Feeder South (D_APP) is responsible for aircraft approaching runway 07R/25L

Intercept during Independent Parallel Operations

  • Runway 07L/25R
    • Intercept: 5000ft via at least 18 NM final
  • Runway 07R/25L:
    • Intercept: 3000ft via at least 15 NM final or 4000ft via at least 18 NM final
    • Pay attention to the MVA when using 3000ft!

Handoff to Director

DBAN/DBAS shall guide arrivals to EDDB in such a way that an interim arrival sequence is reached prior to transferring the aircraft.

During Dependent Parallel Approaches:

  • 5000ft, or higher after coordination

During Independent Parallel Approaches:

  • Runway 07L/25R: TRL
  • Runway 07R/25L: 5000ft

Target Spacing

  • Target Spacing on both runways is 5-6 NM in order to have at least one departure between two arrivals
  • Target Spacing can be reduced after coordination with Berlin Tower
    • Reduced diagonal separation (see above) will result in a reduction of target spacing and therefore needs to be coordinated with  Berlin Tower

Low Visibility Procedures (LVP)

  • Single Use of Runway mandatory (25R/07R for landings, 25L/07L for departures)
  • Minimum spacing 5NM at touchdown

Berlin Arrivals Coordinator

  • When EDDB_Q_APP (DBAQ) is online, this station will take over all inbound coordination (tag and verbal) as well as inbound planning for both Arrival North (DBAN) and Arrival South (DBAS)
  • Both DBAN and DBAS shall not coordinate flights with CTR. This is the only responsibility of DBAQ.
  • DBAQ shall use all required methods of pre-planning/coordination in order to prepare all inbound flights for DBAN/DBAS in such a way that a safe and efficient flow of traffic is ensured at all times.
  • Due to the limitation of Euroscope, DBAQ will receive all tags from CTR. Once the tag transfer is initiated from CTR, DBAQ shall immediately transfer this tag to DBAN or DBAS. DBAN/DBAS will then assume the tag once the pilot called in on the frequency.
  • DBAQ will not use any frequency or control aircraft in any way. Transfer of control belongs to DBAN/DBAS.


Berlin Arrival (DBAN / DBAS) will always clear the approach procedure at EDAY and EDAZ. The aircraft shall be transferred by DBAN / DBAS on the procedure for supervision, in the following situations:

  • EDAY inbound during EDDB 07 Ops: to DBDN
  • EDAZ inbound during EDDB 07 Ops: to DBAST
  • EDAZ inbound during EDDB 25 Ops: to DBDS

Individual coordination with DBDS/DBDN/DBAST (depending on runways in use) is required before clearance of approach by DBAN or DBAS (excl. at EDAY during EDDB 25 Ops)!

Strausberg (EDAY)

ATC Service by Berlin Arrival North (DBAN)


  • Only during 25-Ops
  • IFR Clearance when Strausberg Information is offline
  • No ATC Service provided on the ground
  • Initial climb instructions need to be coordinated with Berlin Arrival


  • Only during 25-Ops
  • Supervision of traffic on the published procedure only
  • Clearance for the RNP approach will always be done by Berlin Arrival
  • No ATC Service provided on the ground (incl. landing clearance)

Schönhagen (EDAZ)

ATC Service by Berlin Director South (DBAST)


  • Only during 07-Ops
  • IFR Clearance when Schönhagen Information is offline
  • No ATC Service provided on the ground
  • Initial climb instructions need to be coordinated with Berlin Arrival


  • Only during 07-Ops
  • Supervision of traffic on the published procedure only (potential conflicts with departures)
  • Clearance for the RNP approach will already be done by Berlin Arrival
  • No ATC Service provided on the ground (incl. landing clearance)
  • Report aircraft being on final to Berlin Tower (because of dependencies)

As soon as an arriving aircraft to EDAZ is about to pass AZ255, approaches on runway 25L in EDDB are prohibited. Berlin Tower shall be informed about EDAZ Inbounds at least 10 minutes prior to approach clearance at MOSEX. Aircraft at Berlin can still depart out of 25L as long as they can guarantee a good climb rate after departure. 


Holzdorf is a military airport south of EDDB within Berlin Arrival. Holzdorf airport has a military area of responsibility (ETSH_APP) from GND-5500 MSL. Holzdorf radar will inform Bremen Radar (Berlin Arrival) about the activity of this AoR. In case the AoR is not active, Berlin Arrival shall provide top-down services at ETSH.

All aircraft from/to ETSH have to coordinated individually between Holzdorf Radar and Bremen/München Radar

As soon as AoR Holzdorf is active, ACC Sectors Thüringen Low North (TRN) and Sachsen Low (SAS) shall be informed about the activity of Hozdorf Radar.


Release Areas


  • GND - FL105 (If Holzdorf AoR active: 5500 MSL - FL105)
  • Delegation from DBAS to TRN/S
  • Only for EDDP inbound traffic during RWY 26 Ops

Activation only by DBAS on request from TRN.


Berlin-Tegel and Berlin-Tempelhof

The airports of Berlin-Tegel and Berlin-Tempelhof are closed. Traffic inbound to these airports is required to cancel IFR. Outbound aircraft have to perform an IFR-Pickup.