ASRC

Tracking Aircraft

1. ONLY track airborne aircraft that have been “radar identified” and you are in communication with.
2. DO NOT track any aircraft that are on the ground.
3. DO NOT track ANY aircraft at the delivery and ground positions.
4. DO NOT track IFR aircraft at the tower position.
5. Only track VFR aircraft that have been assigned a beacon code, are not in the traffic pattern, request/need flight following and must be on your frequency. Handoff VFR aircraft to another controller only if they must be in contact with ATC.
6. Drop track of all VFR aircraft once you tell them to change frequencies.
7. When aircraft leave your airspace and there is no controller to handoff to, you MUST drop track of the aircraft as soon as you tell the aircraft to change frequencies.

Handoffs

1. You will be required to use the handoff “.hand” alias or an equivalent for ALL text aircraft. All text handoffs must include the provided radio names and the frequency that are in the ZDC Position File, NOT the actual text callsign of the position. If using voice there is no need to use a text handoff.
2. DO NOT use the handoff request feature to request handoffs to or from the tower or positions below.
3. Once a handoff request is accepted the initiating controller CANNOT (ASRC will not let you) edit or amend the flight strip, change a temporary or hard altitude, or edit the scratchpad so be sure all amendments are made prior to placing a handoff request.

Flight Strips

1. Only amend flight plans that need to be fixed. You may only amend the plans for aircraft under your control (not necessarily tracking). DO NOT delete previous parts of a route unless you are fixing something.
2. When you amend a route, be sure the pilot can accept the new routing BEFORE you change the flightplan using ASRC.
3. If a pilot is unable to accept a route and must go GPS DIRECT, then insert a departure gate based on the direction if flight, followed by "GPS DIRECT" and insert "hdg" (lowercase letters only) into the scratchpad so the departure controller knows to vector the plane to the departure gate.
4. Examples
   1. Current route, BINKS PALEO V44 SIE CAMRN4, to delete BINKS “.am rte ..PALEO” this removes the points prior to PALEO.
   2. Current route, ZIZZI V308 BILIT PISCA, to delete everything after BILIT “.am rte BILIT..” this removes all the points after BILIT.
   3. To change a departure airport, “.am rte @KIAD”
   4. To change a destination airport, “.am rte KRDU@”

Beacon Codes

1. All aircraft that have CODE flashing in their data blocks must be assigned a new beacon code as soon as possible.
2. Aircraft that come from an uncontrolled sector should be assigned a new beacon code and properly radar identified.
3. You must assign a beacon code from the set allocated to your position using the F9 key. If you do not, the data block may not be displayed properly.
4. If you manually assign a beacon code you MUST assign one from the set allocated to your position and also manually assign the code within ASRC.

Hard or Cruise Altitudes

1. Use the hard altitude (F5) function when assigning a new cruise altitude.
2. In addition, the Center controller should only enter a new hard altitude when issuing a descent that is not per the SOP. Crossing altitudes on STAR’s do not need to be entered as a new hard altitude.

Temporary or Soft Altitudes and Scratchpad

1. The temporary altitude (F8) and scratchpad functions may be used for personal use but may not be used for coordination to replace using the landline or chat box.
2. Temporary altitudes and the scratchpad must be cleared prior to placing a handoff request.
3. If requested by the receiving controller, after coordinating an altitude with the next controller via landline or chat box, the temporary altitude or scratchpad entry does not need to be cleared.
4. Arriving aircraft that are unable to go direct to the entry point to the next sector, place “hdg” (in lowercase) in the scratchpad and be sure the aircraft is on a heading to the entry point. The receiving controller will see “hdg” in the scratchpad and will then provide vectors as appropriate.
5. Remember, controllers should not have to coordinate anything that is per the SOP, so when handing off an aircraft do not enter the assigned altitude as a temporary (or hard) altitude or use the scratchpad for headings or runways.

Approach Controllers

1. Enter assigned headings in the scratchpad for arriving aircraft, that are NOT following the flows, by entering the heading as hxx (in lowercase), where xx is the first two numbers of the heading and omit the last zero. Examples, h01 is heading 010, h17 is heading 170, etc. Clear the scratchpad prior transferring communication to the tower.
2. Enter temporary altitudes for the last assigned altitude. Clear the temporary altitude prior to transferring communication to the tower.
3. If a pilot requests a certain type of approach, enter the approach type into the scratchpad (in lowercase) “vis” for visual approach, “ils” for ILS approach, “vor” for VOR approach, “lda” for LDA approach, “gps” for GPS approach.
4. If a pilot requests a runway that is different from the runway normally assigned per the SOP, coordinate this via landline or chat box with the appropriate controller (tower, approach, final) prior to placing the handoff request.

Departure Controllers

1. If you are unable to give direct to a departure gate prior to handing off, enter “dir” in scratchpad so the next controller knows they need to get the aircraft direct to the departure fix.
2. If the pilot is unable to fly direct to a departure gate, place “hdg” in the scratchpad and assign a heading that would take the aircraft direct to the departure fix. This way the next controller knows the aircraft is unable to fly to the fix.
3. If you are unable to assign an altitude per the SOP (or airspace ceiling if appropriate), then use the temporary altitude so the next controller knows the aircraft has not been assigned the altitude per the SOP. In some cases, this may also need prior coordination.

Tagging aircraft with voice, text or receive voice only

1. ONLY if you are a controlling with voice, tag all aircraft with their voice capabilities:
   • /v - voice
   • /r - receive voice only
   • /t - text only

Air to Ground Voice Communication

1. Enter the voice room name for your Roger Wilco room using your facility then an underscore then your position ID. The combined DC_CTR would use ZDC_06; IAD_TWR would use IAD_5T, etc. See the different position pages for the proper Roger Wilco room for your position.

Ground to Ground Voice Communication

1. Use the override instead of the intercom for coordination. When using the intercom, do not expect the controller to answer the call right away or answer the call at all. It is easier for the receiving controller if the override is used because the controller can still communicate with aircraft on the frequency and talk to another controller at the same time.
2. See the G/G Coordination page for the proper phraseology
3. The use of the override is encouraged for all types of coordination, especially requesting releases, handoffs and point outs