EDDM

Inhaltsverzeichnis 1 Overview 2 General Regulations 3 Airspace Delegation 4 ATC Stations 4.1 München 4.2 Wien 5 Routing and Handoff requirements 5.1 From München FIR to FIR Wien 5.1.1 EDDM departures 5.1.2 LOWI arrivals 5.1.3 LOWK arrivals 5.1.4 LOWL arrivals 5.1.5 LOWS arrivals 5.2 From FIR Wien to München FIR 5.2.1 LOWI departures 5.2.2 LOWL departures 5.2.3 LOWS departures 5.2.4 EDDM arrivals 5.2.5 EDDN arrivals 5.2.6 EDDS arrivals 5.2.7 EDMA/EDMO arrivals 5.2.8 LSZH/LSMD arrivals 5.2.9 EDNY/EDJA/LSZR arrivals

Overview

This is a copy of the original LoA, printed as PDF Version 2.0 from 25th May 2008 by Rainer Brinkschulte, Thorsten Zörner (FIR München) and Bernhard Harb, Clemens Moritz (FIR Wien). This LoA may only be used within the simulated VATSIM environment and is therefore not to be used for real life ATC purposes. Unauthorized use, distribution, duplication or modification of this document on any media, website or in any form is strictly prohibited.

General Regulations

RFL = requested flight level

Handoffs (including transfer of communication) shall be made latest 10 NM prior the respective boundary (FIR border, APP airspace, delegated airspace). After handoff, traffic is NOT released for climb, descent or turns unless otherwise specified in the regulations below.

Traffic overflying EDMM and/or LOVV shall be handed off on a valid ATS route at RFL using the semicircular crusing level system (even/odd). Direct routings shall be coordinated.

Spacing between two aircraft on same level and same routing shall be at least 10 NM if the speed of the succeeding traffic is equal or less than the speed of the preceding traffic, otherwise at least 15 NM. Spacings deviating from this regulation shall be coordinated.

Traffic shall be handed off at the levels defined in the regulations below. If a specified level restriction cannot be met due to a lower RFL, traffic shall be handed off AT RFL, if this does not cause a conflict with any other traffic. Otherwise traffic shall be coordinated.

If a traffic situation is not covered herein, individual coordination between the concerned sectors shall be made. �FLxxx / �FLxxx means „descending / climbing to a specified FL“, without any further restriction. Any required crossing/speed restriction shall be added separately.

Airspace Delegation

• Generally the airspace west of the Rocky-Line

465604n 115030e – 472551n 115624e – 473709n 120341e – 474225n 124440e – 473310n 125112e – 475637n 123749e – 480250n 122727e – :480309n 123045e – 480850n 124245e – 481451n 124034e – 481559n 124150e – 481549n 130545e – 481747n 131053e – 484948n 134711e

is permanently delegated from LOVV to EDMM, except the AoR Innsbruck.

• Generally the airspace east of the Rocky-Line

472551n 115624e – 473709n 120341e – 474225n 124440e – 473310n 125112e – 475637n 123749e – 480250n 122727e – 480309n 123045e – :480850n 124245e – 481451n 124034e – 481559n 124150e – 481549n 130545e – 481747n 131053e – 484948n 134711e

is permanently delegated from EDMM to LOVV.

• The airspace overhead the EDMM sectors C, E, K and R is permanently delegated from EDUU to EDMM, expanding these sectors up to UNL.

• The airspace overhead the Area Königssee

473904n 120659e – 475637n 123749e – 474320n 125205e – 474225n 124440e – 473757n 120951e

is permanently delegated from EDMM to LOWS_APP GND-FL125.

ATC Stations

München

EDMM_U_CTR	München Radar (Upper)	128.970	FL316-UNL
EDDM_C_CTR	München Radar (CHI)	133.670	GND-FL315
EDDM_E_CTR	München Radar (EGG)	129.550	GND-FL315
EDMM_K_CTR	München Radar (KPT)	124.050	GND-FL315
EDMM_R_CTR	München Radar (RDG)	132.500	GND-FL315
EDDM_N_APP	München Arrival(north)	128.020	GND-FL195
EDDM_S_APP	München Arrival(north)	120.770	GND-FL195

• EDMM_R_CTR will be responsible for all EDMM_x_CTR sectors if no other EDMM_x_CTR is online.
• EDMM_U_CTR covers sectors C, E, K and R above FL316. If it is not online, those sectors expand to UNL.
• If EDMM_E_CTR is not online, EDMM_R_CTR will be responsible for the respective airspace.
• If EDMM_C_CTR is not online, EDMM_K_CTR will be responsible for the respective airspace.
• If EDDM_S_APP is not online, EDDM_N_APP will be responsible for the respective airspace.

Wien

LOVV_CTR	Wien Radar	134.350	FL316-UNL
LOVV_L_CTR	Wien Radar (lower)	129.2000	GND-FL125/165
LOVV_U_CTR	Wien Radar (upper)	131.350	FL246-UNL
LOWI_APP	Innsbruck Radar	119.270	GND-FL165
LOWS_APP	Salzburg Radar	123.720	GND-FL125
LOWL_APP	Linz Radar	129.620	GND-FL165

• LOVV_CTR will be responsible for all LOVV_x_CTR sectors if no other LOVV_x_CTR is online.
• If LOWI_APP is not online, LOVV_L_CTR will be responsible for the respective airspace.
• If LOWS_APP is not online, LOVV_L_CTR will be responsible for the respective airspace.
• If LOWL_APP is not online, LOVV_L_CTR will be responsible for the respective airspace.

Routing and Handoff requirements

From München FIR to FIR Wien

EDDM departures

Traffic departing from EDDM shall be routed via...

* MEBEK Y105 KIRDI
* Level: up to FL190
* Release: released for climb
* Handoff: EDDM_S_APP -> LOVV_CTR

LOWI arrivals

Traffic arriving at LOWI shall be routed via...

*TULSI DCT RTT (on STAR)
*Level: down to FL130, TULSI at FL150
*Release: released for descent and turns after passing release line
*Handoff: EDDM_C_CTR -> LOWI_APP

*ALGOI DCT KTI (on STAR)
*Level: down to FL150 (FL180 at ALGOI)
*Release: descent and turns after passing release line
*Handoff: EDDM_K_CTR -> LOWI_APP

LOWK arrivals

Traffic arriving at LOWK shall be routed via...

*UNKEN UL603 or LIZUM UL74/UL607
*LEVEL: FL330
*Release: none
*Handoff: EDDM_C_CTR -> LOVV_CTR

LOWL arrivals

Traffic arriving at LOWL shall be routed via...

*ESEGA L605 or PASAU T703
*Level: down to FL110
*Release: none
*Handoff: EDDM_E_CTR -> LOWL APP

*INSOL U/L725
*Level: FL270 at INSOL
*Release: none
*Handoff: EDDM_C_CTR -> LOVV_U_CTR

LOWS arrivals

Traffic arriving at LOWS shall be routed via...

*MEBEK T702
*Level: down to FL070 (FL090 at MEBEK)
*Release: descent and turns after passing the release line
*Handoff: EDDM_S_APP -> LOWS_APP
*NOTE: EDDM_S_APP may clear dct SBG without coordination

*TITIG L173
*Level: FL070 at TITIG
*Release: descent and turns after passing the release line
*Handoff: EDDM_S_APP -> LOWS APP
*NOTE: EDDM_S_APP may clear dct SBG without coordination

*EGG T700
*Level:down to FL080 (FL100 at EGG)
*Release: descent afer passing EGG
*Handoff: EDDM_E_CTR ->LOWS_APP

*CHIEM T701
*Level: FL120 at CHIEM
*Release: descent and turns after passing the release line
*Handoff: EDDM_C_CTR -> LOWS_APP

From FIR Wien to München FIR

LOWI departures

Traffic departing from LOWI shall be routed via...

*KOGOL M726
*Level: up to FL160
*Release: Release for climb
*Handoff: LOWI_APP -> EDMM_C_CRT
*NOTE: LOWI_APP may clear DCT KOGOL and flights with destination EDDM DCT ANDEC
without coordination

*KOGOL L608 KPT
*Level: up to FL120
*Release: none
*Handoff: LOWI_APP -> EDMM_C_CTR
*NOTE: SID strictly for A/C unable to climb higher than FL120

*LEMSO Y703 KPT or MOGTI L12 KPT
*Level: up to FL160
*Release: released for climb
*Handoff: LOWI_APP -> EDMM_K_CTR

LOWL departures

Traffic departing from LOWL shall be routed via...

*RENKA L610 or LAMSI L604 or SUBEN T161
*Level: 'up to FL120
*Release: released for climb
*Handoff: LOWL_APP -> EDMM_E_CTR

LOWS departures

Traffic departing from LOWS shall be routed via...

*TITIG L173 or NAPSA
*Level: up to FL090
*Release: released for climb after passing L856
*Handoff: LOWS_APP -> EDDM_S_APP

*TRAUN L856
*Level: up to FL120
*Release: released for climb
*Handoff: LOWS_APP -> EDDM_S_APP

*SIMBA Y700
*Level:up to FL110
*Release: released for climb
*Handoff: LOWS_APP -> EDMM_E_CTR

EDDM arrivals

Traffic arriving at EDDM shall be routed via...

*MODSA Q112 NAPSA
*Level: FL140 at MODSA
*Release: descent to FL100 and turns after MODSA
*Handoff: LOVV_CTR -> EDDM_S_APP

*AMADI Q113 NAPSA
*Level: FL130 at AMADI
*Release: descent FL100 and turns after AMADI
*Handoff: LOVV_CTR -> EDDM_S_APP

EDDN arrivals

Traffic arriving at EDDN shall be routed via...

*SUBEN T161
*Level: FL300
*Release: none
*Handoff: LOVV_U_CTR -> EDMM_E_CTR

EDDS arrivals

Traffic arriving at EDDS shall be routed via...

*SBG U/L173
*Level: FL280
*Release: none
*Handoff: LOVV_U_CTR -> EDMM_C_CTR
*NOTE: LOVV_U_CTR may clear direct MUN without coordination

EDMA/EDMO arrivals

Traffic arriving at EDMA or EDMO shall be routed via...

*SBG L173
*Level: FL150
*Release: descent to FL100 and turns after SBG
*Handoff: LOVV_CTR -> EDDM_S_APP

LSZH/LSMD arrivals

Traffic arriving LSZH or LSMD shall be routed via...

*SBG U/L856
*Level: RFL
*Release: none
*Handoff: LOVV_U_CTR -> EDMM_K_CTR

*ERKIR L/UL608
*Level: FL320
*Release: none
*Handoff: LOVV_U_CTR -> EDMM_K_CTR

EDNY/EDJA/LSZR arrivals

Traffic arriving EDNY, EDJA or LSZR shall be routed via...

 *SBG U/L856
*Level: FL300
*Release: none
*Handoff: LOVV_U_CTR -> EDMM_K_CTR

*ERKIR L/UL608
*Level: FL260
*Release: none
*Handoff: LOVV_U_CTR -> EDMM_K_CTR