5-4-6. RECEIVING CONTROLLER HANDOFF

  • Views Views: 9
  • Last updated Last updated:
  • 5-4-6. RECEIVING CONTROLLER HANDOFF

    The receiving controller must:

    1. Ensure that the target position corresponds with the position given by the transferring controller or that there is an appropriate association between an automated data block and the target being transferred before accepting a handoff.
    2. Issue restrictions that are needed for the aircraft to enter your sector safely before accepting the handoff.
    3. Comply with restrictions issued by the transferring controller unless otherwise coordinated.
    4. After accepting a handoff from another controller, confirm the identity of primary target by advising the aircraft of its position, and of a beacon target by observing a code change, an “ident” reply, or a “standby” squawk unless one of these was used during handoff. These provisions do not apply at those towers and GCAs which have been delegated the responsibility for providing radar separation within designated areas by the parent approach control facility and the aircraft identification is assured by sequencing or positioning prior to the handoff.
    5. When using appropriate equipment, consider a discrete beacon target’s identity to be confirmed when:
      1. The data block associated with the target being handed off indicates the computer assigned discrete beacon code is being received, or
      2. You observe the deletion of a discrete code that was displayed in the data block, or

        NOTE: When the aircraft generated discrete beacon code does not match the computer assigned beacon code, the code generated will be displayed in the data block. When the aircraft changes to the assigned discrete code, the code disappears from the data block. In this instance, the observance of code removal from the data block satisfies confirmation requirements.

      3. You observe the numeric display of a discrete code that an aircraft has been instructed to squawk or reports squawking.
    6. Take the identified action prior to accepting control of a track when the following indicators are displayed in the data block:
      1. “AMB” and “AM”: advise the other facility that a disparity exists between the position declared by their computer and that declared by your CARTS/PIDP/STARS system.
      2. “NAT”, “NT,” or “TU”: advise the other facility if a disparity exists between the position declared by their computer and the actual target position.
      3. “DATA”, “CST”, “NONE”, “NX”, “OLD”, or “OL”: initiate verbal coordination.
    7. ERAM: Notify the OS when a MISM is displayed in the data block.
    8. Advise the transferring controller, prior to accepting the transfer of radar identification, that you will delay the climb or the descent of an aircraft through the vertical limits of the transferring controller’s area of jurisdiction, unless otherwise specified in a LOA or a facility directive.
    9. If you decide, after accepting the transfer of radar identification, to delay the aircraft’s climb or descent through the vertical limits of the transferring controller’s area of jurisdiction, advise the transferring controller of that decision as soon as possible.
Top