VATSIM Web Site 
        12 Online Visitor     
MAIN MENU
 
    ATC HANDBOOKS
    » ATC Manual 
    » ATC Guides 
    » ATC References 
 
    ATC UPGRADE
  » Rating Requirements 
    » Upgrade Requests 
 
    ATC SOFTWARE
    » Introduction 
    » ASRC 
    » VRC 
» EuroScope
» ServInfo 
 
    EUD-TD OPERATIONS
    » ATC Academy 
  » VACC Support 
    » Practical C and SC Test Requests
 
    EUD-TD ORGANIZATION
    » Management 
    » Examiners
      » Instructors 
      » Practical Controller Test Pilots
      » VACC TD´s


PILOT SECTION  WORK IN PROGRESS
» New Pilots Start HERE
» VATSIM Pilot Resource Center
» Pilots Introduction
» How to Interact with ATC
» Meteorology 
» Flight Procedures
» Pilot Reference Material



The main purpose of this document is not to teach people how to speak; we hope you know this already. We are also not trying to teach you how to fly. That is also a requirement. What we are trying to achieve here is to teach you how to COMMUNICATE using voice while flying, an altogether different skill.

When flying with voice, every time you key the microphone, you will be using up valuable "airtime". If every time you transmit each instruction takes, say 20 seconds. That could mean that you and your controller only get one command understood and acted upon every 50 seconds or so, by which time other aircraft could have missed a vital instruction  i.e. flown through an ILS localizer or missed a landing clearance. So the main purpose of the training is to learn how to COMMUNICATE with the minimum of fuss and delay, so that the “read-backs” can be passed to the controller without taking up too much of this valuable "airtime".

The key is Comminication and this means that both the Pilot and the ATCO communicate their instructions and understandings to each other. There is nothing more frustrating for an ATCO than dealing with pilots who do not communicate sufficiently, but who simply reply with a "Roger" or (even worse) an "ok" or "Will Do"

So what are the main basics of voice flying? Well there are many, but some of the most important lessons you can learn are these THINK BEOFRE TALKING this sounds obvious, but so many people do not do this, keying the microphone and stumbling and stuttering through an instruction which they have not prepared at all..

An example of R/T messages often heard from pilots online is

"Annnnd..ummmm Charlie Delta ummmm Yankee 662 ummm heading ummm 230 ummm flight level ummm 210. Correction That´s flight level ummm 200 sorry not flight level 210 , my mistake  Charlie Delta Yankee 662 Over, out"

This would take around 20 seconds to say !

Compare it with

"Iberia 845, heading 290, flight level 150, inbound Trosa"

This takes 5 seconds to say and is MUCH clearer to the controller. What´s the difference? Simple -The pilot KNEW what to say before starting to speak!

Hints and Tips

To give you a few pointers here is a list of Do´s and Don´ts of common things that people get wrong when they first try using voice.

DO;

  • Wait your turn. The radio might be busy but that isn't a reason to cut into someone else's conversation with a controller. It just creates even more delays. Also listen out to make sure that the pilot before you reads back his clearance that the controller has given him before you make you call. Remember while you or a controller is transmitting nobydy else can get a message through!!
  • Know what you intend to transmit beofre starting to talk.
  • Be patient, just because the controller is not speaking on the radio does not mean he isn't doing any work. In fact much of the work of a controller is done "off-air" involving co-ordination with other fellow controllers, updating flight strips , looking up clearances or typing instructions all of which take time.
  • Wait a few seconds after joining a frequency before you transmit so you don’t transmit in the middle of a conversation.
  • Readback ALL clearances and instructions.
  • If you don't understand an instruction then ask the controller to say the instruction again, or to explain what it means. Use a private message if you don't want to say it on the air!
  • In order to avoid problems understanding your transmissions please make sure that you have correctly set up AVC using the auto microphone configure function. Also worth a note for both ATC and pilots, Vatsim is a global organisation and has many members to whom English will not be their first language so please spare a special thought for our foreign counterparts and speak clearly and slowly.
  • If you are unable to comply with an instruction from ATC then tell them so that they can plan something else for you before it causes a problem with other aircraft in the vicinity.

DO NOT;

  • Readback the winds or use the phrase "winds copied" in reply to a take off or landing clearance, it's not needed.
  • Reply "standing by" to an instruction to standby. No reply is necessary at all.
  • The use of the word "over" is not required.
  • Use Roger as a reply to a question which needs a direct answer yes (AFFIRM) or no (NEGATIVE).
  • Misunderstand the difference between Flight Levels and Altitudes.

Read Backs

It is very important to read back certain instructions that ATC give to you so that they know that you have understood what they have told you. It its not necessary to read back absolutely everything, the following list shows some important information that should be readback:

  • Taxi instructions
  • Level/climbing/descending instructions
  • Heading instructions
  • Speed instructions
  • Airways or route clearances
  • Approach clearances
  • Runway-in-use
  • Clearance to enter, land on, take-off on, backtrack, cross, or hold short of any active runway
  • Transponder operating instructions
  • Altimeter settings
  • Frequency changes
  • Type of radar service

So please note that when you are given your clearance on the ground do not just reply "Roger", read back the clearance fully so that ATC can spot if you have misheard or misinterpreted something they have said.

  • eg. FL100 is spoken as "flight level one hundred" and FL120 is spoken as "flight level one two zero". Note the word hundred must not be used for headings.

Another phrase used with climbs/descents is "when ready". This places the responsibility on the pilot for deciding when to initiate his climb/descent. Eg, "BAW123 when ready descend FL80 to be level by BNN", here the controller has introduced another phrase "to be level by" as well. This means exactly what is says commence your descent when you want but you must have reached FL80 when you arrive at BNN, note at BNN not 50nm before please!

If on the other hand you do not understand what ATC is communicating to you, then it is equally important that this is properly communicated to ATC as well. if it is a case that you did not understand the instruction then ask ATC to repeat the instruction by using the words "Say Again" as part of your read back,. If it is a case of you not being able to follow the instruction given then use the words "Unable" as part of your read back followed by the reason why you are not able to comply.

 Initial Contact

Many new pilots log on to the network, parked at a gate but then expect ATC to start the communication and when nothing happens they usually log of frustrated due to lack of success.
The Initial Contact on the Ground MUST at all times come from the Pilot. and in the following format

"SpeedBird 123, B737 at Gate E43, Request IFR Clearance to Paris Orly".

This starts the communication flow between Pilot and ATC

Other often heard mistakes my new pilots are those who log on to the network, do all the pre-take off checks, FMS flight programming and then suddenly start commnications by saying

"Transavia 430, Request Taxi"
or even worse
"Transavia 430, Ready for Take Off"

In both cases here the pilot has jumped a few steps of the proper communication procedure.

Similarily, when ATC hands you over to another controller then you, as the pilot need to start the communication process with the new controller. 

Common Phraseology

The following list contains most common phrases to be used in voice by both pilots and controllers.

Word/Phrase

Meaning

Acknowledge

Let me know that you have received and understood this message

Affirm

Yes

Approved

Permission for proposed action granted

Break

Indicates a seperation between messages

Break Break

Indicates the seperation between messages transmitted to different aircraft in a busy environment

Cancel

Annul the previously transmitted clearance

Changing to

I intend to call (unit) on (frequency)

Check

Examine a system or procedure. (Not to be used in any other context. No answer is normally expected

Cleard

Authorised to proceed under the conditions specified

Climb

Climb and maintain

Confirm

I request verification of: (clearance; instruction; action information)

Contact

Establish communications with (your details have been passed)

Correction

An error has been made in this transmission ( or message indicated). The correct version is..

Descend

Descend and maintain

Disregard

Ignore

Hold short

Stop before reaching the specified location. (only used in limited circumstances where no defined point exists e.g. where there is no suitably located holding point, or to reinforce a clearance limit

How do you read

What is the readability of my transmission

I say again

I repeat for clarity and emphasis

Maintain

Continue in accordance with the condition(s) specified or in its literal sense, e.g. "Maintain VFR"

Monitor

Listen out on frequency. (pilots should listen in on freq and what for ATC to initiate the call

Negative

No; Permission not granted; That is not correct or not capable

Pass your message

Proceed with your message

Read back

Repeat all, or the specified part, of this message back to me exactly as received

Report

Pass requested information

Request

I should like to know, or wish to obtain

Roger

I have received all your last transmission. (Under no circumstances to be used in reply to a question requiring a direct answer in the affirmative (affirm) or negative (negative) context

Say again

Repeat all, or the following part of your last transmission

Speak slower

Reduce your rate of speech

Standby

Wait and I will call you (Standby is not an approval or denial. Pilots are not required to read back "Standing by"

Unable

I cannot comply with your request, instruction or clearance. (Unable is normally followed by a reason)

Wilco

I understand your message and will comply with it (abbreviation for comply)

Words twice

As a request. Communication is difficult. Please send every word twice. (As information; since communication is difficult every word in this message will be sent twice


©2003-2008 VATSIM EUROPE DIVISION - TRAINING DEPARTMENT