# EDDG - Münster/Osnabrück Airport # Overview Traffic at the airport is usually characterized by VFR and holiday flights, mixed with some scheduled flights. A specialty of Münster/Osnabrück are the two uncontrolled grass runways North of the hard surface runway. **Münster/Osnabrück is an unrestricted airport** and **part of the [S1 minor program](https://knowledgebase.vatsim-germany.org/books/langen-fir-edgg-cw9/page/s1-training "EDGG S1 minor program")**. GND and TWR can be staffed by all controllers with an **S1** rating or higher who have passed the **required moodle courses**. The Hamm sector (APP) and Münster/Osnabrück Director can be staffed by all controllers with an **S3** rating or higher. ### Münster/Osnabrück ATC Stations
**Station** | **Station ID** | **Login** | **Frequency** | **Remark** | **Endorsement** |
**ATIS** | ADG | EDDG\_ATIS | 127.180 | -- | -- |
**Ground** | DGG | EDDG\_GND | 121.880 | -- | unrestricted: [EDDG GND & TWR CBT](https://moodle.vatsim-germany.org/course/view.php?id=60 "Course EDDG Tower (VATGER Moodle)") |
**Tower** | DGT | EDDG\_TWR | 129.805 | -- | unrestricted: [EDDG GND & TWR CBT](https://moodle.vatsim-germany.org/course/view.php?id=60 "Course EDDG Tower (VATGER Moodle)") |
**Director** | DGAT | EDDG\_F\_APP | 129.180 | relief position | unrestricted: no course |
**Hamm sector** | HMM | EDDG\_HMM\_APP | 129.300 | airborne frequency if HMM or PADH is staffed | unrestricted: no course |
All aerodrome stations at Münster/Osnabrück use the **callsign "Münster"**, e.g. "Münster Tower". The Director station uses the full airport name as the callsign, i.e. "Münster/Osnabrück Director". The normal radar station uses the default "Langen Radar" callsign.
### Quickview [](https://dms.vatsim-germany.org/s/BxBMGnRZnSJbKri "EDDG Quicksheet (VATGER DMS)") *click on the image to open the printable quicksheet* # Ground Münster Ground is responsible for startup and enroute clearance and all aircraft movements at the airport. ### Departure Routes Initial climb for all departure routes is 5000ft AMSL.**Waypoint** | **RWY 07** | **RWY 25** | ||
**DOMEG | **E** | -- | **C** | -- |
Y | Prop/Turbuprop up to 5.7 t MTOW | Z | Jet up to 20 t MTOW & Prop/Turboprop | |
**RKN** *Rekken* | **E** | **-** | **C | -- |
Y | Jet up to 20 t MTOW & Prop/Turboprop | |||
**OSN** *Osnabrück* | **E | -- | **C** | -- |
X | Jet up to 20 t MTOW & Prop/Turboprop | |||
**HMM** *Hamm* | Y | Prop/Turbuprop up to 5.7 t MTOW | Z | Jet up to 20 t MTOW & Prop/Turboprop |
**VRP** | **Entry / Exit** |
**D** | exit rwy 25 |
**N1 - N2** | both |
**T** | exit rwy 07 + entry |
**E** | both |
**S** | both |
**W** | both |
Outbounds should contact APP/CTR **immediately when airborne** unless explicitly told to remain on Tower frequency.
# 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. [](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2022-10/edgg-hmm.png)*Langen 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 from the west and are released for turns and descend. Inbounds on the **BAMSU STAR** will enter the sector descending to reach level at 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**. Inbounds to **EDLV** and **EDLN** will leave the sector via **SOVUX**. 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 climbing FL240 to Maastricht in north-eastern direction. **Inbounds Amsterdam EHAM and EHAA FIR:** Most of the inbounds to Amsterdam EHAM and the EHAA FIR (e.g. EHRD, EHLE...) 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 according to the [LoA](https://knowledgebase.vatsim-germany.org/books/langen-fir-edgg/page/amsterdam-fir-ehaa-langen-fir-edgg "LoA EDGG - EHAA"). **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.**Active runways for EDDL** has to be set for correct level assignments and sector borders! **Only** set the **DEP RWY**, no need to activate the airport itself.
### Restricted Area There are several ED-Rs within the eastern part of sectors PADL and HMM. The military **ED-R 203A** "Münsterland" reaches from **FL80 up to FL150**. Above this is the **ED-R 203B** between **FL150 to FL200**. Both ED-Rs are regular active. Additionally ED-R 162 "Lanta Paderborn" is located within the mentioned ED-Rs reaching from 3.500 ft AMSL up to FL125. All restricted areas are automatically activated in Euroscope according the real world airspace use plan. When active, all flights should stay outside the active ED-Rs. [](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2022-10/edgg-padl-hmm-edr203.png)*ED-R 203A from FL80 to FL150 (red area) - © [openflightmaps.org](https://www.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 (257° L | 5000+) should be used for that up to FL240. Sector Hamm should not use holdings at OSN VOR (207° R | 5000+) for transfering traffic, this traffic need to hold above FL70 within the responsibility of Bremen Radar.