Embedded Files
Coordination at every facility on VATSIM, is crucial to the success and efficiency of each position. We work together as a team, and it’s very important for you as one of our newest controllers here at ZSE to understand the importance of controller coordination.
Examples of scenarios needing coordination:
Runway crossing coordination
Position relief briefings
Non-standard procedures
Some common courtesy notes to make about controller coordination:
Wait for the controller’s response to your initial call before you start talking or making your request. The controller you are trying to coordinate with may be very busy on their own frequency.
Speak clearly and make your request/coordinate using proper phraseology as outlined by Chapter 2, Section 1, and all other applicable sections of the 7110.65.
When the controller with whom you are coordinating accepts or denies your request, be sure to reply with your initials and any other pertinent information to indicate that you understand what was said.
While controlling, all of us should be in our applicable Discord channel. If other conversations are going on and you need to coordinate with another controller in the channel, you can say something like “Break for control!” Everyone shall stop their conversation to allow you to coordinate with whomever you need to. You may also tell others to move their conversations to another channel. Let a staff member know if you encounter issues with this.
Runway Crossing Coordination
Runway Crossing Coordination
The following phraseology shall be utilized when coordinating runway crossings
To request a runway crossing: "CROSS RUNWAY (runway identifier) AT (Location) WITH (number of aircraft) (description of aircraft)"
To respond to a request for runway crossing:
(a) "CROSS RUNWAY (runway identifier) AT (Location) WITH (number of aircraft) (description of aircraft)" Or
NOTE- The aircraft callsign may be used when coordinating, provided the ASDE-X data tag showing the correct ACID and type aircraft is displayed.
(b) "HOLD SHORT OF RUNWAY (runway identifier) (other instructions as required)
NOTE- Other instructions include a request for transfer of communications with the aircraft requesting the runway crossing, aircraft callsign, etc.
3. To advise LC when the coordinated runway operation is complete: "RUNWAY (runway identifier) CROSSINGS COMPLETE"
The following example showcases coordination of a runway crossing. You are working Ground Control (GC) and will coordinate with Local Control (LC) for the crossing.
GC: “Local, Ground.”
LC: “Local, go ahead.”
GC: “Cross runway two at alpha with one, King Air.”
LC: “Cross runway two at alpha.”
GC: “(Controller initials).”
When the runway crossing operation is completed:
GC: "Runway two crossings complete."
LC: "(Controller initials)."
Position Relief Briefings
Position Relief Briefings
In order to close a position (disconnect from the network) while other controllers are on above you, you MUST brief any relevant controllers with information about the traffic and any other specific information relevant to the position. Follow the checklist in vZSE General ATC Procedures 7110.00.
For example, if you were working Hillsboro Ground with Hillsboro Local on above you and you wanted to close, you would need to brief the local controller before disconnecting from the network.
A Position Relief Briefing for Hillsboro Ground and Local might look something like this:
HIO_GND: “Hillsboro Local, Hillsboro Ground.”
HIO_TWR: “Hillsboro Local, go ahead.”
HIO_GND: “Looking to close ground, advise ready for a brief.”
At this point, local may ask you to standby. Wait for them to get back to you before you disconnect.
HIO_TWR: “Ready for brief.”
Here, you as the ground controller shall go over the information required by vZSE 7110.00 Appendix A.
If you're using flight strips as required, this brief could be very brief!
After covering the above information, and in order to close out the briefing, the following interaction MUST occur:
HIO_GND: “Any questions?”
HIO_TWR: “No questions.”
HIO_GND: “(Controller initials)”
HIO_TWR: “(Controller initials).”
Non-standard procedures
Non-standard procedures
While the SOPs and LOAs define the stardard procedures to be used, as the saying goes, "all things are possible through coordination." The less busy things are, the more likely non-standard procedures are to be approved.
If you have a pilot requesting something contrary to standard procedure or you'd like to offer something different, just coordinate with the appropriate controllers. Use the examples and advice above and describe what you are asking for.
Page updated
Report abuse