Skip to main content

EDDF - High Intensity OPS

During high traffic situations with less staffing, the following procedures might be used.

When to use the procedures?

It depends on the traffic situation and can be used after coordination with all involved controllers. We can’t provide any specific rule when to use. If you notice that the airport itself or yourself/any other controller is at the limit already, the procedures may help. Especially if there is any systematic bottle neck (e.g. full holdingpoints, startup delay, huge pushback delay, holdings, stuck traffic at taxiway N8 or N11).

Keep in mind, a full holdingpoint is not always bad! It depends on the overall situation.

DCL (Hoppie) is not working / high frequency load

  1. Click on the aircraft
  2. Enter ".pdc" <space> <enter>
  3. Set CRF

Pilots requesting clearance should be informed with "expect clearance via text". When the frequency load is reducing, revert to voice clearances. Do not use the vATIS NOTAM.

This procedure should also be used for Top-Down Service with high frequency load.

During Top-Down Service (primary APP/CTR) it is also possible to send the text clearance pro active, also when the pilot has not requested the clearance. Activate the vATIS NOTAM "PDC_CLEARANCE" to inform pilots about the procedure.

Departure Routes

During high inbound traffic (e.g. when holdings are required) and low outbound traffic (less than 17 outbounds per 30 minutes) runway 18 can be used for all departures, no runway 25C! 

During high outbound traffic and less inbound traffic, outbounds via MARUN, TOBAK and OBOKA can also use only F/G departures during 25 ops to reduce dependencies between runway 18 and 25C (unless traffic permits the standard departure routes without delay). 

vSID command: .allnorth<space><enter>

Procedures during 07 operations will be unchanged.

Fallback Enroute Clearance via Private Message

If Delivery is not staffed and the frequency load on Apron, Tower or Arrival is too high for voice clearances, the enroute clearance via private message can be used on controller decision for all outbounds.

  • no DCL via Hoppie (amend your controller info and add the vATIS remark!)
  • use the alias “.pdc” for all stations, the alias command will open the chat with the pilot
  • NO clearance request by pilots required!
  • all outbounds should get the message as soon as they have filed the flightplan and the controller has time to send the message (don’t forget to set SID, IC and assign the SQ before the clearance via vSID).
  • Minor route errors can be accepted
  • pilots will call for startup/pushback
  • If the SQ is not set, the pilot still might not have seen the clearance. 

“Your ENROUTE clearance: CLRD to $arr via $sid, RWY $deprwy, CLIMB $temp, SQUAWK $squawk. NO clearance via voice to reduce freq load. NO readback required (do not reply)! Report ready on $com.”

Gate Assignment

The following stands should not be assigned at all for inbound traffic, as we expect most outbounds to connect in that area. If requested by the pilot, it should be coordinated with Center Apron before assigning it. It might be necessary that all such requests have to be denied! This will reduce the work and frequency load for Center Apron.

  • all A stands
  • V134 - V153
  • B10 - B28

Stands will be assigned such that inbounds have the shortest taxiroute and will not taxi through different apron areas. If appropriate stands haven’t been automatically assigned already, they shall be manually assigned by (North-)Tower/Ground for traffic on final according to the scheme below.

Landing RWY 25R  Landing RWY 25L
  • V166 - V270
  • all F stands
  • V94 - V130
  • B41 - B48
  • V164 - V270 (after coordination between West Apron and Tower)
  • all F stands
Landing RWY 07L Landing RWY 07R
  • V157 - V270
  • all F stands
  • V94 - V130
  • B41 - B48

During high outbound traffic (e.g. when startup delays are required), only T should be used for runway crossing after coordination between Tower and Apron.

After coordination bewteen Tower South and Apron South, the inbounds can stay on the tower frequency for parking on the southern apron. 

Delivery

Apron

  • Keep the traffic moving, avoid unnecessary holds and use early handoffs.
  • Outbound traffic, able for any intersection (25C/07C), should be sent to Tower short of the intersection! Do not just send everyone to full length.
  • Traffic can also be sent via L to holding point runway 18 if required (caution during 07 ops when outbounds 07C can block taxiway L and traffic towards runway 18 has to wait behind).
  • Outbound Traffic might only be able to push on the “Break Away Areas”.
  • Use orange/blue lines as well as L-North.
  • S-Intersection should be used for departures on runway 18 to reduce workload for Center and West Apron but only with less inbounds via T!

Tower

  • When the apron is crowded, avoid “swing to depart” if it is not really necessary (swingovers would increase the workload of Apron)
  • Do not use runway 07R/25L for departures. Outbounds from the south should cross runway 07R/25L and depart from the center runway.
  • Display assigned departure route for outbound traffic in the groundradar label for a better overview of SIDs.
  • Consider refusing/delaying any VFR traffic during high IFR rush in order to reduce workload. VFR outbounds should always use runway 18 for departure.
  • Do not use intersections if there is no benefit.
  • Use DSEQ Item in the Taxi-Out List for departure sequence.

Arrival

  • No target spacing for RWY 25L/07L (work with minimum possible spacing)
  • Use target spacing for runway 25R/07R all the time!
    • Heavies parking at the northern Apron should use this runways whenever practicable as they need increased WTC separation anyway.
    • Inbounds should primarily use runway 25L or 07L during low inbound demand due to Tower dependencies.
    • Use the alias commands as contact me (see alias file for all options) - couple north and south arrival!

Center

  • MIT for inbounds via ASPAT on coordination between EDGG and EDMM.
Back to top