EDWW - Bremen Radar

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

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

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

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)

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

EDWW_R_CTR has top-down service for Hannover Approach and its airports. It relieves EDWW_D_CTR.

Two Split - Sector Deister + Ems

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

Sector Börde Complete

Sector Mark Complete

Sector Fläming

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

Two Split

Three Split

Sector Mark, Müritz and Fläming

Visual Display of Sector Split

Sector Mark, Müritz and Börde

Visual Display of Sector Split

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

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

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

Sektorkarte:

Sektor Berlin Departure North/South - DBDN/DBDS

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

Sektorkarte:

EBG Nord-A

ALR, HEI, HAME, HAMW

EBG Nord-A

Übersichtskarte EBG Nord-A

Sektoren (below FL105)

Sektoren (above FL105)

EBG Nord-A

Einzelsektoren

Sektor Aller - ALR

Haupt-Verkehrsströme:

Sektorkarte:

Sektor Heide - HEI

Haupt-Verkehrsströme:

Sektorkarte:

Sektor Hamburg East - HAME

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

Sektorkarte:

Sektor Hamburg West - HAMW

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

Sektorkarte:

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.

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

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.

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.

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

EBG Nord-B

Übersichtskarte EBG Nord-B

EBG Nord-B

Einzelsektoren

Sektor Eider East - EIDE

Haupt-Verkehrsströme:

Sektorkarte:

Sektor Eider West - EIDW

Haupt-Verkehrsströme:

Sektorkarte:

Sektor Friesland - FRI

Haupt-Verkehrsströme:

Sektorkarte:

EBG Ost

BOR, FLG, MAR, MRZ

EBG Ost

Overview EBG OST

EBG Ost

Sectors

Sector Börde - BOR

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)

Sector Chart:

Sector Fläming - FLG

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
EPPO-Inbounds via SUBIX and ARSAP

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:

Sector Mark - MAR

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
EPPO-Inbounds via ALUKA
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:

Sector Müritz - MRZ

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:

Sector Chart:

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.

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:

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

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)

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$

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)

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)

Sektoren (above FL105)

EBG Süd

Einzelsektoren

Sektor Deister - DST

Haupt-Verkehrsströme:

Sektorkarte:

Sektor Ems - EMS

Haupt-Verkehrsströme:

Sektorkarte:

Sektor Harz - HRZ

Haupt-Verkehrsströme:

Sektorkarte:

Sektor Hannover - HAN

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

Sektorkarte:

Login	Sector Indicator	Frequency	Callsign	Remark
EDWW_W_CTR	EIDW	120.225	Bremen Radar	primary station

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

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

Login	Sector Indicator	Frequency	Callsign	Remark
EDWW_M_CTR	MRZ	124.175	Bremen Radar	primary station EBG

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

EDWW - Bremen Radar

Sector Splits

EBG North/South

Complete Coverage

Sector Eider West Complete ("West-Bremen")

EBG North / South Sector Split

EBG North

Two Split - Sector Aller + Eider East

Two Split - Sector Aller + Heide

Three Split - Sector Aller + Eider East + Heide (EDDH Event Split)

EBG South

Two Split - Sector Deister + Harz

Two Split - Sector Deister + Ems

EBG Ost

Single Sector

Sector Müritz Complete

Sector Börde Complete

Sector Mark Complete

Sector Fläming

Two Split

Sector Müritz and Börde

Sector Müritz and Fläming

Sector Mark and Fläming

Sector Mark and Müritz

Three Split

Sector Mark, Müritz and Fläming

Sector Mark, Müritz and Börde

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

Sector Owners (CTR only)

EBG BER

Einzelsektoren

Sektor Berlin Arrival North/South - DBAN/DBAS

Sektor Berlin Departure North/South - DBDN/DBDS

EBG Nord-A

Übersichtskarte EBG Nord-A

Sektoren (below FL105)

Sektoren (above FL105)

Einzelsektoren

Sektor Aller - ALR

Sektor Heide - HEI

Sektor Hamburg East - HAME

Sektor Hamburg West - HAMW

Holdings Hamburg Inbounds

EDDH Holdings and STARs

Critical Areas

Coordination

Topsky

Releasing traffic from the holds

EBG Nord-B

Übersichtskarte EBG Nord-B

Einzelsektoren

Sektor Eider East - EIDE

Sektor Eider West - EIDW

Sektor Friesland - FRI

EBG Ost

Overview EBG OST

Sectors

Sector Börde - BOR

Sector Fläming - FLG

Sector Mark - MAR

Sector Müritz - MRZ

VPA North East (ED-R 401)

Overview

Separation

Priority Airways

VPA Re-Routings

EDDB Inbound/Outbound Traffic

EKCH/EKRN/ESMS Inbound Traffic

EKCH/EKRN/ESMS/EKRK Outbound Traffic

ATC Service and Responsibilities

EBG Süd

Übersichtskarte EBG Süd

Sektoren (below FL105)

Sektoren (above FL105)

Einzelsektoren

Sektor Deister - DST

Sektor Ems - EMS

Sektor Harz - HRZ

Sektor Hannover - HAN