DCS World Wiki - Hoggitworld.com - User contributions [en]

ATC and Airfield Communications

2019-05-12T23:46:46Z

Blackbird: /* ATIS */

''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
*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.
:    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
:    safe.

==== Landing ====

Call for…

: ...'''inbound'''. This is approximately 20 nautical miles out from the airport. You will receive vectors for your approach. Follow these
:    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
:    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>

ATC and Airfield Communications

2019-05-12T23:46:30Z

Blackbird: /* ATIS */

''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.
:    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
:    safe.

==== Landing ====

Call for…

: ...'''inbound'''. This is approximately 20 nautical miles out from the airport. You will receive vectors for your approach. Follow these
:    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
:    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>

ATC and Airfield Communications

2019-05-12T23:30:41Z

Blackbird: /* Downwind */

''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
*hPa/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.
:    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
:    safe.

==== Landing ====

Call for…

: ...'''inbound'''. This is approximately 20 nautical miles out from the airport. You will receive vectors for your approach. Follow these
:    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
:    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>

ATC and Airfield Communications

2019-05-12T23:30:30Z

Blackbird: /* Base/Final */

''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
*hPa/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 decent 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.
:    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
:    safe.

==== Landing ====

Call for…

: ...'''inbound'''. This is approximately 20 nautical miles out from the airport. You will receive vectors for your approach. Follow these
:    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
:    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>

ATC and Airfield Communications

2019-05-12T23:30:07Z

Blackbird: /* Downwind */

''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
*hPa/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 decent 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. Now you are free to descent. 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.
:    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
:    safe.

==== Landing ====

Call for…

: ...'''inbound'''. This is approximately 20 nautical miles out from the airport. You will receive vectors for your approach. Follow these
:    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
:    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>

ATC and Airfield Communications

2019-05-12T23:28:40Z

Blackbird: /* Initial */

''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
*hPa/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 ====

On downwind you should be still on pattern altitude, trimmed on speed and gear/flaps down.

==== Base/Final ====

When the airport is at a 45 degree angle behind you start your base turn. Now you are free to descent. 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.
:    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
:    safe.

==== Landing ====

Call for…

: ...'''inbound'''. This is approximately 20 nautical miles out from the airport. You will receive vectors for your approach. Follow these
:    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
:    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>

Hoggit Instructors

2019-04-24T20:29:45Z

Blackbird: /* The Instructors */

=Contacting an Instructor=

WIP.

=The Instructors=

{| class="wikitable"
!Instructor Name
!Discord Handle
!Reddit Account
!Areas of Knowledge
|-
|Acidic
|Acidic#0001
|Acidictadpole
|Mission Scripting, A-10C.
|-
|Blackbird
|Blackbird#9371
|blackbird300793
|ATC, COMMS, F/A-18C, F-14B Rio, A-10C, AV-8B, M2000C, AJS37, UH-1H, KA-50, P51.
|-
|Brad_Chanderson
|Brad_Chanderson#4502
|Brad_Chanderson
|Hardware, VR, F-14 Pilot, Su-27, F/A-18C, UH-1H, F-5E
|-
|Cajunvoodoo
|Cajunvoodoo#1660
|thomasvoid
|F/A-18C, F-15C, M2000C, A-10C, Su33
|-
|Cosmicdoubloon
|Cosmicdoubloon#2293
|cosmicdoubloon
|A-10C, all FC3, C-101, L-39, F-5E, Gazelle, FW-190, ATC, BFM, mission editor
|-
|GlidingWolf
|GlidingWolf [DUEAG]#2710
|GlidingWolfie
|ATC, COMMS, GCI, LotATC, general procedures, F/A-18C
|-
|LazyBoot
|LazyBoot#0001
|LazyBoot
|F/A-18C Hornet, AJS37 Viggen, AV-8B Harrier, MI-8, SA342 Gazelle, F-14 Tomcat.
|-
|Llama
|Llama#3191
|CMDRLlamaKing
|Ka50, Viggen, AV-8B, M2000C, Huey, Gazelle, UH-1H, F-15C, Su-27
|-
|Nomad
|Yang Xiao Long#0071
|Ltnomad
|ATC, COMMS, F-15C, TF-51D, AV-8B, BVR.
|-
|Osiris
|Osiris#9893
|400Osiris
|F/A-18C, A-10C, F-14B
|-
|squinkys
|squinkys#1776
|squinkys
|Fundamentals of Flight, Airfield Procedures, Carrier Procedures, F/A-18C, A-10C, Mi-8, UH-1H
|}

=Events=

{| class="wikitable"
!Event name
!Date
!Host
!Server
|-
|Example Event
|Jan 11, 2019
|Acidic
|TNN
|}

Hoggit Instructors

2019-01-11T18:25:42Z

Blackbird:

=This page is a Work In Progress=

Welcome to the Hoggit Instructor page. Each instructor in Hoggit Discord should have an entry on this page, indicating what they can help new players with. Upcoming events also appear here.

=Hoggit Instructors=

{| class="wikitable"
!Instructor Name
!Discord Handle
!Reddit Account
!Areas of Knowledge
|-
|Acidic
|Acidic#0001
|Acidictadpole
|Mission Scripting, A-10C.
|-
|Blackbird
|Blackbird#9371
|blackbird300793
|ATC, COMMS, F/A-18C, A-10C, AV-8B, M2000C, AJS37, UH-1H.
|-
|Nomad
|Yang#0071
|Ltnomad
|F-15C, TF-51D, AV-8B.
|}

=Events=

{| class="wikitable"
!Event name
!Date
!Host
!Server
|-
|Example Event
|Jan 11, 2019
|Acidic
|TNN
|}

ATC and Airfield Communications

2019-01-11T16:44:39Z

Blackbird:

''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 ==

For basic radio rules and fundamentals please reference Section 3 of the 818th HACS general and mission communications guide.

== 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 ===

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 2000 ft. AGL) and 250 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 ====

On downwind you should be still on pattern altitude, trimmed on speed and gear/flaps down.

==== Base/Final ====

When the airport is at a 45 degree angle behind you start your base turn. Now you are free to descent. 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.
:    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
:    safe.

==== Landing ====

Call for…

: ...'''inbound'''. This is approximately 20 nautical miles out from the airport. You will receive vectors for your approach. Follow these
:    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
:    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>

ATC and Airfield Communications

2019-01-11T16:27:14Z

Blackbird: Created page with " ''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 H..."

''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 ==

For basic radio rules and fundamentals please reference Section 3 of the 818th HACS general and mission communications guide.

== 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 ===

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 2000 ft. AGL) and 250 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 ====

On downwind you should be still on pattern altitude, trimmed on speed and gear/flaps down.

==== Base/Final ====

When the airport is at a 45 degree angle behind you start your base turn. Now you are free to descent. 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.
:    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
:    safe.

==== Landing ====

Call for…

: ...'''inbound'''. This is approximately 20 nautical miles out from the airport. You will receive vectors for your approach. Follow these
:    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
:    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: #8effaa;font-family: 'Lucida Console'">249.5, Uzi 2-1, radio check.</pre>

<pre style="background-color: #8edeff;font-family: 'Lucida Console'">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.

''Anapa traffic, Uzi 2-1, taxiing out to runway 22.''
''Anapa traffic, Uzi 2-1, lining up on runway 22.''
''Anapa traffic, Uzi 2-1, taking off, runway 22.''

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

''Anapa traffic, Uzi 2-1, departing south east, last call, switching 253 AM, last call.''

==== 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.

''Anapa, Uzi2-1, Inbound from the north east, 25nm out, single ship F/A-18C.''

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.

''Anapa traffic, Uzi 2-1, established runway 22.''
''Anapa traffic, Uzi 2-1, on downwind for runway 22.''

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).

''Anapa traffic, Chevy 4-2, holding short runway 22.''
''Anapa traffic, Uzi 2-1, on 3 mile final runway 22.''
''Anapa traffic, Uzi 2-1, cleared the active.''

=== 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.

Radio transmissions by Hawg 3-1 are ''Italic''.
Radio transmissions by ATC(Anapa tower) are '''Bold'''.

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.

''249.5, Hawg 3-1, radio check.''

'''Hawg 3-1, Anapa tower, got you loud and clear.'''

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.

Anapa tower, Hawg 3-1, roger that, flight of two A-10s at parking position 86 and 87, requesting startup and weather information.

Hawg 3-1, Anapa tower, cleared for startup, expect runway 22, QFE 29.87, CAVOK, wind 337 at 10 knots.

Anapa tower, cleared for startup, Hawg 3-1.

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.

Anapa tower, Hawg 3-1, flight of two, request taxi.

Hawg 3-1, Anapa tower, cleared for taxi runway 22 via whiskey 3 whiskey mike delta, hold short of runway 22, be advised you have 2 viggens taxiing out in front of you, follow after them.

Anapa tower, taxi to runway 22 via w3, w, m, d, following two viggens, holding short runway 22, Hawg 3-1.

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.

Anapa tower, Hawg 3 flight of two, holding short of runway 22, requesting departure.

Hawg 3 flight, Anapa tower, cleared for takeoff runway 22, wind 337 at 10 knots.

Anapa tower, cleared for takeoff runway 22, Hawg 3-1.

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

Anapa tower, Hawg 3 flight, airborne, request departure to the east.

Hawg 3 flight, Anapa tower, cleared to depart east, climb to 5000 feet, traffic from your left at angels 12, contact magic on 253 AM, have a nice day.

Anapa tower, departing east, contacting magic 253 am, thank you, Hawg 3-1 out.

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.

Anapa, Hawg 3-1, Inbound, flight of two A10s, 25 nm north east from the airfield.

Hawg 3-1, Anapa tower, positive ID,active runway is 22, wind 337 at 10 knots, turn right heading 270, decent to 3000 feet.

Anapa Tower, active runway 22, turning right 270, descending to 3000 feet, Hawg 3-1.

From now on follow ATC instructions.

Hawg 3-1, Anapa tower, turn left heading 216 cleared for visual runway 22, report initial.

Anapa tower, turning left 216, cleared for visual runway 22, Hawg 3-1.

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.

Anapa Tower, Hawg 3-1, 10nm out, established.

Hawg 3-1, Anapa tower, cleared for overhead join, left hand break midfield.

Anapa tower, breaking lefthand midfield, Hawg 3-1.

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.

Anapa Tower, Hawg 3-1, in the break.

Anapa Tower, Hawg 3-1, on downwind runway 22.

Anapa Tower, Hawg 3-1, turning base.

Anapa Tower, Hawg 3-1, on final runway 22.

Hawg 3-1, Anapa tower, cleared to land runway 22.

Anapa Tower, cleared to land runway 22, Hawg 3-1.

At last you will receive taxi information from the tower.

Hawg 3-1, Anapa tower, welcome home, taxi to parking position via Alpha Mike.

Anapa tower, taxi to parking via Alpha Make, Hawg 3-1 thank you.

6. ATC brevity quick reference

Hoggit DCS World Wiki

2019-01-11T15:14:50Z

Blackbird: /* Technique Guides & Resources */

<div class="row">
<div class="col-sm-12 hidden-xs">
[[File:Toc.png|class=img-responsive center-block|link=Hoggit DCS World Wiki]]
</div>
<div class="col-sm-12 hidden-sm hidden-md hidden-lg">
[[File:Toc_small.png|class=img-responsive center-block|link=Hoggit DCS World Wiki]]
</div>
<div class="col-sm-12 hidden-xs">
[[File:GAWupdate.png|class=img-responsive center-block|link=Georgia At War]]
</div>
<div class="col-sm-12 hidden-sm hidden-md hidden-lg">
[[File:GAWupdate_small.png|class=img-responsive center-block|link=Georgia At War]]
</div>
</div>

===Learn to Fly===
Welcome to Hoggit's DCS: World Wiki! We're a noob-friendly SeriousFaceTM multiplayer and singleplayer flight simulation community based on Reddit. This Wiki is meant to be a resource for anyone looking for information on the simulations we primarily play, DCS: World and Falcon BMS. We're gathering and organizing all the information related to the games, their peripherals, their quirks, and their tweaks/mods into this central repository in hopes that the World community will find it a valuable "one-stop shop" resource for everything you'd want to know.

[[Frequently Asked Questions]]

[https://www.youtube.com/watch?v=apvriPLtiZA&list=UUHa9LMylydkT0T3qSzAVrlw&feature=c4-overview What is DCS World?]

[[Simulator Scripting Engine Documentation|Looking for MIST/Scripting Documentation?]]

<div class="row">
<div class="col-sm-12">
[https://discord.gg/hoggit <span class="btn btn-lg btn-primary btn-block" href="#" role="button"><img src="images/b/bb/Discord_main.jpg" /> Join the Discord!</span>]
</div>

<div class="col-sm-12">
[[Tuesday Night Noob|<span class="btn btn-lg btn-primary btn-block" href="#" role="button"><img src="images/b/bb/Discord_main.jpg" />Looking to ease your way into multiplayer? Join Tuesday Night Noob!</span>]]
</div>

<div class="col-sm-12">
Hoggit was created as a laid back place for flight simmers of all skill levels to get together and fly online all while learning the modules of DCS World. Multiplayer DCS World groups tend to be very strict and regimented so we wanted to create a niche where people could casually come together and focus on having a good time. A great place to start is our Discord, where you'll find a community of sim pilots who are always willing to lend a hand to a new player, or just talk about sims in general.
</div>
</div>

<center>{{#widget:AdSense
|name=Hoggitwiki header
|width = 728px
|height = 90px
}}</center>

== DCS World Modules ==

<div class="row">
<div class="col-md-4" style="margin-bottom: 3rem; border-right: thin solid #f1f1f1">
====Fighter/Multirole====
<div class="row text-center">
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:F-A-18C-icon.png|link=F/A-18C]]</p>

[[F/A-18C]]
</div>

<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:M2000-icon.png|link=Mirage 2000C]]</p>

[[Mirage 2000C|M-2000C]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:F5.png|link=F-5E Tiger II]]</p>

[[F-5E Tiger II]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:Mig21.png|link=Mig-21bis]]</p>

[[Mig-21bis]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:F86f.png|link=F-86F Sabre]]</p>

[[F-86F Sabre]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:Mig15.png|link=Mig-15bis]]</p>

[[Mig-15bis]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:Fc3.png|link=Flaming Cliffs]]</p>

[[Flaming Cliffs]]
</div>
</div>
</div>
<div class="col-md-4" style="margin-bottom: 3rem; border-right: thin solid #f1f1f1">
====Attack====
<div class="row text-center">
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:A10C-icon.png|link=A-10C]]</p>

[[A-10C]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:av8b.png|link=AV-8B(NA)]]</p>

[[AV-8B(NA)]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:ajs37.png|link=AJS-37]]</p>

[[AJS-37]]
</div>
</div>
<div class="row text-center">
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:Su25t.png|link=Su-25T]]</p>

[[Su-25T]]
</div>
<div class="col-sm-4">

</div>
<div class="col-sm-4">

</div>
</div>
</div>
<div class="col-md-4" style="margin-bottom: 3rem;">
====Rotorcraft====
<div class="row text-center">
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:ka52.png|link=Ka-50]]</p>

[[Ka-50]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:uh1h.png|link=UH-1H]]</p>

[[UH-1H]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:mi8.png|link=Mi-8]]</p>

[[Mi-8]]
</div>
</div>
<div class="row text-center">
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:sa342.png|link=SA342]]</p>

[[SA342]]
</div>
<div class="col-sm-4">

</div>
<div class="col-sm-4">

</div>
</div>
</div>
</div>
<div class="row">
<div class="col-md-4" style="margin-bottom: 3rem; border-right: thin solid #f1f1f1">

====World War 2====
<div class="row text-center">
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:p51.png|link=P-51D]]</p>

[[P-51D]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:bf109.png|link=Bf 109 K-4]]</p>

[[Bf 109 K-4]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:spitfire.png|link=Spitfire Mk. IX]]</p>

[[Spitfire Mk. IX]]
</div>
</div>
<div class="row text-center">
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:fw190.png|link=Fw 190 D-9]]</p>

[[Fw 190 D-9]]
</div>
<div class="col-sm-4">

</div>
<div class="col-sm-4">

</div>
</div>
</div>
<div class="col-md-4" style="margin-bottom: 3rem; border-right: thin solid #f1f1f1">
====Trainers====
<div class="row text-center">
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:l39.png|link=L-39]]</p>

[[L-39]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:c101.png|link=C-101]]</p>

[[C-101]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:hawk.png|link=Hawk T.1A]]</p>

[[Hawk T.1A]]
</div>
</div>
<div class="row text-center">
<div class="col-sm-4">

</div>
<div class="col-sm-4">

</div>
<div class="col-sm-4">

</div>
</div>
</div>

<div class="col-md-4" style="margin-bottom: 3rem;">
====Tools & Utilities====
<div class="row text-center">
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:Srs.png|link=Simple Radio Standalone]]</p>

[[Simple Radio Standalone]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:LotATC.png|link=LotATC]]</p>

[[LotATC]]
</div>
<div class="col-sm-4">

<p style="margin-bottom: 0">[[File:Tacview.png|link=Tacview]]</p>

[[Tacview]]
</div>

<div class="col-sm-4">

<p style="margin-bottom: 0">[[File:Combatflite_logo_abbreviated.png|100px|link=CombatFlite]]</p>

[[CombatFlite]]
</div>

<div class="col-sm-4">

<p style="margin-bottom: 0">[[File:Voice_attack.png|80px|link=Voice Attack]]</p>

[[Voice Attack]]
</div>

<div class="col-sm-4">

<p style="margin-bottom: 0">[[File:OVGME_Logo.PNG|170px|link=OVGME]]</p>

[[OVGME]]
</div>

</div>
</div>

==Non-DCS World Sims==
<div class="row">
<div class="col-sm-4">
<p style="margin-bottom: 0;">[[File:Bms.png|86px|link=Falcon BMS]]</p>
[[Falcon BMS]]
</div>
</div>

<center>{{#widget:AdSense
|name=Hoggitwiki header
|client=ca-pub-6997190595986605
|slot=7221930773
|width = 728px
|height = 90px
}}</center>

== Technique Guides & Resources ==
<div class="row">
<div class="col-md-6">
[[Basic Airmanship|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Basic Airmanship</span>]]
</div>
<div class="col-md-6">
[[Air-to-Air_Combat|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Air-to-Air Combat</span>]]
</div>
</div>
<div class="row">
<div class="col-md-6">
[[Threat Database|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Threat Database</span>]]
</div>
<div class="col-md-6">
[[Air-to-Ground_Combat|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Air-to-Ground Combat</span>]]
</div>
<div class="col-md-6">
[[Charts and Checklists|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Brevity (Jargon), Charts and Checklists</span>]]
</div>
<div class="col-md-6">
[[Carrier Air Operations|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Carrier Air Operations</span>]]
</div>
</div>
<div class="row">
<div class="col-md-6">
[[Getting started with GCI/AWACS|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Getting started with GCI/AWACS</span>]]
</div>
</div>
<div class="row">
<div class="col-md-6">
[[ATC and Airfield Communications|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">ATC and Airfield Communications</span>]]
</div>
</div>



== Multiplayer Guides ==
<div class="row">
<div class="col-md-6">
[[Getting Started With Multiplayer|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Getting Started With Multiplayer</span>]]
</div>
<div class="col-md-6">
[[Simple Radio Standalone|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Multiplayer Comms</span>]]
</div>
</div>
<div class="row">
<div class="col-md-6">
[[Running a Server|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Running a Server</span>]]
</div>
</div>

== Setup Guides ==
<div class="row">
<div class="col-md-6">
[[Peripherals Guide|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Peripherals Guide</span>]]
</div>
<div class="col-md-6">
[[Joystick Profiles|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Joystick Profiles</span>]]
</div>
</div>
<div class="row">
<div class="col-md-6">
[[Headtracking Guides|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Headtracking Guides</span>]]
</div>
<div class="col-md-6">
[[Cockpit Views|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Cockpit Views</span>]]
</div>
<div class="col-md-6">
[[Exporting MFCD Displays|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Exporting MFCD Displays</span>]]
</div>
</div>

== Mission Making Resources ==
<div class="row">
<div class="col-md-6">
[[Simulator_Scripting_Engine_Documentation|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Simulator Scripting Engine Documentation</span>]]
</div>
<div class="col-md-6">
[[Mission Scripting Tools Documentation|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Mission Scripting Tools Documentation</span>]]
</div>
</div>
<div class="row">
<div class="col-md-6">
[[DCS_mission_editor|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Mission Editor Documentation</span>]]
</div>
<div class="col-md-6">
[[DCS_mission_editor_tools_mods|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Editor Tools and Mods</span>]]
</div>
</div>

== Modding ==
<div class="row">
<div class="col-md-6">
[[Modding_Basics|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Getting Started</span>]]
</div>

<div class="col-md-6">
[[DCS_export|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Export</span>]]
</div>
</div>
<div class="row">
<div class="col-md-6">
[[DCS_server_gameGUI|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">DCS Server Control Documentation</span>]]
</div>
<div class="col-md-6">
[[DCS_liveries|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Liveries</span>]]
</div>
</div>

== Other Links ==
<div class="row">
<div class="col-md-6">
[https://www.reddit.com/r/hoggit <span class="btn btn-lg btn-primary btn-block" href="#" role="button">Hoggit on Reddit</span>]
</div>
<div class="col-md-6">
[https://forums.eagle.ru <span class="btn btn-lg btn-primary btn-block" href="#" role="button">Eagle Dynamics Forums</span>]
</div>
</div>

== Current Prices on Recommended Gear==
<div class="row">

<div class="col-sm-4 col-lg-2">
{{#iDisplay://ws-na.amazon-adsystem.com/widgets/q?ServiceVersion=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&source=ac&ref=tf_til&ad_type=product_link&tracking_id=hoggitworld-20&marketplace=amazon&region=US&placement=B004I5XB4K&asins=B004I5XB4K&linkId=839983d8016d022c4e361d068dcedd5e&show_border=true&link_opens_in_new_window=true&price_color=333333&title_color=0066c0&bg_color=ffffff|200|280}}</div>

<div class="col-sm-4 col-lg-2">
{{#iDisplay://ws-na.amazon-adsystem.com/widgets/q?ServiceVersion=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&source=ac&ref=tf_til&ad_type=product_link&tracking_id=hoggitworld-20&marketplace=amazon&region=US&placement=B01LY285ZH&asins=B01LY285ZH&linkId=0f1fe6cb2b72e84f9187d474626d1d93&show_border=true&link_opens_in_new_window=true&price_color=333333&title_color=0066c0&bg_color=ffffff|200|280}}</div>

<div class="col-sm-4 col-lg-2">
{{#iDisplay://ws-na.amazon-adsystem.com/widgets/q?ServiceVersion=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&source=ac&ref=tf_til&ad_type=product_link&tracking_id=hoggitworld-20&marketplace=amazon&region=US&placement=B0029M6VKA&asins=B0029M6VKA&linkId=0f3882a4ce7cc8e7c03973917133f9d2&show_border=true&link_opens_in_new_window=true&price_color=333333&title_color=0066c0&bg_color=ffffff|200|280}}</div>

<div class="col-sm-4 col-lg-2">
{{#iDisplay://ws-na.amazon-adsystem.com/widgets/q?ServiceVersion=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&source=ss&ref=as_ss_li_til&ad_type=product_link&tracking_id=hoggitworld-20&marketplace=amazon&region=US&placement=B01LX398IE&asins=B01LX398IE&linkId=60ad1f8062e080986ecea05098ed8a21&show_border=true&link_opens_in_new_window=true|200|280}}</div>

<div class="col-sm-4 col-lg-2">
{{#iDisplay://ws-na.amazon-adsystem.com/widgets/q?ServiceVersion=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&source=ac&ref=tf_til&ad_type=product_link&tracking_id=hoggitworld-20&marketplace=amazon&region=US&placement=B005CMOV06&asins=B005CMOV06&linkId=3696e75c77379f2aab8dc914c2de19a6&show_border=true&link_opens_in_new_window=true&price_color=333333&title_color=0066c0&bg_color=ffffff|200|280}}</div>

<div class="col-sm-4 col-lg-2">
{{#iDisplay://ws-na.amazon-adsystem.com/widgets/q?ServiceVersion=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&source=ac&ref=tf_til&ad_type=product_link&tracking_id=hoggitworld-20&marketplace=amazon&region=US&placement=B0000512IE&asins=B0000512IE&linkId=c0fc561a2ac5effe5ca2540e14a2f9af&show_border=true&link_opens_in_new_window=true&price_color=333333&title_color=0066c0&bg_color=ffffff|200|280}}</div>
</div>
<div class="row">If nothing appears here, Amazon links are removed by AdBlock. Consider whitelisting our wiki in your ad blocker! We use the money for things like giveaways, contests, and funding our dedicated server.

Check out the [[Peripherals Guide]] for more information.</div>

Hoggit DCS World Wiki

2019-01-11T15:13:58Z

Blackbird: /* Technique Guides & Resources */

<div class="row">
<div class="col-sm-12 hidden-xs">
[[File:Toc.png|class=img-responsive center-block|link=Hoggit DCS World Wiki]]
</div>
<div class="col-sm-12 hidden-sm hidden-md hidden-lg">
[[File:Toc_small.png|class=img-responsive center-block|link=Hoggit DCS World Wiki]]
</div>
<div class="col-sm-12 hidden-xs">
[[File:GAWupdate.png|class=img-responsive center-block|link=Georgia At War]]
</div>
<div class="col-sm-12 hidden-sm hidden-md hidden-lg">
[[File:GAWupdate_small.png|class=img-responsive center-block|link=Georgia At War]]
</div>
</div>

===Learn to Fly===
Welcome to Hoggit's DCS: World Wiki! We're a noob-friendly SeriousFaceTM multiplayer and singleplayer flight simulation community based on Reddit. This Wiki is meant to be a resource for anyone looking for information on the simulations we primarily play, DCS: World and Falcon BMS. We're gathering and organizing all the information related to the games, their peripherals, their quirks, and their tweaks/mods into this central repository in hopes that the World community will find it a valuable "one-stop shop" resource for everything you'd want to know.

[[Frequently Asked Questions]]

[https://www.youtube.com/watch?v=apvriPLtiZA&list=UUHa9LMylydkT0T3qSzAVrlw&feature=c4-overview What is DCS World?]

[[Simulator Scripting Engine Documentation|Looking for MIST/Scripting Documentation?]]

<div class="row">
<div class="col-sm-12">
[https://discord.gg/hoggit <span class="btn btn-lg btn-primary btn-block" href="#" role="button"><img src="images/b/bb/Discord_main.jpg" /> Join the Discord!</span>]
</div>

<div class="col-sm-12">
[[Tuesday Night Noob|<span class="btn btn-lg btn-primary btn-block" href="#" role="button"><img src="images/b/bb/Discord_main.jpg" />Looking to ease your way into multiplayer? Join Tuesday Night Noob!</span>]]
</div>

<div class="col-sm-12">
Hoggit was created as a laid back place for flight simmers of all skill levels to get together and fly online all while learning the modules of DCS World. Multiplayer DCS World groups tend to be very strict and regimented so we wanted to create a niche where people could casually come together and focus on having a good time. A great place to start is our Discord, where you'll find a community of sim pilots who are always willing to lend a hand to a new player, or just talk about sims in general.
</div>
</div>

<center>{{#widget:AdSense
|name=Hoggitwiki header
|width = 728px
|height = 90px
}}</center>

== DCS World Modules ==

<div class="row">
<div class="col-md-4" style="margin-bottom: 3rem; border-right: thin solid #f1f1f1">
====Fighter/Multirole====
<div class="row text-center">
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:F-A-18C-icon.png|link=F/A-18C]]</p>

[[F/A-18C]]
</div>

<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:M2000-icon.png|link=Mirage 2000C]]</p>

[[Mirage 2000C|M-2000C]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:F5.png|link=F-5E Tiger II]]</p>

[[F-5E Tiger II]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:Mig21.png|link=Mig-21bis]]</p>

[[Mig-21bis]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:F86f.png|link=F-86F Sabre]]</p>

[[F-86F Sabre]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:Mig15.png|link=Mig-15bis]]</p>

[[Mig-15bis]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:Fc3.png|link=Flaming Cliffs]]</p>

[[Flaming Cliffs]]
</div>
</div>
</div>
<div class="col-md-4" style="margin-bottom: 3rem; border-right: thin solid #f1f1f1">
====Attack====
<div class="row text-center">
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:A10C-icon.png|link=A-10C]]</p>

[[A-10C]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:av8b.png|link=AV-8B(NA)]]</p>

[[AV-8B(NA)]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:ajs37.png|link=AJS-37]]</p>

[[AJS-37]]
</div>
</div>
<div class="row text-center">
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:Su25t.png|link=Su-25T]]</p>

[[Su-25T]]
</div>
<div class="col-sm-4">

</div>
<div class="col-sm-4">

</div>
</div>
</div>
<div class="col-md-4" style="margin-bottom: 3rem;">
====Rotorcraft====
<div class="row text-center">
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:ka52.png|link=Ka-50]]</p>

[[Ka-50]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:uh1h.png|link=UH-1H]]</p>

[[UH-1H]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:mi8.png|link=Mi-8]]</p>

[[Mi-8]]
</div>
</div>
<div class="row text-center">
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:sa342.png|link=SA342]]</p>

[[SA342]]
</div>
<div class="col-sm-4">

</div>
<div class="col-sm-4">

</div>
</div>
</div>
</div>
<div class="row">
<div class="col-md-4" style="margin-bottom: 3rem; border-right: thin solid #f1f1f1">

====World War 2====
<div class="row text-center">
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:p51.png|link=P-51D]]</p>

[[P-51D]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:bf109.png|link=Bf 109 K-4]]</p>

[[Bf 109 K-4]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:spitfire.png|link=Spitfire Mk. IX]]</p>

[[Spitfire Mk. IX]]
</div>
</div>
<div class="row text-center">
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:fw190.png|link=Fw 190 D-9]]</p>

[[Fw 190 D-9]]
</div>
<div class="col-sm-4">

</div>
<div class="col-sm-4">

</div>
</div>
</div>
<div class="col-md-4" style="margin-bottom: 3rem; border-right: thin solid #f1f1f1">
====Trainers====
<div class="row text-center">
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:l39.png|link=L-39]]</p>

[[L-39]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:c101.png|link=C-101]]</p>

[[C-101]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:hawk.png|link=Hawk T.1A]]</p>

[[Hawk T.1A]]
</div>
</div>
<div class="row text-center">
<div class="col-sm-4">

</div>
<div class="col-sm-4">

</div>
<div class="col-sm-4">

</div>
</div>
</div>

<div class="col-md-4" style="margin-bottom: 3rem;">
====Tools & Utilities====
<div class="row text-center">
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:Srs.png|link=Simple Radio Standalone]]</p>

[[Simple Radio Standalone]]
</div>
<div class="col-sm-4">
<p style="margin-bottom: 0">[[File:LotATC.png|link=LotATC]]</p>

[[LotATC]]
</div>
<div class="col-sm-4">

<p style="margin-bottom: 0">[[File:Tacview.png|link=Tacview]]</p>

[[Tacview]]
</div>

<div class="col-sm-4">

<p style="margin-bottom: 0">[[File:Combatflite_logo_abbreviated.png|100px|link=CombatFlite]]</p>

[[CombatFlite]]
</div>

<div class="col-sm-4">

<p style="margin-bottom: 0">[[File:Voice_attack.png|80px|link=Voice Attack]]</p>

[[Voice Attack]]
</div>

<div class="col-sm-4">

<p style="margin-bottom: 0">[[File:OVGME_Logo.PNG|170px|link=OVGME]]</p>

[[OVGME]]
</div>

</div>
</div>

==Non-DCS World Sims==
<div class="row">
<div class="col-sm-4">
<p style="margin-bottom: 0;">[[File:Bms.png|86px|link=Falcon BMS]]</p>
[[Falcon BMS]]
</div>
</div>

<center>{{#widget:AdSense
|name=Hoggitwiki header
|client=ca-pub-6997190595986605
|slot=7221930773
|width = 728px
|height = 90px
}}</center>

== Technique Guides & Resources ==
<div class="row">
<div class="col-md-6">
[[Basic Airmanship|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Basic Airmanship</span>]]
</div>
<div class="col-md-6">
[[Air-to-Air_Combat|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Air-to-Air Combat</span>]]
</div>
</div>
<div class="row">
<div class="col-md-6">
[[Threat Database|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Threat Database</span>]]
</div>
<div class="col-md-6">
[[Air-to-Ground_Combat|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Air-to-Ground Combat</span>]]
</div>
<div class="col-md-6">
[[Charts and Checklists|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Brevity (Jargon), Charts and Checklists</span>]]
</div>
<div class="col-md-6">
[[Carrier Air Operations|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Carrier Air Operations</span>]]
</div>
</div>
<div class="row">
<div class="col-md-6">
[[Getting started with GCI/AWACS|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Getting started with GCI/AWACS</span>]]
</div>
</div>
<div class="row">
<div class="col-md-6">
[[Getting started with GCI/AWACS|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">ATC and Airfield Communications</span>]]
</div>
</div>



== Multiplayer Guides ==
<div class="row">
<div class="col-md-6">
[[Getting Started With Multiplayer|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Getting Started With Multiplayer</span>]]
</div>
<div class="col-md-6">
[[Simple Radio Standalone|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Multiplayer Comms</span>]]
</div>
</div>
<div class="row">
<div class="col-md-6">
[[Running a Server|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Running a Server</span>]]
</div>
</div>

== Setup Guides ==
<div class="row">
<div class="col-md-6">
[[Peripherals Guide|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Peripherals Guide</span>]]
</div>
<div class="col-md-6">
[[Joystick Profiles|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Joystick Profiles</span>]]
</div>
</div>
<div class="row">
<div class="col-md-6">
[[Headtracking Guides|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Headtracking Guides</span>]]
</div>
<div class="col-md-6">
[[Cockpit Views|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Cockpit Views</span>]]
</div>
<div class="col-md-6">
[[Exporting MFCD Displays|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Exporting MFCD Displays</span>]]
</div>
</div>

== Mission Making Resources ==
<div class="row">
<div class="col-md-6">
[[Simulator_Scripting_Engine_Documentation|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Simulator Scripting Engine Documentation</span>]]
</div>
<div class="col-md-6">
[[Mission Scripting Tools Documentation|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Mission Scripting Tools Documentation</span>]]
</div>
</div>
<div class="row">
<div class="col-md-6">
[[DCS_mission_editor|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Mission Editor Documentation</span>]]
</div>
<div class="col-md-6">
[[DCS_mission_editor_tools_mods|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Editor Tools and Mods</span>]]
</div>
</div>

== Modding ==
<div class="row">
<div class="col-md-6">
[[Modding_Basics|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Getting Started</span>]]
</div>

<div class="col-md-6">
[[DCS_export|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Export</span>]]
</div>
</div>
<div class="row">
<div class="col-md-6">
[[DCS_server_gameGUI|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">DCS Server Control Documentation</span>]]
</div>
<div class="col-md-6">
[[DCS_liveries|
<span class="btn btn-lg btn-primary btn-block" href="#" role="button">Liveries</span>]]
</div>
</div>

== Other Links ==
<div class="row">
<div class="col-md-6">
[https://www.reddit.com/r/hoggit <span class="btn btn-lg btn-primary btn-block" href="#" role="button">Hoggit on Reddit</span>]
</div>
<div class="col-md-6">
[https://forums.eagle.ru <span class="btn btn-lg btn-primary btn-block" href="#" role="button">Eagle Dynamics Forums</span>]
</div>
</div>

== Current Prices on Recommended Gear==
<div class="row">

<div class="col-sm-4 col-lg-2">
{{#iDisplay://ws-na.amazon-adsystem.com/widgets/q?ServiceVersion=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&source=ac&ref=tf_til&ad_type=product_link&tracking_id=hoggitworld-20&marketplace=amazon&region=US&placement=B004I5XB4K&asins=B004I5XB4K&linkId=839983d8016d022c4e361d068dcedd5e&show_border=true&link_opens_in_new_window=true&price_color=333333&title_color=0066c0&bg_color=ffffff|200|280}}</div>

<div class="col-sm-4 col-lg-2">
{{#iDisplay://ws-na.amazon-adsystem.com/widgets/q?ServiceVersion=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&source=ac&ref=tf_til&ad_type=product_link&tracking_id=hoggitworld-20&marketplace=amazon&region=US&placement=B01LY285ZH&asins=B01LY285ZH&linkId=0f1fe6cb2b72e84f9187d474626d1d93&show_border=true&link_opens_in_new_window=true&price_color=333333&title_color=0066c0&bg_color=ffffff|200|280}}</div>

<div class="col-sm-4 col-lg-2">
{{#iDisplay://ws-na.amazon-adsystem.com/widgets/q?ServiceVersion=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&source=ac&ref=tf_til&ad_type=product_link&tracking_id=hoggitworld-20&marketplace=amazon&region=US&placement=B0029M6VKA&asins=B0029M6VKA&linkId=0f3882a4ce7cc8e7c03973917133f9d2&show_border=true&link_opens_in_new_window=true&price_color=333333&title_color=0066c0&bg_color=ffffff|200|280}}</div>

<div class="col-sm-4 col-lg-2">
{{#iDisplay://ws-na.amazon-adsystem.com/widgets/q?ServiceVersion=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&source=ss&ref=as_ss_li_til&ad_type=product_link&tracking_id=hoggitworld-20&marketplace=amazon&region=US&placement=B01LX398IE&asins=B01LX398IE&linkId=60ad1f8062e080986ecea05098ed8a21&show_border=true&link_opens_in_new_window=true|200|280}}</div>

<div class="col-sm-4 col-lg-2">
{{#iDisplay://ws-na.amazon-adsystem.com/widgets/q?ServiceVersion=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&source=ac&ref=tf_til&ad_type=product_link&tracking_id=hoggitworld-20&marketplace=amazon&region=US&placement=B005CMOV06&asins=B005CMOV06&linkId=3696e75c77379f2aab8dc914c2de19a6&show_border=true&link_opens_in_new_window=true&price_color=333333&title_color=0066c0&bg_color=ffffff|200|280}}</div>

<div class="col-sm-4 col-lg-2">
{{#iDisplay://ws-na.amazon-adsystem.com/widgets/q?ServiceVersion=20070822&OneJS=1&Operation=GetAdHtml&MarketPlace=US&source=ac&ref=tf_til&ad_type=product_link&tracking_id=hoggitworld-20&marketplace=amazon&region=US&placement=B0000512IE&asins=B0000512IE&linkId=c0fc561a2ac5effe5ca2540e14a2f9af&show_border=true&link_opens_in_new_window=true&price_color=333333&title_color=0066c0&bg_color=ffffff|200|280}}</div>
</div>
<div class="row">If nothing appears here, Amazon links are removed by AdBlock. Consider whitelisting our wiki in your ad blocker! We use the money for things like giveaways, contests, and funding our dedicated server.

Check out the [[Peripherals Guide]] for more information.</div>

Georgia At War

2018-09-05T13:43:39Z

Blackbird: /* Radios */

<center>{{#widget:AdSense
|name=Hoggitwiki header
|width = 728px
|height = 90px
}}</center>

__TOC__

==Georgia At War User Guide==

[https://www.youtube.com/watch?v=LGDcy3TEvIw What is Georgia At War? ]

Georgia At War is a dynamic campaign where players start with a small foothold in Russian territory near Ukraine, and must fight their way to Maykop. Players must clear and capture territory to create forward bases to keep the pressure up on the enemy and to keep their airfields supplied. You are pitted against an AI commander who will react to your actions, he'll counter attack territory you've captured, proactively capture territory you aren't guarding, and in general do his best to foil your efforts to extend your front line eastward.

===Key Concepts===
====The F10 Menu====
Almost all actions in GAW are done via the F10 menu. This can be used by opening the communication menu (the "\" key by default), and pressing F10 or using the mouse to select "Other".

====Capturing Territory====
The overall objective in GAW is to capture Maykop. However you won't be able to do that without stringing together smaller victories to expand your center of operations. This is important for 2 reasons. First, you have limited supplies at your base. There are warehouses in the theater that must be captured to ensure that you continue receiving weapons at your base. Second, having to fly back to your starting base to rearm and refuel after sorties will decrease the amount of time you are on station, giving the commander openings to retake territory.

Capturing territory (airfields, and FARPs) is done in one of two ways. First players must clear a path to the territory they intend to capture. The mission is different every time so depending on how the commander chose to deploy his forces this may include removing SAM threats, AAA, mechanized infantry, enemy aircraft, or any number of other enemy units that might be covering the territory.

Once a path has been cleared you have two options. The F10 menu can be used to "Deploy airfield security forces" or "Deploy Warehouse/FARP security forces" to deploy a C-130 or a Blackhawk helicopter to the selected airfield. If they successfully arrive, they will deliver a small force of units to capture and hold the territory.

The second option is that players can use the included CTLD scripts to load up a helicopter with troops and vehicles to capture the airfield themselves. Once friendly ground units are in the vicinity of an airfield or FARP and there is no enemy presence, the airfield will be captured.

<center>{{#widget:AdSense
|name=Hoggitwiki header
|width = 728px
|height = 90px
}}</center>

====Completing Missions====
The enemy commander will have many battlefield assets deployed to support his efforts to hold you off. You'll need to soften these assets up to support your push toward Maykop. To see a list of all the available missions, use the F10 menu and select "Get Current Missions". Missions are categorized by type.

'''SEAD'''

SEAD missions involve destroying strategic SAM sites that are deployed across the theater. These missions are critical as these large SAM sites are capable of denying large areas of the map to the players. Completing these missions will allow the blue coalition deeper access into the theater. [https://www.youtube.com/watch?v=wmRbcDTTi6w Su-25T SEAD Guide]

'''Air Interdiction'''

Battlefield Air Interdiction missions involve attacking assets against mobile ground units like armor columns, artillery, or mechanized infantry. These units are very dangerous to both units on the ground holding territory, and low flying vehicles like helicopters that are needed to deliver troops and vehicles to fortify your front line.

'''Strike'''

Strikes are attacks against hardened targets like power plants and ammo dumps. Strikes are necessary to complete the mission, and can have effects on the battle like friendly AI bombing runs or fighter sweeps (these are coming soon). Destroying the MOBILE CPs listed here will greatly degrade the AI commander's ability to call in airborne reinforcements.

'''Naval'''

Naval strikes are similar to strikes except they obviously take place in the open water. Completing these will call in AI friendly units to help with the fight (coming soon), and depending on how the commander has deployed his naval assets clearing these may be necessary to open up deeper areas of the theater.

'''Intercepts'''

These are for air-to-air missions to destroy enemy airborne assets like tankers and AWACS to deny the enemy use of those resources.

<center>{{#widget:AdSense
|name=Hoggitwiki header
|width = 728px
|height = 90px
}}</center>

====CAP====

There are numerous platforms available for players to use to provide CAP for their team. This is a constant need as the AI commander will continuously call in aircraft to stop you. What type of aircraft and how long it takes them to get to the battle is dependent on how many mobile CP's the commander has available. These CP's can be destroyed by the players, and are listed under "Strike" on the "Get Current Missions" menu.

====Logistics====

GAW uses CTLD so players in helicopters can ferry troops to airfields to capture them, or deploy units like SAMs to defend and fortify the front line.

The helicopters capable of performing logistics are the Huey and the Mi-8. These helicopters are available from the start at the Anapa area FARPs, and become available at new FARPS and airfields as they are captured. As you can imagine, this means that capturing territory is incredibly important as it allows you to quickly build fortifications on your front line to defend from enemy counter attacks, and gives both CAP and strike aircraft cushions to operate in free from harassment from enemy aircraft.

Anywhere that you see green smoke is a "logistics zone" where you can pick up troops, or spawn crates to build SAMs. These are always relatively close to the airfield where the spawn is located. As you capture airfields, you'll also unlock new logistics zones close to the airfields in question. The specifics of using CTLD are outside of the scope of this document, however it all uses the F10 menu under the "CTLD" section, and it is very self explanatory.

<center>{{#widget:AdSense
|name=Hoggitwiki header
|width = 728px
|height = 90px
}}</center>

====Friendly Assets====
GAW features a handful of support units controlled by AI that will help you complete the mission. These units are not invincible and the AI commander will occasionally call in strikes to attempt to destroy them! If they are killed, it will be some time before these assets respawn and become available again.

AWACS provides radar coverage and vectoring for bandits and friendly airbases.

There is a carrier operating in the Black Sea to facilitate naval aviation operations.

There is an LHD also operating in the Black Sea to facilitate VTOL aviation operations.

Passive CAP is occasionally called in to help fight back enemy aircraft for when there are few players online providing CAP

There are forward observer slots available so players can provide human AWACS/ATC

===Server Schedule and State Saving===

The state of the mission is saved every 10 minutes. In terms of objectives, you'll never lose more than 10 minutes worth of progress in the event of a crash.

The server is restarted every 4 hours, the state is saved, and is reloaded on restart.

Territory that is not captured is considered "reinforced" at this time, when the mission reloads all territory held by either blue or red will be fully reinforced with new defense units. It's critical to complete any territorial capture within the three hour window! Even if you destroy every single enemy unit at an airfield, if you don't capture before a restart the commander will reinforce it with a new
complement of defenders!

Players will be given warnings at 30, 20, and 5 minutes before server restart. Generally speaking the mission starts at 06:20 and restarts at 09:20. Occasionally we'll change up the time or weather to get a change of scenery.

Tuesday nights we'll be switching the server to Tuesday Night Noob, our training map to help new players ease their way into multiplayer and learn new skills. The mission will not run consistently on Tuesdays depending on turnout for TNN.

We will try to schedule updates for the mission and code during one of the three hour restarts. If we are making updates sometimes it will take a mission a little longer to come back up while we apply updates. In some extreme cases (e.g. the mission is bugged or the game executable is struggling) sometimes we might have to restart the mission outside of the three hour normal restarts. in this case we will make every effort to preserve the state and reload it, but it's not guaranteed.

==How to get Involved==
===Discord===
Join the [https://discord.gg/hoggit Hoggit Discord] and check out the #welcome and #georgia-at-war channels.
===Radios===
The server runs [[Simple_Radio_Standalone|Simple Radio]] at "dcs.hoggitworld.com". User Redditbus created a [https://docs.google.com/spreadsheets/d/1a63VD2WXmShIwpiTTfHuK-5yWKw-3AtXLbv1LBjMyCE/edit#gid=0 google doc] with the radio frequencies we're going to be using. The [https://docs.google.com/document/d/1SbtS7QpBqxN5KbSR8da2qYRCi9ogt4dz37JCfJPLLls/edit?usp=sharing ATC/Airfield Communications Guide] written by Blackbird contains procedures and brevity for Pilots departing from and arriving at Georgia At War airports.

==Video Guides==

===SEAD===
[https://www.youtube.com/watch?v=wmRbcDTTi6w Su-25T SEAD Guide]

==Current Status==
The current status of GAW can be tracked at http://gaw.hoggitworld.com/. Also, Hoggy, our Discord Bot, has the server's status available under his name in the discord.

Georgia At War

2018-09-05T13:34:49Z

Blackbird: /* Server Schedule and State Saving */

<center>{{#widget:AdSense
|name=Hoggitwiki header
|width = 728px
|height = 90px
}}</center>

__TOC__

==Georgia At War User Guide==

[https://www.youtube.com/watch?v=LGDcy3TEvIw What is Georgia At War? ]

Georgia At War is a dynamic campaign where players start with a small foothold in Russian territory near Ukraine, and must fight their way to Maykop. Players must clear and capture territory to create forward bases to keep the pressure up on the enemy and to keep their airfields supplied. You are pitted against an AI commander who will react to your actions, he'll counter attack territory you've captured, proactively capture territory you aren't guarding, and in general do his best to foil your efforts to extend your front line eastward.

===Key Concepts===
====The F10 Menu====
Almost all actions in GAW are done via the F10 menu. This can be used by opening the communication menu (the "\" key by default), and pressing F10 or using the mouse to select "Other".

====Capturing Territory====
The overall objective in GAW is to capture Maykop. However you won't be able to do that without stringing together smaller victories to expand your center of operations. This is important for 2 reasons. First, you have limited supplies at your base. There are warehouses in the theater that must be captured to ensure that you continue receiving weapons at your base. Second, having to fly back to your starting base to rearm and refuel after sorties will decrease the amount of time you are on station, giving the commander openings to retake territory.

Capturing territory (airfields, and FARPs) is done in one of two ways. First players must clear a path to the territory they intend to capture. The mission is different every time so depending on how the commander chose to deploy his forces this may include removing SAM threats, AAA, mechanized infantry, enemy aircraft, or any number of other enemy units that might be covering the territory.

Once a path has been cleared you have two options. The F10 menu can be used to "Deploy airfield security forces" or "Deploy Warehouse/FARP security forces" to deploy a C-130 or a Blackhawk helicopter to the selected airfield. If they successfully arrive, they will deliver a small force of units to capture and hold the territory.

The second option is that players can use the included CTLD scripts to load up a helicopter with troops and vehicles to capture the airfield themselves. Once friendly ground units are in the vicinity of an airfield or FARP and there is no enemy presence, the airfield will be captured.

<center>{{#widget:AdSense
|name=Hoggitwiki header
|width = 728px
|height = 90px
}}</center>

====Completing Missions====
The enemy commander will have many battlefield assets deployed to support his efforts to hold you off. You'll need to soften these assets up to support your push toward Maykop. To see a list of all the available missions, use the F10 menu and select "Get Current Missions". Missions are categorized by type.

'''SEAD'''

SEAD missions involve destroying strategic SAM sites that are deployed across the theater. These missions are critical as these large SAM sites are capable of denying large areas of the map to the players. Completing these missions will allow the blue coalition deeper access into the theater. [https://www.youtube.com/watch?v=wmRbcDTTi6w Su-25T SEAD Guide]

'''Air Interdiction'''

Battlefield Air Interdiction missions involve attacking assets against mobile ground units like armor columns, artillery, or mechanized infantry. These units are very dangerous to both units on the ground holding territory, and low flying vehicles like helicopters that are needed to deliver troops and vehicles to fortify your front line.

'''Strike'''

Strikes are attacks against hardened targets like power plants and ammo dumps. Strikes are necessary to complete the mission, and can have effects on the battle like friendly AI bombing runs or fighter sweeps (these are coming soon). Destroying the MOBILE CPs listed here will greatly degrade the AI commander's ability to call in airborne reinforcements.

'''Naval'''

Naval strikes are similar to strikes except they obviously take place in the open water. Completing these will call in AI friendly units to help with the fight (coming soon), and depending on how the commander has deployed his naval assets clearing these may be necessary to open up deeper areas of the theater.

'''Intercepts'''

These are for air-to-air missions to destroy enemy airborne assets like tankers and AWACS to deny the enemy use of those resources.

<center>{{#widget:AdSense
|name=Hoggitwiki header
|width = 728px
|height = 90px
}}</center>

====CAP====

There are numerous platforms available for players to use to provide CAP for their team. This is a constant need as the AI commander will continuously call in aircraft to stop you. What type of aircraft and how long it takes them to get to the battle is dependent on how many mobile CP's the commander has available. These CP's can be destroyed by the players, and are listed under "Strike" on the "Get Current Missions" menu.

====Logistics====

GAW uses CTLD so players in helicopters can ferry troops to airfields to capture them, or deploy units like SAMs to defend and fortify the front line.

The helicopters capable of performing logistics are the Huey and the Mi-8. These helicopters are available from the start at the Anapa area FARPs, and become available at new FARPS and airfields as they are captured. As you can imagine, this means that capturing territory is incredibly important as it allows you to quickly build fortifications on your front line to defend from enemy counter attacks, and gives both CAP and strike aircraft cushions to operate in free from harassment from enemy aircraft.

Anywhere that you see green smoke is a "logistics zone" where you can pick up troops, or spawn crates to build SAMs. These are always relatively close to the airfield where the spawn is located. As you capture airfields, you'll also unlock new logistics zones close to the airfields in question. The specifics of using CTLD are outside of the scope of this document, however it all uses the F10 menu under the "CTLD" section, and it is very self explanatory.

<center>{{#widget:AdSense
|name=Hoggitwiki header
|width = 728px
|height = 90px
}}</center>

====Friendly Assets====
GAW features a handful of support units controlled by AI that will help you complete the mission. These units are not invincible and the AI commander will occasionally call in strikes to attempt to destroy them! If they are killed, it will be some time before these assets respawn and become available again.

AWACS provides radar coverage and vectoring for bandits and friendly airbases.

There is a carrier operating in the Black Sea to facilitate naval aviation operations.

There is an LHD also operating in the Black Sea to facilitate VTOL aviation operations.

Passive CAP is occasionally called in to help fight back enemy aircraft for when there are few players online providing CAP

There are forward observer slots available so players can provide human AWACS/ATC

===Server Schedule and State Saving===

The state of the mission is saved every 10 minutes. In terms of objectives, you'll never lose more than 10 minutes worth of progress in the event of a crash.

The server is restarted every 4 hours, the state is saved, and is reloaded on restart.

Territory that is not captured is considered "reinforced" at this time, when the mission reloads all territory held by either blue or red will be fully reinforced with new defense units. It's critical to complete any territorial capture within the three hour window! Even if you destroy every single enemy unit at an airfield, if you don't capture before a restart the commander will reinforce it with a new
complement of defenders!

Players will be given warnings at 30, 20, and 5 minutes before server restart. Generally speaking the mission starts at 06:20 and restarts at 09:20. Occasionally we'll change up the time or weather to get a change of scenery.

Tuesday nights we'll be switching the server to Tuesday Night Noob, our training map to help new players ease their way into multiplayer and learn new skills. The mission will not run consistently on Tuesdays depending on turnout for TNN.

We will try to schedule updates for the mission and code during one of the three hour restarts. If we are making updates sometimes it will take a mission a little longer to come back up while we apply updates. In some extreme cases (e.g. the mission is bugged or the game executable is struggling) sometimes we might have to restart the mission outside of the three hour normal restarts. in this case we will make every effort to preserve the state and reload it, but it's not guaranteed.

==How to get Involved==
===Discord===
Join the [https://discord.gg/hoggit Hoggit Discord] and check out the #welcome and #georgia-at-war channels.
===Radios===
The server runs [[Simple_Radio_Standalone|Simple Radio]] at "dcs.hoggitworld.com". User Redditbus created a [https://docs.google.com/spreadsheets/d/1a63VD2WXmShIwpiTTfHuK-5yWKw-3AtXLbv1LBjMyCE/edit#gid=0 google doc] with the radio frequencies we're going to be using.

==Video Guides==

===SEAD===
[https://www.youtube.com/watch?v=wmRbcDTTi6w Su-25T SEAD Guide]

==Current Status==
The current status of GAW can be tracked at http://gaw.hoggitworld.com/. Also, Hoggy, our Discord Bot, has the server's status available under his name in the discord.