7.3 Unicom Procedures
7.3.1 On IVAO, when there is no Air Traffic Service available, all pilots have to broadcast their intentions, in English, in text on the UNICOM, frequency 122.800 channel in Ivap. In uncontrolled airspace, pilots are obliged to inform other users of the airspace, what their intentions are going to be so that separation between aircraft can be maintained.
7.3.2 The following document serves as an example of what the kind of information that needs to be transmitted on the UNICOM channel. The original document was compiled by Dan Poelman, CA-TA2, and has been adapted by XZ-FOC for South African conditions.
7.3.3 The Five W’s of UNICOM procedures are:
- What? Traffic advisory is a text message from a pilot to other pilots in what you plan to do.
- Who? All pilots flying or intend to fly when no ATC is available.
- Where? On the IVAO network.
- When? Anytime your aircraft moves.
- Why? To avoid conflict with other aircrafts – this is called airmanship.
7.3.4 First, there are a few things, you, the Captain, have to ensure are completed in IVAO in terms of traffic advisory.
7.3.5 Make sure there is no ATC service in your area, therefore check periodically.
7.3.6 If no ATC is available, make sure you are tuned in on Ivap on Com1, frequency 122.800, in IVAO this is known as UNICOM.
7.3.7 In practise this means that pilots are either on an assigned ATC frequency or UNICOM.
7.3.8 Pilots have to monitor the UNICOM frequency often in order to obtain text messages that may effect your operation. Text message scroll on top of flight simulator screen but can also be re-read on the pilot client (Ivap).
7.3.9 Look outside before you move your aircraft.
7.3.10 Weather permitting, so if it is nice (VMC conditions) with good visibility, have a good look outside the cockpit to watch for other traffic.
7.3.11 Make sure your transponder and TCAS are on when required to assist in being seen on other pilot TCAS and for you to see other aircraft on TCAS when in range.
7.3.12 Continue periodically to announce traffic advisory in text on UNICOM because you never know if another aircraft just logged on at your arriving airport, as one example.
7.3.13 Know where you are at all times. Otherwise your traffic advisory may be incorrect and may cause a conflict.
7.3.14 Know the current time in Zulu (Universal Coordinated Time). Avoid saying local time or estimating in xxx minutes because, for example, if a pilot states eta 1730Z (meaning estimated time of arrival is 1730 Zulu) then you can always re-read the text instead of re-reading eta in 10 minutes but you do not know when that was announced.
7.3.15 Text traffic advisory message should be in English anywhere on the IVAO network.
7.3.16 Be familiar with some Aviation English and also abbreviations like for example “eta”.
7.3.17 Keep your traffic advisory generic and simple so that all will understand.
7.3.18 A VFR pilot nearby may not understand the specific STAR you announced in your traffic advisory.
7.3.19 Instead use a cardinal point, for example, inbound from the “Northwest”.
7.3.20 While announcing text traffic advisories, you do not need to repeat your call sign since the text message includes your call sign.
How does a pilot make a self-announced traffic advisory?
7.3.21 You have asked yourself the following first.
- Who do I announce the text traffic advisory to?
- What type of aircraft am I using?
- Where am I?
- What do I want to do?
7.3.22 This traffic advisory can be used in phases of flight. From start-up/push back, taxi, take-off, climb, cruise, descend, approach, landing, taxi, shutdown. Therefore make announcements on these stages.
7.3.23 See Main Menu -> Flight Ops section -> Training -> Documentation -> Unicom