EDUU - Rhein Radar

Upper Airspace above FL245 (EDGG), FL315 (EDMM) and FL285 (EDWW)

Overview

EDUU_Sectors_ALL.png

Above FL245 - Langen FIR

FFM, FUL, NTM, SLN, TGO, WUR

Above FL245 - Langen FIR

Above FL245 - Langen FIR (EDGG)

Sector Würzburg - WUR

Login
Sector Indicator
Frequency
Callsign
Remark
EDUU_WUR_CTR
WUR
134.085
Rhein Radar

primary

Sector Würzburg handles mainly traffic in- and outbound to EDDM. Traffic to EDDM is received from all sectors at FL350 or below and should be handed over FL250 to EDMM at DKB.

Traffic outbound EDDF via CINDY will be handed over climbing FL240 from EDGG. This traffic is handed over climbing FL310 to EDMM and has to cross NOMBO FL 245 or above. After coordination with EDMM, traffic that reaches FL310 before the sector border can also be transferred directly to EDUU Isar with release for climb.

Inbounds LSZH (and enroute traffic to the south) will be on N869. There is also the (slim) possibility of enroute traffic in the other direction due to bad routes. Inbounds LSZH should be handed over to TGO at FL320.

EDDM outbounds via Y101 will climb in your sector and join flows to the north or northwest. EDDM outbounds are released for climb FL310 inside EDMMs airspace. WUR can request SLN and NTM to direct EDDM inbounds direct DKB coming from Belgium. By doing so traffic stays mostly clear of FFM.

München Inbounds

Kitzingen is responsible for combining the two traffic flows from Brussels (via MOVUM) and the Düsseldorf area (via BOMBI) at HAREM. All traffic via HAREM T104 ROKIL is handed over to München radar at DKB on FL250. These aircraft are not released for further descent due to the outbounds from EDDS crossing below to the north-east. If a deviating release is issued by Langen Radar, it must always be given by Topsky!

Routes from the Lower (no direct route) which nevertheless fly in the Upper should get a direct to DKB as soon as possible to avoid unnecessary miles.

Outbounds from Frankfurt to Munich Airport (max. FL230) can generally be transferred to Munich Radar independently of the inbounds from the Upper. If possible, however, Langen Radar should take care to sort the aircraft into the sequence.

Since on the relatively straight route through the sector only a few directs can be used to establish a sequence (max. 3 NM possible), speeds should be used on time. If necessary, headings can also be used to generate additional miles if needed (30° deviation on 30 miles results in about 3 NM). If it is not possible to generate the necessary 10 NM, individual aircraft can also be handed over at FL260 after coordination.

Inbounds Munich can also be handed over via DINKU and NOMBO only after coordination with Munich Radar, but this should only be done in exceptional cases.

Sector Nattenheim - NTM

Login
Sector Indicator
Frequency
Callsign
Remark
EDUU_NTM_CTR
NTM
132.080
Rhein Radar

secondary

This sector receives all ULKIG and SOBRA departures from Frankfurt and will hand them over to Maastricht (Brussel sectors). Other than that there's much east and westbound traffic. EBBR inbounds both from SLN and FFM will come to this sector and need to behanded over to the lower Langen Radar. 

Sector Tango - TGO

Login
Sector Indicator
Frequency
Callsign
Remark
EDUU_TGO_CTR
TGO
132.405
Rhein Radar

--

Sector Tango will receive all departures from LSZH and other northbound traffic via (U)N851. Note, that your airspace starts at FL 235 there to facilitate this. Also you will receive LSZH inbounds via EMKIL from WUR on FL320. TGO needs to descend them FL240 at TEDGO and send them to BAD. EMPAX inbounds need to be sent descending along the Arrival to BAD. There’s also the chance for EDDM inbounds via GESLU which need to be sent FL250 to EDMM. 

Sector Fulda - FUL

Login
Sector Indicator
Frequency
Callsign
Remark
EDUU_FUL_CTR
FUL
133.655
Rhein Radar

--

FUL is a small but packed sector. To reduce vertical movement in MUAC, traffic to EDDH should be handed over max FL360. Another important part is EDDF outbounds via TOBAK. This traffic will be handed over to you at FL240 and may still be below the FFM sector. In that case, traffic has to wait or you can request a climb release from FFM. Hand over traffic FL290 to EDMM/EDWW_B or, after coordination, on a higher level to EDUU Saale. Be aware that EDMM/EDWW_B is allowed to give climb FL310 inside FUL without coordination. Make sure there is no traffic on FL300 at this time.

Apart from that, northwestbound moving traffic on L602 or L604 can be handed over on cruise.

You may clear traffic DCT to GESKA, EKERN and NORTA without coordination. EDDH inbounds may be cleared DCT MADOR. Traffic towards the northwest may be cleared DCT NORKU or RKN. 

Sector Frankfurt - FFM

Login
Sector Indicator
Frequency
Callsign
Remark
EDUU_FFM_CTR
FFM
132.330
Rhein Radar

--

Many routes towards EDDM merge at BOMBI and another route from western Europe merges with this one as well at HAREM. EDDM inbounds need to be max FL350 when handover to WUR. It also covers all LSZH inbounds from the north which need to be sent max FL350 when handover to SLN. This traffic can be cleared DCT OMOGI by MUAC.

There are also EDDL inbounds (EKSAK, ARPEG) and outbounds and southbound traffic on N850. This traffic can be cleared DCT to BOMBI by MUAC.

This sector is also responsible for MARUN - NATSU outbounds from EDDF. 

Sector Söllingen - SLN

Login
Sector Indicator
Frequency
Callsign
Remark
EDUU_SLN_CTR
SLN
120.930
Rhein Radar

--

One of the main tasks of Söllingen is to pre sequence LSZH arrivals and to hand them over to BAD at LAMGO FL250. He is also responsible for all ANEKI outbounds of EDDF and southbound traffic towards LSAS. There might be some EDDM arrivals via GESLU which need to be handed over FL350 to TGO.

You may clear traffic DCT to TRA, ROTOS, WIL and OLBEN on the condition, that traffic stays clear of LFFF, TGO and west of TRA. 

Above FL245 - Langen FIR

Overview

EDFF_Sectors_(FL245_-_FL660).png

Above FL315 - München FIR

ALP, CHI, DON, ERL, ISA, SAL, SPE

Above FL315 - München FIR

Above FL315 - München FIR (EDMM)

Overview

EDUU-MM.png

Sektor Donau - DON

Login
Sector Indicator
Frequency
Callsign
Remark
EDUU_DON_CTR
DON
127.290
Rhein Radar --

Sektor Chiem - CHI

Login
Sector Indicator
Frequency
Callsign
Remark
EDUU_CHI_CTR
CHI
123.930
Rhein Radar --

Sektor Isar - ISA

Login
Sector Indicator
Frequency
Callsign
Remark
EDUU_ISA_CTR
ISA
136.335
Rhein Radar --

Sektor Alpen - ALP

Login
Sector Indicator
Frequency
Callsign
Remark
EDUU_ALP_CTR
ALP
133.755
Rhein Radar --

Sektor Erlangen - ERL

Login
Sector Indicator
Frequency
Callsign
Remark
EDUU_ERL_CTR
ERL
136.405
Rhein Radar --

Sektor Saale - SAL

Login
Sector Indicator
Frequency
Callsign
Remark
EDUU_SAL_CTR
SAL
133.860
Rhein Radar --

Der Sektor Saale betreut überwiegend Durchflüge von/nach Großbritannien und den Niederlanden sowie Norddeutschland aus bzw. nach Südosteuropa. Des Weiteren fliegen viele Flugzeuge von Süd nach Nord und umgekehrt. Nicht zu vernachlässigen ist außerdem der Verkehr nach Frankfurt (EDDF), Hamburg (EDDH), München (EDDM), Berlin (EDDB) und Prag (LKPR), welche rechtzeitig einen Sinkflug benötigen. In dieser Sektor kann aufgrund von vielen Vertikalbewegungen sehr schnell komplex werden. 

EDUU_SAL.png

Sektor Spree - SPE

Login
Sector Indicator
Frequency
Callsign
Remark
EDUU_SPE_CTR
SPE
133.285
Rhein Radar --

Der Großteil der Aufgaben des Sektors Spree besteht in der Betreuung des Enroutverkehrs durch den Sektor. Hier fliegen viele Flugzeuge durch den Sektor, welche später in den teschechischen Luftraum eintreten werden. Nicht zu vernachlässigen ist außerdem der Verkehr nach Frankfurt (EDDF), Berlin (EDDB) und Prag (LKPR), welche rechtzeitig einen Sinkflug benötigen. Auch fliegen Abflüge aus Berlin und Leipzig/Halle (EDDP) vermehrt durch diesen Sektor. 

EDUU_SPE.png



Above FL285 - Bremen FIR

HVL, OSE

Above FL285 - Bremen FIR

Above FL285 - Bremen FIR (EDWW)

Sektor Ostsee Low - OSE12

Login
Sector Indicator
Frequency
Callsign
Remark
EDUU_O_CTR
OSE
133.035
Rhein Radar primary Upper EDBB

OSE12.png

Sektor Ostsee High - OSE22

Login
Sector Indicator
Frequency
Callsign
Remark
EDUU_OH_CTR
OH2
126.785
Rhein Radar Secondary station

EDUU_OSE22.png

Sektor Havel Low - HVL12

Login
Sector Indicator
Frequency
Callsign
Remark
EDUU_H_CTR
HVL
128.235
Rhein Radar --

HVL12.png

Sektor Havel High - HVL22

Login
Sector Indicator
Frequency
Callsign
Remark
EDUU_OH_CTR
OH2 126.785 Rhein radar Secondary station

HVL22.png


Sector Owners (CTR only)

Sector OSE Low
Sector OSE High Sector HVL
Sector HVL High

EDUU_OH_CTR
EDUU_OH_CTR
EDUU_O_CTR EDUU_O_CTR EDUU_H_CTR EDUU_H_CTR
EDUU_H_CTR EDUU_H_CTR EDUU_O_CTR EDUU_O_CTR
EDWW_M_CTR EDWW_M_CTR EDWW_B_CTR EDWW_B_CTR
EDWW_K_CTR EDWW_K_CTR EDWW_F_CTR EDWW_F_CTR
EDWW_B_CTR EDWW_B_CTR EDWW_K_CTR EDWW_K_CTR


EDWW_M_CTR EDWW_M_CTR
EDWW_CTR EDWW_CTR EDWW_CTR EDWW_CTR

Tactical Directs

Rhein Radar (EDUU) - EDUU East

EDUU EAST: OSE, HVL, SPE, SAL

EDUU-EDUU

Waypoint Sector Condition
All over-fly waypoints or last waypoint of Sectorgroup

OSE, HVL

SAL, SPE

Only within EDUU Sectors OSE / HVL / SAL / SPE
AMOSA Via EDUU ERL Sector

EDUU - EDYY

Waypoint Sector Condition
TUGDU OSE, SAL
EEL

OSE

HVL

Clear of EDYY MUN Sector
DENOL
PODER
OSN
NORKU

OSE

HVL

SAL


RKN
ABAMI
NVO Clear of EDUU FFM Sector
BERXO
OTMON
XAROL

EDUU - EPWW

Waypoint Sector Condition
MAPIK, KUNER, OSKUD, KOSEX OSE, HVL, SPE
BIMPA, DOSIX Destination EPWA, EPMO

EDUU - EKDK

Waypoint Sector Condition
CDA, AAL, ODN OSE
LOKSA Destination EKBI

EDUU - ESMM

Waypoint Sector Condition
ALAMI, INRER, KOLJA, NILUG, TRS OSE
EVONA Only north of BANUB

EDUU - EDWW

Waypoint Sector Condition
BUMIL, NEBUN HVL, SPE Destination EDDH, EDHI, EDHL, EDDW

EDUU - EDMM

Waypoint Sector Condition

OMELO, HDO, SODRO,

BAMKI, TABAT

OSE, HVL

SAL, SPE


LALUK, LASIS SAL, SPE

Sector Splits

Rhein Radar sector splits.

Sector Splits

Sector Splits - EDUU above EDGG

Complete EDUU (1 controller)

EDUU complete

EDUU_WUR_CTR is the only station that will cover the whole EDUU sector. No other station will cover the whole EDUU airspace. This also means, if there is an ongoing split between two or more controllers and the EDUU_WUR_CTR disconnects or times out, there will be sectors which will no longer be covered by a EDUU station. That means that controller have to change their primary frequency in order to cover every sector again.

North/South Split (1/2 controllers)
This split is exactly the split in upper sectors you get when you split GIN/DKB without upper stations.
There are times where you want to cover only the northern (NTM/FFM/FUL) or southern (SLN/TGO/WUR) part of upper airspace. For example if you have 3 controllers and you have to split lower airspace into GIN/DKB because of traffic, but one of the upper airspaces on one of those station is way over the capacity limits, you can now cover only the upper airsapce above one of those Langen splits without having to control the complete Rhein.
This happens e.g. on LSZH tuesdays with 3 controller, where the upper airspace over GIN is not crowded, while DKB should be split at least in Upper and lower airspace.

EDUU North South Split

EDUU_FUL_CTR covers NTM, FFM and FUL

EDUU complete

EDUU_SLN_CTR covers SLN, TGO and WUR

They will not cover the respective other sectors and can either be opened alone or together.

East/West Split (2 controllers)


This split is the new standard split. The primary stations are still the same but will cover their respective side across the north-south border across EDUU over Langen FIR. If you want to split the upper into 2 stations, this shall be the split you use. On days where TGO is busy, FFM isn't and vice versa. Therefore we chose to trade TGO for FFM. Additionaly, this split allows to easily add a third controller to the split (see next section for more).

EDUU East West Split
EDUU_WUR_CTR covers FUL, WUR and TGO
EDUU_NTM_CTR
covers FFM, NTM and SLN
EDUU_NTM_CTR will not cover the stations of EDUU_WUR_CTR. Therefore if EDUU_WUR_CTR logs off and EDUU_NTM_CTR wants to control complete EDUU, the controller has to change their primary frequency to EDUU_WUR_CTR. Though EDUU_WUR_CTR will cover EDUU_NTM_CTR as described in "Complete EDUU (1 controller)".

Two stations each (3 controllers)

These splits emerge from the East/West Split. They are not possible when a North/South split is active. If that is the case however, all controllers will have to change their primary frequencies.
This split allows every controller to control two stations each. The idea is that traffic is divided evenly across controllers. Depending on the traffic flows at the time, the controllers may choose between two variants.

Variant A

EDUU Three Stationsplit | WUR, NTM and FFM

EDUU_WUR_CTR covers WUR, TGO
EDUU_NTM_CTR covers NTM, SLN
EDUU_FFM_CTR covers FFM, FUL


Variant B

EDUU Three Stationsplit

EDUU_WUR_CTR covers WUR, FUL
EDUU_NTM_CTR covers NTM, FFM
EDUU_TGO_CTR covers TGO, SLN

More controllers (4+ controllers)
Any other controller will only cover the respective single sector they log on as.

EDUU Single Sectors