Order 7110.65P, Air Traffic Control, with changes

2/19/047110.65Preceiving controller’s area of jurisdiction, exceptwhen such coordination is the receiving controller’sresponsibility as stated in para 5−4−6, ReceivingController Handoff, and unless otherwise specifiedby a LOA or a facility directive.3. Restrictions issued to ensure separation arepassed to the receiving controller.d. After transferring communications, continue tocomply with the requirements of subparas c1 and 2.e. Comply with restrictions issued by the receivingcontroller unless otherwise coordinated.f. Comply with the provisions of para 2−1−17,Radio Communications Transfer, subparas a and b.To the extent possible, transfer communicationswhen the transfer of radar identification has beenaccepted.NOTE−Before the ARTS/STARS “modify/quick look” function isused to transfer radar identification, a facility directivewhich specifies communication transfer points is required.g. Advise the receiving controller of pertinentinformation not contained in the data block or flightprogress strip unless covered in a LOA or facilitydirective. Pertinent information includes:1. Assigned heading.2. Air speed restrictions.3. Altitude information issued.4. Observed track or deviation from the lastroute clearance.5. The beacon code if different from thatnormally used or previously coordinated.6. Any other pertinent information.h. Ensure that the data block is associated with theappropriate target.i. Initiate verbal coordination to verify the positionof primary or nondiscrete targets when using theautomated handoff functions except for intrafacilityhandoffs using single-sensor systems or multisensorsystems operating in a mosaic RDP mode.j. Initiate verbal coordination before transferringcontrol of a track when “CST”, “FAIL”, “NONE”,“NB”, “NX”, “IF”, or “NT” is displayed in the datablock.k. Advise the receiving controller that radarmonitoring is required when the aircraft is on a directroute initiated by ATC that exceeds usable NAVAIDdistances.l. Issue restrictions to the receiving controllerwhich are necessary to maintain separation fromother aircraft within your area of jurisdiction beforereleasing control of the aircraft.m. Consider the target being transferred asidentified on the receiving controller’s display whenthe receiving controller acknowledges receiptverbally or has accepted an automated handoff.n. Accomplish the necessary coordination withany intervening controllers whose area of jurisdictionis affected by the receiving controller’s delay in theclimb or the descent of an aircraft through the verticallimits of your area of jurisdiction when the receivingcontroller advises you of that delay before acceptingthe transfer of radar identification unless otherwisespecified by a LOA or a facility directive.5−4−6. RECEIVING CONTROLLER HANDOFFThe receiving controller shall:a. Ensure that the target position corresponds withthe position given by the transferring controller orthat there is an appropriate association between anautomated data block and the target being transferredbefore accepting a handoff.REFERENCE−FAAO 7110.65, Coordinate Use of Airspace, Para 2−1−14.FAAO 7110.65, Control Transfer, Para 2−1−15.FAAO 7110.65, Transferring Controller Handoff, Para 5−4−5.b. Issue restrictions that are needed for the aircraftto enter your sector safely before accepting thehandoff.c. Comply with restrictions issued by the initiatingcontroller unless otherwise coordinated.d. Before you issue control instructions directly toan aircraft that is within another controller’s area ofjurisdiction that will change that aircraft’s heading,route, speed, altitude, or beacon code, ensure thatcoordination has been accomplished with each of thecontrollers listed below whose area of jurisdiction isaffected by those instructions unless otherwisespecified by a LOA or a facility directive:Transfer of Radar Identification5−4−3