Radar Handoffs

Front 1

5-4-1 Application

Back 1

To provide continuous radar service to aircraft and facilitate safe, orderly and expeditious flow of traffic, it is often necessary to transfer id of an aircraft from one controller to another.

Front 2

5-4-2 HANDOFF TERMS

Back 2

An action taken to transfer the RADAR IDENTIFICATION of an aircraft from one controller to another if the aircraft will enter the receiving controllers airspace and radio communications with the aircraft will be transferred.

Front 3

5-4-2 HANDOFF TERMS
RADAR CONTACT

Back 3

1. Used by ATC to inform an aircraft that it is identified on the radar display and radar flight following will be provided.
2. The term used to inform the controller that the aircraft is identified and approval is granted for the aircraft to enter the receiving controllers airspace.

Front 4

5-4-2 HANDOFF TERMS
TRAFFIC

Back 4

1. A term used by a controller to transfer 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 pointout
b. in anticipation of a handoff/pointout, or
c. in conjunction with a request for control of an aircraft
2. A term used by ATC to refer to one or more aircraft that may be in conflict

Front 5

5-4-2 HANDOFF TERMS
TRAFFIC OBSERVED

Back 5

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

Front 6

5-4-3 Methods

Back 6

Transfer the identification of an aircraft by at least one of the following methods
Physically point to the target on the receiving controllers display
1) Use landline voice
2) communications
3) Use automation capabilities

Front 7

5-4-3 Methods
When making a hand-off or issuing traffic restrictions relay information to the receving controller in the following order:

Back 7

1 ) Position of target
2) Aircraft ID
3) Altitude (including restrictions)

Front 8

2-1-15 Transfer of Control

1)

Back 8

Transfer control of an aircraft in accordance with the following conditions:
At a prescribed or coordinated location, time, fix, or altitude

Front 9

2-1-15 Transfer of Control

2)

Back 9

At the time a radar handoff and frequency change to the receiving controller have been completed and when authorized by a facility directive or letter of agreement which specifies the type and extent of control that is transferred.
b. Transfer control of an aircraft only after eliminating any potential conflict with other aircraft for which you have separation responsibility.
c. Assume control of an aircraft only after it is in your area of jurisdiction unless specifically coordinated or as specified by letter of agreement or a facility directive.

Front 10

5-4-5

Back 10

Transferring Controller Handoff

Front 11

THE TRANSFERRING CONTROLLER SHALL

Back 11

a. Complete a radar handoff prior to an aircraft entering the airspace delegated to the receiving controller

Front 12

THE TRANSFERRING CONTROLLER SHALL

Back 12

b. Verbally obtain the receiving controllers 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

Front 13

THE TRANSFERRING CONTROLLER SHALL

Back 13

c. Ensure that prior to transferring communications:
1. Potential violations of adjacent airspace and potential conflicts between aircraft in their own area 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 controllers area.
3. Restrictions issued to ensure separation are passed to the receiving controller

Front 14

THE TRANSFERRING CONTROLLER SHALL

Back 14

d. After transferring communications, continue to comply with c1 and c2 above

Front 15

THE TRANSFERRING CONTROLLER SHALL

Back 15

e. Comply with restrictions issued by receiving controller unless otherwise coordinated

Front 16

THE TRANSFERRING CONTROLLER SHALL

Back 16

f. Comply with 2-1-17 (transfer radio communications before an aircraft enters the receiving controllers area unless otherwise coordinated) and to the extent possible, transfer comm when the transfer of radar identification has been accepted.

Front 17

THE TRANSFERRING CONTROLLER SHALL

Back 17

g. Advise the receiving controller of pertinent information not contained in the FDB or flight progress strip. Pertinent information includes but is not limited to:
1 Assigned heading
2 Airspeed restrictions
3 Altitude information issued
4 Observed track or deviation from the last route clearance
5 Beacon code if different
6 Any other pertinent information

Front 18

THE TRANSFERRING CONTROLLER SHALL

Back 18

h. Ensure that the data block is associated with the appropriate target

Front 19

THE TRANSFERRING CONTROLLER SHALL

Back 19

i. Initiate verbal coordination to verify the position of primary or non-discrete targets when using the automated handoff functions

Front 20

THE TRANSFERRING CONTROLLER SHALL

Back 20

Initiate verbal coordination before transferring control of a track when “CST”, “FAIL” ...etc.. is displayed in the data block

Front 21

THE TRANSFERRING CONTROLLER SHALL:

Back 21

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

Front 22

THE TRANSFERRING CONTROLLER SHALL:

Back 22

l. Issue restrictions to the receiving controller which are necessary to maintain separation from other aircraft within our area before releasing control of the aircraft

Front 23

THE TRANSFERRING CONTROLLER SHALL:

Back 23

m. Consider the target as identified on the receiving controllers display when the receiving controller acknowledges receipt verbally or has accepted an automated handoff

Front 24

THE TRANSFERRING CONTROLLER SHALL:

Back 24

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

Front 25

5-4-6

Back 25

Receiving Controller Handoff

Front 26

Receiving Controller Handoff

Back 26

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 a handoff

Front 27

Receiving Controller Handoff

Back 27

b. Issue restrictions that are needed for the aircraft to enter your sector safely before accepting the handoff

Front 28

Receiving Controller Handoff

Back 28

c. Comply with restrictions issued by the initiating controller unless otherwise coordinated

Front 29

Receiving Controller Handoff

Back 29

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 LOA or a facility directive:
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.

Front 30

Receiving Controller Handoff

Back 30

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.

Front 31

Receiving Controller Handoff

Back 31

f. When using appropriate equipment, consider a discrete beacon target’s identity to be confirmed when:
The data block associated with the target being handed off indicates the computer assigned beacon code is being received, or
You observe the deletion of a discrete code that was displayed, or
You observe the numeric display of a discrete code that an aircraft has been instructed to squawk or reports squawking.

Front 32

Receiving Controller Handoff

Back 32

g. Initiate verbal coordination prior to accepting control of a track when “CST”, “OLD,” ...etc is displayed in the data block

Front 33

Receiving Controller Handoff

Back 33

h. Advise the transferring controller when you will delay the climb or descent of an aircraft through the vertical limits of the other controllers sector

Front 34

Receiving Controller Handoff

Back 34

i. If you decide after accepting the transfer of radar identification to delay the aircrafts climb or descent advise the other controller ASAP. You are now responsible to ensure that all necessary coordination is accomplished

Front 35

HANDOFF COMPUTER ENTRY REQUIREMENTS - Mistakes

Back 35

If the wrong address is entered ,re-entering the CID prior to the O appearing in field E will cancel the handoff to be re-accomplished
Intra facility if the O appeared you can re-caputure the H/O by typing in the CID with a /OK

Front 36

Computer Initiated Handoff

Back 36

Intra-facility:
2 digit sector number and aircraft CID, beacon code, call sign or slew.
37 101 (enter)

Inter-facility
D19 = Denver, K46 or K66 = Kansas City
(facility, sector number, and CID)
D19 104 (enter) or K46 413 (enter)

Approach controls, LNK or OMA
three letter identifier and CID
KKK 110 (enter) or OOO 548 (enter)

Front 37

TO ACCEPT HANDOFF

Back 37

Slew on target and (enter) (center slew button) or
Slew over the appropriate (. ) in the INBD list and (enter) (center slew button) or
Type CID
Type in call sign (enter)

Front 38

2-1-17

Back 38

COMMUNICATION TRANSFER

Front 39

COMMUNICATION TRANSFER

Back 39

Transfer radio communications before an aircraft enters the receiving controllers area unless otherwise coordinated or specified by a LOA or a facility directive.
Transfer communications by specifying the following: The facility name or location name and terminal function to be contacted.

Front 40

5-3-8

Back 40

En Route - Retain data blocks that are associated with the appropriate target symbol to provide continuous identity of aircraft. Retain the data block until the aircraft has exited the sector or delegated airspace and all potential conflicts have been resolved. The data block shall display flight identification and altitude information as a minimum display. The displayed altitude may be assigned, interim or reported altitude.

Front 41

KEYBOARD FUNCTIONS

Back 41

AFTER YOU HAVE TRANSFERRED COMMUNICATIONS YOU CAN TYPE:
/0 CID (enter)

VISUALLY INDICATES COMM TRANSFER COMPLETED