Skip to main content

Handover-Takeover

A proper handover is an essential part of a controller’s workflow and has become increasingly relevant on VATSIM, especially during long events such as Munich 11 to 11, Berlin Overload, or Frankfurt RFO.

This guide outlines the key steps for conducting a structured and efficient handover in the tower environment.

General Considerations

When a handover is imminent (e.g., when the incoming controller joins TeamSpeak), it is advisable to simplify traffic as much as possible. Specifically:

  • Handle standard traffic only.

  • Avoid complex situations or unresolved conflicts.

  • Complete coordination with neighboring stations to ensure a clear traffic picture at handover.

  • Transfer unnecessary aircraft to the next controller beforehand.

To ensure a quick and effective handover, the outgoing controller should plan in advance what needs to be communicated. This is particularly critical during high-traffic periods, as handover errors in such situations can be more consequential.

Both controllers should confirm readiness before starting the handover. The handover completion should be explicitly stated to avoid confusion about who is responsible for the position. The outgoing controller should remain available for a few minutes after handover to address any immediate issues.

WEST Principle for Tower Handover

A structured handover in the tower environment follows the WEST principle:

CategoryExplanationExamples
W - WeatherWeather significantly impacts operations and must always be communicated.- "CTR VMC / CTR IMC"

  • "Runway direction 25"

  • "West wind, medium strength"

  • "Thunderstorm west of the field"

  • "A320 reported wind shear, 2 NM final, lost 30 kt IAS, 200 ft altitude loss" | | E - Equipment | Any equipment issues affecting operations should be noted. On VATSIM, this is rarely relevant. | - "Audio for VATSIM connection issues reported by multiple controllers" | | S - Situation | Describe the current operational environment, including online stations, closures, special events, and agreements. | - "Ground, Approach, and Feeder online"

  • "Taxiway Whiskey closed"

  • "Shuttle event between Frankfurt and London"

  • "Minimum inbound spacing coordinated with Approach"

  • "Departure frequency for all southern departures is 119.2" | | T - Traffic | Outline relevant aircraft within or about to enter the airspace. | - "DISTM filed a Y flight plan, clearance limit CHA, not yet called in"

  • "DLH4FM has IFR clearance but no startup"

  • "BER224 at position 116, long pushback, blue line, nose south"

  • "CXI2247 rolling for takeoff"

  • "RYR2NT at 8 NM, speed 160 kt until 4 NM, no landing clearance"

  • "DEMIL, VFR inbound via Echo, cleared into CTR and circuit" |

The WEST principle serves as a guideline for a clean handover. Any additional important information that does not fit into these categories should still be communicated.

However, irrelevant information should be omitted. For example, during clear weather, there is no need to mention that "there is no thunderstorm."

Example Handover


Control zone VMC,
Runway direction 25,
Clear west wind, medium speed.

We have online: Ground, Approach, and Feeder.
Taxiway Whiskey closed.
No gaps requested by Feeder.

Traffic overview:
- SAS842, just departed from RWY 25.
- DLA9H, at holding point RWY 25, awaiting takeoff clearance.
- PBW11, helicopter VFR, at southern helipad, requesting departure via Echo.
- BAW917S, at 6NM, on frequency, no landing clearance.

Any questions?

A well-structured handover ensures smooth transitions between controllers, reducing errors and maintaining operational efficiency.

Handover Approach / Feeder / Center

While the "Handover Tower" article introduced the WEST principle, this guide presents a more practical approach for handovers between Approach and Center. The WEST principle can still be used in parallel, but it does not comprehensively cover all relevant aspects of such handovers.

For a structured handover between Approach and Center, it is best to move from general to specific:

  1. Basic information – Own area of responsibility and runway direction(s).

  2. Sector configuration & agreements – Adjacent sectors and agreements.

  3. Traffic details – Aircraft on frequency and coordination status.

  4. Additional information – Any other relevant notes.

This approach helps the incoming controller gradually build an understanding of the traffic picture. There is no strict phraseology for handovers—the key is mutual understanding. If anything is unclear, ask.

The handover controller remains responsible for the frequency during the entire handover. In high-traffic situations, a handover can take several minutes. The relieving controller should take over with a clear "my frequency" only when they fully understand the situation.

Handover Breakdown

Basic Information & Weather

  • Own area of responsibility, active runways, approach configuration, special meteorological conditions, and important NOTAMs.

Example (Approach)

"You are Frankfurt Pickup-North; Feeder and Pickup-South are online. 25 and 18 active, 25R has 2.5 NM minimum spacing for Y approaches, 25L has 6 NM spacing due to departures. Strong west wind—fast downwind, turbulence reported."

Example (Center)

"You are the DKB sector without upper. Frankfurt 25, Stuttgart 25, Mannheim 27, Baden-Baden 21. All runways west except Baden (03)."

Sector Configuration & Agreements

  • Which adjacent sectors are online and any special agreements. Go through them in a logical order to avoid forgetting anything.

Example (Approach)

"DKB is online, we have direct NOMBO for CINDY departures, direct ARPEG for Amsterdam. GIN, DKB, and RUD are online."

Example (Center)

"ZUG is online and covering ALB. Frankfurt inbounds come in descending; we may send Munich inbounds direct to ROKIL. HOF and GIN are online. Zurich needs 20 NM spacing for LSZH inbounds."

Traffic

  • Who is on frequency?

  • What is the plan for the aircraft on frequency?

  • Who else is calling, and what has already been coordinated?

Example (Approach)

"ITY414 handed off. DLH123 is first in sequence, at 5000 ft. DLH45H descending to FL70, needs speed reduction soon. DLH401 is inbound for 25S, DLH12J just checked in at RAMOB."

Example (Center)

"SWR2FR descending FL220. Once clear of BCS34T, he can be transferred. DLH123 still at Munich but has a direct SPESA entered."

Additional Information

  • Any remaining relevant details.

Example (Approach)

"We had multiple voice server issues earlier."

Example (Center)

"Parachute dropper at NETEX has called in several times; expect them again soon."

Example Handovers

Approach Handover Example


You take over Frankfurt Pickup-North, Pickup-South and both feeders are online.

We have runways 25 and 18, independent parallel approaches. Y approaches on 25R, 2.5 NM minimum spacing.

Winds are strong westerly, fast downwind, turbulence reported.

GIN, DKB, and RUD are online. We are allowed direct NOMBO for CINDY departures and direct ARPEG for Amsterdam departures.

ITY414 already handed off. DLH123 is first in sequence at 5000 ft, followed by DLH45H descending to FL70, needs speed reduction soon. DLH401 inbound for 25S, DLH12J just called at RAMOB.

Any questions?

Center Handover Example


You take over DKB. SLN is online. Stuttgart is only staffed with Tower.

All runways are west direction except Baden (03).

GIN, FUL, and Zurich are online, no special agreements.

Only SWR2FR is descending FL220 on the frequency. Once clear of BCS34T, he can be transferred.

I have entered direct SPESA for DLH123, but he is still in Munich airspace.

Any questions?

Feeder Handovers

For Feeder handovers, key weather conditions are emphasized more, as wind directly impacts spacing and sequencing. However, sector configuration details are less relevant, since a Feeder sector is never active without a Pickup sector.

Example Feeder Handover

 
Back to top