View source for ATC and Airfield Communications



''DISCLAIMER: THIS GUIDE IS FOR USE IN SIMULATIONS ONLY. DO NOT USE THIS GUIDE FOR REAL LIFE APPLICATIONS AS THE AUTHOR IS NOT A TRAINED ATC. ALSO BEAR IN MIND THIS IS FOR HOGGIT AND GEORGIA AT WAR USE AND MAY NOT BE CONFORMING WITH REAL LIFE AND ICAO PROCEDURES.''

== Purpose ==

Purpose of this Guide is extending the 818th HACS general and mission communications guide by a set of standard communications procedures for use while departing and approaching controlled and uncontrolled airfields. Following these guidelines will drastically reduce the amount collisions and will help making airfield traffic much more efficient for everybody.

== Introduction ==

This document has been written in order to help newer players better understand the communication procedures used for ATC and traffic coordinations. 
This guide should be used in conjunction with the 818th HACS general and mission communications guide. There will be no radio transmission fundamentals in this guide as it is focusing on the Airfield communication only.

== Fundamentals ==

Use radios (SRS for GAW) to not drive or fly into one another around airfields.

=== ATIS ===

Automatic Terminal Information Service (ATIS) is available at all airports.  (Check the briefing for the SRS ATIS frequency of your specific airport) ATIS should be tuned in and listened to prior to taxiing, and prior to announcing landing intentions at a given airport, since the '''current active runway''' for any given airport is clearly stated in the recording.

ATIS is a looped recording that gives GaW users the following information:
*'''Active runway'''
*Wind direction and speed
*Visibility
*Cloud type and density
*Temperature
*Altimeter setting
*QNH/QFE 
<br>

In GAW, ATIS is renewed each hour and assigned a letter for each, starting with Alpha and ending with Delta.

== Airport patterns ==

Airport patterns are used in clear visibility conditions for visual approaches and they increase the number of planes that can be landed in a set timeframe if performed correctly. At uncontrolled Airfields they reduce the number of collisions so they should be basic knowledge for every pilot. Please bear in mind these descriptions are very basic for absolute beginners to get some idea of approach patterns and are not meant to be totally accurate.

=== Overhead break pattern ===
[[File: Overhead Break Pattern GAW.png|500px|thumb]]
The overhead pattern should be the go to method of landing in daytime and good visibility conditions, especially when there is traffic and the airport is uncontrolled. In controlled conditions you can be cleared for a overhead maneuver. The overhead pattern is performed as follows. For additional information and pictures look for resources online as this is a very brief explanation.


==== Initial ====

Establish on runway heading at pattern altitude (usually 1500 ft. AGL) and 300 knots. Once you are within 3-5 nm of the airport you are at the initial point.

==== Break ====

When you are over the runway perform a break into the pattern. This means you turn left or right at a 45 degree bank angle and hold altitude. Reduce your speed and put your gear and flaps down. You can check your kneeboard charts to determine if the runway has a left or right hand pattern. 

==== Downwind ====

You should arrive on downwind on pattern altitude, then descent to 800ft. AGL and get trimmed on speed and gear/flaps down.

==== Base/Final ====

When the airport is at a 45 degree angle behind you start your base turn. If performed correctly you should find yourself on a relatively short final.

=== Straight in ===

During straight in approaches you simply establish on runway heading intercept the glide path and land. This is used during low traffic and for emergency landings. Try not to be too slow during a long final approach because there might be people behind you flying faster. This can mess up separation and someone might eventually go around.

== Necessary radio callouts ==

=== Uncontrolled airfields ===

For uncontrolled airfields the basic procedures contain simply calling out what you are up to and look out for others to avoid collisions. Always takeoff form the active runway or ask what runway is active at the time. Priorities are as follows: 
1. Planes on the runway have absolute priority. 
2. Planes on final have priority over planes awaiting departure.
3. Players awaiting departure need to wait until there is no incoming traffic.

==== Takeoff ====

Call for…

: ...'''radio check''' on ATC/traffic frequency as soon as you have power to your radios.
: ...'''taxi''' out when you are ready to taxi. Look out for other planes taxiing. When in doubt, stop.
: ...'''taking runway''' once you roll onto the runway .
: ...'''taking off''' as you start your takeoff roll.
: ...'''departing/switching frequency''' as soon as you leave the airspace.


==== Landing ====

Call for...

: ...'''inbound''' approximately 20 nautical miles out from the airport.
: ...'''established''' once you are established on runway course and heading approximately 10 nautical miles out.
: ...'''break''' when you are breaking for the overhead pattern.
: ...'''downwind''' as you reach a stable downwind leg.
: ...'''final''' when your final approach has begun.
: ...'''cleared runway''' as soon as you left the active runway.

=== Controlled airfields ===

For controlled airfield you basically request permission to do stuff and get information and instructions by the ATC. Readback important information for the ATC to confirm a correct transmission. Follow ATC instructions as closely.

==== Takeoff ====

Request…

: ...'''startup (optional)''' and do a radio check as soon as you have power to your radios.
: ...'''taxi''' when you are started up. You will receive clearance to taxi to a runway via specified taxiways. 
: &nbsp;&nbsp; Ground charts and airport information are available in the ingame kneeboard.
: ...'''departure''' once you are holding short of the runway. Once cleared for takeoff do not linger around. Be swift, but always be 
: &nbsp;&nbsp; safe.

==== Landing ====

Call for…

: ...'''inbound'''. This is approximately 20 nautical miles out from the airport. You will receive vectors for your approach. Follow these
: &nbsp;&nbsp; instructions closely to avoid colliding with traffic.
: ...'''established''' once you are established on runway course and heading approximately 10 nautical miles out. You will now receive 
: &nbsp;&nbsp; detailed approach instructions and clearances.
: ...'''break''' when you are breaking for the overhead pattern.
: ...'''downwind''' as you reach a stable downwind leg.
: ...'''final when''' your final approach has begun. You will get cleared to land or get a go around at this point.
: ...'''cleared runway''' as soon as you left the active runway. ATC will contact you with taxi instructions for parking.

== Detailed examples ==

=== Uncontrolled airfields ===

General rules for uncontrolled airfields:

Planes on the runway have absolute priority. After that arriving planes on downwind or final have priority over anyone waiting to roll onto the runway.

==== Departure ====

This is a detailed example of an F/A-18C Callsign Uzi 2-1 on the Ramp at Anapa. There is no ATC active at the time.

Radio transmissions by Uzi 2-1 are marked green.

Tune in to the ATC/Traffic frequency (249.5 AM for GaW) as soon as your radios have power and do a radio check to assure you are transmitting loud and clear.

<pre style="background-color: #d1ffd4">249.5, Uzi 2-1, radio check.</pre>

<pre style="background-color: #d1f1ff">Hawg 4-2, Uzi 2-1, got you 5 by 5.</pre>

So you got an answer from another plane. This means the airport is uncontrolled. If you got an answer from an ATC (Callsign Anapa tower or Anapa ground) the airport is controlled. Procedures for this are listed in chapter 2 (Controlled Airfield).

From here on out you basically call out everything you do to all planes in traffic. If not otherwise instructed by a human ATC the active runway for Anapa is always the runway with headwinds. Do not takeoff or land from the wrong end. Another way to find out what runway is in use is to listen to traffic calls and follow what others are doing (as always think for yourself in that case, do not just turn your head off and follow).

Necessary calls are: taxiing out, holding short of the runway, lining up on runway, taking off.

<pre style="background-color: #d1ffd4">Anapa traffic, Uzi 2-1, taxiing out to runway 22.</pre>
<pre style="background-color: #d1ffd4">Anapa traffic, Uzi 2-1, lining up on runway 22.</pre>
<pre style="background-color: #d1ffd4">Anapa traffic, Uzi 2-1, taking off, runway 22.</pre>

Once you are airborne you inform other planes what direction you are departing and which frequency you are switching to.

<pre style="background-color: #d1ffd4">Anapa traffic, Uzi 2-1, departing south east, last call, switching 253 AM, last call.</pre>

==== Arrivals ====

Now the Uzi 2-1 is RTB and inbound to Anapa.

For arrivals your first call should alway be the “inbound call”. It contains the Airfield name you are inbound to, your position, number of aircrafts in the flight, and further remarks like low fuel state.

<pre style="background-color: #d1ffd4">Anapa, Uzi2-1, Inbound from the north east, 25nm out, single ship F/A-18C.</pre>

from this point on you call out where you are at certain points. These points are established (on runway heading 10nm out), breaking over the airfield, downwind, final, cleared runway. Look out for inbound or outbound traffic and listen on your radios where other people are.

<pre style="background-color: #d1ffd4">Anapa traffic, Uzi 2-1, established runway 22.</pre>
<pre style="background-color: #d1ffd4">Anapa traffic, Uzi 2-1, on downwind for runway 22.</pre>

There will be other planes calling out their positions too so be aware you are not the only one in the airspace and check for other planes (e.g. look out the window or at the F10 map).

<pre style="background-color: #d1ffd4">Anapa traffic, Chevy 4-2, holding short runway 22.</pre>
<pre style="background-color: #d1ffd4">Anapa traffic, Uzi 2-1, on 3 mile final runway 22.</pre>
<pre style="background-color: #d1ffd4">Anapa traffic, Uzi 2-1, cleared the active.</pre>

=== Controlled Airfields ===

==== Departures ====

For Controlled Airfields general rules change quite a bit. If you have any special concerns or questions contact tower on radio and ask what you have got to ask. At worst you will get a standby call and you will get an answer after the ATC is done juggling trafic for a bit.

Here is a detailed example scenario for a flight of two A-10Cs Callsign Hawg 3-1 and Hawg 3-2 on the Ramp at Anapa. Anapa is controlled by a human ATC.

<pre style="background-color: #d1ffd4">Radio transmissions by Hawg 3-1 are green.</pre>
Radio transmissions by ATC(Anapa tower) are blue.</pre>

As soon as there is power to the radios tune in to ATC frequency and do a radio check. For GAW this is 249.5 AM.

<pre style="background-color: #d1ffd4">249.5, Hawg 3-1, radio check.</pre>

<pre style="background-color: #d1f1ff">Hawg 3-1, Anapa tower, got you loud and clear.</pre>

Optional:
Now that you know there is a ATC online for Anapa, ask for permission to start up your aircraft and give the tower a basic briefing of your flight.

<pre style="background-color: #d1ffd4">Anapa tower, Hawg 3-1, roger that, flight of two A-10s at parking position 86 and 87, requesting startup and weather information.</pre>

<pre style="background-color: #d1f1ff">Hawg 3-1, Anapa tower, cleared for startup, expect runway 22, QFE 29.87, CAVOK, wind 337 at 10 knots.</pre>

<pre style="background-color: #d1ffd4">Anapa tower, cleared for startup, Hawg 3-1.</pre>

Notice the readback of vital information. This makes sure that you understood the ATC correctly and gives room for corrections. Don't be afraid to ask a "say again", if you did not copy something as radios can be full of static and people talking over each other.

When you are ready and started up call for the tower to get a taxi clearance.

<pre style="background-color: #d1ffd4">Anapa tower, Hawg 3-1, flight of two, request taxi.</pre>

<pre style="background-color: #d1f1ff">Hawg 3-1, Anapa tower, cleared for taxi runway 22 Mike Delta, hold short of runway 22.</pre>

<pre style="background-color: #d1ffd4">Anapa tower, taxi to runway 22 via Mike Delta, holding short runway 22, Hawg 3-1.</pre>

Sometimes you will get remarks beyond your original request like traffic or weather information. Make sure you listen closely for those as they can be quite important. When you are holding short of the runway and ATC has not given clearance for takeoff to you call in and request it.

<pre style="background-color: #d1ffd4">Anapa tower, Hawg 3 flight of two, holding short of runway 22, requesting departure.</pre>

<pre style="background-color: #d1f1ff">Hawg 3 flight, Anapa tower, cleared for takeoff runway 22, wind 337 at 10 knots.</pre>

<pre style="background-color: #d1ffd4">Anapa tower, cleared for takeoff runway 22, Hawg 3-1.</pre>

Once you are airborne call in for a last time to get handed off to GCI/TACCOM.

<pre style="background-color: #d1ffd4">Anapa tower, Hawg 3 flight, airborne, request departure to the east.</pre>

<pre style="background-color: #d1f1ff">Hawg 3 flight, Anapa tower, cleared to depart east, contact magic on 253 AM</pre>

<pre style="background-color: #d1ffd4">Anapa tower, departing east, contacting magic 253 am, thank you, Hawg 3-1 out.</pre>

5.2.2 Arrivals

Now the same flight is RTB and inbound to Anapa for landing.

The procedures for landing at an controlled airfield differ a bit from what you do on an uncontrolled airfield. As always follow ATC instructions as close as possible and redback important information.

First check in on ATC frequency (249.5 for GAW) and call inbound. Do this at best 20-25 nm out from the airport so the atc has time to give you vectors and instructions. Inform ATC about any special remarks like how many planes are in your flight, low fuel or damage at this point.

<pre style="background-color: #d1ffd4">Anapa, Hawg 3-1, Inbound, flight of two A10s, 25 nm north east from the airfield.</pre>

<pre style="background-color: #d1f1ff">Hawg 3-1, Anapa tower, positive ID,active runway is 22, wind 337 at 10 knots, turn right heading 270, decent to 3000 feet.</pre>

<pre style="background-color: #d1ffd4">Anapa Tower, active runway 22, turning right 270, descending to 3000 feet, Hawg 3-1.</pre>

From now on follow ATC instructions.

<pre style="background-color: #d1f1ff">Hawg 3-1, Anapa tower, turn left heading 216 cleared for visual runway 22, report initial.</pre>

<pre style="background-color: #d1ffd4">Anapa tower, turning left 216, cleared for visual runway 22, Hawg 3-1.</pre>

Upon reaching 10 nm from the airport call in for ATC. You will now get detailed approach information. This can be the instruction to do a overhead break or a straight in landing. For a straight in you just intercept the glidepath and come in for a landing on the active runway (mostly used when traffic is low and single planes are inbound). The overhead break consists out of a break, downwind and final circuit and is used for flights of two or more aircraft. ATC can specify a breakpoint in relation to the runway to assure aircraft separation. Since Hawg 3 flight consists out of two A-10s in our example, they will be instructed to do a overhead circuit.

<pre style="background-color: #d1ffd4">Anapa Tower, Hawg 3-1, 10nm out, established.</pre>

<pre style="background-color: #d1f1ff">Hawg 3-1, Anapa tower, cleared for overhead join, left hand break midfield.</pre>

<pre style="background-color: #d1ffd4">Anapa tower, breaking lefthand midfield, Hawg 3-1.</pre>

For now call out your circuit as you would do for a uncontrolled approach (breaking, downwind, base, final). When on final you will get cleared to land or waved off. In case of a “go around” simply fly another circuit and come in to land again.

<pre style="background-color: #d1ffd4">Anapa Tower, Hawg 3-1, in the break.</pre>

<pre style="background-color: #d1ffd4">Anapa Tower, Hawg 3-1, on downwind runway 22.</pre>

<pre style="background-color: #d1ffd4">Anapa Tower, Hawg 3-1, turning base.</pre>

<pre style="background-color: #d1ffd4">Anapa Tower, Hawg 3-1, on final runway 22.</pre>

<pre style="background-color: #d1f1ff">Hawg 3-1, Anapa tower, cleared to land runway 22.</pre>

<pre style="background-color: #d1ffd4">Anapa Tower, cleared to land runway 22, Hawg 3-1.</pre>

At last you will receive taxi information from the tower.

<pre style="background-color: #d1f1ff">Hawg 3-1, Anapa tower, welcome home, taxi to parking position via Alpha Mike.</pre>

<pre style="background-color: #d1ffd4">Anapa tower, taxi to parking via Alpha Mike, Hawg 3-1 thank you.</pre>