# Departure ## Sectorization and Airspace ### Sector Berlin Departure [](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-08/dbd-06.png)[](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-08/dbd-24.png)
**Station** | **Station ID** | **Frequency** | **Login** |
Berlin Departure Nord | DBDN | 120.340 | EDDB\_N\_DEP |
Berlin Departure Süd | DBDS | 120.630 | EDDB\_S\_DEP |
Both frequencies shall be cross-coupled by the responsible controller.
### ARSAP Overflow Area The ARSAP Overflow Area may be activated on request by EDWW sector FLG during periods of high traffic. This will raise the vertical limit of sectors DBDN/DBDS east of EDDB from FL165 to FL235 to transfer departures from EDDB via ARSAP to EPWW sector D directly.During the activity of the ARSAP Overflow Area, full ATS is delegated from FLG to DBDN/DBDS within this area.
[](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-07/inkscape-xiuq8euvnd.png)Due to Euroscope limitations, sectors DBDN and DBDS shall select any runway for EDAE in the active runway dialogue to** **activate the ARSAP Overflow Area. In addition, sectors BOR, FLG and MAR shall also select a runway at EDAE to generate correct sector predictions. This is the only way to delegate this airspace from sector FLG to sectors DBDN/DBDS.
Sector DBDS is responsible for transferring aircraft via ARSAP to EPWW sector D according to the LoA between EDWW and EPWW:**Aerodromes** | **COP** | **Level** | **Special Conditions** | **To Sector** |
Outbound from EDDB | ARSAP | ↑FL170-FL230 | Odd levels below FL230 will only be used when required for separation purposes. DBDS may transfer departures EDDB on top of each other. | EPWW-D |
Inbound to EPPO, EPZG | ARSAP | FL210 | --- | EPWW-D |
Use the LoA for details on level agreements: [https://knowledgebase.vatsim-germany.org/books/bremen-fir-edww/page/bremen-acc-internal](https://knowledgebase.vatsim-germany.org/books/bremen-fir-edww/page/bremen-acc-internal)
Departures EDDB on SUKIP SIDs shall be transferred depending on the following airway: - SUKIP Y206 BUREL shall be transferred to sector BOR - SUKIP M748 SOGMA shall be transferred to sector 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](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 24-Ops | DBDN | BOR |
BUREL | Only during 06-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 |
**Conditions** | **EDDB RWYs 06** | **EDDB RWYs 24** |
IFR clearance | DBDN | DBAN |
Approach clearance | DBAN | DBAN |
Approach monitoring | DBDN | DBAN |
**Runway** | **Available Approach Types** | **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 procedure.
## 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 - IFR clearance ### Responsible stations**Conditions** | **EDDB RWYs 06** | **EDDB RWYs 24** |
IFR clearance | DBAST | DBDS |
Approach clearance | DBAS | DBAS |
Approach monitoring | DBAST | DBDS |
**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 approach monitoring prior to the approach clearance from DBAS. Airacft will be transferred to this monitoring station when on the published procedure.
The station responsible for the approach monitoring shall inform Berlin Tower about the IFR arrival at EDAZ once this traffic joins the approach procedure and once this traffic has landed.
Approaches EDDB runway 24L and IFR approaches EDAZ will be generally considered independent.