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

Carrier Air Operations

2022-12-26T23:39:48Z

Marlan: change case 1 marshal stack alt

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

[[File:AircraftCarrierNight.jpeg|350px|thumb|right|A home away from home for many naval aviators]]

Carrier air operations are the various procedures and techniques that make up landing on a moving ship, called an aircraft carrier: both STOL / STOVL (such as the Harrier and F-35B's) and fixed wing (F-14, F/A-18) can land on a carrier. Because of the relatively small size of aircraft carriers there are a number of rules and procedures that you should follow when on or around an aircraft carrier.

__TOC__

== Carrier Basics ==

Before we dive headfirst into the procedures and rules associated with carrier air operations, we will first go over the various basics that come into play when operating on a carrier. These include items such as how does a carrier work, what does a carrier look like, and what sort of key features should you pay attention to when you cannot make out left from right when operating on a busy carrier.

=== Carrier Features ===

Because of the limited length of an aircraft carrier some special equipment is used for launching (departure, taking off) and recovering (landing) aircraft. Whereas normally a runway would net you somewhere in the ballpark of 6000 - 12000 feet of usable space, having a total length of 1100 feet is already quite spacious for an aircraft carrier. There are various types of key equipment used on a carrier:

; 1. Arresting gear
: Used to slow down / landing aircraft (recoveries)
; 2. Catapults
: Used to speed up / launch aircraft
; 3. Launch ramp
: Used to launch aircraft
; 4. IFLOLS
: Used to guide aircraft into landing (recoveries)

----

==== Ski ramps (STOBAR) ====

[[File:SU-33_Carrier_Takeoff.gif|thumb|right|[https://www.youtube.com/watch?v=Uox9S6UccEE| Su-33 taking on from ski carrier ramp]]]

Most modern aircraft tend to be quite heavy (due to radar / sensor electronics, as well as heavy jet engines) and as such they cannot simply run off the edge of the ship at full speed to get into the air (though this was common practice for the lighter World War 2 aircraft). Instead, you could use a ramp and a high power aircraft (with very little weight).

[[File:Su33ramp.jpg|thumb|right|200px||Ski ramp on a Russian carrier]]

The procedure of using a ramp to launch aircraft is called [https://en.wikipedia.org/wiki/STOBAR| '''STOBAR''' ( Short Take-Off But Arrested Recovery ) ] and is a simple (cost effective) manner of launching aircraft from a carrier. For this you only need a ramp (angled bit of deck) and you will need a high power to weight ratio (i.e. lot of power, little weight) on your aircraft to launch aircraft off of the carrier.

Launching via STOBAR is done by lining the aircraft up to go off the ramp, go full thrust and launch by running off of it. Removable wheel chocks are used to hold the aircraft in place whilst you run up to full power (in the designated spots): the JBD (Jet Blast Deflector, a big piece of metal behind the plane that can be raised) is used to prevent the exhaust from the airplane preparing to take-off from blowing away other aircraft lined up behind it.

Jets take a few seconds to spool up to full power (i.e. no full thrust from the get go), so the use of these chocks is pretty vital. On some (Russian) aircraft a thrust override (carrier takeoff) switch can be set to provide even more engine power, to be used when an aircraft is heavily loaded or in bad weather conditions.

The drawbacks of using STOBAR is that you get to bring less overall weight, so less weapons and fuel to maintain the amount of power versus weight (also called the thrust vs. weight) ratio to be able to safely launch (although you will typically top up on fuel after launching from any carrier). Also, because the ramp takes up valuable space on the carrier (you can't park aircraft on the ramp), you can typically bring less planes aboard and you will not be able to launch as many planes from a STOBAR carrier (as they all have to use the same ramp to launch).

----

==== Catapults (CATOBAR) ====

[[File:F18_Carrier_Takeoff.gif|thumb|right|[https://www.youtube.com/watch?v=ZzVW9315ur0| F/A-18C taking off using the catapult]]]

Rather than implement the STOBAR ramp system, the United States (whom pioneered the system) and most NATO countries instead use the [https://en.wikipedia.org/wiki/CATOBAR| '''CATOBAR''' (Catapult Assisted Take-Off But Arrested Recovery ] system. The aircraft catapult is a launcher to which an aircraft is hooked up, which is then launched using external power from the carrier (either steam or electromagnetic power).

Up to the Cold War most aircraft used a length of reinforced rope (called a bridle) to attach to the catapult shuttle, but in all aircraft after the Cold War the shuttle instead connects to the nose gear of the aircraft via the launch bar. The pilot can selectively lower the launch bar with a switch in the cockpit to hook up to the catapult (shuttle). This shuttle also holds back the aircraft, so that the engines can be run up to full (afterburning) mode before launching. The catapult is then set to the appropriate amount of power and the aircraft can be subsequently launched.

Although more expensive (maintenance costs) to operate than the comparative ramp system, the catapult system allows you more flexibility in operating it: you can increase the amount of power on the catapult for heavier aircraft (more fuel/ordinance), as well as being able to hookup and launch multiple aircraft in quick succession by using multiple catapults.

----

==== Arresting gear ====

[[File:F18_Carrier_Landing.gif|thumb|right|[https://www.youtube.com/watch?v=I3fm4HwVdE8| F/A-18C landing with arrestor wires]]]

To allow aircraft to land in a much smaller space, a number of wires (typically 4 or 5) are strung across the landing deck. The aircraft catches one of these '''arresting wires''' with the use of the hook built into the airframe, after which the aircraft slows down rapidly (though quite harshly). Obviously aircraft such as helicopters and STOL/STOVL (such as the Harrier or F-35) do not need these arresting wires, as they can simply land (semi) vertically.

Because of the limited length of the landing area and the harsh landing, the aircraft used for landing on a carrier (carrier aircraft) also have very robust landing gear to withstand the high rate of descend. In a way, landing on an aircraft carrier is more controlled crashing than actual landing.

To allow aircraft carriers to launch and recover aircraft at the same time, the landing deck often has an offset: this means the landing deck is at an angle compared to the rest of the ship (typically at 9 degrees). Typically you will visually adjust for this offset (respective of the carrier course) in your landing procedure, but during nighttime or bad visibility you will be given a different heading to adjust for this offset automatically.

----

==== IFLOLS ====

[[File:IFLOLS diagram.png|thumb|right|[https://en.wikipedia.org/wiki/Optical_landing_system#Improved_fresnel_lens_optical_landing_system_(IFLOLS)| IFLOLS]]]

The [https://en.wikipedia.org/wiki/Optical_landing_system#Improved_fresnel_lens_optical_landing_system_(IFLOLS)| IFLOLS (Improved Fresnel Optical Landing System)] is a system used on carriers to guide aircraft into the correct landing approach ('line-up'). Aside from extreme weather conditions or nighttime (both leading to limited visibility) landings, you will use this system to correctly line yourself up so that you may make a successful landing first time round.

The LSO (Landing Signal Officer) are in charge of operating these lights and will guide you on landing the aircraft, as well as grading the landing attempt afterwards. Please see the appropriate chapter for further information on LSO Grading: you can use the foldout button below to show the IFLOLS names for the lights.

{| class="mw-collapsible mw-collapsed wikitable"
! colspan="3" style="text-align: center; background-color:#f8a102;" | | IFLOLS: Carrier Landing Lights |
|-
| style="text-align: center; background-color:#f8a102;" | #
| style="text-align: center; background-color:#f8a102;" | Name
| style="text-align: center; background-color:#f8a102;" | Function
|-
| 1
| Ladder /
Meatball
| On this vertical bar with yellow/red lights, the orange ball ('meatball') will move up and down
according to aircraft position. If the ball is too low, your aircraft is too low. If the ball is too high, your
aircraft is too high. The goal is to line it up with the datum lights (2) for optimal landing: should the orange
ball fall into red lights you are dangerously low and you will need to wave off (stop) the landing attempt.
|-
| style="background-color:#accf40;" | 2
| style="background-color:#accf40;" | Datum lights
| style="background-color:#accf40;" | These green horizontal bar of lights indicates your ideal line up: the goal is to have the orange ball ('meatball')
line up with the datum lights for ideal vertical landing position.
|-
| 3
| Cut lights
| On early approach the cut lights illuminate 2 ~ 3 seconds to indicate 'proceed with landing'. Any subsequent
illumination means 'add power', according to length of illumination of lights
|-
| style="background-color:#accf40;" | 4
| style="background-color:#accf40;" | Wave off lights
| style="background-color:#accf40;" | Should the landing fall outside safe parameters (for example you are way too low), the LSO will call 'Wave Off!'
and these lights will illuminate: you need to terminate the landing attempt and go around (climb away).
|-
| 5
| Emergency wave off lights
| Identical in function to normal Wave Off Lights (4): for really dense pilots.
|}

----

==== ACLS / ICLS ====

----

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

=== Carrier Deck Layout ===

Let's first familiarize ourselves with the overall carrier deck layout (topology). Unlike an airfield, where there is space aplenty, the carrier is quite cramped and often busy with other aircraft, so knowing where you are going (and not hindering others) is vital.

[[File:ACTUAL_CARRIER_TOPOLOGY.png|right|800px]]

All (modern) aircraft carriers more or less have the same layout: the figure here shows the diagram of the USS Nimitz class carriers, but we could still apply the location names to all other carriers (including carriers such as the Russian Admiral Kuznetsov).

Objects such as parked aircraft or munition carts can be placed on the aircraft deck (by the mission developer): even if they are not moving ('static') they can till be collideable. So ensure your path and catapult '''are clear before moving''', before finding out on take-off that there is an aircraft parked on the catapult.

The most critical locations on an aircraft carrier are the '''catapults''' or ramp (marked in green and numbered), and the '''landing deck''' (between the red stripes, with yellow centerline). These are for respectively launching aircraft (taking off) and recovering aircraft (landing), so like a runway, '''do not block them'''. Typical recovery or departure intervals are approximately 20 to 30 seconds, so try to cross them quick if you have to and be wary of other aircraft.

{| class="mw-collapsible mw-collapsed wikitable"
! colspan="6" style="text-align: center; background-color:#f8a102;" | | Carrier Topology List |
|-
| style="background-color:#f8a102;" | #
| style="background-color:#f8a102;" | Name
| style="background-color:#f8a102;" | Location
| style="background-color:#f8a102;" | Colour
| style="background-color:#f8a102;" | Function
| style="background-color:#f8a102;" | Notes
|-
| 1
| Landing Deck
| Slanted along deck
| Between red lines,
with yellow centerline
| Landing aircraft
| Keep clear at all times
|-
| style="background-color:#accf40;" | 2
| style="background-color:#accf40;" | Catapults
| style="background-color:#accf40;" | Bow (front)
| style="background-color:#accf40;" | In green,
JBD in light blue
| style="background-color:#accf40;" | Launching aircraft
| style="background-color:#accf40;" | Be mindful about
parked aircraft
obstructing catapults
|-
| 3
| Island
| Starboard,
midways ship
| In purple
| Ship control,
aircraft control tower
| Waive to your Airboss
|-
| style="background-color:#accf40;" | 4
| style="background-color:#accf40;" | Elevators
| style="background-color:#accf40;" | Edge of ship
| style="background-color:#accf40;" | In blue
| style="background-color:#accf40;" | Transporting aircraft
to hangar / deck
| style="background-color:#accf40;" |
|-
| 5
| Crotch
| Bow (front)
| Black
| Do NOT use for landing lineup
|
|-
| style="background-color:#accf40;" | 6
| style="background-color:#accf40;" | Box
| style="background-color:#accf40;" | Between catapults
#1 and #2
| style="background-color:#accf40;" | Black
| style="background-color:#accf40;" | Shooter /
catapult control
| style="background-color:#accf40;" | Little hut where the
catapult controller sits
|-
| 7
| Point
| Starboard bow
|
| QRA: Quick Reaction Alert
| Parking aircraft for quick
reaction air support
|-
| style="background-color:#accf40;" | 8
| style="background-color:#accf40;" | Corral
| style="background-color:#accf40;" | Between elevators
#1 and #2
| style="background-color:#accf40;" |
| style="background-color:#accf40;" | Parking
| style="background-color:#accf40;" |
|-
| 9
| Street
| Midship / Center
|
| Access to elevators, corral, sixpack
|
|-
| style="background-color:#accf40;" | 10
| style="background-color:#accf40;" | Sixpack
| style="background-color:#accf40;" | Midship / Center
| style="background-color:#accf40;" |
| style="background-color:#accf40;" | Parking
| style="background-color:#accf40;" |
|-
| 11
| Junkyard
| Between island and
elevator #3
|
| Parking of AWACS, Tanker,
Transport aircraft
|
|-
| style="background-color:#accf40;" | 12
| style="background-color:#accf40;" | Patio
| style="background-color:#accf40;" | Starboard stern
| style="background-color:#accf40;" |
| style="background-color:#accf40;" | Parking
| style="background-color:#accf40;" |
|-
| 13
| LSO
| Port stern
|
| Landing Officer
| Bunch of guys grading
your landing
|-
| style="background-color:#accf40;" | 14
| style="background-color:#accf40;" | Finger
| style="background-color:#accf40;" | Port stern
| style="background-color:#accf40;" |
| style="background-color:#accf40;" | Parking
| style="background-color:#accf40;" |
|}

Knowing these areas by name is certainly not required, but know to keep the landing deck clear!

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

----

== Carrier Cases ==

During carrier operations we use 1 of 3 possible cases, with cases each having different approaches and procedures: this is to adjust to the weather and visibility conditions. The carrier will normally dictate which case is currently in use, but mainly it is dependant on the minimum visibility ('horizontal sightlines') and ceiling ('vertical visibility') according to the table below:

{| class="wikitable"
! style="background-color:#f8a102; color:#000000;" | Case
! style="background-color:#f8a102;" | Conditions
! style="background-color:#f8a102;" | Ceiling
! style="background-color:#f8a102; color:#000000;" | Visibility
|-
| 1
| No instrument conditions during daytime departures/recoveries
| > 3000 ft (910 m)
| > 5 nm (9.3 km)
|-
| style="background-color:#accc4f;" | 2
| style="background-color:#accc4f;" | (Light) Instrument conditions during daytime departures/recoveries
| style="background-color:#accc4f;" | > 1000 ft (300 m)
| style="background-color:#accc4f;" | > 5 nm (9.3 km)
|-
| 3
| Severe instrument conditions during daytime '''and nighttime''' recoveries
| < 1000 ft (300 m)
| < 5 nm (9.3 km)
|}

Please note that recovering during night time automatically defers you to a case 3 landing, regardless of actual weather and visibility conditions.

=== Altitudes, ranges and distances ===

The Air Traffic Controller in charge of the flight procedures around the carrier is called the 'Marshall', and he gets to boss you around for not flying perfectly perpendicular to his nice pattern / approach. He will tell you what case the carrier is currently operating in, gives you permission to transition to a given holding stack (altitude) or move closer to the carrier (zone).

Most notably the Marshall should tell you the '''BRC''', or '''Base Recovery Course'''. This the current course that the carrier is moving in, and should be the course that you adhere to for landing your aircraft on the carrier deck: please note that the actual carrier landing deck is offset by 9 degrees from the BRC. During Case 3 conditions you will instead be told the '''FB''', or '''Final Bearing''' which is the BRC adjusted with the 9 degree offset (FB = BRC - 9).

Below are the altitude blocks and zone distances associated with carrier operations:

{| class="mw-collapsible mw-collapsed wikitable"
! colspan="7" style="text-align: center; background-color:#f8a102;" | Carrier Altitudes and Zoning
|-
| style="text-align: right; background-color:#f8a102;" | Altitude
| style="background-color:#f8a102;" | Zone
| style="background-color:#000000;" |
| style="background-color:#000000;" |
| style="text-align: right; background-color:#f8a102;" | Distance
| style="background-color:#f8a102;" | Altitude
| style="background-color:#f8a102;" | Zone
|-
| style="text-align: right;" | 6000+ ft
| Case 3 Marshall (traffic) stack
| style="background-color:#000000;" |
| style="background-color:#000000;" |
| style="text-align: right;" | 50 nm DME
| Inf.
| CCA, Carrier Controlled Area
|-
| style="text-align: right; background-color:#accf40;" | 2000+ ft
| style="background-color:#accf40;" | Case 1 holding pattern / stack
| style="background-color:#000000;" |
| style="background-color:#000000;" |
| style="text-align: right; background-color:#accf40;" | 10 nm DME
| style="background-color:#accf40;" | Inf.
| style="background-color:#accf40;" | Marshall Controlled Area
|-
| style="text-align: right;" | 1200 ft
| Case 3 approach and missed approach
| style="background-color:#000000;" |
| style="background-color:#000000;" |
| style="text-align: right;" | 5 nm DME
| 2500 ft
| CCZ, Carrier Controlled Zone
|-
| style="text-align: right; background-color:#accf40;" | 800 ft
| style="background-color:#accf40;" | Case 1 initial overhead break
| style="background-color:#000000;" |
| style="background-color:#000000;" |
| style="text-align: right; background-color:#accf40;" |
| style="background-color:#accf40;" |
| style="background-color:#accf40;" |
|-
| style="text-align: right;" | 600 ft
| Case 1 downwind and missed approach
| style="background-color:#000000;" |
| style="background-color:#000000;" |
| style="text-align: right;" |
|
|
|-
| style="text-align: right; background-color:#accf40;" | 500 ft
| style="background-color:#accf40;" | Case 1 departure in CCZ
| style="background-color:#000000;" |
| style="background-color:#000000;" |
| style="text-align: right; background-color:#accf40;" |
| style="background-color:#accf40;" |
| style="background-color:#accf40;" |
|-
| style="text-align: right;" | 300 ft
| Helicopter operations in CCZ
| style="background-color:#000000;" |
| style="background-color:#000000;" |
| style="text-align: right;" |
|
|
|}

Distances given in '''DME''' (Distance Measuring Equipment) are thus identical to distance from the carrier: this distance can be obtained by using the TACAN signal of the carrier or similar equipment (ICLS).

----

== Carrier TakeOff ==

----

== Carrier Landing ==

For this chapter we have outline the various carrier cases landing procedures and approaches: for ease of use these are split into the traffic pattern and landing pattern. The '''traffic pattern''' is used for approaching to the carrier and holding the in the traffic pattern / stack until you it is your time to land on the carrier (which usually involves waiting for other pilots to land first). The '''landing pattern''' goes about explaining the actual steps for the landing approach. Thanks to Kola360 we have also been able to provide you with the relevant communications guide for these cases.

We would like to give a massive 'Thank you' to '''Jabbers''', '''Kola360''' and '''Redkite''' for their contributions to making these chapters.

----
=== Case 1 Landing ===

<gallery widths=300px heights=300px>
File:Case_1_stack_pattern.png|none|alt=Alt text|Case 1 Traffic Pattern
File:Case 1 landing pattern.png|none|alt=Alt text|Case 1 Landing Pattern
File:IFLOLS diagram.png|none|alt=Alt text|IFLOLS
</gallery>

The Case 1 landing in good visibility conditions is (and probably should be) the first type of landing you learn for carrier recovery. It follows these 3 stages:
; 1. Enter traffic pattern
: For case 1 you will contact the relevant air controllers (see communications list), which will grant your permission to enter the airspace and direct you to a holding pattern / altitude (a circle of approx. 5 nm at 1000 feet intervals, starting at 2000 feet).
; 2. Fly landing pattern
: When you are cleared by the Marshall for landing, you will use the landing pattern to get to the carrier (on final, or 'in the groove')
; 3. Line up with IFLOLS
: The final stage of Case 1 is the line-up with the IFLOLS on final approach, or 'in the groove'



Instructions for Case 1 communications and approach pattern are in the table below. For this communications example our pilot has (side) number '118' and we have a number of radio frequencies (called 'buttons'): the pilot/side number and radio frequencies will most likely be different in your scenario.

{| class="mw-collapsible mw-collapsed wikitable"
! colspan="5" style="text-align: center; background-color:#f8a102;" | Case 1 Communication / Landing Pattern
|-
| style="text-align: center; background-color:#f8a102;" | #
| style="text-align: center; background-color:#f8a102;" | Location
| style="text-align: center; background-color:#f8a102;" | Pilot action
| style="text-align: center; background-color:#f8a102;" | Messages
| style="text-align: center; background-color:#f8a102;" | Frequency
|-
| style="text-align: right;" | 1
| 17000 ft, 75+ DME
Outside of CCA (~ 50 nm)
| style="text-align: center;" | Ask permission from Red Crown to enter.
| Pilot: [Red Crown, 118, Mother's 250 for 75, Angels 17] 
 
Red Crown: [118, Sweet/Sweet, contact Strike on Button 3]
| style="text-align: center;" | Button 4,
256.000 AM
|-
| style="text-align: right; background-color:#accf40;" | 2
| style="background-color:#accf40;" | 12000 ft, 55 DME
Inside CCA
Outside Marshall Area (10 nm)
| style="text-align: center; background-color:#accf40;" | Ask permission from Strike to enter.
| style="background-color:#accf40;" | Pilot: [Strike, 118, flight of 2, Mother's 250 for 55, Angels 12] 
Pilot: [State 5.4, no Alibis] 
 
Strike: [118, Sweet/Sweet, Mother is VFR, Case 1] 
Strike: [Contact Marshall on Button 2] 
| style="text-align: center; background-color:#accf40;" | Button 3,
265.000 AM
|-
| style="text-align: right;" | 3
| 9000 ft, 52 DME
| style="text-align: center;" | Pilot makes call outside 10 nm (but inside CCA).
Contact Marshall to enter CCA.
| Pilot: [Marshall, 118, 2050 for 52, Angels 9, State 5.3] 
Marshall: [118, Case 1, BRC is 010, hold at 2000, Charlie Time 22] 
Marshall: [Altimeter 29.92. Report see me.] 
 
Pilot: [118, Wilco]
| style="text-align: center;" | Button 2,
264.000 AM
|-
| style="text-align: right; background-color:#accf40;" | 4
| style="background-color:#accf40;" | 5000 ft, 10 DME
| style="text-align: center; background-color:#accf40;" | Pilot has visual on carrier. Cleared to enter stack
(2000 ft, stack 1). Monitor button 1 for other traffic.
| style="background-color:#accf40;" | Pilot: [118, See you at 10] 
 
Marshall: [118, Switch Tower on Button 1]
| style="text-align: center; background-color:#accf40;" | Button 2,
264.000 AM
|-
| style="text-align: right;" | 5
| 2000 ft, In the Stack
| style="text-align: center;" | Pilot has obtained Charlie Time from Marshall and
must be 'At Ramp' at given time (2200 hours).
| style="text-align: center;" | Zip Lip, unless [safety concerns].
Monitor Button 1 for traffic
| style="text-align: center;" | Button 1,
301.000 AM
|-
| style="text-align: right; background-color:#accf40;" | 6
| style="background-color:#accf40;" | 2000 ft, In the Stack
| style="text-align: center; background-color:#accf40;" | Pilot matches speed so he is 'At Ramp'
on Charlie Time
| style="text-align: center; background-color:#accf40;" | IMC ONLY
Pilot: [118, Commencing] 
Pilot: [118, at Initial]
| style="text-align: center; background-color:#accf40;" | Button 1,
301.000 AM
|-
| style="text-align: right;" | 7
| 800 ft
| style="text-align: center;" | Case 1 Recovery
| LSO: [3/4 mile, Call the Ball] 
 
Pilot: [118, tomcat/hornet, call/clara, state, auto*] 
 
LSO: [Roger Ball]
| style="text-align: center;" | Button 1,
301.000 AM
|-
| colspan="5" style="text-align: center; background-color:#f8a102;" | Additional case 1 communication
|-
| style="text-align: right;" | 8
| 2000 ft, In the Stack
| Air Boss adds Delta Time to given Charlie Time:
'At Ramp' time becomes Charlie Time + Delta Time
| Air Boss: [118, Delta 6]
| Button 1,
301.000 AM
|-
| style="text-align: right; background-color:#accf40;" | 9
| style="background-color:#accf40;" | 2000 ft, Commencing
| style="background-color:#accf40;" | Pilot has to go into spin pattern before
heading for the initial break
| style="background-color:#accf40;" | Air Boss: [118, Spin It] 
 
Pilot: [118, Spinning]
| style="background-color:#accf40;" | Button 1,
301.000 AM
|-
| style="text-align: right;" | 10
| 600 ft, Abeam carrier
| Pilot has extend downwind too far and must
return to initial (800 ft starboard of carrier),
to redo the case 1 pattern
| Air Boss: [118, too long in the groove,
(an airbus cut you off), wave off and return to pattern]
| Button 1,
301.000 AM
|}

Once you have successfully reached step 7 in the communications example above you should now go into the Case 1 Landing Pattern, as follows in the table below:

{| class="mw-collapsible mw-collapsed wikitable"
! colspan="3" style="text-align: center; background-color:#f8a102;" | Case 1 Landing Pattern
|-
| style="text-align: center; background-color:#f8a102;" | #
| style="text-align: center; background-color:#f8a102;" | F-14
| style="text-align: center; background-color:#f8a102;" | F/A-18
|-
| style="text-align: center;" | A
| style="text-align: center;" | 800 ft entry, approx. 300 - 350 kts,hook down, wing sweep 68
| style="text-align: center;" | 800 ft entry, approx. 300 - 350 kts,hook down
|-
| style="text-align: center; background-color:#accf40;" | B
| colspan="2" style="text-align: center; background-color:#accf40;" | Speedbrake[1], radar altimeter to 370 ft
|-
| style="text-align: center;" | C
| colspan="2" style="text-align: center;" | Level break at 1.5 ~ 2.0 nm DME; 15 to 17 seconds between breaks,level turn at 800 ft.
Turn should be at 45 ~ 50 degrees of bank or at 10% in G of airspeed (i.e. 330 kts -> 3.3 G).
|-
| style="text-align: center; background-color:#accf40;" | D
| style="text-align: center; background-color:#accf40;" | Halfway into turn, set gear down at < 280 ktsand flaps/slats at < 225 kts
| style="text-align: center; background-color:#accf40;" | Halfway into turn, setgear/flaps/slats at < 250 kts
|-
| style="text-align: center;" | E
| colspan="2" style="text-align: center;" | Descend to 600 ft, auto throttle[1]
|-
| style="text-align: center; background-color:#accf40;" | F
| style="text-align: center; background-color:#accf40;" | On-speed AOA at 15 units, set DLC
| style="text-align: center; background-color:#accf40;" | On-speed AOA at 8.1 units
|-
| style="text-align: center;" | G
| colspan="2" style="text-align: center;" | 600 ft
|-
| style="text-align: center; background-color:#accf40;" | H
| colspan="2" style="text-align: center; background-color:#accf40;" | Prepare to turn once abeam of LSO station, at 1 ~ 1.3 nm abeam DME
|-
| style="text-align: center;" | I
| colspan="2" style="text-align: center;" | Commence turn once 'round down' visible, turn at ~ 30 degrees bank
|-
| style="text-align: center; background-color:#accf40;" | J
| colspan="2" style="text-align: center; background-color:#accf40;" | Maintain AOA, halfway into turn at 500 ft
|-
| style="text-align: center;" | K
| colspan="2" style="text-align: center;" | Enter groove at ~ 350 ft (altimeter!), at 3/4 miles, on-speed and call the ball:side number, tomcat/hornet, ball/clara[2], fuelstate[3], (auto[4])
|-
| style="text-align: center; background-color:#6665cd;" | W
| colspan="2" style="text-align: center; background-color:#6665cd;" | Upon (or prior to) waveoff set full power: return to BRC paralleland intercept pattern at LSO / marshall discretion
|-
| colspan="3" style="background-color:#000000;" |
|-
| colspan="2" style="text-align: right;" | Speedbrake / ATC [1]
| As desired
|-
| colspan="2" style="text-align: right; background-color:#f8ff00;" | Clara [2]
| style="background-color:#f8ff00;" | Ball is obscured, LSO will give instructions
|-
| colspan="2" style="text-align: right;" | Fuelstate [3]
| Remaining fuel in thousands of pounds:5100 pounds -> 5.1
|-
| colspan="2" style="text-align: right; background-color:#f8ff00;" | Auto [4]
| style="background-color:#f8ff00;" | Auto throttle is engaged
|}

Once you are on final approach / in the groove (K), you should now switch to the use of the IFLOLS system. This last phase should last around 15 - 17 seconds: any shorter and you may not be able to line up correctly, any longer and the LSO / Marshall will wave you off for being in the pattern for too long.

{| class="mw-collapsible mw-collapsed wikitable"
! colspan="3" style="text-align: center; background-color:#f8a102;" | IFLOLS
|-
| style="text-align: center; background-color:#f8a102;" | #
| style="text-align: center; background-color:#f8a102;" | Name
| style="text-align: center; background-color:#f8a102;" | Function
|-
| 1
| Ladder /
Meatball
| On this vertical bar with yellow/red lights, the orange ball ('meatball') will move up and down
according to aircraft position. If the ball is too low, your aircraft is too low. If the ball is too high, your
aircraft is too high. The goal is to line it up with the datum lights (2) for optimal landing: should the orange
ball fall into red lights you are dangerously low and you will need to wave off (stop) the landing attempt.
|-
| style="background-color:#accf40;" | 2
| style="background-color:#accf40;" | Datum lights
| style="background-color:#accf40;" | These green horizontal bar of lights indicates your ideal line up: the goal is to have the orange ball ('meatball')
line up with the datum lights for ideal vertical landing position.
|-
| 3
| Cut lights
| On early approach the cut lights illuminate 2 ~ 3 seconds to indicate 'proceed with landing'. Any subsequent
illumination means 'add power', according to length of illumination of lights
|-
| style="background-color:#accf40;" | 4
| style="background-color:#accf40;" | Wave off lights
| style="background-color:#accf40;" | Should the landing fall outside safe parameters (for example you are way too low), the LSO will call 'Wave Off!'
and these lights will illuminate: you need to terminate the landing attempt and go around (climb away).
|-
| 5
| Emergency wave off lights
| Identical in function to normal Wave Off Lights (4): for really dense pilots.
|}

The IFLOLS landing phase will typically be accompanied by call-outs from the LSO, which can be found in the next chapter.
----

=== LSO (Landing Signal Officer) ===

In here you will find the various relevant callouts the Landing Signal Officer (LSO) can make during landing. Please refer to the relevant Case 1, 2, 3 landings to find specifics as to the callouts in those situations: for example during Case 1 communications are kept to a minimum (unless there are safety concerns).

==== Carrier Landing LSO Callouts ====

{| class="mw-collapsible mw-collapsed wikitable"
! colspan="3" style="text-align: center; background-color:#f8a102;" | LSO Callouts
|-
| style="text-align: center; background-color:#f8a102;" | Callout
| style="text-align: center; background-color:#f8a102;" | By
| style="text-align: center; background-color:#f8a102;" | Meaning
|-
| Paddles Contact
| LSO
| You are abeam LSO platform, begin final turn
|-
| style="background-color:#accf40;" | 3/4 mile call the ball
| style="background-color:#accf40;" | LSO
| style="background-color:#accf40;" | Can you see the meatball?
|-
| style="color:#3166ff;" | 118 Tomcat Ball 5.6
| style="color:#3166ff;" | Pilot
| style="color:#3166ff;" | Modex / Aircraft Type / Meatball / Fuelstate / Auto* [1]
|-
| style="background-color:#accf40;" | Go Manual
| style="background-color:#accf40;" | LSO
| style="background-color:#accf40;" | Disengage Autothrottles (ATC)
|-
| Roger Ball
| LSO
| Aircraft is cleared to continue
|-
| style="background-color:#accf40;" | You are high
| style="background-color:#accf40;" | LSO
| style="background-color:#accf40;" | Aircraft is above glideslope
|-
| Power
| LSO
| Add power, aircraft below glideslope
|-
| style="background-color:#accf40;" | Right for lineup
| style="background-color:#accf40;" | LSO
| style="background-color:#accf40;" | Come right to centerline
|-
| Come left
| LSO
| Come left to centerline
|-
| style="background-color:#accf40;" | Easy with it
| style="background-color:#accf40;" | LSO
| style="background-color:#accf40;" | Control corrections are excessive
|-
| In Close
| LSO
| Aircraft at ramp
|-
| style="background-color:#accf40;" | You are fast/slow
| style="background-color:#accf40;" | LSO
| style="background-color:#accf40;" | Adjust aircraft AOA, it is incorrect
|-
| style="color:#fe0000;" | Burner!
| style="color:#fe0000;" | LSO
| style="color:#fe0000;" | Select afterburner!
|-
| style="background-color:#accf40; color:#fe0000;" | Wave-Off!
| style="background-color:#accf40; color:#fe0000;" | LSO
| style="background-color:#accf40; color:#fe0000;" | Execute Wave-Off!
|-
| Bolter
| LSO
| You missed all the arrestor wires
|}

As to the pilot 3/4 mile ball call, it used the following format:
Modex / Aircraft Type / Meatball / Fuelstate / Auto* [1]
; Modex
: Side number of aircraft
; Aircraft type
: Tomcat, Hornet, Harrier
; Meatball (IFLOLS)
: If you can visually acquire (see) the meatball, say 'ball'.
: If you cannot see the meatball, say 'clara' and the LSO will talk you in during your landing
; Fuelstate
: The fuel remaining in thoudands of pounds: 5100 pounds -> 5.1, 3500 pounds -> 3.5
; Auto
: Only say this if you are using autothrottles

So for a Hornet with 3400 pounds of fuel, with sidenumber 102, using autothrottles, of which the pilot can see the meatball, the ball call would be:
102 Hornet Ball 3.4 auto
And equally for a Tomacat with 4100 pounds of fuel, side number 118, of which the pilot cannot see the meatball:
118 Tomcat Clara 4.1

==== LSO Grading ====

After you have made a landing attempt you can expect an evaluation and grade for your landing: these are written in the LSO shorthand. On-board a carrier these are typically posted on a board, with on-going scoring: aside from bragging rights, scoring is kept to visualise performance and re-educate pilots doing poorly.

[[File:Carrier glideslope.png|500px|thumb|right|caption|Glide slope naming 
X - At the Start 
IM - In the Middle 
IC - In Close 
AR - At Ramp 
IW - In the Wires 
AW - All the Way 
]]

{| class="mw-collapsible mw-collapsed wikitable"
! colspan="4" style="background-color:#f8a102;" | Overall Grade
|-
| style="background-color:#f8a102;" | Grade
| style="background-color:#f8a102;" | Score
| style="background-color:#f8a102;" | Rating
| style="background-color:#f8a102;" | Score
|-
| _OK_
| OK Underline
| Perfect pass: rarely awarded
| 5
|-
| style="background-color:#accf40;" | OK
| style="background-color:#accf40;" | OK Pass
| style="background-color:#accf40;" | Pass with very minor deviations
| style="background-color:#accf40;" | 4
|-
| (OK)
| Fair Pass
| Pass with one or more safe deviations
| 3
|-
| style="background-color:#accf40;" | B
| style="background-color:#accf40;" | Bolter
| style="background-color:#accf40;" | Safe pass where aircraft fails to hook a wire
| style="background-color:#accf40;" | 2.5
|-
| --
| No Grade
| Pass with gross (still safe) deviations:
failure to listen to LSO, inappropriate actions
| 2
|-
| style="background-color:#accf40;" | TWO
| style="background-color:#accf40;" | Technique Waveoff
| style="background-color:#accf40;" | Pass with unsafe deviations: needed to be aborted
| style="background-color:#accf40;" | 1
|-
| style="background-color:#accf40;" | C
| style="background-color:#accf40;" | Cut Pass
| style="background-color:#accf40;" | Unsafe pass with unacceptable deviations
| style="background-color:#accf40;" | 0
|-
| style="background-color:#accf40;" | WO
| style="background-color:#accf40;" | Foul Deck Waveoff
| style="background-color:#accf40;" | Aborted pass after landing deck fouled (blocked):
no points and not counted towards average
| style="background-color:#accf40;" | ---
|}

Aside from the overall grading board, there will also be a board or score sheet which has the development of each landing noted in the symbology. We can split this apart in the general symbology and the overall symbology, as per the [http://www.navyair.com/LSO_NATOPS_Manual.pdf LSO Natops Manual]. The table below list the most frequently used entries:

{| class="mw-collapsible mw-collapsed wikitable"
! colspan="5" style="text-align: center; background-color:#f8a102;" | LSO General Symbology
|-
| style="background-color:#f8a102;" | Symbology
| style="background-color:#f8a102;" | Meaning
| style="background-color:#000000;" |
| style="text-align: center; background-color:#f8a102;" | Symbology
| style="background-color:#f8a102;" | Meaning
|-
| style="text-align: center;" | WO
| Waveoff
| style="background-color:#000000;" |
| style="text-align: center;" | ()
| A little
|-
| style="text-align: center; background-color:#accf40;" | WOP
| style="background-color:#accf40;" | Waveoff Pattern
| style="background-color:#000000;" |
| style="text-align: center; background-color:#accf40;" | _Comment_
| style="background-color:#accf40;" | A lot
|-
| style="text-align: center;" | OWO
| Own Waveoff
| style="background-color:#000000;" |
| style="text-align: center;" | []
| Ignored signal LSO
|-
| style="text-align: center; background-color:#accf40;" | TWO
| style="background-color:#accf40;" | Technique Waveoff
| style="background-color:#000000;" |
| style="text-align: center; background-color:#accf40;" | O
| style="background-color:#accf40;" | Signal acknowledged
too slowly
|-
| style="text-align: center;" | TLU
| Test Lineup
| style="background-color:#000000;" |
| style="text-align: center;" | OC
| Over Corrected
|-
| style="text-align: center; background-color:#accf40;" | _OK_
| style="background-color:#accf40;" | Perfect Pass
| style="background-color:#000000;" |
| style="text-align: center; background-color:#accf40;" | •
| style="background-color:#accf40;" | Indicates 'on'
|-
| style="text-align: center;" | OK
| Reasonable Pass
| style="background-color:#000000;" |
| style="text-align: center;" | -
| Indicates 'to'
|-
| style="text-align: center; background-color:#accf40;" | (OK)
| style="background-color:#accf40;" | Fair Pass
| style="background-color:#000000;" |
| style="text-align: center; background-color:#accf40;" | PATT
| style="background-color:#accf40;" | Pattern
|-
| style="text-align: center;" | ---
| No Grade
| style="background-color:#000000;" |
| style="text-align: center;" | M1
| Mode 1 ACLS
|-
| style="text-align: center; background-color:#accf40;" | C
| style="background-color:#accf40;" | Cut
| style="background-color:#000000;" |
| style="text-align: center; background-color:#accf40;" | (A)
| style="background-color:#accf40;" | Auto
|-
| style="text-align: center;" | B
| Bolter
| style="background-color:#000000;" |
| style="text-align: center;" | BC
| Missed / incorrect
Ball Call
|-
| style="text-align: center; background-color:#accf40;" | NC
| style="background-color:#accf40;" | No Count
| style="background-color:#000000;" |
| style="text-align: center; background-color:#accf40;" | AFU
| style="background-color:#accf40;" | All 'Fouled' Up
|}

Below are the additional (remaining) entries from the LSO Jargon table: these are not frequently used, unlike the ones in the general table.

{| class="mw-collapsible mw-collapsed wikitable"
! colspan="11" style="text-align: center; background-color:#f8a102;" | LSO Grading Jargon
|-
| style="text-align: center; background-color:#f8a102;" | SYM
| style="background-color:#f8a102;" | Meaning
| style="background-color:#000000;" |
| style="text-align: center; background-color:#f8a102;" | SYM
| style="background-color:#f8a102;" | Meaning
| style="background-color:#000000;" |
| style="text-align: center; background-color:#f8a102;" | SYM
| style="background-color:#f8a102;" | Meaning
| style="background-color:#000000;" |
| style="text-align: center; background-color:#f8a102;" | SYM
| style="background-color:#f8a102;" | Meaning
|-
| style="text-align: center;" | AA
| Angling Approach
| style="background-color:#000000;" |
| style="text-align: center;" | HO
| Hold Off
| style="background-color:#000000;" |
| style="text-align: center;" | OR
| Overrotate
| style="background-color:#000000;" |
| style="text-align: center;" | TMP
| Too Much Power
|-
| style="text-align: center; background-color:#accf40;" | ACC
| style="background-color:#accf40;" | Accelerate
| style="background-color:#000000;" |
| style="text-align: center; background-color:#accf40;" | LIG
| style="background-color:#accf40;" | Long In Groove
| style="background-color:#000000;" |
| style="text-align: center; background-color:#accf40;" | OS
| style="background-color:#accf40;" | Overshoot
| style="background-color:#000000;" |
| style="text-align: center; background-color:#accf40;" | TMRD
| style="background-color:#accf40;" | Too Much Rate of Descent
|-
| style="text-align: center;" | AFU
| All 'Fouled' Up
| style="background-color:#000000;" |
| style="text-align: center;" | LL
| Landed Left
| style="background-color:#000000;" |
| style="text-align: center;" | OSCB
| Overshoot Coming Back
| style="background-color:#000000;" |
| style="text-align: center;" | TMRR
| Too Much Right Rudder
|-
| style="text-align: center; background-color:#accf40;" | B
| style="background-color:#accf40;" | Flat glideslope
| style="background-color:#000000;" |
| style="text-align: center; background-color:#accf40;" | LLU
| style="background-color:#accf40;" | Late LineUp
| style="background-color:#000000;" |
| style="text-align: center; background-color:#accf40;" | P
| style="background-color:#accf40;" | Power
| style="background-color:#000000;" |
| style="text-align: center; background-color:#accf40;" | TTL
| style="background-color:#accf40;" | Turned Too Late
|-
| style="text-align: center;" | C
| Climbing
| style="background-color:#000000;" |
| style="text-align: center;" | LO
| Low
| style="background-color:#000000;" |
| style="text-align: center;" | PD
| Pitching Deck
| style="background-color:#000000;" |
| style="text-align: center;" | TTS
| Turned Too Soon
|-
| style="text-align: center; background-color:#accf40;" | CB
| style="background-color:#accf40;" | Coming Back to lineup
| style="background-color:#000000;" |
| style="text-align: center; background-color:#accf40;" | LR
| style="background-color:#accf40;" | Landed Right
| style="background-color:#000000;" |
| style="text-align: center; background-color:#accf40;" | PNU
| style="background-color:#accf40;" | Pulled Nose Up
| style="background-color:#000000;" |
| style="text-align: center; background-color:#accf40;" | TWA
| style="background-color:#accf40;" | Too Wide Abeam
|-
| style="text-align: center;" | CD
| Coming Down
| style="background-color:#000000;" |
| style="text-align: center;" | LTR
| Left To Right
| style="background-color:#000000;" |
| style="text-align: center;" | ROT
| Rotate
| style="background-color:#000000;" |
| style="text-align: center;" | W
| Wings
|-
| style="text-align: center; background-color:#accf40;" | CH
| style="background-color:#accf40;" | Chased
| style="background-color:#000000;" |
| style="text-align: center; background-color:#accf40;" | LU
| style="background-color:#accf40;" | LineUp
| style="background-color:#000000;" |
| style="text-align: center; background-color:#accf40;" | RUD
| style="background-color:#accf40;" | Rudder
| style="background-color:#000000;" |
| style="text-align: center; background-color:#accf40;" | WU
| style="background-color:#accf40;" | Wrapped Up
|-
| style="text-align: center;" | CO
| Come-On
| style="background-color:#000000;" |
| style="text-align: center;" | LUL
| Lined Up Left
| style="background-color:#000000;" |
| style="text-align: center;" | RUF
| Rough
| style="background-color:#000000;" |
| style="text-align: center;" | XCTL
| Cross Control
|-
| style="text-align: center; background-color:#accf40;" | CU
| style="background-color:#accf40;" | Cocked Up
| style="background-color:#000000;" |
| style="text-align: center; background-color:#accf40;" | LUR
| style="background-color:#accf40;" | Lined Up Right
| style="background-color:#000000;" |
| style="text-align: center; background-color:#accf40;" | RWD
| style="background-color:#accf40;" | Right Wing Down (DWR)
| style="background-color:#000000;" |
| style="text-align: center; background-color:#accf40;" | /
| style="background-color:#accf40;" | Fly through glideslope (going up)
|-
| style="text-align: center;" | DD
| Deck Down
| style="background-color:#000000;" |
| style="text-align: center;" | LWD
| Left Wing Down (DWL)
| style="background-color:#000000;" |
| style="text-align: center;" | RR
| Right Rudder
| style="background-color:#000000;" |
| style="text-align: center;" | \
| Fly through glideslope (going down)
|-
| style="text-align: center; background-color:#accf40;" | DEC
| style="background-color:#accf40;" | Decelerate
| style="background-color:#000000;" |
| style="text-align: center; background-color:#accf40;" | N
| style="background-color:#accf40;" | Nose
| style="background-color:#000000;" |
| style="text-align: center; background-color:#accf40;" | RTL
| style="background-color:#accf40;" | Right To Left
| style="background-color:#000000;" |
| style="text-align: center; background-color:#accf40;" | LLWD
| style="background-color:#accf40;" | Landed Left Wing Down
|-
| style="text-align: center;" | DL
| Drifted Left
| style="background-color:#000000;" |
| style="text-align: center;" | NC
| Nice Correction
| style="background-color:#000000;" |
| style="text-align: center;" | S
| Settle
| style="background-color:#000000;" |
| style="text-align: center;" | LRWD
| Landed Right Wing Down
|-
| style="text-align: center; background-color:#accf40;" | DN
| style="background-color:#accf40;" | Dropped Nose
| style="background-color:#000000;" |
| style="text-align: center; background-color:#accf40;" | ND
| style="background-color:#accf40;" | Nose Down
| style="background-color:#000000;" |
| style="text-align: center; background-color:#accf40;" | SD
| style="background-color:#accf40;" | Spotted Deck
| style="background-color:#000000;" |
| style="text-align: center; background-color:#accf40;" | LNF
| style="background-color:#accf40;" | Landed Nose First
|-
| style="text-align: center;" | DR
| Drifted Right
| style="background-color:#000000;" |
| style="text-align: center;" | NEA
| Not Enough Attitude
| style="background-color:#000000;" |
| style="text-align: center;" | SHT
| Ship's Turn
| style="background-color:#000000;" |
| style="text-align: center;" | ^
| Over the Top
|-
| style="text-align: center; background-color:#accf40;" | DU
| style="background-color:#accf40;" | Deck up
| style="background-color:#000000;" |
| style="text-align: center; background-color:#accf40;" | NEP
| style="background-color:#accf40;" | Not Enough Power
| style="background-color:#000000;" |
| style="text-align: center; background-color:#accf40;" | SKD
| style="background-color:#accf40;" | Skid
| style="background-color:#000000;" |
| style="text-align: center; background-color:#accf40;" |
| style="background-color:#accf40;" |
|-
| style="text-align: center;" | EG
| Eased Gun
| style="background-color:#000000;" |
| style="text-align: center;" | NERD
| Not Enough Rate of Descent
| style="background-color:#000000;" |
| style="text-align: center;" | SLO
| Slow
| style="background-color:#000000;" |
| style="text-align: center;" |
|
|-
| style="text-align: center; background-color:#accf40;" | F
| style="background-color:#accf40;" | Fast
| style="background-color:#000000;" |
| style="text-align: center; background-color:#accf40;" | NERR
| style="background-color:#accf40;" | Not Enough Right Rudder
| style="background-color:#000000;" |
| style="text-align: center; background-color:#accf40;" | SRD
| style="background-color:#accf40;" | Stopped Rate of Descent
| style="background-color:#000000;" |
| style="text-align: center; background-color:#accf40;" |
| style="background-color:#accf40;" |
|-
| style="text-align: center;" | FD
| Fouled Deck
| style="background-color:#000000;" |
| style="text-align: center;" | NESA
| Not Enough Straight Away
| style="background-color:#000000;" |
| style="text-align: center;" | ST
| Steep Turn
| style="background-color:#000000;" |
| style="text-align: center;" |
|
|-
| style="text-align: center; background-color:#accf40;" | GLI
| style="background-color:#accf40;" | Gliding Approach
| style="background-color:#000000;" |
| style="text-align: center; background-color:#accf40;" | NH
| style="background-color:#accf40;" | No Hook
| style="background-color:#000000;" |
| style="text-align: center; background-color:#accf40;" | TCA
| style="background-color:#accf40;" | Too Close Abeam
| style="background-color:#000000;" |
| style="text-align: center; background-color:#accf40;" |
| style="background-color:#accf40;" |
|-
| style="text-align: center;" | H
| High
| style="background-color:#000000;" |
| style="text-align: center;" | NSU
| Not Set Up
| style="background-color:#000000;" |
| style="text-align: center;" | TMA
| Too Much Attitude
| style="background-color:#000000;" |
| style="text-align: center;" |
|
|}

----
=== Case 2 Landing ===

Case 2 recoveries (landings) are in practice a weird (Frankenstein) mix of both Case 1 and Case 3 landings, so we advise you familiarise yourself with these cases first and then come back to the Case 2 recoveries.

In essence the Case 2 recoveries are flown by entering the Case 3 Stack pattern and pushing to the boat (aircraft carrier) as normal, but once you get within visual range of the carrier you instead transition to the Case 1 Landing Pattern.

----

=== Case 3 Landing ===

<gallery widths=400px heights=400px>
File:Case 3 landing pattern.png|Case 3 Landing Pattern
File:IFLOLS diagram.png|thumb|right|[https://en.wikipedia.org/wiki/Optical_landing_system#Improved_fresnel_lens_optical_landing_system_(IFLOLS)| IFLOLS]
</gallery>

{| class="mw-collapsible mw-collapsed wikitable"
! colspan="5" style="text-align: center; background-color:#f8a102;" | Case 3 Communication
|-
| style="background-color:#f8a102;" | #
| style="background-color:#f8a102;" | Location
| style="background-color:#f8a102;" | Pilot Action
| style="background-color:#f8a102;" | Messages
| style="background-color:#f8a102;" | Frequency
|-
| 1
| 17000 ft, 75+ DME
Outside of CCA (~50 nm)
| Ask permission from Red Crown to enter.
| Pilot: [Red Crown, 118, Mother's 250 for 75, Angels 17] 

Red Crown: [118, Sweet/Sweet, contact Strike on Button 3]
| Button 4,
256.000 AM
|-
| style="background-color:#accf40;" | 2
| style="background-color:#accf40;" | 16000 ft, 55 DME
Inside CCA (~ 50 nm), outside
Marshall Area (10 nm)
| style="background-color:#accf40;" | Ask permission from Strike to enter.
| style="background-color:#accf40;" | Pilot: [Strike, 118, flight of 1, Mother's 250 for 55, Angels 12] 
Pilot: [State 5.4, no Alibis] 

Strike: [118, Sweet/Sweet, Mother is IMC, Case 3] 
Strike: [Contact Marshall on Button 2] 
| style="background-color:#accf40;" | Button 3,
265.000 AM
|-
| 3
| 14000 ft, 52 DME
| Ask for assigned stack from Marshall:
Stack is given on radial 082, 22 nm 
behind the carrier and at 7000 ft.

Marshall also gives other key information (write it down!)
| Pilot: [Marshall, 118, 250 for 52, Angels 14, State 5.3]

Marshall: [118, Mother's weather is 600 overcast, visibility 3 miles, altimeter 29.87] 
Marshall: [Case 3 recovery, Marshall on the 082, 22, angels 7.] 

Marshall: [Expected Final Bearing 262, Expected approach time 22, Approach button 18] 

Pilot: [118, Altimeter 29.87, Marshall on the 082, 22, angels 7. Expected approach
time 22.]
| Button 2,
264.000 AM
|-
| style="background-color:#accf40;" | 4
| style="background-color:#accf40;" | 7000 ft, in holding pattern
| style="background-color:#accf40;" | Pilot has established holding pattern at 7000 ft: gives fuel state for Marshall to keep track off
| style="background-color:#accf40;" | Pilot: [118, established angels 7. State 5.1]
| style="background-color:#accf40;" | Button 2,
264.000 AM
|-
| 5
| All flights
| Marshall constantly updates all flights with new info: bearing, visibility, altimeter QFH
| Marshall: [118, altimeter 29.88. New final bearing is 265]
| Button 2,
264.000 AM
|-
| style="background-color:#accf40;" | 6
| style="background-color:#accf40;" | 7000 ft, leaving holding pattern
| style="background-color:#accf40;" | Pilot notifies Marshall the descent 
from holding pattern has begun, 
states altimeter setting +
fuel state
| style="background-color:#accf40;" | Pilot: [118, Commencing, 29.88, state 4.8]
Marshall: [118, roger]
| style="background-color:#accf40;" | Button 2,
264.000 AM
|-
| 7
| 5000 ft (platform),
descending
| Pilot notifies Marshall he is passing
5000 ft (platform)
| Pilot: [118, platform]
| Button 2,
264.000 AM
|-
| style="background-color:#accf40;" | 8
| style="background-color:#accf40;" | 1200 - 5000 ft, descend
| style="background-color:#accf40;" | Marshall hands pilot off to approach
(can happen before reaching platform!)
| style="background-color:#accf40;" | Pilot: [118, checking in, state 4.6]
Marshall: [118, switch button 18]
| style="background-color:#accf40;" | Button 2,
264.000 AM
|-
| 9
| 1200 - 5000 ft, descending
| Pilot checks in with approach: pilot may 
be asked to dirty up earlier / later to 
match correct landing intervals
| Pilot: [118, checking in, state 4.5]
Marshall: [118, final bearing 262]
| Button 18,
251.000 AM
|-
| style="background-color:#accf40;" | 10
| style="background-color:#accf40;" | 1200 ft,
around 4 -8 nm DME
| style="background-color:#accf40;" | When ACLS is acquired, 
approach asks what ACLS ('needles') is showing. 

If unsatisfactory, new lock will be tried: 
if no lock approach will tell pilot to
fly ICLS ('bullseye')
| style="background-color:#accf40;" | Approach: [118, say needles] 
Pilot: [405, fly up, on] 
Approach: [118, fly your needles] 

OR

Approach: [118, fly bullseye]
| style="background-color:#accf40;" | Button 18,
251.000 AM
|-
| 11
| 800 ft,
3/4 mile
| LSO chimes in
| LSO: [3/4 mile, Call The Ball] 
Pilot: [118, tomcat/hornet, ball/clara, state, auto*] 
LSO: [Roger Ball]
| Button 18, 251.000 AM
|}

{| class="mw-collapsible mw-collapsed wikitable"
! colspan="3" style="background-color:#f8a102;" | Case 3 Landing Pattern
|-
| style="text-align: center; background-color:#f8a102;" | Pattern
| colspan="2" style="text-align: center; background-color:#f8a102;" | Step
|-
| style="text-align: center;" | A
| colspan="2" | Marshall stack: starting at 6000 ft, with increments of 1000 ftfor each flight / package
|-
| style="text-align: center; background-color:#accf40;" | B
| colspan="2" style="background-color:#accf40;" | Platform, passing 5000 ft
|-
| style="text-align: center;" | C
| colspan="2" | 10 miles DME, 600 ft, commence landing descent
|-
| style="text-align: center; background-color:#accf40;" | D
| colspan="2" style="background-color:#accf40;" | 6 miles DME, maintain 1200 ft ACLS (Automated Carrier Landing System)[1]
|-
| style="text-align: center;" | E
| colspan="2" | 1.5 miles DME, 600 ft, commence landing descent
|-
| style="text-align: center; background-color:#accf40;" | F
| colspan="2" style="background-color:#accf40;" | 1 mile DME, 400 ft
|-
| style="text-align: center;" | G
| colspan="2" | 3/4 mile DME, call the ballside number, tomcat/hornet, ball/clara[2], fuelstate[3], (auto[4])
|-
| style="text-align: center; background-color:#accf40;" | H
| colspan="2" style="background-color:#accf40;" | 1/2 mile DME, 200 ft
|-
| style="text-align: center;" | I
| colspan="2" | Wave off on Final Heading, climb to 1200 ft
|-
| style="text-align: center; background-color:#accf40;" | J
| colspan="2" style="background-color:#accf40;" | Turn to downwind heading, using 10% speed G-turn
|-
| style="text-align: center;" | K
| colspan="2" | Maintain 1200 ft and on speed AOA, flaps/slats/gear/hook down
|-
| style="text-align: center; background-color:#accf40;" | L
| colspan="2" style="background-color:#accf40;" | Turn into Final Heading via 18 ~ 22 degree bank turn
|-
| colspan="2" style="background-color:#000000;" |
| style="background-color:#000000;" |
|-
| colspan="2" style="text-align: right;" | Speedbrake / ACLS [1]
| As desired
|-
| colspan="2" style="text-align: right; background-color:#f8ff00;" | Clara [2]
| style="background-color:#f8ff00;" | Ball is obscured, LSO will give instructions
|-
| colspan="2" style="text-align: right;" | Fuelstate [3]
| Remaining fuel in thousands of pounds:5100 pounds -> 5.1
|-
| colspan="2" style="text-align: right; background-color:#f8ff00;" | Auto [4]
| style="background-color:#f8ff00;" | Auto throttle is engaged
|}

----

== References ==

[https://www.cnatra.navy.mil/local/docs/pat-pubs/P-816.pdf US Navy Carrier Case 1/2/3 PDF File]

[https://www.youtube.com/watch?v=2yEt9QC5ltg&feature=youtu.be Aircraft Carrier Communications, two hours worth of carrier radio chatter]

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

Getting started with GCI/AWACS

2022-09-26T05:10:50Z

Marlan: /* Responding to flights checking in */

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

'''''Disclaimer''''' 
''This guide is compiled using information available to the public and information based on personal experience in DCS World. This guide does not in any way, shape or form represent real life GCI/AWACS operations or techniques nor is it based on real life experience.''

== What is GCI/AWACS ==
[[File:e3_awacs.jpg|thumb|frame|right|Boeing E-3 Sentry]]
GCI stands for '''G'''round-'''C'''ontrolled '''I'''nterception, an air defence tactic which developed during World War I. One or more radar stations or other observational stations are linked to a command communications centre which guides interceptor aircraft to airborne targets.

Today, GCI has mostly been replaced by Airborne Early Warning and Control (AEW&C) aircraft or more commonly referred to as AWACS ('''A'''irborne '''W'''arning '''A'''nd '''C'''ontrol '''S'''ystem). While AEW&C is expensive and vulnerable in comparison to GCI systems, it has a mobility advantage. In reality a combination of both systems is often used.

The role for an Airforce controller (US) is called an ABM (Air Battle Manager) and a Navy controller (US) is called an AIC (Air Intercept Controller), the roles are very similar but do have some notable differences.

AWACS aircraft are generally speaking big, modified planes with a long-range radar mounted on top. The main radar antenna is mounted on a turntable housed in a circular rotodome, which is 9m (30 feet) in diameter, elliptical in cross-section and 1.8m deep at its centre. The radar system can detect, track and identify low-flying aircraft at approximately 370 km (200 nautical miles) and high-level aircraft at much greater distances.

== AI AWACS in DCS World ==
In DCS World the NATO AWACS comes in the form of the Boeing E-3 Sentry and the Russian equivalent is the Beriev A-50. The player can contact the allied AWACS via the ingame comms menu on the specified frequency in the mission briefing.

=== Comms menu ===
;Vector to bullseye
: The AWACS will provide the player with a bearing and range to bullseye

;Vector to home plate
: The AWACS will provide the player with a bearing and range from bullseye to their home airfield

;Vector to tanker
: The AWACS will provide the player with a bearing and range from bullseye to the tanker

;Request BOGEY DOPE
: The AWACS will provide the player a BRAA call to the closest airborne threat.

;Request PICTURE
: The AWACS will provide the player with BRA calls for each group from bullseye

;DECLARE
: The AWACS will identify friend or foe of a radar locked target

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

=== Understanding BRAA calls ===
[[File:Aspects.png|thumb|frame|right|500x|400px|Figure 1]]
BRAA stands for '''B'''earing '''R'''ange '''A'''ltitude '''A'''spect from your current location.
Aspects other than hot should include a cardinal direction. e.g. "Flank Northwest", "Beam East", "Drag South", "Hot", if an aspect is not provided in a BRAA call, "hot" is assumed.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">BRAA, 183/10, 2 thousand, hot</pre>
would indicate that the target is located at 183 degrees, 10 nautical miles away, and at 2000 feet coming directly towards you.

=== Pronunciation ===
Avoid saying:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi 1-1, Magic, BRAA, 183 for 10 at 2000, hot"</pre>
Instead, it is recommended to omit the "for" and "at", and to use short pauses (here indicated with "..."):
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi one one ... Magic ... BRAA ... one eight zero ... ten ... two thousand ... hot"</pre>

=== Understanding bullseye ===
Bullseye is a fixed point on the map determined pre-mission. All allied aircraft can relate to this point. When receiving a bullseye call, simply use the BRAA format with bullseye as starting point. Bullseye should never be truncated to "Bull" or "Bulls", the full word "Bullseye" should be used (or a coded word, but that would only apply if all players were briefed to it).
[[File:bullseye.png|thumb|frame|center|1000x|800px|Left:Bullseye representation in DCS World - Right: Bullseye details]]

== Human GCI/AWACS ==
In DCS World, players can take the role of GCI/AWACS on multiplayer servers to assist your fellow pilots and friends. In the following sections we’ll go over the basics of airspace management, threat assessment, callsigns, brevity and some useful tools.

Before you begin as a GCI/AWACS controller on a server go over this short checklist:
* Pick a suitable callsign

* Check and confirm the radio frequencies used for GCI/AWACS, general communications and air traffic control
* Tune in the correct frequencies on SRS
* Be in the correct server slot (if necessary)
* Have your tools set up and running
* Announce GCI/AWACS will be available over COMMS and CHAT. State the correct frequency and callsign
<pre style="background-color: #ccc;font-family: 'Lucida Console'">99, <your callsign>, SUNRISE, on <frequency>, check in for control.</pre>
* If you are on the Hoggit Discord and are registering as a GAW GCI controller, the appropriate command on discord would be:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">!gci sunrise GAW <callsign, frequency, any other remarks></pre>
When you're finished with your session, use:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">!gci midnight</pre>

=== Airspace management ===
As a controller your goal is to manage both friendly and hostile airspace. You’ll want to direct your allied flights to intercept enemy threats while at the same time making sure your friendly airspace stays protected.

Divide the airspace you’ll be controlling into two sectors.
# a friendly sector
# a hostile sector

Divide sector 1, your friendly sector, into subsectors based on strategic locations like airfields or a FARPs.

Next, you can assign your available CAP flights to the subsectors you created, and have them patrol or set up orbit. This way you can ensure that
* your allied flights are in proximity to allied aircraft and able to support
* your allied aircraft are not spread out or alone in hostile airspace
* your allied aircraft are in range of a tanker or airfield
* your friendly sector is protected

=== Threat assessment ===
With your airspace divided into sectors and your CAP flights on station you can start intercepting enemy threats. There are 2 major things you want to pay close attention to at all times.
* Where are your allied aircraft in relation to your sectors
* Where are the enemy aircraft in relation to your sectors

Before making a decision to direct your allied flights to intercept, you want to assess the threat
# '''Distance''': what is the distance between the threat and the nearby sector or allied aircraft
# '''Number''': how many enemy aircraft make up the threat
# '''Type''': which type is the enemy threat
# ('''State'''): have they been engaged prior and thus used counter measures and/or weapons

When you have gathered this info you can make a decision to either:
* direct one or more allied aircraft to intercept the threat
* direct one or more aircraft away from the threat to nearby SAM cover
* direct one or more allied aircraft to support engaged allied aircraft

In case you are unsure and need extra information before making a decision, contact your allied flights and ask for a fuel and/or weapons state.

When directing your allied flights to intercept, try to keep them in proximity of other allied flights, so you have enough time to send in support if needed. Do not direct your allied flights into enemy airspace and SAM range without support.

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

=== Callsigns and radio communication ===
When acting as GCI/AWACS controller you want to make sure you have a callsign which
* is clear
* is easy to pronounce
* does not cause confusion
* is not ridiculous

Commonly used callsigns for GCI/AWACS are
* Overlord
* Magic
* Showtime
* Darkstar
* Goliath
* Wizard
* Griffin
* Bigfoot

As GCI/AWACS controller you’ll have to relay a lot of information in a clear, concise and easy to understand manner, usually in a short amount of time. It is important to have a good microphone set up, to speak loud and clear, articulate, not to speak too quickly and use the NATO phonetic alphabet to avoid confusion. We’ll discuss some examples below.

==== Responding to flights checking in ====
When allied flights switch to general comms or designated AWACS comms after take off, they’ll most likely check in on the frequency and let you know who they are and what their intentions are.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, checking in for CAP, request alpha check bullseye”</pre>

In the above example a player lets you know who they are, where they are and what their intentions are. You can respond to acknowledge (and task them if desired).
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Radar Contact, Alpha Check, Bullseye 123/45.”
Flight - "Uzi 1-1, good alpha check."</pre>
"Alpha Check Bullseye" is the bearing from the bullseye TO the fighter, and verifies they understand/have the correct bullseye reference point.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima Charlie, standby for tasking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima, Charlie, fly heading 100/20, anchor at Krymsk”</pre>

==== Directing allied aircraft to intercept ====
When directing aircraft to intercept you want to be clear and concise. Start with who you are talking to, who you are and provide a Bullseye or BRAA call (and optional additional information). It is important to pronounce heading as single digits. For example ‘100’ would be ‘one, zero, zero.’ Targeting technically should be done using bullseye and is more helpful to other players (who know how to use it), that said, many players are not familiar with bullseye so BRAA can be used as well.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/40, 15 thousand, flank north west, hostile.”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/60, 500 feet, hot, hostile, 2 contacts, fulcrum.”</pre>

==== Responding to a Bogey Dope request ====
When a player asks for a Bogey Dope, they are asking for the nearest hostile. Locate the aircraft who made the request, and provide them a BRA to the nearest hostile.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA, 257/15, 10 thousand, drag east”</pre>

When there are no hostile aircraft on scope
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Clean”</pre>

==== Responding to a DECLARE request ====
When you receive a DECLARE request, you are asked to identify friend or foe of a locked target.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, Bullseye 204/8, 12 thousand, DECLARE.”</pre>
or use BRAA (not technically correct, but fine here)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, BRAA 090/15, 12 thousand, DECLARE.”</pre>
Response:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Group, Bullseye 204/8, 12 thousand, hostile, single contact, flanker”</pre>
(fill-ins "single contact" and "flanker" are optional)

==== Miscellaneous ====
Sometimes you will need to ask for additional information, or provide additional information.

Return to base (RTB)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, winchester RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 010/35”</pre>

Ask for state
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, say state”</pre>
Typically, yellow means a fighter can take at least one more engagement, where red means a fighter is unable.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, yellow”</pre>
or
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, fuel green, weapons green”</pre>
or
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, 4/1/2 by 7 point 5”</pre>
"4/1/2" is equivalent to 4 active missiles (e.g. AIM-120), 1 semi-active missile (e.g. AIM-7) and 2 infrared missiles (e.g. AIM-9) with 7,500lbs of fuel remaining. "MINUS" can be added to indicate they do not have, or have insufficient guns. (e.g. "Uzi 1-1, 4/1/2, minus, by 7 point 5")

Inform aircraft to wait for instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, standby”</pre>

Correcting mistakes
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, disregard last”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA 070/5, ... correction, BRAA 090/5, 7 thousand, hot”</pre>

Identify unknown transmitting aircraft
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Last transmitting aircraft, state callsign”</pre>

Inform aircraft about incoming missiles or missile launches (unrealistic, generally only possible with F10 map)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, SAM, bearing 090”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, Missile, bearing 090”</pre>

=== Tools ===
==== SRS AWACS mode (eam) ====
The standard SRS radio overlay only displays up to 3 radios and 1 intercom. The AWACS overlay provides up to 10 radios, which you can manually tune and 1 intercom.

You can use SRS without running DCS World, by using the external AWACS mode (EAM). provide your EAM username and the EAM coalition password. The coalition password is provided by the server admin, or in the server briefing. This is not always available.

==== F10 map, icons and the ruler tool ====
The ingame F10 map is where you’ll spend most of your time doing GCI/AWACS. It provides several functions which you can toggle on or off by personal preference
* health bars
* SAM and AAA detection range indicators
* SAM and AAA engagement range indicators
* grid
* labels indicating type and name
* ruler tool

The most important function you’ll use is the ruler tool. It allows you to create a line from point A to point B and provides you with the length in nautical miles and the heading. When intercepting enemy aircraft you can use the ruler tool to draw a line from your allied aircraft A to the hostile aircraft B and read the distance in nautical miles and the heading indicated on the top bar. When you click on the enemy aircraft icon, you can read its altitude, speed in knots, heading and type on the bottom left.

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

==== LotATC ====
LotATC is an optional program one can use to facilitate GCI simulation. The program is fairly easy to use is highly customizable. LotATC provides many features to aid a GCI.

* The creation of persistant BRAAs
* IFF features
* An ATC mode
* The ability to call BRAAs from the bullseye
* A scale which can be used to respond to Picture calls
* The ability to draw on the map

For more information on LotATC and how to use the software see [https://wiki.hoggitworld.com/view/LotATC LotATC]

== Coordinating with human GCI/AWACS ==
A couple guidelines from the players point of view

Inform AWACS when you tune in or tune out of the AWACS frequency.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F18, 10nm North of Anapa, checking in for CAP”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single Mirage 2000, checking in for CAP”</pre>

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, bingo fuel, RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 100/35”</pre>

Do not clutter the AWACS frequency with off-topic chatter, use the correct frequencies as stated in mission briefing.

Do not read back a BRAA call. Simply acknowledge you received and understood the message by saying your callsign. If you did not understand the transmission, ask the AWACS to repeat.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA 100/45, 20 thousand, flank north west”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Uzi 1-1”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, say again”</pre>

Getting started with GCI/AWACS

2022-09-05T15:17:21Z

Marlan: /* Miscellaneous */

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

'''''Disclaimer''''' 
''This guide is compiled using information available to the public and information based on personal experience in DCS World. This guide does not in any way, shape or form represent real life GCI/AWACS operations or techniques nor is it based on real life experience.''

== What is GCI/AWACS ==
[[File:e3_awacs.jpg|thumb|frame|right|Boeing E-3 Sentry]]
GCI stands for '''G'''round-'''C'''ontrolled '''I'''nterception, an air defence tactic which developed during World War I. One or more radar stations or other observational stations are linked to a command communications centre which guides interceptor aircraft to airborne targets.

Today, GCI has mostly been replaced by Airborne Early Warning and Control (AEW&C) aircraft or more commonly referred to as AWACS ('''A'''irborne '''W'''arning '''A'''nd '''C'''ontrol '''S'''ystem). While AEW&C is expensive and vulnerable in comparison to GCI systems, it has a mobility advantage. In reality a combination of both systems is often used.

The role for an Airforce controller (US) is called an ABM (Air Battle Manager) and a Navy controller (US) is called an AIC (Air Intercept Controller), the roles are very similar but do have some notable differences.

AWACS aircraft are generally speaking big, modified planes with a long-range radar mounted on top. The main radar antenna is mounted on a turntable housed in a circular rotodome, which is 9m (30 feet) in diameter, elliptical in cross-section and 1.8m deep at its centre. The radar system can detect, track and identify low-flying aircraft at approximately 370 km (200 nautical miles) and high-level aircraft at much greater distances.

== AI AWACS in DCS World ==
In DCS World the NATO AWACS comes in the form of the Boeing E-3 Sentry and the Russian equivalent is the Beriev A-50. The player can contact the allied AWACS via the ingame comms menu on the specified frequency in the mission briefing.

=== Comms menu ===
;Vector to bullseye
: The AWACS will provide the player with a bearing and range to bullseye

;Vector to home plate
: The AWACS will provide the player with a bearing and range from bullseye to their home airfield

;Vector to tanker
: The AWACS will provide the player with a bearing and range from bullseye to the tanker

;Request BOGEY DOPE
: The AWACS will provide the player a BRAA call to the closest airborne threat.

;Request PICTURE
: The AWACS will provide the player with BRA calls for each group from bullseye

;DECLARE
: The AWACS will identify friend or foe of a radar locked target

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

=== Understanding BRAA calls ===
[[File:Aspects.png|thumb|frame|right|500x|400px|Figure 1]]
BRAA stands for '''B'''earing '''R'''ange '''A'''ltitude '''A'''spect from your current location.
Aspects other than hot should include a cardinal direction. e.g. "Flank Northwest", "Beam East", "Drag South", "Hot", if an aspect is not provided in a BRAA call, "hot" is assumed.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">BRAA, 183/10, 2 thousand, hot</pre>
would indicate that the target is located at 183 degrees, 10 nautical miles away, and at 2000 feet coming directly towards you.

=== Pronunciation ===
Avoid saying:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi 1-1, Magic, BRAA, 183 for 10 at 2000, hot"</pre>
Instead, it is recommended to omit the "for" and "at", and to use short pauses (here indicated with "..."):
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi one one ... Magic ... BRAA ... one eight zero ... ten ... two thousand ... hot"</pre>

=== Understanding bullseye ===
Bullseye is a fixed point on the map determined pre-mission. All allied aircraft can relate to this point. When receiving a bullseye call, simply use the BRAA format with bullseye as starting point. Bullseye should never be truncated to "Bull" or "Bulls", the full word "Bullseye" should be used (or a coded word, but that would only apply if all players were briefed to it).
[[File:bullseye.png|thumb|frame|center|1000x|800px|Left:Bullseye representation in DCS World - Right: Bullseye details]]

== Human GCI/AWACS ==
In DCS World, players can take the role of GCI/AWACS on multiplayer servers to assist your fellow pilots and friends. In the following sections we’ll go over the basics of airspace management, threat assessment, callsigns, brevity and some useful tools.

Before you begin as a GCI/AWACS controller on a server go over this short checklist:
* Pick a suitable callsign

* Check and confirm the radio frequencies used for GCI/AWACS, general communications and air traffic control
* Tune in the correct frequencies on SRS
* Be in the correct server slot (if necessary)
* Have your tools set up and running
* Announce GCI/AWACS will be available over COMMS and CHAT. State the correct frequency and callsign
<pre style="background-color: #ccc;font-family: 'Lucida Console'">99, <your callsign>, SUNRISE, on <frequency>, check in for control.</pre>
* If you are on the Hoggit Discord and are registering as a GAW GCI controller, the appropriate command on discord would be:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">!gci sunrise GAW <callsign, frequency, any other remarks></pre>
When you're finished with your session, use:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">!gci midnight</pre>

=== Airspace management ===
As a controller your goal is to manage both friendly and hostile airspace. You’ll want to direct your allied flights to intercept enemy threats while at the same time making sure your friendly airspace stays protected.

Divide the airspace you’ll be controlling into two sectors.
# a friendly sector
# a hostile sector

Divide sector 1, your friendly sector, into subsectors based on strategic locations like airfields or a FARPs.

Next, you can assign your available CAP flights to the subsectors you created, and have them patrol or set up orbit. This way you can ensure that
* your allied flights are in proximity to allied aircraft and able to support
* your allied aircraft are not spread out or alone in hostile airspace
* your allied aircraft are in range of a tanker or airfield
* your friendly sector is protected

=== Threat assessment ===
With your airspace divided into sectors and your CAP flights on station you can start intercepting enemy threats. There are 2 major things you want to pay close attention to at all times.
* Where are your allied aircraft in relation to your sectors
* Where are the enemy aircraft in relation to your sectors

Before making a decision to direct your allied flights to intercept, you want to assess the threat
# '''Distance''': what is the distance between the threat and the nearby sector or allied aircraft
# '''Number''': how many enemy aircraft make up the threat
# '''Type''': which type is the enemy threat
# ('''State'''): have they been engaged prior and thus used counter measures and/or weapons

When you have gathered this info you can make a decision to either:
* direct one or more allied aircraft to intercept the threat
* direct one or more aircraft away from the threat to nearby SAM cover
* direct one or more allied aircraft to support engaged allied aircraft

In case you are unsure and need extra information before making a decision, contact your allied flights and ask for a fuel and/or weapons state.

When directing your allied flights to intercept, try to keep them in proximity of other allied flights, so you have enough time to send in support if needed. Do not direct your allied flights into enemy airspace and SAM range without support.

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

=== Callsigns and radio communication ===
When acting as GCI/AWACS controller you want to make sure you have a callsign which
* is clear
* is easy to pronounce
* does not cause confusion
* is not ridiculous

Commonly used callsigns for GCI/AWACS are
* Overlord
* Magic
* Showtime
* Darkstar
* Goliath
* Wizard
* Griffin
* Bigfoot

As GCI/AWACS controller you’ll have to relay a lot of information in a clear, concise and easy to understand manner, usually in a short amount of time. It is important to have a good microphone set up, to speak loud and clear, articulate, not to speak too quickly and use the NATO phonetic alphabet to avoid confusion. We’ll discuss some examples below.

==== Responding to flights checking in ====
When allied flights switch to general comms or designated AWACS comms after take off, they’ll most likely check in on the frequency and let you know who they are and what their intentions are.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F-18, 10 miles North of Anapa, checking in for CAP”</pre>

In the above example a player lets you know who they are, where they are and what their intentions are. You can respond to acknowledge (and task them if desired).
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Radar Contact, Alpha Check, Bullseye 123/45.”</pre>
"Alpha Check Bullseye" is the bearing from the bullseye TO the fighter, and verifies they understand/have the correct bullseye reference point.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima Charlie, standby for tasking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima, Charlie, fly heading 100/20, anchor at Krymsk”</pre>

==== Directing allied aircraft to intercept ====
When directing aircraft to intercept you want to be clear and concise. Start with who you are talking to, who you are and provide a Bullseye or BRAA call (and optional additional information). It is important to pronounce heading as single digits. For example ‘100’ would be ‘one, zero, zero.’ Targeting technically should be done using bullseye and is more helpful to other players (who know how to use it), that said, many players are not familiar with bullseye so BRAA can be used as well.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/40, 15 thousand, flank north west, hostile.”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/60, 500 feet, hot, hostile, 2 contacts, fulcrum.”</pre>

==== Responding to a Bogey Dope request ====
When a player asks for a Bogey Dope, they are asking for the nearest hostile. Locate the aircraft who made the request, and provide them a BRA to the nearest hostile.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA, 257/15, 10 thousand, drag east”</pre>

When there are no hostile aircraft on scope
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Clean”</pre>

==== Responding to a DECLARE request ====
When you receive a DECLARE request, you are asked to identify friend or foe of a locked target.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, Bullseye 204/8, 12 thousand, DECLARE.”</pre>
or use BRAA (not technically correct, but fine here)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, BRAA 090/15, 12 thousand, DECLARE.”</pre>
Response:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Group, Bullseye 204/8, 12 thousand, hostile, single contact, flanker”</pre>
(fill-ins "single contact" and "flanker" are optional)

==== Miscellaneous ====
Sometimes you will need to ask for additional information, or provide additional information.

Return to base (RTB)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, winchester RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 010/35”</pre>

Ask for state
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, say state”</pre>
Typically, yellow means a fighter can take at least one more engagement, where red means a fighter is unable.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, yellow”</pre>
or
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, fuel green, weapons green”</pre>
or
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, 4/1/2 by 7 point 5”</pre>
"4/1/2" is equivalent to 4 active missiles (e.g. AIM-120), 1 semi-active missile (e.g. AIM-7) and 2 infrared missiles (e.g. AIM-9) with 7,500lbs of fuel remaining. "MINUS" can be added to indicate they do not have, or have insufficient guns. (e.g. "Uzi 1-1, 4/1/2, minus, by 7 point 5")

Inform aircraft to wait for instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, standby”</pre>

Correcting mistakes
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, disregard last”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA 070/5, ... correction, BRAA 090/5, 7 thousand, hot”</pre>

Identify unknown transmitting aircraft
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Last transmitting aircraft, state callsign”</pre>

Inform aircraft about incoming missiles or missile launches (unrealistic, generally only possible with F10 map)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, SAM, bearing 090”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, Missile, bearing 090”</pre>

=== Tools ===
==== SRS AWACS mode (eam) ====
The standard SRS radio overlay only displays up to 3 radios and 1 intercom. The AWACS overlay provides up to 10 radios, which you can manually tune and 1 intercom.

You can use SRS without running DCS World, by using the external AWACS mode (EAM). provide your EAM username and the EAM coalition password. The coalition password is provided by the server admin, or in the server briefing. This is not always available.

==== F10 map, icons and the ruler tool ====
The ingame F10 map is where you’ll spend most of your time doing GCI/AWACS. It provides several functions which you can toggle on or off by personal preference
* health bars
* SAM and AAA detection range indicators
* SAM and AAA engagement range indicators
* grid
* labels indicating type and name
* ruler tool

The most important function you’ll use is the ruler tool. It allows you to create a line from point A to point B and provides you with the length in nautical miles and the heading. When intercepting enemy aircraft you can use the ruler tool to draw a line from your allied aircraft A to the hostile aircraft B and read the distance in nautical miles and the heading indicated on the top bar. When you click on the enemy aircraft icon, you can read its altitude, speed in knots, heading and type on the bottom left.

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

==== LotATC ====
LotATC is an optional program one can use to facilitate GCI simulation. The program is fairly easy to use is highly customizable. LotATC provides many features to aid a GCI.

* The creation of persistant BRAAs
* IFF features
* An ATC mode
* The ability to call BRAAs from the bullseye
* A scale which can be used to respond to Picture calls
* The ability to draw on the map

For more information on LotATC and how to use the software see [https://wiki.hoggitworld.com/view/LotATC LotATC]

== Coordinating with human GCI/AWACS ==
A couple guidelines from the players point of view

Inform AWACS when you tune in or tune out of the AWACS frequency.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F18, 10nm North of Anapa, checking in for CAP”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single Mirage 2000, checking in for CAP”</pre>

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, bingo fuel, RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 100/35”</pre>

Do not clutter the AWACS frequency with off-topic chatter, use the correct frequencies as stated in mission briefing.

Do not read back a BRAA call. Simply acknowledge you received and understood the message by saying your callsign. If you did not understand the transmission, ask the AWACS to repeat.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA 100/45, 20 thousand, flank north west”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Uzi 1-1”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, say again”</pre>

Getting started with GCI/AWACS

2022-09-05T15:16:12Z

Marlan: /* Miscellaneous */

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

'''''Disclaimer''''' 
''This guide is compiled using information available to the public and information based on personal experience in DCS World. This guide does not in any way, shape or form represent real life GCI/AWACS operations or techniques nor is it based on real life experience.''

== What is GCI/AWACS ==
[[File:e3_awacs.jpg|thumb|frame|right|Boeing E-3 Sentry]]
GCI stands for '''G'''round-'''C'''ontrolled '''I'''nterception, an air defence tactic which developed during World War I. One or more radar stations or other observational stations are linked to a command communications centre which guides interceptor aircraft to airborne targets.

Today, GCI has mostly been replaced by Airborne Early Warning and Control (AEW&C) aircraft or more commonly referred to as AWACS ('''A'''irborne '''W'''arning '''A'''nd '''C'''ontrol '''S'''ystem). While AEW&C is expensive and vulnerable in comparison to GCI systems, it has a mobility advantage. In reality a combination of both systems is often used.

The role for an Airforce controller (US) is called an ABM (Air Battle Manager) and a Navy controller (US) is called an AIC (Air Intercept Controller), the roles are very similar but do have some notable differences.

AWACS aircraft are generally speaking big, modified planes with a long-range radar mounted on top. The main radar antenna is mounted on a turntable housed in a circular rotodome, which is 9m (30 feet) in diameter, elliptical in cross-section and 1.8m deep at its centre. The radar system can detect, track and identify low-flying aircraft at approximately 370 km (200 nautical miles) and high-level aircraft at much greater distances.

== AI AWACS in DCS World ==
In DCS World the NATO AWACS comes in the form of the Boeing E-3 Sentry and the Russian equivalent is the Beriev A-50. The player can contact the allied AWACS via the ingame comms menu on the specified frequency in the mission briefing.

=== Comms menu ===
;Vector to bullseye
: The AWACS will provide the player with a bearing and range to bullseye

;Vector to home plate
: The AWACS will provide the player with a bearing and range from bullseye to their home airfield

;Vector to tanker
: The AWACS will provide the player with a bearing and range from bullseye to the tanker

;Request BOGEY DOPE
: The AWACS will provide the player a BRAA call to the closest airborne threat.

;Request PICTURE
: The AWACS will provide the player with BRA calls for each group from bullseye

;DECLARE
: The AWACS will identify friend or foe of a radar locked target

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

=== Understanding BRAA calls ===
[[File:Aspects.png|thumb|frame|right|500x|400px|Figure 1]]
BRAA stands for '''B'''earing '''R'''ange '''A'''ltitude '''A'''spect from your current location.
Aspects other than hot should include a cardinal direction. e.g. "Flank Northwest", "Beam East", "Drag South", "Hot", if an aspect is not provided in a BRAA call, "hot" is assumed.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">BRAA, 183/10, 2 thousand, hot</pre>
would indicate that the target is located at 183 degrees, 10 nautical miles away, and at 2000 feet coming directly towards you.

=== Pronunciation ===
Avoid saying:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi 1-1, Magic, BRAA, 183 for 10 at 2000, hot"</pre>
Instead, it is recommended to omit the "for" and "at", and to use short pauses (here indicated with "..."):
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi one one ... Magic ... BRAA ... one eight zero ... ten ... two thousand ... hot"</pre>

=== Understanding bullseye ===
Bullseye is a fixed point on the map determined pre-mission. All allied aircraft can relate to this point. When receiving a bullseye call, simply use the BRAA format with bullseye as starting point. Bullseye should never be truncated to "Bull" or "Bulls", the full word "Bullseye" should be used (or a coded word, but that would only apply if all players were briefed to it).
[[File:bullseye.png|thumb|frame|center|1000x|800px|Left:Bullseye representation in DCS World - Right: Bullseye details]]

== Human GCI/AWACS ==
In DCS World, players can take the role of GCI/AWACS on multiplayer servers to assist your fellow pilots and friends. In the following sections we’ll go over the basics of airspace management, threat assessment, callsigns, brevity and some useful tools.

Before you begin as a GCI/AWACS controller on a server go over this short checklist:
* Pick a suitable callsign

* Check and confirm the radio frequencies used for GCI/AWACS, general communications and air traffic control
* Tune in the correct frequencies on SRS
* Be in the correct server slot (if necessary)
* Have your tools set up and running
* Announce GCI/AWACS will be available over COMMS and CHAT. State the correct frequency and callsign
<pre style="background-color: #ccc;font-family: 'Lucida Console'">99, <your callsign>, SUNRISE, on <frequency>, check in for control.</pre>
* If you are on the Hoggit Discord and are registering as a GAW GCI controller, the appropriate command on discord would be:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">!gci sunrise GAW <callsign, frequency, any other remarks></pre>
When you're finished with your session, use:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">!gci midnight</pre>

=== Airspace management ===
As a controller your goal is to manage both friendly and hostile airspace. You’ll want to direct your allied flights to intercept enemy threats while at the same time making sure your friendly airspace stays protected.

Divide the airspace you’ll be controlling into two sectors.
# a friendly sector
# a hostile sector

Divide sector 1, your friendly sector, into subsectors based on strategic locations like airfields or a FARPs.

Next, you can assign your available CAP flights to the subsectors you created, and have them patrol or set up orbit. This way you can ensure that
* your allied flights are in proximity to allied aircraft and able to support
* your allied aircraft are not spread out or alone in hostile airspace
* your allied aircraft are in range of a tanker or airfield
* your friendly sector is protected

=== Threat assessment ===
With your airspace divided into sectors and your CAP flights on station you can start intercepting enemy threats. There are 2 major things you want to pay close attention to at all times.
* Where are your allied aircraft in relation to your sectors
* Where are the enemy aircraft in relation to your sectors

Before making a decision to direct your allied flights to intercept, you want to assess the threat
# '''Distance''': what is the distance between the threat and the nearby sector or allied aircraft
# '''Number''': how many enemy aircraft make up the threat
# '''Type''': which type is the enemy threat
# ('''State'''): have they been engaged prior and thus used counter measures and/or weapons

When you have gathered this info you can make a decision to either:
* direct one or more allied aircraft to intercept the threat
* direct one or more aircraft away from the threat to nearby SAM cover
* direct one or more allied aircraft to support engaged allied aircraft

In case you are unsure and need extra information before making a decision, contact your allied flights and ask for a fuel and/or weapons state.

When directing your allied flights to intercept, try to keep them in proximity of other allied flights, so you have enough time to send in support if needed. Do not direct your allied flights into enemy airspace and SAM range without support.

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

=== Callsigns and radio communication ===
When acting as GCI/AWACS controller you want to make sure you have a callsign which
* is clear
* is easy to pronounce
* does not cause confusion
* is not ridiculous

Commonly used callsigns for GCI/AWACS are
* Overlord
* Magic
* Showtime
* Darkstar
* Goliath
* Wizard
* Griffin
* Bigfoot

As GCI/AWACS controller you’ll have to relay a lot of information in a clear, concise and easy to understand manner, usually in a short amount of time. It is important to have a good microphone set up, to speak loud and clear, articulate, not to speak too quickly and use the NATO phonetic alphabet to avoid confusion. We’ll discuss some examples below.

==== Responding to flights checking in ====
When allied flights switch to general comms or designated AWACS comms after take off, they’ll most likely check in on the frequency and let you know who they are and what their intentions are.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F-18, 10 miles North of Anapa, checking in for CAP”</pre>

In the above example a player lets you know who they are, where they are and what their intentions are. You can respond to acknowledge (and task them if desired).
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Radar Contact, Alpha Check, Bullseye 123/45.”</pre>
"Alpha Check Bullseye" is the bearing from the bullseye TO the fighter, and verifies they understand/have the correct bullseye reference point.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima Charlie, standby for tasking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima, Charlie, fly heading 100/20, anchor at Krymsk”</pre>

==== Directing allied aircraft to intercept ====
When directing aircraft to intercept you want to be clear and concise. Start with who you are talking to, who you are and provide a Bullseye or BRAA call (and optional additional information). It is important to pronounce heading as single digits. For example ‘100’ would be ‘one, zero, zero.’ Targeting technically should be done using bullseye and is more helpful to other players (who know how to use it), that said, many players are not familiar with bullseye so BRAA can be used as well.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/40, 15 thousand, flank north west, hostile.”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/60, 500 feet, hot, hostile, 2 contacts, fulcrum.”</pre>

==== Responding to a Bogey Dope request ====
When a player asks for a Bogey Dope, they are asking for the nearest hostile. Locate the aircraft who made the request, and provide them a BRA to the nearest hostile.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA, 257/15, 10 thousand, drag east”</pre>

When there are no hostile aircraft on scope
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Clean”</pre>

==== Responding to a DECLARE request ====
When you receive a DECLARE request, you are asked to identify friend or foe of a locked target.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, Bullseye 204/8, 12 thousand, DECLARE.”</pre>
or use BRAA (not technically correct, but fine here)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, BRAA 090/15, 12 thousand, DECLARE.”</pre>
Response:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Group, Bullseye 204/8, 12 thousand, hostile, single contact, flanker”</pre>
(fill-ins "single contact" and "flanker" are optional)

==== Miscellaneous ====
Sometimes you will need to ask for additional information, or provide additional information.

Return to base (RTB)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, winchester RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 010/35”</pre>

Ask for state
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, say state”</pre>
Typically, yellow means a fighter can take at least one more engagement, where red means a fighter is unable.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, yellow”</pre>
or
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, fuel green, weapons green”</pre>
or
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, 4/1/2 by 7 point 5”</pre>
"4/1/2" is equivalent to 4 active missiles (e.g. AIM-120), 1 semi-active missile (e.g. AIM-7) and 2 infrared missiles (e.g. AIM-9) with 7,500lbs of fuel remaining. "MINUS" can be added to indicate they do not have, or have insufficient guns. (e.g. "Uzi 1-1, 4/1/2, minus, by 7 point 5")

Inform aircraft to wait for instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, standby”</pre>

Ignore last transmitted message/instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, disregard last”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA 070/5, ... disregard, BRAA 090/5, 7000, hot”</pre>

Identify unknown transmitting aircraft
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Last transmitting aircraft, state callsign”</pre>

Inform aircraft about incoming missiles or missile launches (unrealistic, generally only possible with F10 map)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, SAM, bearing 090”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, Missile, bearing 090”</pre>

=== Tools ===
==== SRS AWACS mode (eam) ====
The standard SRS radio overlay only displays up to 3 radios and 1 intercom. The AWACS overlay provides up to 10 radios, which you can manually tune and 1 intercom.

You can use SRS without running DCS World, by using the external AWACS mode (EAM). provide your EAM username and the EAM coalition password. The coalition password is provided by the server admin, or in the server briefing. This is not always available.

==== F10 map, icons and the ruler tool ====
The ingame F10 map is where you’ll spend most of your time doing GCI/AWACS. It provides several functions which you can toggle on or off by personal preference
* health bars
* SAM and AAA detection range indicators
* SAM and AAA engagement range indicators
* grid
* labels indicating type and name
* ruler tool

The most important function you’ll use is the ruler tool. It allows you to create a line from point A to point B and provides you with the length in nautical miles and the heading. When intercepting enemy aircraft you can use the ruler tool to draw a line from your allied aircraft A to the hostile aircraft B and read the distance in nautical miles and the heading indicated on the top bar. When you click on the enemy aircraft icon, you can read its altitude, speed in knots, heading and type on the bottom left.

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

==== LotATC ====
LotATC is an optional program one can use to facilitate GCI simulation. The program is fairly easy to use is highly customizable. LotATC provides many features to aid a GCI.

* The creation of persistant BRAAs
* IFF features
* An ATC mode
* The ability to call BRAAs from the bullseye
* A scale which can be used to respond to Picture calls
* The ability to draw on the map

For more information on LotATC and how to use the software see [https://wiki.hoggitworld.com/view/LotATC LotATC]

== Coordinating with human GCI/AWACS ==
A couple guidelines from the players point of view

Inform AWACS when you tune in or tune out of the AWACS frequency.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F18, 10nm North of Anapa, checking in for CAP”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single Mirage 2000, checking in for CAP”</pre>

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, bingo fuel, RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 100/35”</pre>

Do not clutter the AWACS frequency with off-topic chatter, use the correct frequencies as stated in mission briefing.

Do not read back a BRAA call. Simply acknowledge you received and understood the message by saying your callsign. If you did not understand the transmission, ask the AWACS to repeat.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA 100/45, 20 thousand, flank north west”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Uzi 1-1”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, say again”</pre>

Getting started with GCI/AWACS

2022-09-05T15:14:25Z

Marlan: /* Pronunciation */

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

'''''Disclaimer''''' 
''This guide is compiled using information available to the public and information based on personal experience in DCS World. This guide does not in any way, shape or form represent real life GCI/AWACS operations or techniques nor is it based on real life experience.''

== What is GCI/AWACS ==
[[File:e3_awacs.jpg|thumb|frame|right|Boeing E-3 Sentry]]
GCI stands for '''G'''round-'''C'''ontrolled '''I'''nterception, an air defence tactic which developed during World War I. One or more radar stations or other observational stations are linked to a command communications centre which guides interceptor aircraft to airborne targets.

Today, GCI has mostly been replaced by Airborne Early Warning and Control (AEW&C) aircraft or more commonly referred to as AWACS ('''A'''irborne '''W'''arning '''A'''nd '''C'''ontrol '''S'''ystem). While AEW&C is expensive and vulnerable in comparison to GCI systems, it has a mobility advantage. In reality a combination of both systems is often used.

The role for an Airforce controller (US) is called an ABM (Air Battle Manager) and a Navy controller (US) is called an AIC (Air Intercept Controller), the roles are very similar but do have some notable differences.

AWACS aircraft are generally speaking big, modified planes with a long-range radar mounted on top. The main radar antenna is mounted on a turntable housed in a circular rotodome, which is 9m (30 feet) in diameter, elliptical in cross-section and 1.8m deep at its centre. The radar system can detect, track and identify low-flying aircraft at approximately 370 km (200 nautical miles) and high-level aircraft at much greater distances.

== AI AWACS in DCS World ==
In DCS World the NATO AWACS comes in the form of the Boeing E-3 Sentry and the Russian equivalent is the Beriev A-50. The player can contact the allied AWACS via the ingame comms menu on the specified frequency in the mission briefing.

=== Comms menu ===
;Vector to bullseye
: The AWACS will provide the player with a bearing and range to bullseye

;Vector to home plate
: The AWACS will provide the player with a bearing and range from bullseye to their home airfield

;Vector to tanker
: The AWACS will provide the player with a bearing and range from bullseye to the tanker

;Request BOGEY DOPE
: The AWACS will provide the player a BRAA call to the closest airborne threat.

;Request PICTURE
: The AWACS will provide the player with BRA calls for each group from bullseye

;DECLARE
: The AWACS will identify friend or foe of a radar locked target

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

=== Understanding BRAA calls ===
[[File:Aspects.png|thumb|frame|right|500x|400px|Figure 1]]
BRAA stands for '''B'''earing '''R'''ange '''A'''ltitude '''A'''spect from your current location.
Aspects other than hot should include a cardinal direction. e.g. "Flank Northwest", "Beam East", "Drag South", "Hot", if an aspect is not provided in a BRAA call, "hot" is assumed.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">BRAA, 183/10, 2 thousand, hot</pre>
would indicate that the target is located at 183 degrees, 10 nautical miles away, and at 2000 feet coming directly towards you.

=== Pronunciation ===
Avoid saying:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi 1-1, Magic, BRAA, 183 for 10 at 2000, hot"</pre>
Instead, it is recommended to omit the "for" and "at", and to use short pauses (here indicated with "..."):
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi one one ... Magic ... BRAA ... one eight zero ... ten ... two thousand ... hot"</pre>

=== Understanding bullseye ===
Bullseye is a fixed point on the map determined pre-mission. All allied aircraft can relate to this point. When receiving a bullseye call, simply use the BRAA format with bullseye as starting point. Bullseye should never be truncated to "Bull" or "Bulls", the full word "Bullseye" should be used (or a coded word, but that would only apply if all players were briefed to it).
[[File:bullseye.png|thumb|frame|center|1000x|800px|Left:Bullseye representation in DCS World - Right: Bullseye details]]

== Human GCI/AWACS ==
In DCS World, players can take the role of GCI/AWACS on multiplayer servers to assist your fellow pilots and friends. In the following sections we’ll go over the basics of airspace management, threat assessment, callsigns, brevity and some useful tools.

Before you begin as a GCI/AWACS controller on a server go over this short checklist:
* Pick a suitable callsign

* Check and confirm the radio frequencies used for GCI/AWACS, general communications and air traffic control
* Tune in the correct frequencies on SRS
* Be in the correct server slot (if necessary)
* Have your tools set up and running
* Announce GCI/AWACS will be available over COMMS and CHAT. State the correct frequency and callsign
<pre style="background-color: #ccc;font-family: 'Lucida Console'">99, <your callsign>, SUNRISE, on <frequency>, check in for control.</pre>
* If you are on the Hoggit Discord and are registering as a GAW GCI controller, the appropriate command on discord would be:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">!gci sunrise GAW <callsign, frequency, any other remarks></pre>
When you're finished with your session, use:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">!gci midnight</pre>

=== Airspace management ===
As a controller your goal is to manage both friendly and hostile airspace. You’ll want to direct your allied flights to intercept enemy threats while at the same time making sure your friendly airspace stays protected.

Divide the airspace you’ll be controlling into two sectors.
# a friendly sector
# a hostile sector

Divide sector 1, your friendly sector, into subsectors based on strategic locations like airfields or a FARPs.

Next, you can assign your available CAP flights to the subsectors you created, and have them patrol or set up orbit. This way you can ensure that
* your allied flights are in proximity to allied aircraft and able to support
* your allied aircraft are not spread out or alone in hostile airspace
* your allied aircraft are in range of a tanker or airfield
* your friendly sector is protected

=== Threat assessment ===
With your airspace divided into sectors and your CAP flights on station you can start intercepting enemy threats. There are 2 major things you want to pay close attention to at all times.
* Where are your allied aircraft in relation to your sectors
* Where are the enemy aircraft in relation to your sectors

Before making a decision to direct your allied flights to intercept, you want to assess the threat
# '''Distance''': what is the distance between the threat and the nearby sector or allied aircraft
# '''Number''': how many enemy aircraft make up the threat
# '''Type''': which type is the enemy threat
# ('''State'''): have they been engaged prior and thus used counter measures and/or weapons

When you have gathered this info you can make a decision to either:
* direct one or more allied aircraft to intercept the threat
* direct one or more aircraft away from the threat to nearby SAM cover
* direct one or more allied aircraft to support engaged allied aircraft

In case you are unsure and need extra information before making a decision, contact your allied flights and ask for a fuel and/or weapons state.

When directing your allied flights to intercept, try to keep them in proximity of other allied flights, so you have enough time to send in support if needed. Do not direct your allied flights into enemy airspace and SAM range without support.

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

=== Callsigns and radio communication ===
When acting as GCI/AWACS controller you want to make sure you have a callsign which
* is clear
* is easy to pronounce
* does not cause confusion
* is not ridiculous

Commonly used callsigns for GCI/AWACS are
* Overlord
* Magic
* Showtime
* Darkstar
* Goliath
* Wizard
* Griffin
* Bigfoot

As GCI/AWACS controller you’ll have to relay a lot of information in a clear, concise and easy to understand manner, usually in a short amount of time. It is important to have a good microphone set up, to speak loud and clear, articulate, not to speak too quickly and use the NATO phonetic alphabet to avoid confusion. We’ll discuss some examples below.

==== Responding to flights checking in ====
When allied flights switch to general comms or designated AWACS comms after take off, they’ll most likely check in on the frequency and let you know who they are and what their intentions are.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F-18, 10 miles North of Anapa, checking in for CAP”</pre>

In the above example a player lets you know who they are, where they are and what their intentions are. You can respond to acknowledge (and task them if desired).
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Radar Contact, Alpha Check, Bullseye 123/45.”</pre>
"Alpha Check Bullseye" is the bearing from the bullseye TO the fighter, and verifies they understand/have the correct bullseye reference point.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima Charlie, standby for tasking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima, Charlie, fly heading 100/20, anchor at Krymsk”</pre>

==== Directing allied aircraft to intercept ====
When directing aircraft to intercept you want to be clear and concise. Start with who you are talking to, who you are and provide a Bullseye or BRAA call (and optional additional information). It is important to pronounce heading as single digits. For example ‘100’ would be ‘one, zero, zero.’ Targeting technically should be done using bullseye and is more helpful to other players (who know how to use it), that said, many players are not familiar with bullseye so BRAA can be used as well.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/40, 15 thousand, flank north west, hostile.”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/60, 500 feet, hot, hostile, 2 contacts, fulcrum.”</pre>

==== Responding to a Bogey Dope request ====
When a player asks for a Bogey Dope, they are asking for the nearest hostile. Locate the aircraft who made the request, and provide them a BRA to the nearest hostile.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA, 257/15, 10 thousand, drag east”</pre>

When there are no hostile aircraft on scope
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Clean”</pre>

==== Responding to a DECLARE request ====
When you receive a DECLARE request, you are asked to identify friend or foe of a locked target.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, Bullseye 204/8, 12 thousand, DECLARE.”</pre>
or use BRAA (not technically correct, but fine here)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, BRAA 090/15, 12 thousand, DECLARE.”</pre>
Response:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Group, Bullseye 204/8, 12 thousand, hostile, single contact, flanker”</pre>
(fill-ins "single contact" and "flanker" are optional)

==== Miscellaneous ====
Sometimes you will need to ask for additional information, or provide additional information.

Return to base (RTB)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, winchester RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 010/35”</pre>

Ask for state
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, say state”</pre>
Typically, yellow means a fighter can take at least one more engagement, where red means a fighter is unable.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, fuel green, weapons green”</pre>
or
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, 4/1/2 by 7 point 5”</pre>
"4/1/2" is equivalent to 4 active missiles (e.g. AIM-120), 1 semi-active missile (e.g. AIM-7) and 2 infrared missiles (e.g. AIM-9) with 7,500lbs of fuel remaining. "MINUS" can be added to indicate they do not have, or have insufficient guns. (e.g. "Uzi 1-1, 4/1/2, minus, by 7 point 5")

Inform aircraft to wait for instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, standby”</pre>

Ignore last transmitted message/instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, disregard last”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA 070/5, ... disregard, BRAA 090/5, 7000, hot”</pre>

Identify unknown transmitting aircraft
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Last transmitting aircraft, state callsign”</pre>

Inform aircraft about incoming missiles or missile launches (unrealistic, generally only possible with F10 map)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, SAM, bearing 090”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, Missile, bearing 090”</pre>

=== Tools ===
==== SRS AWACS mode (eam) ====
The standard SRS radio overlay only displays up to 3 radios and 1 intercom. The AWACS overlay provides up to 10 radios, which you can manually tune and 1 intercom.

You can use SRS without running DCS World, by using the external AWACS mode (EAM). provide your EAM username and the EAM coalition password. The coalition password is provided by the server admin, or in the server briefing. This is not always available.

==== F10 map, icons and the ruler tool ====
The ingame F10 map is where you’ll spend most of your time doing GCI/AWACS. It provides several functions which you can toggle on or off by personal preference
* health bars
* SAM and AAA detection range indicators
* SAM and AAA engagement range indicators
* grid
* labels indicating type and name
* ruler tool

The most important function you’ll use is the ruler tool. It allows you to create a line from point A to point B and provides you with the length in nautical miles and the heading. When intercepting enemy aircraft you can use the ruler tool to draw a line from your allied aircraft A to the hostile aircraft B and read the distance in nautical miles and the heading indicated on the top bar. When you click on the enemy aircraft icon, you can read its altitude, speed in knots, heading and type on the bottom left.

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

==== LotATC ====
LotATC is an optional program one can use to facilitate GCI simulation. The program is fairly easy to use is highly customizable. LotATC provides many features to aid a GCI.

* The creation of persistant BRAAs
* IFF features
* An ATC mode
* The ability to call BRAAs from the bullseye
* A scale which can be used to respond to Picture calls
* The ability to draw on the map

For more information on LotATC and how to use the software see [https://wiki.hoggitworld.com/view/LotATC LotATC]

== Coordinating with human GCI/AWACS ==
A couple guidelines from the players point of view

Inform AWACS when you tune in or tune out of the AWACS frequency.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F18, 10nm North of Anapa, checking in for CAP”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single Mirage 2000, checking in for CAP”</pre>

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, bingo fuel, RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 100/35”</pre>

Do not clutter the AWACS frequency with off-topic chatter, use the correct frequencies as stated in mission briefing.

Do not read back a BRAA call. Simply acknowledge you received and understood the message by saying your callsign. If you did not understand the transmission, ask the AWACS to repeat.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA 100/45, 20 thousand, flank north west”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Uzi 1-1”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, say again”</pre>

Getting started with GCI/AWACS

2022-09-04T13:43:18Z

Marlan: /* Coordinating with human GCI/AWACS */

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

'''''Disclaimer''''' 
''This guide is compiled using information available to the public and information based on personal experience in DCS World. This guide does not in any way, shape or form represent real life GCI/AWACS operations or techniques nor is it based on real life experience.''

== What is GCI/AWACS ==
[[File:e3_awacs.jpg|thumb|frame|right|Boeing E-3 Sentry]]
GCI stands for '''G'''round-'''C'''ontrolled '''I'''nterception, an air defence tactic which developed during World War I. One or more radar stations or other observational stations are linked to a command communications centre which guides interceptor aircraft to airborne targets.

Today, GCI has mostly been replaced by Airborne Early Warning and Control (AEW&C) aircraft or more commonly referred to as AWACS ('''A'''irborne '''W'''arning '''A'''nd '''C'''ontrol '''S'''ystem). While AEW&C is expensive and vulnerable in comparison to GCI systems, it has a mobility advantage. In reality a combination of both systems is often used.

The role for an Airforce controller (US) is called an ABM (Air Battle Manager) and a Navy controller (US) is called an AIC (Air Intercept Controller), the roles are very similar but do have some notable differences.

AWACS aircraft are generally speaking big, modified planes with a long-range radar mounted on top. The main radar antenna is mounted on a turntable housed in a circular rotodome, which is 9m (30 feet) in diameter, elliptical in cross-section and 1.8m deep at its centre. The radar system can detect, track and identify low-flying aircraft at approximately 370 km (200 nautical miles) and high-level aircraft at much greater distances.

== AI AWACS in DCS World ==
In DCS World the NATO AWACS comes in the form of the Boeing E-3 Sentry and the Russian equivalent is the Beriev A-50. The player can contact the allied AWACS via the ingame comms menu on the specified frequency in the mission briefing.

=== Comms menu ===
;Vector to bullseye
: The AWACS will provide the player with a bearing and range to bullseye

;Vector to home plate
: The AWACS will provide the player with a bearing and range from bullseye to their home airfield

;Vector to tanker
: The AWACS will provide the player with a bearing and range from bullseye to the tanker

;Request BOGEY DOPE
: The AWACS will provide the player a BRAA call to the closest airborne threat.

;Request PICTURE
: The AWACS will provide the player with BRA calls for each group from bullseye

;DECLARE
: The AWACS will identify friend or foe of a radar locked target

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

=== Understanding BRAA calls ===
[[File:Aspects.png|thumb|frame|right|500x|400px|Figure 1]]
BRAA stands for '''B'''earing '''R'''ange '''A'''ltitude '''A'''spect from your current location.
Aspects other than hot should include a cardinal direction. e.g. "Flank Northwest", "Beam East", "Drag South", "Hot", if an aspect is not provided in a BRAA call, "hot" is assumed.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">BRAA, 183/10, 2 thousand, hot</pre>
would indicate that the target is located at 183 degrees, 10 nautical miles away, and at 2000 feet coming directly towards you.

=== Pronunciation ===
Instead of
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi 1-1, Magic, BRAA, 183 for 10 at 2000, hot"</pre>
it is recommended to omit the "for" and "at", and to use short pauses (here indicated with "..."):
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi one one ... Magic ... BRAA ... one eight zero ... ten ... two thousand ... hot"</pre>

=== Understanding bullseye ===
Bullseye is a fixed point on the map determined pre-mission. All allied aircraft can relate to this point. When receiving a bullseye call, simply use the BRAA format with bullseye as starting point. Bullseye should never be truncated to "Bull" or "Bulls", the full word "Bullseye" should be used (or a coded word, but that would only apply if all players were briefed to it).
[[File:bullseye.png|thumb|frame|center|1000x|800px|Left:Bullseye representation in DCS World - Right: Bullseye details]]

== Human GCI/AWACS ==
In DCS World, players can take the role of GCI/AWACS on multiplayer servers to assist your fellow pilots and friends. In the following sections we’ll go over the basics of airspace management, threat assessment, callsigns, brevity and some useful tools.

Before you begin as a GCI/AWACS controller on a server go over this short checklist:
* Pick a suitable callsign

* Check and confirm the radio frequencies used for GCI/AWACS, general communications and air traffic control
* Tune in the correct frequencies on SRS
* Be in the correct server slot (if necessary)
* Have your tools set up and running
* Announce GCI/AWACS will be available over COMMS and CHAT. State the correct frequency and callsign
<pre style="background-color: #ccc;font-family: 'Lucida Console'">99, <your callsign>, SUNRISE, on <frequency>, check in for control.</pre>
* If you are on the Hoggit Discord and are registering as a GAW GCI controller, the appropriate command on discord would be:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">!gci sunrise GAW <callsign, frequency, any other remarks></pre>
When you're finished with your session, use:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">!gci midnight</pre>

=== Airspace management ===
As a controller your goal is to manage both friendly and hostile airspace. You’ll want to direct your allied flights to intercept enemy threats while at the same time making sure your friendly airspace stays protected.

Divide the airspace you’ll be controlling into two sectors.
# a friendly sector
# a hostile sector

Divide sector 1, your friendly sector, into subsectors based on strategic locations like airfields or a FARPs.

Next, you can assign your available CAP flights to the subsectors you created, and have them patrol or set up orbit. This way you can ensure that
* your allied flights are in proximity to allied aircraft and able to support
* your allied aircraft are not spread out or alone in hostile airspace
* your allied aircraft are in range of a tanker or airfield
* your friendly sector is protected

=== Threat assessment ===
With your airspace divided into sectors and your CAP flights on station you can start intercepting enemy threats. There are 2 major things you want to pay close attention to at all times.
* Where are your allied aircraft in relation to your sectors
* Where are the enemy aircraft in relation to your sectors

Before making a decision to direct your allied flights to intercept, you want to assess the threat
# '''Distance''': what is the distance between the threat and the nearby sector or allied aircraft
# '''Number''': how many enemy aircraft make up the threat
# '''Type''': which type is the enemy threat
# ('''State'''): have they been engaged prior and thus used counter measures and/or weapons

When you have gathered this info you can make a decision to either:
* direct one or more allied aircraft to intercept the threat
* direct one or more aircraft away from the threat to nearby SAM cover
* direct one or more allied aircraft to support engaged allied aircraft

In case you are unsure and need extra information before making a decision, contact your allied flights and ask for a fuel and/or weapons state.

When directing your allied flights to intercept, try to keep them in proximity of other allied flights, so you have enough time to send in support if needed. Do not direct your allied flights into enemy airspace and SAM range without support.

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

=== Callsigns and radio communication ===
When acting as GCI/AWACS controller you want to make sure you have a callsign which
* is clear
* is easy to pronounce
* does not cause confusion
* is not ridiculous

Commonly used callsigns for GCI/AWACS are
* Overlord
* Magic
* Showtime
* Darkstar
* Goliath
* Wizard
* Griffin
* Bigfoot

As GCI/AWACS controller you’ll have to relay a lot of information in a clear, concise and easy to understand manner, usually in a short amount of time. It is important to have a good microphone set up, to speak loud and clear, articulate, not to speak too quickly and use the NATO phonetic alphabet to avoid confusion. We’ll discuss some examples below.

==== Responding to flights checking in ====
When allied flights switch to general comms or designated AWACS comms after take off, they’ll most likely check in on the frequency and let you know who they are and what their intentions are.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F-18, 10 miles North of Anapa, checking in for CAP”</pre>

In the above example a player lets you know who they are, where they are and what their intentions are. You can respond to acknowledge (and task them if desired).
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Radar Contact, Alpha Check, Bullseye 123/45.”</pre>
"Alpha Check Bullseye" is the bearing from the bullseye TO the fighter, and verifies they understand/have the correct bullseye reference point.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima Charlie, standby for tasking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima, Charlie, fly heading 100/20, anchor at Krymsk”</pre>

==== Directing allied aircraft to intercept ====
When directing aircraft to intercept you want to be clear and concise. Start with who you are talking to, who you are and provide a Bullseye or BRAA call (and optional additional information). It is important to pronounce heading as single digits. For example ‘100’ would be ‘one, zero, zero.’ Targeting technically should be done using bullseye and is more helpful to other players (who know how to use it), that said, many players are not familiar with bullseye so BRAA can be used as well.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/40, 15 thousand, flank north west, hostile.”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/60, 500 feet, hot, hostile, 2 contacts, fulcrum.”</pre>

==== Responding to a Bogey Dope request ====
When a player asks for a Bogey Dope, they are asking for the nearest hostile. Locate the aircraft who made the request, and provide them a BRA to the nearest hostile.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA, 257/15, 10 thousand, drag east”</pre>

When there are no hostile aircraft on scope
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Clean”</pre>

==== Responding to a DECLARE request ====
When you receive a DECLARE request, you are asked to identify friend or foe of a locked target.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, Bullseye 204/8, 12 thousand, DECLARE.”</pre>
or use BRAA (not technically correct, but fine here)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, BRAA 090/15, 12 thousand, DECLARE.”</pre>
Response:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Group, Bullseye 204/8, 12 thousand, hostile, single contact, flanker”</pre>
(fill-ins "single contact" and "flanker" are optional)

==== Miscellaneous ====
Sometimes you will need to ask for additional information, or provide additional information.

Return to base (RTB)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, winchester RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 010/35”</pre>

Ask for state
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, say state”</pre>
Typically, yellow means a fighter can take at least one more engagement, where red means a fighter is unable.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, fuel green, weapons green”</pre>
or
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, 4/1/2 by 7 point 5”</pre>
"4/1/2" is equivalent to 4 active missiles (e.g. AIM-120), 1 semi-active missile (e.g. AIM-7) and 2 infrared missiles (e.g. AIM-9) with 7,500lbs of fuel remaining. "MINUS" can be added to indicate they do not have, or have insufficient guns. (e.g. "Uzi 1-1, 4/1/2, minus, by 7 point 5")

Inform aircraft to wait for instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, standby”</pre>

Ignore last transmitted message/instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, disregard last”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA 070/5, ... disregard, BRAA 090/5, 7000, hot”</pre>

Identify unknown transmitting aircraft
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Last transmitting aircraft, state callsign”</pre>

Inform aircraft about incoming missiles or missile launches (unrealistic, generally only possible with F10 map)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, SAM, bearing 090”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, Missile, bearing 090”</pre>

=== Tools ===
==== SRS AWACS mode (eam) ====
The standard SRS radio overlay only displays up to 3 radios and 1 intercom. The AWACS overlay provides up to 10 radios, which you can manually tune and 1 intercom.

You can use SRS without running DCS World, by using the external AWACS mode (EAM). provide your EAM username and the EAM coalition password. The coalition password is provided by the server admin, or in the server briefing. This is not always available.

==== F10 map, icons and the ruler tool ====
The ingame F10 map is where you’ll spend most of your time doing GCI/AWACS. It provides several functions which you can toggle on or off by personal preference
* health bars
* SAM and AAA detection range indicators
* SAM and AAA engagement range indicators
* grid
* labels indicating type and name
* ruler tool

The most important function you’ll use is the ruler tool. It allows you to create a line from point A to point B and provides you with the length in nautical miles and the heading. When intercepting enemy aircraft you can use the ruler tool to draw a line from your allied aircraft A to the hostile aircraft B and read the distance in nautical miles and the heading indicated on the top bar. When you click on the enemy aircraft icon, you can read its altitude, speed in knots, heading and type on the bottom left.

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

==== LotATC ====
LotATC is an optional program one can use to facilitate GCI simulation. The program is fairly easy to use is highly customizable. LotATC provides many features to aid a GCI.

* The creation of persistant BRAAs
* IFF features
* An ATC mode
* The ability to call BRAAs from the bullseye
* A scale which can be used to respond to Picture calls
* The ability to draw on the map

For more information on LotATC and how to use the software see [https://wiki.hoggitworld.com/view/LotATC LotATC]

== Coordinating with human GCI/AWACS ==
A couple guidelines from the players point of view

Inform AWACS when you tune in or tune out of the AWACS frequency.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F18, 10nm North of Anapa, checking in for CAP”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single Mirage 2000, checking in for CAP”</pre>

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, bingo fuel, RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 100/35”</pre>

Do not clutter the AWACS frequency with off-topic chatter, use the correct frequencies as stated in mission briefing.

Do not read back a BRAA call. Simply acknowledge you received and understood the message by saying your callsign. If you did not understand the transmission, ask the AWACS to repeat.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA 100/45, 20 thousand, flank north west”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Uzi 1-1”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, say again”</pre>

Getting started with GCI/AWACS

2022-09-04T13:42:03Z

Marlan: /* Human GCI/AWACS */

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

'''''Disclaimer''''' 
''This guide is compiled using information available to the public and information based on personal experience in DCS World. This guide does not in any way, shape or form represent real life GCI/AWACS operations or techniques nor is it based on real life experience.''

== What is GCI/AWACS ==
[[File:e3_awacs.jpg|thumb|frame|right|Boeing E-3 Sentry]]
GCI stands for '''G'''round-'''C'''ontrolled '''I'''nterception, an air defence tactic which developed during World War I. One or more radar stations or other observational stations are linked to a command communications centre which guides interceptor aircraft to airborne targets.

Today, GCI has mostly been replaced by Airborne Early Warning and Control (AEW&C) aircraft or more commonly referred to as AWACS ('''A'''irborne '''W'''arning '''A'''nd '''C'''ontrol '''S'''ystem). While AEW&C is expensive and vulnerable in comparison to GCI systems, it has a mobility advantage. In reality a combination of both systems is often used.

The role for an Airforce controller (US) is called an ABM (Air Battle Manager) and a Navy controller (US) is called an AIC (Air Intercept Controller), the roles are very similar but do have some notable differences.

AWACS aircraft are generally speaking big, modified planes with a long-range radar mounted on top. The main radar antenna is mounted on a turntable housed in a circular rotodome, which is 9m (30 feet) in diameter, elliptical in cross-section and 1.8m deep at its centre. The radar system can detect, track and identify low-flying aircraft at approximately 370 km (200 nautical miles) and high-level aircraft at much greater distances.

== AI AWACS in DCS World ==
In DCS World the NATO AWACS comes in the form of the Boeing E-3 Sentry and the Russian equivalent is the Beriev A-50. The player can contact the allied AWACS via the ingame comms menu on the specified frequency in the mission briefing.

=== Comms menu ===
;Vector to bullseye
: The AWACS will provide the player with a bearing and range to bullseye

;Vector to home plate
: The AWACS will provide the player with a bearing and range from bullseye to their home airfield

;Vector to tanker
: The AWACS will provide the player with a bearing and range from bullseye to the tanker

;Request BOGEY DOPE
: The AWACS will provide the player a BRAA call to the closest airborne threat.

;Request PICTURE
: The AWACS will provide the player with BRA calls for each group from bullseye

;DECLARE
: The AWACS will identify friend or foe of a radar locked target

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

=== Understanding BRAA calls ===
[[File:Aspects.png|thumb|frame|right|500x|400px|Figure 1]]
BRAA stands for '''B'''earing '''R'''ange '''A'''ltitude '''A'''spect from your current location.
Aspects other than hot should include a cardinal direction. e.g. "Flank Northwest", "Beam East", "Drag South", "Hot", if an aspect is not provided in a BRAA call, "hot" is assumed.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">BRAA, 183/10, 2 thousand, hot</pre>
would indicate that the target is located at 183 degrees, 10 nautical miles away, and at 2000 feet coming directly towards you.

=== Pronunciation ===
Instead of
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi 1-1, Magic, BRAA, 183 for 10 at 2000, hot"</pre>
it is recommended to omit the "for" and "at", and to use short pauses (here indicated with "..."):
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi one one ... Magic ... BRAA ... one eight zero ... ten ... two thousand ... hot"</pre>

=== Understanding bullseye ===
Bullseye is a fixed point on the map determined pre-mission. All allied aircraft can relate to this point. When receiving a bullseye call, simply use the BRAA format with bullseye as starting point. Bullseye should never be truncated to "Bull" or "Bulls", the full word "Bullseye" should be used (or a coded word, but that would only apply if all players were briefed to it).
[[File:bullseye.png|thumb|frame|center|1000x|800px|Left:Bullseye representation in DCS World - Right: Bullseye details]]

== Human GCI/AWACS ==
In DCS World, players can take the role of GCI/AWACS on multiplayer servers to assist your fellow pilots and friends. In the following sections we’ll go over the basics of airspace management, threat assessment, callsigns, brevity and some useful tools.

Before you begin as a GCI/AWACS controller on a server go over this short checklist:
* Pick a suitable callsign

* Check and confirm the radio frequencies used for GCI/AWACS, general communications and air traffic control
* Tune in the correct frequencies on SRS
* Be in the correct server slot (if necessary)
* Have your tools set up and running
* Announce GCI/AWACS will be available over COMMS and CHAT. State the correct frequency and callsign
<pre style="background-color: #ccc;font-family: 'Lucida Console'">99, <your callsign>, SUNRISE, on <frequency>, check in for control.</pre>
* If you are on the Hoggit Discord and are registering as a GAW GCI controller, the appropriate command on discord would be:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">!gci sunrise GAW <callsign, frequency, any other remarks></pre>
When you're finished with your session, use:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">!gci midnight</pre>

=== Airspace management ===
As a controller your goal is to manage both friendly and hostile airspace. You’ll want to direct your allied flights to intercept enemy threats while at the same time making sure your friendly airspace stays protected.

Divide the airspace you’ll be controlling into two sectors.
# a friendly sector
# a hostile sector

Divide sector 1, your friendly sector, into subsectors based on strategic locations like airfields or a FARPs.

Next, you can assign your available CAP flights to the subsectors you created, and have them patrol or set up orbit. This way you can ensure that
* your allied flights are in proximity to allied aircraft and able to support
* your allied aircraft are not spread out or alone in hostile airspace
* your allied aircraft are in range of a tanker or airfield
* your friendly sector is protected

=== Threat assessment ===
With your airspace divided into sectors and your CAP flights on station you can start intercepting enemy threats. There are 2 major things you want to pay close attention to at all times.
* Where are your allied aircraft in relation to your sectors
* Where are the enemy aircraft in relation to your sectors

Before making a decision to direct your allied flights to intercept, you want to assess the threat
# '''Distance''': what is the distance between the threat and the nearby sector or allied aircraft
# '''Number''': how many enemy aircraft make up the threat
# '''Type''': which type is the enemy threat
# ('''State'''): have they been engaged prior and thus used counter measures and/or weapons

When you have gathered this info you can make a decision to either:
* direct one or more allied aircraft to intercept the threat
* direct one or more aircraft away from the threat to nearby SAM cover
* direct one or more allied aircraft to support engaged allied aircraft

In case you are unsure and need extra information before making a decision, contact your allied flights and ask for a fuel and/or weapons state.

When directing your allied flights to intercept, try to keep them in proximity of other allied flights, so you have enough time to send in support if needed. Do not direct your allied flights into enemy airspace and SAM range without support.

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

=== Callsigns and radio communication ===
When acting as GCI/AWACS controller you want to make sure you have a callsign which
* is clear
* is easy to pronounce
* does not cause confusion
* is not ridiculous

Commonly used callsigns for GCI/AWACS are
* Overlord
* Magic
* Showtime
* Darkstar
* Goliath
* Wizard
* Griffin
* Bigfoot

As GCI/AWACS controller you’ll have to relay a lot of information in a clear, concise and easy to understand manner, usually in a short amount of time. It is important to have a good microphone set up, to speak loud and clear, articulate, not to speak too quickly and use the NATO phonetic alphabet to avoid confusion. We’ll discuss some examples below.

==== Responding to flights checking in ====
When allied flights switch to general comms or designated AWACS comms after take off, they’ll most likely check in on the frequency and let you know who they are and what their intentions are.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F-18, 10 miles North of Anapa, checking in for CAP”</pre>

In the above example a player lets you know who they are, where they are and what their intentions are. You can respond to acknowledge (and task them if desired).
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Radar Contact, Alpha Check, Bullseye 123/45.”</pre>
"Alpha Check Bullseye" is the bearing from the bullseye TO the fighter, and verifies they understand/have the correct bullseye reference point.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima Charlie, standby for tasking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima, Charlie, fly heading 100/20, anchor at Krymsk”</pre>

==== Directing allied aircraft to intercept ====
When directing aircraft to intercept you want to be clear and concise. Start with who you are talking to, who you are and provide a Bullseye or BRAA call (and optional additional information). It is important to pronounce heading as single digits. For example ‘100’ would be ‘one, zero, zero.’ Targeting technically should be done using bullseye and is more helpful to other players (who know how to use it), that said, many players are not familiar with bullseye so BRAA can be used as well.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/40, 15 thousand, flank north west, hostile.”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/60, 500 feet, hot, hostile, 2 contacts, fulcrum.”</pre>

==== Responding to a Bogey Dope request ====
When a player asks for a Bogey Dope, they are asking for the nearest hostile. Locate the aircraft who made the request, and provide them a BRA to the nearest hostile.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA, 257/15, 10 thousand, drag east”</pre>

When there are no hostile aircraft on scope
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Clean”</pre>

==== Responding to a DECLARE request ====
When you receive a DECLARE request, you are asked to identify friend or foe of a locked target.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, Bullseye 204/8, 12 thousand, DECLARE.”</pre>
or use BRAA (not technically correct, but fine here)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, BRAA 090/15, 12 thousand, DECLARE.”</pre>
Response:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Group, Bullseye 204/8, 12 thousand, hostile, single contact, flanker”</pre>
(fill-ins "single contact" and "flanker" are optional)

==== Miscellaneous ====
Sometimes you will need to ask for additional information, or provide additional information.

Return to base (RTB)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, winchester RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 010/35”</pre>

Ask for state
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, say state”</pre>
Typically, yellow means a fighter can take at least one more engagement, where red means a fighter is unable.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, fuel green, weapons green”</pre>
or
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, 4/1/2 by 7 point 5”</pre>
"4/1/2" is equivalent to 4 active missiles (e.g. AIM-120), 1 semi-active missile (e.g. AIM-7) and 2 infrared missiles (e.g. AIM-9) with 7,500lbs of fuel remaining. "MINUS" can be added to indicate they do not have, or have insufficient guns. (e.g. "Uzi 1-1, 4/1/2, minus, by 7 point 5")

Inform aircraft to wait for instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, standby”</pre>

Ignore last transmitted message/instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, disregard last”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA 070/5, ... disregard, BRAA 090/5, 7000, hot”</pre>

Identify unknown transmitting aircraft
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Last transmitting aircraft, state callsign”</pre>

Inform aircraft about incoming missiles or missile launches (unrealistic, generally only possible with F10 map)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, SAM, bearing 090”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, Missile, bearing 090”</pre>

=== Tools ===
==== SRS AWACS mode (eam) ====
The standard SRS radio overlay only displays up to 3 radios and 1 intercom. The AWACS overlay provides up to 10 radios, which you can manually tune and 1 intercom.

You can use SRS without running DCS World, by using the external AWACS mode (EAM). provide your EAM username and the EAM coalition password. The coalition password is provided by the server admin, or in the server briefing. This is not always available.

==== F10 map, icons and the ruler tool ====
The ingame F10 map is where you’ll spend most of your time doing GCI/AWACS. It provides several functions which you can toggle on or off by personal preference
* health bars
* SAM and AAA detection range indicators
* SAM and AAA engagement range indicators
* grid
* labels indicating type and name
* ruler tool

The most important function you’ll use is the ruler tool. It allows you to create a line from point A to point B and provides you with the length in nautical miles and the heading. When intercepting enemy aircraft you can use the ruler tool to draw a line from your allied aircraft A to the hostile aircraft B and read the distance in nautical miles and the heading indicated on the top bar. When you click on the enemy aircraft icon, you can read its altitude, speed in knots, heading and type on the bottom left.

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

==== LotATC ====
LotATC is an optional program one can use to facilitate GCI simulation. The program is fairly easy to use is highly customizable. LotATC provides many features to aid a GCI.

* The creation of persistant BRAAs
* IFF features
* An ATC mode
* The ability to call BRAAs from the bullseye
* A scale which can be used to respond to Picture calls
* The ability to draw on the map

For more information on LotATC and how to use the software see [https://wiki.hoggitworld.com/view/LotATC LotATC]

== Coordinating with human GCI/AWACS ==
A couple guidelines from the players point of view

Inform AWACS when you tune in or tune out of the AWACS frequency.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F18, 10nm North of Anapa, checking in for CAP”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single Mirage 2000, checking in for CAP”</pre>

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, bingo fuel, RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 100/35”</pre>

Do not clutter the AWACS frequency with off-topic chatter, use the correct frequencies as stated in mission briefing.

Do not read back a BRA call. Simply acknowledge you received and understood the message by saying your callsign. If you did not understand the transmission, ask AWACS to repeat.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA 100/45, 20 thousand, flank north west”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Uzi 1-1”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, say again”</pre>

Getting started with GCI/AWACS

2022-09-04T13:40:11Z

Marlan: /* Human GCI/AWACS */

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

'''''Disclaimer''''' 
''This guide is compiled using information available to the public and information based on personal experience in DCS World. This guide does not in any way, shape or form represent real life GCI/AWACS operations or techniques nor is it based on real life experience.''

== What is GCI/AWACS ==
[[File:e3_awacs.jpg|thumb|frame|right|Boeing E-3 Sentry]]
GCI stands for '''G'''round-'''C'''ontrolled '''I'''nterception, an air defence tactic which developed during World War I. One or more radar stations or other observational stations are linked to a command communications centre which guides interceptor aircraft to airborne targets.

Today, GCI has mostly been replaced by Airborne Early Warning and Control (AEW&C) aircraft or more commonly referred to as AWACS ('''A'''irborne '''W'''arning '''A'''nd '''C'''ontrol '''S'''ystem). While AEW&C is expensive and vulnerable in comparison to GCI systems, it has a mobility advantage. In reality a combination of both systems is often used.

The role for an Airforce controller (US) is called an ABM (Air Battle Manager) and a Navy controller (US) is called an AIC (Air Intercept Controller), the roles are very similar but do have some notable differences.

AWACS aircraft are generally speaking big, modified planes with a long-range radar mounted on top. The main radar antenna is mounted on a turntable housed in a circular rotodome, which is 9m (30 feet) in diameter, elliptical in cross-section and 1.8m deep at its centre. The radar system can detect, track and identify low-flying aircraft at approximately 370 km (200 nautical miles) and high-level aircraft at much greater distances.

== AI AWACS in DCS World ==
In DCS World the NATO AWACS comes in the form of the Boeing E-3 Sentry and the Russian equivalent is the Beriev A-50. The player can contact the allied AWACS via the ingame comms menu on the specified frequency in the mission briefing.

=== Comms menu ===
;Vector to bullseye
: The AWACS will provide the player with a bearing and range to bullseye

;Vector to home plate
: The AWACS will provide the player with a bearing and range from bullseye to their home airfield

;Vector to tanker
: The AWACS will provide the player with a bearing and range from bullseye to the tanker

;Request BOGEY DOPE
: The AWACS will provide the player a BRAA call to the closest airborne threat.

;Request PICTURE
: The AWACS will provide the player with BRA calls for each group from bullseye

;DECLARE
: The AWACS will identify friend or foe of a radar locked target

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

=== Understanding BRAA calls ===
[[File:Aspects.png|thumb|frame|right|500x|400px|Figure 1]]
BRAA stands for '''B'''earing '''R'''ange '''A'''ltitude '''A'''spect from your current location.
Aspects other than hot should include a cardinal direction. e.g. "Flank Northwest", "Beam East", "Drag South", "Hot", if an aspect is not provided in a BRAA call, "hot" is assumed.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">BRAA, 183/10, 2 thousand, hot</pre>
would indicate that the target is located at 183 degrees, 10 nautical miles away, and at 2000 feet coming directly towards you.

=== Pronunciation ===
Instead of
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi 1-1, Magic, BRAA, 183 for 10 at 2000, hot"</pre>
it is recommended to omit the "for" and "at", and to use short pauses (here indicated with "..."):
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi one one ... Magic ... BRAA ... one eight zero ... ten ... two thousand ... hot"</pre>

=== Understanding bullseye ===
Bullseye is a fixed point on the map determined pre-mission. All allied aircraft can relate to this point. When receiving a bullseye call, simply use the BRAA format with bullseye as starting point. Bullseye should never be truncated to "Bull" or "Bulls", the full word "Bullseye" should be used (or a coded word, but that would only apply if all players were briefed to it).
[[File:bullseye.png|thumb|frame|center|1000x|800px|Left:Bullseye representation in DCS World - Right: Bullseye details]]

== Human GCI/AWACS ==
In DCS World, players can take the role of GCI/AWACS on multiplayer servers to assist your fellow pilots and friends. In the following sections we’ll go over the basics of airspace management, threat assessment, callsigns, brevity and some useful tools.

Before you begin as a GCI/AWACS controller on a server go over this short checklist:
* Pick a suitable callsign

* Check and confirm the radio frequencies used for GCI/AWACS, general communications and air traffic control
* Tune in the correct frequencies on SRS
* Be in the correct server slot (if necessary)
* Have your tools set up and running
* Announce GCI/AWACS will be available over COMMS and CHAT. State the correct frequency and callsign
<pre style="background-color: #ccc;font-family: 'Lucida Console'">99, <your callsign>, SUNRISE, on <frequency>, check in for control.</pre>
* If you are on the Hoggit Discord and are registering as a GAW GCI controller, the appropriate command on discord would be "!gci sunrise GAW <callsign, frequency, any other remarks>" command, use "!gci midnight" when you're finished with your session.

=== Airspace management ===
As a controller your goal is to manage both friendly and hostile airspace. You’ll want to direct your allied flights to intercept enemy threats while at the same time making sure your friendly airspace stays protected.

Divide the airspace you’ll be controlling into two sectors.
# a friendly sector
# a hostile sector

Divide sector 1, your friendly sector, into subsectors based on strategic locations like airfields or a FARPs.

Next, you can assign your available CAP flights to the subsectors you created, and have them patrol or set up orbit. This way you can ensure that
* your allied flights are in proximity to allied aircraft and able to support
* your allied aircraft are not spread out or alone in hostile airspace
* your allied aircraft are in range of a tanker or airfield
* your friendly sector is protected

=== Threat assessment ===
With your airspace divided into sectors and your CAP flights on station you can start intercepting enemy threats. There are 2 major things you want to pay close attention to at all times.
* Where are your allied aircraft in relation to your sectors
* Where are the enemy aircraft in relation to your sectors

Before making a decision to direct your allied flights to intercept, you want to assess the threat
# '''Distance''': what is the distance between the threat and the nearby sector or allied aircraft
# '''Number''': how many enemy aircraft make up the threat
# '''Type''': which type is the enemy threat
# ('''State'''): have they been engaged prior and thus used counter measures and/or weapons

When you have gathered this info you can make a decision to either:
* direct one or more allied aircraft to intercept the threat
* direct one or more aircraft away from the threat to nearby SAM cover
* direct one or more allied aircraft to support engaged allied aircraft

In case you are unsure and need extra information before making a decision, contact your allied flights and ask for a fuel and/or weapons state.

When directing your allied flights to intercept, try to keep them in proximity of other allied flights, so you have enough time to send in support if needed. Do not direct your allied flights into enemy airspace and SAM range without support.

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

=== Callsigns and radio communication ===
When acting as GCI/AWACS controller you want to make sure you have a callsign which
* is clear
* is easy to pronounce
* does not cause confusion
* is not ridiculous

Commonly used callsigns for GCI/AWACS are
* Overlord
* Magic
* Showtime
* Darkstar
* Goliath
* Wizard
* Griffin
* Bigfoot

As GCI/AWACS controller you’ll have to relay a lot of information in a clear, concise and easy to understand manner, usually in a short amount of time. It is important to have a good microphone set up, to speak loud and clear, articulate, not to speak too quickly and use the NATO phonetic alphabet to avoid confusion. We’ll discuss some examples below.

==== Responding to flights checking in ====
When allied flights switch to general comms or designated AWACS comms after take off, they’ll most likely check in on the frequency and let you know who they are and what their intentions are.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F-18, 10 miles North of Anapa, checking in for CAP”</pre>

In the above example a player lets you know who they are, where they are and what their intentions are. You can respond to acknowledge (and task them if desired).
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Radar Contact, Alpha Check, Bullseye 123/45.”</pre>
"Alpha Check Bullseye" is the bearing from the bullseye TO the fighter, and verifies they understand/have the correct bullseye reference point.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima Charlie, standby for tasking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima, Charlie, fly heading 100/20, anchor at Krymsk”</pre>

==== Directing allied aircraft to intercept ====
When directing aircraft to intercept you want to be clear and concise. Start with who you are talking to, who you are and provide a Bullseye or BRAA call (and optional additional information). It is important to pronounce heading as single digits. For example ‘100’ would be ‘one, zero, zero.’ Targeting technically should be done using bullseye and is more helpful to other players (who know how to use it), that said, many players are not familiar with bullseye so BRAA can be used as well.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/40, 15 thousand, flank north west, hostile.”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/60, 500 feet, hot, hostile, 2 contacts, fulcrum.”</pre>

==== Responding to a Bogey Dope request ====
When a player asks for a Bogey Dope, they are asking for the nearest hostile. Locate the aircraft who made the request, and provide them a BRA to the nearest hostile.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA, 257/15, 10 thousand, drag east”</pre>

When there are no hostile aircraft on scope
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Clean”</pre>

==== Responding to a DECLARE request ====
When you receive a DECLARE request, you are asked to identify friend or foe of a locked target.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, Bullseye 204/8, 12 thousand, DECLARE.”</pre>
or use BRAA (not technically correct, but fine here)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, BRAA 090/15, 12 thousand, DECLARE.”</pre>
Response:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Group, Bullseye 204/8, 12 thousand, hostile, single contact, flanker”</pre>
(fill-ins "single contact" and "flanker" are optional)

==== Miscellaneous ====
Sometimes you will need to ask for additional information, or provide additional information.

Return to base (RTB)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, winchester RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 010/35”</pre>

Ask for state
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, say state”</pre>
Typically, yellow means a fighter can take at least one more engagement, where red means a fighter is unable.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, fuel green, weapons green”</pre>
or
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, 4/1/2 by 7 point 5”</pre>
"4/1/2" is equivalent to 4 active missiles (e.g. AIM-120), 1 semi-active missile (e.g. AIM-7) and 2 infrared missiles (e.g. AIM-9) with 7,500lbs of fuel remaining. "MINUS" can be added to indicate they do not have, or have insufficient guns. (e.g. "Uzi 1-1, 4/1/2, minus, by 7 point 5")

Inform aircraft to wait for instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, standby”</pre>

Ignore last transmitted message/instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, disregard last”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA 070/5, ... disregard, BRAA 090/5, 7000, hot”</pre>

Identify unknown transmitting aircraft
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Last transmitting aircraft, state callsign”</pre>

Inform aircraft about incoming missiles or missile launches (unrealistic, generally only possible with F10 map)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, SAM, bearing 090”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, Missile, bearing 090”</pre>

=== Tools ===
==== SRS AWACS mode (eam) ====
The standard SRS radio overlay only displays up to 3 radios and 1 intercom. The AWACS overlay provides up to 10 radios, which you can manually tune and 1 intercom.

You can use SRS without running DCS World, by using the external AWACS mode (EAM). provide your EAM username and the EAM coalition password. The coalition password is provided by the server admin, or in the server briefing. This is not always available.

==== F10 map, icons and the ruler tool ====
The ingame F10 map is where you’ll spend most of your time doing GCI/AWACS. It provides several functions which you can toggle on or off by personal preference
* health bars
* SAM and AAA detection range indicators
* SAM and AAA engagement range indicators
* grid
* labels indicating type and name
* ruler tool

The most important function you’ll use is the ruler tool. It allows you to create a line from point A to point B and provides you with the length in nautical miles and the heading. When intercepting enemy aircraft you can use the ruler tool to draw a line from your allied aircraft A to the hostile aircraft B and read the distance in nautical miles and the heading indicated on the top bar. When you click on the enemy aircraft icon, you can read its altitude, speed in knots, heading and type on the bottom left.

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

==== LotATC ====
LotATC is an optional program one can use to facilitate GCI simulation. The program is fairly easy to use is highly customizable. LotATC provides many features to aid a GCI.

* The creation of persistant BRAAs
* IFF features
* An ATC mode
* The ability to call BRAAs from the bullseye
* A scale which can be used to respond to Picture calls
* The ability to draw on the map

For more information on LotATC and how to use the software see [https://wiki.hoggitworld.com/view/LotATC LotATC]

== Coordinating with human GCI/AWACS ==
A couple guidelines from the players point of view

Inform AWACS when you tune in or tune out of the AWACS frequency.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F18, 10nm North of Anapa, checking in for CAP”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single Mirage 2000, checking in for CAP”</pre>

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, bingo fuel, RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 100/35”</pre>

Do not clutter the AWACS frequency with off-topic chatter, use the correct frequencies as stated in mission briefing.

Do not read back a BRA call. Simply acknowledge you received and understood the message by saying your callsign. If you did not understand the transmission, ask AWACS to repeat.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA 100/45, 20 thousand, flank north west”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Uzi 1-1”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, say again”</pre>

Getting started with GCI/AWACS

2022-09-04T13:38:34Z

Marlan: /* Understanding bullseye */

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

'''''Disclaimer''''' 
''This guide is compiled using information available to the public and information based on personal experience in DCS World. This guide does not in any way, shape or form represent real life GCI/AWACS operations or techniques nor is it based on real life experience.''

== What is GCI/AWACS ==
[[File:e3_awacs.jpg|thumb|frame|right|Boeing E-3 Sentry]]
GCI stands for '''G'''round-'''C'''ontrolled '''I'''nterception, an air defence tactic which developed during World War I. One or more radar stations or other observational stations are linked to a command communications centre which guides interceptor aircraft to airborne targets.

Today, GCI has mostly been replaced by Airborne Early Warning and Control (AEW&C) aircraft or more commonly referred to as AWACS ('''A'''irborne '''W'''arning '''A'''nd '''C'''ontrol '''S'''ystem). While AEW&C is expensive and vulnerable in comparison to GCI systems, it has a mobility advantage. In reality a combination of both systems is often used.

The role for an Airforce controller (US) is called an ABM (Air Battle Manager) and a Navy controller (US) is called an AIC (Air Intercept Controller), the roles are very similar but do have some notable differences.

AWACS aircraft are generally speaking big, modified planes with a long-range radar mounted on top. The main radar antenna is mounted on a turntable housed in a circular rotodome, which is 9m (30 feet) in diameter, elliptical in cross-section and 1.8m deep at its centre. The radar system can detect, track and identify low-flying aircraft at approximately 370 km (200 nautical miles) and high-level aircraft at much greater distances.

== AI AWACS in DCS World ==
In DCS World the NATO AWACS comes in the form of the Boeing E-3 Sentry and the Russian equivalent is the Beriev A-50. The player can contact the allied AWACS via the ingame comms menu on the specified frequency in the mission briefing.

=== Comms menu ===
;Vector to bullseye
: The AWACS will provide the player with a bearing and range to bullseye

;Vector to home plate
: The AWACS will provide the player with a bearing and range from bullseye to their home airfield

;Vector to tanker
: The AWACS will provide the player with a bearing and range from bullseye to the tanker

;Request BOGEY DOPE
: The AWACS will provide the player a BRAA call to the closest airborne threat.

;Request PICTURE
: The AWACS will provide the player with BRA calls for each group from bullseye

;DECLARE
: The AWACS will identify friend or foe of a radar locked target

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

=== Understanding BRAA calls ===
[[File:Aspects.png|thumb|frame|right|500x|400px|Figure 1]]
BRAA stands for '''B'''earing '''R'''ange '''A'''ltitude '''A'''spect from your current location.
Aspects other than hot should include a cardinal direction. e.g. "Flank Northwest", "Beam East", "Drag South", "Hot", if an aspect is not provided in a BRAA call, "hot" is assumed.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">BRAA, 183/10, 2 thousand, hot</pre>
would indicate that the target is located at 183 degrees, 10 nautical miles away, and at 2000 feet coming directly towards you.

=== Pronunciation ===
Instead of
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi 1-1, Magic, BRAA, 183 for 10 at 2000, hot"</pre>
it is recommended to omit the "for" and "at", and to use short pauses (here indicated with "..."):
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi one one ... Magic ... BRAA ... one eight zero ... ten ... two thousand ... hot"</pre>

=== Understanding bullseye ===
Bullseye is a fixed point on the map determined pre-mission. All allied aircraft can relate to this point. When receiving a bullseye call, simply use the BRAA format with bullseye as starting point. Bullseye should never be truncated to "Bull" or "Bulls", the full word "Bullseye" should be used (or a coded word, but that would only apply if all players were briefed to it).
[[File:bullseye.png|thumb|frame|center|1000x|800px|Left:Bullseye representation in DCS World - Right: Bullseye details]]

== Human GCI/AWACS ==
In DCS World, players can take the role of GCI/AWACS on multiplayer servers to assist your fellow pilots and friends. In the following sections we’ll go over the basics of airspace management, threat assessment, callsigns, brevity and some useful tools.

Before you begin as a GCI/AWACS controller on a server go over this short checklist:
* Pick a suitable callsign

* Check and confirm the radio frequencies used for GCI/AWACS, general communications and air traffic control
* Tune in the correct frequencies on SRS
* Be in the correct server slot (if necessary)
* Have your tools set up and running
* Announce GCI/AWACS will be available over COMMS and CHAT. State the correct frequency and callsign
<pre style="background-color: #ccc;font-family: 'Lucida Console'">all flights on frequency be advised <callsign> will be available on <frequency> for GCI/AWACS</pre>
* If you are on the Hoggit Discord and are registering as a GAW GCI controller, the appropriate command on discord would be "!gci sunrise GAW <callsign, frequency, any other remarks>" command, use "!gci midnight" when you're finished with your session.

=== Airspace management ===
As a controller your goal is to manage both friendly and hostile airspace. You’ll want to direct your allied flights to intercept enemy threats while at the same time making sure your friendly airspace stays protected.

Divide the airspace you’ll be controlling into two sectors.
# a friendly sector
# a hostile sector

Divide sector 1, your friendly sector, into subsectors based on strategic locations like airfields or a FARPs.

Next, you can assign your available CAP flights to the subsectors you created, and have them patrol or set up orbit. This way you can ensure that
* your allied flights are in proximity to allied aircraft and able to support
* your allied aircraft are not spread out or alone in hostile airspace
* your allied aircraft are in range of a tanker or airfield
* your friendly sector is protected

=== Threat assessment ===
With your airspace divided into sectors and your CAP flights on station you can start intercepting enemy threats. There are 2 major things you want to pay close attention to at all times.
* Where are your allied aircraft in relation to your sectors
* Where are the enemy aircraft in relation to your sectors

Before making a decision to direct your allied flights to intercept, you want to assess the threat
# '''Distance''': what is the distance between the threat and the nearby sector or allied aircraft
# '''Number''': how many enemy aircraft make up the threat
# '''Type''': which type is the enemy threat
# ('''State'''): have they been engaged prior and thus used counter measures and/or weapons

When you have gathered this info you can make a decision to either:
* direct one or more allied aircraft to intercept the threat
* direct one or more aircraft away from the threat to nearby SAM cover
* direct one or more allied aircraft to support engaged allied aircraft

In case you are unsure and need extra information before making a decision, contact your allied flights and ask for a fuel and/or weapons state.

When directing your allied flights to intercept, try to keep them in proximity of other allied flights, so you have enough time to send in support if needed. Do not direct your allied flights into enemy airspace and SAM range without support.

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

=== Callsigns and radio communication ===
When acting as GCI/AWACS controller you want to make sure you have a callsign which
* is clear
* is easy to pronounce
* does not cause confusion
* is not ridiculous

Commonly used callsigns for GCI/AWACS are
* Overlord
* Magic
* Showtime
* Darkstar
* Goliath
* Wizard
* Griffin
* Bigfoot

As GCI/AWACS controller you’ll have to relay a lot of information in a clear, concise and easy to understand manner, usually in a short amount of time. It is important to have a good microphone set up, to speak loud and clear, articulate, not to speak too quickly and use the NATO phonetic alphabet to avoid confusion. We’ll discuss some examples below.

==== Responding to flights checking in ====
When allied flights switch to general comms or designated AWACS comms after take off, they’ll most likely check in on the frequency and let you know who they are and what their intentions are.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F-18, 10 miles North of Anapa, checking in for CAP”</pre>

In the above example a player lets you know who they are, where they are and what their intentions are. You can respond to acknowledge (and task them if desired).
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Radar Contact, Alpha Check, Bullseye 123/45.”</pre>
"Alpha Check Bullseye" is the bearing from the bullseye TO the fighter, and verifies they understand/have the correct bullseye reference point.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima Charlie, standby for tasking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima, Charlie, fly heading 100/20, anchor at Krymsk”</pre>

==== Directing allied aircraft to intercept ====
When directing aircraft to intercept you want to be clear and concise. Start with who you are talking to, who you are and provide a Bullseye or BRAA call (and optional additional information). It is important to pronounce heading as single digits. For example ‘100’ would be ‘one, zero, zero.’ Targeting technically should be done using bullseye and is more helpful to other players (who know how to use it), that said, many players are not familiar with bullseye so BRAA can be used as well.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/40, 15 thousand, flank north west, hostile.”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/60, 500 feet, hot, hostile, 2 contacts, fulcrum.”</pre>

==== Responding to a Bogey Dope request ====
When a player asks for a Bogey Dope, they are asking for the nearest hostile. Locate the aircraft who made the request, and provide them a BRA to the nearest hostile.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA, 257/15, 10 thousand, drag east”</pre>

When there are no hostile aircraft on scope
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Clean”</pre>

==== Responding to a DECLARE request ====
When you receive a DECLARE request, you are asked to identify friend or foe of a locked target.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, Bullseye 204/8, 12 thousand, DECLARE.”</pre>
or use BRAA (not technically correct, but fine here)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, BRAA 090/15, 12 thousand, DECLARE.”</pre>
Response:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Group, Bullseye 204/8, 12 thousand, hostile, single contact, flanker”</pre>
(fill-ins "single contact" and "flanker" are optional)

==== Miscellaneous ====
Sometimes you will need to ask for additional information, or provide additional information.

Return to base (RTB)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, winchester RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 010/35”</pre>

Ask for state
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, say state”</pre>
Typically, yellow means a fighter can take at least one more engagement, where red means a fighter is unable.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, fuel green, weapons green”</pre>
or
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, 4/1/2 by 7 point 5”</pre>
"4/1/2" is equivalent to 4 active missiles (e.g. AIM-120), 1 semi-active missile (e.g. AIM-7) and 2 infrared missiles (e.g. AIM-9) with 7,500lbs of fuel remaining. "MINUS" can be added to indicate they do not have, or have insufficient guns. (e.g. "Uzi 1-1, 4/1/2, minus, by 7 point 5")

Inform aircraft to wait for instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, standby”</pre>

Ignore last transmitted message/instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, disregard last”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA 070/5, ... disregard, BRAA 090/5, 7000, hot”</pre>

Identify unknown transmitting aircraft
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Last transmitting aircraft, state callsign”</pre>

Inform aircraft about incoming missiles or missile launches (unrealistic, generally only possible with F10 map)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, SAM, bearing 090”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, Missile, bearing 090”</pre>

=== Tools ===
==== SRS AWACS mode (eam) ====
The standard SRS radio overlay only displays up to 3 radios and 1 intercom. The AWACS overlay provides up to 10 radios, which you can manually tune and 1 intercom.

You can use SRS without running DCS World, by using the external AWACS mode (EAM). provide your EAM username and the EAM coalition password. The coalition password is provided by the server admin, or in the server briefing. This is not always available.

==== F10 map, icons and the ruler tool ====
The ingame F10 map is where you’ll spend most of your time doing GCI/AWACS. It provides several functions which you can toggle on or off by personal preference
* health bars
* SAM and AAA detection range indicators
* SAM and AAA engagement range indicators
* grid
* labels indicating type and name
* ruler tool

The most important function you’ll use is the ruler tool. It allows you to create a line from point A to point B and provides you with the length in nautical miles and the heading. When intercepting enemy aircraft you can use the ruler tool to draw a line from your allied aircraft A to the hostile aircraft B and read the distance in nautical miles and the heading indicated on the top bar. When you click on the enemy aircraft icon, you can read its altitude, speed in knots, heading and type on the bottom left.

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

==== LotATC ====
LotATC is an optional program one can use to facilitate GCI simulation. The program is fairly easy to use is highly customizable. LotATC provides many features to aid a GCI.

* The creation of persistant BRAAs
* IFF features
* An ATC mode
* The ability to call BRAAs from the bullseye
* A scale which can be used to respond to Picture calls
* The ability to draw on the map

For more information on LotATC and how to use the software see [https://wiki.hoggitworld.com/view/LotATC LotATC]

== Coordinating with human GCI/AWACS ==
A couple guidelines from the players point of view

Inform AWACS when you tune in or tune out of the AWACS frequency.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F18, 10nm North of Anapa, checking in for CAP”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single Mirage 2000, checking in for CAP”</pre>

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, bingo fuel, RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 100/35”</pre>

Do not clutter the AWACS frequency with off-topic chatter, use the correct frequencies as stated in mission briefing.

Do not read back a BRA call. Simply acknowledge you received and understood the message by saying your callsign. If you did not understand the transmission, ask AWACS to repeat.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA 100/45, 20 thousand, flank north west”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Uzi 1-1”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, say again”</pre>

Getting started with GCI/AWACS

2022-09-04T13:36:33Z

Marlan: /* Understanding bullseye */

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

'''''Disclaimer''''' 
''This guide is compiled using information available to the public and information based on personal experience in DCS World. This guide does not in any way, shape or form represent real life GCI/AWACS operations or techniques nor is it based on real life experience.''

== What is GCI/AWACS ==
[[File:e3_awacs.jpg|thumb|frame|right|Boeing E-3 Sentry]]
GCI stands for '''G'''round-'''C'''ontrolled '''I'''nterception, an air defence tactic which developed during World War I. One or more radar stations or other observational stations are linked to a command communications centre which guides interceptor aircraft to airborne targets.

Today, GCI has mostly been replaced by Airborne Early Warning and Control (AEW&C) aircraft or more commonly referred to as AWACS ('''A'''irborne '''W'''arning '''A'''nd '''C'''ontrol '''S'''ystem). While AEW&C is expensive and vulnerable in comparison to GCI systems, it has a mobility advantage. In reality a combination of both systems is often used.

The role for an Airforce controller (US) is called an ABM (Air Battle Manager) and a Navy controller (US) is called an AIC (Air Intercept Controller), the roles are very similar but do have some notable differences.

AWACS aircraft are generally speaking big, modified planes with a long-range radar mounted on top. The main radar antenna is mounted on a turntable housed in a circular rotodome, which is 9m (30 feet) in diameter, elliptical in cross-section and 1.8m deep at its centre. The radar system can detect, track and identify low-flying aircraft at approximately 370 km (200 nautical miles) and high-level aircraft at much greater distances.

== AI AWACS in DCS World ==
In DCS World the NATO AWACS comes in the form of the Boeing E-3 Sentry and the Russian equivalent is the Beriev A-50. The player can contact the allied AWACS via the ingame comms menu on the specified frequency in the mission briefing.

=== Comms menu ===
;Vector to bullseye
: The AWACS will provide the player with a bearing and range to bullseye

;Vector to home plate
: The AWACS will provide the player with a bearing and range from bullseye to their home airfield

;Vector to tanker
: The AWACS will provide the player with a bearing and range from bullseye to the tanker

;Request BOGEY DOPE
: The AWACS will provide the player a BRAA call to the closest airborne threat.

;Request PICTURE
: The AWACS will provide the player with BRA calls for each group from bullseye

;DECLARE
: The AWACS will identify friend or foe of a radar locked target

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

=== Understanding BRAA calls ===
[[File:Aspects.png|thumb|frame|right|500x|400px|Figure 1]]
BRAA stands for '''B'''earing '''R'''ange '''A'''ltitude '''A'''spect from your current location.
Aspects other than hot should include a cardinal direction. e.g. "Flank Northwest", "Beam East", "Drag South", "Hot", if an aspect is not provided in a BRAA call, "hot" is assumed.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">BRAA, 183/10, 2 thousand, hot</pre>
would indicate that the target is located at 183 degrees, 10 nautical miles away, and at 2000 feet coming directly towards you.

=== Pronunciation ===
Instead of
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi 1-1, Magic, BRAA, 183 for 10 at 2000, hot"</pre>
it is recommended to omit the "for" and "at", and to use short pauses (here indicated with "..."):
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi one one ... Magic ... BRAA ... one eight zero ... ten ... two thousand ... hot"</pre>

=== Understanding bullseye ===
Bullseye is a fixed point on the map determined pre-mission. All allied aircraft can relate to this point. When receiving a bullseye call, simply use the BRAA format with bullseye as starting point. Bullseye in DCS is represented with the following symbols
[[File:bullseye.png|thumb|frame|center|1000x|800px|Left:Bullseye representation in DCS World - Right: Bullseye details]]

== Human GCI/AWACS ==
In DCS World, players can take the role of GCI/AWACS on multiplayer servers to assist your fellow pilots and friends. In the following sections we’ll go over the basics of airspace management, threat assessment, callsigns, brevity and some useful tools.

Before you begin as a GCI/AWACS controller on a server go over this short checklist:
* Pick a suitable callsign

* Check and confirm the radio frequencies used for GCI/AWACS, general communications and air traffic control
* Tune in the correct frequencies on SRS
* Be in the correct server slot (if necessary)
* Have your tools set up and running
* Announce GCI/AWACS will be available over COMMS and CHAT. State the correct frequency and callsign
<pre style="background-color: #ccc;font-family: 'Lucida Console'">all flights on frequency be advised <callsign> will be available on <frequency> for GCI/AWACS</pre>
* If you are on the Hoggit Discord and are registering as a GAW GCI controller, the appropriate command on discord would be "!gci sunrise GAW <callsign, frequency, any other remarks>" command, use "!gci midnight" when you're finished with your session.

=== Airspace management ===
As a controller your goal is to manage both friendly and hostile airspace. You’ll want to direct your allied flights to intercept enemy threats while at the same time making sure your friendly airspace stays protected.

Divide the airspace you’ll be controlling into two sectors.
# a friendly sector
# a hostile sector

Divide sector 1, your friendly sector, into subsectors based on strategic locations like airfields or a FARPs.

Next, you can assign your available CAP flights to the subsectors you created, and have them patrol or set up orbit. This way you can ensure that
* your allied flights are in proximity to allied aircraft and able to support
* your allied aircraft are not spread out or alone in hostile airspace
* your allied aircraft are in range of a tanker or airfield
* your friendly sector is protected

=== Threat assessment ===
With your airspace divided into sectors and your CAP flights on station you can start intercepting enemy threats. There are 2 major things you want to pay close attention to at all times.
* Where are your allied aircraft in relation to your sectors
* Where are the enemy aircraft in relation to your sectors

Before making a decision to direct your allied flights to intercept, you want to assess the threat
# '''Distance''': what is the distance between the threat and the nearby sector or allied aircraft
# '''Number''': how many enemy aircraft make up the threat
# '''Type''': which type is the enemy threat
# ('''State'''): have they been engaged prior and thus used counter measures and/or weapons

When you have gathered this info you can make a decision to either:
* direct one or more allied aircraft to intercept the threat
* direct one or more aircraft away from the threat to nearby SAM cover
* direct one or more allied aircraft to support engaged allied aircraft

In case you are unsure and need extra information before making a decision, contact your allied flights and ask for a fuel and/or weapons state.

When directing your allied flights to intercept, try to keep them in proximity of other allied flights, so you have enough time to send in support if needed. Do not direct your allied flights into enemy airspace and SAM range without support.

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

=== Callsigns and radio communication ===
When acting as GCI/AWACS controller you want to make sure you have a callsign which
* is clear
* is easy to pronounce
* does not cause confusion
* is not ridiculous

Commonly used callsigns for GCI/AWACS are
* Overlord
* Magic
* Showtime
* Darkstar
* Goliath
* Wizard
* Griffin
* Bigfoot

As GCI/AWACS controller you’ll have to relay a lot of information in a clear, concise and easy to understand manner, usually in a short amount of time. It is important to have a good microphone set up, to speak loud and clear, articulate, not to speak too quickly and use the NATO phonetic alphabet to avoid confusion. We’ll discuss some examples below.

==== Responding to flights checking in ====
When allied flights switch to general comms or designated AWACS comms after take off, they’ll most likely check in on the frequency and let you know who they are and what their intentions are.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F-18, 10 miles North of Anapa, checking in for CAP”</pre>

In the above example a player lets you know who they are, where they are and what their intentions are. You can respond to acknowledge (and task them if desired).
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Radar Contact, Alpha Check, Bullseye 123/45.”</pre>
"Alpha Check Bullseye" is the bearing from the bullseye TO the fighter, and verifies they understand/have the correct bullseye reference point.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima Charlie, standby for tasking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima, Charlie, fly heading 100/20, anchor at Krymsk”</pre>

==== Directing allied aircraft to intercept ====
When directing aircraft to intercept you want to be clear and concise. Start with who you are talking to, who you are and provide a Bullseye or BRAA call (and optional additional information). It is important to pronounce heading as single digits. For example ‘100’ would be ‘one, zero, zero.’ Targeting technically should be done using bullseye and is more helpful to other players (who know how to use it), that said, many players are not familiar with bullseye so BRAA can be used as well.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/40, 15 thousand, flank north west, hostile.”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/60, 500 feet, hot, hostile, 2 contacts, fulcrum.”</pre>

==== Responding to a Bogey Dope request ====
When a player asks for a Bogey Dope, they are asking for the nearest hostile. Locate the aircraft who made the request, and provide them a BRA to the nearest hostile.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA, 257/15, 10 thousand, drag east”</pre>

When there are no hostile aircraft on scope
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Clean”</pre>

==== Responding to a DECLARE request ====
When you receive a DECLARE request, you are asked to identify friend or foe of a locked target.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, Bullseye 204/8, 12 thousand, DECLARE.”</pre>
or use BRAA (not technically correct, but fine here)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, BRAA 090/15, 12 thousand, DECLARE.”</pre>
Response:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Group, Bullseye 204/8, 12 thousand, hostile, single contact, flanker”</pre>
(fill-ins "single contact" and "flanker" are optional)

==== Miscellaneous ====
Sometimes you will need to ask for additional information, or provide additional information.

Return to base (RTB)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, winchester RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 010/35”</pre>

Ask for state
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, say state”</pre>
Typically, yellow means a fighter can take at least one more engagement, where red means a fighter is unable.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, fuel green, weapons green”</pre>
or
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, 4/1/2 by 7 point 5”</pre>
"4/1/2" is equivalent to 4 active missiles (e.g. AIM-120), 1 semi-active missile (e.g. AIM-7) and 2 infrared missiles (e.g. AIM-9) with 7,500lbs of fuel remaining. "MINUS" can be added to indicate they do not have, or have insufficient guns. (e.g. "Uzi 1-1, 4/1/2, minus, by 7 point 5")

Inform aircraft to wait for instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, standby”</pre>

Ignore last transmitted message/instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, disregard last”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA 070/5, ... disregard, BRAA 090/5, 7000, hot”</pre>

Identify unknown transmitting aircraft
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Last transmitting aircraft, state callsign”</pre>

Inform aircraft about incoming missiles or missile launches (unrealistic, generally only possible with F10 map)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, SAM, bearing 090”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, Missile, bearing 090”</pre>

=== Tools ===
==== SRS AWACS mode (eam) ====
The standard SRS radio overlay only displays up to 3 radios and 1 intercom. The AWACS overlay provides up to 10 radios, which you can manually tune and 1 intercom.

You can use SRS without running DCS World, by using the external AWACS mode (EAM). provide your EAM username and the EAM coalition password. The coalition password is provided by the server admin, or in the server briefing. This is not always available.

==== F10 map, icons and the ruler tool ====
The ingame F10 map is where you’ll spend most of your time doing GCI/AWACS. It provides several functions which you can toggle on or off by personal preference
* health bars
* SAM and AAA detection range indicators
* SAM and AAA engagement range indicators
* grid
* labels indicating type and name
* ruler tool

The most important function you’ll use is the ruler tool. It allows you to create a line from point A to point B and provides you with the length in nautical miles and the heading. When intercepting enemy aircraft you can use the ruler tool to draw a line from your allied aircraft A to the hostile aircraft B and read the distance in nautical miles and the heading indicated on the top bar. When you click on the enemy aircraft icon, you can read its altitude, speed in knots, heading and type on the bottom left.

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

==== LotATC ====
LotATC is an optional program one can use to facilitate GCI simulation. The program is fairly easy to use is highly customizable. LotATC provides many features to aid a GCI.

* The creation of persistant BRAAs
* IFF features
* An ATC mode
* The ability to call BRAAs from the bullseye
* A scale which can be used to respond to Picture calls
* The ability to draw on the map

For more information on LotATC and how to use the software see [https://wiki.hoggitworld.com/view/LotATC LotATC]

== Coordinating with human GCI/AWACS ==
A couple guidelines from the players point of view

Inform AWACS when you tune in or tune out of the AWACS frequency.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F18, 10nm North of Anapa, checking in for CAP”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single Mirage 2000, checking in for CAP”</pre>

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, bingo fuel, RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 100/35”</pre>

Do not clutter the AWACS frequency with off-topic chatter, use the correct frequencies as stated in mission briefing.

Do not read back a BRA call. Simply acknowledge you received and understood the message by saying your callsign. If you did not understand the transmission, ask AWACS to repeat.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA 100/45, 20 thousand, flank north west”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Uzi 1-1”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, say again”</pre>

Getting started with GCI/AWACS

2022-09-04T13:36:18Z

Marlan: /* What is GCI/AWACS */

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

'''''Disclaimer''''' 
''This guide is compiled using information available to the public and information based on personal experience in DCS World. This guide does not in any way, shape or form represent real life GCI/AWACS operations or techniques nor is it based on real life experience.''

== What is GCI/AWACS ==
[[File:e3_awacs.jpg|thumb|frame|right|Boeing E-3 Sentry]]
GCI stands for '''G'''round-'''C'''ontrolled '''I'''nterception, an air defence tactic which developed during World War I. One or more radar stations or other observational stations are linked to a command communications centre which guides interceptor aircraft to airborne targets.

Today, GCI has mostly been replaced by Airborne Early Warning and Control (AEW&C) aircraft or more commonly referred to as AWACS ('''A'''irborne '''W'''arning '''A'''nd '''C'''ontrol '''S'''ystem). While AEW&C is expensive and vulnerable in comparison to GCI systems, it has a mobility advantage. In reality a combination of both systems is often used.

The role for an Airforce controller (US) is called an ABM (Air Battle Manager) and a Navy controller (US) is called an AIC (Air Intercept Controller), the roles are very similar but do have some notable differences.

AWACS aircraft are generally speaking big, modified planes with a long-range radar mounted on top. The main radar antenna is mounted on a turntable housed in a circular rotodome, which is 9m (30 feet) in diameter, elliptical in cross-section and 1.8m deep at its centre. The radar system can detect, track and identify low-flying aircraft at approximately 370 km (200 nautical miles) and high-level aircraft at much greater distances.

== AI AWACS in DCS World ==
In DCS World the NATO AWACS comes in the form of the Boeing E-3 Sentry and the Russian equivalent is the Beriev A-50. The player can contact the allied AWACS via the ingame comms menu on the specified frequency in the mission briefing.

=== Comms menu ===
;Vector to bullseye
: The AWACS will provide the player with a bearing and range to bullseye

;Vector to home plate
: The AWACS will provide the player with a bearing and range from bullseye to their home airfield

;Vector to tanker
: The AWACS will provide the player with a bearing and range from bullseye to the tanker

;Request BOGEY DOPE
: The AWACS will provide the player a BRAA call to the closest airborne threat.

;Request PICTURE
: The AWACS will provide the player with BRA calls for each group from bullseye

;DECLARE
: The AWACS will identify friend or foe of a radar locked target

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

=== Understanding BRAA calls ===
[[File:Aspects.png|thumb|frame|right|500x|400px|Figure 1]]
BRAA stands for '''B'''earing '''R'''ange '''A'''ltitude '''A'''spect from your current location.
Aspects other than hot should include a cardinal direction. e.g. "Flank Northwest", "Beam East", "Drag South", "Hot", if an aspect is not provided in a BRAA call, "hot" is assumed.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">BRAA, 183/10, 2 thousand, hot</pre>
would indicate that the target is located at 183 degrees, 10 nautical miles away, and at 2000 feet coming directly towards you.

=== Pronunciation ===
Instead of
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi 1-1, Magic, BRAA, 183 for 10 at 2000, hot"</pre>
it is recommended to omit the "for" and "at", and to use short pauses (here indicated with "..."):
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi one one ... Magic ... BRAA ... one eight zero ... ten ... two thousand ... hot"</pre>

=== Understanding bullseye ===
Bullseye is a fixed point on the map determined pre-mission. All allied aircraft can relate to this point. When receiving a bullseye call, simply use the BRA format with bullseye as starting point. Bullseye in DCS is represented with the following symbols
[[File:bullseye.png|thumb|frame|center|1000x|800px|Left:Bullseye representation in DCS World - Right: Bullseye details]]

== Human GCI/AWACS ==
In DCS World, players can take the role of GCI/AWACS on multiplayer servers to assist your fellow pilots and friends. In the following sections we’ll go over the basics of airspace management, threat assessment, callsigns, brevity and some useful tools.

Before you begin as a GCI/AWACS controller on a server go over this short checklist:
* Pick a suitable callsign

* Check and confirm the radio frequencies used for GCI/AWACS, general communications and air traffic control
* Tune in the correct frequencies on SRS
* Be in the correct server slot (if necessary)
* Have your tools set up and running
* Announce GCI/AWACS will be available over COMMS and CHAT. State the correct frequency and callsign
<pre style="background-color: #ccc;font-family: 'Lucida Console'">all flights on frequency be advised <callsign> will be available on <frequency> for GCI/AWACS</pre>
* If you are on the Hoggit Discord and are registering as a GAW GCI controller, the appropriate command on discord would be "!gci sunrise GAW <callsign, frequency, any other remarks>" command, use "!gci midnight" when you're finished with your session.

=== Airspace management ===
As a controller your goal is to manage both friendly and hostile airspace. You’ll want to direct your allied flights to intercept enemy threats while at the same time making sure your friendly airspace stays protected.

Divide the airspace you’ll be controlling into two sectors.
# a friendly sector
# a hostile sector

Divide sector 1, your friendly sector, into subsectors based on strategic locations like airfields or a FARPs.

Next, you can assign your available CAP flights to the subsectors you created, and have them patrol or set up orbit. This way you can ensure that
* your allied flights are in proximity to allied aircraft and able to support
* your allied aircraft are not spread out or alone in hostile airspace
* your allied aircraft are in range of a tanker or airfield
* your friendly sector is protected

=== Threat assessment ===
With your airspace divided into sectors and your CAP flights on station you can start intercepting enemy threats. There are 2 major things you want to pay close attention to at all times.
* Where are your allied aircraft in relation to your sectors
* Where are the enemy aircraft in relation to your sectors

Before making a decision to direct your allied flights to intercept, you want to assess the threat
# '''Distance''': what is the distance between the threat and the nearby sector or allied aircraft
# '''Number''': how many enemy aircraft make up the threat
# '''Type''': which type is the enemy threat
# ('''State'''): have they been engaged prior and thus used counter measures and/or weapons

When you have gathered this info you can make a decision to either:
* direct one or more allied aircraft to intercept the threat
* direct one or more aircraft away from the threat to nearby SAM cover
* direct one or more allied aircraft to support engaged allied aircraft

In case you are unsure and need extra information before making a decision, contact your allied flights and ask for a fuel and/or weapons state.

When directing your allied flights to intercept, try to keep them in proximity of other allied flights, so you have enough time to send in support if needed. Do not direct your allied flights into enemy airspace and SAM range without support.

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

=== Callsigns and radio communication ===
When acting as GCI/AWACS controller you want to make sure you have a callsign which
* is clear
* is easy to pronounce
* does not cause confusion
* is not ridiculous

Commonly used callsigns for GCI/AWACS are
* Overlord
* Magic
* Showtime
* Darkstar
* Goliath
* Wizard
* Griffin
* Bigfoot

As GCI/AWACS controller you’ll have to relay a lot of information in a clear, concise and easy to understand manner, usually in a short amount of time. It is important to have a good microphone set up, to speak loud and clear, articulate, not to speak too quickly and use the NATO phonetic alphabet to avoid confusion. We’ll discuss some examples below.

==== Responding to flights checking in ====
When allied flights switch to general comms or designated AWACS comms after take off, they’ll most likely check in on the frequency and let you know who they are and what their intentions are.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F-18, 10 miles North of Anapa, checking in for CAP”</pre>

In the above example a player lets you know who they are, where they are and what their intentions are. You can respond to acknowledge (and task them if desired).
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Radar Contact, Alpha Check, Bullseye 123/45.”</pre>
"Alpha Check Bullseye" is the bearing from the bullseye TO the fighter, and verifies they understand/have the correct bullseye reference point.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima Charlie, standby for tasking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima, Charlie, fly heading 100/20, anchor at Krymsk”</pre>

==== Directing allied aircraft to intercept ====
When directing aircraft to intercept you want to be clear and concise. Start with who you are talking to, who you are and provide a Bullseye or BRAA call (and optional additional information). It is important to pronounce heading as single digits. For example ‘100’ would be ‘one, zero, zero.’ Targeting technically should be done using bullseye and is more helpful to other players (who know how to use it), that said, many players are not familiar with bullseye so BRAA can be used as well.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/40, 15 thousand, flank north west, hostile.”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/60, 500 feet, hot, hostile, 2 contacts, fulcrum.”</pre>

==== Responding to a Bogey Dope request ====
When a player asks for a Bogey Dope, they are asking for the nearest hostile. Locate the aircraft who made the request, and provide them a BRA to the nearest hostile.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA, 257/15, 10 thousand, drag east”</pre>

When there are no hostile aircraft on scope
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Clean”</pre>

==== Responding to a DECLARE request ====
When you receive a DECLARE request, you are asked to identify friend or foe of a locked target.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, Bullseye 204/8, 12 thousand, DECLARE.”</pre>
or use BRAA (not technically correct, but fine here)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, BRAA 090/15, 12 thousand, DECLARE.”</pre>
Response:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Group, Bullseye 204/8, 12 thousand, hostile, single contact, flanker”</pre>
(fill-ins "single contact" and "flanker" are optional)

==== Miscellaneous ====
Sometimes you will need to ask for additional information, or provide additional information.

Return to base (RTB)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, winchester RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 010/35”</pre>

Ask for state
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, say state”</pre>
Typically, yellow means a fighter can take at least one more engagement, where red means a fighter is unable.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, fuel green, weapons green”</pre>
or
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, 4/1/2 by 7 point 5”</pre>
"4/1/2" is equivalent to 4 active missiles (e.g. AIM-120), 1 semi-active missile (e.g. AIM-7) and 2 infrared missiles (e.g. AIM-9) with 7,500lbs of fuel remaining. "MINUS" can be added to indicate they do not have, or have insufficient guns. (e.g. "Uzi 1-1, 4/1/2, minus, by 7 point 5")

Inform aircraft to wait for instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, standby”</pre>

Ignore last transmitted message/instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, disregard last”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA 070/5, ... disregard, BRAA 090/5, 7000, hot”</pre>

Identify unknown transmitting aircraft
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Last transmitting aircraft, state callsign”</pre>

Inform aircraft about incoming missiles or missile launches (unrealistic, generally only possible with F10 map)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, SAM, bearing 090”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, Missile, bearing 090”</pre>

=== Tools ===
==== SRS AWACS mode (eam) ====
The standard SRS radio overlay only displays up to 3 radios and 1 intercom. The AWACS overlay provides up to 10 radios, which you can manually tune and 1 intercom.

You can use SRS without running DCS World, by using the external AWACS mode (EAM). provide your EAM username and the EAM coalition password. The coalition password is provided by the server admin, or in the server briefing. This is not always available.

==== F10 map, icons and the ruler tool ====
The ingame F10 map is where you’ll spend most of your time doing GCI/AWACS. It provides several functions which you can toggle on or off by personal preference
* health bars
* SAM and AAA detection range indicators
* SAM and AAA engagement range indicators
* grid
* labels indicating type and name
* ruler tool

The most important function you’ll use is the ruler tool. It allows you to create a line from point A to point B and provides you with the length in nautical miles and the heading. When intercepting enemy aircraft you can use the ruler tool to draw a line from your allied aircraft A to the hostile aircraft B and read the distance in nautical miles and the heading indicated on the top bar. When you click on the enemy aircraft icon, you can read its altitude, speed in knots, heading and type on the bottom left.

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

==== LotATC ====
LotATC is an optional program one can use to facilitate GCI simulation. The program is fairly easy to use is highly customizable. LotATC provides many features to aid a GCI.

* The creation of persistant BRAAs
* IFF features
* An ATC mode
* The ability to call BRAAs from the bullseye
* A scale which can be used to respond to Picture calls
* The ability to draw on the map

For more information on LotATC and how to use the software see [https://wiki.hoggitworld.com/view/LotATC LotATC]

== Coordinating with human GCI/AWACS ==
A couple guidelines from the players point of view

Inform AWACS when you tune in or tune out of the AWACS frequency.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F18, 10nm North of Anapa, checking in for CAP”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single Mirage 2000, checking in for CAP”</pre>

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, bingo fuel, RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 100/35”</pre>

Do not clutter the AWACS frequency with off-topic chatter, use the correct frequencies as stated in mission briefing.

Do not read back a BRA call. Simply acknowledge you received and understood the message by saying your callsign. If you did not understand the transmission, ask AWACS to repeat.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA 100/45, 20 thousand, flank north west”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Uzi 1-1”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, say again”</pre>

Getting started with GCI/AWACS

2022-09-04T13:35:48Z

Marlan: /* What is GCI/AWACS */

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

'''''Disclaimer''''' 
''This guide is compiled using information available to the public and information based on personal experience in DCS World. This guide does not in any way, shape or form represent real life GCI/AWACS operations or techniques nor is it based on real life experience.''

== What is GCI/AWACS ==
[[File:e3_awacs.jpg|thumb|frame|right|Boeing E-3 Sentry]]
GCI stands for '''G'''round-'''C'''ontrolled '''I'''nterception, an air defence tactic which developed during World War I. One or more radar stations or other observational stations are linked to a command communications centre which guides interceptor aircraft to airborne targets.

Today, GCI has mostly been replaced by Airborne Early Warning and Control (AEW&C) aircraft or more commonly referred to as AWACS ('''A'''irborne '''W'''arning '''A'''nd '''C'''ontrol '''S'''ystem). While AEW&C is expensive and vulnerable in comparison to GCI systems, it has a mobility advantage. In reality a combination of both systems is often used.

The role for an Airforce controller (in the US at least) is called an ABM (Air Battle Manager) and a Navy controller (US) is called an AIC (Air Intercept Controller), the roles are very similar but do have some notable differences.

AWACS aircraft are generally speaking big, modified planes with a long-range radar mounted on top. The main radar antenna is mounted on a turntable housed in a circular rotodome, which is 9m (30 feet) in diameter, elliptical in cross-section and 1.8m deep at its centre. The radar system can detect, track and identify low-flying aircraft at approximately 370 km (200 nautical miles) and high-level aircraft at much greater distances.

== AI AWACS in DCS World ==
In DCS World the NATO AWACS comes in the form of the Boeing E-3 Sentry and the Russian equivalent is the Beriev A-50. The player can contact the allied AWACS via the ingame comms menu on the specified frequency in the mission briefing.

=== Comms menu ===
;Vector to bullseye
: The AWACS will provide the player with a bearing and range to bullseye

;Vector to home plate
: The AWACS will provide the player with a bearing and range from bullseye to their home airfield

;Vector to tanker
: The AWACS will provide the player with a bearing and range from bullseye to the tanker

;Request BOGEY DOPE
: The AWACS will provide the player a BRAA call to the closest airborne threat.

;Request PICTURE
: The AWACS will provide the player with BRA calls for each group from bullseye

;DECLARE
: The AWACS will identify friend or foe of a radar locked target

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

=== Understanding BRAA calls ===
[[File:Aspects.png|thumb|frame|right|500x|400px|Figure 1]]
BRAA stands for '''B'''earing '''R'''ange '''A'''ltitude '''A'''spect from your current location.
Aspects other than hot should include a cardinal direction. e.g. "Flank Northwest", "Beam East", "Drag South", "Hot", if an aspect is not provided in a BRAA call, "hot" is assumed.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">BRAA, 183/10, 2 thousand, hot</pre>
would indicate that the target is located at 183 degrees, 10 nautical miles away, and at 2000 feet coming directly towards you.

=== Pronunciation ===
Instead of
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi 1-1, Magic, BRAA, 183 for 10 at 2000, hot"</pre>
it is recommended to omit the "for" and "at", and to use short pauses (here indicated with "..."):
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi one one ... Magic ... BRAA ... one eight zero ... ten ... two thousand ... hot"</pre>

=== Understanding bullseye ===
Bullseye is a fixed point on the map determined pre-mission. All allied aircraft can relate to this point. When receiving a bullseye call, simply use the BRA format with bullseye as starting point. Bullseye in DCS is represented with the following symbols
[[File:bullseye.png|thumb|frame|center|1000x|800px|Left:Bullseye representation in DCS World - Right: Bullseye details]]

== Human GCI/AWACS ==
In DCS World, players can take the role of GCI/AWACS on multiplayer servers to assist your fellow pilots and friends. In the following sections we’ll go over the basics of airspace management, threat assessment, callsigns, brevity and some useful tools.

Before you begin as a GCI/AWACS controller on a server go over this short checklist:
* Pick a suitable callsign

* Check and confirm the radio frequencies used for GCI/AWACS, general communications and air traffic control
* Tune in the correct frequencies on SRS
* Be in the correct server slot (if necessary)
* Have your tools set up and running
* Announce GCI/AWACS will be available over COMMS and CHAT. State the correct frequency and callsign
<pre style="background-color: #ccc;font-family: 'Lucida Console'">all flights on frequency be advised <callsign> will be available on <frequency> for GCI/AWACS</pre>
* If you are on the Hoggit Discord and are registering as a GAW GCI controller, the appropriate command on discord would be "!gci sunrise GAW <callsign, frequency, any other remarks>" command, use "!gci midnight" when you're finished with your session.

=== Airspace management ===
As a controller your goal is to manage both friendly and hostile airspace. You’ll want to direct your allied flights to intercept enemy threats while at the same time making sure your friendly airspace stays protected.

Divide the airspace you’ll be controlling into two sectors.
# a friendly sector
# a hostile sector

Divide sector 1, your friendly sector, into subsectors based on strategic locations like airfields or a FARPs.

Next, you can assign your available CAP flights to the subsectors you created, and have them patrol or set up orbit. This way you can ensure that
* your allied flights are in proximity to allied aircraft and able to support
* your allied aircraft are not spread out or alone in hostile airspace
* your allied aircraft are in range of a tanker or airfield
* your friendly sector is protected

=== Threat assessment ===
With your airspace divided into sectors and your CAP flights on station you can start intercepting enemy threats. There are 2 major things you want to pay close attention to at all times.
* Where are your allied aircraft in relation to your sectors
* Where are the enemy aircraft in relation to your sectors

Before making a decision to direct your allied flights to intercept, you want to assess the threat
# '''Distance''': what is the distance between the threat and the nearby sector or allied aircraft
# '''Number''': how many enemy aircraft make up the threat
# '''Type''': which type is the enemy threat
# ('''State'''): have they been engaged prior and thus used counter measures and/or weapons

When you have gathered this info you can make a decision to either:
* direct one or more allied aircraft to intercept the threat
* direct one or more aircraft away from the threat to nearby SAM cover
* direct one or more allied aircraft to support engaged allied aircraft

In case you are unsure and need extra information before making a decision, contact your allied flights and ask for a fuel and/or weapons state.

When directing your allied flights to intercept, try to keep them in proximity of other allied flights, so you have enough time to send in support if needed. Do not direct your allied flights into enemy airspace and SAM range without support.

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

=== Callsigns and radio communication ===
When acting as GCI/AWACS controller you want to make sure you have a callsign which
* is clear
* is easy to pronounce
* does not cause confusion
* is not ridiculous

Commonly used callsigns for GCI/AWACS are
* Overlord
* Magic
* Showtime
* Darkstar
* Goliath
* Wizard
* Griffin
* Bigfoot

As GCI/AWACS controller you’ll have to relay a lot of information in a clear, concise and easy to understand manner, usually in a short amount of time. It is important to have a good microphone set up, to speak loud and clear, articulate, not to speak too quickly and use the NATO phonetic alphabet to avoid confusion. We’ll discuss some examples below.

==== Responding to flights checking in ====
When allied flights switch to general comms or designated AWACS comms after take off, they’ll most likely check in on the frequency and let you know who they are and what their intentions are.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F-18, 10 miles North of Anapa, checking in for CAP”</pre>

In the above example a player lets you know who they are, where they are and what their intentions are. You can respond to acknowledge (and task them if desired).
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Radar Contact, Alpha Check, Bullseye 123/45.”</pre>
"Alpha Check Bullseye" is the bearing from the bullseye TO the fighter, and verifies they understand/have the correct bullseye reference point.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima Charlie, standby for tasking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima, Charlie, fly heading 100/20, anchor at Krymsk”</pre>

==== Directing allied aircraft to intercept ====
When directing aircraft to intercept you want to be clear and concise. Start with who you are talking to, who you are and provide a Bullseye or BRAA call (and optional additional information). It is important to pronounce heading as single digits. For example ‘100’ would be ‘one, zero, zero.’ Targeting technically should be done using bullseye and is more helpful to other players (who know how to use it), that said, many players are not familiar with bullseye so BRAA can be used as well.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/40, 15 thousand, flank north west, hostile.”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/60, 500 feet, hot, hostile, 2 contacts, fulcrum.”</pre>

==== Responding to a Bogey Dope request ====
When a player asks for a Bogey Dope, they are asking for the nearest hostile. Locate the aircraft who made the request, and provide them a BRA to the nearest hostile.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA, 257/15, 10 thousand, drag east”</pre>

When there are no hostile aircraft on scope
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Clean”</pre>

==== Responding to a DECLARE request ====
When you receive a DECLARE request, you are asked to identify friend or foe of a locked target.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, Bullseye 204/8, 12 thousand, DECLARE.”</pre>
or use BRAA (not technically correct, but fine here)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, BRAA 090/15, 12 thousand, DECLARE.”</pre>
Response:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Group, Bullseye 204/8, 12 thousand, hostile, single contact, flanker”</pre>
(fill-ins "single contact" and "flanker" are optional)

==== Miscellaneous ====
Sometimes you will need to ask for additional information, or provide additional information.

Return to base (RTB)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, winchester RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 010/35”</pre>

Ask for state
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, say state”</pre>
Typically, yellow means a fighter can take at least one more engagement, where red means a fighter is unable.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, fuel green, weapons green”</pre>
or
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, 4/1/2 by 7 point 5”</pre>
"4/1/2" is equivalent to 4 active missiles (e.g. AIM-120), 1 semi-active missile (e.g. AIM-7) and 2 infrared missiles (e.g. AIM-9) with 7,500lbs of fuel remaining. "MINUS" can be added to indicate they do not have, or have insufficient guns. (e.g. "Uzi 1-1, 4/1/2, minus, by 7 point 5")

Inform aircraft to wait for instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, standby”</pre>

Ignore last transmitted message/instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, disregard last”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA 070/5, ... disregard, BRAA 090/5, 7000, hot”</pre>

Identify unknown transmitting aircraft
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Last transmitting aircraft, state callsign”</pre>

Inform aircraft about incoming missiles or missile launches (unrealistic, generally only possible with F10 map)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, SAM, bearing 090”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, Missile, bearing 090”</pre>

=== Tools ===
==== SRS AWACS mode (eam) ====
The standard SRS radio overlay only displays up to 3 radios and 1 intercom. The AWACS overlay provides up to 10 radios, which you can manually tune and 1 intercom.

You can use SRS without running DCS World, by using the external AWACS mode (EAM). provide your EAM username and the EAM coalition password. The coalition password is provided by the server admin, or in the server briefing. This is not always available.

==== F10 map, icons and the ruler tool ====
The ingame F10 map is where you’ll spend most of your time doing GCI/AWACS. It provides several functions which you can toggle on or off by personal preference
* health bars
* SAM and AAA detection range indicators
* SAM and AAA engagement range indicators
* grid
* labels indicating type and name
* ruler tool

The most important function you’ll use is the ruler tool. It allows you to create a line from point A to point B and provides you with the length in nautical miles and the heading. When intercepting enemy aircraft you can use the ruler tool to draw a line from your allied aircraft A to the hostile aircraft B and read the distance in nautical miles and the heading indicated on the top bar. When you click on the enemy aircraft icon, you can read its altitude, speed in knots, heading and type on the bottom left.

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

==== LotATC ====
LotATC is an optional program one can use to facilitate GCI simulation. The program is fairly easy to use is highly customizable. LotATC provides many features to aid a GCI.

* The creation of persistant BRAAs
* IFF features
* An ATC mode
* The ability to call BRAAs from the bullseye
* A scale which can be used to respond to Picture calls
* The ability to draw on the map

For more information on LotATC and how to use the software see [https://wiki.hoggitworld.com/view/LotATC LotATC]

== Coordinating with human GCI/AWACS ==
A couple guidelines from the players point of view

Inform AWACS when you tune in or tune out of the AWACS frequency.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F18, 10nm North of Anapa, checking in for CAP”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single Mirage 2000, checking in for CAP”</pre>

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, bingo fuel, RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 100/35”</pre>

Do not clutter the AWACS frequency with off-topic chatter, use the correct frequencies as stated in mission briefing.

Do not read back a BRA call. Simply acknowledge you received and understood the message by saying your callsign. If you did not understand the transmission, ask AWACS to repeat.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA 100/45, 20 thousand, flank north west”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Uzi 1-1”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, say again”</pre>

Getting started with GCI/AWACS

2022-09-04T13:30:30Z

Marlan: /* Understanding BRAA calls */

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

'''''Disclaimer''''' 
''This guide is compiled using information available to the public and information based on personal experience in DCS World. This guide does not in any way, shape or form represent real life GCI/AWACS operations or techniques nor is it based on real life experience.''

== What is GCI/AWACS ==
[[File:e3_awacs.jpg|thumb|frame|right|Boeing E-3 Sentry]]
GCI stands for '''G'''round-'''C'''ontrolled '''I'''nterception, an air defence tactic which developed during World War I. One or more radar stations or other observational stations are linked to a command communications centre which guides interceptor aircraft to airborne targets.

Today, GCI has mostly been replaced by Airborne Early Warning and Control (AEW&C) aircraft or more commonly referred to as AWACS ('''A'''irborne '''W'''arning '''A'''nd '''C'''ontrol '''S'''ystem). While AEW&C is expensive and vulnerable in comparison to GCI systems, it has a mobility advantage. In reality a combination of both systems is often used.

AWACS aircraft are generally speaking big, modified planes with a long-range radar mounted on top. The main radar antenna is mounted on a turntable housed in a circular rotodome, which is 9m (30 feet) in diameter, elliptical in cross-section and 1.8m deep at its centre. The radar system can detect, track and identify low-flying aircraft at approximately 370 km (200 nautical miles) and high-level aircraft at much greater distances.

== AI AWACS in DCS World ==
In DCS World the NATO AWACS comes in the form of the Boeing E-3 Sentry and the Russian equivalent is the Beriev A-50. The player can contact the allied AWACS via the ingame comms menu on the specified frequency in the mission briefing.

=== Comms menu ===
;Vector to bullseye
: The AWACS will provide the player with a bearing and range to bullseye

;Vector to home plate
: The AWACS will provide the player with a bearing and range from bullseye to their home airfield

;Vector to tanker
: The AWACS will provide the player with a bearing and range from bullseye to the tanker

;Request BOGEY DOPE
: The AWACS will provide the player a BRAA call to the closest airborne threat.

;Request PICTURE
: The AWACS will provide the player with BRA calls for each group from bullseye

;DECLARE
: The AWACS will identify friend or foe of a radar locked target

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

=== Understanding BRAA calls ===
[[File:Aspects.png|thumb|frame|right|500x|400px|Figure 1]]
BRAA stands for '''B'''earing '''R'''ange '''A'''ltitude '''A'''spect from your current location.
Aspects other than hot should include a cardinal direction. e.g. "Flank Northwest", "Beam East", "Drag South", "Hot", if an aspect is not provided in a BRAA call, "hot" is assumed.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">BRAA, 183/10, 2 thousand, hot</pre>
would indicate that the target is located at 183 degrees, 10 nautical miles away, and at 2000 feet coming directly towards you.

=== Pronunciation ===
Instead of
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi 1-1, Magic, BRAA, 183 for 10 at 2000, hot"</pre>
it is recommended to omit the "for" and "at", and to use short pauses (here indicated with "..."):
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi one one ... Magic ... BRAA ... one eight zero ... ten ... two thousand ... hot"</pre>

=== Understanding bullseye ===
Bullseye is a fixed point on the map determined pre-mission. All allied aircraft can relate to this point. When receiving a bullseye call, simply use the BRA format with bullseye as starting point. Bullseye in DCS is represented with the following symbols
[[File:bullseye.png|thumb|frame|center|1000x|800px|Left:Bullseye representation in DCS World - Right: Bullseye details]]

== Human GCI/AWACS ==
In DCS World, players can take the role of GCI/AWACS on multiplayer servers to assist your fellow pilots and friends. In the following sections we’ll go over the basics of airspace management, threat assessment, callsigns, brevity and some useful tools.

Before you begin as a GCI/AWACS controller on a server go over this short checklist:
* Pick a suitable callsign

* Check and confirm the radio frequencies used for GCI/AWACS, general communications and air traffic control
* Tune in the correct frequencies on SRS
* Be in the correct server slot (if necessary)
* Have your tools set up and running
* Announce GCI/AWACS will be available over COMMS and CHAT. State the correct frequency and callsign
<pre style="background-color: #ccc;font-family: 'Lucida Console'">all flights on frequency be advised <callsign> will be available on <frequency> for GCI/AWACS</pre>
* If you are on the Hoggit Discord and are registering as a GAW GCI controller, the appropriate command on discord would be "!gci sunrise GAW <callsign, frequency, any other remarks>" command, use "!gci midnight" when you're finished with your session.

=== Airspace management ===
As a controller your goal is to manage both friendly and hostile airspace. You’ll want to direct your allied flights to intercept enemy threats while at the same time making sure your friendly airspace stays protected.

Divide the airspace you’ll be controlling into two sectors.
# a friendly sector
# a hostile sector

Divide sector 1, your friendly sector, into subsectors based on strategic locations like airfields or a FARPs.

Next, you can assign your available CAP flights to the subsectors you created, and have them patrol or set up orbit. This way you can ensure that
* your allied flights are in proximity to allied aircraft and able to support
* your allied aircraft are not spread out or alone in hostile airspace
* your allied aircraft are in range of a tanker or airfield
* your friendly sector is protected

=== Threat assessment ===
With your airspace divided into sectors and your CAP flights on station you can start intercepting enemy threats. There are 2 major things you want to pay close attention to at all times.
* Where are your allied aircraft in relation to your sectors
* Where are the enemy aircraft in relation to your sectors

Before making a decision to direct your allied flights to intercept, you want to assess the threat
# '''Distance''': what is the distance between the threat and the nearby sector or allied aircraft
# '''Number''': how many enemy aircraft make up the threat
# '''Type''': which type is the enemy threat
# ('''State'''): have they been engaged prior and thus used counter measures and/or weapons

When you have gathered this info you can make a decision to either:
* direct one or more allied aircraft to intercept the threat
* direct one or more aircraft away from the threat to nearby SAM cover
* direct one or more allied aircraft to support engaged allied aircraft

In case you are unsure and need extra information before making a decision, contact your allied flights and ask for a fuel and/or weapons state.

When directing your allied flights to intercept, try to keep them in proximity of other allied flights, so you have enough time to send in support if needed. Do not direct your allied flights into enemy airspace and SAM range without support.

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

=== Callsigns and radio communication ===
When acting as GCI/AWACS controller you want to make sure you have a callsign which
* is clear
* is easy to pronounce
* does not cause confusion
* is not ridiculous

Commonly used callsigns for GCI/AWACS are
* Overlord
* Magic
* Showtime
* Darkstar
* Goliath
* Wizard
* Griffin
* Bigfoot

As GCI/AWACS controller you’ll have to relay a lot of information in a clear, concise and easy to understand manner, usually in a short amount of time. It is important to have a good microphone set up, to speak loud and clear, articulate, not to speak too quickly and use the NATO phonetic alphabet to avoid confusion. We’ll discuss some examples below.

==== Responding to flights checking in ====
When allied flights switch to general comms or designated AWACS comms after take off, they’ll most likely check in on the frequency and let you know who they are and what their intentions are.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F-18, 10 miles North of Anapa, checking in for CAP”</pre>

In the above example a player lets you know who they are, where they are and what their intentions are. You can respond to acknowledge (and task them if desired).
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Radar Contact, Alpha Check, Bullseye 123/45.”</pre>
"Alpha Check Bullseye" is the bearing from the bullseye TO the fighter, and verifies they understand/have the correct bullseye reference point.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima Charlie, standby for tasking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima, Charlie, fly heading 100/20, anchor at Krymsk”</pre>

==== Directing allied aircraft to intercept ====
When directing aircraft to intercept you want to be clear and concise. Start with who you are talking to, who you are and provide a Bullseye or BRAA call (and optional additional information). It is important to pronounce heading as single digits. For example ‘100’ would be ‘one, zero, zero.’ Targeting technically should be done using bullseye and is more helpful to other players (who know how to use it), that said, many players are not familiar with bullseye so BRAA can be used as well.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/40, 15 thousand, flank north west, hostile.”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/60, 500 feet, hot, hostile, 2 contacts, fulcrum.”</pre>

==== Responding to a Bogey Dope request ====
When a player asks for a Bogey Dope, they are asking for the nearest hostile. Locate the aircraft who made the request, and provide them a BRA to the nearest hostile.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA, 257/15, 10 thousand, drag east”</pre>

When there are no hostile aircraft on scope
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Clean”</pre>

==== Responding to a DECLARE request ====
When you receive a DECLARE request, you are asked to identify friend or foe of a locked target.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, Bullseye 204/8, 12 thousand, DECLARE.”</pre>
or use BRAA (not technically correct, but fine here)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, BRAA 090/15, 12 thousand, DECLARE.”</pre>
Response:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Group, Bullseye 204/8, 12 thousand, hostile, single contact, flanker”</pre>
(fill-ins "single contact" and "flanker" are optional)

==== Miscellaneous ====
Sometimes you will need to ask for additional information, or provide additional information.

Return to base (RTB)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, winchester RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 010/35”</pre>

Ask for state
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, say state”</pre>
Typically, yellow means a fighter can take at least one more engagement, where red means a fighter is unable.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, fuel green, weapons green”</pre>
or
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, 4/1/2 by 7 point 5”</pre>
"4/1/2" is equivalent to 4 active missiles (e.g. AIM-120), 1 semi-active missile (e.g. AIM-7) and 2 infrared missiles (e.g. AIM-9) with 7,500lbs of fuel remaining. "MINUS" can be added to indicate they do not have, or have insufficient guns. (e.g. "Uzi 1-1, 4/1/2, minus, by 7 point 5")

Inform aircraft to wait for instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, standby”</pre>

Ignore last transmitted message/instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, disregard last”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA 070/5, ... disregard, BRAA 090/5, 7000, hot”</pre>

Identify unknown transmitting aircraft
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Last transmitting aircraft, state callsign”</pre>

Inform aircraft about incoming missiles or missile launches (unrealistic, generally only possible with F10 map)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, SAM, bearing 090”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, Missile, bearing 090”</pre>

=== Tools ===
==== SRS AWACS mode (eam) ====
The standard SRS radio overlay only displays up to 3 radios and 1 intercom. The AWACS overlay provides up to 10 radios, which you can manually tune and 1 intercom.

You can use SRS without running DCS World, by using the external AWACS mode (EAM). provide your EAM username and the EAM coalition password. The coalition password is provided by the server admin, or in the server briefing. This is not always available.

==== F10 map, icons and the ruler tool ====
The ingame F10 map is where you’ll spend most of your time doing GCI/AWACS. It provides several functions which you can toggle on or off by personal preference
* health bars
* SAM and AAA detection range indicators
* SAM and AAA engagement range indicators
* grid
* labels indicating type and name
* ruler tool

The most important function you’ll use is the ruler tool. It allows you to create a line from point A to point B and provides you with the length in nautical miles and the heading. When intercepting enemy aircraft you can use the ruler tool to draw a line from your allied aircraft A to the hostile aircraft B and read the distance in nautical miles and the heading indicated on the top bar. When you click on the enemy aircraft icon, you can read its altitude, speed in knots, heading and type on the bottom left.

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

==== LotATC ====
LotATC is an optional program one can use to facilitate GCI simulation. The program is fairly easy to use is highly customizable. LotATC provides many features to aid a GCI.

* The creation of persistant BRAAs
* IFF features
* An ATC mode
* The ability to call BRAAs from the bullseye
* A scale which can be used to respond to Picture calls
* The ability to draw on the map

For more information on LotATC and how to use the software see [https://wiki.hoggitworld.com/view/LotATC LotATC]

== Coordinating with human GCI/AWACS ==
A couple guidelines from the players point of view

Inform AWACS when you tune in or tune out of the AWACS frequency.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F18, 10nm North of Anapa, checking in for CAP”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single Mirage 2000, checking in for CAP”</pre>

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, bingo fuel, RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 100/35”</pre>

Do not clutter the AWACS frequency with off-topic chatter, use the correct frequencies as stated in mission briefing.

Do not read back a BRA call. Simply acknowledge you received and understood the message by saying your callsign. If you did not understand the transmission, ask AWACS to repeat.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA 100/45, 20 thousand, flank north west”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Uzi 1-1”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, say again”</pre>

Getting started with GCI/AWACS

2022-09-04T13:30:17Z

Marlan: /* Understanding BRAA calls */

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

'''''Disclaimer''''' 
''This guide is compiled using information available to the public and information based on personal experience in DCS World. This guide does not in any way, shape or form represent real life GCI/AWACS operations or techniques nor is it based on real life experience.''

== What is GCI/AWACS ==
[[File:e3_awacs.jpg|thumb|frame|right|Boeing E-3 Sentry]]
GCI stands for '''G'''round-'''C'''ontrolled '''I'''nterception, an air defence tactic which developed during World War I. One or more radar stations or other observational stations are linked to a command communications centre which guides interceptor aircraft to airborne targets.

Today, GCI has mostly been replaced by Airborne Early Warning and Control (AEW&C) aircraft or more commonly referred to as AWACS ('''A'''irborne '''W'''arning '''A'''nd '''C'''ontrol '''S'''ystem). While AEW&C is expensive and vulnerable in comparison to GCI systems, it has a mobility advantage. In reality a combination of both systems is often used.

AWACS aircraft are generally speaking big, modified planes with a long-range radar mounted on top. The main radar antenna is mounted on a turntable housed in a circular rotodome, which is 9m (30 feet) in diameter, elliptical in cross-section and 1.8m deep at its centre. The radar system can detect, track and identify low-flying aircraft at approximately 370 km (200 nautical miles) and high-level aircraft at much greater distances.

== AI AWACS in DCS World ==
In DCS World the NATO AWACS comes in the form of the Boeing E-3 Sentry and the Russian equivalent is the Beriev A-50. The player can contact the allied AWACS via the ingame comms menu on the specified frequency in the mission briefing.

=== Comms menu ===
;Vector to bullseye
: The AWACS will provide the player with a bearing and range to bullseye

;Vector to home plate
: The AWACS will provide the player with a bearing and range from bullseye to their home airfield

;Vector to tanker
: The AWACS will provide the player with a bearing and range from bullseye to the tanker

;Request BOGEY DOPE
: The AWACS will provide the player a BRAA call to the closest airborne threat.

;Request PICTURE
: The AWACS will provide the player with BRA calls for each group from bullseye

;DECLARE
: The AWACS will identify friend or foe of a radar locked target

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

=== Understanding BRAA calls ===
[[File:Aspects.png|thumb|frame|right|500x|400px|Figure 1]]
BRAA stands for '''B'''earing '''R'''ange '''A'''ltitude '''A'''spect from your current location. See figure 1 for each aspect. Aspects other than hot should include a cardinal direction. e.g. "Flank Northwest", "Beam East", "Drag South", "Hot", if an aspect is not provided in a BRAA call, "hot" is assumed.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">BRAA, 183/10, 2 thousand, hot</pre>
would indicate that the target is located at 183 degrees, 10 nautical miles away, and at 2000 feet coming directly towards you.

=== Pronunciation ===
Instead of
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi 1-1, Magic, BRAA, 183 for 10 at 2000, hot"</pre>
it is recommended to omit the "for" and "at", and to use short pauses (here indicated with "..."):
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi one one ... Magic ... BRAA ... one eight zero ... ten ... two thousand ... hot"</pre>

=== Understanding bullseye ===
Bullseye is a fixed point on the map determined pre-mission. All allied aircraft can relate to this point. When receiving a bullseye call, simply use the BRA format with bullseye as starting point. Bullseye in DCS is represented with the following symbols
[[File:bullseye.png|thumb|frame|center|1000x|800px|Left:Bullseye representation in DCS World - Right: Bullseye details]]

== Human GCI/AWACS ==
In DCS World, players can take the role of GCI/AWACS on multiplayer servers to assist your fellow pilots and friends. In the following sections we’ll go over the basics of airspace management, threat assessment, callsigns, brevity and some useful tools.

Before you begin as a GCI/AWACS controller on a server go over this short checklist:
* Pick a suitable callsign

* Check and confirm the radio frequencies used for GCI/AWACS, general communications and air traffic control
* Tune in the correct frequencies on SRS
* Be in the correct server slot (if necessary)
* Have your tools set up and running
* Announce GCI/AWACS will be available over COMMS and CHAT. State the correct frequency and callsign
<pre style="background-color: #ccc;font-family: 'Lucida Console'">all flights on frequency be advised <callsign> will be available on <frequency> for GCI/AWACS</pre>
* If you are on the Hoggit Discord and are registering as a GAW GCI controller, the appropriate command on discord would be "!gci sunrise GAW <callsign, frequency, any other remarks>" command, use "!gci midnight" when you're finished with your session.

=== Airspace management ===
As a controller your goal is to manage both friendly and hostile airspace. You’ll want to direct your allied flights to intercept enemy threats while at the same time making sure your friendly airspace stays protected.

Divide the airspace you’ll be controlling into two sectors.
# a friendly sector
# a hostile sector

Divide sector 1, your friendly sector, into subsectors based on strategic locations like airfields or a FARPs.

Next, you can assign your available CAP flights to the subsectors you created, and have them patrol or set up orbit. This way you can ensure that
* your allied flights are in proximity to allied aircraft and able to support
* your allied aircraft are not spread out or alone in hostile airspace
* your allied aircraft are in range of a tanker or airfield
* your friendly sector is protected

=== Threat assessment ===
With your airspace divided into sectors and your CAP flights on station you can start intercepting enemy threats. There are 2 major things you want to pay close attention to at all times.
* Where are your allied aircraft in relation to your sectors
* Where are the enemy aircraft in relation to your sectors

Before making a decision to direct your allied flights to intercept, you want to assess the threat
# '''Distance''': what is the distance between the threat and the nearby sector or allied aircraft
# '''Number''': how many enemy aircraft make up the threat
# '''Type''': which type is the enemy threat
# ('''State'''): have they been engaged prior and thus used counter measures and/or weapons

When you have gathered this info you can make a decision to either:
* direct one or more allied aircraft to intercept the threat
* direct one or more aircraft away from the threat to nearby SAM cover
* direct one or more allied aircraft to support engaged allied aircraft

In case you are unsure and need extra information before making a decision, contact your allied flights and ask for a fuel and/or weapons state.

When directing your allied flights to intercept, try to keep them in proximity of other allied flights, so you have enough time to send in support if needed. Do not direct your allied flights into enemy airspace and SAM range without support.

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

=== Callsigns and radio communication ===
When acting as GCI/AWACS controller you want to make sure you have a callsign which
* is clear
* is easy to pronounce
* does not cause confusion
* is not ridiculous

Commonly used callsigns for GCI/AWACS are
* Overlord
* Magic
* Showtime
* Darkstar
* Goliath
* Wizard
* Griffin
* Bigfoot

As GCI/AWACS controller you’ll have to relay a lot of information in a clear, concise and easy to understand manner, usually in a short amount of time. It is important to have a good microphone set up, to speak loud and clear, articulate, not to speak too quickly and use the NATO phonetic alphabet to avoid confusion. We’ll discuss some examples below.

==== Responding to flights checking in ====
When allied flights switch to general comms or designated AWACS comms after take off, they’ll most likely check in on the frequency and let you know who they are and what their intentions are.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F-18, 10 miles North of Anapa, checking in for CAP”</pre>

In the above example a player lets you know who they are, where they are and what their intentions are. You can respond to acknowledge (and task them if desired).
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Radar Contact, Alpha Check, Bullseye 123/45.”</pre>
"Alpha Check Bullseye" is the bearing from the bullseye TO the fighter, and verifies they understand/have the correct bullseye reference point.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima Charlie, standby for tasking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima, Charlie, fly heading 100/20, anchor at Krymsk”</pre>

==== Directing allied aircraft to intercept ====
When directing aircraft to intercept you want to be clear and concise. Start with who you are talking to, who you are and provide a Bullseye or BRAA call (and optional additional information). It is important to pronounce heading as single digits. For example ‘100’ would be ‘one, zero, zero.’ Targeting technically should be done using bullseye and is more helpful to other players (who know how to use it), that said, many players are not familiar with bullseye so BRAA can be used as well.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/40, 15 thousand, flank north west, hostile.”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/60, 500 feet, hot, hostile, 2 contacts, fulcrum.”</pre>

==== Responding to a Bogey Dope request ====
When a player asks for a Bogey Dope, they are asking for the nearest hostile. Locate the aircraft who made the request, and provide them a BRA to the nearest hostile.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA, 257/15, 10 thousand, drag east”</pre>

When there are no hostile aircraft on scope
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Clean”</pre>

==== Responding to a DECLARE request ====
When you receive a DECLARE request, you are asked to identify friend or foe of a locked target.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, Bullseye 204/8, 12 thousand, DECLARE.”</pre>
or use BRAA (not technically correct, but fine here)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, BRAA 090/15, 12 thousand, DECLARE.”</pre>
Response:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Group, Bullseye 204/8, 12 thousand, hostile, single contact, flanker”</pre>
(fill-ins "single contact" and "flanker" are optional)

==== Miscellaneous ====
Sometimes you will need to ask for additional information, or provide additional information.

Return to base (RTB)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, winchester RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 010/35”</pre>

Ask for state
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, say state”</pre>
Typically, yellow means a fighter can take at least one more engagement, where red means a fighter is unable.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, fuel green, weapons green”</pre>
or
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, 4/1/2 by 7 point 5”</pre>
"4/1/2" is equivalent to 4 active missiles (e.g. AIM-120), 1 semi-active missile (e.g. AIM-7) and 2 infrared missiles (e.g. AIM-9) with 7,500lbs of fuel remaining. "MINUS" can be added to indicate they do not have, or have insufficient guns. (e.g. "Uzi 1-1, 4/1/2, minus, by 7 point 5")

Inform aircraft to wait for instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, standby”</pre>

Ignore last transmitted message/instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, disregard last”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA 070/5, ... disregard, BRAA 090/5, 7000, hot”</pre>

Identify unknown transmitting aircraft
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Last transmitting aircraft, state callsign”</pre>

Inform aircraft about incoming missiles or missile launches (unrealistic, generally only possible with F10 map)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, SAM, bearing 090”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, Missile, bearing 090”</pre>

=== Tools ===
==== SRS AWACS mode (eam) ====
The standard SRS radio overlay only displays up to 3 radios and 1 intercom. The AWACS overlay provides up to 10 radios, which you can manually tune and 1 intercom.

You can use SRS without running DCS World, by using the external AWACS mode (EAM). provide your EAM username and the EAM coalition password. The coalition password is provided by the server admin, or in the server briefing. This is not always available.

==== F10 map, icons and the ruler tool ====
The ingame F10 map is where you’ll spend most of your time doing GCI/AWACS. It provides several functions which you can toggle on or off by personal preference
* health bars
* SAM and AAA detection range indicators
* SAM and AAA engagement range indicators
* grid
* labels indicating type and name
* ruler tool

The most important function you’ll use is the ruler tool. It allows you to create a line from point A to point B and provides you with the length in nautical miles and the heading. When intercepting enemy aircraft you can use the ruler tool to draw a line from your allied aircraft A to the hostile aircraft B and read the distance in nautical miles and the heading indicated on the top bar. When you click on the enemy aircraft icon, you can read its altitude, speed in knots, heading and type on the bottom left.

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

==== LotATC ====
LotATC is an optional program one can use to facilitate GCI simulation. The program is fairly easy to use is highly customizable. LotATC provides many features to aid a GCI.

* The creation of persistant BRAAs
* IFF features
* An ATC mode
* The ability to call BRAAs from the bullseye
* A scale which can be used to respond to Picture calls
* The ability to draw on the map

For more information on LotATC and how to use the software see [https://wiki.hoggitworld.com/view/LotATC LotATC]

== Coordinating with human GCI/AWACS ==
A couple guidelines from the players point of view

Inform AWACS when you tune in or tune out of the AWACS frequency.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F18, 10nm North of Anapa, checking in for CAP”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single Mirage 2000, checking in for CAP”</pre>

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, bingo fuel, RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 100/35”</pre>

Do not clutter the AWACS frequency with off-topic chatter, use the correct frequencies as stated in mission briefing.

Do not read back a BRA call. Simply acknowledge you received and understood the message by saying your callsign. If you did not understand the transmission, ask AWACS to repeat.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA 100/45, 20 thousand, flank north west”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Uzi 1-1”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, say again”</pre>

Getting started with GCI/AWACS

2022-09-04T13:26:38Z

Marlan: /* Understanding BRAA calls */

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

'''''Disclaimer''''' 
''This guide is compiled using information available to the public and information based on personal experience in DCS World. This guide does not in any way, shape or form represent real life GCI/AWACS operations or techniques nor is it based on real life experience.''

== What is GCI/AWACS ==
[[File:e3_awacs.jpg|thumb|frame|right|Boeing E-3 Sentry]]
GCI stands for '''G'''round-'''C'''ontrolled '''I'''nterception, an air defence tactic which developed during World War I. One or more radar stations or other observational stations are linked to a command communications centre which guides interceptor aircraft to airborne targets.

Today, GCI has mostly been replaced by Airborne Early Warning and Control (AEW&C) aircraft or more commonly referred to as AWACS ('''A'''irborne '''W'''arning '''A'''nd '''C'''ontrol '''S'''ystem). While AEW&C is expensive and vulnerable in comparison to GCI systems, it has a mobility advantage. In reality a combination of both systems is often used.

AWACS aircraft are generally speaking big, modified planes with a long-range radar mounted on top. The main radar antenna is mounted on a turntable housed in a circular rotodome, which is 9m (30 feet) in diameter, elliptical in cross-section and 1.8m deep at its centre. The radar system can detect, track and identify low-flying aircraft at approximately 370 km (200 nautical miles) and high-level aircraft at much greater distances.

== AI AWACS in DCS World ==
In DCS World the NATO AWACS comes in the form of the Boeing E-3 Sentry and the Russian equivalent is the Beriev A-50. The player can contact the allied AWACS via the ingame comms menu on the specified frequency in the mission briefing.

=== Comms menu ===
;Vector to bullseye
: The AWACS will provide the player with a bearing and range to bullseye

;Vector to home plate
: The AWACS will provide the player with a bearing and range from bullseye to their home airfield

;Vector to tanker
: The AWACS will provide the player with a bearing and range from bullseye to the tanker

;Request BOGEY DOPE
: The AWACS will provide the player a BRAA call to the closest airborne threat.

;Request PICTURE
: The AWACS will provide the player with BRA calls for each group from bullseye

;DECLARE
: The AWACS will identify friend or foe of a radar locked target

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

=== Understanding BRAA calls ===
[[File:Aspects.png|thumb|frame|right|500x|400px|Figure 1]]
BRAA stands for '''B'''earing '''R'''ange '''A'''ltitude '''A'''spect from your current location.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">BRAA, 183/10, 2 thousand, hot</pre> would mean the target is located at 183 degrees, 10 nautical miles away, and at 2000 feet coming directly towards you. North is 360. For aspect see figure 1.

=== Pronunciation ===
Instead of
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi 1-1, Magic, BRAA, 183 for 10 at 2000, hot"</pre>
it is recommended to omit the "for" and "at", and to use short pauses (here indicated with "..."):
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi one one ... Magic ... BRAA ... one eight zero ... ten ... two thousand ... hot"</pre>

=== Understanding bullseye ===
Bullseye is a fixed point on the map determined pre-mission. All allied aircraft can relate to this point. When receiving a bullseye call, simply use the BRA format with bullseye as starting point. Bullseye in DCS is represented with the following symbols
[[File:bullseye.png|thumb|frame|center|1000x|800px|Left:Bullseye representation in DCS World - Right: Bullseye details]]

== Human GCI/AWACS ==
In DCS World, players can take the role of GCI/AWACS on multiplayer servers to assist your fellow pilots and friends. In the following sections we’ll go over the basics of airspace management, threat assessment, callsigns, brevity and some useful tools.

Before you begin as a GCI/AWACS controller on a server go over this short checklist:
* Pick a suitable callsign

* Check and confirm the radio frequencies used for GCI/AWACS, general communications and air traffic control
* Tune in the correct frequencies on SRS
* Be in the correct server slot (if necessary)
* Have your tools set up and running
* Announce GCI/AWACS will be available over COMMS and CHAT. State the correct frequency and callsign
<pre style="background-color: #ccc;font-family: 'Lucida Console'">all flights on frequency be advised <callsign> will be available on <frequency> for GCI/AWACS</pre>
* If you are on the Hoggit Discord and are registering as a GAW GCI controller, the appropriate command on discord would be "!gci sunrise GAW <callsign, frequency, any other remarks>" command, use "!gci midnight" when you're finished with your session.

=== Airspace management ===
As a controller your goal is to manage both friendly and hostile airspace. You’ll want to direct your allied flights to intercept enemy threats while at the same time making sure your friendly airspace stays protected.

Divide the airspace you’ll be controlling into two sectors.
# a friendly sector
# a hostile sector

Divide sector 1, your friendly sector, into subsectors based on strategic locations like airfields or a FARPs.

Next, you can assign your available CAP flights to the subsectors you created, and have them patrol or set up orbit. This way you can ensure that
* your allied flights are in proximity to allied aircraft and able to support
* your allied aircraft are not spread out or alone in hostile airspace
* your allied aircraft are in range of a tanker or airfield
* your friendly sector is protected

=== Threat assessment ===
With your airspace divided into sectors and your CAP flights on station you can start intercepting enemy threats. There are 2 major things you want to pay close attention to at all times.
* Where are your allied aircraft in relation to your sectors
* Where are the enemy aircraft in relation to your sectors

Before making a decision to direct your allied flights to intercept, you want to assess the threat
# '''Distance''': what is the distance between the threat and the nearby sector or allied aircraft
# '''Number''': how many enemy aircraft make up the threat
# '''Type''': which type is the enemy threat
# ('''State'''): have they been engaged prior and thus used counter measures and/or weapons

When you have gathered this info you can make a decision to either:
* direct one or more allied aircraft to intercept the threat
* direct one or more aircraft away from the threat to nearby SAM cover
* direct one or more allied aircraft to support engaged allied aircraft

In case you are unsure and need extra information before making a decision, contact your allied flights and ask for a fuel and/or weapons state.

When directing your allied flights to intercept, try to keep them in proximity of other allied flights, so you have enough time to send in support if needed. Do not direct your allied flights into enemy airspace and SAM range without support.

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

=== Callsigns and radio communication ===
When acting as GCI/AWACS controller you want to make sure you have a callsign which
* is clear
* is easy to pronounce
* does not cause confusion
* is not ridiculous

Commonly used callsigns for GCI/AWACS are
* Overlord
* Magic
* Showtime
* Darkstar
* Goliath
* Wizard
* Griffin
* Bigfoot

As GCI/AWACS controller you’ll have to relay a lot of information in a clear, concise and easy to understand manner, usually in a short amount of time. It is important to have a good microphone set up, to speak loud and clear, articulate, not to speak too quickly and use the NATO phonetic alphabet to avoid confusion. We’ll discuss some examples below.

==== Responding to flights checking in ====
When allied flights switch to general comms or designated AWACS comms after take off, they’ll most likely check in on the frequency and let you know who they are and what their intentions are.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F-18, 10 miles North of Anapa, checking in for CAP”</pre>

In the above example a player lets you know who they are, where they are and what their intentions are. You can respond to acknowledge (and task them if desired).
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Radar Contact, Alpha Check, Bullseye 123/45.”</pre>
"Alpha Check Bullseye" is the bearing from the bullseye TO the fighter, and verifies they understand/have the correct bullseye reference point.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima Charlie, standby for tasking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima, Charlie, fly heading 100/20, anchor at Krymsk”</pre>

==== Directing allied aircraft to intercept ====
When directing aircraft to intercept you want to be clear and concise. Start with who you are talking to, who you are and provide a Bullseye or BRAA call (and optional additional information). It is important to pronounce heading as single digits. For example ‘100’ would be ‘one, zero, zero.’ Targeting technically should be done using bullseye and is more helpful to other players (who know how to use it), that said, many players are not familiar with bullseye so BRAA can be used as well.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/40, 15 thousand, flank north west, hostile.”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/60, 500 feet, hot, hostile, 2 contacts, fulcrum.”</pre>

==== Responding to a Bogey Dope request ====
When a player asks for a Bogey Dope, they are asking for the nearest hostile. Locate the aircraft who made the request, and provide them a BRA to the nearest hostile.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA, 257/15, 10 thousand, drag east”</pre>

When there are no hostile aircraft on scope
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Clean”</pre>

==== Responding to a DECLARE request ====
When you receive a DECLARE request, you are asked to identify friend or foe of a locked target.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, Bullseye 204/8, 12 thousand, DECLARE.”</pre>
or use BRAA (not technically correct, but fine here)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, BRAA 090/15, 12 thousand, DECLARE.”</pre>
Response:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Group, Bullseye 204/8, 12 thousand, hostile, single contact, flanker”</pre>
(fill-ins "single contact" and "flanker" are optional)

==== Miscellaneous ====
Sometimes you will need to ask for additional information, or provide additional information.

Return to base (RTB)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, winchester RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 010/35”</pre>

Ask for state
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, say state”</pre>
Typically, yellow means a fighter can take at least one more engagement, where red means a fighter is unable.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, fuel green, weapons green”</pre>
or
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, 4/1/2 by 7 point 5”</pre>
"4/1/2" is equivalent to 4 active missiles (e.g. AIM-120), 1 semi-active missile (e.g. AIM-7) and 2 infrared missiles (e.g. AIM-9) with 7,500lbs of fuel remaining. "MINUS" can be added to indicate they do not have, or have insufficient guns. (e.g. "Uzi 1-1, 4/1/2, minus, by 7 point 5")

Inform aircraft to wait for instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, standby”</pre>

Ignore last transmitted message/instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, disregard last”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA 070/5, ... disregard, BRAA 090/5, 7000, hot”</pre>

Identify unknown transmitting aircraft
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Last transmitting aircraft, state callsign”</pre>

Inform aircraft about incoming missiles or missile launches (unrealistic, generally only possible with F10 map)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, SAM, bearing 090”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, Missile, bearing 090”</pre>

=== Tools ===
==== SRS AWACS mode (eam) ====
The standard SRS radio overlay only displays up to 3 radios and 1 intercom. The AWACS overlay provides up to 10 radios, which you can manually tune and 1 intercom.

You can use SRS without running DCS World, by using the external AWACS mode (EAM). provide your EAM username and the EAM coalition password. The coalition password is provided by the server admin, or in the server briefing. This is not always available.

==== F10 map, icons and the ruler tool ====
The ingame F10 map is where you’ll spend most of your time doing GCI/AWACS. It provides several functions which you can toggle on or off by personal preference
* health bars
* SAM and AAA detection range indicators
* SAM and AAA engagement range indicators
* grid
* labels indicating type and name
* ruler tool

The most important function you’ll use is the ruler tool. It allows you to create a line from point A to point B and provides you with the length in nautical miles and the heading. When intercepting enemy aircraft you can use the ruler tool to draw a line from your allied aircraft A to the hostile aircraft B and read the distance in nautical miles and the heading indicated on the top bar. When you click on the enemy aircraft icon, you can read its altitude, speed in knots, heading and type on the bottom left.

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

==== LotATC ====
LotATC is an optional program one can use to facilitate GCI simulation. The program is fairly easy to use is highly customizable. LotATC provides many features to aid a GCI.

* The creation of persistant BRAAs
* IFF features
* An ATC mode
* The ability to call BRAAs from the bullseye
* A scale which can be used to respond to Picture calls
* The ability to draw on the map

For more information on LotATC and how to use the software see [https://wiki.hoggitworld.com/view/LotATC LotATC]

== Coordinating with human GCI/AWACS ==
A couple guidelines from the players point of view

Inform AWACS when you tune in or tune out of the AWACS frequency.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F18, 10nm North of Anapa, checking in for CAP”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single Mirage 2000, checking in for CAP”</pre>

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, bingo fuel, RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 100/35”</pre>

Do not clutter the AWACS frequency with off-topic chatter, use the correct frequencies as stated in mission briefing.

Do not read back a BRA call. Simply acknowledge you received and understood the message by saying your callsign. If you did not understand the transmission, ask AWACS to repeat.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA 100/45, 20 thousand, flank north west”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Uzi 1-1”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, say again”</pre>

File:Aspects.png

2022-09-04T13:26:09Z

Marlan:

File:Aspect.jpg

2022-09-04T13:25:35Z

Marlan: Marlan uploaded a new version of File:Aspect.jpg

File:Aspect.jpg

2022-09-04T13:23:19Z

Marlan: Marlan uploaded a new version of File:Aspect.jpg

File:Aspect.jpg

2022-09-04T13:21:42Z

Marlan: Marlan uploaded a new version of File:Aspect.jpg

Getting started with GCI/AWACS

2022-09-04T13:19:32Z

Marlan: /* Coordinating with human GCI/AWACS */

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

'''''Disclaimer''''' 
''This guide is compiled using information available to the public and information based on personal experience in DCS World. This guide does not in any way, shape or form represent real life GCI/AWACS operations or techniques nor is it based on real life experience.''

== What is GCI/AWACS ==
[[File:e3_awacs.jpg|thumb|frame|right|Boeing E-3 Sentry]]
GCI stands for '''G'''round-'''C'''ontrolled '''I'''nterception, an air defence tactic which developed during World War I. One or more radar stations or other observational stations are linked to a command communications centre which guides interceptor aircraft to airborne targets.

Today, GCI has mostly been replaced by Airborne Early Warning and Control (AEW&C) aircraft or more commonly referred to as AWACS ('''A'''irborne '''W'''arning '''A'''nd '''C'''ontrol '''S'''ystem). While AEW&C is expensive and vulnerable in comparison to GCI systems, it has a mobility advantage. In reality a combination of both systems is often used.

AWACS aircraft are generally speaking big, modified planes with a long-range radar mounted on top. The main radar antenna is mounted on a turntable housed in a circular rotodome, which is 9m (30 feet) in diameter, elliptical in cross-section and 1.8m deep at its centre. The radar system can detect, track and identify low-flying aircraft at approximately 370 km (200 nautical miles) and high-level aircraft at much greater distances.

== AI AWACS in DCS World ==
In DCS World the NATO AWACS comes in the form of the Boeing E-3 Sentry and the Russian equivalent is the Beriev A-50. The player can contact the allied AWACS via the ingame comms menu on the specified frequency in the mission briefing.

=== Comms menu ===
;Vector to bullseye
: The AWACS will provide the player with a bearing and range to bullseye

;Vector to home plate
: The AWACS will provide the player with a bearing and range from bullseye to their home airfield

;Vector to tanker
: The AWACS will provide the player with a bearing and range from bullseye to the tanker

;Request BOGEY DOPE
: The AWACS will provide the player a BRAA call to the closest airborne threat.

;Request PICTURE
: The AWACS will provide the player with BRA calls for each group from bullseye

;DECLARE
: The AWACS will identify friend or foe of a radar locked target

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

=== Understanding BRAA calls ===
[[File:aspect.jpg|thumb|frame|right|500x|400px|Figure 1]]
BRAA stands for '''B'''earing '''R'''ange '''A'''ltitude '''A'''spect from your current location.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">BRAA, 183/10, 2 thousand, hot</pre> would mean the target is located at 183 degrees, 10 nautical miles away, and at 2000 feet coming directly towards you. North is 360. For aspect see figure 1.

=== Pronunciation ===
Instead of
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi 1-1, Magic, BRAA, 183 for 10 at 2000, hot"</pre>
it is recommended to omit the "for" and "at", and to use short pauses (here indicated with "..."):
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi one one ... Magic ... BRAA ... one eight zero ... ten ... two thousand ... hot"</pre>

=== Understanding bullseye ===
Bullseye is a fixed point on the map determined pre-mission. All allied aircraft can relate to this point. When receiving a bullseye call, simply use the BRA format with bullseye as starting point. Bullseye in DCS is represented with the following symbols
[[File:bullseye.png|thumb|frame|center|1000x|800px|Left:Bullseye representation in DCS World - Right: Bullseye details]]

== Human GCI/AWACS ==
In DCS World, players can take the role of GCI/AWACS on multiplayer servers to assist your fellow pilots and friends. In the following sections we’ll go over the basics of airspace management, threat assessment, callsigns, brevity and some useful tools.

Before you begin as a GCI/AWACS controller on a server go over this short checklist:
* Pick a suitable callsign

* Check and confirm the radio frequencies used for GCI/AWACS, general communications and air traffic control
* Tune in the correct frequencies on SRS
* Be in the correct server slot (if necessary)
* Have your tools set up and running
* Announce GCI/AWACS will be available over COMMS and CHAT. State the correct frequency and callsign
<pre style="background-color: #ccc;font-family: 'Lucida Console'">all flights on frequency be advised <callsign> will be available on <frequency> for GCI/AWACS</pre>
* If you are on the Hoggit Discord and are registering as a GAW GCI controller, the appropriate command on discord would be "!gci sunrise GAW <callsign, frequency, any other remarks>" command, use "!gci midnight" when you're finished with your session.

=== Airspace management ===
As a controller your goal is to manage both friendly and hostile airspace. You’ll want to direct your allied flights to intercept enemy threats while at the same time making sure your friendly airspace stays protected.

Divide the airspace you’ll be controlling into two sectors.
# a friendly sector
# a hostile sector

Divide sector 1, your friendly sector, into subsectors based on strategic locations like airfields or a FARPs.

Next, you can assign your available CAP flights to the subsectors you created, and have them patrol or set up orbit. This way you can ensure that
* your allied flights are in proximity to allied aircraft and able to support
* your allied aircraft are not spread out or alone in hostile airspace
* your allied aircraft are in range of a tanker or airfield
* your friendly sector is protected

=== Threat assessment ===
With your airspace divided into sectors and your CAP flights on station you can start intercepting enemy threats. There are 2 major things you want to pay close attention to at all times.
* Where are your allied aircraft in relation to your sectors
* Where are the enemy aircraft in relation to your sectors

Before making a decision to direct your allied flights to intercept, you want to assess the threat
# '''Distance''': what is the distance between the threat and the nearby sector or allied aircraft
# '''Number''': how many enemy aircraft make up the threat
# '''Type''': which type is the enemy threat
# ('''State'''): have they been engaged prior and thus used counter measures and/or weapons

When you have gathered this info you can make a decision to either:
* direct one or more allied aircraft to intercept the threat
* direct one or more aircraft away from the threat to nearby SAM cover
* direct one or more allied aircraft to support engaged allied aircraft

In case you are unsure and need extra information before making a decision, contact your allied flights and ask for a fuel and/or weapons state.

When directing your allied flights to intercept, try to keep them in proximity of other allied flights, so you have enough time to send in support if needed. Do not direct your allied flights into enemy airspace and SAM range without support.

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

=== Callsigns and radio communication ===
When acting as GCI/AWACS controller you want to make sure you have a callsign which
* is clear
* is easy to pronounce
* does not cause confusion
* is not ridiculous

Commonly used callsigns for GCI/AWACS are
* Overlord
* Magic
* Showtime
* Darkstar
* Goliath
* Wizard
* Griffin
* Bigfoot

As GCI/AWACS controller you’ll have to relay a lot of information in a clear, concise and easy to understand manner, usually in a short amount of time. It is important to have a good microphone set up, to speak loud and clear, articulate, not to speak too quickly and use the NATO phonetic alphabet to avoid confusion. We’ll discuss some examples below.

==== Responding to flights checking in ====
When allied flights switch to general comms or designated AWACS comms after take off, they’ll most likely check in on the frequency and let you know who they are and what their intentions are.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F-18, 10 miles North of Anapa, checking in for CAP”</pre>

In the above example a player lets you know who they are, where they are and what their intentions are. You can respond to acknowledge (and task them if desired).
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Radar Contact, Alpha Check, Bullseye 123/45.”</pre>
"Alpha Check Bullseye" is the bearing from the bullseye TO the fighter, and verifies they understand/have the correct bullseye reference point.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima Charlie, standby for tasking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima, Charlie, fly heading 100/20, anchor at Krymsk”</pre>

==== Directing allied aircraft to intercept ====
When directing aircraft to intercept you want to be clear and concise. Start with who you are talking to, who you are and provide a Bullseye or BRAA call (and optional additional information). It is important to pronounce heading as single digits. For example ‘100’ would be ‘one, zero, zero.’ Targeting technically should be done using bullseye and is more helpful to other players (who know how to use it), that said, many players are not familiar with bullseye so BRAA can be used as well.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/40, 15 thousand, flank north west, hostile.”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/60, 500 feet, hot, hostile, 2 contacts, fulcrum.”</pre>

==== Responding to a Bogey Dope request ====
When a player asks for a Bogey Dope, they are asking for the nearest hostile. Locate the aircraft who made the request, and provide them a BRA to the nearest hostile.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA, 257/15, 10 thousand, drag east”</pre>

When there are no hostile aircraft on scope
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Clean”</pre>

==== Responding to a DECLARE request ====
When you receive a DECLARE request, you are asked to identify friend or foe of a locked target.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, Bullseye 204/8, 12 thousand, DECLARE.”</pre>
or use BRAA (not technically correct, but fine here)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, BRAA 090/15, 12 thousand, DECLARE.”</pre>
Response:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Group, Bullseye 204/8, 12 thousand, hostile, single contact, flanker”</pre>
(fill-ins "single contact" and "flanker" are optional)

==== Miscellaneous ====
Sometimes you will need to ask for additional information, or provide additional information.

Return to base (RTB)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, winchester RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 010/35”</pre>

Ask for state
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, say state”</pre>
Typically, yellow means a fighter can take at least one more engagement, where red means a fighter is unable.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, fuel green, weapons green”</pre>
or
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, 4/1/2 by 7 point 5”</pre>
"4/1/2" is equivalent to 4 active missiles (e.g. AIM-120), 1 semi-active missile (e.g. AIM-7) and 2 infrared missiles (e.g. AIM-9) with 7,500lbs of fuel remaining. "MINUS" can be added to indicate they do not have, or have insufficient guns. (e.g. "Uzi 1-1, 4/1/2, minus, by 7 point 5")

Inform aircraft to wait for instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, standby”</pre>

Ignore last transmitted message/instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, disregard last”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA 070/5, ... disregard, BRAA 090/5, 7000, hot”</pre>

Identify unknown transmitting aircraft
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Last transmitting aircraft, state callsign”</pre>

Inform aircraft about incoming missiles or missile launches (unrealistic, generally only possible with F10 map)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, SAM, bearing 090”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, Missile, bearing 090”</pre>

=== Tools ===
==== SRS AWACS mode (eam) ====
The standard SRS radio overlay only displays up to 3 radios and 1 intercom. The AWACS overlay provides up to 10 radios, which you can manually tune and 1 intercom.

You can use SRS without running DCS World, by using the external AWACS mode (EAM). provide your EAM username and the EAM coalition password. The coalition password is provided by the server admin, or in the server briefing. This is not always available.

==== F10 map, icons and the ruler tool ====
The ingame F10 map is where you’ll spend most of your time doing GCI/AWACS. It provides several functions which you can toggle on or off by personal preference
* health bars
* SAM and AAA detection range indicators
* SAM and AAA engagement range indicators
* grid
* labels indicating type and name
* ruler tool

The most important function you’ll use is the ruler tool. It allows you to create a line from point A to point B and provides you with the length in nautical miles and the heading. When intercepting enemy aircraft you can use the ruler tool to draw a line from your allied aircraft A to the hostile aircraft B and read the distance in nautical miles and the heading indicated on the top bar. When you click on the enemy aircraft icon, you can read its altitude, speed in knots, heading and type on the bottom left.

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

==== LotATC ====
LotATC is an optional program one can use to facilitate GCI simulation. The program is fairly easy to use is highly customizable. LotATC provides many features to aid a GCI.

* The creation of persistant BRAAs
* IFF features
* An ATC mode
* The ability to call BRAAs from the bullseye
* A scale which can be used to respond to Picture calls
* The ability to draw on the map

For more information on LotATC and how to use the software see [https://wiki.hoggitworld.com/view/LotATC LotATC]

== Coordinating with human GCI/AWACS ==
A couple guidelines from the players point of view

Inform AWACS when you tune in or tune out of the AWACS frequency.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F18, 10nm North of Anapa, checking in for CAP”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single Mirage 2000, checking in for CAP”</pre>

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, bingo fuel, RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 100/35”</pre>

Do not clutter the AWACS frequency with off-topic chatter, use the correct frequencies as stated in mission briefing.

Do not read back a BRA call. Simply acknowledge you received and understood the message by saying your callsign. If you did not understand the transmission, ask AWACS to repeat.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA 100/45, 20 thousand, flank north west”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Uzi 1-1”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, say again”</pre>

Getting started with GCI/AWACS

2022-09-04T13:19:08Z

Marlan: /* Miscellaneous */

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

'''''Disclaimer''''' 
''This guide is compiled using information available to the public and information based on personal experience in DCS World. This guide does not in any way, shape or form represent real life GCI/AWACS operations or techniques nor is it based on real life experience.''

== What is GCI/AWACS ==
[[File:e3_awacs.jpg|thumb|frame|right|Boeing E-3 Sentry]]
GCI stands for '''G'''round-'''C'''ontrolled '''I'''nterception, an air defence tactic which developed during World War I. One or more radar stations or other observational stations are linked to a command communications centre which guides interceptor aircraft to airborne targets.

Today, GCI has mostly been replaced by Airborne Early Warning and Control (AEW&C) aircraft or more commonly referred to as AWACS ('''A'''irborne '''W'''arning '''A'''nd '''C'''ontrol '''S'''ystem). While AEW&C is expensive and vulnerable in comparison to GCI systems, it has a mobility advantage. In reality a combination of both systems is often used.

AWACS aircraft are generally speaking big, modified planes with a long-range radar mounted on top. The main radar antenna is mounted on a turntable housed in a circular rotodome, which is 9m (30 feet) in diameter, elliptical in cross-section and 1.8m deep at its centre. The radar system can detect, track and identify low-flying aircraft at approximately 370 km (200 nautical miles) and high-level aircraft at much greater distances.

== AI AWACS in DCS World ==
In DCS World the NATO AWACS comes in the form of the Boeing E-3 Sentry and the Russian equivalent is the Beriev A-50. The player can contact the allied AWACS via the ingame comms menu on the specified frequency in the mission briefing.

=== Comms menu ===
;Vector to bullseye
: The AWACS will provide the player with a bearing and range to bullseye

;Vector to home plate
: The AWACS will provide the player with a bearing and range from bullseye to their home airfield

;Vector to tanker
: The AWACS will provide the player with a bearing and range from bullseye to the tanker

;Request BOGEY DOPE
: The AWACS will provide the player a BRAA call to the closest airborne threat.

;Request PICTURE
: The AWACS will provide the player with BRA calls for each group from bullseye

;DECLARE
: The AWACS will identify friend or foe of a radar locked target

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

=== Understanding BRAA calls ===
[[File:aspect.jpg|thumb|frame|right|500x|400px|Figure 1]]
BRAA stands for '''B'''earing '''R'''ange '''A'''ltitude '''A'''spect from your current location.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">BRAA, 183/10, 2 thousand, hot</pre> would mean the target is located at 183 degrees, 10 nautical miles away, and at 2000 feet coming directly towards you. North is 360. For aspect see figure 1.

=== Pronunciation ===
Instead of
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi 1-1, Magic, BRAA, 183 for 10 at 2000, hot"</pre>
it is recommended to omit the "for" and "at", and to use short pauses (here indicated with "..."):
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi one one ... Magic ... BRAA ... one eight zero ... ten ... two thousand ... hot"</pre>

=== Understanding bullseye ===
Bullseye is a fixed point on the map determined pre-mission. All allied aircraft can relate to this point. When receiving a bullseye call, simply use the BRA format with bullseye as starting point. Bullseye in DCS is represented with the following symbols
[[File:bullseye.png|thumb|frame|center|1000x|800px|Left:Bullseye representation in DCS World - Right: Bullseye details]]

== Human GCI/AWACS ==
In DCS World, players can take the role of GCI/AWACS on multiplayer servers to assist your fellow pilots and friends. In the following sections we’ll go over the basics of airspace management, threat assessment, callsigns, brevity and some useful tools.

Before you begin as a GCI/AWACS controller on a server go over this short checklist:
* Pick a suitable callsign

* Check and confirm the radio frequencies used for GCI/AWACS, general communications and air traffic control
* Tune in the correct frequencies on SRS
* Be in the correct server slot (if necessary)
* Have your tools set up and running
* Announce GCI/AWACS will be available over COMMS and CHAT. State the correct frequency and callsign
<pre style="background-color: #ccc;font-family: 'Lucida Console'">all flights on frequency be advised <callsign> will be available on <frequency> for GCI/AWACS</pre>
* If you are on the Hoggit Discord and are registering as a GAW GCI controller, the appropriate command on discord would be "!gci sunrise GAW <callsign, frequency, any other remarks>" command, use "!gci midnight" when you're finished with your session.

=== Airspace management ===
As a controller your goal is to manage both friendly and hostile airspace. You’ll want to direct your allied flights to intercept enemy threats while at the same time making sure your friendly airspace stays protected.

Divide the airspace you’ll be controlling into two sectors.
# a friendly sector
# a hostile sector

Divide sector 1, your friendly sector, into subsectors based on strategic locations like airfields or a FARPs.

Next, you can assign your available CAP flights to the subsectors you created, and have them patrol or set up orbit. This way you can ensure that
* your allied flights are in proximity to allied aircraft and able to support
* your allied aircraft are not spread out or alone in hostile airspace
* your allied aircraft are in range of a tanker or airfield
* your friendly sector is protected

=== Threat assessment ===
With your airspace divided into sectors and your CAP flights on station you can start intercepting enemy threats. There are 2 major things you want to pay close attention to at all times.
* Where are your allied aircraft in relation to your sectors
* Where are the enemy aircraft in relation to your sectors

Before making a decision to direct your allied flights to intercept, you want to assess the threat
# '''Distance''': what is the distance between the threat and the nearby sector or allied aircraft
# '''Number''': how many enemy aircraft make up the threat
# '''Type''': which type is the enemy threat
# ('''State'''): have they been engaged prior and thus used counter measures and/or weapons

When you have gathered this info you can make a decision to either:
* direct one or more allied aircraft to intercept the threat
* direct one or more aircraft away from the threat to nearby SAM cover
* direct one or more allied aircraft to support engaged allied aircraft

In case you are unsure and need extra information before making a decision, contact your allied flights and ask for a fuel and/or weapons state.

When directing your allied flights to intercept, try to keep them in proximity of other allied flights, so you have enough time to send in support if needed. Do not direct your allied flights into enemy airspace and SAM range without support.

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

=== Callsigns and radio communication ===
When acting as GCI/AWACS controller you want to make sure you have a callsign which
* is clear
* is easy to pronounce
* does not cause confusion
* is not ridiculous

Commonly used callsigns for GCI/AWACS are
* Overlord
* Magic
* Showtime
* Darkstar
* Goliath
* Wizard
* Griffin
* Bigfoot

As GCI/AWACS controller you’ll have to relay a lot of information in a clear, concise and easy to understand manner, usually in a short amount of time. It is important to have a good microphone set up, to speak loud and clear, articulate, not to speak too quickly and use the NATO phonetic alphabet to avoid confusion. We’ll discuss some examples below.

==== Responding to flights checking in ====
When allied flights switch to general comms or designated AWACS comms after take off, they’ll most likely check in on the frequency and let you know who they are and what their intentions are.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F-18, 10 miles North of Anapa, checking in for CAP”</pre>

In the above example a player lets you know who they are, where they are and what their intentions are. You can respond to acknowledge (and task them if desired).
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Radar Contact, Alpha Check, Bullseye 123/45.”</pre>
"Alpha Check Bullseye" is the bearing from the bullseye TO the fighter, and verifies they understand/have the correct bullseye reference point.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima Charlie, standby for tasking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima, Charlie, fly heading 100/20, anchor at Krymsk”</pre>

==== Directing allied aircraft to intercept ====
When directing aircraft to intercept you want to be clear and concise. Start with who you are talking to, who you are and provide a Bullseye or BRAA call (and optional additional information). It is important to pronounce heading as single digits. For example ‘100’ would be ‘one, zero, zero.’ Targeting technically should be done using bullseye and is more helpful to other players (who know how to use it), that said, many players are not familiar with bullseye so BRAA can be used as well.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/40, 15 thousand, flank north west, hostile.”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/60, 500 feet, hot, hostile, 2 contacts, fulcrum.”</pre>

==== Responding to a Bogey Dope request ====
When a player asks for a Bogey Dope, they are asking for the nearest hostile. Locate the aircraft who made the request, and provide them a BRA to the nearest hostile.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA, 257/15, 10 thousand, drag east”</pre>

When there are no hostile aircraft on scope
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Clean”</pre>

==== Responding to a DECLARE request ====
When you receive a DECLARE request, you are asked to identify friend or foe of a locked target.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, Bullseye 204/8, 12 thousand, DECLARE.”</pre>
or use BRAA (not technically correct, but fine here)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, BRAA 090/15, 12 thousand, DECLARE.”</pre>
Response:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Group, Bullseye 204/8, 12 thousand, hostile, single contact, flanker”</pre>
(fill-ins "single contact" and "flanker" are optional)

==== Miscellaneous ====
Sometimes you will need to ask for additional information, or provide additional information.

Return to base (RTB)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, winchester RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 010/35”</pre>

Ask for state
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, say state”</pre>
Typically, yellow means a fighter can take at least one more engagement, where red means a fighter is unable.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, fuel green, weapons green”</pre>
or
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, 4/1/2 by 7 point 5”</pre>
"4/1/2" is equivalent to 4 active missiles (e.g. AIM-120), 1 semi-active missile (e.g. AIM-7) and 2 infrared missiles (e.g. AIM-9) with 7,500lbs of fuel remaining. "MINUS" can be added to indicate they do not have, or have insufficient guns. (e.g. "Uzi 1-1, 4/1/2, minus, by 7 point 5")

Inform aircraft to wait for instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, standby”</pre>

Ignore last transmitted message/instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, disregard last”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA 070/5, ... disregard, BRAA 090/5, 7000, hot”</pre>

Identify unknown transmitting aircraft
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Last transmitting aircraft, state callsign”</pre>

Inform aircraft about incoming missiles or missile launches (unrealistic, generally only possible with F10 map)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, SAM, bearing 090”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, Missile, bearing 090”</pre>

=== Tools ===
==== SRS AWACS mode (eam) ====
The standard SRS radio overlay only displays up to 3 radios and 1 intercom. The AWACS overlay provides up to 10 radios, which you can manually tune and 1 intercom.

You can use SRS without running DCS World, by using the external AWACS mode (EAM). provide your EAM username and the EAM coalition password. The coalition password is provided by the server admin, or in the server briefing. This is not always available.

==== F10 map, icons and the ruler tool ====
The ingame F10 map is where you’ll spend most of your time doing GCI/AWACS. It provides several functions which you can toggle on or off by personal preference
* health bars
* SAM and AAA detection range indicators
* SAM and AAA engagement range indicators
* grid
* labels indicating type and name
* ruler tool

The most important function you’ll use is the ruler tool. It allows you to create a line from point A to point B and provides you with the length in nautical miles and the heading. When intercepting enemy aircraft you can use the ruler tool to draw a line from your allied aircraft A to the hostile aircraft B and read the distance in nautical miles and the heading indicated on the top bar. When you click on the enemy aircraft icon, you can read its altitude, speed in knots, heading and type on the bottom left.

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

==== LotATC ====
LotATC is an optional program one can use to facilitate GCI simulation. The program is fairly easy to use is highly customizable. LotATC provides many features to aid a GCI.

* The creation of persistant BRAAs
* IFF features
* An ATC mode
* The ability to call BRAAs from the bullseye
* A scale which can be used to respond to Picture calls
* The ability to draw on the map

For more information on LotATC and how to use the software see [https://wiki.hoggitworld.com/view/LotATC LotATC]

== Coordinating with human GCI/AWACS ==
A couple guidelines from the players point of view

Inform AWACS when you tune in or tune out of the AWACS frequency.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F18, 10nm North of Anapa, checking in for CAP”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single Mirage 2000, checking in for CAP”</pre>

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, bingo fuel, RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 100/35”</pre>

Do not clutter the AWACS frequency with off-topic chatter, use the correct frequencies as stated in mission briefing.

Do not read back a BRA call. Simply acknowledge you received and understood the message by saying your callsign. If you did not understand the transmission, ask AWACS to repeat.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA 100/45, 20 thousand, flank north west”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Uzi 1-1”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, say again”</pre>

Getting started with GCI/AWACS

2022-09-04T13:09:40Z

Marlan: /* Responding to a Bogey Dope request */

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

'''''Disclaimer''''' 
''This guide is compiled using information available to the public and information based on personal experience in DCS World. This guide does not in any way, shape or form represent real life GCI/AWACS operations or techniques nor is it based on real life experience.''

== What is GCI/AWACS ==
[[File:e3_awacs.jpg|thumb|frame|right|Boeing E-3 Sentry]]
GCI stands for '''G'''round-'''C'''ontrolled '''I'''nterception, an air defence tactic which developed during World War I. One or more radar stations or other observational stations are linked to a command communications centre which guides interceptor aircraft to airborne targets.

Today, GCI has mostly been replaced by Airborne Early Warning and Control (AEW&C) aircraft or more commonly referred to as AWACS ('''A'''irborne '''W'''arning '''A'''nd '''C'''ontrol '''S'''ystem). While AEW&C is expensive and vulnerable in comparison to GCI systems, it has a mobility advantage. In reality a combination of both systems is often used.

AWACS aircraft are generally speaking big, modified planes with a long-range radar mounted on top. The main radar antenna is mounted on a turntable housed in a circular rotodome, which is 9m (30 feet) in diameter, elliptical in cross-section and 1.8m deep at its centre. The radar system can detect, track and identify low-flying aircraft at approximately 370 km (200 nautical miles) and high-level aircraft at much greater distances.

== AI AWACS in DCS World ==
In DCS World the NATO AWACS comes in the form of the Boeing E-3 Sentry and the Russian equivalent is the Beriev A-50. The player can contact the allied AWACS via the ingame comms menu on the specified frequency in the mission briefing.

=== Comms menu ===
;Vector to bullseye
: The AWACS will provide the player with a bearing and range to bullseye

;Vector to home plate
: The AWACS will provide the player with a bearing and range from bullseye to their home airfield

;Vector to tanker
: The AWACS will provide the player with a bearing and range from bullseye to the tanker

;Request BOGEY DOPE
: The AWACS will provide the player a BRAA call to the closest airborne threat.

;Request PICTURE
: The AWACS will provide the player with BRA calls for each group from bullseye

;DECLARE
: The AWACS will identify friend or foe of a radar locked target

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

=== Understanding BRAA calls ===
[[File:aspect.jpg|thumb|frame|right|500x|400px|Figure 1]]
BRAA stands for '''B'''earing '''R'''ange '''A'''ltitude '''A'''spect from your current location.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">BRAA, 183/10, 2 thousand, hot</pre> would mean the target is located at 183 degrees, 10 nautical miles away, and at 2000 feet coming directly towards you. North is 360. For aspect see figure 1.

=== Pronunciation ===
Instead of
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi 1-1, Magic, BRAA, 183 for 10 at 2000, hot"</pre>
it is recommended to omit the "for" and "at", and to use short pauses (here indicated with "..."):
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi one one ... Magic ... BRAA ... one eight zero ... ten ... two thousand ... hot"</pre>

=== Understanding bullseye ===
Bullseye is a fixed point on the map determined pre-mission. All allied aircraft can relate to this point. When receiving a bullseye call, simply use the BRA format with bullseye as starting point. Bullseye in DCS is represented with the following symbols
[[File:bullseye.png|thumb|frame|center|1000x|800px|Left:Bullseye representation in DCS World - Right: Bullseye details]]

== Human GCI/AWACS ==
In DCS World, players can take the role of GCI/AWACS on multiplayer servers to assist your fellow pilots and friends. In the following sections we’ll go over the basics of airspace management, threat assessment, callsigns, brevity and some useful tools.

Before you begin as a GCI/AWACS controller on a server go over this short checklist:
* Pick a suitable callsign

* Check and confirm the radio frequencies used for GCI/AWACS, general communications and air traffic control
* Tune in the correct frequencies on SRS
* Be in the correct server slot (if necessary)
* Have your tools set up and running
* Announce GCI/AWACS will be available over COMMS and CHAT. State the correct frequency and callsign
<pre style="background-color: #ccc;font-family: 'Lucida Console'">all flights on frequency be advised <callsign> will be available on <frequency> for GCI/AWACS</pre>
* If you are on the Hoggit Discord and are registering as a GAW GCI controller, the appropriate command on discord would be "!gci sunrise GAW <callsign, frequency, any other remarks>" command, use "!gci midnight" when you're finished with your session.

=== Airspace management ===
As a controller your goal is to manage both friendly and hostile airspace. You’ll want to direct your allied flights to intercept enemy threats while at the same time making sure your friendly airspace stays protected.

Divide the airspace you’ll be controlling into two sectors.
# a friendly sector
# a hostile sector

Divide sector 1, your friendly sector, into subsectors based on strategic locations like airfields or a FARPs.

Next, you can assign your available CAP flights to the subsectors you created, and have them patrol or set up orbit. This way you can ensure that
* your allied flights are in proximity to allied aircraft and able to support
* your allied aircraft are not spread out or alone in hostile airspace
* your allied aircraft are in range of a tanker or airfield
* your friendly sector is protected

=== Threat assessment ===
With your airspace divided into sectors and your CAP flights on station you can start intercepting enemy threats. There are 2 major things you want to pay close attention to at all times.
* Where are your allied aircraft in relation to your sectors
* Where are the enemy aircraft in relation to your sectors

Before making a decision to direct your allied flights to intercept, you want to assess the threat
# '''Distance''': what is the distance between the threat and the nearby sector or allied aircraft
# '''Number''': how many enemy aircraft make up the threat
# '''Type''': which type is the enemy threat
# ('''State'''): have they been engaged prior and thus used counter measures and/or weapons

When you have gathered this info you can make a decision to either:
* direct one or more allied aircraft to intercept the threat
* direct one or more aircraft away from the threat to nearby SAM cover
* direct one or more allied aircraft to support engaged allied aircraft

In case you are unsure and need extra information before making a decision, contact your allied flights and ask for a fuel and/or weapons state.

When directing your allied flights to intercept, try to keep them in proximity of other allied flights, so you have enough time to send in support if needed. Do not direct your allied flights into enemy airspace and SAM range without support.

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

=== Callsigns and radio communication ===
When acting as GCI/AWACS controller you want to make sure you have a callsign which
* is clear
* is easy to pronounce
* does not cause confusion
* is not ridiculous

Commonly used callsigns for GCI/AWACS are
* Overlord
* Magic
* Showtime
* Darkstar
* Goliath
* Wizard
* Griffin
* Bigfoot

As GCI/AWACS controller you’ll have to relay a lot of information in a clear, concise and easy to understand manner, usually in a short amount of time. It is important to have a good microphone set up, to speak loud and clear, articulate, not to speak too quickly and use the NATO phonetic alphabet to avoid confusion. We’ll discuss some examples below.

==== Responding to flights checking in ====
When allied flights switch to general comms or designated AWACS comms after take off, they’ll most likely check in on the frequency and let you know who they are and what their intentions are.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F-18, 10 miles North of Anapa, checking in for CAP”</pre>

In the above example a player lets you know who they are, where they are and what their intentions are. You can respond to acknowledge (and task them if desired).
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Radar Contact, Alpha Check, Bullseye 123/45.”</pre>
"Alpha Check Bullseye" is the bearing from the bullseye TO the fighter, and verifies they understand/have the correct bullseye reference point.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima Charlie, standby for tasking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima, Charlie, fly heading 100/20, anchor at Krymsk”</pre>

==== Directing allied aircraft to intercept ====
When directing aircraft to intercept you want to be clear and concise. Start with who you are talking to, who you are and provide a Bullseye or BRAA call (and optional additional information). It is important to pronounce heading as single digits. For example ‘100’ would be ‘one, zero, zero.’ Targeting technically should be done using bullseye and is more helpful to other players (who know how to use it), that said, many players are not familiar with bullseye so BRAA can be used as well.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/40, 15 thousand, flank north west, hostile.”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/60, 500 feet, hot, hostile, 2 contacts, fulcrum.”</pre>

==== Responding to a Bogey Dope request ====
When a player asks for a Bogey Dope, they are asking for the nearest hostile. Locate the aircraft who made the request, and provide them a BRA to the nearest hostile.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRAA, 257/15, 10 thousand, drag east”</pre>

When there are no hostile aircraft on scope
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Clean”</pre>

==== Responding to a DECLARE request ====
When you receive a DECLARE request, you are asked to identify friend or foe of a locked target.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, Bullseye 204/8, 12 thousand, DECLARE.”</pre>
or use BRAA (not technically correct, but fine here)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, BRAA 090/15, 12 thousand, DECLARE.”</pre>
Response:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Group, Bullseye 204/8, 12 thousand, hostile, single contact, flanker”</pre>
(fill-ins "single contact" and "flanker" are optional)

==== Miscellaneous ====
Sometimes you will need to ask for additional information, or provide additional information.

Return to base (RTB)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, winchester RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 010/35”</pre>

Ask for fuel state
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, state fuel”</pre>

Ask for weapons state:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, state weapons”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, 4/1/2 plus”</pre>
Note: Number of ARH, SARH, and IR-seeking missiles, and plus for Guns.

Inform aircraft to wait for instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, standby”</pre>

Ignore last transmitted message/instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, disregard last”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA 070/5, ... disregard, BRA 090/5, 7000, hot”</pre>

Identify unknown transmitting aircraft
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, request Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Last transmitting aircraft, state callsign”</pre>

Inform aircraft about incoming missiles or missile launches (unrealistic, generally only possible with F10 map)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, SAM, bearing 090”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, Missile, bearing 090”</pre>

=== Tools ===
==== SRS AWACS mode (eam) ====
The standard SRS radio overlay only displays up to 3 radios and 1 intercom. The AWACS overlay provides up to 10 radios, which you can manually tune and 1 intercom.

You can use SRS without running DCS World, by using the external AWACS mode (EAM). provide your EAM username and the EAM coalition password. The coalition password is provided by the server admin, or in the server briefing. This is not always available.

==== F10 map, icons and the ruler tool ====
The ingame F10 map is where you’ll spend most of your time doing GCI/AWACS. It provides several functions which you can toggle on or off by personal preference
* health bars
* SAM and AAA detection range indicators
* SAM and AAA engagement range indicators
* grid
* labels indicating type and name
* ruler tool

The most important function you’ll use is the ruler tool. It allows you to create a line from point A to point B and provides you with the length in nautical miles and the heading. When intercepting enemy aircraft you can use the ruler tool to draw a line from your allied aircraft A to the hostile aircraft B and read the distance in nautical miles and the heading indicated on the top bar. When you click on the enemy aircraft icon, you can read its altitude, speed in knots, heading and type on the bottom left.

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

==== LotATC ====
LotATC is an optional program one can use to facilitate GCI simulation. The program is fairly easy to use is highly customizable. LotATC provides many features to aid a GCI.

* The creation of persistant BRAAs
* IFF features
* An ATC mode
* The ability to call BRAAs from the bullseye
* A scale which can be used to respond to Picture calls
* The ability to draw on the map

For more information on LotATC and how to use the software see [https://wiki.hoggitworld.com/view/LotATC LotATC]

== Coordinating with human GCI/AWACS ==
A couple guidelines from the players point of view

Inform AWACS when you tune in or tune out of the AWACS frequency.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F18, 10nm North of Anapa, checking in for CAP”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single Mirage 2000, checking in for CAP”</pre>

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, bingo fuel, RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 100/35”</pre>

Do not clutter the AWACS frequency with off-topic chatter, use the correct frequencies as stated in mission briefing.

Do not read back a BRA call. Simply acknowledge you received and understood the message by saying your callsign. If you did not understand the transmission, ask AWACS to repeat.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA 100/45, 20 thousand, flank north west”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Uzi 1-1”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, say again”</pre>

Getting started with GCI/AWACS

2022-09-04T13:09:04Z

Marlan: /* Directing allied aircraft to intercept */

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

'''''Disclaimer''''' 
''This guide is compiled using information available to the public and information based on personal experience in DCS World. This guide does not in any way, shape or form represent real life GCI/AWACS operations or techniques nor is it based on real life experience.''

== What is GCI/AWACS ==
[[File:e3_awacs.jpg|thumb|frame|right|Boeing E-3 Sentry]]
GCI stands for '''G'''round-'''C'''ontrolled '''I'''nterception, an air defence tactic which developed during World War I. One or more radar stations or other observational stations are linked to a command communications centre which guides interceptor aircraft to airborne targets.

Today, GCI has mostly been replaced by Airborne Early Warning and Control (AEW&C) aircraft or more commonly referred to as AWACS ('''A'''irborne '''W'''arning '''A'''nd '''C'''ontrol '''S'''ystem). While AEW&C is expensive and vulnerable in comparison to GCI systems, it has a mobility advantage. In reality a combination of both systems is often used.

AWACS aircraft are generally speaking big, modified planes with a long-range radar mounted on top. The main radar antenna is mounted on a turntable housed in a circular rotodome, which is 9m (30 feet) in diameter, elliptical in cross-section and 1.8m deep at its centre. The radar system can detect, track and identify low-flying aircraft at approximately 370 km (200 nautical miles) and high-level aircraft at much greater distances.

== AI AWACS in DCS World ==
In DCS World the NATO AWACS comes in the form of the Boeing E-3 Sentry and the Russian equivalent is the Beriev A-50. The player can contact the allied AWACS via the ingame comms menu on the specified frequency in the mission briefing.

=== Comms menu ===
;Vector to bullseye
: The AWACS will provide the player with a bearing and range to bullseye

;Vector to home plate
: The AWACS will provide the player with a bearing and range from bullseye to their home airfield

;Vector to tanker
: The AWACS will provide the player with a bearing and range from bullseye to the tanker

;Request BOGEY DOPE
: The AWACS will provide the player a BRAA call to the closest airborne threat.

;Request PICTURE
: The AWACS will provide the player with BRA calls for each group from bullseye

;DECLARE
: The AWACS will identify friend or foe of a radar locked target

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

=== Understanding BRAA calls ===
[[File:aspect.jpg|thumb|frame|right|500x|400px|Figure 1]]
BRAA stands for '''B'''earing '''R'''ange '''A'''ltitude '''A'''spect from your current location.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">BRAA, 183/10, 2 thousand, hot</pre> would mean the target is located at 183 degrees, 10 nautical miles away, and at 2000 feet coming directly towards you. North is 360. For aspect see figure 1.

=== Pronunciation ===
Instead of
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi 1-1, Magic, BRAA, 183 for 10 at 2000, hot"</pre>
it is recommended to omit the "for" and "at", and to use short pauses (here indicated with "..."):
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi one one ... Magic ... BRAA ... one eight zero ... ten ... two thousand ... hot"</pre>

=== Understanding bullseye ===
Bullseye is a fixed point on the map determined pre-mission. All allied aircraft can relate to this point. When receiving a bullseye call, simply use the BRA format with bullseye as starting point. Bullseye in DCS is represented with the following symbols
[[File:bullseye.png|thumb|frame|center|1000x|800px|Left:Bullseye representation in DCS World - Right: Bullseye details]]

== Human GCI/AWACS ==
In DCS World, players can take the role of GCI/AWACS on multiplayer servers to assist your fellow pilots and friends. In the following sections we’ll go over the basics of airspace management, threat assessment, callsigns, brevity and some useful tools.

Before you begin as a GCI/AWACS controller on a server go over this short checklist:
* Pick a suitable callsign

* Check and confirm the radio frequencies used for GCI/AWACS, general communications and air traffic control
* Tune in the correct frequencies on SRS
* Be in the correct server slot (if necessary)
* Have your tools set up and running
* Announce GCI/AWACS will be available over COMMS and CHAT. State the correct frequency and callsign
<pre style="background-color: #ccc;font-family: 'Lucida Console'">all flights on frequency be advised <callsign> will be available on <frequency> for GCI/AWACS</pre>
* If you are on the Hoggit Discord and are registering as a GAW GCI controller, the appropriate command on discord would be "!gci sunrise GAW <callsign, frequency, any other remarks>" command, use "!gci midnight" when you're finished with your session.

=== Airspace management ===
As a controller your goal is to manage both friendly and hostile airspace. You’ll want to direct your allied flights to intercept enemy threats while at the same time making sure your friendly airspace stays protected.

Divide the airspace you’ll be controlling into two sectors.
# a friendly sector
# a hostile sector

Divide sector 1, your friendly sector, into subsectors based on strategic locations like airfields or a FARPs.

Next, you can assign your available CAP flights to the subsectors you created, and have them patrol or set up orbit. This way you can ensure that
* your allied flights are in proximity to allied aircraft and able to support
* your allied aircraft are not spread out or alone in hostile airspace
* your allied aircraft are in range of a tanker or airfield
* your friendly sector is protected

=== Threat assessment ===
With your airspace divided into sectors and your CAP flights on station you can start intercepting enemy threats. There are 2 major things you want to pay close attention to at all times.
* Where are your allied aircraft in relation to your sectors
* Where are the enemy aircraft in relation to your sectors

Before making a decision to direct your allied flights to intercept, you want to assess the threat
# '''Distance''': what is the distance between the threat and the nearby sector or allied aircraft
# '''Number''': how many enemy aircraft make up the threat
# '''Type''': which type is the enemy threat
# ('''State'''): have they been engaged prior and thus used counter measures and/or weapons

When you have gathered this info you can make a decision to either:
* direct one or more allied aircraft to intercept the threat
* direct one or more aircraft away from the threat to nearby SAM cover
* direct one or more allied aircraft to support engaged allied aircraft

In case you are unsure and need extra information before making a decision, contact your allied flights and ask for a fuel and/or weapons state.

When directing your allied flights to intercept, try to keep them in proximity of other allied flights, so you have enough time to send in support if needed. Do not direct your allied flights into enemy airspace and SAM range without support.

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

=== Callsigns and radio communication ===
When acting as GCI/AWACS controller you want to make sure you have a callsign which
* is clear
* is easy to pronounce
* does not cause confusion
* is not ridiculous

Commonly used callsigns for GCI/AWACS are
* Overlord
* Magic
* Showtime
* Darkstar
* Goliath
* Wizard
* Griffin
* Bigfoot

As GCI/AWACS controller you’ll have to relay a lot of information in a clear, concise and easy to understand manner, usually in a short amount of time. It is important to have a good microphone set up, to speak loud and clear, articulate, not to speak too quickly and use the NATO phonetic alphabet to avoid confusion. We’ll discuss some examples below.

==== Responding to flights checking in ====
When allied flights switch to general comms or designated AWACS comms after take off, they’ll most likely check in on the frequency and let you know who they are and what their intentions are.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F-18, 10 miles North of Anapa, checking in for CAP”</pre>

In the above example a player lets you know who they are, where they are and what their intentions are. You can respond to acknowledge (and task them if desired).
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Radar Contact, Alpha Check, Bullseye 123/45.”</pre>
"Alpha Check Bullseye" is the bearing from the bullseye TO the fighter, and verifies they understand/have the correct bullseye reference point.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima Charlie, standby for tasking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima, Charlie, fly heading 100/20, anchor at Krymsk”</pre>

==== Directing allied aircraft to intercept ====
When directing aircraft to intercept you want to be clear and concise. Start with who you are talking to, who you are and provide a Bullseye or BRAA call (and optional additional information). It is important to pronounce heading as single digits. For example ‘100’ would be ‘one, zero, zero.’ Targeting technically should be done using bullseye and is more helpful to other players (who know how to use it), that said, many players are not familiar with bullseye so BRAA can be used as well.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/40, 15 thousand, flank north west, hostile.”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/60, 500 feet, hot, hostile, 2 contacts, fulcrum.”</pre>

==== Responding to a Bogey Dope request ====
When a player asks for a Bogey Dope, they are asking for the nearest hostile. Locate the aircraft who made the request, and provide them a BRA to the nearest hostile.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA, 257/15, 10 thousand, drag east”</pre>

When there are no hostile aircraft on scope
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Clean”</pre>

==== Responding to a DECLARE request ====
When you receive a DECLARE request, you are asked to identify friend or foe of a locked target.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, Bullseye 204/8, 12 thousand, DECLARE.”</pre>
or use BRAA (not technically correct, but fine here)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, BRAA 090/15, 12 thousand, DECLARE.”</pre>
Response:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Group, Bullseye 204/8, 12 thousand, hostile, single contact, flanker”</pre>
(fill-ins "single contact" and "flanker" are optional)

==== Miscellaneous ====
Sometimes you will need to ask for additional information, or provide additional information.

Return to base (RTB)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, winchester RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 010/35”</pre>

Ask for fuel state
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, state fuel”</pre>

Ask for weapons state:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, state weapons”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, 4/1/2 plus”</pre>
Note: Number of ARH, SARH, and IR-seeking missiles, and plus for Guns.

Inform aircraft to wait for instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, standby”</pre>

Ignore last transmitted message/instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, disregard last”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA 070/5, ... disregard, BRA 090/5, 7000, hot”</pre>

Identify unknown transmitting aircraft
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, request Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Last transmitting aircraft, state callsign”</pre>

Inform aircraft about incoming missiles or missile launches (unrealistic, generally only possible with F10 map)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, SAM, bearing 090”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, Missile, bearing 090”</pre>

=== Tools ===
==== SRS AWACS mode (eam) ====
The standard SRS radio overlay only displays up to 3 radios and 1 intercom. The AWACS overlay provides up to 10 radios, which you can manually tune and 1 intercom.

You can use SRS without running DCS World, by using the external AWACS mode (EAM). provide your EAM username and the EAM coalition password. The coalition password is provided by the server admin, or in the server briefing. This is not always available.

==== F10 map, icons and the ruler tool ====
The ingame F10 map is where you’ll spend most of your time doing GCI/AWACS. It provides several functions which you can toggle on or off by personal preference
* health bars
* SAM and AAA detection range indicators
* SAM and AAA engagement range indicators
* grid
* labels indicating type and name
* ruler tool

The most important function you’ll use is the ruler tool. It allows you to create a line from point A to point B and provides you with the length in nautical miles and the heading. When intercepting enemy aircraft you can use the ruler tool to draw a line from your allied aircraft A to the hostile aircraft B and read the distance in nautical miles and the heading indicated on the top bar. When you click on the enemy aircraft icon, you can read its altitude, speed in knots, heading and type on the bottom left.

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

==== LotATC ====
LotATC is an optional program one can use to facilitate GCI simulation. The program is fairly easy to use is highly customizable. LotATC provides many features to aid a GCI.

* The creation of persistant BRAAs
* IFF features
* An ATC mode
* The ability to call BRAAs from the bullseye
* A scale which can be used to respond to Picture calls
* The ability to draw on the map

For more information on LotATC and how to use the software see [https://wiki.hoggitworld.com/view/LotATC LotATC]

== Coordinating with human GCI/AWACS ==
A couple guidelines from the players point of view

Inform AWACS when you tune in or tune out of the AWACS frequency.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F18, 10nm North of Anapa, checking in for CAP”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single Mirage 2000, checking in for CAP”</pre>

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, bingo fuel, RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 100/35”</pre>

Do not clutter the AWACS frequency with off-topic chatter, use the correct frequencies as stated in mission briefing.

Do not read back a BRA call. Simply acknowledge you received and understood the message by saying your callsign. If you did not understand the transmission, ask AWACS to repeat.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA 100/45, 20 thousand, flank north west”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Uzi 1-1”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, say again”</pre>

Getting started with GCI/AWACS

2022-09-04T13:06:50Z

Marlan: /* Understanding BRAA calls */

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

'''''Disclaimer''''' 
''This guide is compiled using information available to the public and information based on personal experience in DCS World. This guide does not in any way, shape or form represent real life GCI/AWACS operations or techniques nor is it based on real life experience.''

== What is GCI/AWACS ==
[[File:e3_awacs.jpg|thumb|frame|right|Boeing E-3 Sentry]]
GCI stands for '''G'''round-'''C'''ontrolled '''I'''nterception, an air defence tactic which developed during World War I. One or more radar stations or other observational stations are linked to a command communications centre which guides interceptor aircraft to airborne targets.

Today, GCI has mostly been replaced by Airborne Early Warning and Control (AEW&C) aircraft or more commonly referred to as AWACS ('''A'''irborne '''W'''arning '''A'''nd '''C'''ontrol '''S'''ystem). While AEW&C is expensive and vulnerable in comparison to GCI systems, it has a mobility advantage. In reality a combination of both systems is often used.

AWACS aircraft are generally speaking big, modified planes with a long-range radar mounted on top. The main radar antenna is mounted on a turntable housed in a circular rotodome, which is 9m (30 feet) in diameter, elliptical in cross-section and 1.8m deep at its centre. The radar system can detect, track and identify low-flying aircraft at approximately 370 km (200 nautical miles) and high-level aircraft at much greater distances.

== AI AWACS in DCS World ==
In DCS World the NATO AWACS comes in the form of the Boeing E-3 Sentry and the Russian equivalent is the Beriev A-50. The player can contact the allied AWACS via the ingame comms menu on the specified frequency in the mission briefing.

=== Comms menu ===
;Vector to bullseye
: The AWACS will provide the player with a bearing and range to bullseye

;Vector to home plate
: The AWACS will provide the player with a bearing and range from bullseye to their home airfield

;Vector to tanker
: The AWACS will provide the player with a bearing and range from bullseye to the tanker

;Request BOGEY DOPE
: The AWACS will provide the player a BRAA call to the closest airborne threat.

;Request PICTURE
: The AWACS will provide the player with BRA calls for each group from bullseye

;DECLARE
: The AWACS will identify friend or foe of a radar locked target

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

=== Understanding BRAA calls ===
[[File:aspect.jpg|thumb|frame|right|500x|400px|Figure 1]]
BRAA stands for '''B'''earing '''R'''ange '''A'''ltitude '''A'''spect from your current location.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">BRAA, 183/10, 2 thousand, hot</pre> would mean the target is located at 183 degrees, 10 nautical miles away, and at 2000 feet coming directly towards you. North is 360. For aspect see figure 1.

=== Pronunciation ===
Instead of
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi 1-1, Magic, BRAA, 183 for 10 at 2000, hot"</pre>
it is recommended to omit the "for" and "at", and to use short pauses (here indicated with "..."):
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi one one ... Magic ... BRAA ... one eight zero ... ten ... two thousand ... hot"</pre>

=== Understanding bullseye ===
Bullseye is a fixed point on the map determined pre-mission. All allied aircraft can relate to this point. When receiving a bullseye call, simply use the BRA format with bullseye as starting point. Bullseye in DCS is represented with the following symbols
[[File:bullseye.png|thumb|frame|center|1000x|800px|Left:Bullseye representation in DCS World - Right: Bullseye details]]

== Human GCI/AWACS ==
In DCS World, players can take the role of GCI/AWACS on multiplayer servers to assist your fellow pilots and friends. In the following sections we’ll go over the basics of airspace management, threat assessment, callsigns, brevity and some useful tools.

Before you begin as a GCI/AWACS controller on a server go over this short checklist:
* Pick a suitable callsign

* Check and confirm the radio frequencies used for GCI/AWACS, general communications and air traffic control
* Tune in the correct frequencies on SRS
* Be in the correct server slot (if necessary)
* Have your tools set up and running
* Announce GCI/AWACS will be available over COMMS and CHAT. State the correct frequency and callsign
<pre style="background-color: #ccc;font-family: 'Lucida Console'">all flights on frequency be advised <callsign> will be available on <frequency> for GCI/AWACS</pre>
* If you are on the Hoggit Discord and are registering as a GAW GCI controller, the appropriate command on discord would be "!gci sunrise GAW <callsign, frequency, any other remarks>" command, use "!gci midnight" when you're finished with your session.

=== Airspace management ===
As a controller your goal is to manage both friendly and hostile airspace. You’ll want to direct your allied flights to intercept enemy threats while at the same time making sure your friendly airspace stays protected.

Divide the airspace you’ll be controlling into two sectors.
# a friendly sector
# a hostile sector

Divide sector 1, your friendly sector, into subsectors based on strategic locations like airfields or a FARPs.

Next, you can assign your available CAP flights to the subsectors you created, and have them patrol or set up orbit. This way you can ensure that
* your allied flights are in proximity to allied aircraft and able to support
* your allied aircraft are not spread out or alone in hostile airspace
* your allied aircraft are in range of a tanker or airfield
* your friendly sector is protected

=== Threat assessment ===
With your airspace divided into sectors and your CAP flights on station you can start intercepting enemy threats. There are 2 major things you want to pay close attention to at all times.
* Where are your allied aircraft in relation to your sectors
* Where are the enemy aircraft in relation to your sectors

Before making a decision to direct your allied flights to intercept, you want to assess the threat
# '''Distance''': what is the distance between the threat and the nearby sector or allied aircraft
# '''Number''': how many enemy aircraft make up the threat
# '''Type''': which type is the enemy threat
# ('''State'''): have they been engaged prior and thus used counter measures and/or weapons

When you have gathered this info you can make a decision to either:
* direct one or more allied aircraft to intercept the threat
* direct one or more aircraft away from the threat to nearby SAM cover
* direct one or more allied aircraft to support engaged allied aircraft

In case you are unsure and need extra information before making a decision, contact your allied flights and ask for a fuel and/or weapons state.

When directing your allied flights to intercept, try to keep them in proximity of other allied flights, so you have enough time to send in support if needed. Do not direct your allied flights into enemy airspace and SAM range without support.

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

=== Callsigns and radio communication ===
When acting as GCI/AWACS controller you want to make sure you have a callsign which
* is clear
* is easy to pronounce
* does not cause confusion
* is not ridiculous

Commonly used callsigns for GCI/AWACS are
* Overlord
* Magic
* Showtime
* Darkstar
* Goliath
* Wizard
* Griffin
* Bigfoot

As GCI/AWACS controller you’ll have to relay a lot of information in a clear, concise and easy to understand manner, usually in a short amount of time. It is important to have a good microphone set up, to speak loud and clear, articulate, not to speak too quickly and use the NATO phonetic alphabet to avoid confusion. We’ll discuss some examples below.

==== Responding to flights checking in ====
When allied flights switch to general comms or designated AWACS comms after take off, they’ll most likely check in on the frequency and let you know who they are and what their intentions are.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F-18, 10 miles North of Anapa, checking in for CAP”</pre>

In the above example a player lets you know who they are, where they are and what their intentions are. You can respond to acknowledge (and task them if desired).
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Radar Contact, Alpha Check, Bullseye 123/45.”</pre>
"Alpha Check Bullseye" is the bearing from the bullseye TO the fighter, and verifies they understand/have the correct bullseye reference point.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima Charlie, standby for tasking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima, Charlie, fly heading 100/20, anchor at Krymsk”</pre>

==== Directing allied aircraft to intercept ====
When directing aircraft to intercept you want to be clear and concise. Start with who you are talking to, who you are and provide a BRA(A) call (and optional additional information). It is important to pronounce heading as single digits. For example ‘100’ would be ‘one, zero, zero.’

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/40, 15 thousand, flank north west, hostile.”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/60, 500 feet, hot, hostile, 2 contacts, fulcrum.”</pre>

==== Responding to a Bogey Dope request ====
When a player asks for a Bogey Dope, they are asking for the nearest hostile. Locate the aircraft who made the request, and provide them a BRA to the nearest hostile.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA, 257/15, 10 thousand, drag east”</pre>

When there are no hostile aircraft on scope
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Clean”</pre>

==== Responding to a DECLARE request ====
When you receive a DECLARE request, you are asked to identify friend or foe of a locked target.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, Bullseye 204/8, 12 thousand, DECLARE.”</pre>
or use BRAA (not technically correct, but fine here)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, BRAA 090/15, 12 thousand, DECLARE.”</pre>
Response:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Group, Bullseye 204/8, 12 thousand, hostile, single contact, flanker”</pre>
(fill-ins "single contact" and "flanker" are optional)

==== Miscellaneous ====
Sometimes you will need to ask for additional information, or provide additional information.

Return to base (RTB)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, winchester RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 010/35”</pre>

Ask for fuel state
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, state fuel”</pre>

Ask for weapons state:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, state weapons”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, 4/1/2 plus”</pre>
Note: Number of ARH, SARH, and IR-seeking missiles, and plus for Guns.

Inform aircraft to wait for instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, standby”</pre>

Ignore last transmitted message/instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, disregard last”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA 070/5, ... disregard, BRA 090/5, 7000, hot”</pre>

Identify unknown transmitting aircraft
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, request Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Last transmitting aircraft, state callsign”</pre>

Inform aircraft about incoming missiles or missile launches (unrealistic, generally only possible with F10 map)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, SAM, bearing 090”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, Missile, bearing 090”</pre>

=== Tools ===
==== SRS AWACS mode (eam) ====
The standard SRS radio overlay only displays up to 3 radios and 1 intercom. The AWACS overlay provides up to 10 radios, which you can manually tune and 1 intercom.

You can use SRS without running DCS World, by using the external AWACS mode (EAM). provide your EAM username and the EAM coalition password. The coalition password is provided by the server admin, or in the server briefing. This is not always available.

==== F10 map, icons and the ruler tool ====
The ingame F10 map is where you’ll spend most of your time doing GCI/AWACS. It provides several functions which you can toggle on or off by personal preference
* health bars
* SAM and AAA detection range indicators
* SAM and AAA engagement range indicators
* grid
* labels indicating type and name
* ruler tool

The most important function you’ll use is the ruler tool. It allows you to create a line from point A to point B and provides you with the length in nautical miles and the heading. When intercepting enemy aircraft you can use the ruler tool to draw a line from your allied aircraft A to the hostile aircraft B and read the distance in nautical miles and the heading indicated on the top bar. When you click on the enemy aircraft icon, you can read its altitude, speed in knots, heading and type on the bottom left.

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

==== LotATC ====
LotATC is an optional program one can use to facilitate GCI simulation. The program is fairly easy to use is highly customizable. LotATC provides many features to aid a GCI.

* The creation of persistant BRAAs
* IFF features
* An ATC mode
* The ability to call BRAAs from the bullseye
* A scale which can be used to respond to Picture calls
* The ability to draw on the map

For more information on LotATC and how to use the software see [https://wiki.hoggitworld.com/view/LotATC LotATC]

== Coordinating with human GCI/AWACS ==
A couple guidelines from the players point of view

Inform AWACS when you tune in or tune out of the AWACS frequency.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F18, 10nm North of Anapa, checking in for CAP”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single Mirage 2000, checking in for CAP”</pre>

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, bingo fuel, RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 100/35”</pre>

Do not clutter the AWACS frequency with off-topic chatter, use the correct frequencies as stated in mission briefing.

Do not read back a BRA call. Simply acknowledge you received and understood the message by saying your callsign. If you did not understand the transmission, ask AWACS to repeat.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA 100/45, 20 thousand, flank north west”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Uzi 1-1”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, say again”</pre>

Getting started with GCI/AWACS

2022-09-03T18:38:22Z

Marlan: /* Understanding BRAA calls */

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

'''''Disclaimer''''' 
''This guide is compiled using information available to the public and information based on personal experience in DCS World. This guide does not in any way, shape or form represent real life GCI/AWACS operations or techniques nor is it based on real life experience.''

== What is GCI/AWACS ==
[[File:e3_awacs.jpg|thumb|frame|right|Boeing E-3 Sentry]]
GCI stands for '''G'''round-'''C'''ontrolled '''I'''nterception, an air defence tactic which developed during World War I. One or more radar stations or other observational stations are linked to a command communications centre which guides interceptor aircraft to airborne targets.

Today, GCI has mostly been replaced by Airborne Early Warning and Control (AEW&C) aircraft or more commonly referred to as AWACS ('''A'''irborne '''W'''arning '''A'''nd '''C'''ontrol '''S'''ystem). While AEW&C is expensive and vulnerable in comparison to GCI systems, it has a mobility advantage. In reality a combination of both systems is often used.

AWACS aircraft are generally speaking big, modified planes with a long-range radar mounted on top. The main radar antenna is mounted on a turntable housed in a circular rotodome, which is 9m (30 feet) in diameter, elliptical in cross-section and 1.8m deep at its centre. The radar system can detect, track and identify low-flying aircraft at approximately 370 km (200 nautical miles) and high-level aircraft at much greater distances.

== AI AWACS in DCS World ==
In DCS World the NATO AWACS comes in the form of the Boeing E-3 Sentry and the Russian equivalent is the Beriev A-50. The player can contact the allied AWACS via the ingame comms menu on the specified frequency in the mission briefing.

=== Comms menu ===
;Vector to bullseye
: The AWACS will provide the player with a bearing and range to bullseye

;Vector to home plate
: The AWACS will provide the player with a bearing and range from bullseye to their home airfield

;Vector to tanker
: The AWACS will provide the player with a bearing and range from bullseye to the tanker

;Request BOGEY DOPE
: The AWACS will provide the player a BRAA call to the closest airborne threat.

;Request PICTURE
: The AWACS will provide the player with BRA calls for each group from bullseye

;DECLARE
: The AWACS will identify friend or foe of a radar locked target

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

=== Understanding BRAA calls ===
[[File:aspect.jpg|thumb|frame|right|500x|400px|Figure 1]]
BRAA stands for '''B'''earing '''R'''ange '''A'''ltitude '''A'''spect from your current location.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">BRAA, 183/10, 2000, hot</pre> would mean the target is located at 183 degrees, 10 nautical miles away, and at 2000 feet coming directly towards you. North is 360. For aspect see figure 1.

=== Pronunciation ===
Instead of
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi 1-1, Magic, BRAA, 183 for 10 at 2000, hot"</pre>
it is recommended to omit the "for" and "at", and to use short pauses (here indicated with "..."):
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi one one ... Magic ... BRAA ... one eight zero ... ten ... two thousand ... hot"</pre>

=== Understanding bullseye ===
Bullseye is a fixed point on the map determined pre-mission. All allied aircraft can relate to this point. When receiving a bullseye call, simply use the BRA format with bullseye as starting point. Bullseye in DCS is represented with the following symbols
[[File:bullseye.png|thumb|frame|center|1000x|800px|Left:Bullseye representation in DCS World - Right: Bullseye details]]

== Human GCI/AWACS ==
In DCS World, players can take the role of GCI/AWACS on multiplayer servers to assist your fellow pilots and friends. In the following sections we’ll go over the basics of airspace management, threat assessment, callsigns, brevity and some useful tools.

Before you begin as a GCI/AWACS controller on a server go over this short checklist:
* Pick a suitable callsign

* Check and confirm the radio frequencies used for GCI/AWACS, general communications and air traffic control
* Tune in the correct frequencies on SRS
* Be in the correct server slot (if necessary)
* Have your tools set up and running
* Announce GCI/AWACS will be available over COMMS and CHAT. State the correct frequency and callsign
<pre style="background-color: #ccc;font-family: 'Lucida Console'">all flights on frequency be advised <callsign> will be available on <frequency> for GCI/AWACS</pre>
* If you are on the Hoggit Discord and are registering as a GAW GCI controller, the appropriate command on discord would be "!gci sunrise GAW <callsign, frequency, any other remarks>" command, use "!gci midnight" when you're finished with your session.

=== Airspace management ===
As a controller your goal is to manage both friendly and hostile airspace. You’ll want to direct your allied flights to intercept enemy threats while at the same time making sure your friendly airspace stays protected.

Divide the airspace you’ll be controlling into two sectors.
# a friendly sector
# a hostile sector

Divide sector 1, your friendly sector, into subsectors based on strategic locations like airfields or a FARPs.

Next, you can assign your available CAP flights to the subsectors you created, and have them patrol or set up orbit. This way you can ensure that
* your allied flights are in proximity to allied aircraft and able to support
* your allied aircraft are not spread out or alone in hostile airspace
* your allied aircraft are in range of a tanker or airfield
* your friendly sector is protected

=== Threat assessment ===
With your airspace divided into sectors and your CAP flights on station you can start intercepting enemy threats. There are 2 major things you want to pay close attention to at all times.
* Where are your allied aircraft in relation to your sectors
* Where are the enemy aircraft in relation to your sectors

Before making a decision to direct your allied flights to intercept, you want to assess the threat
# '''Distance''': what is the distance between the threat and the nearby sector or allied aircraft
# '''Number''': how many enemy aircraft make up the threat
# '''Type''': which type is the enemy threat
# ('''State'''): have they been engaged prior and thus used counter measures and/or weapons

When you have gathered this info you can make a decision to either:
* direct one or more allied aircraft to intercept the threat
* direct one or more aircraft away from the threat to nearby SAM cover
* direct one or more allied aircraft to support engaged allied aircraft

In case you are unsure and need extra information before making a decision, contact your allied flights and ask for a fuel and/or weapons state.

When directing your allied flights to intercept, try to keep them in proximity of other allied flights, so you have enough time to send in support if needed. Do not direct your allied flights into enemy airspace and SAM range without support.

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

=== Callsigns and radio communication ===
When acting as GCI/AWACS controller you want to make sure you have a callsign which
* is clear
* is easy to pronounce
* does not cause confusion
* is not ridiculous

Commonly used callsigns for GCI/AWACS are
* Overlord
* Magic
* Showtime
* Darkstar
* Goliath
* Wizard
* Griffin
* Bigfoot

As GCI/AWACS controller you’ll have to relay a lot of information in a clear, concise and easy to understand manner, usually in a short amount of time. It is important to have a good microphone set up, to speak loud and clear, articulate, not to speak too quickly and use the NATO phonetic alphabet to avoid confusion. We’ll discuss some examples below.

==== Responding to flights checking in ====
When allied flights switch to general comms or designated AWACS comms after take off, they’ll most likely check in on the frequency and let you know who they are and what their intentions are.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F-18, 10 miles North of Anapa, checking in for CAP”</pre>

In the above example a player lets you know who they are, where they are and what their intentions are. You can respond to acknowledge (and task them if desired).
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Radar Contact, Alpha Check, Bullseye 123/45.”</pre>
"Alpha Check Bullseye" is the bearing from the bullseye TO the fighter, and verifies they understand/have the correct bullseye reference point.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima Charlie, standby for tasking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima, Charlie, fly heading 100/20, anchor at Krymsk”</pre>

==== Directing allied aircraft to intercept ====
When directing aircraft to intercept you want to be clear and concise. Start with who you are talking to, who you are and provide a BRA(A) call (and optional additional information). It is important to pronounce heading as single digits. For example ‘100’ would be ‘one, zero, zero.’

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/40, 15 thousand, flank north west, hostile.”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/60, 500 feet, hot, hostile, 2 contacts, fulcrum.”</pre>

==== Responding to a Bogey Dope request ====
When a player asks for a Bogey Dope, they are asking for the nearest hostile. Locate the aircraft who made the request, and provide them a BRA to the nearest hostile.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA, 257/15, 10 thousand, drag east”</pre>

When there are no hostile aircraft on scope
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Clean”</pre>

==== Responding to a DECLARE request ====
When you receive a DECLARE request, you are asked to identify friend or foe of a locked target.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, Bullseye 204/8, 12 thousand, DECLARE.”</pre>
or use BRAA (not technically correct, but fine here)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, BRAA 090/15, 12 thousand, DECLARE.”</pre>
Response:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Group, Bullseye 204/8, 12 thousand, hostile, single contact, flanker”</pre>
(fill-ins "single contact" and "flanker" are optional)

==== Miscellaneous ====
Sometimes you will need to ask for additional information, or provide additional information.

Return to base (RTB)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, winchester RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 010/35”</pre>

Ask for fuel state
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, state fuel”</pre>

Ask for weapons state:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, state weapons”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, 4/1/2 plus”</pre>
Note: Number of ARH, SARH, and IR-seeking missiles, and plus for Guns.

Inform aircraft to wait for instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, standby”</pre>

Ignore last transmitted message/instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, disregard last”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA 070/5, ... disregard, BRA 090/5, 7000, hot”</pre>

Identify unknown transmitting aircraft
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, request Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Last transmitting aircraft, state callsign”</pre>

Inform aircraft about incoming missiles or missile launches (unrealistic, generally only possible with F10 map)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, SAM, bearing 090”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, Missile, bearing 090”</pre>

=== Tools ===
==== SRS AWACS mode (eam) ====
The standard SRS radio overlay only displays up to 3 radios and 1 intercom. The AWACS overlay provides up to 10 radios, which you can manually tune and 1 intercom.

You can use SRS without running DCS World, by using the external AWACS mode (EAM). provide your EAM username and the EAM coalition password. The coalition password is provided by the server admin, or in the server briefing. This is not always available.

==== F10 map, icons and the ruler tool ====
The ingame F10 map is where you’ll spend most of your time doing GCI/AWACS. It provides several functions which you can toggle on or off by personal preference
* health bars
* SAM and AAA detection range indicators
* SAM and AAA engagement range indicators
* grid
* labels indicating type and name
* ruler tool

The most important function you’ll use is the ruler tool. It allows you to create a line from point A to point B and provides you with the length in nautical miles and the heading. When intercepting enemy aircraft you can use the ruler tool to draw a line from your allied aircraft A to the hostile aircraft B and read the distance in nautical miles and the heading indicated on the top bar. When you click on the enemy aircraft icon, you can read its altitude, speed in knots, heading and type on the bottom left.

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

==== LotATC ====
LotATC is an optional program one can use to facilitate GCI simulation. The program is fairly easy to use is highly customizable. LotATC provides many features to aid a GCI.

* The creation of persistant BRAAs
* IFF features
* An ATC mode
* The ability to call BRAAs from the bullseye
* A scale which can be used to respond to Picture calls
* The ability to draw on the map

For more information on LotATC and how to use the software see [https://wiki.hoggitworld.com/view/LotATC LotATC]

== Coordinating with human GCI/AWACS ==
A couple guidelines from the players point of view

Inform AWACS when you tune in or tune out of the AWACS frequency.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F18, 10nm North of Anapa, checking in for CAP”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single Mirage 2000, checking in for CAP”</pre>

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, bingo fuel, RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 100/35”</pre>

Do not clutter the AWACS frequency with off-topic chatter, use the correct frequencies as stated in mission briefing.

Do not read back a BRA call. Simply acknowledge you received and understood the message by saying your callsign. If you did not understand the transmission, ask AWACS to repeat.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA 100/45, 20 thousand, flank north west”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Uzi 1-1”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, say again”</pre>

Getting started with GCI/AWACS

2022-09-03T18:38:01Z

Marlan: /* Pronunciation */

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

'''''Disclaimer''''' 
''This guide is compiled using information available to the public and information based on personal experience in DCS World. This guide does not in any way, shape or form represent real life GCI/AWACS operations or techniques nor is it based on real life experience.''

== What is GCI/AWACS ==
[[File:e3_awacs.jpg|thumb|frame|right|Boeing E-3 Sentry]]
GCI stands for '''G'''round-'''C'''ontrolled '''I'''nterception, an air defence tactic which developed during World War I. One or more radar stations or other observational stations are linked to a command communications centre which guides interceptor aircraft to airborne targets.

Today, GCI has mostly been replaced by Airborne Early Warning and Control (AEW&C) aircraft or more commonly referred to as AWACS ('''A'''irborne '''W'''arning '''A'''nd '''C'''ontrol '''S'''ystem). While AEW&C is expensive and vulnerable in comparison to GCI systems, it has a mobility advantage. In reality a combination of both systems is often used.

AWACS aircraft are generally speaking big, modified planes with a long-range radar mounted on top. The main radar antenna is mounted on a turntable housed in a circular rotodome, which is 9m (30 feet) in diameter, elliptical in cross-section and 1.8m deep at its centre. The radar system can detect, track and identify low-flying aircraft at approximately 370 km (200 nautical miles) and high-level aircraft at much greater distances.

== AI AWACS in DCS World ==
In DCS World the NATO AWACS comes in the form of the Boeing E-3 Sentry and the Russian equivalent is the Beriev A-50. The player can contact the allied AWACS via the ingame comms menu on the specified frequency in the mission briefing.

=== Comms menu ===
;Vector to bullseye
: The AWACS will provide the player with a bearing and range to bullseye

;Vector to home plate
: The AWACS will provide the player with a bearing and range from bullseye to their home airfield

;Vector to tanker
: The AWACS will provide the player with a bearing and range from bullseye to the tanker

;Request BOGEY DOPE
: The AWACS will provide the player a BRAA call to the closest airborne threat.

;Request PICTURE
: The AWACS will provide the player with BRA calls for each group from bullseye

;DECLARE
: The AWACS will identify friend or foe of a radar locked target

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

=== Understanding BRAA calls ===
[[File:aspect.jpg|thumb|frame|right|500x|400px|Figure 1]]
BRAA stands for '''B'''earing '''R'''ange '''A'''ltitude '''A'''spect from your current location.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">BRA, 183, 10, 2000, hot</pre> would mean the target is located at 183 degrees, 10 nautical miles away, and at 2000 feet coming directly towards you. North is 360. For aspect see figure 1.

=== Pronunciation ===
Instead of
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi 1-1, Magic, BRAA, 183 for 10 at 2000, hot"</pre>
it is recommended to omit the "for" and "at", and to use short pauses (here indicated with "..."):
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi one one ... Magic ... BRAA ... one eight zero ... ten ... two thousand ... hot"</pre>

=== Understanding bullseye ===
Bullseye is a fixed point on the map determined pre-mission. All allied aircraft can relate to this point. When receiving a bullseye call, simply use the BRA format with bullseye as starting point. Bullseye in DCS is represented with the following symbols
[[File:bullseye.png|thumb|frame|center|1000x|800px|Left:Bullseye representation in DCS World - Right: Bullseye details]]

== Human GCI/AWACS ==
In DCS World, players can take the role of GCI/AWACS on multiplayer servers to assist your fellow pilots and friends. In the following sections we’ll go over the basics of airspace management, threat assessment, callsigns, brevity and some useful tools.

Before you begin as a GCI/AWACS controller on a server go over this short checklist:
* Pick a suitable callsign

* Check and confirm the radio frequencies used for GCI/AWACS, general communications and air traffic control
* Tune in the correct frequencies on SRS
* Be in the correct server slot (if necessary)
* Have your tools set up and running
* Announce GCI/AWACS will be available over COMMS and CHAT. State the correct frequency and callsign
<pre style="background-color: #ccc;font-family: 'Lucida Console'">all flights on frequency be advised <callsign> will be available on <frequency> for GCI/AWACS</pre>
* If you are on the Hoggit Discord and are registering as a GAW GCI controller, the appropriate command on discord would be "!gci sunrise GAW <callsign, frequency, any other remarks>" command, use "!gci midnight" when you're finished with your session.

=== Airspace management ===
As a controller your goal is to manage both friendly and hostile airspace. You’ll want to direct your allied flights to intercept enemy threats while at the same time making sure your friendly airspace stays protected.

Divide the airspace you’ll be controlling into two sectors.
# a friendly sector
# a hostile sector

Divide sector 1, your friendly sector, into subsectors based on strategic locations like airfields or a FARPs.

Next, you can assign your available CAP flights to the subsectors you created, and have them patrol or set up orbit. This way you can ensure that
* your allied flights are in proximity to allied aircraft and able to support
* your allied aircraft are not spread out or alone in hostile airspace
* your allied aircraft are in range of a tanker or airfield
* your friendly sector is protected

=== Threat assessment ===
With your airspace divided into sectors and your CAP flights on station you can start intercepting enemy threats. There are 2 major things you want to pay close attention to at all times.
* Where are your allied aircraft in relation to your sectors
* Where are the enemy aircraft in relation to your sectors

Before making a decision to direct your allied flights to intercept, you want to assess the threat
# '''Distance''': what is the distance between the threat and the nearby sector or allied aircraft
# '''Number''': how many enemy aircraft make up the threat
# '''Type''': which type is the enemy threat
# ('''State'''): have they been engaged prior and thus used counter measures and/or weapons

When you have gathered this info you can make a decision to either:
* direct one or more allied aircraft to intercept the threat
* direct one or more aircraft away from the threat to nearby SAM cover
* direct one or more allied aircraft to support engaged allied aircraft

In case you are unsure and need extra information before making a decision, contact your allied flights and ask for a fuel and/or weapons state.

When directing your allied flights to intercept, try to keep them in proximity of other allied flights, so you have enough time to send in support if needed. Do not direct your allied flights into enemy airspace and SAM range without support.

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

=== Callsigns and radio communication ===
When acting as GCI/AWACS controller you want to make sure you have a callsign which
* is clear
* is easy to pronounce
* does not cause confusion
* is not ridiculous

Commonly used callsigns for GCI/AWACS are
* Overlord
* Magic
* Showtime
* Darkstar
* Goliath
* Wizard
* Griffin
* Bigfoot

As GCI/AWACS controller you’ll have to relay a lot of information in a clear, concise and easy to understand manner, usually in a short amount of time. It is important to have a good microphone set up, to speak loud and clear, articulate, not to speak too quickly and use the NATO phonetic alphabet to avoid confusion. We’ll discuss some examples below.

==== Responding to flights checking in ====
When allied flights switch to general comms or designated AWACS comms after take off, they’ll most likely check in on the frequency and let you know who they are and what their intentions are.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F-18, 10 miles North of Anapa, checking in for CAP”</pre>

In the above example a player lets you know who they are, where they are and what their intentions are. You can respond to acknowledge (and task them if desired).
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Radar Contact, Alpha Check, Bullseye 123/45.”</pre>
"Alpha Check Bullseye" is the bearing from the bullseye TO the fighter, and verifies they understand/have the correct bullseye reference point.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima Charlie, standby for tasking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima, Charlie, fly heading 100/20, anchor at Krymsk”</pre>

==== Directing allied aircraft to intercept ====
When directing aircraft to intercept you want to be clear and concise. Start with who you are talking to, who you are and provide a BRA(A) call (and optional additional information). It is important to pronounce heading as single digits. For example ‘100’ would be ‘one, zero, zero.’

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/40, 15 thousand, flank north west, hostile.”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/60, 500 feet, hot, hostile, 2 contacts, fulcrum.”</pre>

==== Responding to a Bogey Dope request ====
When a player asks for a Bogey Dope, they are asking for the nearest hostile. Locate the aircraft who made the request, and provide them a BRA to the nearest hostile.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA, 257/15, 10 thousand, drag east”</pre>

When there are no hostile aircraft on scope
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Clean”</pre>

==== Responding to a DECLARE request ====
When you receive a DECLARE request, you are asked to identify friend or foe of a locked target.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, Bullseye 204/8, 12 thousand, DECLARE.”</pre>
or use BRAA (not technically correct, but fine here)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, BRAA 090/15, 12 thousand, DECLARE.”</pre>
Response:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Group, Bullseye 204/8, 12 thousand, hostile, single contact, flanker”</pre>
(fill-ins "single contact" and "flanker" are optional)

==== Miscellaneous ====
Sometimes you will need to ask for additional information, or provide additional information.

Return to base (RTB)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, winchester RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 010/35”</pre>

Ask for fuel state
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, state fuel”</pre>

Ask for weapons state:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, state weapons”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, 4/1/2 plus”</pre>
Note: Number of ARH, SARH, and IR-seeking missiles, and plus for Guns.

Inform aircraft to wait for instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, standby”</pre>

Ignore last transmitted message/instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, disregard last”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA 070/5, ... disregard, BRA 090/5, 7000, hot”</pre>

Identify unknown transmitting aircraft
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, request Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Last transmitting aircraft, state callsign”</pre>

Inform aircraft about incoming missiles or missile launches (unrealistic, generally only possible with F10 map)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, SAM, bearing 090”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, Missile, bearing 090”</pre>

=== Tools ===
==== SRS AWACS mode (eam) ====
The standard SRS radio overlay only displays up to 3 radios and 1 intercom. The AWACS overlay provides up to 10 radios, which you can manually tune and 1 intercom.

You can use SRS without running DCS World, by using the external AWACS mode (EAM). provide your EAM username and the EAM coalition password. The coalition password is provided by the server admin, or in the server briefing. This is not always available.

==== F10 map, icons and the ruler tool ====
The ingame F10 map is where you’ll spend most of your time doing GCI/AWACS. It provides several functions which you can toggle on or off by personal preference
* health bars
* SAM and AAA detection range indicators
* SAM and AAA engagement range indicators
* grid
* labels indicating type and name
* ruler tool

The most important function you’ll use is the ruler tool. It allows you to create a line from point A to point B and provides you with the length in nautical miles and the heading. When intercepting enemy aircraft you can use the ruler tool to draw a line from your allied aircraft A to the hostile aircraft B and read the distance in nautical miles and the heading indicated on the top bar. When you click on the enemy aircraft icon, you can read its altitude, speed in knots, heading and type on the bottom left.

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

==== LotATC ====
LotATC is an optional program one can use to facilitate GCI simulation. The program is fairly easy to use is highly customizable. LotATC provides many features to aid a GCI.

* The creation of persistant BRAAs
* IFF features
* An ATC mode
* The ability to call BRAAs from the bullseye
* A scale which can be used to respond to Picture calls
* The ability to draw on the map

For more information on LotATC and how to use the software see [https://wiki.hoggitworld.com/view/LotATC LotATC]

== Coordinating with human GCI/AWACS ==
A couple guidelines from the players point of view

Inform AWACS when you tune in or tune out of the AWACS frequency.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F18, 10nm North of Anapa, checking in for CAP”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single Mirage 2000, checking in for CAP”</pre>

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, bingo fuel, RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 100/35”</pre>

Do not clutter the AWACS frequency with off-topic chatter, use the correct frequencies as stated in mission briefing.

Do not read back a BRA call. Simply acknowledge you received and understood the message by saying your callsign. If you did not understand the transmission, ask AWACS to repeat.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA 100/45, 20 thousand, flank north west”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Uzi 1-1”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, say again”</pre>

Getting started with GCI/AWACS

2022-09-03T18:37:18Z

Marlan: /* Responding to flights checking in */

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

'''''Disclaimer''''' 
''This guide is compiled using information available to the public and information based on personal experience in DCS World. This guide does not in any way, shape or form represent real life GCI/AWACS operations or techniques nor is it based on real life experience.''

== What is GCI/AWACS ==
[[File:e3_awacs.jpg|thumb|frame|right|Boeing E-3 Sentry]]
GCI stands for '''G'''round-'''C'''ontrolled '''I'''nterception, an air defence tactic which developed during World War I. One or more radar stations or other observational stations are linked to a command communications centre which guides interceptor aircraft to airborne targets.

Today, GCI has mostly been replaced by Airborne Early Warning and Control (AEW&C) aircraft or more commonly referred to as AWACS ('''A'''irborne '''W'''arning '''A'''nd '''C'''ontrol '''S'''ystem). While AEW&C is expensive and vulnerable in comparison to GCI systems, it has a mobility advantage. In reality a combination of both systems is often used.

AWACS aircraft are generally speaking big, modified planes with a long-range radar mounted on top. The main radar antenna is mounted on a turntable housed in a circular rotodome, which is 9m (30 feet) in diameter, elliptical in cross-section and 1.8m deep at its centre. The radar system can detect, track and identify low-flying aircraft at approximately 370 km (200 nautical miles) and high-level aircraft at much greater distances.

== AI AWACS in DCS World ==
In DCS World the NATO AWACS comes in the form of the Boeing E-3 Sentry and the Russian equivalent is the Beriev A-50. The player can contact the allied AWACS via the ingame comms menu on the specified frequency in the mission briefing.

=== Comms menu ===
;Vector to bullseye
: The AWACS will provide the player with a bearing and range to bullseye

;Vector to home plate
: The AWACS will provide the player with a bearing and range from bullseye to their home airfield

;Vector to tanker
: The AWACS will provide the player with a bearing and range from bullseye to the tanker

;Request BOGEY DOPE
: The AWACS will provide the player a BRAA call to the closest airborne threat.

;Request PICTURE
: The AWACS will provide the player with BRA calls for each group from bullseye

;DECLARE
: The AWACS will identify friend or foe of a radar locked target

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

=== Understanding BRAA calls ===
[[File:aspect.jpg|thumb|frame|right|500x|400px|Figure 1]]
BRAA stands for '''B'''earing '''R'''ange '''A'''ltitude '''A'''spect from your current location.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">BRA, 183, 10, 2000, hot</pre> would mean the target is located at 183 degrees, 10 nautical miles away, and at 2000 feet coming directly towards you. North is 360. For aspect see figure 1.

=== Pronunciation ===
Instead of
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi 1-1, Magic, BRA, 183 for 10 at 2000, hot"</pre>
it is recommended to omit the "for" and "at", and to use short pauses (here indicated with "..."):
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi one one ... Magic ... BRA ... one eight zero ... ten ... two thousand ... hot"</pre>

=== Understanding bullseye ===
Bullseye is a fixed point on the map determined pre-mission. All allied aircraft can relate to this point. When receiving a bullseye call, simply use the BRA format with bullseye as starting point. Bullseye in DCS is represented with the following symbols
[[File:bullseye.png|thumb|frame|center|1000x|800px|Left:Bullseye representation in DCS World - Right: Bullseye details]]

== Human GCI/AWACS ==
In DCS World, players can take the role of GCI/AWACS on multiplayer servers to assist your fellow pilots and friends. In the following sections we’ll go over the basics of airspace management, threat assessment, callsigns, brevity and some useful tools.

Before you begin as a GCI/AWACS controller on a server go over this short checklist:
* Pick a suitable callsign

* Check and confirm the radio frequencies used for GCI/AWACS, general communications and air traffic control
* Tune in the correct frequencies on SRS
* Be in the correct server slot (if necessary)
* Have your tools set up and running
* Announce GCI/AWACS will be available over COMMS and CHAT. State the correct frequency and callsign
<pre style="background-color: #ccc;font-family: 'Lucida Console'">all flights on frequency be advised <callsign> will be available on <frequency> for GCI/AWACS</pre>
* If you are on the Hoggit Discord and are registering as a GAW GCI controller, the appropriate command on discord would be "!gci sunrise GAW <callsign, frequency, any other remarks>" command, use "!gci midnight" when you're finished with your session.

=== Airspace management ===
As a controller your goal is to manage both friendly and hostile airspace. You’ll want to direct your allied flights to intercept enemy threats while at the same time making sure your friendly airspace stays protected.

Divide the airspace you’ll be controlling into two sectors.
# a friendly sector
# a hostile sector

Divide sector 1, your friendly sector, into subsectors based on strategic locations like airfields or a FARPs.

Next, you can assign your available CAP flights to the subsectors you created, and have them patrol or set up orbit. This way you can ensure that
* your allied flights are in proximity to allied aircraft and able to support
* your allied aircraft are not spread out or alone in hostile airspace
* your allied aircraft are in range of a tanker or airfield
* your friendly sector is protected

=== Threat assessment ===
With your airspace divided into sectors and your CAP flights on station you can start intercepting enemy threats. There are 2 major things you want to pay close attention to at all times.
* Where are your allied aircraft in relation to your sectors
* Where are the enemy aircraft in relation to your sectors

Before making a decision to direct your allied flights to intercept, you want to assess the threat
# '''Distance''': what is the distance between the threat and the nearby sector or allied aircraft
# '''Number''': how many enemy aircraft make up the threat
# '''Type''': which type is the enemy threat
# ('''State'''): have they been engaged prior and thus used counter measures and/or weapons

When you have gathered this info you can make a decision to either:
* direct one or more allied aircraft to intercept the threat
* direct one or more aircraft away from the threat to nearby SAM cover
* direct one or more allied aircraft to support engaged allied aircraft

In case you are unsure and need extra information before making a decision, contact your allied flights and ask for a fuel and/or weapons state.

When directing your allied flights to intercept, try to keep them in proximity of other allied flights, so you have enough time to send in support if needed. Do not direct your allied flights into enemy airspace and SAM range without support.

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

=== Callsigns and radio communication ===
When acting as GCI/AWACS controller you want to make sure you have a callsign which
* is clear
* is easy to pronounce
* does not cause confusion
* is not ridiculous

Commonly used callsigns for GCI/AWACS are
* Overlord
* Magic
* Showtime
* Darkstar
* Goliath
* Wizard
* Griffin
* Bigfoot

As GCI/AWACS controller you’ll have to relay a lot of information in a clear, concise and easy to understand manner, usually in a short amount of time. It is important to have a good microphone set up, to speak loud and clear, articulate, not to speak too quickly and use the NATO phonetic alphabet to avoid confusion. We’ll discuss some examples below.

==== Responding to flights checking in ====
When allied flights switch to general comms or designated AWACS comms after take off, they’ll most likely check in on the frequency and let you know who they are and what their intentions are.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F-18, 10 miles North of Anapa, checking in for CAP”</pre>

In the above example a player lets you know who they are, where they are and what their intentions are. You can respond to acknowledge (and task them if desired).
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Radar Contact, Alpha Check, Bullseye 123/45.”</pre>
"Alpha Check Bullseye" is the bearing from the bullseye TO the fighter, and verifies they understand/have the correct bullseye reference point.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima Charlie, standby for tasking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima, Charlie, fly heading 100/20, anchor at Krymsk”</pre>

==== Directing allied aircraft to intercept ====
When directing aircraft to intercept you want to be clear and concise. Start with who you are talking to, who you are and provide a BRA(A) call (and optional additional information). It is important to pronounce heading as single digits. For example ‘100’ would be ‘one, zero, zero.’

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/40, 15 thousand, flank north west, hostile.”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/60, 500 feet, hot, hostile, 2 contacts, fulcrum.”</pre>

==== Responding to a Bogey Dope request ====
When a player asks for a Bogey Dope, they are asking for the nearest hostile. Locate the aircraft who made the request, and provide them a BRA to the nearest hostile.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA, 257/15, 10 thousand, drag east”</pre>

When there are no hostile aircraft on scope
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Clean”</pre>

==== Responding to a DECLARE request ====
When you receive a DECLARE request, you are asked to identify friend or foe of a locked target.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, Bullseye 204/8, 12 thousand, DECLARE.”</pre>
or use BRAA (not technically correct, but fine here)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, BRAA 090/15, 12 thousand, DECLARE.”</pre>
Response:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Group, Bullseye 204/8, 12 thousand, hostile, single contact, flanker”</pre>
(fill-ins "single contact" and "flanker" are optional)

==== Miscellaneous ====
Sometimes you will need to ask for additional information, or provide additional information.

Return to base (RTB)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, winchester RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 010/35”</pre>

Ask for fuel state
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, state fuel”</pre>

Ask for weapons state:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, state weapons”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, 4/1/2 plus”</pre>
Note: Number of ARH, SARH, and IR-seeking missiles, and plus for Guns.

Inform aircraft to wait for instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, standby”</pre>

Ignore last transmitted message/instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, disregard last”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA 070/5, ... disregard, BRA 090/5, 7000, hot”</pre>

Identify unknown transmitting aircraft
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, request Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Last transmitting aircraft, state callsign”</pre>

Inform aircraft about incoming missiles or missile launches (unrealistic, generally only possible with F10 map)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, SAM, bearing 090”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, Missile, bearing 090”</pre>

=== Tools ===
==== SRS AWACS mode (eam) ====
The standard SRS radio overlay only displays up to 3 radios and 1 intercom. The AWACS overlay provides up to 10 radios, which you can manually tune and 1 intercom.

You can use SRS without running DCS World, by using the external AWACS mode (EAM). provide your EAM username and the EAM coalition password. The coalition password is provided by the server admin, or in the server briefing. This is not always available.

==== F10 map, icons and the ruler tool ====
The ingame F10 map is where you’ll spend most of your time doing GCI/AWACS. It provides several functions which you can toggle on or off by personal preference
* health bars
* SAM and AAA detection range indicators
* SAM and AAA engagement range indicators
* grid
* labels indicating type and name
* ruler tool

The most important function you’ll use is the ruler tool. It allows you to create a line from point A to point B and provides you with the length in nautical miles and the heading. When intercepting enemy aircraft you can use the ruler tool to draw a line from your allied aircraft A to the hostile aircraft B and read the distance in nautical miles and the heading indicated on the top bar. When you click on the enemy aircraft icon, you can read its altitude, speed in knots, heading and type on the bottom left.

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

==== LotATC ====
LotATC is an optional program one can use to facilitate GCI simulation. The program is fairly easy to use is highly customizable. LotATC provides many features to aid a GCI.

* The creation of persistant BRAAs
* IFF features
* An ATC mode
* The ability to call BRAAs from the bullseye
* A scale which can be used to respond to Picture calls
* The ability to draw on the map

For more information on LotATC and how to use the software see [https://wiki.hoggitworld.com/view/LotATC LotATC]

== Coordinating with human GCI/AWACS ==
A couple guidelines from the players point of view

Inform AWACS when you tune in or tune out of the AWACS frequency.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F18, 10nm North of Anapa, checking in for CAP”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single Mirage 2000, checking in for CAP”</pre>

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, bingo fuel, RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 100/35”</pre>

Do not clutter the AWACS frequency with off-topic chatter, use the correct frequencies as stated in mission briefing.

Do not read back a BRA call. Simply acknowledge you received and understood the message by saying your callsign. If you did not understand the transmission, ask AWACS to repeat.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA 100/45, 20 thousand, flank north west”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Uzi 1-1”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, say again”</pre>

Getting started with GCI/AWACS

2022-09-03T18:34:38Z

Marlan: /* Directing allied aircraft to intercept */

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

'''''Disclaimer''''' 
''This guide is compiled using information available to the public and information based on personal experience in DCS World. This guide does not in any way, shape or form represent real life GCI/AWACS operations or techniques nor is it based on real life experience.''

== What is GCI/AWACS ==
[[File:e3_awacs.jpg|thumb|frame|right|Boeing E-3 Sentry]]
GCI stands for '''G'''round-'''C'''ontrolled '''I'''nterception, an air defence tactic which developed during World War I. One or more radar stations or other observational stations are linked to a command communications centre which guides interceptor aircraft to airborne targets.

Today, GCI has mostly been replaced by Airborne Early Warning and Control (AEW&C) aircraft or more commonly referred to as AWACS ('''A'''irborne '''W'''arning '''A'''nd '''C'''ontrol '''S'''ystem). While AEW&C is expensive and vulnerable in comparison to GCI systems, it has a mobility advantage. In reality a combination of both systems is often used.

AWACS aircraft are generally speaking big, modified planes with a long-range radar mounted on top. The main radar antenna is mounted on a turntable housed in a circular rotodome, which is 9m (30 feet) in diameter, elliptical in cross-section and 1.8m deep at its centre. The radar system can detect, track and identify low-flying aircraft at approximately 370 km (200 nautical miles) and high-level aircraft at much greater distances.

== AI AWACS in DCS World ==
In DCS World the NATO AWACS comes in the form of the Boeing E-3 Sentry and the Russian equivalent is the Beriev A-50. The player can contact the allied AWACS via the ingame comms menu on the specified frequency in the mission briefing.

=== Comms menu ===
;Vector to bullseye
: The AWACS will provide the player with a bearing and range to bullseye

;Vector to home plate
: The AWACS will provide the player with a bearing and range from bullseye to their home airfield

;Vector to tanker
: The AWACS will provide the player with a bearing and range from bullseye to the tanker

;Request BOGEY DOPE
: The AWACS will provide the player a BRAA call to the closest airborne threat.

;Request PICTURE
: The AWACS will provide the player with BRA calls for each group from bullseye

;DECLARE
: The AWACS will identify friend or foe of a radar locked target

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

=== Understanding BRAA calls ===
[[File:aspect.jpg|thumb|frame|right|500x|400px|Figure 1]]
BRAA stands for '''B'''earing '''R'''ange '''A'''ltitude '''A'''spect from your current location.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">BRA, 183, 10, 2000, hot</pre> would mean the target is located at 183 degrees, 10 nautical miles away, and at 2000 feet coming directly towards you. North is 360. For aspect see figure 1.

=== Pronunciation ===
Instead of
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi 1-1, Magic, BRA, 183 for 10 at 2000, hot"</pre>
it is recommended to omit the "for" and "at", and to use short pauses (here indicated with "..."):
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi one one ... Magic ... BRA ... one eight zero ... ten ... two thousand ... hot"</pre>

=== Understanding bullseye ===
Bullseye is a fixed point on the map determined pre-mission. All allied aircraft can relate to this point. When receiving a bullseye call, simply use the BRA format with bullseye as starting point. Bullseye in DCS is represented with the following symbols
[[File:bullseye.png|thumb|frame|center|1000x|800px|Left:Bullseye representation in DCS World - Right: Bullseye details]]

== Human GCI/AWACS ==
In DCS World, players can take the role of GCI/AWACS on multiplayer servers to assist your fellow pilots and friends. In the following sections we’ll go over the basics of airspace management, threat assessment, callsigns, brevity and some useful tools.

Before you begin as a GCI/AWACS controller on a server go over this short checklist:
* Pick a suitable callsign

* Check and confirm the radio frequencies used for GCI/AWACS, general communications and air traffic control
* Tune in the correct frequencies on SRS
* Be in the correct server slot (if necessary)
* Have your tools set up and running
* Announce GCI/AWACS will be available over COMMS and CHAT. State the correct frequency and callsign
<pre style="background-color: #ccc;font-family: 'Lucida Console'">all flights on frequency be advised <callsign> will be available on <frequency> for GCI/AWACS</pre>
* If you are on the Hoggit Discord and are registering as a GAW GCI controller, the appropriate command on discord would be "!gci sunrise GAW <callsign, frequency, any other remarks>" command, use "!gci midnight" when you're finished with your session.

=== Airspace management ===
As a controller your goal is to manage both friendly and hostile airspace. You’ll want to direct your allied flights to intercept enemy threats while at the same time making sure your friendly airspace stays protected.

Divide the airspace you’ll be controlling into two sectors.
# a friendly sector
# a hostile sector

Divide sector 1, your friendly sector, into subsectors based on strategic locations like airfields or a FARPs.

Next, you can assign your available CAP flights to the subsectors you created, and have them patrol or set up orbit. This way you can ensure that
* your allied flights are in proximity to allied aircraft and able to support
* your allied aircraft are not spread out or alone in hostile airspace
* your allied aircraft are in range of a tanker or airfield
* your friendly sector is protected

=== Threat assessment ===
With your airspace divided into sectors and your CAP flights on station you can start intercepting enemy threats. There are 2 major things you want to pay close attention to at all times.
* Where are your allied aircraft in relation to your sectors
* Where are the enemy aircraft in relation to your sectors

Before making a decision to direct your allied flights to intercept, you want to assess the threat
# '''Distance''': what is the distance between the threat and the nearby sector or allied aircraft
# '''Number''': how many enemy aircraft make up the threat
# '''Type''': which type is the enemy threat
# ('''State'''): have they been engaged prior and thus used counter measures and/or weapons

When you have gathered this info you can make a decision to either:
* direct one or more allied aircraft to intercept the threat
* direct one or more aircraft away from the threat to nearby SAM cover
* direct one or more allied aircraft to support engaged allied aircraft

In case you are unsure and need extra information before making a decision, contact your allied flights and ask for a fuel and/or weapons state.

When directing your allied flights to intercept, try to keep them in proximity of other allied flights, so you have enough time to send in support if needed. Do not direct your allied flights into enemy airspace and SAM range without support.

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

=== Callsigns and radio communication ===
When acting as GCI/AWACS controller you want to make sure you have a callsign which
* is clear
* is easy to pronounce
* does not cause confusion
* is not ridiculous

Commonly used callsigns for GCI/AWACS are
* Overlord
* Magic
* Showtime
* Darkstar
* Goliath
* Wizard
* Griffin
* Bigfoot

As GCI/AWACS controller you’ll have to relay a lot of information in a clear, concise and easy to understand manner, usually in a short amount of time. It is important to have a good microphone set up, to speak loud and clear, articulate, not to speak too quickly and use the NATO phonetic alphabet to avoid confusion. We’ll discuss some examples below.

==== Responding to flights checking in ====
When allied flights switch to general comms or designated AWACS comms after take off, they’ll most likely check in on the frequency and let you know who they are and what their intentions are.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single flight F-18, 10 miles North of Anapa, checking in for CAP”</pre>

In the above example a player lets you know who they are, where they are and what their intentions are. You can respond to acknowledge (and task them if desired).

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima Charlie, standby for tasking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima, Charlie, fly heading 100 for 20, anchor at Krymsk”</pre>

==== Directing allied aircraft to intercept ====
When directing aircraft to intercept you want to be clear and concise. Start with who you are talking to, who you are and provide a BRA(A) call (and optional additional information). It is important to pronounce heading as single digits. For example ‘100’ would be ‘one, zero, zero.’

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/40, 15 thousand, flank north west, hostile.”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, TARGET, Group, BRAA, 100/60, 500 feet, hot, hostile, 2 contacts, fulcrum.”</pre>

==== Responding to a Bogey Dope request ====
When a player asks for a Bogey Dope, they are asking for the nearest hostile. Locate the aircraft who made the request, and provide them a BRA to the nearest hostile.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA, 257/15, 10 thousand, drag east”</pre>

When there are no hostile aircraft on scope
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Clean”</pre>

==== Responding to a DECLARE request ====
When you receive a DECLARE request, you are asked to identify friend or foe of a locked target.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, Bullseye 204/8, 12 thousand, DECLARE.”</pre>
or use BRAA (not technically correct, but fine here)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, BRAA 090/15, 12 thousand, DECLARE.”</pre>
Response:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Group, Bullseye 204/8, 12 thousand, hostile, single contact, flanker”</pre>
(fill-ins "single contact" and "flanker" are optional)

==== Miscellaneous ====
Sometimes you will need to ask for additional information, or provide additional information.

Return to base (RTB)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, winchester RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 010/35”</pre>

Ask for fuel state
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, state fuel”</pre>

Ask for weapons state:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, state weapons”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, 4/1/2 plus”</pre>
Note: Number of ARH, SARH, and IR-seeking missiles, and plus for Guns.

Inform aircraft to wait for instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, standby”</pre>

Ignore last transmitted message/instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, disregard last”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA 070/5, ... disregard, BRA 090/5, 7000, hot”</pre>

Identify unknown transmitting aircraft
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, request Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Last transmitting aircraft, state callsign”</pre>

Inform aircraft about incoming missiles or missile launches (unrealistic, generally only possible with F10 map)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, SAM, bearing 090”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, Missile, bearing 090”</pre>

=== Tools ===
==== SRS AWACS mode (eam) ====
The standard SRS radio overlay only displays up to 3 radios and 1 intercom. The AWACS overlay provides up to 10 radios, which you can manually tune and 1 intercom.

You can use SRS without running DCS World, by using the external AWACS mode (EAM). provide your EAM username and the EAM coalition password. The coalition password is provided by the server admin, or in the server briefing. This is not always available.

==== F10 map, icons and the ruler tool ====
The ingame F10 map is where you’ll spend most of your time doing GCI/AWACS. It provides several functions which you can toggle on or off by personal preference
* health bars
* SAM and AAA detection range indicators
* SAM and AAA engagement range indicators
* grid
* labels indicating type and name
* ruler tool

The most important function you’ll use is the ruler tool. It allows you to create a line from point A to point B and provides you with the length in nautical miles and the heading. When intercepting enemy aircraft you can use the ruler tool to draw a line from your allied aircraft A to the hostile aircraft B and read the distance in nautical miles and the heading indicated on the top bar. When you click on the enemy aircraft icon, you can read its altitude, speed in knots, heading and type on the bottom left.

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

==== LotATC ====
LotATC is an optional program one can use to facilitate GCI simulation. The program is fairly easy to use is highly customizable. LotATC provides many features to aid a GCI.

* The creation of persistant BRAAs
* IFF features
* An ATC mode
* The ability to call BRAAs from the bullseye
* A scale which can be used to respond to Picture calls
* The ability to draw on the map

For more information on LotATC and how to use the software see [https://wiki.hoggitworld.com/view/LotATC LotATC]

== Coordinating with human GCI/AWACS ==
A couple guidelines from the players point of view

Inform AWACS when you tune in or tune out of the AWACS frequency.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F18, 10nm North of Anapa, checking in for CAP”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single Mirage 2000, checking in for CAP”</pre>

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, bingo fuel, RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 100/35”</pre>

Do not clutter the AWACS frequency with off-topic chatter, use the correct frequencies as stated in mission briefing.

Do not read back a BRA call. Simply acknowledge you received and understood the message by saying your callsign. If you did not understand the transmission, ask AWACS to repeat.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA 100/45, 20 thousand, flank north west”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Uzi 1-1”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, say again”</pre>

Getting started with GCI/AWACS

2022-09-03T18:33:19Z

Marlan: /* Responding to a Bogey Dope request */

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

'''''Disclaimer''''' 
''This guide is compiled using information available to the public and information based on personal experience in DCS World. This guide does not in any way, shape or form represent real life GCI/AWACS operations or techniques nor is it based on real life experience.''

== What is GCI/AWACS ==
[[File:e3_awacs.jpg|thumb|frame|right|Boeing E-3 Sentry]]
GCI stands for '''G'''round-'''C'''ontrolled '''I'''nterception, an air defence tactic which developed during World War I. One or more radar stations or other observational stations are linked to a command communications centre which guides interceptor aircraft to airborne targets.

Today, GCI has mostly been replaced by Airborne Early Warning and Control (AEW&C) aircraft or more commonly referred to as AWACS ('''A'''irborne '''W'''arning '''A'''nd '''C'''ontrol '''S'''ystem). While AEW&C is expensive and vulnerable in comparison to GCI systems, it has a mobility advantage. In reality a combination of both systems is often used.

AWACS aircraft are generally speaking big, modified planes with a long-range radar mounted on top. The main radar antenna is mounted on a turntable housed in a circular rotodome, which is 9m (30 feet) in diameter, elliptical in cross-section and 1.8m deep at its centre. The radar system can detect, track and identify low-flying aircraft at approximately 370 km (200 nautical miles) and high-level aircraft at much greater distances.

== AI AWACS in DCS World ==
In DCS World the NATO AWACS comes in the form of the Boeing E-3 Sentry and the Russian equivalent is the Beriev A-50. The player can contact the allied AWACS via the ingame comms menu on the specified frequency in the mission briefing.

=== Comms menu ===
;Vector to bullseye
: The AWACS will provide the player with a bearing and range to bullseye

;Vector to home plate
: The AWACS will provide the player with a bearing and range from bullseye to their home airfield

;Vector to tanker
: The AWACS will provide the player with a bearing and range from bullseye to the tanker

;Request BOGEY DOPE
: The AWACS will provide the player a BRAA call to the closest airborne threat.

;Request PICTURE
: The AWACS will provide the player with BRA calls for each group from bullseye

;DECLARE
: The AWACS will identify friend or foe of a radar locked target

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

=== Understanding BRAA calls ===
[[File:aspect.jpg|thumb|frame|right|500x|400px|Figure 1]]
BRAA stands for '''B'''earing '''R'''ange '''A'''ltitude '''A'''spect from your current location.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">BRA, 183, 10, 2000, hot</pre> would mean the target is located at 183 degrees, 10 nautical miles away, and at 2000 feet coming directly towards you. North is 360. For aspect see figure 1.

=== Pronunciation ===
Instead of
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi 1-1, Magic, BRA, 183 for 10 at 2000, hot"</pre>
it is recommended to omit the "for" and "at", and to use short pauses (here indicated with "..."):
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi one one ... Magic ... BRA ... one eight zero ... ten ... two thousand ... hot"</pre>

=== Understanding bullseye ===
Bullseye is a fixed point on the map determined pre-mission. All allied aircraft can relate to this point. When receiving a bullseye call, simply use the BRA format with bullseye as starting point. Bullseye in DCS is represented with the following symbols
[[File:bullseye.png|thumb|frame|center|1000x|800px|Left:Bullseye representation in DCS World - Right: Bullseye details]]

== Human GCI/AWACS ==
In DCS World, players can take the role of GCI/AWACS on multiplayer servers to assist your fellow pilots and friends. In the following sections we’ll go over the basics of airspace management, threat assessment, callsigns, brevity and some useful tools.

Before you begin as a GCI/AWACS controller on a server go over this short checklist:
* Pick a suitable callsign

* Check and confirm the radio frequencies used for GCI/AWACS, general communications and air traffic control
* Tune in the correct frequencies on SRS
* Be in the correct server slot (if necessary)
* Have your tools set up and running
* Announce GCI/AWACS will be available over COMMS and CHAT. State the correct frequency and callsign
<pre style="background-color: #ccc;font-family: 'Lucida Console'">all flights on frequency be advised <callsign> will be available on <frequency> for GCI/AWACS</pre>
* If you are on the Hoggit Discord and are registering as a GAW GCI controller, the appropriate command on discord would be "!gci sunrise GAW <callsign, frequency, any other remarks>" command, use "!gci midnight" when you're finished with your session.

=== Airspace management ===
As a controller your goal is to manage both friendly and hostile airspace. You’ll want to direct your allied flights to intercept enemy threats while at the same time making sure your friendly airspace stays protected.

Divide the airspace you’ll be controlling into two sectors.
# a friendly sector
# a hostile sector

Divide sector 1, your friendly sector, into subsectors based on strategic locations like airfields or a FARPs.

Next, you can assign your available CAP flights to the subsectors you created, and have them patrol or set up orbit. This way you can ensure that
* your allied flights are in proximity to allied aircraft and able to support
* your allied aircraft are not spread out or alone in hostile airspace
* your allied aircraft are in range of a tanker or airfield
* your friendly sector is protected

=== Threat assessment ===
With your airspace divided into sectors and your CAP flights on station you can start intercepting enemy threats. There are 2 major things you want to pay close attention to at all times.
* Where are your allied aircraft in relation to your sectors
* Where are the enemy aircraft in relation to your sectors

Before making a decision to direct your allied flights to intercept, you want to assess the threat
# '''Distance''': what is the distance between the threat and the nearby sector or allied aircraft
# '''Number''': how many enemy aircraft make up the threat
# '''Type''': which type is the enemy threat
# ('''State'''): have they been engaged prior and thus used counter measures and/or weapons

When you have gathered this info you can make a decision to either:
* direct one or more allied aircraft to intercept the threat
* direct one or more aircraft away from the threat to nearby SAM cover
* direct one or more allied aircraft to support engaged allied aircraft

In case you are unsure and need extra information before making a decision, contact your allied flights and ask for a fuel and/or weapons state.

When directing your allied flights to intercept, try to keep them in proximity of other allied flights, so you have enough time to send in support if needed. Do not direct your allied flights into enemy airspace and SAM range without support.

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

=== Callsigns and radio communication ===
When acting as GCI/AWACS controller you want to make sure you have a callsign which
* is clear
* is easy to pronounce
* does not cause confusion
* is not ridiculous

Commonly used callsigns for GCI/AWACS are
* Overlord
* Magic
* Showtime
* Darkstar
* Goliath
* Wizard
* Griffin
* Bigfoot

As GCI/AWACS controller you’ll have to relay a lot of information in a clear, concise and easy to understand manner, usually in a short amount of time. It is important to have a good microphone set up, to speak loud and clear, articulate, not to speak too quickly and use the NATO phonetic alphabet to avoid confusion. We’ll discuss some examples below.

==== Responding to flights checking in ====
When allied flights switch to general comms or designated AWACS comms after take off, they’ll most likely check in on the frequency and let you know who they are and what their intentions are.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single flight F-18, 10 miles North of Anapa, checking in for CAP”</pre>

In the above example a player lets you know who they are, where they are and what their intentions are. You can respond to acknowledge (and task them if desired).

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima Charlie, standby for tasking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima, Charlie, fly heading 100 for 20, anchor at Krymsk”</pre>

==== Directing allied aircraft to intercept ====
When directing aircraft to intercept you want to be clear and concise. Start with who you are talking to, who you are and provide a BRA(A) call (and optional additional information). It is important to pronounce heading as single digits. For example ‘100’ would be ‘one, zero, zero.’

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA, 100, 40, 15 000, flanking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA, 100, 60, 500, hot, 2 ship type MiG-29”</pre>

==== Responding to a Bogey Dope request ====
When a player asks for a Bogey Dope, they are asking for the nearest hostile. Locate the aircraft who made the request, and provide them a BRA to the nearest hostile.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA, 257/15, 10 thousand, drag east”</pre>

When there are no hostile aircraft on scope
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Clean”</pre>

==== Responding to a DECLARE request ====
When you receive a DECLARE request, you are asked to identify friend or foe of a locked target.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, Bullseye 204/8, 12 thousand, DECLARE.”</pre>
or use BRAA (not technically correct, but fine here)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, BRAA 090/15, 12 thousand, DECLARE.”</pre>
Response:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Group, Bullseye 204/8, 12 thousand, hostile, single contact, flanker”</pre>
(fill-ins "single contact" and "flanker" are optional)

==== Miscellaneous ====
Sometimes you will need to ask for additional information, or provide additional information.

Return to base (RTB)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, winchester RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 010/35”</pre>

Ask for fuel state
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, state fuel”</pre>

Ask for weapons state:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, state weapons”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, 4/1/2 plus”</pre>
Note: Number of ARH, SARH, and IR-seeking missiles, and plus for Guns.

Inform aircraft to wait for instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, standby”</pre>

Ignore last transmitted message/instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, disregard last”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA 070/5, ... disregard, BRA 090/5, 7000, hot”</pre>

Identify unknown transmitting aircraft
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, request Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Last transmitting aircraft, state callsign”</pre>

Inform aircraft about incoming missiles or missile launches (unrealistic, generally only possible with F10 map)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, SAM, bearing 090”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, Missile, bearing 090”</pre>

=== Tools ===
==== SRS AWACS mode (eam) ====
The standard SRS radio overlay only displays up to 3 radios and 1 intercom. The AWACS overlay provides up to 10 radios, which you can manually tune and 1 intercom.

You can use SRS without running DCS World, by using the external AWACS mode (EAM). provide your EAM username and the EAM coalition password. The coalition password is provided by the server admin, or in the server briefing. This is not always available.

==== F10 map, icons and the ruler tool ====
The ingame F10 map is where you’ll spend most of your time doing GCI/AWACS. It provides several functions which you can toggle on or off by personal preference
* health bars
* SAM and AAA detection range indicators
* SAM and AAA engagement range indicators
* grid
* labels indicating type and name
* ruler tool

The most important function you’ll use is the ruler tool. It allows you to create a line from point A to point B and provides you with the length in nautical miles and the heading. When intercepting enemy aircraft you can use the ruler tool to draw a line from your allied aircraft A to the hostile aircraft B and read the distance in nautical miles and the heading indicated on the top bar. When you click on the enemy aircraft icon, you can read its altitude, speed in knots, heading and type on the bottom left.

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

==== LotATC ====
LotATC is an optional program one can use to facilitate GCI simulation. The program is fairly easy to use is highly customizable. LotATC provides many features to aid a GCI.

* The creation of persistant BRAAs
* IFF features
* An ATC mode
* The ability to call BRAAs from the bullseye
* A scale which can be used to respond to Picture calls
* The ability to draw on the map

For more information on LotATC and how to use the software see [https://wiki.hoggitworld.com/view/LotATC LotATC]

== Coordinating with human GCI/AWACS ==
A couple guidelines from the players point of view

Inform AWACS when you tune in or tune out of the AWACS frequency.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F18, 10nm North of Anapa, checking in for CAP”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single Mirage 2000, checking in for CAP”</pre>

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, bingo fuel, RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 100/35”</pre>

Do not clutter the AWACS frequency with off-topic chatter, use the correct frequencies as stated in mission briefing.

Do not read back a BRA call. Simply acknowledge you received and understood the message by saying your callsign. If you did not understand the transmission, ask AWACS to repeat.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA 100/45, 20 thousand, flank north west”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Uzi 1-1”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, say again”</pre>

Getting started with GCI/AWACS

2022-09-03T18:32:49Z

Marlan: /* Responding to a DECLARE request */

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

'''''Disclaimer''''' 
''This guide is compiled using information available to the public and information based on personal experience in DCS World. This guide does not in any way, shape or form represent real life GCI/AWACS operations or techniques nor is it based on real life experience.''

== What is GCI/AWACS ==
[[File:e3_awacs.jpg|thumb|frame|right|Boeing E-3 Sentry]]
GCI stands for '''G'''round-'''C'''ontrolled '''I'''nterception, an air defence tactic which developed during World War I. One or more radar stations or other observational stations are linked to a command communications centre which guides interceptor aircraft to airborne targets.

Today, GCI has mostly been replaced by Airborne Early Warning and Control (AEW&C) aircraft or more commonly referred to as AWACS ('''A'''irborne '''W'''arning '''A'''nd '''C'''ontrol '''S'''ystem). While AEW&C is expensive and vulnerable in comparison to GCI systems, it has a mobility advantage. In reality a combination of both systems is often used.

AWACS aircraft are generally speaking big, modified planes with a long-range radar mounted on top. The main radar antenna is mounted on a turntable housed in a circular rotodome, which is 9m (30 feet) in diameter, elliptical in cross-section and 1.8m deep at its centre. The radar system can detect, track and identify low-flying aircraft at approximately 370 km (200 nautical miles) and high-level aircraft at much greater distances.

== AI AWACS in DCS World ==
In DCS World the NATO AWACS comes in the form of the Boeing E-3 Sentry and the Russian equivalent is the Beriev A-50. The player can contact the allied AWACS via the ingame comms menu on the specified frequency in the mission briefing.

=== Comms menu ===
;Vector to bullseye
: The AWACS will provide the player with a bearing and range to bullseye

;Vector to home plate
: The AWACS will provide the player with a bearing and range from bullseye to their home airfield

;Vector to tanker
: The AWACS will provide the player with a bearing and range from bullseye to the tanker

;Request BOGEY DOPE
: The AWACS will provide the player a BRAA call to the closest airborne threat.

;Request PICTURE
: The AWACS will provide the player with BRA calls for each group from bullseye

;DECLARE
: The AWACS will identify friend or foe of a radar locked target

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

=== Understanding BRAA calls ===
[[File:aspect.jpg|thumb|frame|right|500x|400px|Figure 1]]
BRAA stands for '''B'''earing '''R'''ange '''A'''ltitude '''A'''spect from your current location.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">BRA, 183, 10, 2000, hot</pre> would mean the target is located at 183 degrees, 10 nautical miles away, and at 2000 feet coming directly towards you. North is 360. For aspect see figure 1.

=== Pronunciation ===
Instead of
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi 1-1, Magic, BRA, 183 for 10 at 2000, hot"</pre>
it is recommended to omit the "for" and "at", and to use short pauses (here indicated with "..."):
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi one one ... Magic ... BRA ... one eight zero ... ten ... two thousand ... hot"</pre>

=== Understanding bullseye ===
Bullseye is a fixed point on the map determined pre-mission. All allied aircraft can relate to this point. When receiving a bullseye call, simply use the BRA format with bullseye as starting point. Bullseye in DCS is represented with the following symbols
[[File:bullseye.png|thumb|frame|center|1000x|800px|Left:Bullseye representation in DCS World - Right: Bullseye details]]

== Human GCI/AWACS ==
In DCS World, players can take the role of GCI/AWACS on multiplayer servers to assist your fellow pilots and friends. In the following sections we’ll go over the basics of airspace management, threat assessment, callsigns, brevity and some useful tools.

Before you begin as a GCI/AWACS controller on a server go over this short checklist:
* Pick a suitable callsign

* Check and confirm the radio frequencies used for GCI/AWACS, general communications and air traffic control
* Tune in the correct frequencies on SRS
* Be in the correct server slot (if necessary)
* Have your tools set up and running
* Announce GCI/AWACS will be available over COMMS and CHAT. State the correct frequency and callsign
<pre style="background-color: #ccc;font-family: 'Lucida Console'">all flights on frequency be advised <callsign> will be available on <frequency> for GCI/AWACS</pre>
* If you are on the Hoggit Discord and are registering as a GAW GCI controller, the appropriate command on discord would be "!gci sunrise GAW <callsign, frequency, any other remarks>" command, use "!gci midnight" when you're finished with your session.

=== Airspace management ===
As a controller your goal is to manage both friendly and hostile airspace. You’ll want to direct your allied flights to intercept enemy threats while at the same time making sure your friendly airspace stays protected.

Divide the airspace you’ll be controlling into two sectors.
# a friendly sector
# a hostile sector

Divide sector 1, your friendly sector, into subsectors based on strategic locations like airfields or a FARPs.

Next, you can assign your available CAP flights to the subsectors you created, and have them patrol or set up orbit. This way you can ensure that
* your allied flights are in proximity to allied aircraft and able to support
* your allied aircraft are not spread out or alone in hostile airspace
* your allied aircraft are in range of a tanker or airfield
* your friendly sector is protected

=== Threat assessment ===
With your airspace divided into sectors and your CAP flights on station you can start intercepting enemy threats. There are 2 major things you want to pay close attention to at all times.
* Where are your allied aircraft in relation to your sectors
* Where are the enemy aircraft in relation to your sectors

Before making a decision to direct your allied flights to intercept, you want to assess the threat
# '''Distance''': what is the distance between the threat and the nearby sector or allied aircraft
# '''Number''': how many enemy aircraft make up the threat
# '''Type''': which type is the enemy threat
# ('''State'''): have they been engaged prior and thus used counter measures and/or weapons

When you have gathered this info you can make a decision to either:
* direct one or more allied aircraft to intercept the threat
* direct one or more aircraft away from the threat to nearby SAM cover
* direct one or more allied aircraft to support engaged allied aircraft

In case you are unsure and need extra information before making a decision, contact your allied flights and ask for a fuel and/or weapons state.

When directing your allied flights to intercept, try to keep them in proximity of other allied flights, so you have enough time to send in support if needed. Do not direct your allied flights into enemy airspace and SAM range without support.

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

=== Callsigns and radio communication ===
When acting as GCI/AWACS controller you want to make sure you have a callsign which
* is clear
* is easy to pronounce
* does not cause confusion
* is not ridiculous

Commonly used callsigns for GCI/AWACS are
* Overlord
* Magic
* Showtime
* Darkstar
* Goliath
* Wizard
* Griffin
* Bigfoot

As GCI/AWACS controller you’ll have to relay a lot of information in a clear, concise and easy to understand manner, usually in a short amount of time. It is important to have a good microphone set up, to speak loud and clear, articulate, not to speak too quickly and use the NATO phonetic alphabet to avoid confusion. We’ll discuss some examples below.

==== Responding to flights checking in ====
When allied flights switch to general comms or designated AWACS comms after take off, they’ll most likely check in on the frequency and let you know who they are and what their intentions are.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single flight F-18, 10 miles North of Anapa, checking in for CAP”</pre>

In the above example a player lets you know who they are, where they are and what their intentions are. You can respond to acknowledge (and task them if desired).

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima Charlie, standby for tasking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima, Charlie, fly heading 100 for 20, anchor at Krymsk”</pre>

==== Directing allied aircraft to intercept ====
When directing aircraft to intercept you want to be clear and concise. Start with who you are talking to, who you are and provide a BRA(A) call (and optional additional information). It is important to pronounce heading as single digits. For example ‘100’ would be ‘one, zero, zero.’

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA, 100, 40, 15 000, flanking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA, 100, 60, 500, hot, 2 ship type MiG-29”</pre>

==== Responding to a Bogey Dope request ====
When a player asks for a Bogey Dope, they are asking for the nearest hostile. Locate the aircraft who made the request, and provide them a BRA to the nearest hostile.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Request Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA, 257, 15, 10 000, cold”</pre>

When there are no hostile aircraft on scope
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Clean”</pre>

==== Responding to a DECLARE request ====
When you receive a DECLARE request, you are asked to identify friend or foe of a locked target.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, Bullseye 204/8, 12 thousand, DECLARE.”</pre>
or use BRAA (not technically correct, but fine here)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, BRAA 090/15, 12 thousand, DECLARE.”</pre>
Response:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Group, Bullseye 204/8, 12 thousand, hostile, single contact, flanker”</pre>
(fill-ins "single contact" and "flanker" are optional)

==== Miscellaneous ====
Sometimes you will need to ask for additional information, or provide additional information.

Return to base (RTB)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, winchester RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 010/35”</pre>

Ask for fuel state
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, state fuel”</pre>

Ask for weapons state:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, state weapons”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, 4/1/2 plus”</pre>
Note: Number of ARH, SARH, and IR-seeking missiles, and plus for Guns.

Inform aircraft to wait for instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, standby”</pre>

Ignore last transmitted message/instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, disregard last”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA 070/5, ... disregard, BRA 090/5, 7000, hot”</pre>

Identify unknown transmitting aircraft
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, request Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Last transmitting aircraft, state callsign”</pre>

Inform aircraft about incoming missiles or missile launches (unrealistic, generally only possible with F10 map)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, SAM, bearing 090”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, Missile, bearing 090”</pre>

=== Tools ===
==== SRS AWACS mode (eam) ====
The standard SRS radio overlay only displays up to 3 radios and 1 intercom. The AWACS overlay provides up to 10 radios, which you can manually tune and 1 intercom.

You can use SRS without running DCS World, by using the external AWACS mode (EAM). provide your EAM username and the EAM coalition password. The coalition password is provided by the server admin, or in the server briefing. This is not always available.

==== F10 map, icons and the ruler tool ====
The ingame F10 map is where you’ll spend most of your time doing GCI/AWACS. It provides several functions which you can toggle on or off by personal preference
* health bars
* SAM and AAA detection range indicators
* SAM and AAA engagement range indicators
* grid
* labels indicating type and name
* ruler tool

The most important function you’ll use is the ruler tool. It allows you to create a line from point A to point B and provides you with the length in nautical miles and the heading. When intercepting enemy aircraft you can use the ruler tool to draw a line from your allied aircraft A to the hostile aircraft B and read the distance in nautical miles and the heading indicated on the top bar. When you click on the enemy aircraft icon, you can read its altitude, speed in knots, heading and type on the bottom left.

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

==== LotATC ====
LotATC is an optional program one can use to facilitate GCI simulation. The program is fairly easy to use is highly customizable. LotATC provides many features to aid a GCI.

* The creation of persistant BRAAs
* IFF features
* An ATC mode
* The ability to call BRAAs from the bullseye
* A scale which can be used to respond to Picture calls
* The ability to draw on the map

For more information on LotATC and how to use the software see [https://wiki.hoggitworld.com/view/LotATC LotATC]

== Coordinating with human GCI/AWACS ==
A couple guidelines from the players point of view

Inform AWACS when you tune in or tune out of the AWACS frequency.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F18, 10nm North of Anapa, checking in for CAP”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single Mirage 2000, checking in for CAP”</pre>

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, bingo fuel, RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 100/35”</pre>

Do not clutter the AWACS frequency with off-topic chatter, use the correct frequencies as stated in mission briefing.

Do not read back a BRA call. Simply acknowledge you received and understood the message by saying your callsign. If you did not understand the transmission, ask AWACS to repeat.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA 100/45, 20 thousand, flank north west”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Uzi 1-1”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, say again”</pre>

Getting started with GCI/AWACS

2022-09-03T18:31:58Z

Marlan: /* Responding to a DECLARE request */

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

'''''Disclaimer''''' 
''This guide is compiled using information available to the public and information based on personal experience in DCS World. This guide does not in any way, shape or form represent real life GCI/AWACS operations or techniques nor is it based on real life experience.''

== What is GCI/AWACS ==
[[File:e3_awacs.jpg|thumb|frame|right|Boeing E-3 Sentry]]
GCI stands for '''G'''round-'''C'''ontrolled '''I'''nterception, an air defence tactic which developed during World War I. One or more radar stations or other observational stations are linked to a command communications centre which guides interceptor aircraft to airborne targets.

Today, GCI has mostly been replaced by Airborne Early Warning and Control (AEW&C) aircraft or more commonly referred to as AWACS ('''A'''irborne '''W'''arning '''A'''nd '''C'''ontrol '''S'''ystem). While AEW&C is expensive and vulnerable in comparison to GCI systems, it has a mobility advantage. In reality a combination of both systems is often used.

AWACS aircraft are generally speaking big, modified planes with a long-range radar mounted on top. The main radar antenna is mounted on a turntable housed in a circular rotodome, which is 9m (30 feet) in diameter, elliptical in cross-section and 1.8m deep at its centre. The radar system can detect, track and identify low-flying aircraft at approximately 370 km (200 nautical miles) and high-level aircraft at much greater distances.

== AI AWACS in DCS World ==
In DCS World the NATO AWACS comes in the form of the Boeing E-3 Sentry and the Russian equivalent is the Beriev A-50. The player can contact the allied AWACS via the ingame comms menu on the specified frequency in the mission briefing.

=== Comms menu ===
;Vector to bullseye
: The AWACS will provide the player with a bearing and range to bullseye

;Vector to home plate
: The AWACS will provide the player with a bearing and range from bullseye to their home airfield

;Vector to tanker
: The AWACS will provide the player with a bearing and range from bullseye to the tanker

;Request BOGEY DOPE
: The AWACS will provide the player a BRAA call to the closest airborne threat.

;Request PICTURE
: The AWACS will provide the player with BRA calls for each group from bullseye

;DECLARE
: The AWACS will identify friend or foe of a radar locked target

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

=== Understanding BRAA calls ===
[[File:aspect.jpg|thumb|frame|right|500x|400px|Figure 1]]
BRAA stands for '''B'''earing '''R'''ange '''A'''ltitude '''A'''spect from your current location.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">BRA, 183, 10, 2000, hot</pre> would mean the target is located at 183 degrees, 10 nautical miles away, and at 2000 feet coming directly towards you. North is 360. For aspect see figure 1.

=== Pronunciation ===
Instead of
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi 1-1, Magic, BRA, 183 for 10 at 2000, hot"</pre>
it is recommended to omit the "for" and "at", and to use short pauses (here indicated with "..."):
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi one one ... Magic ... BRA ... one eight zero ... ten ... two thousand ... hot"</pre>

=== Understanding bullseye ===
Bullseye is a fixed point on the map determined pre-mission. All allied aircraft can relate to this point. When receiving a bullseye call, simply use the BRA format with bullseye as starting point. Bullseye in DCS is represented with the following symbols
[[File:bullseye.png|thumb|frame|center|1000x|800px|Left:Bullseye representation in DCS World - Right: Bullseye details]]

== Human GCI/AWACS ==
In DCS World, players can take the role of GCI/AWACS on multiplayer servers to assist your fellow pilots and friends. In the following sections we’ll go over the basics of airspace management, threat assessment, callsigns, brevity and some useful tools.

Before you begin as a GCI/AWACS controller on a server go over this short checklist:
* Pick a suitable callsign

* Check and confirm the radio frequencies used for GCI/AWACS, general communications and air traffic control
* Tune in the correct frequencies on SRS
* Be in the correct server slot (if necessary)
* Have your tools set up and running
* Announce GCI/AWACS will be available over COMMS and CHAT. State the correct frequency and callsign
<pre style="background-color: #ccc;font-family: 'Lucida Console'">all flights on frequency be advised <callsign> will be available on <frequency> for GCI/AWACS</pre>
* If you are on the Hoggit Discord and are registering as a GAW GCI controller, the appropriate command on discord would be "!gci sunrise GAW <callsign, frequency, any other remarks>" command, use "!gci midnight" when you're finished with your session.

=== Airspace management ===
As a controller your goal is to manage both friendly and hostile airspace. You’ll want to direct your allied flights to intercept enemy threats while at the same time making sure your friendly airspace stays protected.

Divide the airspace you’ll be controlling into two sectors.
# a friendly sector
# a hostile sector

Divide sector 1, your friendly sector, into subsectors based on strategic locations like airfields or a FARPs.

Next, you can assign your available CAP flights to the subsectors you created, and have them patrol or set up orbit. This way you can ensure that
* your allied flights are in proximity to allied aircraft and able to support
* your allied aircraft are not spread out or alone in hostile airspace
* your allied aircraft are in range of a tanker or airfield
* your friendly sector is protected

=== Threat assessment ===
With your airspace divided into sectors and your CAP flights on station you can start intercepting enemy threats. There are 2 major things you want to pay close attention to at all times.
* Where are your allied aircraft in relation to your sectors
* Where are the enemy aircraft in relation to your sectors

Before making a decision to direct your allied flights to intercept, you want to assess the threat
# '''Distance''': what is the distance between the threat and the nearby sector or allied aircraft
# '''Number''': how many enemy aircraft make up the threat
# '''Type''': which type is the enemy threat
# ('''State'''): have they been engaged prior and thus used counter measures and/or weapons

When you have gathered this info you can make a decision to either:
* direct one or more allied aircraft to intercept the threat
* direct one or more aircraft away from the threat to nearby SAM cover
* direct one or more allied aircraft to support engaged allied aircraft

In case you are unsure and need extra information before making a decision, contact your allied flights and ask for a fuel and/or weapons state.

When directing your allied flights to intercept, try to keep them in proximity of other allied flights, so you have enough time to send in support if needed. Do not direct your allied flights into enemy airspace and SAM range without support.

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

=== Callsigns and radio communication ===
When acting as GCI/AWACS controller you want to make sure you have a callsign which
* is clear
* is easy to pronounce
* does not cause confusion
* is not ridiculous

Commonly used callsigns for GCI/AWACS are
* Overlord
* Magic
* Showtime
* Darkstar
* Goliath
* Wizard
* Griffin
* Bigfoot

As GCI/AWACS controller you’ll have to relay a lot of information in a clear, concise and easy to understand manner, usually in a short amount of time. It is important to have a good microphone set up, to speak loud and clear, articulate, not to speak too quickly and use the NATO phonetic alphabet to avoid confusion. We’ll discuss some examples below.

==== Responding to flights checking in ====
When allied flights switch to general comms or designated AWACS comms after take off, they’ll most likely check in on the frequency and let you know who they are and what their intentions are.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single flight F-18, 10 miles North of Anapa, checking in for CAP”</pre>

In the above example a player lets you know who they are, where they are and what their intentions are. You can respond to acknowledge (and task them if desired).

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima Charlie, standby for tasking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima, Charlie, fly heading 100 for 20, anchor at Krymsk”</pre>

==== Directing allied aircraft to intercept ====
When directing aircraft to intercept you want to be clear and concise. Start with who you are talking to, who you are and provide a BRA(A) call (and optional additional information). It is important to pronounce heading as single digits. For example ‘100’ would be ‘one, zero, zero.’

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA, 100, 40, 15 000, flanking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA, 100, 60, 500, hot, 2 ship type MiG-29”</pre>

==== Responding to a Bogey Dope request ====
When a player asks for a Bogey Dope, they are asking for the nearest hostile. Locate the aircraft who made the request, and provide them a BRA to the nearest hostile.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Request Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA, 257, 15, 10 000, cold”</pre>

When there are no hostile aircraft on scope
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Clean”</pre>

==== Responding to a DECLARE request ====
When you receive a DECLARE request, you are asked to identify friend or foe of a locked target.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, Bullseye 204/8, 12 thousand, DECLARE.”</pre>
or use BRAA (not technically correct, but fine here)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Group, BRAA 090/15, 12 thousand, DECLARE.”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Group, Bullseye 204/8, 12 thousand, hostile, single contact, flanker”</pre>

==== Miscellaneous ====
Sometimes you will need to ask for additional information, or provide additional information.

Return to base (RTB)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, winchester RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 010/35”</pre>

Ask for fuel state
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, state fuel”</pre>

Ask for weapons state:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, state weapons”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, 4/1/2 plus”</pre>
Note: Number of ARH, SARH, and IR-seeking missiles, and plus for Guns.

Inform aircraft to wait for instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, standby”</pre>

Ignore last transmitted message/instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, disregard last”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA 070/5, ... disregard, BRA 090/5, 7000, hot”</pre>

Identify unknown transmitting aircraft
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, request Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Last transmitting aircraft, state callsign”</pre>

Inform aircraft about incoming missiles or missile launches (unrealistic, generally only possible with F10 map)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, SAM, bearing 090”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, Missile, bearing 090”</pre>

=== Tools ===
==== SRS AWACS mode (eam) ====
The standard SRS radio overlay only displays up to 3 radios and 1 intercom. The AWACS overlay provides up to 10 radios, which you can manually tune and 1 intercom.

You can use SRS without running DCS World, by using the external AWACS mode (EAM). provide your EAM username and the EAM coalition password. The coalition password is provided by the server admin, or in the server briefing. This is not always available.

==== F10 map, icons and the ruler tool ====
The ingame F10 map is where you’ll spend most of your time doing GCI/AWACS. It provides several functions which you can toggle on or off by personal preference
* health bars
* SAM and AAA detection range indicators
* SAM and AAA engagement range indicators
* grid
* labels indicating type and name
* ruler tool

The most important function you’ll use is the ruler tool. It allows you to create a line from point A to point B and provides you with the length in nautical miles and the heading. When intercepting enemy aircraft you can use the ruler tool to draw a line from your allied aircraft A to the hostile aircraft B and read the distance in nautical miles and the heading indicated on the top bar. When you click on the enemy aircraft icon, you can read its altitude, speed in knots, heading and type on the bottom left.

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

==== LotATC ====
LotATC is an optional program one can use to facilitate GCI simulation. The program is fairly easy to use is highly customizable. LotATC provides many features to aid a GCI.

* The creation of persistant BRAAs
* IFF features
* An ATC mode
* The ability to call BRAAs from the bullseye
* A scale which can be used to respond to Picture calls
* The ability to draw on the map

For more information on LotATC and how to use the software see [https://wiki.hoggitworld.com/view/LotATC LotATC]

== Coordinating with human GCI/AWACS ==
A couple guidelines from the players point of view

Inform AWACS when you tune in or tune out of the AWACS frequency.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F18, 10nm North of Anapa, checking in for CAP”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single Mirage 2000, checking in for CAP”</pre>

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, bingo fuel, RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 100/35”</pre>

Do not clutter the AWACS frequency with off-topic chatter, use the correct frequencies as stated in mission briefing.

Do not read back a BRA call. Simply acknowledge you received and understood the message by saying your callsign. If you did not understand the transmission, ask AWACS to repeat.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA 100/45, 20 thousand, flank north west”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Uzi 1-1”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, say again”</pre>

Getting started with GCI/AWACS

2022-09-03T18:27:17Z

Marlan: /* Coordinating with human GCI/AWACS */

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

'''''Disclaimer''''' 
''This guide is compiled using information available to the public and information based on personal experience in DCS World. This guide does not in any way, shape or form represent real life GCI/AWACS operations or techniques nor is it based on real life experience.''

== What is GCI/AWACS ==
[[File:e3_awacs.jpg|thumb|frame|right|Boeing E-3 Sentry]]
GCI stands for '''G'''round-'''C'''ontrolled '''I'''nterception, an air defence tactic which developed during World War I. One or more radar stations or other observational stations are linked to a command communications centre which guides interceptor aircraft to airborne targets.

Today, GCI has mostly been replaced by Airborne Early Warning and Control (AEW&C) aircraft or more commonly referred to as AWACS ('''A'''irborne '''W'''arning '''A'''nd '''C'''ontrol '''S'''ystem). While AEW&C is expensive and vulnerable in comparison to GCI systems, it has a mobility advantage. In reality a combination of both systems is often used.

AWACS aircraft are generally speaking big, modified planes with a long-range radar mounted on top. The main radar antenna is mounted on a turntable housed in a circular rotodome, which is 9m (30 feet) in diameter, elliptical in cross-section and 1.8m deep at its centre. The radar system can detect, track and identify low-flying aircraft at approximately 370 km (200 nautical miles) and high-level aircraft at much greater distances.

== AI AWACS in DCS World ==
In DCS World the NATO AWACS comes in the form of the Boeing E-3 Sentry and the Russian equivalent is the Beriev A-50. The player can contact the allied AWACS via the ingame comms menu on the specified frequency in the mission briefing.

=== Comms menu ===
;Vector to bullseye
: The AWACS will provide the player with a bearing and range to bullseye

;Vector to home plate
: The AWACS will provide the player with a bearing and range from bullseye to their home airfield

;Vector to tanker
: The AWACS will provide the player with a bearing and range from bullseye to the tanker

;Request BOGEY DOPE
: The AWACS will provide the player a BRAA call to the closest airborne threat.

;Request PICTURE
: The AWACS will provide the player with BRA calls for each group from bullseye

;DECLARE
: The AWACS will identify friend or foe of a radar locked target

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

=== Understanding BRAA calls ===
[[File:aspect.jpg|thumb|frame|right|500x|400px|Figure 1]]
BRAA stands for '''B'''earing '''R'''ange '''A'''ltitude '''A'''spect from your current location.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">BRA, 183, 10, 2000, hot</pre> would mean the target is located at 183 degrees, 10 nautical miles away, and at 2000 feet coming directly towards you. North is 360. For aspect see figure 1.

=== Pronunciation ===
Instead of
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi 1-1, Magic, BRA, 183 for 10 at 2000, hot"</pre>
it is recommended to omit the "for" and "at", and to use short pauses (here indicated with "..."):
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi one one ... Magic ... BRA ... one eight zero ... ten ... two thousand ... hot"</pre>

=== Understanding bullseye ===
Bullseye is a fixed point on the map determined pre-mission. All allied aircraft can relate to this point. When receiving a bullseye call, simply use the BRA format with bullseye as starting point. Bullseye in DCS is represented with the following symbols
[[File:bullseye.png|thumb|frame|center|1000x|800px|Left:Bullseye representation in DCS World - Right: Bullseye details]]

== Human GCI/AWACS ==
In DCS World, players can take the role of GCI/AWACS on multiplayer servers to assist your fellow pilots and friends. In the following sections we’ll go over the basics of airspace management, threat assessment, callsigns, brevity and some useful tools.

Before you begin as a GCI/AWACS controller on a server go over this short checklist:
* Pick a suitable callsign

* Check and confirm the radio frequencies used for GCI/AWACS, general communications and air traffic control
* Tune in the correct frequencies on SRS
* Be in the correct server slot (if necessary)
* Have your tools set up and running
* Announce GCI/AWACS will be available over COMMS and CHAT. State the correct frequency and callsign
<pre style="background-color: #ccc;font-family: 'Lucida Console'">all flights on frequency be advised <callsign> will be available on <frequency> for GCI/AWACS</pre>
* If you are on the Hoggit Discord and are registering as a GAW GCI controller, the appropriate command on discord would be "!gci sunrise GAW <callsign, frequency, any other remarks>" command, use "!gci midnight" when you're finished with your session.

=== Airspace management ===
As a controller your goal is to manage both friendly and hostile airspace. You’ll want to direct your allied flights to intercept enemy threats while at the same time making sure your friendly airspace stays protected.

Divide the airspace you’ll be controlling into two sectors.
# a friendly sector
# a hostile sector

Divide sector 1, your friendly sector, into subsectors based on strategic locations like airfields or a FARPs.

Next, you can assign your available CAP flights to the subsectors you created, and have them patrol or set up orbit. This way you can ensure that
* your allied flights are in proximity to allied aircraft and able to support
* your allied aircraft are not spread out or alone in hostile airspace
* your allied aircraft are in range of a tanker or airfield
* your friendly sector is protected

=== Threat assessment ===
With your airspace divided into sectors and your CAP flights on station you can start intercepting enemy threats. There are 2 major things you want to pay close attention to at all times.
* Where are your allied aircraft in relation to your sectors
* Where are the enemy aircraft in relation to your sectors

Before making a decision to direct your allied flights to intercept, you want to assess the threat
# '''Distance''': what is the distance between the threat and the nearby sector or allied aircraft
# '''Number''': how many enemy aircraft make up the threat
# '''Type''': which type is the enemy threat
# ('''State'''): have they been engaged prior and thus used counter measures and/or weapons

When you have gathered this info you can make a decision to either:
* direct one or more allied aircraft to intercept the threat
* direct one or more aircraft away from the threat to nearby SAM cover
* direct one or more allied aircraft to support engaged allied aircraft

In case you are unsure and need extra information before making a decision, contact your allied flights and ask for a fuel and/or weapons state.

When directing your allied flights to intercept, try to keep them in proximity of other allied flights, so you have enough time to send in support if needed. Do not direct your allied flights into enemy airspace and SAM range without support.

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

=== Callsigns and radio communication ===
When acting as GCI/AWACS controller you want to make sure you have a callsign which
* is clear
* is easy to pronounce
* does not cause confusion
* is not ridiculous

Commonly used callsigns for GCI/AWACS are
* Overlord
* Magic
* Showtime
* Darkstar
* Goliath
* Wizard
* Griffin
* Bigfoot

As GCI/AWACS controller you’ll have to relay a lot of information in a clear, concise and easy to understand manner, usually in a short amount of time. It is important to have a good microphone set up, to speak loud and clear, articulate, not to speak too quickly and use the NATO phonetic alphabet to avoid confusion. We’ll discuss some examples below.

==== Responding to flights checking in ====
When allied flights switch to general comms or designated AWACS comms after take off, they’ll most likely check in on the frequency and let you know who they are and what their intentions are.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single flight F-18, 10 miles North of Anapa, checking in for CAP”</pre>

In the above example a player lets you know who they are, where they are and what their intentions are. You can respond to acknowledge (and task them if desired).

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima Charlie, standby for tasking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima, Charlie, fly heading 100 for 20, anchor at Krymsk”</pre>

==== Directing allied aircraft to intercept ====
When directing aircraft to intercept you want to be clear and concise. Start with who you are talking to, who you are and provide a BRA(A) call (and optional additional information). It is important to pronounce heading as single digits. For example ‘100’ would be ‘one, zero, zero.’

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA, 100, 40, 15 000, flanking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA, 100, 60, 500, hot, 2 ship type MiG-29”</pre>

==== Responding to a Bogey Dope request ====
When a player asks for a Bogey Dope, they are asking for the nearest hostile. Locate the aircraft who made the request, and provide them a BRA to the nearest hostile.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Request Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA, 257, 15, 10 000, cold”</pre>

When there are no hostile aircraft on scope
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Clean”</pre>

==== Responding to a DECLARE request ====
When you receive a DECLARE request, you are asked to identify friend or foe of a locked target.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, DECLARE 204, for 8”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, hostile/friendly”</pre>

==== Miscellaneous ====
Sometimes you will need to ask for additional information, or provide additional information.

Return to base (RTB)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, winchester RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 010/35”</pre>

Ask for fuel state
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, state fuel”</pre>

Ask for weapons state:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, state weapons”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, 4/1/2 plus”</pre>
Note: Number of ARH, SARH, and IR-seeking missiles, and plus for Guns.

Inform aircraft to wait for instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, standby”</pre>

Ignore last transmitted message/instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, disregard last”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA 070/5, ... disregard, BRA 090/5, 7000, hot”</pre>

Identify unknown transmitting aircraft
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, request Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Last transmitting aircraft, state callsign”</pre>

Inform aircraft about incoming missiles or missile launches (unrealistic, generally only possible with F10 map)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, SAM, bearing 090”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, Missile, bearing 090”</pre>

=== Tools ===
==== SRS AWACS mode (eam) ====
The standard SRS radio overlay only displays up to 3 radios and 1 intercom. The AWACS overlay provides up to 10 radios, which you can manually tune and 1 intercom.

You can use SRS without running DCS World, by using the external AWACS mode (EAM). provide your EAM username and the EAM coalition password. The coalition password is provided by the server admin, or in the server briefing. This is not always available.

==== F10 map, icons and the ruler tool ====
The ingame F10 map is where you’ll spend most of your time doing GCI/AWACS. It provides several functions which you can toggle on or off by personal preference
* health bars
* SAM and AAA detection range indicators
* SAM and AAA engagement range indicators
* grid
* labels indicating type and name
* ruler tool

The most important function you’ll use is the ruler tool. It allows you to create a line from point A to point B and provides you with the length in nautical miles and the heading. When intercepting enemy aircraft you can use the ruler tool to draw a line from your allied aircraft A to the hostile aircraft B and read the distance in nautical miles and the heading indicated on the top bar. When you click on the enemy aircraft icon, you can read its altitude, speed in knots, heading and type on the bottom left.

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

==== LotATC ====
LotATC is an optional program one can use to facilitate GCI simulation. The program is fairly easy to use is highly customizable. LotATC provides many features to aid a GCI.

* The creation of persistant BRAAs
* IFF features
* An ATC mode
* The ability to call BRAAs from the bullseye
* A scale which can be used to respond to Picture calls
* The ability to draw on the map

For more information on LotATC and how to use the software see [https://wiki.hoggitworld.com/view/LotATC LotATC]

== Coordinating with human GCI/AWACS ==
A couple guidelines from the players point of view

Inform AWACS when you tune in or tune out of the AWACS frequency.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single F18, 10nm North of Anapa, checking in for CAP”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single Mirage 2000, checking in for CAP”</pre>

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, bingo fuel, RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 100/35”</pre>

Do not clutter the AWACS frequency with off-topic chatter, use the correct frequencies as stated in mission briefing.

Do not read back a BRA call. Simply acknowledge you received and understood the message by saying your callsign. If you did not understand the transmission, ask AWACS to repeat.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA 100/45, 20 thousand, flank north west”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Uzi 1-1”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, say again”</pre>

Getting started with GCI/AWACS

2022-09-03T18:25:28Z

Marlan: /* Miscellaneous */

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

'''''Disclaimer''''' 
''This guide is compiled using information available to the public and information based on personal experience in DCS World. This guide does not in any way, shape or form represent real life GCI/AWACS operations or techniques nor is it based on real life experience.''

== What is GCI/AWACS ==
[[File:e3_awacs.jpg|thumb|frame|right|Boeing E-3 Sentry]]
GCI stands for '''G'''round-'''C'''ontrolled '''I'''nterception, an air defence tactic which developed during World War I. One or more radar stations or other observational stations are linked to a command communications centre which guides interceptor aircraft to airborne targets.

Today, GCI has mostly been replaced by Airborne Early Warning and Control (AEW&C) aircraft or more commonly referred to as AWACS ('''A'''irborne '''W'''arning '''A'''nd '''C'''ontrol '''S'''ystem). While AEW&C is expensive and vulnerable in comparison to GCI systems, it has a mobility advantage. In reality a combination of both systems is often used.

AWACS aircraft are generally speaking big, modified planes with a long-range radar mounted on top. The main radar antenna is mounted on a turntable housed in a circular rotodome, which is 9m (30 feet) in diameter, elliptical in cross-section and 1.8m deep at its centre. The radar system can detect, track and identify low-flying aircraft at approximately 370 km (200 nautical miles) and high-level aircraft at much greater distances.

== AI AWACS in DCS World ==
In DCS World the NATO AWACS comes in the form of the Boeing E-3 Sentry and the Russian equivalent is the Beriev A-50. The player can contact the allied AWACS via the ingame comms menu on the specified frequency in the mission briefing.

=== Comms menu ===
;Vector to bullseye
: The AWACS will provide the player with a bearing and range to bullseye

;Vector to home plate
: The AWACS will provide the player with a bearing and range from bullseye to their home airfield

;Vector to tanker
: The AWACS will provide the player with a bearing and range from bullseye to the tanker

;Request BOGEY DOPE
: The AWACS will provide the player a BRAA call to the closest airborne threat.

;Request PICTURE
: The AWACS will provide the player with BRA calls for each group from bullseye

;DECLARE
: The AWACS will identify friend or foe of a radar locked target

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

=== Understanding BRAA calls ===
[[File:aspect.jpg|thumb|frame|right|500x|400px|Figure 1]]
BRAA stands for '''B'''earing '''R'''ange '''A'''ltitude '''A'''spect from your current location.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">BRA, 183, 10, 2000, hot</pre> would mean the target is located at 183 degrees, 10 nautical miles away, and at 2000 feet coming directly towards you. North is 360. For aspect see figure 1.

=== Pronunciation ===
Instead of
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi 1-1, Magic, BRA, 183 for 10 at 2000, hot"</pre>
it is recommended to omit the "for" and "at", and to use short pauses (here indicated with "..."):
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi one one ... Magic ... BRA ... one eight zero ... ten ... two thousand ... hot"</pre>

=== Understanding bullseye ===
Bullseye is a fixed point on the map determined pre-mission. All allied aircraft can relate to this point. When receiving a bullseye call, simply use the BRA format with bullseye as starting point. Bullseye in DCS is represented with the following symbols
[[File:bullseye.png|thumb|frame|center|1000x|800px|Left:Bullseye representation in DCS World - Right: Bullseye details]]

== Human GCI/AWACS ==
In DCS World, players can take the role of GCI/AWACS on multiplayer servers to assist your fellow pilots and friends. In the following sections we’ll go over the basics of airspace management, threat assessment, callsigns, brevity and some useful tools.

Before you begin as a GCI/AWACS controller on a server go over this short checklist:
* Pick a suitable callsign

* Check and confirm the radio frequencies used for GCI/AWACS, general communications and air traffic control
* Tune in the correct frequencies on SRS
* Be in the correct server slot (if necessary)
* Have your tools set up and running
* Announce GCI/AWACS will be available over COMMS and CHAT. State the correct frequency and callsign
<pre style="background-color: #ccc;font-family: 'Lucida Console'">all flights on frequency be advised <callsign> will be available on <frequency> for GCI/AWACS</pre>
* If you are on the Hoggit Discord and are registering as a GAW GCI controller, the appropriate command on discord would be "!gci sunrise GAW <callsign, frequency, any other remarks>" command, use "!gci midnight" when you're finished with your session.

=== Airspace management ===
As a controller your goal is to manage both friendly and hostile airspace. You’ll want to direct your allied flights to intercept enemy threats while at the same time making sure your friendly airspace stays protected.

Divide the airspace you’ll be controlling into two sectors.
# a friendly sector
# a hostile sector

Divide sector 1, your friendly sector, into subsectors based on strategic locations like airfields or a FARPs.

Next, you can assign your available CAP flights to the subsectors you created, and have them patrol or set up orbit. This way you can ensure that
* your allied flights are in proximity to allied aircraft and able to support
* your allied aircraft are not spread out or alone in hostile airspace
* your allied aircraft are in range of a tanker or airfield
* your friendly sector is protected

=== Threat assessment ===
With your airspace divided into sectors and your CAP flights on station you can start intercepting enemy threats. There are 2 major things you want to pay close attention to at all times.
* Where are your allied aircraft in relation to your sectors
* Where are the enemy aircraft in relation to your sectors

Before making a decision to direct your allied flights to intercept, you want to assess the threat
# '''Distance''': what is the distance between the threat and the nearby sector or allied aircraft
# '''Number''': how many enemy aircraft make up the threat
# '''Type''': which type is the enemy threat
# ('''State'''): have they been engaged prior and thus used counter measures and/or weapons

When you have gathered this info you can make a decision to either:
* direct one or more allied aircraft to intercept the threat
* direct one or more aircraft away from the threat to nearby SAM cover
* direct one or more allied aircraft to support engaged allied aircraft

In case you are unsure and need extra information before making a decision, contact your allied flights and ask for a fuel and/or weapons state.

When directing your allied flights to intercept, try to keep them in proximity of other allied flights, so you have enough time to send in support if needed. Do not direct your allied flights into enemy airspace and SAM range without support.

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

=== Callsigns and radio communication ===
When acting as GCI/AWACS controller you want to make sure you have a callsign which
* is clear
* is easy to pronounce
* does not cause confusion
* is not ridiculous

Commonly used callsigns for GCI/AWACS are
* Overlord
* Magic
* Showtime
* Darkstar
* Goliath
* Wizard
* Griffin
* Bigfoot

As GCI/AWACS controller you’ll have to relay a lot of information in a clear, concise and easy to understand manner, usually in a short amount of time. It is important to have a good microphone set up, to speak loud and clear, articulate, not to speak too quickly and use the NATO phonetic alphabet to avoid confusion. We’ll discuss some examples below.

==== Responding to flights checking in ====
When allied flights switch to general comms or designated AWACS comms after take off, they’ll most likely check in on the frequency and let you know who they are and what their intentions are.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single flight F-18, 10 miles North of Anapa, checking in for CAP”</pre>

In the above example a player lets you know who they are, where they are and what their intentions are. You can respond to acknowledge (and task them if desired).

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima Charlie, standby for tasking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima, Charlie, fly heading 100 for 20, anchor at Krymsk”</pre>

==== Directing allied aircraft to intercept ====
When directing aircraft to intercept you want to be clear and concise. Start with who you are talking to, who you are and provide a BRA(A) call (and optional additional information). It is important to pronounce heading as single digits. For example ‘100’ would be ‘one, zero, zero.’

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA, 100, 40, 15 000, flanking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA, 100, 60, 500, hot, 2 ship type MiG-29”</pre>

==== Responding to a Bogey Dope request ====
When a player asks for a Bogey Dope, they are asking for the nearest hostile. Locate the aircraft who made the request, and provide them a BRA to the nearest hostile.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Request Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA, 257, 15, 10 000, cold”</pre>

When there are no hostile aircraft on scope
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Clean”</pre>

==== Responding to a DECLARE request ====
When you receive a DECLARE request, you are asked to identify friend or foe of a locked target.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, DECLARE 204, for 8”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, hostile/friendly”</pre>

==== Miscellaneous ====
Sometimes you will need to ask for additional information, or provide additional information.

Return to base (RTB)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, winchester RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 010/35”</pre>

Ask for fuel state
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, state fuel”</pre>

Ask for weapons state:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, state weapons”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, 4/1/2 plus”</pre>
Note: Number of ARH, SARH, and IR-seeking missiles, and plus for Guns.

Inform aircraft to wait for instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, standby”</pre>

Ignore last transmitted message/instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, disregard last”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA 070/5, ... disregard, BRA 090/5, 7000, hot”</pre>

Identify unknown transmitting aircraft
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, request Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Last transmitting aircraft, state callsign”</pre>

Inform aircraft about incoming missiles or missile launches (unrealistic, generally only possible with F10 map)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, SAM, bearing 090”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, Missile, bearing 090”</pre>

=== Tools ===
==== SRS AWACS mode (eam) ====
The standard SRS radio overlay only displays up to 3 radios and 1 intercom. The AWACS overlay provides up to 10 radios, which you can manually tune and 1 intercom.

You can use SRS without running DCS World, by using the external AWACS mode (EAM). provide your EAM username and the EAM coalition password. The coalition password is provided by the server admin, or in the server briefing. This is not always available.

==== F10 map, icons and the ruler tool ====
The ingame F10 map is where you’ll spend most of your time doing GCI/AWACS. It provides several functions which you can toggle on or off by personal preference
* health bars
* SAM and AAA detection range indicators
* SAM and AAA engagement range indicators
* grid
* labels indicating type and name
* ruler tool

The most important function you’ll use is the ruler tool. It allows you to create a line from point A to point B and provides you with the length in nautical miles and the heading. When intercepting enemy aircraft you can use the ruler tool to draw a line from your allied aircraft A to the hostile aircraft B and read the distance in nautical miles and the heading indicated on the top bar. When you click on the enemy aircraft icon, you can read its altitude, speed in knots, heading and type on the bottom left.

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

==== LotATC ====
LotATC is an optional program one can use to facilitate GCI simulation. The program is fairly easy to use is highly customizable. LotATC provides many features to aid a GCI.

* The creation of persistant BRAAs
* IFF features
* An ATC mode
* The ability to call BRAAs from the bullseye
* A scale which can be used to respond to Picture calls
* The ability to draw on the map

For more information on LotATC and how to use the software see [https://wiki.hoggitworld.com/view/LotATC LotATC]

== Coordinating with human GCI/AWACS ==
A couple guidelines from the players point of view

Inform AWACS when you tune in or tune out of the AWACS frequency.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single flight F18, 10nm North of Anapa, checking in for CAP”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, type Mirage 2000, checking in for CAP”</pre>

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, bingo fuel, RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Roger, fly heading 100 for 35”</pre>

Do not clutter the AWACS frequency with off-topic chatter, use the correct frequencies as stated in mission briefing.

Do not read back a BRA call. Simply acknowledge you received and understood the message by saying your callsign. If you did not understand the transmission, ask AWACS to repeat.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA 100, 45, 20 000, flanking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Uzi 1-1”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, repeat last”</pre>

Getting started with GCI/AWACS

2022-09-03T18:25:04Z

Marlan: /* Miscellaneous */

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

'''''Disclaimer''''' 
''This guide is compiled using information available to the public and information based on personal experience in DCS World. This guide does not in any way, shape or form represent real life GCI/AWACS operations or techniques nor is it based on real life experience.''

== What is GCI/AWACS ==
[[File:e3_awacs.jpg|thumb|frame|right|Boeing E-3 Sentry]]
GCI stands for '''G'''round-'''C'''ontrolled '''I'''nterception, an air defence tactic which developed during World War I. One or more radar stations or other observational stations are linked to a command communications centre which guides interceptor aircraft to airborne targets.

Today, GCI has mostly been replaced by Airborne Early Warning and Control (AEW&C) aircraft or more commonly referred to as AWACS ('''A'''irborne '''W'''arning '''A'''nd '''C'''ontrol '''S'''ystem). While AEW&C is expensive and vulnerable in comparison to GCI systems, it has a mobility advantage. In reality a combination of both systems is often used.

AWACS aircraft are generally speaking big, modified planes with a long-range radar mounted on top. The main radar antenna is mounted on a turntable housed in a circular rotodome, which is 9m (30 feet) in diameter, elliptical in cross-section and 1.8m deep at its centre. The radar system can detect, track and identify low-flying aircraft at approximately 370 km (200 nautical miles) and high-level aircraft at much greater distances.

== AI AWACS in DCS World ==
In DCS World the NATO AWACS comes in the form of the Boeing E-3 Sentry and the Russian equivalent is the Beriev A-50. The player can contact the allied AWACS via the ingame comms menu on the specified frequency in the mission briefing.

=== Comms menu ===
;Vector to bullseye
: The AWACS will provide the player with a bearing and range to bullseye

;Vector to home plate
: The AWACS will provide the player with a bearing and range from bullseye to their home airfield

;Vector to tanker
: The AWACS will provide the player with a bearing and range from bullseye to the tanker

;Request BOGEY DOPE
: The AWACS will provide the player a BRAA call to the closest airborne threat.

;Request PICTURE
: The AWACS will provide the player with BRA calls for each group from bullseye

;DECLARE
: The AWACS will identify friend or foe of a radar locked target

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

=== Understanding BRAA calls ===
[[File:aspect.jpg|thumb|frame|right|500x|400px|Figure 1]]
BRAA stands for '''B'''earing '''R'''ange '''A'''ltitude '''A'''spect from your current location.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">BRA, 183, 10, 2000, hot</pre> would mean the target is located at 183 degrees, 10 nautical miles away, and at 2000 feet coming directly towards you. North is 360. For aspect see figure 1.

=== Pronunciation ===
Instead of
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi 1-1, Magic, BRA, 183 for 10 at 2000, hot"</pre>
it is recommended to omit the "for" and "at", and to use short pauses (here indicated with "..."):
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi one one ... Magic ... BRA ... one eight zero ... ten ... two thousand ... hot"</pre>

=== Understanding bullseye ===
Bullseye is a fixed point on the map determined pre-mission. All allied aircraft can relate to this point. When receiving a bullseye call, simply use the BRA format with bullseye as starting point. Bullseye in DCS is represented with the following symbols
[[File:bullseye.png|thumb|frame|center|1000x|800px|Left:Bullseye representation in DCS World - Right: Bullseye details]]

== Human GCI/AWACS ==
In DCS World, players can take the role of GCI/AWACS on multiplayer servers to assist your fellow pilots and friends. In the following sections we’ll go over the basics of airspace management, threat assessment, callsigns, brevity and some useful tools.

Before you begin as a GCI/AWACS controller on a server go over this short checklist:
* Pick a suitable callsign

* Check and confirm the radio frequencies used for GCI/AWACS, general communications and air traffic control
* Tune in the correct frequencies on SRS
* Be in the correct server slot (if necessary)
* Have your tools set up and running
* Announce GCI/AWACS will be available over COMMS and CHAT. State the correct frequency and callsign
<pre style="background-color: #ccc;font-family: 'Lucida Console'">all flights on frequency be advised <callsign> will be available on <frequency> for GCI/AWACS</pre>
* If you are on the Hoggit Discord and are registering as a GAW GCI controller, the appropriate command on discord would be "!gci sunrise GAW <callsign, frequency, any other remarks>" command, use "!gci midnight" when you're finished with your session.

=== Airspace management ===
As a controller your goal is to manage both friendly and hostile airspace. You’ll want to direct your allied flights to intercept enemy threats while at the same time making sure your friendly airspace stays protected.

Divide the airspace you’ll be controlling into two sectors.
# a friendly sector
# a hostile sector

Divide sector 1, your friendly sector, into subsectors based on strategic locations like airfields or a FARPs.

Next, you can assign your available CAP flights to the subsectors you created, and have them patrol or set up orbit. This way you can ensure that
* your allied flights are in proximity to allied aircraft and able to support
* your allied aircraft are not spread out or alone in hostile airspace
* your allied aircraft are in range of a tanker or airfield
* your friendly sector is protected

=== Threat assessment ===
With your airspace divided into sectors and your CAP flights on station you can start intercepting enemy threats. There are 2 major things you want to pay close attention to at all times.
* Where are your allied aircraft in relation to your sectors
* Where are the enemy aircraft in relation to your sectors

Before making a decision to direct your allied flights to intercept, you want to assess the threat
# '''Distance''': what is the distance between the threat and the nearby sector or allied aircraft
# '''Number''': how many enemy aircraft make up the threat
# '''Type''': which type is the enemy threat
# ('''State'''): have they been engaged prior and thus used counter measures and/or weapons

When you have gathered this info you can make a decision to either:
* direct one or more allied aircraft to intercept the threat
* direct one or more aircraft away from the threat to nearby SAM cover
* direct one or more allied aircraft to support engaged allied aircraft

In case you are unsure and need extra information before making a decision, contact your allied flights and ask for a fuel and/or weapons state.

When directing your allied flights to intercept, try to keep them in proximity of other allied flights, so you have enough time to send in support if needed. Do not direct your allied flights into enemy airspace and SAM range without support.

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

=== Callsigns and radio communication ===
When acting as GCI/AWACS controller you want to make sure you have a callsign which
* is clear
* is easy to pronounce
* does not cause confusion
* is not ridiculous

Commonly used callsigns for GCI/AWACS are
* Overlord
* Magic
* Showtime
* Darkstar
* Goliath
* Wizard
* Griffin
* Bigfoot

As GCI/AWACS controller you’ll have to relay a lot of information in a clear, concise and easy to understand manner, usually in a short amount of time. It is important to have a good microphone set up, to speak loud and clear, articulate, not to speak too quickly and use the NATO phonetic alphabet to avoid confusion. We’ll discuss some examples below.

==== Responding to flights checking in ====
When allied flights switch to general comms or designated AWACS comms after take off, they’ll most likely check in on the frequency and let you know who they are and what their intentions are.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single flight F-18, 10 miles North of Anapa, checking in for CAP”</pre>

In the above example a player lets you know who they are, where they are and what their intentions are. You can respond to acknowledge (and task them if desired).

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima Charlie, standby for tasking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima, Charlie, fly heading 100 for 20, anchor at Krymsk”</pre>

==== Directing allied aircraft to intercept ====
When directing aircraft to intercept you want to be clear and concise. Start with who you are talking to, who you are and provide a BRA(A) call (and optional additional information). It is important to pronounce heading as single digits. For example ‘100’ would be ‘one, zero, zero.’

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA, 100, 40, 15 000, flanking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA, 100, 60, 500, hot, 2 ship type MiG-29”</pre>

==== Responding to a Bogey Dope request ====
When a player asks for a Bogey Dope, they are asking for the nearest hostile. Locate the aircraft who made the request, and provide them a BRA to the nearest hostile.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Request Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA, 257, 15, 10 000, cold”</pre>

When there are no hostile aircraft on scope
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Clean”</pre>

==== Responding to a DECLARE request ====
When you receive a DECLARE request, you are asked to identify friend or foe of a locked target.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, DECLARE 204, for 8”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, hostile/friendly”</pre>

==== Miscellaneous ====
Sometimes you will need to ask for additional information, or provide additional information.

Return to base (RTB)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, winchester RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 010/35”</pre>

Ask for fuel state
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, state fuel”</pre>

Ask for weapons state:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, state weapons”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, 4/1/2 plus”</pre>
Note: Number of ARH, SARH, and IR-seeking missiles, and plus for Guns.

Inform aircraft to wait for instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, standby”</pre>

Ignore last transmitted message/instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, disregard last”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA 070/5, ... disregard, BRA 090/5, 7000, hot”</pre>

Identify unknown transmitting aircraft
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, request Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Last transmitting aircraft, state callsign”</pre>

Inform aircraft about incoming missiles or missile launches (unrealistic, only possible with F10 map)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, SAM, bearing 090”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, Missile, bearing 090”</pre>

=== Tools ===
==== SRS AWACS mode (eam) ====
The standard SRS radio overlay only displays up to 3 radios and 1 intercom. The AWACS overlay provides up to 10 radios, which you can manually tune and 1 intercom.

You can use SRS without running DCS World, by using the external AWACS mode (EAM). provide your EAM username and the EAM coalition password. The coalition password is provided by the server admin, or in the server briefing. This is not always available.

==== F10 map, icons and the ruler tool ====
The ingame F10 map is where you’ll spend most of your time doing GCI/AWACS. It provides several functions which you can toggle on or off by personal preference
* health bars
* SAM and AAA detection range indicators
* SAM and AAA engagement range indicators
* grid
* labels indicating type and name
* ruler tool

The most important function you’ll use is the ruler tool. It allows you to create a line from point A to point B and provides you with the length in nautical miles and the heading. When intercepting enemy aircraft you can use the ruler tool to draw a line from your allied aircraft A to the hostile aircraft B and read the distance in nautical miles and the heading indicated on the top bar. When you click on the enemy aircraft icon, you can read its altitude, speed in knots, heading and type on the bottom left.

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

==== LotATC ====
LotATC is an optional program one can use to facilitate GCI simulation. The program is fairly easy to use is highly customizable. LotATC provides many features to aid a GCI.

* The creation of persistant BRAAs
* IFF features
* An ATC mode
* The ability to call BRAAs from the bullseye
* A scale which can be used to respond to Picture calls
* The ability to draw on the map

For more information on LotATC and how to use the software see [https://wiki.hoggitworld.com/view/LotATC LotATC]

== Coordinating with human GCI/AWACS ==
A couple guidelines from the players point of view

Inform AWACS when you tune in or tune out of the AWACS frequency.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single flight F18, 10nm North of Anapa, checking in for CAP”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, type Mirage 2000, checking in for CAP”</pre>

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, bingo fuel, RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Roger, fly heading 100 for 35”</pre>

Do not clutter the AWACS frequency with off-topic chatter, use the correct frequencies as stated in mission briefing.

Do not read back a BRA call. Simply acknowledge you received and understood the message by saying your callsign. If you did not understand the transmission, ask AWACS to repeat.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA 100, 45, 20 000, flanking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Uzi 1-1”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, repeat last”</pre>

Getting started with GCI/AWACS

2022-09-03T18:24:16Z

Marlan: /* Miscellaneous */

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

'''''Disclaimer''''' 
''This guide is compiled using information available to the public and information based on personal experience in DCS World. This guide does not in any way, shape or form represent real life GCI/AWACS operations or techniques nor is it based on real life experience.''

== What is GCI/AWACS ==
[[File:e3_awacs.jpg|thumb|frame|right|Boeing E-3 Sentry]]
GCI stands for '''G'''round-'''C'''ontrolled '''I'''nterception, an air defence tactic which developed during World War I. One or more radar stations or other observational stations are linked to a command communications centre which guides interceptor aircraft to airborne targets.

Today, GCI has mostly been replaced by Airborne Early Warning and Control (AEW&C) aircraft or more commonly referred to as AWACS ('''A'''irborne '''W'''arning '''A'''nd '''C'''ontrol '''S'''ystem). While AEW&C is expensive and vulnerable in comparison to GCI systems, it has a mobility advantage. In reality a combination of both systems is often used.

AWACS aircraft are generally speaking big, modified planes with a long-range radar mounted on top. The main radar antenna is mounted on a turntable housed in a circular rotodome, which is 9m (30 feet) in diameter, elliptical in cross-section and 1.8m deep at its centre. The radar system can detect, track and identify low-flying aircraft at approximately 370 km (200 nautical miles) and high-level aircraft at much greater distances.

== AI AWACS in DCS World ==
In DCS World the NATO AWACS comes in the form of the Boeing E-3 Sentry and the Russian equivalent is the Beriev A-50. The player can contact the allied AWACS via the ingame comms menu on the specified frequency in the mission briefing.

=== Comms menu ===
;Vector to bullseye
: The AWACS will provide the player with a bearing and range to bullseye

;Vector to home plate
: The AWACS will provide the player with a bearing and range from bullseye to their home airfield

;Vector to tanker
: The AWACS will provide the player with a bearing and range from bullseye to the tanker

;Request BOGEY DOPE
: The AWACS will provide the player a BRAA call to the closest airborne threat.

;Request PICTURE
: The AWACS will provide the player with BRA calls for each group from bullseye

;DECLARE
: The AWACS will identify friend or foe of a radar locked target

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

=== Understanding BRAA calls ===
[[File:aspect.jpg|thumb|frame|right|500x|400px|Figure 1]]
BRAA stands for '''B'''earing '''R'''ange '''A'''ltitude '''A'''spect from your current location.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">BRA, 183, 10, 2000, hot</pre> would mean the target is located at 183 degrees, 10 nautical miles away, and at 2000 feet coming directly towards you. North is 360. For aspect see figure 1.

=== Pronunciation ===
Instead of
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi 1-1, Magic, BRA, 183 for 10 at 2000, hot"</pre>
it is recommended to omit the "for" and "at", and to use short pauses (here indicated with "..."):
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi one one ... Magic ... BRA ... one eight zero ... ten ... two thousand ... hot"</pre>

=== Understanding bullseye ===
Bullseye is a fixed point on the map determined pre-mission. All allied aircraft can relate to this point. When receiving a bullseye call, simply use the BRA format with bullseye as starting point. Bullseye in DCS is represented with the following symbols
[[File:bullseye.png|thumb|frame|center|1000x|800px|Left:Bullseye representation in DCS World - Right: Bullseye details]]

== Human GCI/AWACS ==
In DCS World, players can take the role of GCI/AWACS on multiplayer servers to assist your fellow pilots and friends. In the following sections we’ll go over the basics of airspace management, threat assessment, callsigns, brevity and some useful tools.

Before you begin as a GCI/AWACS controller on a server go over this short checklist:
* Pick a suitable callsign

* Check and confirm the radio frequencies used for GCI/AWACS, general communications and air traffic control
* Tune in the correct frequencies on SRS
* Be in the correct server slot (if necessary)
* Have your tools set up and running
* Announce GCI/AWACS will be available over COMMS and CHAT. State the correct frequency and callsign
<pre style="background-color: #ccc;font-family: 'Lucida Console'">all flights on frequency be advised <callsign> will be available on <frequency> for GCI/AWACS</pre>
* If you are on the Hoggit Discord and are registering as a GAW GCI controller, the appropriate command on discord would be "!gci sunrise GAW <callsign, frequency, any other remarks>" command, use "!gci midnight" when you're finished with your session.

=== Airspace management ===
As a controller your goal is to manage both friendly and hostile airspace. You’ll want to direct your allied flights to intercept enemy threats while at the same time making sure your friendly airspace stays protected.

Divide the airspace you’ll be controlling into two sectors.
# a friendly sector
# a hostile sector

Divide sector 1, your friendly sector, into subsectors based on strategic locations like airfields or a FARPs.

Next, you can assign your available CAP flights to the subsectors you created, and have them patrol or set up orbit. This way you can ensure that
* your allied flights are in proximity to allied aircraft and able to support
* your allied aircraft are not spread out or alone in hostile airspace
* your allied aircraft are in range of a tanker or airfield
* your friendly sector is protected

=== Threat assessment ===
With your airspace divided into sectors and your CAP flights on station you can start intercepting enemy threats. There are 2 major things you want to pay close attention to at all times.
* Where are your allied aircraft in relation to your sectors
* Where are the enemy aircraft in relation to your sectors

Before making a decision to direct your allied flights to intercept, you want to assess the threat
# '''Distance''': what is the distance between the threat and the nearby sector or allied aircraft
# '''Number''': how many enemy aircraft make up the threat
# '''Type''': which type is the enemy threat
# ('''State'''): have they been engaged prior and thus used counter measures and/or weapons

When you have gathered this info you can make a decision to either:
* direct one or more allied aircraft to intercept the threat
* direct one or more aircraft away from the threat to nearby SAM cover
* direct one or more allied aircraft to support engaged allied aircraft

In case you are unsure and need extra information before making a decision, contact your allied flights and ask for a fuel and/or weapons state.

When directing your allied flights to intercept, try to keep them in proximity of other allied flights, so you have enough time to send in support if needed. Do not direct your allied flights into enemy airspace and SAM range without support.

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

=== Callsigns and radio communication ===
When acting as GCI/AWACS controller you want to make sure you have a callsign which
* is clear
* is easy to pronounce
* does not cause confusion
* is not ridiculous

Commonly used callsigns for GCI/AWACS are
* Overlord
* Magic
* Showtime
* Darkstar
* Goliath
* Wizard
* Griffin
* Bigfoot

As GCI/AWACS controller you’ll have to relay a lot of information in a clear, concise and easy to understand manner, usually in a short amount of time. It is important to have a good microphone set up, to speak loud and clear, articulate, not to speak too quickly and use the NATO phonetic alphabet to avoid confusion. We’ll discuss some examples below.

==== Responding to flights checking in ====
When allied flights switch to general comms or designated AWACS comms after take off, they’ll most likely check in on the frequency and let you know who they are and what their intentions are.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single flight F-18, 10 miles North of Anapa, checking in for CAP”</pre>

In the above example a player lets you know who they are, where they are and what their intentions are. You can respond to acknowledge (and task them if desired).

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima Charlie, standby for tasking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima, Charlie, fly heading 100 for 20, anchor at Krymsk”</pre>

==== Directing allied aircraft to intercept ====
When directing aircraft to intercept you want to be clear and concise. Start with who you are talking to, who you are and provide a BRA(A) call (and optional additional information). It is important to pronounce heading as single digits. For example ‘100’ would be ‘one, zero, zero.’

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA, 100, 40, 15 000, flanking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA, 100, 60, 500, hot, 2 ship type MiG-29”</pre>

==== Responding to a Bogey Dope request ====
When a player asks for a Bogey Dope, they are asking for the nearest hostile. Locate the aircraft who made the request, and provide them a BRA to the nearest hostile.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Request Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA, 257, 15, 10 000, cold”</pre>

When there are no hostile aircraft on scope
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Clean”</pre>

==== Responding to a DECLARE request ====
When you receive a DECLARE request, you are asked to identify friend or foe of a locked target.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, DECLARE 204, for 8”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, hostile/friendly”</pre>

==== Miscellaneous ====
Sometimes you will need to ask for additional information, or provide additional information.

Return to base (RTB)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, winchester RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, fly heading 010/35”</pre>

Ask for fuel state
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, state fuel”</pre>

Ask for weapons state:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, state weapons”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, 4/1/2 plus”</pre>
Note: Number of ARH, SARH, and IR-seeking missiles, and plus for Guns.

Inform aircraft to wait for instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, standby”</pre>

Ignore last transmitted message/instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, disregard last”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA 070/5, ... disregard, BRA 090/5, 7000, hot”</pre>

Identify unknown transmitting aircraft
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, request Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Last transmitting aircraft, state callsign”</pre>

Inform aircraft about incoming missiles or missile launches (unrealistic, only possible with F10 map)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND West, SAM, bearing 090”</pre>

=== Tools ===
==== SRS AWACS mode (eam) ====
The standard SRS radio overlay only displays up to 3 radios and 1 intercom. The AWACS overlay provides up to 10 radios, which you can manually tune and 1 intercom.

You can use SRS without running DCS World, by using the external AWACS mode (EAM). provide your EAM username and the EAM coalition password. The coalition password is provided by the server admin, or in the server briefing. This is not always available.

==== F10 map, icons and the ruler tool ====
The ingame F10 map is where you’ll spend most of your time doing GCI/AWACS. It provides several functions which you can toggle on or off by personal preference
* health bars
* SAM and AAA detection range indicators
* SAM and AAA engagement range indicators
* grid
* labels indicating type and name
* ruler tool

The most important function you’ll use is the ruler tool. It allows you to create a line from point A to point B and provides you with the length in nautical miles and the heading. When intercepting enemy aircraft you can use the ruler tool to draw a line from your allied aircraft A to the hostile aircraft B and read the distance in nautical miles and the heading indicated on the top bar. When you click on the enemy aircraft icon, you can read its altitude, speed in knots, heading and type on the bottom left.

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

==== LotATC ====
LotATC is an optional program one can use to facilitate GCI simulation. The program is fairly easy to use is highly customizable. LotATC provides many features to aid a GCI.

* The creation of persistant BRAAs
* IFF features
* An ATC mode
* The ability to call BRAAs from the bullseye
* A scale which can be used to respond to Picture calls
* The ability to draw on the map

For more information on LotATC and how to use the software see [https://wiki.hoggitworld.com/view/LotATC LotATC]

== Coordinating with human GCI/AWACS ==
A couple guidelines from the players point of view

Inform AWACS when you tune in or tune out of the AWACS frequency.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single flight F18, 10nm North of Anapa, checking in for CAP”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, type Mirage 2000, checking in for CAP”</pre>

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, bingo fuel, RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Roger, fly heading 100 for 35”</pre>

Do not clutter the AWACS frequency with off-topic chatter, use the correct frequencies as stated in mission briefing.

Do not read back a BRA call. Simply acknowledge you received and understood the message by saying your callsign. If you did not understand the transmission, ask AWACS to repeat.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA 100, 45, 20 000, flanking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Uzi 1-1”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, repeat last”</pre>

Getting started with GCI/AWACS

2022-09-03T18:19:08Z

Marlan: "Picture Clear" to "Clean"

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

'''''Disclaimer''''' 
''This guide is compiled using information available to the public and information based on personal experience in DCS World. This guide does not in any way, shape or form represent real life GCI/AWACS operations or techniques nor is it based on real life experience.''

== What is GCI/AWACS ==
[[File:e3_awacs.jpg|thumb|frame|right|Boeing E-3 Sentry]]
GCI stands for '''G'''round-'''C'''ontrolled '''I'''nterception, an air defence tactic which developed during World War I. One or more radar stations or other observational stations are linked to a command communications centre which guides interceptor aircraft to airborne targets.

Today, GCI has mostly been replaced by Airborne Early Warning and Control (AEW&C) aircraft or more commonly referred to as AWACS ('''A'''irborne '''W'''arning '''A'''nd '''C'''ontrol '''S'''ystem). While AEW&C is expensive and vulnerable in comparison to GCI systems, it has a mobility advantage. In reality a combination of both systems is often used.

AWACS aircraft are generally speaking big, modified planes with a long-range radar mounted on top. The main radar antenna is mounted on a turntable housed in a circular rotodome, which is 9m (30 feet) in diameter, elliptical in cross-section and 1.8m deep at its centre. The radar system can detect, track and identify low-flying aircraft at approximately 370 km (200 nautical miles) and high-level aircraft at much greater distances.

== AI AWACS in DCS World ==
In DCS World the NATO AWACS comes in the form of the Boeing E-3 Sentry and the Russian equivalent is the Beriev A-50. The player can contact the allied AWACS via the ingame comms menu on the specified frequency in the mission briefing.

=== Comms menu ===
;Vector to bullseye
: The AWACS will provide the player with a bearing and range to bullseye

;Vector to home plate
: The AWACS will provide the player with a bearing and range from bullseye to their home airfield

;Vector to tanker
: The AWACS will provide the player with a bearing and range from bullseye to the tanker

;Request BOGEY DOPE
: The AWACS will provide the player a BRAA call to the closest airborne threat.

;Request PICTURE
: The AWACS will provide the player with BRA calls for each group from bullseye

;DECLARE
: The AWACS will identify friend or foe of a radar locked target

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

=== Understanding BRAA calls ===
[[File:aspect.jpg|thumb|frame|right|500x|400px|Figure 1]]
BRAA stands for '''B'''earing '''R'''ange '''A'''ltitude '''A'''spect from your current location.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">BRA, 183, 10, 2000, hot</pre> would mean the target is located at 183 degrees, 10 nautical miles away, and at 2000 feet coming directly towards you. North is 360. For aspect see figure 1.

=== Pronunciation ===
Instead of
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi 1-1, Magic, BRA, 183 for 10 at 2000, hot"</pre>
it is recommended to omit the "for" and "at", and to use short pauses (here indicated with "..."):
<pre style="background-color: #ccc;font-family: 'Lucida Console'">"Uzi one one ... Magic ... BRA ... one eight zero ... ten ... two thousand ... hot"</pre>

=== Understanding bullseye ===
Bullseye is a fixed point on the map determined pre-mission. All allied aircraft can relate to this point. When receiving a bullseye call, simply use the BRA format with bullseye as starting point. Bullseye in DCS is represented with the following symbols
[[File:bullseye.png|thumb|frame|center|1000x|800px|Left:Bullseye representation in DCS World - Right: Bullseye details]]

== Human GCI/AWACS ==
In DCS World, players can take the role of GCI/AWACS on multiplayer servers to assist your fellow pilots and friends. In the following sections we’ll go over the basics of airspace management, threat assessment, callsigns, brevity and some useful tools.

Before you begin as a GCI/AWACS controller on a server go over this short checklist:
* Pick a suitable callsign

* Check and confirm the radio frequencies used for GCI/AWACS, general communications and air traffic control
* Tune in the correct frequencies on SRS
* Be in the correct server slot (if necessary)
* Have your tools set up and running
* Announce GCI/AWACS will be available over COMMS and CHAT. State the correct frequency and callsign
<pre style="background-color: #ccc;font-family: 'Lucida Console'">all flights on frequency be advised <callsign> will be available on <frequency> for GCI/AWACS</pre>
* If you are on the Hoggit Discord and are registering as a GAW GCI controller, the appropriate command on discord would be "!gci sunrise GAW <callsign, frequency, any other remarks>" command, use "!gci midnight" when you're finished with your session.

=== Airspace management ===
As a controller your goal is to manage both friendly and hostile airspace. You’ll want to direct your allied flights to intercept enemy threats while at the same time making sure your friendly airspace stays protected.

Divide the airspace you’ll be controlling into two sectors.
# a friendly sector
# a hostile sector

Divide sector 1, your friendly sector, into subsectors based on strategic locations like airfields or a FARPs.

Next, you can assign your available CAP flights to the subsectors you created, and have them patrol or set up orbit. This way you can ensure that
* your allied flights are in proximity to allied aircraft and able to support
* your allied aircraft are not spread out or alone in hostile airspace
* your allied aircraft are in range of a tanker or airfield
* your friendly sector is protected

=== Threat assessment ===
With your airspace divided into sectors and your CAP flights on station you can start intercepting enemy threats. There are 2 major things you want to pay close attention to at all times.
* Where are your allied aircraft in relation to your sectors
* Where are the enemy aircraft in relation to your sectors

Before making a decision to direct your allied flights to intercept, you want to assess the threat
# '''Distance''': what is the distance between the threat and the nearby sector or allied aircraft
# '''Number''': how many enemy aircraft make up the threat
# '''Type''': which type is the enemy threat
# ('''State'''): have they been engaged prior and thus used counter measures and/or weapons

When you have gathered this info you can make a decision to either:
* direct one or more allied aircraft to intercept the threat
* direct one or more aircraft away from the threat to nearby SAM cover
* direct one or more allied aircraft to support engaged allied aircraft

In case you are unsure and need extra information before making a decision, contact your allied flights and ask for a fuel and/or weapons state.

When directing your allied flights to intercept, try to keep them in proximity of other allied flights, so you have enough time to send in support if needed. Do not direct your allied flights into enemy airspace and SAM range without support.

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

=== Callsigns and radio communication ===
When acting as GCI/AWACS controller you want to make sure you have a callsign which
* is clear
* is easy to pronounce
* does not cause confusion
* is not ridiculous

Commonly used callsigns for GCI/AWACS are
* Overlord
* Magic
* Showtime
* Darkstar
* Goliath
* Wizard
* Griffin
* Bigfoot

As GCI/AWACS controller you’ll have to relay a lot of information in a clear, concise and easy to understand manner, usually in a short amount of time. It is important to have a good microphone set up, to speak loud and clear, articulate, not to speak too quickly and use the NATO phonetic alphabet to avoid confusion. We’ll discuss some examples below.

==== Responding to flights checking in ====
When allied flights switch to general comms or designated AWACS comms after take off, they’ll most likely check in on the frequency and let you know who they are and what their intentions are.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single flight F-18, 10 miles North of Anapa, checking in for CAP”</pre>

In the above example a player lets you know who they are, where they are and what their intentions are. You can respond to acknowledge (and task them if desired).

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima Charlie, standby for tasking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Lima, Charlie, fly heading 100 for 20, anchor at Krymsk”</pre>

==== Directing allied aircraft to intercept ====
When directing aircraft to intercept you want to be clear and concise. Start with who you are talking to, who you are and provide a BRA(A) call (and optional additional information). It is important to pronounce heading as single digits. For example ‘100’ would be ‘one, zero, zero.’

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA, 100, 40, 15 000, flanking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA, 100, 60, 500, hot, 2 ship type MiG-29”</pre>

==== Responding to a Bogey Dope request ====
When a player asks for a Bogey Dope, they are asking for the nearest hostile. Locate the aircraft who made the request, and provide them a BRA to the nearest hostile.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, Request Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA, 257, 15, 10 000, cold”</pre>

When there are no hostile aircraft on scope
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Clean”</pre>

==== Responding to a DECLARE request ====
When you receive a DECLARE request, you are asked to identify friend or foe of a locked target.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, DECLARE 204, for 8”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, hostile/friendly”</pre>

==== Miscellaneous ====
Sometimes you will need to ask for additional information, or provide additional information.

Return to base (RTB)
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, winchester RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, Roger, fly heading 010 for 35”</pre>

Ask for fuel state
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, state fuel”</pre>

Ask for weapons state:
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, state weapons”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, 4 1 2 plus”</pre>
Note: Number of ARH, SARH, and IR-seeking missiles, and plus for Guns.

Inform aircraft to wait for instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, standby”</pre>

Ignore last transmitted message/instructions
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, disregard last”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA 070, 5, ... disregard, BRA 090, 5, 7000, hot”</pre>

Identify unknown transmitting aircraft
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, request Bogey Dope”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Last transmitting aircraft, state callsign”</pre>

Inform aircraft about incoming missiles or missile launches
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, DEFEND”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, missile launch, 9 o’clock, go defensive”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, SAM launch, 12 o’clock go defensive”</pre>

=== Tools ===
==== SRS AWACS mode (eam) ====
The standard SRS radio overlay only displays up to 3 radios and 1 intercom. The AWACS overlay provides up to 10 radios, which you can manually tune and 1 intercom.

You can use SRS without running DCS World, by using the external AWACS mode (EAM). provide your EAM username and the EAM coalition password. The coalition password is provided by the server admin, or in the server briefing. This is not always available.

==== F10 map, icons and the ruler tool ====
The ingame F10 map is where you’ll spend most of your time doing GCI/AWACS. It provides several functions which you can toggle on or off by personal preference
* health bars
* SAM and AAA detection range indicators
* SAM and AAA engagement range indicators
* grid
* labels indicating type and name
* ruler tool

The most important function you’ll use is the ruler tool. It allows you to create a line from point A to point B and provides you with the length in nautical miles and the heading. When intercepting enemy aircraft you can use the ruler tool to draw a line from your allied aircraft A to the hostile aircraft B and read the distance in nautical miles and the heading indicated on the top bar. When you click on the enemy aircraft icon, you can read its altitude, speed in knots, heading and type on the bottom left.

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

==== LotATC ====
LotATC is an optional program one can use to facilitate GCI simulation. The program is fairly easy to use is highly customizable. LotATC provides many features to aid a GCI.

* The creation of persistant BRAAs
* IFF features
* An ATC mode
* The ability to call BRAAs from the bullseye
* A scale which can be used to respond to Picture calls
* The ability to draw on the map

For more information on LotATC and how to use the software see [https://wiki.hoggitworld.com/view/LotATC LotATC]

== Coordinating with human GCI/AWACS ==
A couple guidelines from the players point of view

Inform AWACS when you tune in or tune out of the AWACS frequency.
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, single flight F18, 10nm North of Anapa, checking in for CAP”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, type Mirage 2000, checking in for CAP”</pre>

<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, bingo fuel, RTB”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Roger, fly heading 100 for 35”</pre>

Do not clutter the AWACS frequency with off-topic chatter, use the correct frequencies as stated in mission briefing.

Do not read back a BRA call. Simply acknowledge you received and understood the message by saying your callsign. If you did not understand the transmission, ask AWACS to repeat.

<pre style="background-color: #ccc;font-family: 'Lucida Console'">AWACS - “Uzi 1-1, Magic, BRA 100, 45, 20 000, flanking”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Uzi 1-1”</pre>
<pre style="background-color: #ccc;font-family: 'Lucida Console'">Flight - “Magic, Uzi 1-1, repeat last”</pre>