EDWW - Bremen Radar

Sector ALR	Sector EID	Sector HEI	Sector HAM	Sector FRI
EDWW_A_CTR	EDWW_E_CTR	EDWW_H_CTR	EDDH_APP	EDDW_APP
EDWW_H_CTR	EDWW_A_CTR	EDWW_A_CTR	EDWW_H_CTR	EDWW_E_CTR
			EDWW_A_CTR	EDWW_A_CTR
EDWW_W_CTR
EDWW_CTR

Sector JEV	Sector HOL
EDYY_JL/JH/HL/HH_CTR
EDWW_E_CTR
EDWW_A_CTR
EDWW_W_CTR
EDWW_CTR

Sector Splits

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

Sector Müritz and Börde

Visual Display of Sector Split

Sector Müritz and Fläming

Visual Display of Sector Split

Sector Mark and Fläming

Visual Display of Sector Split

Sector Mark and Müritz

Visual Display of Sector 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

Sector Splits

Sector Splits - EBG Süd

Single Sector

Sector Ems Complete

This sector covers all EBG Süd stations and EDYY CEL + EDYY SOL + EDYY MNS.

Sector Harz Complete

This sector covers all EBG Süd stations and EDYY CEL + EDYY SOL.

Two Split

Sector Ems and Harz

Visual Display of Sector Split

Sector Owners

Sector EMS	Sector HRZ	Sector HAN
EDWW_S_CTR	EDWW_R_CTR	EDDV_APP
EDWW_R_CTR	EDWW_S_CTR	EDWW_R_CTR
		EDWW_S_CTR
EDWW_W_CTR
EDWW_CTR

Sector CEL	Sector SOL	Sector MNS
EDYY_CL/CH/SL/SH/ML/MH_CTR		EDYY_RL/RH/ML/MH/MM_CTR
EDWW_S_CTR	EDWW_R_CTR	EDGG_PAH_CTR
EDWW_R_CTR	EDWW_S_CTR	EDYY_SL/SH_CTR
		EDWW_S_CTR
EDWW_W_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, HAM

EBG Nord-A

Overview EBG Nord-A

Sectors below FL105

Sectors above FL105

EBG Nord-A

Sectors

Sector Aller - ALR

Main Traffic Flows:

EDDH/HI-Outbounds via HABFU, IDEKO, and WSN
EDDW-Outbounds via WSN and GESTO
EDDV-Outbounds via IDEKO
EDDH/HI-Inbounds via REVLA and BASUM to RIBSO
EDDW-Inbounds via GIBMA and EKROV
EDDV-Inbounds via IDEKO

Main Crossing/Conflict Points:

Vicinity of WSN
Vicinity of ELSOB

IFR Aerodromes within the Sector:

None

Sector Chart:

Sector Heide - HEI

Main Traffic Flows:

EDDH/HI/HL-Outbounds via AMLUH, LUGEG, HAM and RAMAR
EDDV-Outbounds via CEL and BATEL
EDDW-Outbounds via GESTO
EDDH/HI/HL-Inbounds via BOGMU, NOLGO, RARUP and HAM
EDDV/VE-Inbounds via DRIBO and HLZ
EDDW-Inbounds via GESTO

Main Crossing/Conflict Points:

Vicinity of HAM
Vicinity of HLZ
Vicinity of RAMAR
Vicinity of BOGMU

IFR Aerodromes within the Sector:

None

Sector Chart:

Sector Hamburg - HAM

Further information: SOP Hamburg.

Sector Chart:

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

EID, FRI

EBG Nord-B

Overview EBG Nord-B

EBG Nord-B

Sectors

Sector Eider - EID

Main Traffic Flows:

EDDH-Outbounds via ELSOB and SOKWO
EDDW-Outbounds via SOFED
EDDH-Inbounds via OSTOR to RIBSO and EKERN to BOGMU
EDDW-Inbounds via REVLA to ALR
EKBI-Inbounds via TUSKA and AMRAK
Military into ED-Rs, ED-Ds and TRA 201 or EUCSEA

Main Crossing/Conflict Points:

Vicinity of ABFAD
Vicinity of SOKWO-RENSU

IFR Aerodromes within the Sector:

Sylt - EDXW
Kiel-Holtenau - EDHK (uncontrolled)
Nordholz - ETMN (military)
Hohn - ETNH (military)
Schleswig - ETNS (miliatyr)

Sector Chart:

Sector Friesland - FRI

Further information: SOP Bremen.

Sector Chart:

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:

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

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

EMS, HRZ, HAN

EBG Süd

Overview EBG Süd

Sectors below FL105

Sectors above FL105

EBG Süd

Sectors

Sector Ems - EMS

Main Traffic Flows:

EDDH/HI-Outbounds via HABFU and IDEKO
EDDW-Outbounds via BASUM, WIMCI and NIE
EDDV-Outbounds via NIE and VAXEV
EDDG/LW-Outbounds via OSN
EDDH/HI-Inbounds via BASUM
EDDW-Inbounds via BASUM, NIE and PIXUR
EDDV-Inbounds via NIE
EDDG/LP/LW-Inbounds via OSN
EDDL-Inbounds via OSN

Main Crossing/Conflict Points:

Vicinity of NIE
Vicinity of OSN
Vicinity of BASUM
Vicinity of ROBEG

IFR Aerodromes within the Sector:

Diepholz - ETND (military)

Sector Chart:

Sector Harz - HRZ

Main Traffic Flows:

EDDV-Outbounds via POVEL, WRB and WERRA
EDDW-Outbounds via SAS and VAXEV
EDVK-Outbounds via XAROL and ELNAT
EDLP-Outbounds via WRB
EDDL/LW-Outbounds via ESADU
EDDV-Inbounds via SAS and ROBEG
EDDW-Inbounds via SAS
EDLW-Inbounds via ESADU
EDLP-Inbounds via WRB

Main Crossing/Conflict Points:

Vicinity of SAS
Vicinity of WRB
Vicinity of ROBEG
Vicinity of POVEL

IFR Aerodromes within the Sector:

Kassel-Calden (EDVK)

Sector Chart:

Sector Hannover - HAN

More information SOP Hannover.

Sector Chart:

Login	Sector Indicator	Frequency	Callsign	Remark
EDWW_A_CTR	ALR	126.325	Bremen Radar	primary station EBG Nord A+B

Login	Sector Indicator	Frequency	Callsign	Remark
EDWW_E_CTR	EID	124.075	Bremen Radar	primary station EBG Nord B

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

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

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

EDWW - Bremen Radar

Sector Splits

Sector Splits - EBG Nord

Single Sector

Sector Aller Complete

Sector Eider Complete

Sector Heide Complete

Two Split

Sector Aller and Eider

Sector Aller and Heide

Sector Eider and Heide

Three Split

Sector Aller, Eider and Heide

Sector Owners

Sector Split - 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)

Sector Splits - EBG Süd

Single Sector

Sector Ems Complete

Sector Harz Complete

Two Split

Sector Ems and Harz

Sector Owners

EBG BER

Einzelsektoren

Sektor Berlin Arrival North/South - DBAN/DBAS

Sektor Berlin Departure North/South - DBDN/DBDS

EBG Nord-A

Overview EBG Nord-A

Sectors below FL105

Sectors above FL105

Sectors

Sector Aller - ALR

Sector Heide - HEI

Sector Hamburg - HAM

Holdings Hamburg Inbounds

EDDH Holdings and STARs

Critical Areas

Coordination

Topsky

Releasing traffic from the holds

EBG Nord-B

Overview EBG Nord-B

Sectors

Sector Eider - EID

Sector 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

Overview EBG Süd

Sectors below FL105

Sectors above FL105