L5 - Handoffs25-11-2005 | |
 |
L5 - Handoffs25-11-2005 | |
|
|
A handoff is a transfer of responsibility of an aircraft from one controller to another including a frequency change (in FS, this involves both text and voice modes - they are automatic when choosing a controller into the ATC directory of Squawkbox). A handoff should occur each time an aircraft is leaving a controller's area of responsability to enter the one of another active controller. The rule to be applied is ONE AIRSPACE, ONE CONTROLLER. There must not be two controllers managing the same portion of an airspace or airfield. An airspace can be divided in 2 sectors (west and east for instance) but only one controller will manage each sector. There could be a XXXX_W_APP (for west sector) and a XXXX_E_APP (for east sector) but in no case should 2 controllers deal with a single sector. Handoff points and procedures are usually determined into agreement letters. However, when no agreement letter has been established, the handoff procedures are established online (by chat) between the connected controllers activating adjacent areas. Here are the general cases that will help determining the handoff points and/or altitudes : - handoff from GND to TWR : when aircraft is on holding point. Particularity : if aircraft has to taxi via the runway, the pilot should contact the tower (remember the runway is the only part of the ground which does not belong to the ground controller - the runway is under the responsability of the tower controller because he/she is the one delivering clearances to land and to take off).
- handoff from TWR to DEP or APP : just after take-off when aircraft is airborne, usually before 2,000 ft AGL.
- handoff from APP to APP : before aircraft is reaching the lateral limit of APP airspace, at the altitude determined when coordinating the flight by chat.
- handoff from APP to CTR : before aircraft is reaching upper limit of APP airspace and/or when reaching a specific point (fix or navaid). FL 120 or 12,000 ft is often used as a limit between APP and CTR.
- handoof from CTR to CTR : before aircraft is reaching the lateral limit of CTR airspace and/or when reaching a specific point (fix or navaid), at the FL determined when coordinating the flight by chat.
- handoff from CTR to UP_CTR : before aircraft is reaching upper limit of CTR airspace and/or when reaching a specific point (fix or navaid). FL 195 or 240 are often used as limits between lower and upper airspaces.
- handoff from CTR to APP : before aircraft is reaching lower limit of CTR airspace and/or when reaching a specific point (fix or navaid). FL 120 or 12,000 ft is often used as a limit between APP and CTR.
- handoff from APP to TWR : . for IFR arrival, when aircraft established on ILS or on final, usually at 2,000 or 3,000 ft at about 10 NM inbound. . for VFR arrival, when aircraft in sight of airfield or reporting point, usually at 2,000 or 3,000 ft within 10 NM around the airfield.
- handoff from TWR to GND : when aircraft has vacated the runway. In PC, several commands are available by right clicking on an aircratf tip. When logging as a controller, it is recommended to open a chat window with the controllers you will have to work with so that you can coordinate your handoffs by chat. See L5-Coordination for details. IMPORTANT NOTE : you must not transfer an aircraft which is in conflict with another one. You must deal with the conflict first and then execute the handoff when the situation is clear. If the plane is already reaching the limit of your area of responsability, the least is to coordinate that (by chat) with the controller you are going to give your traffic to. |
|
|
