5-4-1 Section 4. Transfer of Radar Identification

5-4-1 Application

 To provide continuous radar service to an aircraft and facilitate a safe, orderly, and expeditious flow of traffic, it is often necessary to transfer radar identification of an aircraft from one controller to another. This section describes the terms, methods, and responsibilities associated with this task. Interfacility and intrafacility transfers of radar identification shall be accomplished in all areas of radar surveillance except where it is not operationally feasible. Where such constraints exist, they shall be:

 a. Covered in letters of agreement which clearly state that control will not be based upon a radar handoff, or
 b. Coordinated by the transferring and receiving controllers for a specified period of time.

REFERENCE -
FAAO 7110.65, Coordination with Receiving Facility, paragraph 4-3-7.

5-4-2 Terms

 a. Handoff - An action taken to transfer the radar identification of an aircraft from one controller to another controller if the aircraft will enter the receiving controller's airspace and radio communications with the aircraft will be transferred.
 b. Radar Contact - The term used to inform the controller initiating a handoff that the aircraft is identified and approval is granted for the aircraft to enter the receiving controller's airspace.
 c. Point Out - A physical or automated action taken by a controller to transfer the radar identification of an aircraft to another controller if the aircraft will or may enter the airspace or protected airspace of another controller and radio communications will not be transferred.
 d. Point Out Approved - The term used to inform the controller initiating a point out that the aircraft is identified and that approval is granted for the aircraft to enter the receiving controller's airspace, as coordinated, without a communications transfer or the appropriate automated system response.
 e. Traffic - A term used to transfer radar identification of an aircraft to another controller for the purpose of coordinating separation action. Traffic is normally issued (a) in response to a handoff or point out, (b) in anticipation of a handoff or point out, or (c) in conjunction with a request for control of an aircraft.
 f. Traffic Observed - The term used to inform the controller issuing the traffic restrictions that the traffic is identified and that the restrictions issued are understood and will be complied with.

5-4-3 Methods

 a. Transfer the radar identification of an aircraft by at least one of the following methods:
  1. Physically point to the target on the receiving controller's display.
  2. Use landline voice communications.
  3. Use automation capabilities.
  4. TERMINAL: Use the "Modify" or "Quick Look" functions for data transfer between the TRACON and tower cab only if specific procedures are established in a facility directive. The local controller has the responsibility to determine whether or not conditions are adequate for the use of ARTS data on the BRITE/DBRITE.

{New-98-3 Revised February 26, 1998}

 REFERENCE -
  FAAO 7210.3, Use of ARTS Modify and Quick Look Functions, paragraph 11-2-4.

  5. EN ROUTE: EDARC/HOST or DARC/HOST have interfacility handoff capabilities that can be manually initiated and accepted through the Quick Action Keys (QAK), or used in automatic handoff mode as in HOST Stage A. DARC or EDARC do not have the capabilities for interfacility handoffs. Therefore, handoffs between facilities must be made via landline voice communications when operating in DARC or EDARC.
 b. When making a handoff, point-out, or issuing traffic restrictions, relay information to the receiving controller in the following order:
  1. The position of the target relative to a fix, map symbol, or radar target known and displayed by both the receiving and transferring controller. Mileage from the reference point may be omitted when relaying the position of a target if a full data block associated with the target has been forced on the receiving controller's radar display.

EXAMPLE -
"Point out, southwest of Richmond VOR..."
  2. The aircraft identification, as follows:
   (a) The aircraft call sign, or
   (b) The discrete beacon code of the aircraft during interfacility point-outs only, if both the receiving and the transferring controllers agree.

NOTE -
Acceptance of a point out using the discrete beacon code as the aircraft's identification constitutes agreement.

  3. The assigned altitude, appropriate restrictions, and information that the aircraft is climbing or descending, if applicable, except when inter/intrafacility directives ensure that the altitude information will be known by the receiving controller.

NOTE -
1 - When physically pointing to the target, you do not have to state the aircraft position.
2 - Those en route facilities using HOST software that provides capability for passing interim altitude shall include the specific operations and procedures for use of this procedure in a LOA between the appropriate facilities.

PHRASEOLOGY -
 HANDOFF/POINT-OUT/TRAFFIC (aircraft position) (aircraft ID)
or
 (discrete beacon code point-out only) (altitude, restrictions, and other appropriate information, if applicable).
 c. When receiving a handoff, point-out, or traffic restrictions, respond to the transferring controller as follows:

PHRASEOLOGY -
 (Aircraft ID) (restrictions, if applicable) RADAR CONTACT,
or
 (Aircraft ID or discrete beacon code) (restrictions, if applicable) POINT-OUT APPROVED,
or
 TRAFFIC OBSERVED,
or
 UNABLE (appropriate information, as required).
 d. If any doubt as to target identification exists after attempting confirmation in accordance with this section, apply the provisions of paragraph 5-3-5, Questionable Identification.

REFERENCE -
FAAO 7110.65, Validation of Mode C Readout, paragraph 5-2-18.

5-4-4 Traffic

 a. When using the term "traffic" for coordinating separation, the controller issuing traffic shall issue appropriate restrictions.
 b. The controller accepting the restrictions shall be responsible to ensure that approved separation is maintained between the involved aircraft.

5-4-5 Transferring Controller Handoff

 The transferring controller shall:
  a. Complete a radar handoff prior to an aircraft's entering the airspace delegated to the receiving controller.

REFERENCE -
FAAO 7110.65, Coordinate Use of Airspace, paragraph 2-1-14.
FAAO 7110.65, Control Transfer, paragraph 2-1-15.
FAAO 7110.65, Receiving Controller Handoff, paragraph 5-4-6.

  b. Verbally obtain the receiving controller's approval prior to making any changes to an aircraft's flight path, altitude, or data block information while the handoff is being initiated or after acceptance, unless otherwise specified by a LOA or a facility directive.

NOTE -
Those en route facilities using HOST software that provides capability for passing interim altitude shall include the specific operations and procedures for use of this procedure in a LOA between the appropriate facilities.

  c. Ensure that, prior to transferring communications:
   1. Potential violations of adjacent airspace and potential conflicts between aircraft in their own area of jurisdiction are resolved.
   2. Necessary coordination has been accomplished with all controllers through whose area of jurisdiction the aircraft will pass prior to entering the receiving controller's area of jurisdiction, except when such coordination is the receiving controller's responsibility as stated in paragraph 5-4-6, Receiving Controller Handoff, and unless otherwise specified by a LOA or a facility directive.
   3. Restrictions issued to ensure separation are passed to the receiving controller.
  d. After transferring communications, continue to comply with the requirements of subparagraphs c1 and c2.
  e. Comply with restrictions issued by the receiving controller unless otherwise coordinated.
  f. Comply with the provisions of paragraph 2-1-17 a and to the extent possible, transfer communications when the transfer of radar identification has been accepted.

NOTE -
Before ARTS "Modify/Quick Look" function is used to transfer radar identification, a facility directive which specifies communication transfer points is required.

  g. Advise the receiving controller of pertinent information not contained in the data block or flight progress strip unless covered in a letter of agreement or facility directive. Pertinent information includes:

   1. Assigned heading.
   2. Air speed restrictions.
   3. Altitude information issued.
   4. Observed track or deviation from the last route clearance.
   5. The beacon code if different from that normally used or previously coordinated.
   6. Any other pertinent information.
  h. Ensure that the data block is associated with the appropriate target.
  i. Initiate verbal coordination to verify the position of primary or nondiscrete targets when using the automated handoff functions except for intrafacility handoffs using single sensor systems or multisensor systems operating in a mosaic RDP mode.
  j. Initiate verbal coordination before transferring control of a track when "CST," "FAIL," "NONE," "NB," "NX," "IF," or "NT" is displayed in the data block.
  k. Advise the receiving controller that radar monitoring is required when the aircraft is on a direct route initiated by ATC that exceeds usable NAVAID distances.

  l. Issue restrictions to the receiving controller which are necessary to maintain separation from other aircraft within your area of jurisdiction before releasing control of the aircraft.
  m. Consider the target being transferred as identified on the receiving controller's display when the receiving controller acknowledges receipt verbally or has accepted an automated handoff.
  n. Accomplish the necessary coordination with any intervening controllers whose area of jurisdiction is affected by the receiving controller's delay in the climb or the descent of an aircraft through the vertical limits of your area of jurisdiction when the receiving controller advises you of that delay before accepting the transfer of radar identification unless otherwise specified by a LOA or a facility directive.

5-4-6 Receiving Controller Handoff

 The receiving controller shall:
 a. 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 an handoff.

REFERENCE -
FAAO 7110.65, Coordinate Use of Airspace, paragraph 2-1-14.
FAAO 7110.65, Control Transfer, paragraph 2-1-15.
FAAO 7110.65, Transferring Controller Handoff, paragraph 5-4-5.

 b. Issue restrictions that are needed for the aircraft to enter your sector safely before accepting the handoff.
 c. Comply with restrictions issued by the initiating controller unless otherwise coordinated.
 d. Before you issue control instructions directly to an aircraft that is within another controller's area of jurisdiction that will change that aircraft's heading, route, speed, altitude, or beacon code, ensure that coordination has been accomplished with each of the controllers listed below whose area of jurisdiction is affected by those instructions unless otherwise specified by a letter of agreement or a facility directive:

NOTE -
Those en route facilities using HOST software that provides capability for passing interim altitude shall include the specific operations and procedures for use of this procedure in a letter of agreement between the appropriate facilities.

  1. The controller within whose area of jurisdiction the control instructions will be issued.
  2. Any intervening controller(s) through whose area of jurisdiction the aircraft will pass.
 e. 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.

REFERENCE -
FAAO 7110.65, Approach Separation Responsibility, paragraph 5-9-5.

 f. 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.
 g. Initiate verbal coordination prior to accepting control of a track when "CST," "NAT," "NT," "NONE," "NB," "NX," "OLD," "OL," "AMB," "AM," or "TU" is displayed in the data block.
  1. When an automated interfacility handoff action is initiated and "AMB" or "AM" is displayed in the full data block, advise the other facility that a disparity exists between the position declared by their computer and that declared by your ARTS/PIDP system.
  2. When an automated interfacility handoff action is initiated and "NAT," "NT," or "TU" is displayed in the full data block, advise the other facility if a disparity exists between the position declared by their computer and the actual target position.
 h. 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 letter of agreement or a facility directive.

NOTE -
Those en route facilities using HOST software that provides capability for passing interim altitude shall include the specific operations and procedures for use of this procedure in a letter of agreement between the appropriate facilities.
 i. 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. YOU now have the responsibility to ensure that the necessary coordination is accomplished with any intervening controller(s) whose area of jurisdiction is affected by that delay, unless otherwise specified in a letter of agreement or a facility directive.

NOTE -
Those en route facilities using HOST software that provides capability for passing interim altitude shall include the specific operations and procedures for use of this procedure in a letter of agreement between the appropriate facilities.

5-4-7 Point Out

 a. The transferring controller shall:
  1. Obtain verbal approval before permitting an aircraft to enter the receiving controller's delegated airspace. TERMINAL: Automated approval may be utilized in lieu of verbal, provided the appropriate ARTS software is operational (automated point out function), and the procedures are specified in a facility directive/LOA.
  2. Obtain the receiving controller's approval before making any changes to an aircraft's flight path, altitude, or data block information after the point out has been approved.

NOTE -
Those en route facilities using HOST software that provides capability for passing interim altitude shall include the specific operations and procedures for use of this procedure in a letter of agreement between the appropriate facilities.
  3. Comply with restrictions issued by the receiving controller unless otherwise coordinated.
  4. Be responsible for subsequent radar handoffs and communications transfer, including flight data revisions and coordination, unless otherwise agreed to by the receiving controller or as specified in a LOA.
 b. The receiving controller shall:
  1. Ensure that the target position corresponds with the position given by the transferring controller or that there is an association between a computer data block and the target being transferred prior to approving a point out.
  2. Be responsible for separation between point out aircraft and other aircraft for which he/she has separation responsibility.
  3. Issue restrictions necessary to provide separation from other aircraft within his/her area of jurisdiction.

5-4-8 Automated Information Transfer (AIT)

 Transfer radar identification and/or altitude control without verbal coordination under the following conditions:
 a. During radar handoff, and;
 b. Via information displayed in full data blocks, and;
 c. Within the same facility, except as provided in paragraph 5-4-9, and;
 d. When following procedures specified in your facility AIT directive.

5-4-9 Interfacility Automated Information Transfer

EN ROUTE
 Transfer radar identification without verbal coordination under the following conditions:
 a. During radar handoff, and;
 b. Via information displayed in full data blocks, and;
 c. On aircraft at assigned altitude in level flight, and;
 d. Only the first sector within the receiving facility shall utilize the procedure, and;
 e. When following procedures specified in your facility AIT directive and LOA.