Approach
Sectorization
München Radar sectors Thüringen Low Nord (TRN) and Thüringen Low Süd (TRS) are responsible for all arrivals and departures from/to Leipzig/Halle (EDDP), and TRS also services Erfurt-Weimar (EDDE), and the uncontrolled IFR airfield Leipzig Altenburg (EDAC).
TRS also covers Sachsen Low (SAS) unless EDDC_SAS_APP or EDMM_MEI_CTR are open. All controllers are expected to cross-couple the frequencies of the sectors they cover.
Leipzig Arrival South (EDDP_SD_APP) can be staffed as feeder position in EDDP. EDDP_ND_APP is not to be opened unless on a rostered event. EDDP_SD_APP cross-couples the EDDP_ND_APP frequency.
Approach sectors underlying EBG Ost
Airspace
Leipzig/Halle (EDDP)
Around Leipzig/Halle, Airspace D (non-CTR) is established up to FL75. Between FL75 and FL100, in the Airspace E band, an additional TMZ is established. VFR traffic is expected to squawk 4404 and monitor 126.175 (EDDP_TRS_APP).
Both Airspace D and the TMZ Leipzig consist of always-active parts, and HX parts that are active depending on the operating direction (26 – east active, 08 – west active).
IFR traffic should be kept within protected airspace during daytime. Speed restrictions of Airspace D (≤250 kt) may not be lifted.
Airspace around EDDP. Source: Openflightmaps
Erfurt-Weimar (EDDE)
Erfurt-Weimar is surrounded by Airspace E, and TMZ(HX) Erfurt, activated for IFR traffic on demand. The TMZ code is 4410, and VFR traffic is expected to monitor 126.175 (EDDP_TRS_APP).
Airspace around EDDE. Source: Openflightmaps
Departing traffic
Leipzig/Halle
Traffic is handed off to München Radar in their first procedure turn (SID or OID), when proper separation is established.
The speed limit for Airspace D (250 kts) shall not be cancelled.
Departing aircraft may always be cleared to the last waypoint of the SID. Particular attention should be paid to potential conflicts in SAS airspace.
Handover Agreements
Refer to the EDMM LOP and EDMM-EDWW LoA, both available in ATCISS, for handover agreements.
Arriving traffic
RNAV-capable traffic arrives via the arrival fixes KOJEC, LUXBO, GOXLI, and YAWOY. Non-RNAV traffic will likely file to a nearby VOR (GOT, LEG). As non-RNAV arrivals are no longer available, the respective traffic should be provided with radar vectors to final.
If Bremen Radar is not staffed, Thüringen shall monitor the airspace for KOJEC arrivals and ensure they do not enter the overlying EDMM ACC sectors.
The speed limit for Airspace D (250 kts) shall not be cancelled; approaching aircraft shall always be guided in protected airspace (TMZ or Airspace C/D) during daytime.
Noise Abatement (2200–0600 lcl): Traffic shall be kept clear of the cities Leipzig and Halle whenever possible. The GOXLI and YAWOY procedures are designed to avoid overflights over the city of Leipzig, exercise care when instructing a direct.
Approach paths
Incoming traffic via KOJEC and GOXLI is to be issued with STAR clearance by Thüringen, traffic via YAWOY and LUXBO receive STAR clearance from SAS: Aircraft should expect FL110 at KOJEC, LUXBO, GOXLI and YAWOY.
Arriving and departing traffic will cross in most cases, requiring attention to ensure separation. As an example, during 26 operations, SIDs and STARs cross as follows:
The following altitudes are recommended on the STARs:
| Position | Altitude |
| STAR Fix | FL110 |
| Upwind | FL100 |
| Downwind before mid-field | FL080 |
| Downwind after mid-field | 5000ft |
Approach types
At Leipzig/Halle Airport, there are three published approach types for all runways. Leipzig has ILS, LOC, and RNP approaches. If a visual approach needs to be cleared, the approach controller is obliged to inform the Tower controller.
At night, the final approach must be at least at 11 NM for noise protection reasons (26: DP447/DP437, 08: DP442/DP432).
Operating mode
The default operating mode is Dependent Parallel Approaches on both runways. At all times, a diagonal separation of 1.5 NM is required.
The full requirements for DPA operations can be found here.
Independent parallel approaches are permitted in Leipzig. However, the primary operating mode is staggered. Every controller must familiarise themselves with the conditions of the respective operating mode in advance. Further information is available at the Tower-SOP. It is important to note that despite all conditions for IPA or staggered approaches, the MVA must be observed at all times!
Runway assignments
- Aircraft via KOJEC, LUXBO can expect the northern runway
- Aircraft via GOXLI, YAWOY can expect the southern runway
- Aircraft parked on aprons 1 and 3 can expect the northern runway
- If traffic conditions permit, cargo aircraft land on the southern runway
- Aircraft types A346/B77W/B744/B748/A388 should be assigned to the southern runway
Depending on the traffic situation, deviations from these specifications are possible. However, the Arrival controller determines the runway to be used by aircraft in all cases. During high-traffic operations, it is recommended to send more aircraft to the northern runway, as the southern runway is heavily congested with departures due to cargo traffic.
Handover to Leipzig Arrival
The handover to Leipzig Arrival normally takes place at a speed of 220 kts. If traffic conditions permit or require, aircraft may also be handed over at a higher or lower speed.
Traffic on the downwind leg is normally handed over as shown below:
| Downwind | RWY 08 | RWY 26 |
| North | 5000ft | 4000ft |
| South | 4000ft | 5000ft |
Individual direct approaches can also be coordinated with Leipzig Arrival.
Two Feeder Operations
Before opening the second arrival position, TRS, TRN and DPSD need to be staffed. The following procedures are necessary for two arrivals:
Independent Parallel Approachesshallbe usedIndependent Parallel Approaches need to fly anILSapproachoranRNPApproachwith vertical guidance(LNAV-only is not authorized, this is described on the approach charts as well)Intercept headings need to be ≤ 30 degrees to the final approach track.1 NM straight and level on the intercept heading,2 NM straight and level on the final approach courseLeipzig Arrival North (ND_APP) receives aircraft for the northern runwayLeipzig Arrival South (SD_APP) receives aircraft for the southern runwayTRS/TRN assign the runway, notify the pilot, and transfer aircraft to the appropriate Arrival station.
Application of RECAT-EU procedures
RECAT-EU separation can be applied at EDDP.
The use of RECAT-EU is only allowed for the category "Lower Heavy/Upper Heavy" and "Lower Heavy/Lower Heavy", specifically:
Upper Heavy |
Lower Heavy |
| A330 | A300 |
| A340 | A310 |
| A350 | B703 |
| B747 | B757 |
| B777 | B767 |
| B787 | B783 |
| IL96 | C135 |
| DC10 | |
| DC85 | |
| IL76 | |
| MD11 | |
| TU22 | |
| TU95 |
According to the procedure, 2 of the above aircraft types only have to be separated 3NM (wake turbulence) unless another method of separation (e.g. radar separation) requires more separation.
The pilot can refuse this procedure at any time, but shall inform you early.
Caution between Upper-Heavy and Lower-Heavy! The "Lower Heavy" must be preceding!
Mediums are excluded from this procedure!
Erfurt-Weimar
Aircraft are guided either via headings or the STAR. Clearance for the STAR is always given from Thüringen Süd Low. Here, particular attention must be paid to the convergence of traffic on the downwind and base legs. In addition, attention must be paid to VFR traffic, as the Erfurt TMZ area is very small and not every pilot is aware of the activity in this airspace. Furthermore, the MVA in Erfurt plays a not insignificant role. As soon as low visibility operations have to be used, approach direction 09 is no longer usable. Only the ILS on 27 up to CAT IIIb is permitted here.
Holzdorf
The Holzdorf military airfield has an area of responsibility in which Holzdorf Radar can control aircraft when activated. Berlin Arrival South is obliged to inform München Radar about the activation/deactivation of Holzdorf.
All aircraft to/from Holzdorf must be individually coordinated between Bremen Radar/München Radar and Holzdorf Radar.
Release Areas
TORGAU Area
- GND - FL105 (Wenn Holzdorf AoR aktiv: 5500 MSL - FL105)
- Delegation von DBAS an TRN/S
- Only EDDP Inbound RWY 26
Activation only possible upon request from TRN/S by DBAS
MULDE A Area
- FL135 - FL165/FL195
- Delegation von TRN/S an ACC Sector FLG
- For EDDB TMA Inbounds (earlier descent possible)
Activation only possible upon request from ACC Sector FLG via TRN/S
MULDE B Area
- FL165 - FL195
- Delegation von TRN/S an ACC Sector FLG
- For EDDB TMA Inbounds (earlier descent possible)
Activation only possible upon request from ACC Sector FLG via TRN/S



