Order 7110.65P, Air Traffic Control, with changes

7110.65P 2/19/04from the reference point may be omitted whenrelaying the position of a target if a full data blockassociated with the target has been forced on thereceiving 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 aircraftduring interfacility point-outs only, if both thereceiving and the transferring controllers agree.NOTE−Acceptance of a point-out using the discrete beacon codeas the aircraft’s identification constitutes agreement.3. The assigned altitude, appropriate restrictions,and information that the aircraft is climbing ordescending, if applicable, except when inter/intrafacilitydirectives ensure that the altitude informationwill be known by the receiving controller.NOTE−1. When physically pointing to the target, you do not haveto state the aircraft position.2. Those en route facilities using host software thatprovides capability for passing interim altitude shallinclude the specific operations and procedures for use ofthis 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, ifapplicable).c. When receiving a handoff, point-out, or trafficrestrictions, respond to the transferring controller asfollows:PHRASEOLOGY−(Aircraft ID) (restrictions, if applicable) RADARCONTACT,or(aircraft ID or discrete beacon code) (restrictions, ifapplicable) POINT-OUT APPROVED,orTRAFFIC OBSERVED,orUNABLE (appropriate information, as required).d. If any doubt as to target identification existsafter attempting confirmation in accordance with thissection, apply the provisions of para 5−3−5,Questionable Identification.REFERENCE−FAAO 7110.65, Validation of Mode C Readout, Para 5−2−17.5−4−4. TRAFFICa. When using the term “traffic” for coordinatingseparation, the controller issuing traffic shall issueappropriate restrictions.b. The controller accepting the restrictions shall beresponsible to ensure that approved separation ismaintained between the involved aircraft.5−4−5. TRANSFERRING CONTROLLERHANDOFFThe transferring controller shall:a. Complete a radar handoff prior to an aircraft’sentering the airspace delegated to the receivingcontroller.REFERENCE−FAAO 7110.65, Coordinate Use of Airspace, Para 2−1−14.FAAO 7110.65, Control Transfer, Para 2−1−15.FAAO 7110.65, Receiving Controller Handoff, Para 5−4−6.b. Verbally obtain the receiving controller’sapproval prior to making any changes to an aircraft’sflight path, altitude, or data block information whilethe handoff is being initiated or after acceptance,unless otherwise specified by a LOA or a facilitydirective.NOTE−Those en route facilities using host software that providescapability for passing interim altitude shall include thespecific operations and procedures for use of thisprocedure in a LOA between the appropriate facilities.c. Ensure that, prior to transferring communications:1. Potential violations of adjacent airspace andpotential conflicts between aircraft in their own areaof jurisdiction are resolved.2. Necessary coordination has been accomplishedwith all controllers through whose area ofjurisdiction the aircraft will pass prior to entering the5−4−2Transfer of Radar Identification