|
|
|

UNICOM Radio Procedures
When we signed on to the new HC server we were asked to accept and agree to Terms of Service while participating in the Hovercontrol Multi-User Flight Environment. Terms of Service Practical Guide – FAQ is also included in that information. Within the FAQ’s there is a question regarding voice communications.
UNICOM is an acronym derived from UNiversal Integrated COMmunication. Usually this is “a privately-operated advisory air-to-ground radio service at uncontrolled airfields, in the USA. The UNICOM radio frequency is used near an uncontrolled airport for pilots to make their presence and intentions known to each other. In addition, the radio frequency is reserved for pilots or ground personnel to communicate information related to flight operations and safety in the vicinity of an airport.” – Quotation from AOPA. UNICOM includes a Common Traffic Advisor frequency, or CTAF, which is available for radio communications within a non-towered flight environment. You can find the CTAF listings plaster all over the Sectionals and Approach Plates (Terminal Procedures) issued by the FAA where non-towered operations exist. The AOPA Air Safety Foundation strongly suggests that pilots keep their radios tuned to CTAF when in the non-towered environment. Here’s a link to an AOPA safety bulletin that you may find very informative.
Click Here for AOPA safety bulletin
As you know, HC uses non-towered or uncontrolled airspace environments at Missoula and Hood River. HC’s Teamspeak includes channels to be use for UNICOM and CTAF. Making radio calls on HC’s UNICOM/CTAF is a common sense issue. Basically, other pilots will need to know WHO you are, WHERE you are, and what your INTENTIONS are. Let’s try breaking this down a little further.
Who you are is not only your callsign but also the type of aircraft you are flying. Even though HC is primarily a helicopter environment, mentioning that you are in a “120” doesn’t really help a pilot who might not have wide knowledge of aircraft types. Using terms like “helicopter” or “Type Bell helicopter” might help. A distinctive part of your radio callsign is included, too. “Helicopter One Zulu Zulu” is perfectly acceptable in this regard if your callsign is HC111ZZ, for example.
Where you are is a situational awareness type issue. Mentioning that you are on “downwind runway 25” will cause other pilots to instinctively look to the downwind leg for that runway. Mentioning only that you are at Missoula or Hood River is questionable at best and should be avoided.
Your intentions are of real interest to other pilots. VFR separation is a requirement - especially in the traffic pattern. You could conceivable have aircraft all around you including above and below you. You want to be as accurate as possible and as brief as possible when stating your intentions. “Missoula Traffic, Helicopter One Zulu Zulu, 5 miles northwest of the airport transitioning to the Southeast at six thousand, Missoula.” Hearing such a radio call would cause other pilots to instinctively look for a helicopter, 5-miles northwest of KMSO, at 6,000 MSL, and heading southeast. This certainly would help plan ahead for required VFR separation.
Movement areas are ground operations that include movement of any kind on taxiways and runways that are not active. An “active” runway depends on conditions – wind, visibility, etc. (Understand that most of our flying is now under server generated weather conditions and knowing the active runway is imperative for safety). Since aircraft will be moving on the ground at an airport the WHO, WHERE, INTENTIONS must be applied as well. Think of a radio call like, “Hood River Ground, Helicopter One Zulu Zulu, hover taxiing west on the south taxiway to runway 7 for departure.” It is highly recommended that helicopters hover-taxi over taxiways only. This avoids haphazard conditions and helps maintain orderly movement of all aircraft. Think real-world.
|