Departure

All

Sectorization sectorsand forAirspace

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

• If there's only one Departure station online, the other Departure sector will also be covered
• A second Departure controller should only connect with approval from the controller already being only. The same applies to position bookings.
  
• Berlin Departure shall cross-couple both frequencies at any time.
• All handoffs to APP/DEP shall be performed to the "correct" (/cross-coupled) sector frequency.

Procedures 07-Ops

Departure Routes

07R

Station	Station ID	Frequency	Login
SIDsBerlin 07LDeparture Nord	DBDN	120.340	SIDsEDDB_N_DEP
Berlin Departure Süd	DBDS	120.630	EDDB_S_DEP

Both

• frequencies shall be cross-coupled by the responsible controller. 

  Airspace

  All active ED-Rs displayed on the radar screen shall be simulated. ED-R4 and ED-R146 will be active 24/7.

  Departing trafficTraffic from differentEDDB

  departure

  Modes of Operation

  Independent Parallel Departures

  Independent parallel departures shall always be used, except if the following requirements are not met:

  REQUIREMENTS AND PROCEDURES FOR INDEPENDENT PARALLEL DEPARTURES

  1. Parallel runways ismay be used for independent asinstrument longdepartures as follows:
     
     1.  both runways are used for mixed arrivals and departures (mixed operation).
        
     2. Independent IFR departures should only be conducted from parallel runways when the conditions listed below are met:
        1. both aircraft are onflying aan publishedRNAV procedureor (vectoredRNP instrument departure and
        2. ATS operational procedures ensure that the required track divergence is achieved.

  In case departing traffic deviates from the departure route, the responsible tower controller needs to create separation immediately. 

  Note: Vectored and visual departures are not publishedapproved procedures!)for independent parallel departures

   

  SUSPENSION OF INDEPENDENT PARALLEL OPERATIONS DUE TO METEOROLOGICAL CONDITIONS:

  The meteorological conditions to be considered include, but are not limited to, the following:

  1. wind shear;
  2. Itturbulence;
  is
  3. downdrafts; Tower'sand
  responsibility
  4. crosswind and significant meteorological conditions such as thunderstorms, which might otherwise increase deviations from the final approach course or track to assurethe enoughextent separationthat betweensafety Qmay andbe Zimpaired.
  /

  B
  and

  Dedicated KRunway SIDs.
  Operations (DROps)

  In Berlin, dedicated runway operations will be used during the following conditions:

  • Low Visibility Procedures
  • Suspension of Independent Parallel Departures (e.g. due to CB, wind shear, turbulence, downdrafts, strong crosswind)
  • Special regulation of traffic flows (e.g. shuttle event)

  Special

  For Procedures

  Berlin, the following runway configurations are preferred for dedicated runway operations:
  • 07-Operations: 07L departures, 07R approaches
  • 25-Operations: 25L departures, 25R approaches

  Departure Release

  Hoffmann-Kurve
  DueDepartures do not have to noisebe abatementreleased proceduresby aircraftBerlin followingDeparture aunless:
  

  Q-
  • Berlin Departure explicitly restricts departures by time, SID or until further notice
  • Departures out of the non-operational runway 07Rconfig
  will
  • The performfirst departure after a runway change
  • The first departure after an unplanned missed approach
  • After every departure route with the famousdesignator "Hoffmann-Kurve"K, M or Z

  Crossing Departures

  As traffic may be departing independently parallel from EDDB, Berlin Departure is responsible for managing crossing departures (e.g. LOGDO1A vs. SUKIP2N). AircraftClose operatorscoordination arewith ACC sectors BOR, FLG and MAR is required to flycross andepartures earlyefficiently. rightOften, turnit is necessary to thelevel south after passing 600ft. Berlin Tower will transfer those aircraft as soon as they are established on the crosswind leg. 

  Berühmte Berliner Hoffmann-Kurve

  Departing traffic following the LOGDO 1Q or SUKIP 1Q will have an initial climb of FL080. Special climb gradients are required in order to stay clear of arriving traffic.

  DBAS4 Airspace
  During 07-Ops Departure South will have a special delegated airspace inside the sector of Berlin Arrival South. This will ensure thatoff departing traffic staysto clearensure ofseparation anyduring airspacecrossing. ofIt Berlinmay Arrival.also Thisbe delegated airspace is known as the "DBAS4 Window".

  Sector DBAS 4

  ED-R 146
  Aircraft flying on the SUKIP 1K or LOGDO 1K are excluded from the flight restriction of ED-R 146. Departing traffic with an RFL below FL105 hasuseful to beassign transferredheadings to Berlin Arrival North (DBAN).

  Kreuzende Directs
  Pay special attention to departing aircraft flying through the DBAS 4 Window (see above). It has to be assured thatlet departing traffic will not leave this window below FL105 when getting a direct routing, in order to keep departing traffic clear of arriving traffic.

  Potential Conflict Departures - Arrivals

  Procedures 25-Ops

  Abflugrouten

  SIDs 25L	SIDs 25R

  • Departing traffic from different departure runways is independent as long as both aircraft are on a published procedure (vectored departures are not published procedures!)
    

  Special Procedures

  Parallel Departures to the West
  During 25-Ops you will often face SUKIP and LOGDO departures flying parallel. It might be necessary to let the aircraft cross beforemore performingexpeditiously. the handover to the next station. It is helpful to do the crossing at low altitudes (earliest above 5000ft). Pay special attention to vertical separation.

  Direct DB433
  Usually, arriving traffic via OGBER will get a direct instruction to DB433. This crosses the airspace of DBDN and therefore needs a general or individual release for Berlin Departure. This normally doesn't cause any major conflicts because traffic will cross DBDN's airspace only at a tiny bit, in the vicinity of ED-R 146.

  Handoffs from Departure to Center

  Traffic on the same or crossing departure routes needs to have at least a minimum separation of 53 NM before handoff to Center.the ItACC might be necessary to give level-offs to aircraft to ensure separation during crossings.

  (Potential) Conflicts shall not be transferred to Center at any time!sectors.

  Use the LoA for details on level agreements: https://knowledgebase.vatsim-germany.org/books/bremen-fir-edww/page/bremen-acc-internal 

  AfterDepartures coordinationEDDB withon SectorSUKIP BOR,SIDs departuresshall viabe transferred depending on the following airway:
  - SUKIP Y206 BUREL shall be transferred to sector BOR
  - SUKIP M748 SOGMA mightshall be transferred to Sectorsector MAR.MAR

  Departure-Split

  During a departure split, both sectors are not allowed to give instructions to aircraft to cross the other's sector. Coordination is always necessary!

  Check the LoA for the handoff level between DBDN and DBDS: https://knowledgebase.vatsim-germany.org/books/bremen-fir-edww/page/bremen-acc-internal 

  Tactical Directs

  Tactical Direct	Special Conditions	From Sector	To Sector
  HLZ	Only during 25-Ops	DBDN	BOR
  BUREL	Only during 07-Ops
  POVEL	-
  PODER	Only with Destination EDDK and RFL above FL245
  DENOL	Only with Destination EDDL/EDLV and RFL above FL245
  MAG	-	DBDS
  ODLUN	-
  MAXAN	-
  ARSAP	-		FLG

  Departure-Split

  During a Departure-Split, both sectors are not allowed to give instructions to aircraft to cross the other's sector. Coordination is always necessary!

  Check the LoA for handoff level between DBDN and DBDS: https://knowledgebase.vatsim-germany.org/books/bremen-fir-edww/page/bremen-acc-internal 
  

  Noise Abatement

  Due to Noise Abatement Procedures, it is only possible to turn aircraft off the published procedure when above a certain altitude.

  • Jets: 5000ft
  • Props: 3000ft

  Strausberg/Schönhagen

  Missed Approaches

  Missed approaches are being transferred from Berlin Tower to Berlin Departure. The departure controller shall coordinate the further routing immediately, once informed by Tower about the missed approach.  

  Strausberg (EDAY)

  ATC Service by Departure NorthStrausberg (DBDN)

  EDAY)

  Departuresis an uncontrolled aerodrome located about 20 NM northeast of EDDB. Due to published IFR procedures limited service has to be provided for IFR traffic:

  • OnlyApproach duringclearance 07-Opsand approach monitoring
  • IFR Clearance when Strausberg Information is offline
  • No ATC Service provided on the ground
  • Initial climb instructions need to be coordinated with Berlin Arrivalclearance

  Responsible stations

  Conditions	EDDB RWYs 07	EDDB RWYs 25
  IFR clearance	DBDN	DBAN
  Approach clearance	DBAN	DBAN
  Approach monitoring	DBDN	DBAN

  Approach Types

  ArrivalsThere is one published approach type available at EDAY: 

  • Only
  during07-Ops
  • Supervision

  Runway	Available ofApproach trafficTypes	IAF	Altitude at IAF
  05/23	RNP	RENKI	4000 ft

  Coordination is required with the station responsible for the approach monitoring prior to the approach clearance from DBAN. Airacft will be transferred to this monitoring station when on the published procedureprocedure. only

  Schönhagen (EDAZ)

  Schönhagen (EDAZ) is an uncontrolled aerodrome located about 15 NM southwest of EDDB. Due to published IFR procedures limited service has to be provided for IFR traffic:

  • Approach clearance and approach monitoring
  • ClearanceIFR clearance

  Responsible stations

  Conditions	EDDB RWYs 07	EDDB RWYs 25
  IFR clearance	DBAST	DBDS
  Approach clearance	DBAS	DBAS
  Approach monitoring	DBAST	DBDS

  Approach Types

  There is one published approach type available at EDAY: 

  Runway	Available Approach Types	IAF	Altitude at IAF
  25	RNP	MOSEX	3000 ft or 4000 ft, depending on MVA
  07	Only RNP 25 followed by circling runway 07 is available.

  Due to the crossing of EDDB D(CTR), Berlin Tower shall be informed about every approach on runway 25 at EDAZ.

  Coordination is required with the station responsible for the RNPapproach monitoring prior to the approach clearance from DBAS. Airacft will already be done by Berlin Arrival

  • No ATC Service provided on the ground (incl. landing clearance)

  Schönhagen (EDAZ)

  ATC Service by Departure South (DBDS)

  Departures

  • Only during 25-Ops
  • IFR Clearance when Schönhagen Information is offline
  • No ATC Service provided on the ground
  • Initial climb instructions needtransferred to bethis coordinatedmonitoring withstation Berlin Arrival

  Arrivals

  • Only during 25-Ops
  • Supervision of trafficwhen on the published procedureprocedure. only
    (potential

    The conflictsstation with departures)

  • Clearanceresponsible for the RNP approach willmonitoring alreadyshall be done by Berlin Arrival
  • No ATC Service provided on the ground (incl. landing clearance)
  • Report aircraft being on final toinform Berlin Tower (becauseabout the IFR arrival at EDAZ once this traffic joins the approach procedure and once this traffic has landed. 

    Missed approach procedures RWY 25L EDDB are not separated from RNP APP RWY 25 EDAZ. Still, approaches EDDB runway 25L and IFR approaches EDAZ will be generally considered independent. In case of dependencies)

  a
  missed approach at EDDB, Berlin Tower is responsible for providing separation.