# EDWW - Bremen Radar # Sector Splits Bremen Radar Sector Splits for RG Bremen and RG Berlin # EBG North/South

Valid AIRAC 2311 - new sector ownerships to allow a better EBG North/South split.

[![edww-ebg-nord-sued-split-eng.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-11/scaled-1680-/edww-ebg-nord-sued-split-eng.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-11/edww-ebg-nord-sued-split-eng.png) ### Complete Coverage #### Sector Eider West Complete ("West-Bremen")
**Login** **Sector Indicator** **Frequency** **Callsign** **Remark**
EDWW\_W\_CTR EIDW120.225 Bremen Radar primary station
Covers **Bremen:** ALR, EIDE, EIDW, HEI, DST, EMS, HRZ **Maastricht:** JEV, HOL, CEL, MNS, SOL

**EBG North + South Endorsement needed! (ALR + DST)** [Center Endorsements](https://knowledgebase.vatsim-germany.org/books/atd/page/endorsements-bremen-fir) valid before AIRAC 2311 are transferred into EBG North + South Endorsements.

Eider West (EDWW\_W\_CTR) does not have priority over its own sector. If EDWW\_A\_CTR or EDWW\_E\_CTR is online, they will control the airspace of EIDW. This station is meant to be used in low traffic situations, as an EDWW West Upper/Lower Split together with Maastricht stations or as a "before primetime/event sector" until other controllers join. #### EBG North / South Sector Split
**Login** **Sector Indicator** **Frequency** **Callsign** **Remark**
EDWW\_A\_CTR ALR126.325 Bremen Radar EBG North primary station
EDWW\_D\_CTRDST128.760Bremen RadarEBG South primary station
**EDWW\_A\_CTR** covers **Bremen:** ALR, EIDE, EIDW, HEI **Maastricht:** JEV, HOL **EDWW\_D\_CTR** covers **Bremen:** DST, EMS, HRZ **Maastricht:** CEL, MNS, SOL

These stations do not cover the other EBG region, if one of them is offline!

### EBG North #### Two Split - Sector Aller + Eider East
**Login** **Sector Indicator** **Frequency** **Callsign** **Covering**
EDWW\_A\_CTR ALR126.325 Bremen Radar ALR, HEI, HAME, HAMW Upper: -
EDWW\_E\_CTREIDE124.075Bremen RadarEIDE, EIDW, FRI Upper: JEV, HOL
EDWW\_A\_CTR has all inbound streams to Hamburg and can concentrate on the EDDH top-down service while EDWW\_E\_CTR covers everything else including the upper airspace. #### Two Split - Sector Aller + Heide
**Login** **Sector Indicator** **Frequency** **Callsign** **Covering**
EDWW\_A\_CTR ALR126.325 Bremen Radar ALR, EIDE, EIDW, FRI Upper: JEV, HOL
EDWW\_H\_CTRHEI125.855Bremen RadarHEI, HAME, HAMW Upper: -
**Heide Sector is now a top-down CTR.** This split is useful if Hamburg is not staffed and relieves the EDWW\_A\_CTR (EBG North primary sector). EDWW\_A\_CTR keeps one inbound stream over RIBSO. #### Three Split - Sector Aller + Eider East + Heide (EDDH Event Split)
**Login** **Sector Indicator** **Frequency** **Callsign** **Covering**
EDWW\_A\_CTR ALR126.325 Bremen Radar ALR Upper: -
EDWW\_E\_CTREIDE124.075Bremen RadarEIDE, EIDW, FRI Upper: JEV, HOL
EDWW\_H\_CTRHEI125.855Bremen RadarHEI, HAME, HAMW Upper: -
EDWW\_A\_CTR only has its ALR airspace with one Hamburg inbound stream over RIBSO. This relives the EDWW\_H\_CTR. ### EBG South #### Two Split - Sector Deister + Harz
**Login** **Sector Indicator** **Frequency** **Callsign** **Covering**
EDWW\_D\_CTR DST128.760 Bremen Radar DST, EMS Upper: SOL, MNS, CEL
EDWW\_R\_CTRHRZ126.655Bremen RadarHRZ, HAN Upper: -
EDWW\_R\_CTR has top-down service for Hannover Approach and its airports. It relieves EDWW\_D\_CTR. #### Two Split - Sector Deister + Ems
**Login** **Sector Indicator** **Frequency** **Callsign** **Covering**
EDWW\_D\_CTR DST128.760 Bremen Radar DST, HRZ Upper: SOL, CEL
EDWW\_S\_CTREMS125.025Bremen RadarEMS Upper: MNS
East/West split of the EBG South region. Maastricht Münster (MNS) is controlled by Langen North, if one of their centers is online. # EBG Ost ### Single Sector

Müritz, Mark or Börde will cover MRZ, MAR, BOR, FLG, EDDB APP and OSE, HVL when no other position of EBG Ost is online.

#### Sector Müritz Complete
**Login** **Sector Indicator** **Frequency** **Callsign** **Remark**
EDWW\_M\_CTR MRZ124.175 Bremen Radar primary station EBG
#### Sector Börde Complete
**Login** **Sector Indicator** **Frequency** **Callsign** **Remark**
EDWW\_B\_CTR BOR123.225 Bremen Radar --
#### Sector Mark Complete
**Login** **Sector Indicator** **Frequency** **Callsign** **Remark**
EDWW\_K\_CTR MAR136.050 Bremen Radar --
#### Sector Fläming
**Login** **Sector Indicator** **Frequency** **Callsign** **Remark**
EDWW\_F\_CTR FLG136.450 Bremen Radar --

Fläming will cover BOR, FLG, MAR, EDDB APP and HVL when no other position of EBG Ost is online.

### Two Split #### Sector Müritz and Börde
**Login** **Sector Indicator** **Frequency** **Callsign** **Remark**
EDWW\_M\_CTR MRZ124.175 Bremen Radar --
EDWW\_B\_CTR BOR123.225 Bremen Radar --
[**Visual Display of Sector Split**](https://atciss.vatsim-germany.org/map?pos=ed%2FMRZ&pos=ed%2FBOR) #### Sector Müritz and Fläming
**Login** **Sector Indicator** **Frequency** **Callsign** **Remark**
EDWW\_M\_CTR MRZ124.175 Bremen Radar --
EDWW\_F\_CTR FLG136.450 Bremen Radar --
[**Visual Display of Sector Split**](https://atciss.vatsim-germany.org/map?pos=ed%2FMRZ&pos=ed%2FFLG) #### Sector Mark and Fläming
**Login** **Sector Indicator** **Frequency** **Callsign** **Remark**
EDWW\_K\_CTR MAR136.050 Bremen Radar --
EDWW\_F\_CTR FLG136.450 Bremen Radar --
[**Visual Display of Sector Split**](https://atciss.vatsim-germany.org/map?pos=ed%2FMAR&pos=ed%2FFLG) #### Sector Mark and Müritz
**Login** **Sector Indicator** **Frequency** **Callsign** **Remark**
EDWW\_K\_CTR MAR136.050 Bremen Radar --
EDWW\_M\_CTR MRZ124.175 Bremen Radar --
[**Visual Display of Sector Split**](https://atciss.vatsim-germany.org/map?pos=ed%2FMRZ&pos=ed%2FMAR) ### Three Split #### Sector Mark, Müritz and Fläming
**Login** **Sector Indicator** **Frequency** **Callsign** **Remark**
EDWW\_K\_CTR MAR136.050 Bremen Radar --
EDWW\_M\_CTR MRZ124.175 Bremen Radar --
EDWW\_F\_CTR FLG136.450 Bremen Radar --
[**Visual Display of Sector Split**](https://atciss.vatsim-germany.org/map?pos=ed%2FMRZ&pos=ed%2FMAR&pos=ed%2FFLG) #### Sector Mark, Müritz and Börde
**Login** **Sector Indicator** **Frequency** **Callsign** **Remark**
EDWW\_K\_CTR MAR136.050 Bremen Radar --
EDWW\_M\_CTR MRZ124.175 Bremen Radar --
EDWW\_B\_CTR BOR123.225 Bremen Radar --
[**Visual Display of Sector Split**](https://atciss.vatsim-germany.org/map?pos=ed%2FMRZ&pos=ed%2FMAR&pos=ed%2FBOR) #### Sector Müritz, Börde and Fläming
**Login** **Sector Indicator** **Frequency** **Callsign** **Remark**
EDWW\_K\_CTR MAR136.050 Bremen Radar --
EDWW\_B\_CTR BOR123.225 Bremen Radar --
EDWW\_F\_CTR FLG136.450 Bremen Radar --
[**Visual Display of Sector Split**](https://atciss.vatsim-germany.org/map?pos=ed%2FMRZ&pos=ed%2FBOR&pos=ed%2FFLG) ### Sector Owners (CTR only)
**Sector MRZ** **Sector MAR** **Sector BOR** **Sector FLG** **Sector EDDB APP**
EDWW\_M\_CTREDWW\_K\_CTREDWW\_B\_CTREDWW\_F\_CTREDWW\_F\_CTR
EDWW\_K\_CTREDWW\_M\_CTREDWW\_K\_CTREDWW\_B\_CTREDWW\_B\_CTR
EDWW\_B\_CTREDWW\_B\_CTREDWW\_F\_CTREDWW\_K\_CTREDWW\_K\_CTR
EDWW\_F\_CTR EDWW\_M\_CTREDWW\_M\_CTREDWW\_M\_CTR
EDWW\_CTREDWW\_CTREDWW\_CTREDWW\_CTREDWW\_CTR
####
**Sector OSE** **Sector HVL**
EDUU\_O\_CTREDUU\_H\_CTR
EDUU\_H\_CTREDUU\_O\_CTR
EDWW\_M\_CTREDWW\_B\_CTR
EDWW\_K\_CTREDWW\_F\_CTR
EDWW\_B\_CTREDWW\_K\_CTR
EDWW\_M\_CTR
EDWW\_CTREDWW\_CTR
# EBG BER DBAN, DBAS, DBDN, DBDS # Einzelsektoren #### Sektor Berlin Arrival North/South - DBAN/DBAS
**Login** **Sector Indicator** **Frequency** **Callsign** **Remark**
[EDDB\_N\_APP](https://knowledgebase.vatsim-germany.org/books/sops-fir-bremen/page/arrival-iZx) DBAN 119.630 Bremen Radar --
[EDDB\_S\_APP](https://knowledgebase.vatsim-germany.org/books/sops-fir-bremen/page/arrival-iZx) DBAS 126.425 Bremen Radar --
Mehr Infos zu den Sektoren Berlin Arrival sind in der [SOP für Berlin-Brandenburg](https://knowledgebase.vatsim-germany.org/books/sops-fir-bremen/page/arrival-iZx) nachzulesen. **Sektorkarte:** [![DBA 06.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-08/dba-06.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-08/dba-06.png)[![DBA 24.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-08/dba-24.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-08/dba-24.png) #### Sektor Berlin Departure North/South - DBDN/DBDS
**Login** **Sector Indicator** **Frequency** **Callsign** **Remark**
[EDDB\_N\_DEP](https://knowledgebase.vatsim-germany.org/books/sops-fir-bremen/page/departure) DBDN 120.340 Bremen Radar --
[EDDB\_S\_DEP](https://knowledgebase.vatsim-germany.org/books/sops-fir-bremen/page/departure) DBDS 120.630 Bremen Radar --
Mehr Infos zu den Sektoren Berlin Departure sind in der [SOP für Berlin-Brandenburg](https://knowledgebase.vatsim-germany.org/books/sops-fir-bremen/page/departure) nachzulesen. **Sektorkarte:** [![DBD 06.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-08/dbd-06.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-08/dbd-06.png)[![DBD 24.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-08/dbd-24.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-08/dbd-24.png) # EBG Nord-A ALR, HEI, HAME, HAMW # Übersichtskarte EBG Nord-A ### Sektoren (below FL105) [![EBG NORD-A -FL105.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-02/scaled-1680-/ebg-nord-a-fl105.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-02/ebg-nord-a-fl105.png) ### Sektoren (above FL105) [![EBG NORD-A +FL105.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-02/scaled-1680-/ZOeebg-nord-a-fl105.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-02/ZOeebg-nord-a-fl105.png) # Einzelsektoren #### Sektor Aller - ALR
**Login** **Sector Indicator** **Frequency** **Callsign** **Remark**
EDWW\_A\_CTR ALR 126.325 Bremen Radar --
**Haupt-Verkehrsströme:** **Sektorkarte:** **[![ALR.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-02/scaled-1680-/alr.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-02/alr.png)** #### Sektor Heide - HEI
**Login** **Sector Indicator** **Frequency** **Callsign** **Remark**
EDWW\_H\_CTR HEI125.855 Bremen Radar --
**Haupt-Verkehrsströme:** **Sektorkarte:** **[![HEI.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-02/hei.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-02/hei.png)** #### Sektor Hamburg East - HAME
**Login** **Sector Indicator** **Frequency** **Callsign** **Remark**
[EDDH\_E\_APP](https://knowledgebase.vatsim-germany.org/books/sops-fir-bremen/page/arrival-nHt) HAME 119.510 Bremen Radar --
Mehr Infos zum Hamburg East sind in der [SOP für Hamburg](https://knowledgebase.vatsim-germany.org/books/sops-fir-bremen/chapter/eddh-hamburg-airport) nachzulesen. **Sektorkarte:** **[![HAME.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-02/hame.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-02/hame.png)** #### Sektor Hamburg West - HAMW
**Login** **Sector Indicator** **Frequency** **Callsign** **Remark**
[EDDH\_W\_APP](https://knowledgebase.vatsim-germany.org/books/sops-fir-bremen/page/arrival-nHt) HAMW 134.255 Bremen Radar --
Mehr Infos zum Sektor Hamburg West sind in der [SOP für Hamburg](https://knowledgebase.vatsim-germany.org/books/sops-fir-bremen/chapter/eddh-hamburg-airport) nachzulesen. **Sektorkarte:** **[![HAMW.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-02/hamw.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-02/hamw.png)** # Holdings Hamburg Inbounds Holdings offer the most efficient opportunity to deal with high traffic situations and relieve overloaded sectors especially approach sectors. [![EDWW_HEI_holding.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2022-11/scaled-1680-/edww-hei-holding.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2022-11/edww-hei-holding.png)*A typical thursday evening* The following procedures are the standard when building up holdings. Other methods have to be coordinated. ### EDDH Holdings and STARs
**Waypoint****23****15****05****33****Holding**
RIBSOPDAS028° right turns
NOLGOPD / (W)AS005° left turns
RARUPPDAS276° right turns
BOGMUPDA / (N)S229° right turns
All holding information are included in the [DFS-Pack](https://de.wiki.vatsim-germany.org/DFS_Pack_Manual%7C). Just type .*(Waypoint)* for inbound course and turn direction of the published hold procedure. ### Critical Areas The holdings are mostly not conflicting with departing traffic. In some cases, you have to keep an eye on several situations - **RARUP** holding with departing traffic via RAMAR, when stack is high a climb gradient is low headings are recommended - **RARUP** holding has three traffic flows merging at RARUP. Level separation has to be established before reaching the hold. - **NOLGO** holdings with right turns instead of left are conflicting with departing traffic via AMLUH - **BOGMU** holding is feeded by two sectors EIDE and HEI from MICOS and ALS area. In normal operation HEI manages the BOGMU hold. EIDE should coordinate in a adequate time before reaching the hold ### Coordination Every station, especially sectors of the lower airspace and approach sectors can arrange the use of holds. Every arrival and center sector handling holdings must be informed. When holdings are requested, holdings have to be established at every waypoint to guarantee similar delays. It is unfair to the pilots that other routings e.g. via RIBSO have a pseudo prioritization because they do not need to hold. Furthermore, with not holding every aircraft the traffic flow gets less plannable. When a coordinator is online it is strongly recommended ALR and HEI share their scope so the coordinator can see the holding management lists. ### Topsky Topsky offers several tools to make the work as an vATC easier. To work with the Topsky Holding lists you have to make a right click on the Callsign and click on *Hold*. Another window appears in which you can select the waypoint where the aircraft has to hold. Then a holding list appears. By clicking on a waypoint in the holding management list you can open a graphical overview of the holding stack. You can also use the *S-Highlight* to highlight the callsign and level of every aircraft within the hold. [![EDWW_hold_select.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2022-11/scaled-1680-/edww-hold-select.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2022-11/edww-hold-select.png)*Topsky Callsign menu, select Hold and S-Highlight* Please do not forget to click *XHold* when the aircraft is cleared to leave the hold. This function can be found the same way as to select the holding. Otherwise on the next station's EuroScope instance a holding list will pop up. We strongly recommend sorting your holding list with the ETO so the aircraft with the longest delay is the top item. ### Releasing traffic from the holds
For the standard runway configuration 23ARR/33DEP it is recommended to delegate arriving traffic via BOGMU from HAME to HAMW so every sector handles one downwind. [![EDDH_Holdings_23_HDG.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2022-11/scaled-1680-/eddh-holdings-23-hdg.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2022-11/eddh-holdings-23-hdg.png)*There are several oprions to release the holds* In general, the receiving sector determines when an aircraft can be released. The center controllers have to release the aircraft with the „oldest“ ETO. The aim of every controller is a *similar* delay for every aircraft. By doing so it can be necessary one downwind has to feeded with 5nm instead of 10-12nm. The most flexible way to release holdings are headings, the use of STARs is still possible but can lead into irregular spacings. The picture shows possible traffic flows archived with headings. When holding traffic, frequent and concise coordination is indispensable. Examples for coordination: - “I take DLH016 heading 230, descending FL100.” - “Give me EWG9MA left turn heading 360” - “EZY998 next time inbound NOLGO left heading 340.” # EBG Nord-B EIDE, EIDW, FRI # Übersichtskarte EBG Nord-B [![EBG NORD-B.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-02/scaled-1680-/ebg-nord-b.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-02/ebg-nord-b.png) # Einzelsektoren #### Sektor Eider East - EIDE
**Login** **Sector Indicator** **Frequency** **Callsign** **Remark**
EDWW\_E\_CTR EIDE 124.075 Bremen Radar --
**Haupt-Verkehrsströme:** **Sektorkarte:[![EIDE.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-02/eide.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-02/eide.png)** #### Sektor Eider West - EIDW
**Login** **Sector Indicator** **Frequency** **Callsign** **Remark**
EDWW\_W\_CTR EIDW 120.225 Bremen Radar --
**Haupt-Verkehrsströme:** **Sektorkarte:** **[![EIDW.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-02/eidw.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-02/eidw.png)** #### Sektor Friesland - FRI
**Login** **Sector Indicator** **Frequency** **Callsign** **Remark**
EDDW\_APP FRI 124.800 Bremen Radar --
**Haupt-Verkehrsströme:** **Sektorkarte:** **[![FRI.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-02/fri.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-02/fri.png)** # EBG Ost BOR, FLG, MAR, MRZ # Overview EBG OST [![EDWW_Overview EDWW Ost.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-05/edww-overview-edww-ost.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-05/edww-overview-edww-ost.png) # Sectors #### Sector Börde - BOR
**Login** **Sector Indicator** **Frequency** **Callsign** **Remark**
EDWW\_B\_CTR BOR 123.225 Bremen Radar --
**Main Traffic Flows:** - EDDB-Outbounds via HLZ, POVEL and ABGUS to EDUU or EDYY - EDDB-Outbounds via MAXAN, DIBDO, BARAP and ODLUN to EDMM - EDDP-Outbounds via ODLUN Y233 EMBOX L986 POVEL - EDDP-Outbounds via ODLUN M736 BUREL - EDDP-Inbounds via BUREL M736 BARAP - EDDV-Outbounds via POVEL - EDDV-Inbounds via HLZ **Main Crossing/Conflict Points:** - Parallel departures out of EDDB via SUKIP and LOGDO - Vicinity of MAG VOR **IFR Aerodromes within the Sector:** - [Magdeburg/City - EDBM (uncontrolled)](https://aip.dfs.de/BasicIFR/pages/C0046A.html) - Magdeburg/Cochstedt - EDBC (uncontrolled) **Sector Chart:** **[![BOR.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-05/bor.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-05/bor.png)** #### Sector Fläming - FLG
**Login** **Sector Indicator** **Frequency** **Callsign** **Remark**
EDWW\_F\_CTR FLG136.450 Bremen Radar --
**Main Traffic Flows:** - EDDB-Outbounds via BEBKU and EBASA to EDMM - EDDB-Outbounds via ARSAP to EPWW - EDDB-Inbounds via ATGUP, NUKRO and KLF - EDDP-Outbounds via RUDAK - EDDP-Inbounds via BEBKU - EDDC-Outbounds and Inbounds via KOBUS and OSKAN **Main Crossing/Conflict Points:** - Parallel departures out of EDDB via ARSAP - Vicinity of KLF VOR - Vicinity of BEBKU **IFR Aerodromes within the Sector:** - - **Sector Chart:** **[![FLG.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-07/flg.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-07/flg.png)** #### Sector Mark - MAR
**Login** **Sector Indicator** **Frequency** **Callsign** **Remark**
EDWW\_K\_CTR MAR 136.050 Bremen Radar --
**Main Traffic Flows:** - EDDB-Outbounds via GENTI M748, GERGA T239, GERGA M725 - EDDB-Outbounds via ALUKA/BODLA to EPWW - EDDB-Inbounds via OGBER and KETAP - EDDP-Outbounds and Inbounds via BUREL - EDDH-Outbounds via NUSGU - EDDH-Inbounds via BUMIL - EDDV-Outbounds and Inbounds via BKD - EPSC-Inbounds via BODLA - EPSC-Outbounds via PESEL **Main Crossing/Conflict Points:** - Vicinity of SOGMA - Vicinity of RENKI - Vicinity of BKD VOR **IFR Aerodromes within the Sector:** - - **Sector Chart:** **[![MAR.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-05/mar.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-05/mar.png)** #### Sector Müritz - MRZ
**Login** **Sector Indicator** **Frequency** **Callsign** **Remark**
EDWW\_M\_CTR MRZ 124.175 Bremen Radar --
**Main Traffic Flows:** - EDDB-Inbounds via RODEP - EDDH-Outbounds via BERIM - EDDH-Inbounds via BERIM and ROSOK - EKCH/ESMS-Outbounds via SALLO - EKCH-Inbounds via NIKDA/KOSEB/MONAK - ESMS-Inbounds via BAKLI - EPSC-Inbounds via FARCU - EPSC-Outbounds via BINKA **Main Crossing/Conflict Points:** - Vicinity of BERIM - Vicinity of MONAK - Vicinity of PEROM **IFR Aerodromes within the Sector:** - [Heringsdorf - EDAH](https://aip.dfs.de/BasicIFR/pages/C00372.html) - [Rostock-Laage - ETNL (civil/military)](https://aip.dfs.de/BasicIFR/pages/C00632.html) - [Barth - EDBH (uncontrolled)](https://aip.dfs.de/BasicIFR/pages/C000DD.html) - [Neubrandenburg - EDBN (uncontrolled)](https://aip.dfs.de/BasicIFR/pages/C00527.html) **Sector Chart:** **[![MRZ.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-05/mrz.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-05/mrz.png)** # VPA North East (ED-R 401) ### Overview Within Bremen Radar EBG East, (M)VPA North East (ED-R 401) may be active. The area consists of multiple sub-sectors which in most cases can be opened independently. The reserved level band is subject to individual coordination with the pilots/mission planner. In general, the reserved airspace shall be chosen in a way that training missions have a minimal impact on normal traffic operations. [![MVPA North East.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-11/scaled-1680-/mvpa-north-east.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-11/mvpa-north-east.png) The areas will mostly be booked via the [Vatsim Germany Forums.](https://board.vatsim-germany.org/threads/area-booking-vatger.67465/) Alternatively, pilots may coordinate openings of certain sub-sectors individually on frequency or private messages.

The combined use of the entire airspace ED-R401/MORE and BASIC 1NH is not possible.

### Separation Bremen Radar and Rhein Radar shall maintain the following separation to active VPA sub-sectors: - Lateral Separation: 5 NM - Vertical Separation: 1000 ft or 2000 ft if upper limit is inside RVSM airspace

To avoid entries into active VPA sectors, Bremen Radar and Rhein Radar may use radar vectors, directs, airways or re-routings.

### Priority Airways IFR traffic is allowed to cross VPA sectors BASIC 1N and BASIC 2N when proceeding on the following airways (between FL100-FL285): - T298 - M725 - M602 - Z400 - M44 This traffic is not allowed to cross any other VPA sub-sector. Traffic may be initially re-routed via USEDU or radar vectors to enter BASIC 2N via USEDU M602 PENET. Lower/Upper transitions are allowed provided traffic proceeds on the mentioned airways and stays clear of other VPA sub-sectors.

IFR is prohibited from crossing BASIC 1N or BASIC 2N on the mentioned airways between FL220 and FL280 whenever sub-sectors MORE 101 or MORE 102 are active.

A Topsky Map of Priority Airways can be displayed in the EDWW Euroscope Package (Maps > MIL MAPS).

[![VPA Prio Airways.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-11/scaled-1680-/vpa-prio-airways.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-11/vpa-prio-airways.png)

IFR traffic shall only be cleared to proceed via the mentioned priority airways when Bremen Radar provided traffic information to the traffic using VPA sectors BASIC 1N/2N.

### VPA Re-Routings During the activation of certain sub-sectors of VPA North East, Bremen Radar sector Müritz is responsible for coordinating the re-routings with the surrounding sectors. Re-routings on frequency may only include direct routings to required waypoints if the routing does not specifically require all mentioned airways. The complete and valid route including all airways may be used for flow measures and pre-coordinated routings. To reduce workload, Bremen Radar may consider restricting traffic from EDDB, EDDC, EDDP, EDAY, EDAZ and EDBM with destination EKCH, EKRK, ESMS, ESMK or EKRN and vice versa to stay below FL285. #### EDDB Inbound/Outbound Traffic Whenever VPA sectors 2N, 2A, 2B, 2C, 2D or 2E are active, traffic from/to Berlin may be re-routed the following way to stay clear of restricted airspace: - **Arrivals EDDB:** UESDU Z14 BEKBA T280 KETAP (marked in red) - **Departures EDDB:** GERGA M725 RENKI Y89 USEDU (marked in pink) [![MVPA EDDB In_Out.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-11/scaled-1680-/mvpa-eddb-in-out.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-11/mvpa-eddb-in-out.png) #### EKCH/EKRN/ESMS Inbound Traffic Whenever VPA sectors MORE 101 or MORE 102 are active, traffic to EKCH, EKRN and ESMS may be re-routed the following way to stay clear of restricted airspace: - **Arrivals EKCH (via KOSEB)**: USEDU DCT BINZE Z14 BANKU DCT KOSEB (marked in orange) - **Arrivals EKRN/ESMK (via DETNI)**: USEDU Z14 BEBEB DCT UMSET (marked in pink) - **Arrivals ESMS/EKRN**: ROSOK M726 SULIV Z14 BANKU DCT BAKLI (marked in violet) - **Arrivals ESMS**: USEDU Z14 BEBEB DCT BAKLI (marked in green) [![MVPA EKCH_EKRN_ESMS In.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-11/scaled-1680-/mvpa-ekch-ekrn-esms-in.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-11/mvpa-ekch-ekrn-esms-in.png) #### EKCH/EKRN/ESMS/EKRK Outbound Traffic Whenever VPA sectors MORE 101 or MORE 102 are active, traffic from EKCH, EKRN and ESMS may be re-routed the following way to stay clear of restricted airspace: - **Departures EKCH/EKRK/ESMS**: SALLO DCT BEBEB Z14 USEDU (marked in violet) - **Departures EKRN**: UNGAV DCT BEBEB Z14 USEDU (marked in orange) [![MVPA EKCH_EKRN_ESMS Out.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-11/scaled-1680-/mvpa-ekch-ekrn-esms-out.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-11/mvpa-ekch-ekrn-esms-out.png) ### ATC Service and Responsibilities Bremen Radar sector MRZ is the main responsible sector for coordinating openings and closures of VPA North East sectors. In general, Bremen Radar shall not provide tactical service for traffic inside the VPA. Instead, Bremen Radar should only clear traffic to enter the VPA when active.
Phraseology for Entry **ATC:** *"*\[Callsign\]*, (IFR cancelled at time...), approved to operate VPA North East part* \[active sub-sectors\]*, FL100 up to* \[upper limit of subsectors\]*, report finished. Frequency change approved."* **Example:** *"NATO301, (IFR cancelled at time...), approved to operate VPA North East part BASIC1A 1B, FL100 up to FL300, report finished. Frequency change approved."*
Traffic may enter the VPA either IFR or VFR. Preferably the cancellation is performed before entry. VFR traffic leaving the VPA below should inform Bremen Radar when clear of the area. VFR traffic will usually descend below FL100 to leave the VPA. Alternatively, traffic may also request an IFR clearance when inside of the VPA. In this case, this traffic is released to leave the VPA under IFR. # EBG Süd DST, EMS, HRZ, HAN # Übersichtskarte EBG Süd ### Sektoren (below FL105) [![EBG Süd -FL105.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-02/scaled-1680-/ebg-sud-fl105.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-02/ebg-sud-fl105.png) ### Sektoren (above FL105) [![EBG Süd +FL105.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-02/scaled-1680-/pNjebg-sud-fl105.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-02/pNjebg-sud-fl105.png) # Einzelsektoren #### Sektor Deister - DST
**Login** **Sector Indicator** **Frequency** **Callsign** **Remark**
EDWW\_D\_CTR DST128.760 Bremen Radar --
**Haupt-Verkehrsströme:** **Sektorkarte:** **[![DST.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-02/scaled-1680-/dst.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-02/dst.png)** #### Sektor Ems - EMS
**Login** **Sector Indicator** **Frequency** **Callsign** **Remark**
EDWW\_S\_CTR EMS 125.025 Bremen Radar --
**Haupt-Verkehrsströme:** **Sektorkarte:** **[![EMS.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-02/scaled-1680-/ems.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-02/ems.png)** #### Sektor Harz - HRZ
**Login** **Sector Indicator** **Frequency** **Callsign** **Remark**
EDWW\_R\_CTR HRZ 126.655 Bremen Radar --
**Haupt-Verkehrsströme:** **Sektorkarte:** **[![HRZ.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-02/scaled-1680-/hrz.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-02/hrz.png)** #### Sektor Hannover - HAN
**Login** **Sector Indicator** **Frequency** **Callsign** **Remark**
[EDDV\_APP](https://knowledgebase.vatsim-germany.org/books/sops-fir-bremen/page/arrival) HAN119.490 Bremen Radar --
Mehr Infos zum Sektor Hannover sind in der [SOP für Hannover](https://knowledgebase.vatsim-germany.org/books/sops-fir-bremen/chapter/eddv-hannover-airport) nachzulesen. **Sektorkarte:** **[![HAN.png](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-02/scaled-1680-/han.png)](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-02/han.png)**