Virtual Air Traffic Simulation - USA Division
Pointouts and Handoffs
In the following ATCast video, brought to you by SATCA
Discover Simple, Private Sharing at Drop.io
Review
What is a pointout?
The pilot controller glossary defines a pointout as the following:
From The FAA – Pilot Controller Glossary
"RADAR POINT OUT- An action taken by a controller to transfer the radar identification of an aircraft to another controller if the aircraft will or may enter the airspace or protected airspace of another controller and radio communications will not be transferred."
When do we use a pointout?
You utilize a pointout anytime one of your aircraft, will or may, enter another controller's airspace. If you think that you may need to issue a pointout, then you probably should. It is always better to err on the side of caution.
Phraseology
When initiating the handoff the following items must be included:
- The phrase "Pointout"
- The location of the aircraft, unless physically pointing to the controller's screen.
- The aircraft callsign, or squawk code if no callsign is displayed
- The altitude of the aircraft
- Your intentions
Once the receiving controller identifies the aircraft, he will issue one of the following instructions:
"POINTOUT APPROVED" - If the receiving controller states this, then your aircraft can enter his airspace as requested, and you can retain control of the aircraft.
"RADAR CONTACT" - If the receiving controller states this, then in order for your aircraft to enter his airspace, you must hand the aircraft off to him.
"YOUR CONTROL" - If the receiving controller states this, then you can do whatever you want to do with your aircraft inside of his airspace.
"UNABLE" - If the receiving controller states this, then your aircraft may not enter his airspace at all.
Another phrase you may hear in a point out is the following:
"TRAFFIC (position of aircraft)" - Along with an aircraft’s position used by the controller approving a pointout means "Separate your pointout aircraft from this aircraft of mine while in my airspace."
Once you have visual confirmation of the aircraft the receiving controller is referring to, then you can state the following:
"TRAFFIC OBSERVED" - This indicates to the receiving controller that you see his aircraft and are going to keep your aircraft separated from it.
Handoffs
The Pilot/Controller Glossary defines a Handoff as....
From The FAA – Pilot Controller Glossary
"HANDOFF- An action taken to transfer the radar identification of an aircraft from one controller to another if the aircraft will enter the receiving controller's airspace and radio communications with the aircraft will be transferred."
In the following ATCast video, brought to you by SATCA
Discover Simple, Private Sharing at Drop.io
Review
There are three methods you may use to transfer radar identification.
- Physically pointing to the controller's screen
- Use the landline to preform a manual handoff
- Use automation capabilities (the most common form on VATSIM)
Manual Handoff Procedures
When utilizing a manual handoff, the following items must be included in the following order:
- The term "Handoff"
- The position of the aircraft in relation to something that both controllers can see (A NAVAID works well for this purpose)
- The aircraft identification
- The altitude information of the aircraft
If you are physically pointing to a controller's screen, then you may omit the position information, however the rest of the information must be given.
If the receiving controller issues the phrase "Radar Contact", then radar identification has been transferred and you may instruct the pilot to contact the next controller.
Automated Handoff Procedures
Preforming an automated handoff on VATSIM is simple. If using VRC you can simply right click on the aircraft, click handoff, and select the controller. This will request the transfer. Your instructor will give you more information on utilizing this feature.
Responsibilities of Transferring and Receiving Controllers
Transferring Controller
The controller initiating the transfer has five (5) responsibilities:
- The transferring controller must initiate the handoff prior to the aircraft entering the receiving controller's airspace.
- If the aircraft's course, altitude, etc., is changed during or after the handoff was approved, verbal coordination and approval must occur unless specified in an SOP or facility directive.
- Before the transfer is initiated, all conflicts with other aircraft or airspace must be resolved and coordinated.
- Communications must be transferred after the radar handoff has been accepted and before the aircraft enters the receiving controller's airspace. A handoff has been accepted when the receiving controller states, "Radar Contact" or if using automation, the target is accepted by the next sector.
- Any relevant information must be passed on, such as speed or altitude restrictions, if it deviates from what is normally expected.
Receiving Controller
The controller receiving the transfer has for (4) responsibilities:
- The identity of the target must be confirmed
- Ensure there are no conflicts prior to accepting the handoff
- Do not issue control instructions to the aircraft until they are inside of your airspace unless previously coordinated with a controller, either verbally, or via a SOP or facility directive.
- Verify the targets Mode C altitude.
