EDWW - Bremen Radar

Lower Airspace GND - FL245/FL285

Sector Splits

Bremen Radar Sector Splits for RG Bremen and RG Berlin

Sector Splits

EBG North/South

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

edww-ebg-nord-sued-split-eng.png

Complete Coverage

Sector Eider West Complete ("West-Bremen")

Login
Sector Indicator
Frequency
Callsign
Remark
EDWW_W_CTR
EIDW 120.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 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
ALR 126.325
Bremen Radar
EBG North primary station
EDWW_D_CTR DST 128.760 Bremen Radar EBG 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
ALR 126.325
Bremen Radar

ALR, HEI, HAME, HAMW

Upper: -

EDWW_E_CTR EIDE 124.075 Bremen Radar

EIDE, 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
ALR 126.325
Bremen Radar

ALR, EIDE, EIDW, FRI

Upper: JEV, HOL

EDWW_H_CTR HEI 125.855 Bremen Radar

HEI, 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
ALR 126.325
Bremen Radar

ALR

Upper: -

EDWW_E_CTR EIDE 124.075 Bremen Radar

EIDE, EIDW, FRI

Upper: JEV, HOL

EDWW_H_CTR HEI 125.855 Bremen Radar

HEI, 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
DST 128.760
Bremen Radar

DST, EMS

Upper: SOL, MNS, CEL

EDWW_R_CTR HRZ 126.655 Bremen Radar

HRZ, 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
DST 128.760
Bremen Radar

DST, HRZ

Upper: SOL, CEL

EDWW_S_CTR EMS 125.025 Bremen Radar

EMS

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.

Sector Splits

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
MRZ 124.175
Bremen Radar
primary station EBG

Sector Börde Complete

Login
Sector Indicator
Frequency
Callsign
Remark
EDWW_B_CTR
BOR 123.225
Bremen Radar
--

Sector Mark Complete

Login
Sector Indicator
Frequency
Callsign
Remark
EDWW_K_CTR
MAR 136.050
Bremen Radar
--

Sector Fläming

Login
Sector Indicator
Frequency
Callsign
Remark
EDWW_F_CTR
FLG 136.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
MRZ 124.175
Bremen Radar
--
EDWW_B_CTR
BOR 123.225
Bremen Radar
--

Visual Display of Sector Split

Sector Müritz and Fläming

Login
Sector Indicator
Frequency
Callsign
Remark
EDWW_M_CTR
MRZ 124.175
Bremen Radar
--
EDWW_F_CTR
FLG 136.450
Bremen Radar
--

Visual Display of Sector Split

Sector Mark and Fläming

Login
Sector Indicator
Frequency
Callsign
Remark
EDWW_K_CTR
MAR 136.050
Bremen Radar
--
EDWW_F_CTR
FLG 136.450
Bremen Radar
--

Visual Display of Sector Split

Sector Mark and Müritz

Login
Sector Indicator
Frequency
Callsign
Remark
EDWW_K_CTR
MAR 136.050
Bremen Radar
--
EDWW_M_CTR
MRZ 124.175
Bremen Radar
--

Visual Display of Sector Split

Three Split

Sector Mark, Müritz and Fläming

Login
Sector Indicator
Frequency
Callsign
Remark
EDWW_K_CTR
MAR 136.050
Bremen Radar
--
EDWW_M_CTR
MRZ 124.175
Bremen Radar
--
EDWW_F_CTR
FLG 136.450
Bremen Radar
--

Visual Display of Sector Split

Sector Mark, Müritz and Börde

Login
Sector Indicator
Frequency
Callsign
Remark
EDWW_K_CTR
MAR 136.050
Bremen Radar
--
EDWW_M_CTR
MRZ 124.175
Bremen Radar
--
EDWW_B_CTR
BOR 123.225
Bremen Radar
--

Visual Display of Sector Split

Sector Müritz, Börde and Fläming

Login
Sector Indicator
Frequency
Callsign
Remark
EDWW_K_CTR
MAR 136.050
Bremen Radar
--
EDWW_B_CTR
BOR 123.225
Bremen Radar
--
EDWW_F_CTR
FLG 136.450
Bremen Radar
--

Visual Display of Sector Split

Sector Owners (CTR only)

Sector MRZ
Sector MAR
Sector BOR
Sector FLG
Sector EDDB APP
EDWW_M_CTR EDWW_K_CTR EDWW_B_CTR EDWW_F_CTR EDWW_F_CTR
EDWW_K_CTR EDWW_M_CTR EDWW_K_CTR EDWW_B_CTR EDWW_B_CTR
EDWW_B_CTR EDWW_B_CTR EDWW_F_CTR EDWW_K_CTR EDWW_K_CTR

EDWW_F_CTR
EDWW_M_CTR EDWW_M_CTR EDWW_M_CTR
EDWW_CTR EDWW_CTR EDWW_CTR EDWW_CTR EDWW_CTR


Sector OSE
Sector HVL
EDUU_O_CTR EDUU_H_CTR
EDUU_H_CTR EDUU_O_CTR
EDWW_M_CTR EDWW_B_CTR
EDWW_K_CTR EDWW_F_CTR
EDWW_B_CTR EDWW_K_CTR

EDWW_M_CTR
EDWW_CTR EDWW_CTR

EBG BER

DBAN, DBAS, DBDN, DBDS

EBG BER

Einzelsektoren

Sektor Berlin Arrival North/South - DBAN/DBAS

Login
Sector Indicator
Frequency
Callsign
Remark
EDDB_N_APP
DBAN
119.630
Bremen Radar
--
EDDB_S_APP
DBAS
126.425
Bremen Radar
--

Mehr Infos zu den Sektoren Berlin Arrival sind in der SOP für Berlin-Brandenburg nachzulesen.

Sektorkarte:

DBA 06.pngDBA 24.png

Sektor Berlin Departure North/South - DBDN/DBDS

Login
Sector Indicator
Frequency
Callsign
Remark
EDDB_N_DEP
DBDN
120.340
Bremen Radar
--
EDDB_S_DEP
DBDS
120.630
Bremen Radar
--

Mehr Infos zu den Sektoren Berlin Departure sind in der SOP für Berlin-Brandenburg nachzulesen.

Sektorkarte:

DBD 06.pngDBD 24.png

EBG Nord-A

ALR, HEI, HAME, HAMW

EBG Nord-A

Übersichtskarte EBG Nord-A

Sektoren (below FL105)

EBG NORD-A -FL105.png

Sektoren (above FL105)

EBG NORD-A +FL105.png

EBG Nord-A

Einzelsektoren

Sektor Aller - ALR

Login
Sector Indicator
Frequency
Callsign
Remark
EDWW_A_CTR
ALR
126.325
Bremen Radar
--

Haupt-Verkehrsströme:

Sektorkarte:

ALR.png


Sektor Heide - HEI

Login
Sector Indicator
Frequency
Callsign
Remark
EDWW_H_CTR
HEI 125.855
Bremen Radar
--

Haupt-Verkehrsströme:

Sektorkarte:

HEI.png


Sektor Hamburg East - HAME

Login
Sector Indicator
Frequency
Callsign
Remark
EDDH_E_APP
HAME
119.510
Bremen Radar
--

Mehr Infos zum Hamburg East sind in der SOP für Hamburg nachzulesen.

Sektorkarte:

HAME.png


Sektor Hamburg West - HAMW

Login
Sector Indicator
Frequency
Callsign
Remark
EDDH_W_APP
HAMW
134.255
Bremen Radar
--

Mehr Infos zum Sektor Hamburg West sind in der SOP für Hamburg nachzulesen.

Sektorkarte:

HAMW.png



EBG Nord-A

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.pngA 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
RIBSO P D A S

028°

right turns

NOLGO P D / (W) A S

005°

left turns

RARUP P D A S

276°

right turns

BOGMU P D A / (N) S

229°

right turns

All holding information are included in the DFS-Pack. 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

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.pngTopsky 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.pngThere 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:

EBG Nord-B

EIDE, EIDW, FRI

EBG Nord-B

Übersichtskarte EBG Nord-B

EBG NORD-B.png

EBG Nord-B

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


Sektor Eider West - EIDW

Login
Sector Indicator
Frequency
Callsign
Remark
EDWW_W_CTR
EIDW
120.225
Bremen Radar
--

Haupt-Verkehrsströme:

Sektorkarte:

EIDW.png


Sektor Friesland - FRI

Login
Sector Indicator
Frequency
Callsign
Remark
EDDW_APP
FRI
124.800
Bremen Radar
--

Haupt-Verkehrsströme:

Sektorkarte:

FRI.png

EBG Ost

BOR, FLG, MAR, MRZ

EBG Ost

Overview EBG OST

EDWW_Overview EDWW Ost.png

EBG Ost

Sectors

Sector Börde - BOR

Login
Sector Indicator
Frequency
Callsign
Remark
EDWW_B_CTR
BOR
123.225
Bremen Radar
--

Main Traffic Flows:

Main Crossing/Conflict Points:

IFR Aerodromes within the Sector:

Sector Chart:

BOR.png

Sector Fläming - FLG

Login
Sector Indicator
Frequency
Callsign
Remark
EDWW_F_CTR
FLG 136.450
Bremen Radar
--

Main Traffic Flows:

Main Crossing/Conflict Points:

IFR Aerodromes within the Sector:

Sector Chart:

FLG.png

Sector Mark - MAR

Login
Sector Indicator
Frequency
Callsign
Remark
EDWW_K_CTR
MAR
136.050
Bremen Radar
--

Main Traffic Flows:

Main Crossing/Conflict Points:

IFR Aerodromes within the Sector:

Sector Chart:

MAR.png

Sector Müritz - MRZ

Login
Sector Indicator
Frequency
Callsign
Remark
EDWW_M_CTR
MRZ
124.175
Bremen Radar
--

Main Traffic Flows:

Main Crossing/Conflict Points:

IFR Aerodromes within the Sector:

Sector Chart:

MRZ.png

EBG Ost

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

The areas will mostly be booked via the Vatsim Germany Forums. 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:

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):

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

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:

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:

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:

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

EBG Süd

Übersichtskarte EBG Süd

Sektoren (below FL105)

EBG Süd -FL105.png

Sektoren (above FL105)

EBG Süd +FL105.png

EBG Süd

Einzelsektoren

Sektor Deister - DST

Login
Sector Indicator
Frequency
Callsign
Remark
EDWW_D_CTR
DST 128.760
Bremen Radar
--

Haupt-Verkehrsströme:

Sektorkarte:

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


Sektor Harz - HRZ

Login
Sector Indicator
Frequency
Callsign
Remark
EDWW_R_CTR
HRZ
126.655
Bremen Radar
--

Haupt-Verkehrsströme:

Sektorkarte:

HRZ.png


Sektor Hannover - HAN

Login
Sector Indicator
Frequency
Callsign
Remark
EDDV_APP
HAN 119.490
Bremen Radar
--

Mehr Infos zum Sektor Hannover sind in der SOP für Hannover nachzulesen.

Sektorkarte:

HAN.png