Guidelines

Introduction

In the early days of on-line flying with ATC, text was the only method of communication.

Most people's typing was slow, mistakes were common and although some shortcuts could be selected, no-one was really satisfied with the way it worked.

After a while Roger Wilco was used and complete IP-addresses had to be entered first before you could speak to a controller.

It was an improvement already, but in dense traffic environment, during a late hand-over on short final, after a go-around or whatever situation that involved high workload in the cockpit, copying the IP-address while trying to stay airborne often resulted in a crash...

Nowadays, thanks to the latest developments in technology and a core of highly skilled Software Developpers within IVAO, frequency selection can be done swiftly without endangering any "virtual" life.

Although slow and inefficient, some people still use text for a number of reasons:

  • a newbie on IVAO may not feel sufficiently confident to speak on a "frequency"
  • someone may not want to make "noise" and disturb his/her relatives or neighbours
  • some people may have a broken microphone but can't miss IVAO while they are waiting to buy a new one...

Whatever reason people have to use text, they still have the right to do so and to receive ATC service!

BUT.... there is a HUGE drawback to this...

Most of the communication between Pilots and ATC is done by voice. Text can be easily overlooked by ATC when busy with other traffic and this could cause some delay before you may receive a clearance.

Text-Text communication is slow, inefficient and demands particular effort from the controller. In a busy environment you will be his nightmare for several reasons:

  • while typing your clearance or instruction, he's not able to concentrate on his traffic
  • your readback via text is relatively slow and by the time you have started to do what ATC wanted, it may be too late...
  • if you or the controller made a mistake, everything will have to start over again from the beginning and the situation will rapidly get worse (frustrating for both of you!)
  • just imagine what will happen if he urgently needs to give you traffic information...

If you use Text-Text as a controller, you won't make people happy either! Here are some reasons why:

  • while typing in the Ivap text-box, the pilot will not be able to make any inputs in his FlightSim
  • if at some point he forgets to click in the Ivap-textbox to type a message, his keyboard commands will make his FlightSim do all kinds of things he didn't intend to and his flight may end in a crash!
  • in situations where the pilot needs instruction or clearance urgently, such as a landing clearance in short final, by the time you have typed and sent his clearance or instruction and he has typed the readback and complied with it... it could be much too late
  • a pilot who is flying his aircraft manually will flip up-side-down in no time if he has to type while in a turn or executing delicate manoeuvre!
  • any other reason you can think of...

To make everything as enjoyable as possible for everyone, while keeping things practical and somewhat realistic, Text-Voice Communication is the best alternative to Text-Text Communication.

Guidelines

Text-Voice Communication means that either a Pilot or an ATC uses text, whilst the other people on the same frequency use Voice.

This method is designed to reduce the "lag" (reaction time) between an instruction, clearance or request and their compliance or reply.

If the reason you want to use text is for "noise abatement" at home, use a headset to listen to Pilots or ATC.

Use the Text-Voice Abbreviations in the next topic as much as possible.

Pilot uses Text - ATC uses Voice

Pilot

  1. make sure you file TEXT-VOICE in the Remark Field of your Flight Plan.

  2. in text communications DON'T TYPE your CALLSIGN nor that of ATC to establish communication.

  3. USE the Text-Voice ABBREVIATIONS to communicate in standard Aviation English phraseology as much as possible.

  4. WHEN AIRBORNE, FIRST EXECUTE then READBACK an ATC instruction or clearance (unlike in voice communication).

  5. ON THE GROUND, FIRST READBACK then EXECUTE an ATC instruction or clearance.

  6. ONLY the LAST INSTRUCTION or CLEARANCE you received needs to be READ BACK as in 4 or 5, if you haven't had the time to readback the previous one.

ATC

  1. CHECK the FLIGHT PLAN of a pilot who uses text to make sure he knows the TEXT-VOICE procedure.

  2. Do ATC BY VOICE as to any other pilot, BUT REPEAT instructions, clearances and/or information to the pilot who uses text by: CALLSIGN, INSTRUCTION ...I SAY AGAIN,... CALLSIGN, INSTRUCTION (1)

  3. When AIRBORNE, the Pilot will have to FIRST COMPLY, then READBACK to reduce "LAG" (2)

  4. ON THE GROUND, the Pilot will have to do his READBACK FIRST.

  5. LIMIT the number of TRANSMISSIONS to a minimum.

RMK: (1) Newbies who are not used to our strange Aviation language, will learn to understand it much faster by hearing the message twice!

(2) Keep a sharp look-out on what the Pilot does, if he makes a mistake then correct it immediately and REPEAT the instruction.

ATC uses Text - Pilot uses Voice

ATC

  1. Make TEXT ALIASSES in Ivac BEFORE coming ONLINE (Ivac Manual ...)

  2. CONNECT with IVAC and OPEN a VOICE CHANNEL on TS as you would when you use voice

  3. In your ATIS REMARK insert TEXT-VOICE

  4. use PLAIN TEXT instead of ABBREVIATIONS IF A PILOT does NOT UNDERSTAND them

Pilot

  1. When reading TEXT-VOICE in the ATIS, use NORMAL 2-way VOICE communication

  2. Don't expect an immediate reply from ATC, BE PATIENT