Skip to main content

Handover-Takeover

A structured and informative handover ensures a smooth transition when transferring control of a sector. This is especially critical during high-traffic periods and events, where situational awareness must be maintained.

WEST Principle for Tower Handovers

Category Explanation Examples
W - Weather Any weather conditions that impact operations. "CTR VMC / CTR IMC," "Thunderstorm west of the field," "A320 reported wind shear on final, lost 30 kt IAS."
E - Equipment Mention any operationally significant equipment issues (rarely relevant on VATSIM). "Multiple controllers reported Audio for VATSIM connection issues."
S - Situation Describe the current operational environment, including staffing, airspace restrictions, or agreements. "Approach, Ground, and Feeder online," "Taxiway Whiskey closed," "Minimum inbound spacing coordinated with Approach."
T - Traffic List active aircraft and pending actions. "RYR2NT at 8 NM, speed 160 kt until 4 NM, no landing clearance," "BER224 at position 116, long pushback, nose south."

Structuring Approach and Center Handovers

When conducting handover between Approach and Center, follow a general → specific structure:

  1. Basic Information → Area of responsibility, active runways, NOTAMs.
  2. Sector Configuration & Agreements → Which adjacent sectors are online, special coordination agreements.
  3. Traffic Picture → Who is on frequency, their current status, any coordination already completed.
  4. Additional Details → Any reported issues, equipment failures, special operations.

This structured approach helps the incoming controller gradually build an understanding of the traffic picture before assuming control.

Handover Completion Process

  • The handover controller remains responsible for the frequency until the relieving controller is fully ready to assume control.
  • In high-traffic situations, handovers may take several minutes—the relieving controller should only assume the frequency when confident in the airspace situation.

RAWFTO Handover Format

Runways
  • Which runways are in use?
  • Any recent or planned runway changes?
Airspace
  • Any abnormal conditions in your airspace?
  • Which adjacent sectors are online?
  • Are any airspace 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 each jurisdiction and aircraft on screen.
  • Highlight any pending coordination or outstanding instructions.
Outstanding Instructions / Other Information
  • Any ongoing coordination that needs completion?
  • Any frequency transfers still pending?
  • Any additional notes or situational awareness items?
Example Handover Exchange
"Runway 16 for arrivals, 27 for departures at YMML. Runway 34L and 34R at YSSY. Runway 35 at YSCB. Runway 25 at YMAY.

"Airspace: We're controlling ELW, extending to GUN, and providing top-down service at YMML, YSSY, and YSCB. AY Tower is online. MUN is also online, extending to ARL and HUO. Airspace releases are all normal."

"Weather: Mostly normal, but Area QNHs are high, except for a small part east of Area 30."

"Frequencies: Active on 123.75 and 129.8."

"Traffic: QFA428 is taxiing for 34L at YSSY, WOL2 departure to YMML. No other calls on the ground at YSSY, YSCB, or YMML. VOZ831 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 needed. JST528 and BNZ192 are arriving from the north, haven’t checked for conflicts yet."

"Outstanding: Just frequency transfers and pending handoffs."

"Any questions?"
Back to top