Order 7110.65P, Air Traffic Control, with changes

2/17/057110.65P CHG 22. Obtain the receiving controller’s approvalbefore making any changes to an aircraft’s flight path,altitude, or data block information after the point outhas been approved.NOTE−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.3. Comply with restrictions issued by thereceiving controller unless otherwise coordinated.4. Be responsible for subsequent radar handoffsand communications transfer, including flight datarevisions and coordination, unless otherwise agreedto by the receiving controller or as specified in a LOA.b. The receiving controller shall:1. Ensure that the target position correspondswith the position given by the transferring controlleror that there is an association between a computerdata block and the target being transferred prior toapproving a point out.2. Be responsible for separation between pointout aircraft and other aircraft for which he/she hasseparation responsibility.3. Issue restrictions necessary to provideseparation from other aircraft within his/her area ofjurisdiction.5−4−8. AUTOMATED INFORMATION TRANSFER(AIT)Transfer radar identification, altitude control, and/oren route fourth line control information, withoutverbal coordination under the following conditions:a. During radar handoff; andb. Via information displayed in full data blocks;andc. Within the same facility, except as provided inpara 5−4−9, Interfacility Automated InformationTransfer; andd. When following procedures specified in yourfacility AIT directive.REFERENCE−FAAO 7110.65, En Route Fourth Line Data Block Usage, Para 5−4−1.5−4−9. INTERFACILITY AUTOMATEDINFORMATION TRANSFEREN ROUTETransfer radar identification without verbal coordinationunder the following conditions:a. During radar handoff; andb. Via information displayed in full data blocks;andc. On aircraft at assigned altitude in level flight;andd. Only the first sector within the receiving facilityshall utilize the procedure; ande. When following procedures specified in yourfacility AIT directive and LOA.5−4−10. PREARRANGED COORDINATIONPrearranged coordination allowing aircraft underyour control to enter another controller’s area ofjurisdiction may only be approved providedprocedures are established and published in a facilitydirective/LOA in accordance with FAAO 7210.3,para 3−7−7, Prearranged Coordination.NOTE−Under no circumstances may one controller permit anaircraft to enter another’s airspace without propercoordination. Coordination can be accomplished byseveral means; i.e., radar handoff, automated informationtransfer, verbal, point−out, and by prearrangedcoordination procedures identified in a facility directivethat clearly describe the correct application. Airspaceboundaries should not be permitted to become barriers tothe efficient movement of traffic. In addition, completecoordination, awareness of traffic flow, and understandingof each position’s responsibility concerning penetration ofanother’s airspace cannot be overemphasized.REFERENCE−FAAO 7110.65, Coordinate Use of Airspace, Para 2−1−14.FAAO 7110.65, Transfer of Radar Identification, Methods, Para 5−4−3.FAAO 7110.65, Automated Information Transfer (AIT), Para 5−4−8.FAAO 7210.3, Prearranged Coordination, Para 3−7−7.Transfer of Radar Identification5−4−5