Skip to main content

Handover-Takeover

A properstructured and informative handover isensures ana essentialsmooth parttransition when transferring control 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.sector. This is particularlyespecially critical during high-traffic periods,periods asand handoverevents, errorswhere insituational suchawareness situations canmust be more consequential.maintained.

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

Handovers

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

IMC,"
Category Explanation Examples
W - Weather WeatherAny significantlyweather impactsconditions operationsthat andimpact must always be communicated.operations. - "CTR VMC / CTR IMC"

  • "Runway direction 25"

  • "West wind, medium strength"

  • "Thunderstorm west of the field"

    field,"

  • "A320 reported wind shear,shear 2 NMon final, lost 30 kt IAS,IAS." 200 ft altitude loss" | | E - Equipment |Mention Anyany operationally significant equipment issues affecting operations should be noted. On VATSIM, this is (rarely relevant.relevant |on -VATSIM). "Multiple controllers reported Audio for VATSIM connection issuesissues." reported by multiple controllers" | | S - Situation | Describe the current operational environment, including onlinestaffing, stations,airspace closures,restrictions, special events, andor agreements. |"Approach, - "Ground, Approach, and Feeder online"

    online,"

  • "Taxiway Whiskey closed"

    closed,"

  • "Shuttle event between Frankfurt and London"

  • "Minimum inbound spacing coordinated with Approach"

    Approach."

  • "Departure frequency for all southern departures is 119.2" | | T - Traffic |List Outline relevantactive aircraft withinand orpending aboutactions. 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"

  • 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,BER224 at holdingposition point116, RWYlong 25,pushback, awaitingnose takeoffsouth."
clearance.
-
PBW11,
helicopter
VFR,

Structuring 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. TheHandovers

When conducting 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, itfollow is best to move froma general to→ specific: structure:

  1. Basic informationInformation –→ Own areaArea of responsibilityresponsibility, andactive runwayrunways, direction(s).

    NOTAMs.

  2. Sector configurationConfiguration & agreementsAgreements –→ AdjacentWhich adjacent sectors andare online, special coordination agreements.

  3. Traffic detailsPicture –→ AircraftWho is on frequencyfrequency, andtheir current status, any coordination status.

    already completed.

  4. Additional informationDetails –→ Any otherreported relevantissues, notes.

    equipment failures, special operations.

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

Handover Completion Process

  • The handover controller remains responsible for the frequency duringuntil the entirerelieving handover.controller is fully ready to assume control.
  • In high-traffic situations, ahandovers handover canmay take several minutes. Theminutes—the relieving controller should takeonly overassume with a clear "mythe frequency" only when theyconfident fully understandin the situation.

    airspace

    situation.

RAWFTO Handover Breakdown

Format
Basic Information & WeatherRunways
  • Which

    Ownrunways areaare ofin responsibility,use?

    • active
  • Any runways,recent approachor configuration,planned specialrunway meteorological conditions, and important NOTAMs.

    changes?

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

Airspace
  • Any

    abnormal conditions in your airspace?

  • Which adjacent sectors are online?
    • and
  • Are any specialairspace agreements.releases active?
  • Are you extending control to adjacent sectors?
  • Are you providing top-down service to any aerodromes?
Weather
  • Any significant or abnormal weather affecting operations?
  • Is the Area QNH restricting cruise at FL110 (below 1013 hPa)?
Frequencies
  • What active frequencies are in use?
  • Any planned changes or handoffs?
Traffic
  • Go through themeach 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,jurisdiction 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?

    screen    .
  • Highlight

    Whoany elsepending iscoordination calling,or andoutstanding what has already been coordinated?

    instructions.

Example

Outstanding (Approach)

Instructions
/

"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."

AdditionalOther Information

  • Any remainingongoing relevantcoordination details.

    that needs completion?
  • Any frequency transfers still pending?
  • Any additional notes or situational awareness items?

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 ExampleExchange
You"Runway take16 overfor Frankfurtarrivals, Pickup-North,27 Pickup-Southfor departures at YMML. Runway 34L and both34R feedersat areYSSY. online.Runway We35 haveat runwaysYSCB. Runway 25 andat 18,YMAY.

independent"Airspace: parallelWe're approaches.controlling YELW, approachesextending onto 25R, 2.5 NM minimum spacing.

Winds are strong westerly, fast downwind, turbulence reported.

GIN, DKB,GUN, and RUDproviding aretop-down online.service Weat areYMML, allowed direct NOMBO for CINDY departuresYSSY, and directYSCB. ARPEGAY 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. SLNTower is online. StuttgartMUN is onlyalso staffedonline, withextending Tower.to AllARL runwaysand HUO. Airspace releases are westall directionnormal."

"Weather: Mostly normal, but Area QNHs are high, except Badenfor (03).a GIN,small FUL,part east of Area 30."

"Frequencies: Active on 123.75 and Zurich129.8."

are"Traffic: online, no special agreements.

Only SWR2FRQFA428 is descendingtaxiing FL220for 34L at YSSY, WOL2 departure to YMML. No other calls on the frequency.ground Onceat clearYSSY, ofYSCB, BCS34T,or heYMML. canVOZ831 is climbing, coordination with MUN is complete. LPD has clearance to leave controlled airspace descending. QJE1721 and UAL19 are estimating LIZZI at the same time, so sequencing will be transferred.needed. IJST528 haveand enteredBNZ192 directare SPESAarriving from the north, haven’t checked for DLH123,conflicts butyet."

he"Outstanding: isJust stillfrequency intransfers Munichand airspace.pending handoffs."

"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
Runways 25, you are Feeder for both runways. Dependent parallel approaches, Y approaches on 25R.

General spacing: 5 NM due to departures on both runways.

Strong winds, aircraft are reducing speed quickly.

ITY414 has 180 kt until 6NM, already with Tower.

SWR2FR behind it needs to slow down soon.

DLH404 is on base turn for 25L.

AUA1LN will call next.

Any questions?
Back to top