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. "CTRHeavy VMCrain /reducing CTRvisibility IMC,to 2000m," "ThunderstormWind westgusts ofup to 35 knots from the field,west," "A320Moderate turbulence reported windat shear on final, lost 30 kt IAS.FL120."
E - Equipment Mention any operationally significant equipment issues (rarely relevant on VATSIM). "MultipleILS controllersfor Runway 22 out of service," "Transponder issues reported Audiowith several aircraft," "Coordination line to adjacent sector is down, using text chat for VATSIM connection issues.now."
S - Situation Describe the current operational environment, including staffing, airspace restrictions, or agreements. "Approach, Ground,Ground and FeederTower online, Approach offline—providing top-down service," "TaxiwayRunway Whiskey18 closed,closed for maintenance," "MinimumHolding inboundestablished spacingfor coordinatedarrivals withdue Approach.to congestion."
T - Traffic List active aircraft and pending actions. "RYR2NTBAW123 cleared for takeoff, waiting for departure separation," "AFR452 holding at 8FL150 NM,due speedto 160 kt until 4 NM, no landing clearance,traffic," "BER224DLH789 atapproaching positionthe 116,boundary, longhandoff pushback,required nosein south.2 minutes."

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 1635L in use for arrivals,departures, Runway 35R for arrivals at GMMN. GMME operating Runway 27 for departuresboth at YMML. Runway 34Larrivals and 34R at YSSY. Runway 35 at YSCB. Runway 25 at YMAY.departures."

"Airspace: We'reGMMM_CTR controllingis ELW,online, extending to GUN,cover GMMN_APP and providingGMME_APP. Providing top-down service at YMML, YSSY,GMMN and YSCB.GMME. AYNo Towertemporary isrestrictions online.or MUNclosures. isTraffic also online, extending to ARL and HUO. Airspace releases are allflow normal."

"Weather: MostlyWinds normal,010° butat Area12 QNHsknots, areoccasional high,gusts exceptup forto a18 smallknots partat eastGMMN. ofVisibility Area10km, 30.no significant weather affecting arrivals. Cloud cover SCT at 4000 feet, BKN at 10,000 feet. GMME reporting similar conditions with lighter winds at 5 knots from the west."

"Frequencies: Active on 123.75119.10 and 129.8.124.75 active. Handoffs to DAAA_CTR for eastbound traffic above FL250."

"Traffic: QFA428RAM213 is taxiing for 34Ldeparture atfrom YSSY,35L, WOL2 departureIFR to YMML.LFPG. No other calls on the ground at YSSY, YSCB, or YMML. VOZ831ATY502 is climbing,descending DCT ORSUP, coordination with MUNDAAA_CTR is complete.done. LPDAFR423 hasis 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 arrivinginbound from the north, haven’testimating checkedBARIS in four minutes. LBY112 is climbing out, handoff needed to the next sector. CN-RGB (a VFR flight) is holding at 2000 feet west of the field for conflicts yet.sequencing."

"Outstanding: Just frequency transfers and pendingthe handoffs.handoff for LBY112. No conflicts at the moment."

"Any questions?"
Back to top