356
edits
Changes
→Handoff Process
4) Transfer of control
'''Offering'''
If a hand-off is not accepted then the offering controllers
shall keep the aircraft within their own Sector.
Note: Refer to VRC documentation on handoffs.
'''Accepting''' IVaC1 Have an option for auto-accept handoff.
Controllers should accept hand-offs promptly to avoid
additional co-ordination or vectoring.
'''Communication'''
Example: CPA520, contact Taipei control 129.9.
It is a good habit to transfer earlier, like 10 NM prior next sector for better coordination for the next sector controller to planCommunication transfer should normally be effectedbefore an aircraft enters the next Sector.
'''Control'''After the aircraft reaches an agreed point or level to transfer control, the responsibility for the next sector controller. The receiving controllers shall not alter theroute, speed, or level of the aircraft until after it hasentered the Sector.
Note. For IVAO purpose, Please ensure that prior to offering handoff, proper separation is established lateral separation of Enroute 10 NM, Approach airspace 5 NM and vertical separation 1000 ft in a general situation when rules and regulation is not stipulated in the [[Letter of Agreements |Letters of Agreement(Loa)]]
== CHAPTER 3 SEPARATION STANDARDS ==