Skip to main content

Tower

Tower positions

In Leipzig there are the following two Tower positions:

Position Station ID Login
 Frequency
Tower North
 PTN
 EDDP_N_TWR
 125.955
Tower South (primary)
 PTS
 EDDP_S_TWR
 121.105

If both Tower positions are staffed, the CTR is split in half in the middle, parallel to the runways. The north tower is responsible for the northern half of the CTR, the south tower for the southern half.

If only one tower is staffed, it also takes over the duties of the other tower and cross couples both frequencies.

Departing traffic

Leipzig Tower receives all departing aircraft from Leipzig Ground latest at the holding point.

As both north- and southbound SIDs are used from both runways, the procedures will cross in the departure sector. To ensure separation, departure releases are required if the two Tower positions are worked by different controllers:

  • S_TWR is required to obtain a departure release for ORTAG, and PENEM departures,
  • N_TWR is required to obtain a departure release for NEVKO, GOLAT, and DRN departures.

Traffic is handed off to München Radar on the charted frequencies:

126.065 126.175
PENEM
ORTAG		 NEVKO
GOLAT
DRN

If there is no parallel departure within 3 NM, the hand-off can be made when the aircraft is airborne.

Otherwise, the rules of Independent Parallel Departures apply:

Independent parallel departures

To use independent parallel departures, the following criteria must be met:

  • All aircraft are flying a published departure procedure
  • A crossing of the flown departure procedures will not happen (evaluation and departure release)
  • The tower controller(s) must ensure that all involved aircraft do not turn before the published turns in the departure procedure. If one aircraft deviates from the extended centerline before the published turn, it and all other aircraft, that are closer than 3 NM have to be turned away from the extended centerline immediately
  • Both aircraft are handed over to the departure frequency once one of them turns away from the extended centerline as published in the departure procedure.

It is possible that aircraft with a good climb performance reach theirn initial climb (FL70) before one of them turns away from the extended centerline. To prevent an aircraft from levelling out, you can request a higher level from the responsible approach controller.

Arriving traffic

Leipzig Tower receives all arriving aircraft one of the published approach procedures unless otherwise coordinated (e.g. visual approach). When traffic vacates the runway, they are handed off to Leipzig Ground

RECAT-EU

RECAT-EU can be applied in Leipzig. Separation of traffic pairs Lower Heavy preceding and Lower or Upper Heavy succeeding require only 3 NM wake-turbulence separation. See the relevant section in the Approach SOP for details.

Pilots can refuse this procedure at any time, but are expected to inform ATC early.

Modes of Operation

Dependent Parallel Approaches are in operation by default, with a minimum diagonal separation of 1,5 NM.

Preferred operating direction

The preferred operating direction is 26 up to a tailwind component of 5 knots. Winds at 3000–5000 ft are also be taken into consideration when deciding.

Control zone

The Leipzig control zone extends roughly between the cities of Halle and Leipzig. The vertical limit of the CTR is 2500ft MSL. Entry and exit into the control zone is via the mandatory reporting points:

  • North: November 1/2
  • South: Sierra 1/2

Traffic circuits are not authorised between the runways.

EDDP_CTR.pngControllzone Leipzig - © openflightmaps.org

Handovers between the towers should take place between the runways. A transfer point (e. g. circling) would be the tower.

HIRO

Due to the higher traffic volume at night, pilots are expected to vacate the runway between 2200lcl and 0600lcl via the following high-speed taxiways:

Aircraft type
 Runway 08R Runway 26L

B752 / A306 / B763

ALL MEDIUM (Jet and Prop)

 S6 (2550m/7382ft) S4 (1850m/6070ft)

Aircraft parked at Apron 4/5 cross taxiway T and shall hold short of V.

Low Visibility Procedures (LVP)

In Leipzig, the ILS is authorised for all runways up to CATIIIb. 

During low-visibility operations, single-use of runway operations shall be used (segregated parallel operations); individual approaches may deviate from this.

To broadcast the information via ATIS that LVP are active, the ATIS maker URL is supplemented by "&lvp", which appears in the ATIS:

LOW VISIBILITY PROCEDURES IN OPERATION CAT II AND III AVAILABLE

Back to top