Document Information
Version 2
Created 12/28/2015 03:08
Last Updated 11/24/2020 22:22
by Finn Hutter

Ground to Ground Voice Communications

 

SOP-006

ZSE Senior Staff

Version 2

 

Amended 2018-10-25, changes noted in bold font.

 

1. PURPOSE

This Standard Operating Procedure (SOP) provides a plan for the use of ground-to-ground voice communications within ZSE.

2. ROLES AND RESPONSIBILITIES

This SOP shall be maintained, revised, updated, or canceled by ZSE the Senior Staff, and shall be effective unless there is a conflict with the VATUSA/VATSIM policies in which case they shall supersede these procedures.

3. DISTRIBUTION

This SOP is to be read and used by all ZSE controllers.

4. BACKGROUND

Controller-to-controller communications are a necessity in any modern air traffic environment. Through the use of landlines, controllers within and between facilities can communicate information and make requests. This SOP addresses general methods of communication outlined in technical order 7110.65 as well as specific procedures for Seattle ARTCC facilities.

5. FACILITY NAMING CONVENTIONS

a. All positions with a unique radio call sign shall use that call sign when communicating on G/G channels. Examples:

i. Seattle TRACON - "Seattle Approach"

ii. KPDX Tower - "Portland Tower" or "Portland Local"

iii. KGEG Ground - "Spokane Ground"

b. Seattle Center

i. When combined, Seattle Center shall use the call sign "Seattle Center"

ii. When sectorized, each sector of Seattle Center shall use their sector letter in their call sign in addition to the words "Seattle Center". Example: “North Center”

c. In cases where controllers are certain no confusion shall arise, call signs may be shortened. A call from Seattle Ground to Seattle Tower may use the call signs "Ground" and "Tower" between themselves. Here is a call from Ground to Tower. (eg. “Tower, Ground, Request Clearance for AAL558 to cross Runway 16L and 16C")

6. INTERPHONE MESSAGE FORMAT

Controllers shall use the following format for intra/interfacility communications.

a. For intercom/interphone communications:

i. Caller initiates the call and when it is answered, begins by stating the position being called, their position and the type of message (handoff, point out, APREQ).

ii. Receiver replies with their position and replies to message and ends with operating initials.

iii. Caller gives operating initials and terminates the call.

b. For override communications:

i. Caller initiates the call and shall remain silent until acknowledged by the receiver.

ii. Receiver acknowledges override call by stating their position followed by the phrase "go ahead override".

iii. Caller states message.

iv. Receiver replies to message and ends with operating initials.

v. Caller gives operating initials and terminates the call.

Examples of interphone and override messages can be found in FAAO 7110.65 section 2-4-12.