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 must be accomplished in all areas of radar surveillance except where it is not operationally feasible. Where such constraints exist, they must be:
NOTE: Automated handoff capabilities are only available when FDP is operational.
NOTE: Acceptance of a point-out using the discrete beacon code as the aircraft's identification constitutes agreement.
NOTE: When physically pointing to the target, you do not have to state the aircraft position.
Unless otherwise coordinated or specified in an LOA or facility directive, the transferring controller must:
NOTE: Before the STARS “modify/quick look” function is used to effect a handoff, a facility directive that specifies communication transfer points is required.
The receiving controller must:
NOTE: When the beacon code received from the aircraft does not match the computer assigned beacon code, the code received (ERAM, MEARTS) or the site-adapted code (received, computer-assigned, or both for STARS) will be displayed in the data block. When the aircraft changes to the computer assigned code, the code is automatically removed from the data block. In this instance, the observance of code removal from the data block satisfies confirmation requirements.
Transfer radar identification, altitude control, and/or en route fourth line control information, without verbal coordination under the following conditions:
NOTE: Information transferred using AIT procedures may be bi-directional, and may involve more than two sectors. Complete coordination, awareness of traffic flow, and understanding of each position's responsibilities concerning AIT procedures cannot be overemphasized.
Prearranged coordination allowing aircraft under your control to enter another controller's area of jurisdiction may only be approved provided procedures are established and published in a facility directive in accordance with FAA Order JO 7210.3, paragraph 3-6-6, Prearranged Coordination.
NOTE: Under no circumstances may one controller permit an aircraft to enter another's airspace without proper coordination. Coordination can be accomplished by several means; i.e., radar handoff, automated information transfer, verbal, point-out, and by prearranged coordination procedures identified in a facility directive that clearly describe the correct application. Airspace boundaries should not be permitted to become barriers to the efficient movement of traffic. In addition, complete coordination, awareness of traffic flow, and understanding of each position's responsibility concerning penetration of another's airspace cannot be overemphasized.
NOTE: A “+” notation may be added to denote an assigned speed at or greater than the displayed value. A “-” notation may be added to denote an assigned speed at or less than the displayed value.
NOTE: Due to system and character limitations the usage of these standardized entries may require additional support via facility directive in order to provide complete coordination.