Skip to main content

Arrival - Sector Hamm

Responsible for all arrivals and departures into Münster/Osnabrück is Langen Sector Hamm (HMM). Most of the time this sector also covers sector Paderborn Low (PADL) which is responsible for Dortmund EDLW and Paderborn/Lippstadt EDLP.

EDGG_HMM.pngLangen Sector Hamm HMM

Münster Arrivals/Departures

Inbounds: All flights into Münster have to use BAMSU (inside DLA sector) or DOMEG as last waypoint. All STARs end at HMM, thereafter the published ILS, RNP or NDB approach can be cleared. If using vectors to the final, the MVA need to be taken into account. Inbounds via BASUM are already cleared for the STAR by the previous controller. It's also possible to coordinate directs with the previous controller to HMM without using the published arrival, especially when coming from Amsterdam FIR.

Inbounds from Amsterdam via SONEB Z841 DOMEG will enter the sector atfrom the westFL110 and are released for turns and descend. Inbounds on the BAMSU STAR will enter the sector descending to FL90reach to reachlevel at HMM (around FL170).HMM.

Traffic Flows

Inbounds Düsseldorf: One of the main duties at Hamm is to sequenze the inbound flow into Düsseldorf EDDL. Three routings entering the sector coming from Bremen/Maastricht via OSN, RORUS and DENOL, merging at HMM to continue via T851 to HALME. All inbounds are handed over to Düsseldorf Arrival at FL130. Inbounds to EDLV and EDLN will leave the sector via SOVUX at FL120..

After coordination with Düsseldorf Arrival, sector Hamm may already clear the appropriate arrival/transition for the inbound via HALME.

Outbounds Düsseldorf: Outbounds Düsseldorf will enter sector Hamm via MEVEL and will leave the sector most of the time climbing FL240 to Maastricht in north-eastern direction.

Inbounds Amsterdam: Most of the inbound to Amsterdam EHAM will overfly sector Hamm towards NORKU and will always stay clear of the sector. Some lower routings lead via HMM T281 NORKU as well as HMM L602 RKN and are transfered at RFL.

Inbounds Dortmund and Paderborn: If sector Paderborn Low PADL is staffed, inbound traffic to Dortmund EDLW and Paderborn/Lippstadt EDLP need to be coordinated individually. Usually FL80 is used.

Handoff Levels

All levels for inbound, outbound and transfering traffic  for sectors HMM and PADL are available at the Quicksheet. All levels that are not listed need to be coordinated individually!

Restricted Area

The military ED-R 203A "Münster" is covering a huge part within the sectors HMM and PADL from FL80 up to FL150. It is active during the week from monday to friday 0700 (0600) until 2230 (2130) and on friday only until 1600 (1500) UTC (summer) and by NOTAM. All flights should stay outside the active ED-R.

EDGG_PADL_HMM_EDR203.pngED-R 203A from FL80 to FL150 (red area) - © openflightmaps.org

VFR Traffic

In real life the sector is known for a lot of VFR and training flights due to many flight schools located in this area.

FIS: All VFR traffic that are provided with Flight Information Service should get Squawk 7742.

TMZ: VFR Ttraffic within the TMZ of Münster not using flight information services should set transpondercode 6104.

Holdings

If holdings are required (e.g. for Düsseldorf inbounds) HMM VOR should be used for that up to FL240.

Sector Hamm should not use holdings at OSN for transfering traffic, this traffic need to hold above FL70 within the responsibility of Bremen Radar.

Back to top