LOA Langen (EDFF) - München (EDMM)
Inhaltsverzeichnis
General
Purpose
The purpose of this Letter of Agreement is to define the coordination procedures to be applied between München FIR and Langen FIR when providing ATS to air traffic (IFR/VFR) on the VATSIM network. All information and procedures described in this Letter of Agreement shall not be used for real world purposes.
Operational Status
All operational significant information and procedures contained in this Letter of Agreement shall be distributed to all concerned controllers by appropriate means. This Letter of Agreement itself constitutes public information.
Validity
This Letter of Agreement becomes effective on September 10 2020. Updates may be applied continuously by agreement of the NAV Departments and will be published in the respective forums.
Areas of Responsibility & Sectorization
Areas of Responsibility
The lateral and vertical limits of the respective areas of responsibility are as follows:
München FIR
Lateral limits: München FIR as described in AIP Germany
Vertical limits: GND – FL660
Langen FIR
Lateral limits: Langen FIR as described in AIP Germany
Vertical limits: GND – FL660
Sectorization
Any Rhein Radar station can only be staffed if the sector below is covered by another Langen/München Radar station.
München FIR
The authorative sectorization is implemented in GNG. RG München publishes an overview here.
Langen FIR
The authorative sectorization is implemented in GNG. RG Frankfurt publishes an overview here.
Delegation of the Responsibility for the Provision of ATS
General
FRKL
The airspace below FL135 and east of N50.30.00 E010.31.18 – N50.13.37 E010.17.20 – N49.51.07 E010.18.00 – N49.38.20 E010.18.20 – N49.19.20 E010.22.20 – N49.10.43 E010.35.16 is permanently delegated from EDFF to EDMM and handled by EDDN_APP.
ANS Area
The airspace between FL245 and 305 in the area N49.39.17 E010.45.56 – N49.26.30 E010.58.00 – N49.10.43 E010.35.16 – N49.17.00 E010.27.30 – N49.23.54 E010.21.22 – N49.30.40 E 010.30.12 – N49.39.17 E010.45.56 is delegated from EDFF to EDMM and handled by EDMM_A_CTR. If no responsible EDMM_CTR is online, this area is controlled by the EDGG_CTR responsible for Kitzingen sector.
Procedures for Coordination
Definitions
A release is an authorization for the accepting ATS unit to climb, descend and/or turn (by no more than 45°) a specific aircraft before the transfer of control point. The transferring ATS unit remains responsible for separation within its Area of Responsibility unless otherwise agreed. Wherever VATSIM callsigns are used to describe the terms of a certain procedure, this procedure is also applicable for all higher stations that take over the responsibilities of said station. E.g., procedures for an APP-station are also applicable for the respective CTR station fulfilling the duties of said APP station. The use of VATSIM callsigns in this document includes any variation of said callsigns. E.g. any procedure applicable for EDMM_CTR may also be used by EDMM_X_CTR or EDUU_X_CTR.
General Conditions
Coordination of flights shall take place via the agreed coordination points (COP). Coordinated flights shall be handed off via a valid COP. Any deviation shall be coordinated verbally, by text or by EuroScope inter-sector coordination. 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. After Transfer of communications, traffic is NOT released for climb, descent or turns until Transfer of control or otherwise specified in this Letter of Agreement.
IFR flights from München FIR to Langen FIR
| Destination | COPX | Level Allocation | Special Conditions |
|---|---|---|---|
| EDFH EDRZ EDSB EDDR ELLX | ALAXA | FL320 | |
| EDDF | ASPAT | FL240 | GIMAX @FL240 Clearance for ASPAT-STAR or via T161 by München |
| EDDK EDLW EDLA EDKZ EDLP EDLI EDVK EDFQ EDDL | VELIS | FL300 | |
| EDDF | ESEGU | FL220 | |
| EDDF | ROBEL | FL200 | Descending, cross ROBEL at level released for turn and descent below FL245 |
| EDDF | VAGAB | FL210 | RUNEN@ FL210 released for turn and descent below FL245 |
| EDDR EDFH EBLG EHBK ELLX | INBED | FL320 | |
| LFST LFGA LFSB LFJL | KUNOD | FL280 | |
| EDDS | LUPOL | FL180 | |
| EDDF | PETIX | FL240 | ODEGU@ FL240 Clearance for PETIX-STAR by München |
| EDSB EDDR EDRZ EDFH EBLG EHBK ELLX | PETIX | FL280 | |
| EDDS | RUFGA | FL240 | Released for turns passing GORKO |
| ETAR EDDR EDRZ EDSB | RUFGA | FL220 | Released for turns passing GORKO |
| EDFM EDFV EDRY | RUFGA | FL200 | Released for turns passing GORKO |
| EDDK EDLW EDLP | SULUS | FL260 | |
| EDFM EDFV EDRY | SULUS | FL220 | |
| EDDF EDDK EDDL EDF* EDK* EDL* | TAMEB | FL240 | (old routes) |
| EDDS EDSB EDDR EDR* EDTY EDTL EDM* EDJA ETS* | TAMEB | FL320 | (old routes) |
| EDDS | TEKSI | FL110 | Flights are released for turn passing a line DODIL – LUP subject traffic leaving the AoR |
| EDDK EDLW EDLA EDKZ EDLP EDLI EDVK | GASKA TESDU |
FL320 | |
| EDDS EDSB | KEGOS | FL220 | |
| EDLP EDL* | VAGAB | FL320 |
| Departure | COPX | Maximum Level Allocation | Special Conditions |
|---|---|---|---|
| LKPR | ALAXA | FL320 | |
| EDDP EDDE EDAC | AMOSA | FL310 | |
| EDDN | DKB SUKAD IBAGA |
FL130 | Flights from RWY28 are released for turns Flights from RWY10 are released for turns and climb |
| EDDE | ERSIL | FL140 | Climbing |
| EDDE | RASPU KOMIB |
FL260 | |
| EDDM | GORKO | FL340 | |
| EDDN EDQ* | GORKO | FL260 | Climbing, latest GASKA @ level |
| EDDM EDMA EDMO | INBED | max. FL300 | Climbing, latest IBAGA @ level |
| LOWI | KUNOD | FL340 | |
| EDJA | PELOG | FL80 | |
| EDAC EDDP | ROBEL | FL280 | |
| EDJA | SUDEN | FL80 | |
| EDDN EDQM EDQD | SULUS | FL180 | |
| EDDP | TAMEB | FL260 | |
| EDDP EDAC | KOMIB | FL300 | |
| EDDP EDAC | AMOSA | FL310 | |
| EDQ* | VAGAB | FL180 |
IFR flights from Langen FIR to München FIR
| Destination | COPX | Level Allocation | Special Conditions |
|---|---|---|---|
| EDQ* | BOKNI | FL170 | |
| EDMA EDMO EDJA ETSN ETSI ETSA ETSL | DKB NOMBO |
FL110 | Descending, out of FL150 |
| EDDM | DKB NOMBO |
FL230 | Departure EDFF |
| EDDM | DINKU NOMBO DKB |
FL250 | Overflow routings via DKB, NOMBO and DINKU can be used in parallel: DINKU DCT AKANU, NOMBO DCT RIXED, DKB DCT ANORA |
| EDDM | ELMOX | FL250 | Clearance to descend via ELMOX STAR by Langen, if traffic permits |
| EDDM | GESLU | FL250 | |
| EDDN | VELIS | FL170 | |
| EDDN | ERTES | FL130 | Descending, out of FL160 |
| EDDN | LETKU | FL110 | Descending, out of FL135 |
| EDDE EDBA EDGE EDOU | MADET ROBEL |
FL110 | Released for descent and turn |
| EDDE | RASPU | FL210 | |
| EDMM | GUPIN | FL170 | |
| EDJA | REUTL | FL90 | |
| EDAC EDDP | TAMEB | FL250 | |
| EDDP | ERSIL | FL260 | via ERSIL - ESEGU |
| EDDP | IBAGA | FL310 | |
| EDDC | SULUS | FL370 | |
| EDQ* | SULUS | FL170 | |
| LOWI LOWS | DKB | FL310 | |
| LOWI LSZS LSZA LSZL LIPB | BATUB UTABA |
FL310 |
| Departure | COPX | Maximum Level Allocation | Special Conditions |
|---|---|---|---|
| EDDS | ABTAL KUNOD |
FL140 | Climbing, released for turns when passing FL100 Direct handoff to EDMM |
| EDDS EDSB EDFM | AMOSA | FL230 | |
| EDDF EDFF | BARSU | FL230 | |
| EDDF EDFE EDFZ ETOU | ERSIL | FL290 | |
| EDDF EDFE EDFZ ETOU | TAMEB | FL290 | |
| EDDR EDRZ EDSB | GUPIN | FL230 | |
| EDDS EDSB EDTY | KEGOS | FL230 | |
| EDDF EDFE EDFZ ETOU | NOMBO | FL310 | Climbing, out of FL250 |
| EDDF EDFF EDDS EDSB | SULUS | FL230 | Or higher odd up to 290, level @ SULUS |
VFR flights from München FIR to Langen FIR
For controlled VFR flights and VFR at night flights above 2500 feet GND coordination, transfer of control and transfer of communication shall take place as for IFR flights. Uncontrolled VFR flights shall be transferred to the appropriate sector if in radio contact. If online, EDGG_F_CTR (Langen Information), 128.950, shall be the primary sector for uncontrolled VFR flights.
VFR flights from Langen FIR to München FIR
For controlled VFR flights and VFR at night flights above 2500 feet GND coordination, transfer of control and transfer of communication shall take place as for IFR flights. Uncontrolled VFR flights shall be transferred to the appropriate sector if in radio contact. If online, EDMM_I_CTR (München Information), 120.650, shall be the primary sector for uncontrolled VFR flights.
Special Procedures
No special procedures in use.
Transfer of Control and Transfer of Communications
Transfer of Control
Transfer of Control shall take place at the boundary of AoR.
- If the downstream sector in EuroScope is set to .break, Silent Handoff is suspended and transfer of communication can only take place after the downstream sector has assumed the flight via the appropriate function of the radar client.
- If it becomes necessary to reduce or suspend transfers, a 5 minute prior notification is required.
- When transfers are suspended, Silent Handoff is suspended as well.
Silent transfer of control
The following values for silent transfer of control strictly apply for aircraft on same flight level. If possible, they should also be met between aircraft on different flight levels, but with same destination:
- If preceding aircraft is on same speed or faster: 10nm
- If succeeding aircraft is faster by 20kts/M0.05 or less: 20nm
- If succeeding aircraft is faster by 40kts/M0.10 or less: 30nm
Transfer of Communications
Transfer of Communications shall take place no later than Transfer of Control.
Hand-Off procedure
Unless otherwise agreed between stations online, the following hand-off procedure, called Silent transfer of control, shall apply:
- The upstream sector initiates a transfer via the appropriate function of the radar client.
- The upstream sector sends the aircraft to the frequency of the downstream sector by voice or text.
- Upon initial call, the downstream sector assumes the flight via the appropriate function of the radar client.
- The transfer of communications shall be initiated early enough so that the pilot will call the downstream controller before or shortly after reaching his sector.
SSR Code Assignment
Both ATS units shall transfer flights on verified discrete SSR codes or for Aircraft with Mode S capabilities and suitable destinations code 1000. Any change of SSR code by the accepting ATS unit may only take place after the transfer of control point.
