UOAF Codex - User contributions [en]

BFM tactics

2017-04-08T08:36:56Z

Lexi:

[[File:Scissors.jpg||none|546x|left|]]

=Learning objectives=
# Understand the concept of energy
# Understand the concept of lift vector
# Understand the concept of the corner speed (turn radius vs turn rate)
# Know the different pursuit curves. (Lead, lag and pure pursuit)
# know the high and low yoyo maneuvers
# know the difference between one circle and two circles turns and when to employ them
# know the flat and rolling scissors
# understand the concept of flying the elbow
# understand the concept of the egg (god's G)
# know how to use the dogfight mode, the HMCS and the radar modes linked to them
# know the brevity words usualy used in dogfight

=Learning files=
* [http://www.krauselabs.net/dump/FighterCombatTactics.pdf Shaw's Fighter Combat Tactics and Maneuvering]
*[http://www.simhq.com/_air/air_097a.html How to be a Good Stick]

=Energy=
[[File:Em.jpg||none|640px|left|]]
*0.55 Mach is around 366 knots
*Don’t pull back hard on the stick and unnecessarily bleed off energy

=Video Examples=
<embedvideo service="youtube" dimensions="400">https://www.youtube.com/watch?v=jNgvFeWr14g</embedvideo>
<embedvideo service="youtube" dimensions="400">https://www.youtube.com/watch?v=CBOcWEOUlec</embedvideo>
<embedvideo service="youtube" dimensions="400">https://www.youtube.com/watch?v=6oKqS_tZsuM</embedvideo>

{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Advanced avionics

2017-03-25T11:27:40Z

Lexi: /* boresighting procedure */

=Learning objectives=
# CRUS page
# Time page and ROLEX
# BINGO page
# STPT page
# MARK page
# TFR
# FLIR
 

=DED pages=
==CRUS Page==
The Cruise page provides information for navigation, time and fuel while cruising. It has 4 submodes: TOS, RNG, HOME and EDR 
Each submode '''MUST BE''' mode selected to become active and supply accurate information and cues.(HUD carrets mainly) Remember mode-selecting is done with the M-SEL 0 button and when active highlights the area. 
The submodes of the CRUS page are accessed sequentially with DCS SEQ. 
[[File:UFC CRUS-TOS-page.jpg|thumb|right|CRUS page in TOS submode]]
===TOS (TIME Over Steerpoint) submode===
This submode is used a lot by flight leaders to respect mission timings.(that's what they're talking about when they're saying i.e "Lobo 1 is on carret") 
When activated with M-SEL a carret is displayed on HUD in the speed tape. To ensure that you reach the steerpoint on time for TOS match your airspeed with the caret. 
The ETA to the steerpoint is also displayed in the HUD.
[[File:UFC CRUS-RNG-page.jpg|thumb|right|CRUS page in RNG submode]]
===RNG (Range) submode===
When RNG is mode selected a caret is displayed on the HUD speed tape to pinpoint the best conserve fuel speed at this altitude. Optimum speed for fuel conservation changes with altitude. 
Only the active steerpoint can be toggled on this subpage. 
Further information given on this page shows fuel remaining when reaching the active steerpoint, wind direction and speed.
[[File:UFC CRUS-HOME-page.jpg|thumb|right|CRUS page in HOME submode]]
===HOME submode===
When HOME is mode selected 2 carets are displayed in the HUD on the speed tape and on the altitude tape. Following these 2 carets will establish the best profile to reach Home Plate (or any steerpoint designated as HMPT).
The procedure to fly this profile is to select full military power, reach the speed caret first then pitch to reach the altitude mark while maintaining the speed on the caret. Altitude may vary according to fuel burned. 
Please note, optimal altitude is given in radar altitude on the DED, but may be different on your HUD scale depending on the altimeter setting. If you follow both carets you will reach the home point at the selected optimum altitude. The altitude caret will disappear once you can start your descent. Further information displayed on this page indicates home point (can be changed to any INS steerpoint (e.g. alternate)), onboard fuel quantity remaining when reaching active steerpoint, optimum altitude for the HOME profile, wind direction and speed.
[[File:UFC CRUS-EDR-page.jpg|thumb|right|CRUS page in EDR submode]]
===EDR (Endurance) submode===
When EDR mode is mode selected a speed caret is placed on the HUD tape to give a reference speed for best endurance at this altitude. This is very useful for holding patterns or maximum endurance cruise for instance. Further information given is time to bingo, optimum Mach number and wind direction and speed.

==TIME page and ROLEX==
[[File:UFC Time-page.jpg|thumb|right|TIME page]]
The TIME page allows the pilot to set a HACK timer and a DELTA TOS for ROLEX calls. The first line gives the current system time. The second line is the hack timer. As the arrows indicate, pressing the ICP NEXT rocker button will start/freeze/resume the timer and ICP PREVIOUS rocker button will reset the hack timer to zero. When the HACK timer is running it is also visible on the CNI page. 
ROLEX calls are initiated when TOS for all steerpoints need to be adjusted. This is done through the TIME page by changing the DELTA TOS. Place the scratchpad on the DELTA TOS line and input the ROLEX value. If a minus is required start your input with the 0 (zero) ICP key for the minus sign. 
:For instance: “Mamba flight Rolex +2” => TIME, DCS down to DELTA TOS: 2, 0, 0, ENTR 
:Another example: “Mamba flight Rolex -3” => TIME, DCS down to DELTA TOS: 0, 3, 0, 0, ENTR 

<embedvideo service="youtube">https://www.youtube.com/watch?v=irEEdxfGe-g</embedvideo>

==BINGO page==
[[File:UFC BINGO-page.jpg|thumb|right|BINGO page]]
The BINGO page is where you input your briefed Joker/Bingo settings. It is made up of two lines: the first one is where you enter your Joker or Bingo setting and the second line is the total fuel remaining on board. It is good practice as a mission begins to input the Joker value. You can then reset it to the briefed Bingo value once Joker fuel is reached. 
Assuming those fuel consumption :
:*Low alt = 20 lbs/Nm - 100 ft to FL150 / RPM 100% / 540 kts GS
:*Med alt = 15 lbs/Nm - FL150 to FL250 / RPM 100% / 540 kts GS
:*Hgh alt = 10 lbs/Nm - FL250 to FL400 / RPM 100% / 400 kts GS
Here is a quick way to calculate your BINGO : 
:(return leg * consumption) + (diverted leg * consumption) + normal recovery fuel (F-16 MLU ,block 10, 15, 20, 25, 30 and 32 = 1000 lbs / F-16 block 40 to 52 = 1200 lbs) + two landing trials (400 lbs). 
The JOKER is usually set to BINGO + 1000 lbs which correspond to 1 mn of afterburner or 10 mn of flight time at 350 kts.
[[File:BMS FUEL chart.jpg||none|450px|left|]] 

==STPT page==
[[File:UFC STPT-page.png|thumb|right|STPT page]]
The Steerpoint page gives the pilot information about the INS steerpoint. 
:*The first line allows the pilots to toggle the active steerpoint with the NEXT/PREV ICP buttons (notice the up & down arrows) and the MAN or AUTO steerpoint function, which can be toggled with DCS SEQ. MAN means that the new steerpoint has to be manually selected. AUTO will increment to the next steerpoint automatically when the INS detects the proximity of the current waypoint. In AUTO mode an “A” symbol is displayed on the CNI page next to the steerpoint.
:*The second line is the LATITUDE of the currently selected steerpoint. Placing the scratchpad there will let the pilot enter the latitude for this particular navigation point.
:*The third line is the LONGITUDE of the selected steerpoint. It can also be changed by placing the scratchpad accordingly and entering new coordinates.
:*The fourth line is the elevation of the steerpoint (the altitude at which you are supposed to overfly the steerpoint according to your INS flight plan). This is different from the real jet that has the ground spot height for steerpoint in this field (it is quite relevant to TGP mechanisation and finding the target).
:*The fifth line is the TOS (Time Over Steerpoint) which gives you the local time the steerpoint will be reached, if you are following the route of flight as planned.

==MARK page==
[[File:UFC MARK-page.png|thumb|right|MARK page]]
The MARK page is used to create markpoints. Ownship markpoints are stored in steerpoints 26-30.(Once #30 is filled, the next markpoint will overwrite #26 and so on) 
Markpoints can be made from 4 different systems:
:*OFLY (Overfly GPS/INS)
:*FCR (Fire Control Radar)
:*HUD (Head Up Display)
:*TGP (Targeting Pod).
There are thus 4 submodes in the MARK page. To toggle between the submodes use DCS SEQ. The system defaults to a specific subpage according to master mode and Sensor of Interest (SOI) and may enable automatic markpoint recording (automatic markpoint are only made in the Air to Air mode) 
Markpoints are created with TMS forward (TMS up) and are visible on the HSD page once created as a cyan cross. 

=TFR (Terrain Following Radar)=
[[File:BMS-TFR.png|thumb|right|TFR screen in MFD]]
It is available only on F-16s carrying both LANTIRN pods (Block 25/30/32/40 EAF/42/52+, KF-16 & F-16I). The TFR is a short range radar that allows you to follow the terrain at very low altitude with automatic fly up protection. 
As with all pods / systems the TFR needs a certain amount of time to become operational. This time starts when the TFR is placed out of OFF to STBY. The TFR is ready when the NOT TIMED OUT message disappears. Obviously the chin hardpoints must be powered and the radar altimeter must be operational. 
Activate the TFR by placing it in NORM and select the desired SCP. Both options highlight on the TFR page. The TFR E-scope display will start displaying a visual representation of the terrain ahead. 
The TFR has 3 Ride options: HARD - SOFT - SMTH (smooth) and 7 modes of operation: OFF – BIT – STBY – NORM – LPI – WX – VLC
===NORM===
This is the normal mode of operation and accessed with OSB #20. It has 3 submodes: 
:*MAN TF: the pilot receives FPM cueing (MAN TF box) in the HUD to maintain a selected altitude above ground level. He hand flies the jet but the TFR offers automatic fly-up protection if the MANUAL TF FLYUP switch is in ENABLE. The ADV light on the MISC panel is unlit.
:*AUTO TF: the flight control computer uses the vertical acceleration commands generated in the LANTIRN pod to maneuver the aircraft to maintain the selected SCP (Set Clearance Plane) altitude. In AUTO TF the ADV light on the MISC panel has the top indicator (ACTIVE) lit and a horizontal line is shown near the FPM on the HUD. The pilot can override the TFR (just like the autopilot) by depressing the paddle switch on the stick. While the paddle is depressed the STBY (bottom part of the ADV) light on the MISC panel is illuminated.
:*Blended TF: the autopilot is engaged to hold a specific barometric altitude (or attitude). If the LANTIRN pod detects the aircraft violating the selected minimum AGL the system will automatically maneuver the aircraft to maintain the minimum AGL until the terrain has dropped away. A/P PITCH switch is in ALT or ATT HOLD. STBY ADV light is on. Horizontal line visible.
===LPI===
LPI stands for Low Probability of Intercept. It allows minimal TFR use with the RF switch placed in the QUIET position. It is activated by pressing OSB #19 or automatically upon placing the RF switch in QUIET. 
NOTE: placing the RF switch in SILENT places the TFR in STBY.
===WX===
WX mode is used in bad weather (rain) to minimize uncommanded fly-ups due to conflicting radar returns in rain or fog. It is activated with either the MFD TFR page OSB#17 or the ICP WX button.
===VLC===
Very Low Clearance mode (100ft SCP) is accessed from OSB #10. This mode is to be used only on relatively flat terrain or over water. 

=FLIR (Forward Looking IR)=
[[File:BMS-FLIR.png|thumb|right|FLIR in MFD (top) and HUD]]
The FLIR page is only available when both LANTIRN pods are loaded on the chin pylons of compatible F-16s (Block 25/30/32/40 EAF/42/52+, KF-16 & F-16I).Obviously chin hardpoints must be powered up for the FLIR to be operational. The FLIR needs between 8 and 15 minutes to cool down before use so start the process as soon as possible. The FLIR will be ready to operate as soon as the NOT TIMED OUT message disappears from the MFD. 
OSB #18 places the FLIR in standby. OSB #20 places the FLIR in operational mode (OPER). Once operational the FLIR page will display the infrared view in front of the pod. The image can be repeated on the HUD by rotating the BRT ICP wheel upwards. The FLIR level can be changed with the ICP up and down FLIR arrows. The current gain and level values are displayed on the top left corner of the FLIR MFD. 
==Boresighting Procedure==
OSB #10 is the boresight option. The boresight is used to better match the image in the HUD with the image from the FLIR camera at a certain range. 
Depress OSB#10 and the BSGT mnemonic highlights. The HUD FLIR image can then be slewed with the cursors. Do not boresight on close objects. It is advised to boresight in flight on large objects such as the edge of a mountain or a road for instance. Once both images are superimposed correctly depress OSB#10 again and the BSGT mnemonic will return to its initial state. 
Once the FLIR image is displayed on the HUD the MFD page does not need to be active, though it is advisable to have it on one of the DA buttons for easy access to boresighting.
==LOOK-INTO-TURN (LIT) and SNAPLOOK capabilities==
LOOK-INTO-TURN (LIT) and SNAPLOOK capabilities are available on the HUD.
:*LIT: when the bank angle is above 5° holding DMS UP will shift the FLIR view slightly into the turn to provide lead obstacle clearance. The FLIR image reverts to forward looking when DMS UP is released.
:*SNAPLOOK: The view can be shifted further in flight by holding DMS UP and moving the cursors in any direction, even in a turn. The view will revert to forward looking when DMS UP is released.
When LIT or SNAPLOOK are active the FPM is dashed.

{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Air-to-air refuelling

2017-03-25T11:24:52Z

Lexi: /* Procedures */

[[File:F16-aar.jpg||none|500px|left|]] 

=Learning objectives=
#Finding the Tanker
#Pre & Post Refueling positions/formation
#Pre-Tanker Checks
#Cleared to Contact

=Learning files=
<embedvideo service="youtube">https://www.youtube.com/watch?v=5Ekj7DxP0pg</embedvideo>

Before we start in earnest, the #1 tip you can remember – '''small inputs'''!

If you're going to move your throttle, stick or pedals once you are anywhere near the tanker, be gentle. If you feel yourself getting tense, drop back 100 feet, release the death-grip you have on your stick, and shake out the tension for a second. This requires precision flying skills which in turn requires practice practice practice - it's tough, but not impossible. Just focus, and keep your inputs small. A good technique some use is to actually unwrap your fingers from the stick and use only small pushes with the web of the hand, base of the thumb and forefinger to get into position. Whatever works for you!

=Procedures=
The F16 does not carry a lot of fuel, so air-to-air refueling is '''a must''' in longer sorties; this service is provided by KC-10 and KC-135 aircraft in BMS Falcon 4.33.

First, the pilot needs to find the tanker. There are essentially four ways to find the tanker:

#Contact AWACS for vectors
#Use the FCR to locate potential tanker contacts (assuming you already know roughly where to look)
#Use the tanker’s TACAN channel to provide directions. Note however, that the air-to-air TACAN used by tankers in BMS typically provides only distance information. The one exception to this is the KC-10 which will also provide bearing information.
#Use of marked “tanker tracks” on the HSD. If you or the mission planner marked the tanker positions on the 2D planning screen these steer point lines / boxes will appear on your HSD.

==Distance Matters==
Before refueling the flight will need to establish radio contact with the tanker to ask for fuel. It is critical that ALL ships in a flight be within the 10nm bubble centered on the tanker during communications. Depending on the distance from the tanker, when flight lead makes the initial contact the answer will either be:

*If the flight is farther than 10 Nm the tanker will respond with heading and distance for rejoin.
*If the flight is at or within 10 Nm the flight will be cleared directly to the pre-contact position. At this point the flight is to proceed to the Observation Area on the tanker's left wing -(see picture)

The standard formation for refueling is left echelon where all ships waiting to take fuel are on the left wing of the tanker and each other stacked high (you can tell if you are stacked enough if the you can see the opposite wing of the tanker). When an aircraft is done refueling move to the same position on the right wing of the tanker (now echelon right and again stacked high).

==Pre-Tanker Checks==

The following steps should be taken prior to reaching the left observation station at the tanker and are typically done more than 3-5nm away from the tanker:

*Master Arm OFF
*External Lights ON
*Radar STANDBY (Done at 1nm - Use the OVRD button on the FCR)
*DED Bingo Page ACTIVE (Optional)
*AR Door OPEN (Note: IRL it is good practice to open the AR door three to five minutes prior refueling to allow the external tanks to depressurize slightly but not too early due to the possibility of creating a trapped fuel situation)

==Cleared to Pre-Contact Position==

Once the tanker has cleared you to Pre-Contact, acknowledge that call on UHF (or other prebriefed channel) then move to the pre-contact position. This position needs to be held for a few seconds to be recognized by the coded boomer. Basically, the receiver aircraft will be 50 feet below at 30° down from the tanker. The best method to get that position correctly is to put the gun cross on the tip of the boom and fly towards it until the boom is just in front of the cockpit. There is no need to request fuel from the tanker; if you are in the correct position you will be cleared to Contact Position. Be advised, there are absolutely no director lights at this stage. Hold position a few feet level behind the boom.

[[File:AAR.png|thumb|400px|Director lights]]

==Cleared to Contact Position==
[[File:Refueling lights.jpg|thumb|right|Refueling lights]]
When the boom operator has a good visual with the pilot the tanker will call “call sign, cleared to contact position”. Again, acknowledge the tanker call on UHF (or prebriefed channel) and move to the contact position. The director lights F (Forward) and U (Up) will switch on to give further positional guidance (if the lights go towards F, it means move forward, if they go towards U they mean up, A means aft and D means down). Start to move towards the boom and it will move to left or right to let the pilot get into contact position. The key is to make very small corrections. Make a small adjustment as needed, wait for the reaction, and continue as needed. Do not overreact.

The tanker will call “call sign, cleared to contact position”. Again, acknowledge the tanker call on UHF (or prebriefed channel) and move to the contact position. The director lights F (Forward) and U (Up) will switch on to give further positional guidance (if the lights go towards F, it means move forward, if they go towards U they mean up, A means aft and D means down). Start to move towards the boom and it will move to left or right to let the pilot get into contact position. The key is to make very small corrections. Make a small adjustment as needed, wait for the reaction, and continue as needed. Do not overreact.

==On the boom (Contact!)==

When all the lights go out don't move, the boom operator is trying to connect! The pilot needs to hold this position for a few seconds. Once contact has been made the director lights will become active again; these will help the pilot to adjust position to stay connected with the boom. In previous versions of Falcon the pilot may remember the boom “snapping” into the correct position no matter what; this is no longer the case with BMS. The boom will remain connected as long as the receiver stays within its manoeuvring envelope. When the boom connects the blue RDY light on the right indexer shuts off and the green AR/NWS light comes on.

While on the boom, the only (UHF) radio calls required by the pilot are:

*“Contact” or “Good flow” to indicate you are on the boom and receiving fuel
*“1000 to go” to indicate you are within 1000 lbs. of your desired fuel capacity

[[File:Observation_%26_Reform_Area.jpg|thumb|]]

==Disconnecting==

If your desired fuel level is less than fully topped off, press your NWS/Disc button once you have reached the desired quantity. Once disconnected, press Y-3 to notify the tanker you are done and the next aircraft can be cleared into position. The tanker needs to be called with this “done refueling” command to allow the next flight member to be cleared for refuel. It is very important that the cadet press Y-3 IMMEDIATELY after disconnecting (the closer to the boom the better). The only exception to this is if you are the LAST aircraft in your flight; in that case rejoin your flight in the right observation area before calling Y-3. Failure of any pilot to clear the tanker will result in failed tanking operations for other flights!

If the pilot needs to take on additional fuel after requesting a disconnect (NWS button) AND before clearing the tanker with “Y-3”, simply back off a bit and re-request fuel (Y-2). This is the only time you will need to request fuel once the initial refueling request has been made. The boom operator should clear you to the pre-contact position and you can begin the process over again.

The last aircraft in the flight must be sure to press Y-3, preferably once he has rejoined his wingman on the right side. At all times the flight MUST remain within 10nm of the tanker and the last pilot MUST clear the tanker (Y-3) before leaving the 10nm bubble.

==Tanker/AAR Comms Overview==

*From the left observation position, acknowledge “<Call sign> Cleared to Pre-Contact”
*Once connected and fuel is flowing, call “<Call sign> has good flow”
*Once within 1000 lbs of your desired fuel level, call “<Call sign> 1000 to go”
*Issue a Y-3 command to clear the tanker once you have completed your refueling

Communications and brevity

2017-03-19T10:38:45Z

Lexi: /* Learning Objectives */

[[File:F16-pilot.jpg||none|500px|left|]] 

== Learning Objectives ==
#Understand the correct syntax used when communicating between fighter aircraft.
#Learn the important brevity code words. 

=== Learning Files ===
* [http://www.krauselabs.net/dump/Us_Marine_Corps---Multi_Service_Brevity_Codes_Mcrp_3-25B.pdf MULTI-SERVICE BREVITY CODES PDF]
*[https://en.wikipedia.org/wiki/Multiservice_tactical_brevity_code Wikipedia Brevity Page]

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively, this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate their messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

==== Definitions ====
: '''Ship''': Single aircraft.
: '''Element''': Two ships working in tandem. This is the basic combat unit.
: '''Flight''': Two elements working in tandem. (Sometimes you can have three-ship flights).
: '''Package''': Two or more flights tasked with accomplishing a single mission.

====Types of radio messages====
There are two (main) kinds of messages: ''Advisories'' and ''directives''. 
An '''advisory''' is a message where you state what you are doing or intending to do. It is particularly important to remember if you're a flight lead or element lead to let other flights know when you're being engaged, or if you're engaging someone, or if you're running away from something.
Advisories do not need to be acknowledged, although they can be.

Examples:
* The flight lead can call out his altitude and speed when climbing from take-off to let his flight know if they’re going to fast or lagging behind.
* Giving an ''"IN"'' call when attacking a ground target.
* Giving an ''"Engaged defensive"'' call to the rest of the package if your flight finds itself engaged by enemy fighters.

A '''directive''' is an order to perform some action. They’re usually given by element-, flight-, or package leaders to their subordinates. However others can also give directives depending on the circumstances. E.g. you are supporting your element leader in a dogfight and you see a bandit about to fire on him, you would then direct your leader to "BREAK" in concert with you trying to gain a position to attack the bandit.

==== Responding to communications ====

'''Within the flight (VHF)''' when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Viper 1-4 unable, engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

'''Between flights (UHF)''', the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

Whenever you start a message not directed toward others you start with your callsign. On package comms where everyone will hear you, you use your full callsign.

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO give an "Engaged offensive" call followed by the BRAA or bullseye of the target when in a dogfight.

DO remain calm and speak clearly.

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture)

DON'T use "over" or "out".

DON'T use "break" to signal a pause. Break is a brevity word to perform a rapid turn.

''These are not the same as the [[:Category:Official Documentation|UO SOPs]] or the [http://forums.unitedoperations.net/index.php/topic/15344-uoaf-sops UOAF SOPs], which are the rules of the community. You've read [[:Category:Official Documentation|the rules]], right?''

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''second''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"Panther 1, '''Lobo 2''' engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are committing to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"Panther 1, '''Lobo 2'''"}}

Indicating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{red|"Lobo 2, '''Panther 1'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| AS FRAGGED
| Unit or element will be performing exactly as stated by the air tasking order (ATO).
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BANZAI
| Informative or directive call to execute launch-and-decide tactics.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| (system) BENT
| System indicated is inoperative.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BIRD
| Friendly surface-to-air missile (SAM).
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| BLOW THROUGH
| Directive or informative call that indicates aircraft will continue straight ahead at the merge and not become anchored with target/targets.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BOGEY DOPE
| Request for target information as requested or closest group in BRAA (with appropriate fill-ins).
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUGOUT (with direction)
| Separation from that particular engagement/attack/operation; no intent to reengage/return.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CEASE FIRE
| Discontinue firing/do not open fire. Complete intercept if weapons are in flight. Continue to track.
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CHERUBS || Hundreds of feet above ground level. (“CHERUBS 3” means 300 feet AGL)<ref>CHERUBS '''only''' means altitude above ground level, and is not to be used as a general codeword for hundreds of feet. Saying "ANGELS 20 CHERUBS 3" when meaning 20300 feet MSL is not allowed.</ref>
|-
| CHICKS
| Friendly aircraft.
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTINUE
| Continue present maneuver; does not imply a change in clearance to engage or expend ordnance.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| COVER
| Directive/informative call to assume a supporting position that will allow engagement of a specified track or threat to the flight if required.
|-
| CRANK [left/right] || Turn as far as possible left or right while keeping the target on your radar
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| DROP KICK
| Informative to the flight that an intentional deviation from any briefed action is being made.
|-
| DROPPING
| Informative call that a fighter has discontinued targeting responsibility.
|-
| ENGAGED
| Informative call used to establish engaged and support roles in the visual arena.
|-
| EXTEND (with direction)
| Short-term maneuver to gain energy, distance, or separation normally with the intent of reengaging.
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FAST
| Target speed is estimated to be 600 to 900 knots ground speed/Mach 1 to 1.5.
|-
| FEET WET/DRY
| Flying over water/land.
|-
| FENCE IN || Directive to prepare your aircraft for battle. See UOAF SOP Section
|-
| FLASH (system)
| Temporarily activate specified system for identification purposes (e.g., IFF, afterburner, flare, or chaff).
|-
| FLOW [direction] || Turn to and fly in the designated heading
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HIGH
| Target is between 25,000 and 40,000 feet MSL.
|-
| HOLDING HANDS
| Aircraft in visual formation
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOSTILE
| A contact identified as an enemy upon which clearance to fire is authorized IAW the theater rules of engagement (ROE).
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| IN
| Informative call indicating a turn toward a known threat, may imply a request for information.
|-
| JINK
| Directive call to perform an unpredictable maneuver to negate a gun tracking solution.
|-
| JOKER || Prebriefed fuel remaining when you should start heading home
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| KILL
| Directive call to fire on designated target.
|-
| KNOCK-IT-OFF
| Directive call to cease air combat maneuvers/attacks/activities.
|-
| LEAN (with direction)
| Directive/informative call to maneuver in a direction to avoid the threat.
|-
| LOCKED (with position)
| Radar lock-on; correct targeting is not assumed.
|-
| LOW
| Below 10,000 feet MSL
|-
| MAGNUM || With direction and type of target. Anti-radiation weapon launched
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. <ref>"Ducks on a pond" is also used in BMS (and the best RTB call).</ref>
|-
| MARKING
| Friendly aircraft leaving contrails.
|-
| MARSHAL(ING)
| Establish(ed) at a specific point.
|-
| MERGE(D)
| Informative call that friendlies and targets have arrived in the same visual arena.
|-
| MUD || RWR indication of SAM or AAA radar
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO FACTOR || Not a threat
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCH(ING)
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OFF (with direction)
| Informative call indicating attack is terminated and maneuvering to the indicated direction.
|-
| OFFSET (with direction)
| Informative call indicating maneuver in a specified direction with reference to the target.
|-
| OUT
| Informative call indicating a turn to a cold aspect relative to the known threat.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PADLOCKED
| Informative call indicating aircrew cannot take eyes off an aircraft or ground target without risk of losing tally/visual.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PINCE
| Threat maneuvering for a bracket attack.
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| POP
| Starting climb for A/S attack OR Max performance climb out of low-altitude structure.
|-
| POSIT
| Request for friendly position; response in terms of a geographic landmark or off a common reference point.
|-
| PRESS
| Directive call to continue the attack; mutual support will be maintained. Supportive role will be assumed by the speaker.
|-
| PUMP
| A briefed maneuver to low aspect to stop closure on the threat or geographical boundary with the intent to reengage. Will be used to initiate a Grinder tactic.
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RESET
| Proceed to a pre-briefed position or area of operation (AO).
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER''' (type with direction)
| Informative call of an RWR indication of SAM launch.
|-
| SKIP IT
| Veto of fighter commit call, usually followed with further directions.
|-
| SKOSH
| Aircraft is out of or unable to employ active radar missiles.
|-
| SLICE / SLICEBACK (LEFT/RIGHT)
| Directive call to perform a high-G descending turn in the stated direction, usually 180-degree turn.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| STRIPPED
| Informative call that aircraft is out of briefed formation
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VAMPIRE
| Hostile antiship missile launch.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WEEDS
| Indicates that aircraft are operating close to the surface.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}

=Final Reminders=

For a "complete" list of brevity terms, see '''OPERATIONAL BREVITY WORDS, DEFINITIONS, AND COUNTERAIR (AFTTP 3-1.1).pdf''' in the ''/docs/Operational Manuals/'' folder of your Falcon install.
:
==== ABCs ====
When communicating, especially in a combat situation, remember the ABCs of radio protocol:

'''Accuracy'''

Make sure what you are saying is accurate and think about what you need to say before you broadcast.

'''Brevity'''

Be brief and use brevity terms as much as possible. In a hectic situation there’s a lot of information that needs to be transmitted and processed, and only one person can talk on the radio at a time.

'''Clarity'''

Speak clearly and slowly enough that other people can understand you. The last part is particularly important if you’re not a native english speaker or speaking to a non-native speaker.
{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-19T10:38:31Z

Lexi: /* Learning Objectives */ Learning objectives

[[File:F16-pilot.jpg||none|500px|left|]] 

== Learning Objectives ==
#Understand the correct syntax used when communicating between fighter aircraft (both interflight and intraflight).
#Learn the important brevity code words. 

=== Learning Files ===
* [http://www.krauselabs.net/dump/Us_Marine_Corps---Multi_Service_Brevity_Codes_Mcrp_3-25B.pdf MULTI-SERVICE BREVITY CODES PDF]
*[https://en.wikipedia.org/wiki/Multiservice_tactical_brevity_code Wikipedia Brevity Page]

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively, this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate their messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

==== Definitions ====
: '''Ship''': Single aircraft.
: '''Element''': Two ships working in tandem. This is the basic combat unit.
: '''Flight''': Two elements working in tandem. (Sometimes you can have three-ship flights).
: '''Package''': Two or more flights tasked with accomplishing a single mission.

====Types of radio messages====
There are two (main) kinds of messages: ''Advisories'' and ''directives''. 
An '''advisory''' is a message where you state what you are doing or intending to do. It is particularly important to remember if you're a flight lead or element lead to let other flights know when you're being engaged, or if you're engaging someone, or if you're running away from something.
Advisories do not need to be acknowledged, although they can be.

Examples:
* The flight lead can call out his altitude and speed when climbing from take-off to let his flight know if they’re going to fast or lagging behind.
* Giving an ''"IN"'' call when attacking a ground target.
* Giving an ''"Engaged defensive"'' call to the rest of the package if your flight finds itself engaged by enemy fighters.

A '''directive''' is an order to perform some action. They’re usually given by element-, flight-, or package leaders to their subordinates. However others can also give directives depending on the circumstances. E.g. you are supporting your element leader in a dogfight and you see a bandit about to fire on him, you would then direct your leader to "BREAK" in concert with you trying to gain a position to attack the bandit.

==== Responding to communications ====

'''Within the flight (VHF)''' when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Viper 1-4 unable, engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

'''Between flights (UHF)''', the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

Whenever you start a message not directed toward others you start with your callsign. On package comms where everyone will hear you, you use your full callsign.

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO give an "Engaged offensive" call followed by the BRAA or bullseye of the target when in a dogfight.

DO remain calm and speak clearly.

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture)

DON'T use "over" or "out".

DON'T use "break" to signal a pause. Break is a brevity word to perform a rapid turn.

''These are not the same as the [[:Category:Official Documentation|UO SOPs]] or the [http://forums.unitedoperations.net/index.php/topic/15344-uoaf-sops UOAF SOPs], which are the rules of the community. You've read [[:Category:Official Documentation|the rules]], right?''

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''second''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"Panther 1, '''Lobo 2''' engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are committing to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"Panther 1, '''Lobo 2'''"}}

Indicating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{red|"Lobo 2, '''Panther 1'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| AS FRAGGED
| Unit or element will be performing exactly as stated by the air tasking order (ATO).
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BANZAI
| Informative or directive call to execute launch-and-decide tactics.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| (system) BENT
| System indicated is inoperative.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BIRD
| Friendly surface-to-air missile (SAM).
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| BLOW THROUGH
| Directive or informative call that indicates aircraft will continue straight ahead at the merge and not become anchored with target/targets.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BOGEY DOPE
| Request for target information as requested or closest group in BRAA (with appropriate fill-ins).
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUGOUT (with direction)
| Separation from that particular engagement/attack/operation; no intent to reengage/return.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CEASE FIRE
| Discontinue firing/do not open fire. Complete intercept if weapons are in flight. Continue to track.
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CHERUBS || Hundreds of feet above ground level. (“CHERUBS 3” means 300 feet AGL)<ref>CHERUBS '''only''' means altitude above ground level, and is not to be used as a general codeword for hundreds of feet. Saying "ANGELS 20 CHERUBS 3" when meaning 20300 feet MSL is not allowed.</ref>
|-
| CHICKS
| Friendly aircraft.
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTINUE
| Continue present maneuver; does not imply a change in clearance to engage or expend ordnance.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| COVER
| Directive/informative call to assume a supporting position that will allow engagement of a specified track or threat to the flight if required.
|-
| CRANK [left/right] || Turn as far as possible left or right while keeping the target on your radar
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| DROP KICK
| Informative to the flight that an intentional deviation from any briefed action is being made.
|-
| DROPPING
| Informative call that a fighter has discontinued targeting responsibility.
|-
| ENGAGED
| Informative call used to establish engaged and support roles in the visual arena.
|-
| EXTEND (with direction)
| Short-term maneuver to gain energy, distance, or separation normally with the intent of reengaging.
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FAST
| Target speed is estimated to be 600 to 900 knots ground speed/Mach 1 to 1.5.
|-
| FEET WET/DRY
| Flying over water/land.
|-
| FENCE IN || Directive to prepare your aircraft for battle. See UOAF SOP Section
|-
| FLASH (system)
| Temporarily activate specified system for identification purposes (e.g., IFF, afterburner, flare, or chaff).
|-
| FLOW [direction] || Turn to and fly in the designated heading
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HIGH
| Target is between 25,000 and 40,000 feet MSL.
|-
| HOLDING HANDS
| Aircraft in visual formation
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOSTILE
| A contact identified as an enemy upon which clearance to fire is authorized IAW the theater rules of engagement (ROE).
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| IN
| Informative call indicating a turn toward a known threat, may imply a request for information.
|-
| JINK
| Directive call to perform an unpredictable maneuver to negate a gun tracking solution.
|-
| JOKER || Prebriefed fuel remaining when you should start heading home
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| KILL
| Directive call to fire on designated target.
|-
| KNOCK-IT-OFF
| Directive call to cease air combat maneuvers/attacks/activities.
|-
| LEAN (with direction)
| Directive/informative call to maneuver in a direction to avoid the threat.
|-
| LOCKED (with position)
| Radar lock-on; correct targeting is not assumed.
|-
| LOW
| Below 10,000 feet MSL
|-
| MAGNUM || With direction and type of target. Anti-radiation weapon launched
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. <ref>"Ducks on a pond" is also used in BMS (and the best RTB call).</ref>
|-
| MARKING
| Friendly aircraft leaving contrails.
|-
| MARSHAL(ING)
| Establish(ed) at a specific point.
|-
| MERGE(D)
| Informative call that friendlies and targets have arrived in the same visual arena.
|-
| MUD || RWR indication of SAM or AAA radar
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO FACTOR || Not a threat
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCH(ING)
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OFF (with direction)
| Informative call indicating attack is terminated and maneuvering to the indicated direction.
|-
| OFFSET (with direction)
| Informative call indicating maneuver in a specified direction with reference to the target.
|-
| OUT
| Informative call indicating a turn to a cold aspect relative to the known threat.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PADLOCKED
| Informative call indicating aircrew cannot take eyes off an aircraft or ground target without risk of losing tally/visual.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PINCE
| Threat maneuvering for a bracket attack.
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| POP
| Starting climb for A/S attack OR Max performance climb out of low-altitude structure.
|-
| POSIT
| Request for friendly position; response in terms of a geographic landmark or off a common reference point.
|-
| PRESS
| Directive call to continue the attack; mutual support will be maintained. Supportive role will be assumed by the speaker.
|-
| PUMP
| A briefed maneuver to low aspect to stop closure on the threat or geographical boundary with the intent to reengage. Will be used to initiate a Grinder tactic.
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RESET
| Proceed to a pre-briefed position or area of operation (AO).
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER''' (type with direction)
| Informative call of an RWR indication of SAM launch.
|-
| SKIP IT
| Veto of fighter commit call, usually followed with further directions.
|-
| SKOSH
| Aircraft is out of or unable to employ active radar missiles.
|-
| SLICE / SLICEBACK (LEFT/RIGHT)
| Directive call to perform a high-G descending turn in the stated direction, usually 180-degree turn.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| STRIPPED
| Informative call that aircraft is out of briefed formation
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VAMPIRE
| Hostile antiship missile launch.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WEEDS
| Indicates that aircraft are operating close to the surface.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}

=Final Reminders=

For a "complete" list of brevity terms, see '''OPERATIONAL BREVITY WORDS, DEFINITIONS, AND COUNTERAIR (AFTTP 3-1.1).pdf''' in the ''/docs/Operational Manuals/'' folder of your Falcon install.
:
==== ABCs ====
When communicating, especially in a combat situation, remember the ABCs of radio protocol:

'''Accuracy'''

Make sure what you are saying is accurate and think about what you need to say before you broadcast.

'''Brevity'''

Be brief and use brevity terms as much as possible. In a hectic situation there’s a lot of information that needs to be transmitted and processed, and only one person can talk on the radio at a time.

'''Clarity'''

Speak clearly and slowly enough that other people can understand you. The last part is particularly important if you’re not a native english speaker or speaking to a non-native speaker.
{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-19T10:36:41Z

Lexi: /* Learning Files */ Fixing messed up HTML link, whoops.

[[File:F16-pilot.jpg||none|500px|left|]] 

== Learning Objectives ==
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
* [http://www.krauselabs.net/dump/Us_Marine_Corps---Multi_Service_Brevity_Codes_Mcrp_3-25B.pdf MULTI-SERVICE BREVITY CODES PDF]
*[https://en.wikipedia.org/wiki/Multiservice_tactical_brevity_code Wikipedia Brevity Page]

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively, this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate their messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

==== Definitions ====
: '''Ship''': Single aircraft.
: '''Element''': Two ships working in tandem. This is the basic combat unit.
: '''Flight''': Two elements working in tandem. (Sometimes you can have three-ship flights).
: '''Package''': Two or more flights tasked with accomplishing a single mission.

====Types of radio messages====
There are two (main) kinds of messages: ''Advisories'' and ''directives''. 
An '''advisory''' is a message where you state what you are doing or intending to do. It is particularly important to remember if you're a flight lead or element lead to let other flights know when you're being engaged, or if you're engaging someone, or if you're running away from something.
Advisories do not need to be acknowledged, although they can be.

Examples:
* The flight lead can call out his altitude and speed when climbing from take-off to let his flight know if they’re going to fast or lagging behind.
* Giving an ''"IN"'' call when attacking a ground target.
* Giving an ''"Engaged defensive"'' call to the rest of the package if your flight finds itself engaged by enemy fighters.

A '''directive''' is an order to perform some action. They’re usually given by element-, flight-, or package leaders to their subordinates. However others can also give directives depending on the circumstances. E.g. you are supporting your element leader in a dogfight and you see a bandit about to fire on him, you would then direct your leader to "BREAK" in concert with you trying to gain a position to attack the bandit.

==== Responding to communications ====

'''Within the flight (VHF)''' when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Viper 1-4 unable, engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

'''Between flights (UHF)''', the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

Whenever you start a message not directed toward others you start with your callsign. On package comms where everyone will hear you, you use your full callsign.

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO give an "Engaged offensive" call followed by the BRAA or bullseye of the target when in a dogfight.

DO remain calm and speak clearly.

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture)

DON'T use "over" or "out".

DON'T use "break" to signal a pause. Break is a brevity word to perform a rapid turn.

''These are not the same as the [[:Category:Official Documentation|UO SOPs]] or the [http://forums.unitedoperations.net/index.php/topic/15344-uoaf-sops UOAF SOPs], which are the rules of the community. You've read [[:Category:Official Documentation|the rules]], right?''

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''second''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"Panther 1, '''Lobo 2''' engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are committing to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"Panther 1, '''Lobo 2'''"}}

Indicating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{red|"Lobo 2, '''Panther 1'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| AS FRAGGED
| Unit or element will be performing exactly as stated by the air tasking order (ATO).
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BANZAI
| Informative or directive call to execute launch-and-decide tactics.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| (system) BENT
| System indicated is inoperative.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BIRD
| Friendly surface-to-air missile (SAM).
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| BLOW THROUGH
| Directive or informative call that indicates aircraft will continue straight ahead at the merge and not become anchored with target/targets.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BOGEY DOPE
| Request for target information as requested or closest group in BRAA (with appropriate fill-ins).
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUGOUT (with direction)
| Separation from that particular engagement/attack/operation; no intent to reengage/return.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CEASE FIRE
| Discontinue firing/do not open fire. Complete intercept if weapons are in flight. Continue to track.
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CHERUBS || Hundreds of feet above ground level. (“CHERUBS 3” means 300 feet AGL)<ref>CHERUBS '''only''' means altitude above ground level, and is not to be used as a general codeword for hundreds of feet. Saying "ANGELS 20 CHERUBS 3" when meaning 20300 feet MSL is not allowed.</ref>
|-
| CHICKS
| Friendly aircraft.
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTINUE
| Continue present maneuver; does not imply a change in clearance to engage or expend ordnance.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| COVER
| Directive/informative call to assume a supporting position that will allow engagement of a specified track or threat to the flight if required.
|-
| CRANK [left/right] || Turn as far as possible left or right while keeping the target on your radar
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| DROP KICK
| Informative to the flight that an intentional deviation from any briefed action is being made.
|-
| DROPPING
| Informative call that a fighter has discontinued targeting responsibility.
|-
| ENGAGED
| Informative call used to establish engaged and support roles in the visual arena.
|-
| EXTEND (with direction)
| Short-term maneuver to gain energy, distance, or separation normally with the intent of reengaging.
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FAST
| Target speed is estimated to be 600 to 900 knots ground speed/Mach 1 to 1.5.
|-
| FEET WET/DRY
| Flying over water/land.
|-
| FENCE IN || Directive to prepare your aircraft for battle. See UOAF SOP Section
|-
| FLASH (system)
| Temporarily activate specified system for identification purposes (e.g., IFF, afterburner, flare, or chaff).
|-
| FLOW [direction] || Turn to and fly in the designated heading
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HIGH
| Target is between 25,000 and 40,000 feet MSL.
|-
| HOLDING HANDS
| Aircraft in visual formation
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOSTILE
| A contact identified as an enemy upon which clearance to fire is authorized IAW the theater rules of engagement (ROE).
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| IN
| Informative call indicating a turn toward a known threat, may imply a request for information.
|-
| JINK
| Directive call to perform an unpredictable maneuver to negate a gun tracking solution.
|-
| JOKER || Prebriefed fuel remaining when you should start heading home
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| KILL
| Directive call to fire on designated target.
|-
| KNOCK-IT-OFF
| Directive call to cease air combat maneuvers/attacks/activities.
|-
| LEAN (with direction)
| Directive/informative call to maneuver in a direction to avoid the threat.
|-
| LOCKED (with position)
| Radar lock-on; correct targeting is not assumed.
|-
| LOW
| Below 10,000 feet MSL
|-
| MAGNUM || With direction and type of target. Anti-radiation weapon launched
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. <ref>"Ducks on a pond" is also used in BMS (and the best RTB call).</ref>
|-
| MARKING
| Friendly aircraft leaving contrails.
|-
| MARSHAL(ING)
| Establish(ed) at a specific point.
|-
| MERGE(D)
| Informative call that friendlies and targets have arrived in the same visual arena.
|-
| MUD || RWR indication of SAM or AAA radar
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO FACTOR || Not a threat
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCH(ING)
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OFF (with direction)
| Informative call indicating attack is terminated and maneuvering to the indicated direction.
|-
| OFFSET (with direction)
| Informative call indicating maneuver in a specified direction with reference to the target.
|-
| OUT
| Informative call indicating a turn to a cold aspect relative to the known threat.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PADLOCKED
| Informative call indicating aircrew cannot take eyes off an aircraft or ground target without risk of losing tally/visual.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PINCE
| Threat maneuvering for a bracket attack.
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| POP
| Starting climb for A/S attack OR Max performance climb out of low-altitude structure.
|-
| POSIT
| Request for friendly position; response in terms of a geographic landmark or off a common reference point.
|-
| PRESS
| Directive call to continue the attack; mutual support will be maintained. Supportive role will be assumed by the speaker.
|-
| PUMP
| A briefed maneuver to low aspect to stop closure on the threat or geographical boundary with the intent to reengage. Will be used to initiate a Grinder tactic.
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RESET
| Proceed to a pre-briefed position or area of operation (AO).
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER''' (type with direction)
| Informative call of an RWR indication of SAM launch.
|-
| SKIP IT
| Veto of fighter commit call, usually followed with further directions.
|-
| SKOSH
| Aircraft is out of or unable to employ active radar missiles.
|-
| SLICE / SLICEBACK (LEFT/RIGHT)
| Directive call to perform a high-G descending turn in the stated direction, usually 180-degree turn.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| STRIPPED
| Informative call that aircraft is out of briefed formation
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VAMPIRE
| Hostile antiship missile launch.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WEEDS
| Indicates that aircraft are operating close to the surface.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}

=Final Reminders=

For a "complete" list of brevity terms, see '''OPERATIONAL BREVITY WORDS, DEFINITIONS, AND COUNTERAIR (AFTTP 3-1.1).pdf''' in the ''/docs/Operational Manuals/'' folder of your Falcon install.
:
==== ABCs ====
When communicating, especially in a combat situation, remember the ABCs of radio protocol:

'''Accuracy'''

Make sure what you are saying is accurate and think about what you need to say before you broadcast.

'''Brevity'''

Be brief and use brevity terms as much as possible. In a hectic situation there’s a lot of information that needs to be transmitted and processed, and only one person can talk on the radio at a time.

'''Clarity'''

Speak clearly and slowly enough that other people can understand you. The last part is particularly important if you’re not a native english speaker or speaking to a non-native speaker.
{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-19T10:35:59Z

Lexi: /* Learning Objectives */ Link change

[[File:F16-pilot.jpg||none|500px|left|]] 

== Learning Objectives ==
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
* [http://www.krauselabs.net/dump/Us_Marine_Corps---Multi_Service_Brevity_Codes_Mcrp_3-25B.pdf MULTI-SERVICE BREVITY CODES ]
*[https://en.wikipedia.org/wiki/Multiservice_tactical_brevity_code]

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively, this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate their messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

==== Definitions ====
: '''Ship''': Single aircraft.
: '''Element''': Two ships working in tandem. This is the basic combat unit.
: '''Flight''': Two elements working in tandem. (Sometimes you can have three-ship flights).
: '''Package''': Two or more flights tasked with accomplishing a single mission.

====Types of radio messages====
There are two (main) kinds of messages: ''Advisories'' and ''directives''. 
An '''advisory''' is a message where you state what you are doing or intending to do. It is particularly important to remember if you're a flight lead or element lead to let other flights know when you're being engaged, or if you're engaging someone, or if you're running away from something.
Advisories do not need to be acknowledged, although they can be.

Examples:
* The flight lead can call out his altitude and speed when climbing from take-off to let his flight know if they’re going to fast or lagging behind.
* Giving an ''"IN"'' call when attacking a ground target.
* Giving an ''"Engaged defensive"'' call to the rest of the package if your flight finds itself engaged by enemy fighters.

A '''directive''' is an order to perform some action. They’re usually given by element-, flight-, or package leaders to their subordinates. However others can also give directives depending on the circumstances. E.g. you are supporting your element leader in a dogfight and you see a bandit about to fire on him, you would then direct your leader to "BREAK" in concert with you trying to gain a position to attack the bandit.

==== Responding to communications ====

'''Within the flight (VHF)''' when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Viper 1-4 unable, engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

'''Between flights (UHF)''', the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

Whenever you start a message not directed toward others you start with your callsign. On package comms where everyone will hear you, you use your full callsign.

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO give an "Engaged offensive" call followed by the BRAA or bullseye of the target when in a dogfight.

DO remain calm and speak clearly.

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture)

DON'T use "over" or "out".

DON'T use "break" to signal a pause. Break is a brevity word to perform a rapid turn.

''These are not the same as the [[:Category:Official Documentation|UO SOPs]] or the [http://forums.unitedoperations.net/index.php/topic/15344-uoaf-sops UOAF SOPs], which are the rules of the community. You've read [[:Category:Official Documentation|the rules]], right?''

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''second''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"Panther 1, '''Lobo 2''' engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are committing to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"Panther 1, '''Lobo 2'''"}}

Indicating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{red|"Lobo 2, '''Panther 1'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| AS FRAGGED
| Unit or element will be performing exactly as stated by the air tasking order (ATO).
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BANZAI
| Informative or directive call to execute launch-and-decide tactics.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| (system) BENT
| System indicated is inoperative.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BIRD
| Friendly surface-to-air missile (SAM).
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| BLOW THROUGH
| Directive or informative call that indicates aircraft will continue straight ahead at the merge and not become anchored with target/targets.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BOGEY DOPE
| Request for target information as requested or closest group in BRAA (with appropriate fill-ins).
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUGOUT (with direction)
| Separation from that particular engagement/attack/operation; no intent to reengage/return.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CEASE FIRE
| Discontinue firing/do not open fire. Complete intercept if weapons are in flight. Continue to track.
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CHERUBS || Hundreds of feet above ground level. (“CHERUBS 3” means 300 feet AGL)<ref>CHERUBS '''only''' means altitude above ground level, and is not to be used as a general codeword for hundreds of feet. Saying "ANGELS 20 CHERUBS 3" when meaning 20300 feet MSL is not allowed.</ref>
|-
| CHICKS
| Friendly aircraft.
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTINUE
| Continue present maneuver; does not imply a change in clearance to engage or expend ordnance.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| COVER
| Directive/informative call to assume a supporting position that will allow engagement of a specified track or threat to the flight if required.
|-
| CRANK [left/right] || Turn as far as possible left or right while keeping the target on your radar
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| DROP KICK
| Informative to the flight that an intentional deviation from any briefed action is being made.
|-
| DROPPING
| Informative call that a fighter has discontinued targeting responsibility.
|-
| ENGAGED
| Informative call used to establish engaged and support roles in the visual arena.
|-
| EXTEND (with direction)
| Short-term maneuver to gain energy, distance, or separation normally with the intent of reengaging.
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FAST
| Target speed is estimated to be 600 to 900 knots ground speed/Mach 1 to 1.5.
|-
| FEET WET/DRY
| Flying over water/land.
|-
| FENCE IN || Directive to prepare your aircraft for battle. See UOAF SOP Section
|-
| FLASH (system)
| Temporarily activate specified system for identification purposes (e.g., IFF, afterburner, flare, or chaff).
|-
| FLOW [direction] || Turn to and fly in the designated heading
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HIGH
| Target is between 25,000 and 40,000 feet MSL.
|-
| HOLDING HANDS
| Aircraft in visual formation
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOSTILE
| A contact identified as an enemy upon which clearance to fire is authorized IAW the theater rules of engagement (ROE).
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| IN
| Informative call indicating a turn toward a known threat, may imply a request for information.
|-
| JINK
| Directive call to perform an unpredictable maneuver to negate a gun tracking solution.
|-
| JOKER || Prebriefed fuel remaining when you should start heading home
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| KILL
| Directive call to fire on designated target.
|-
| KNOCK-IT-OFF
| Directive call to cease air combat maneuvers/attacks/activities.
|-
| LEAN (with direction)
| Directive/informative call to maneuver in a direction to avoid the threat.
|-
| LOCKED (with position)
| Radar lock-on; correct targeting is not assumed.
|-
| LOW
| Below 10,000 feet MSL
|-
| MAGNUM || With direction and type of target. Anti-radiation weapon launched
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. <ref>"Ducks on a pond" is also used in BMS (and the best RTB call).</ref>
|-
| MARKING
| Friendly aircraft leaving contrails.
|-
| MARSHAL(ING)
| Establish(ed) at a specific point.
|-
| MERGE(D)
| Informative call that friendlies and targets have arrived in the same visual arena.
|-
| MUD || RWR indication of SAM or AAA radar
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO FACTOR || Not a threat
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCH(ING)
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OFF (with direction)
| Informative call indicating attack is terminated and maneuvering to the indicated direction.
|-
| OFFSET (with direction)
| Informative call indicating maneuver in a specified direction with reference to the target.
|-
| OUT
| Informative call indicating a turn to a cold aspect relative to the known threat.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PADLOCKED
| Informative call indicating aircrew cannot take eyes off an aircraft or ground target without risk of losing tally/visual.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PINCE
| Threat maneuvering for a bracket attack.
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| POP
| Starting climb for A/S attack OR Max performance climb out of low-altitude structure.
|-
| POSIT
| Request for friendly position; response in terms of a geographic landmark or off a common reference point.
|-
| PRESS
| Directive call to continue the attack; mutual support will be maintained. Supportive role will be assumed by the speaker.
|-
| PUMP
| A briefed maneuver to low aspect to stop closure on the threat or geographical boundary with the intent to reengage. Will be used to initiate a Grinder tactic.
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RESET
| Proceed to a pre-briefed position or area of operation (AO).
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER''' (type with direction)
| Informative call of an RWR indication of SAM launch.
|-
| SKIP IT
| Veto of fighter commit call, usually followed with further directions.
|-
| SKOSH
| Aircraft is out of or unable to employ active radar missiles.
|-
| SLICE / SLICEBACK (LEFT/RIGHT)
| Directive call to perform a high-G descending turn in the stated direction, usually 180-degree turn.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| STRIPPED
| Informative call that aircraft is out of briefed formation
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VAMPIRE
| Hostile antiship missile launch.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WEEDS
| Indicates that aircraft are operating close to the surface.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}

=Final Reminders=

For a "complete" list of brevity terms, see '''OPERATIONAL BREVITY WORDS, DEFINITIONS, AND COUNTERAIR (AFTTP 3-1.1).pdf''' in the ''/docs/Operational Manuals/'' folder of your Falcon install.
:
==== ABCs ====
When communicating, especially in a combat situation, remember the ABCs of radio protocol:

'''Accuracy'''

Make sure what you are saying is accurate and think about what you need to say before you broadcast.

'''Brevity'''

Be brief and use brevity terms as much as possible. In a hectic situation there’s a lot of information that needs to be transmitted and processed, and only one person can talk on the radio at a time.

'''Clarity'''

Speak clearly and slowly enough that other people can understand you. The last part is particularly important if you’re not a native english speaker or speaking to a non-native speaker.
{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-19T10:32:21Z

Lexi: Reorganisation

[[File:F16-pilot.jpg||none|500px|left|]] 

== Learning Objectives ==
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
* [http://www.krauselabs.net/dump/Us_Marine_Corps---Multi_Service_Brevity_Codes_Mcrp_3-25B.pdf MULTI-SERVICE BREVITY CODES ]
*[https://en.wikipedia.org/wiki/Brevity_code Brevity_code]

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively, this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate their messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

==== Definitions ====
: '''Ship''': Single aircraft.
: '''Element''': Two ships working in tandem. This is the basic combat unit.
: '''Flight''': Two elements working in tandem. (Sometimes you can have three-ship flights).
: '''Package''': Two or more flights tasked with accomplishing a single mission.

====Types of radio messages====
There are two (main) kinds of messages: ''Advisories'' and ''directives''. 
An '''advisory''' is a message where you state what you are doing or intending to do. It is particularly important to remember if you're a flight lead or element lead to let other flights know when you're being engaged, or if you're engaging someone, or if you're running away from something.
Advisories do not need to be acknowledged, although they can be.

Examples:
* The flight lead can call out his altitude and speed when climbing from take-off to let his flight know if they’re going to fast or lagging behind.
* Giving an ''"IN"'' call when attacking a ground target.
* Giving an ''"Engaged defensive"'' call to the rest of the package if your flight finds itself engaged by enemy fighters.

A '''directive''' is an order to perform some action. They’re usually given by element-, flight-, or package leaders to their subordinates. However others can also give directives depending on the circumstances. E.g. you are supporting your element leader in a dogfight and you see a bandit about to fire on him, you would then direct your leader to "BREAK" in concert with you trying to gain a position to attack the bandit.

==== Responding to communications ====

'''Within the flight (VHF)''' when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Viper 1-4 unable, engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

'''Between flights (UHF)''', the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

Whenever you start a message not directed toward others you start with your callsign. On package comms where everyone will hear you, you use your full callsign.

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO give an "Engaged offensive" call followed by the BRAA or bullseye of the target when in a dogfight.

DO remain calm and speak clearly.

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture)

DON'T use "over" or "out".

DON'T use "break" to signal a pause. Break is a brevity word to perform a rapid turn.

''These are not the same as the [[:Category:Official Documentation|UO SOPs]] or the [http://forums.unitedoperations.net/index.php/topic/15344-uoaf-sops UOAF SOPs], which are the rules of the community. You've read [[:Category:Official Documentation|the rules]], right?''

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''second''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"Panther 1, '''Lobo 2''' engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are committing to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"Panther 1, '''Lobo 2'''"}}

Indicating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{red|"Lobo 2, '''Panther 1'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| AS FRAGGED
| Unit or element will be performing exactly as stated by the air tasking order (ATO).
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BANZAI
| Informative or directive call to execute launch-and-decide tactics.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| (system) BENT
| System indicated is inoperative.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BIRD
| Friendly surface-to-air missile (SAM).
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| BLOW THROUGH
| Directive or informative call that indicates aircraft will continue straight ahead at the merge and not become anchored with target/targets.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BOGEY DOPE
| Request for target information as requested or closest group in BRAA (with appropriate fill-ins).
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUGOUT (with direction)
| Separation from that particular engagement/attack/operation; no intent to reengage/return.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CEASE FIRE
| Discontinue firing/do not open fire. Complete intercept if weapons are in flight. Continue to track.
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CHERUBS || Hundreds of feet above ground level. (“CHERUBS 3” means 300 feet AGL)<ref>CHERUBS '''only''' means altitude above ground level, and is not to be used as a general codeword for hundreds of feet. Saying "ANGELS 20 CHERUBS 3" when meaning 20300 feet MSL is not allowed.</ref>
|-
| CHICKS
| Friendly aircraft.
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTINUE
| Continue present maneuver; does not imply a change in clearance to engage or expend ordnance.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| COVER
| Directive/informative call to assume a supporting position that will allow engagement of a specified track or threat to the flight if required.
|-
| CRANK [left/right] || Turn as far as possible left or right while keeping the target on your radar
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| DROP KICK
| Informative to the flight that an intentional deviation from any briefed action is being made.
|-
| DROPPING
| Informative call that a fighter has discontinued targeting responsibility.
|-
| ENGAGED
| Informative call used to establish engaged and support roles in the visual arena.
|-
| EXTEND (with direction)
| Short-term maneuver to gain energy, distance, or separation normally with the intent of reengaging.
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FAST
| Target speed is estimated to be 600 to 900 knots ground speed/Mach 1 to 1.5.
|-
| FEET WET/DRY
| Flying over water/land.
|-
| FENCE IN || Directive to prepare your aircraft for battle. See UOAF SOP Section
|-
| FLASH (system)
| Temporarily activate specified system for identification purposes (e.g., IFF, afterburner, flare, or chaff).
|-
| FLOW [direction] || Turn to and fly in the designated heading
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HIGH
| Target is between 25,000 and 40,000 feet MSL.
|-
| HOLDING HANDS
| Aircraft in visual formation
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOSTILE
| A contact identified as an enemy upon which clearance to fire is authorized IAW the theater rules of engagement (ROE).
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| IN
| Informative call indicating a turn toward a known threat, may imply a request for information.
|-
| JINK
| Directive call to perform an unpredictable maneuver to negate a gun tracking solution.
|-
| JOKER || Prebriefed fuel remaining when you should start heading home
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| KILL
| Directive call to fire on designated target.
|-
| KNOCK-IT-OFF
| Directive call to cease air combat maneuvers/attacks/activities.
|-
| LEAN (with direction)
| Directive/informative call to maneuver in a direction to avoid the threat.
|-
| LOCKED (with position)
| Radar lock-on; correct targeting is not assumed.
|-
| LOW
| Below 10,000 feet MSL
|-
| MAGNUM || With direction and type of target. Anti-radiation weapon launched
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. <ref>"Ducks on a pond" is also used in BMS (and the best RTB call).</ref>
|-
| MARKING
| Friendly aircraft leaving contrails.
|-
| MARSHAL(ING)
| Establish(ed) at a specific point.
|-
| MERGE(D)
| Informative call that friendlies and targets have arrived in the same visual arena.
|-
| MUD || RWR indication of SAM or AAA radar
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO FACTOR || Not a threat
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCH(ING)
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OFF (with direction)
| Informative call indicating attack is terminated and maneuvering to the indicated direction.
|-
| OFFSET (with direction)
| Informative call indicating maneuver in a specified direction with reference to the target.
|-
| OUT
| Informative call indicating a turn to a cold aspect relative to the known threat.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PADLOCKED
| Informative call indicating aircrew cannot take eyes off an aircraft or ground target without risk of losing tally/visual.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PINCE
| Threat maneuvering for a bracket attack.
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| POP
| Starting climb for A/S attack OR Max performance climb out of low-altitude structure.
|-
| POSIT
| Request for friendly position; response in terms of a geographic landmark or off a common reference point.
|-
| PRESS
| Directive call to continue the attack; mutual support will be maintained. Supportive role will be assumed by the speaker.
|-
| PUMP
| A briefed maneuver to low aspect to stop closure on the threat or geographical boundary with the intent to reengage. Will be used to initiate a Grinder tactic.
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RESET
| Proceed to a pre-briefed position or area of operation (AO).
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER''' (type with direction)
| Informative call of an RWR indication of SAM launch.
|-
| SKIP IT
| Veto of fighter commit call, usually followed with further directions.
|-
| SKOSH
| Aircraft is out of or unable to employ active radar missiles.
|-
| SLICE / SLICEBACK (LEFT/RIGHT)
| Directive call to perform a high-G descending turn in the stated direction, usually 180-degree turn.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| STRIPPED
| Informative call that aircraft is out of briefed formation
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VAMPIRE
| Hostile antiship missile launch.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WEEDS
| Indicates that aircraft are operating close to the surface.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}

=Final Reminders=

For a "complete" list of brevity terms, see '''OPERATIONAL BREVITY WORDS, DEFINITIONS, AND COUNTERAIR (AFTTP 3-1.1).pdf''' in the ''/docs/Operational Manuals/'' folder of your Falcon install.
:
==== ABCs ====
When communicating, especially in a combat situation, remember the ABCs of radio protocol:

'''Accuracy'''

Make sure what you are saying is accurate and think about what you need to say before you broadcast.

'''Brevity'''

Be brief and use brevity terms as much as possible. In a hectic situation there’s a lot of information that needs to be transmitted and processed, and only one person can talk on the radio at a time.

'''Clarity'''

Speak clearly and slowly enough that other people can understand you. The last part is particularly important if you’re not a native english speaker or speaking to a non-native speaker.
{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-19T10:28:26Z

Lexi: /* Responding to communications */

[[File:F16-pilot.jpg||none|500px|left|]] 

== Learning Objectives ==
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
* [http://www.krauselabs.net/dump/Us_Marine_Corps---Multi_Service_Brevity_Codes_Mcrp_3-25B.pdf MULTI-SERVICE BREVITY CODES ]
*[https://en.wikipedia.org/wiki/Brevity_code Brevity_code]

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively, this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate their messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

==== Definitions ====
: '''Ship''': Single aircraft.
: '''Element''': Two ships working in tandem. This is the basic combat unit.
: '''Flight''': Two elements working in tandem. (Sometimes you can have three-ship flights).
: '''Package''': Two or more flights tasked with accomplishing a single mission.

====Types of radio messages====
There are two (main) kinds of messages: ''Advisories'' and ''directives''. 
An '''advisory''' is a message where you state what you are doing or intending to do. It is particularly important to remember if you're a flight lead or element lead to let other flights know when you're being engaged, or if you're engaging someone, or if you're running away from something.
Advisories do not need to be acknowledged, although they can be.

Examples:
* The flight lead can call out his altitude and speed when climbing from take-off to let his flight know if they’re going to fast or lagging behind.
* Giving an ''"IN"'' call when attacking a ground target.
* Giving an ''"Engaged defensive"'' call to the rest of the package if your flight finds itself engaged by enemy fighters.

A '''directive''' is an order to perform some action. They’re usually given by element-, flight-, or package leaders to their subordinates. However others can also give directives depending on the circumstances. E.g. you are supporting your element leader in a dogfight and you see a bandit about to fire on him, you would then direct your leader to "BREAK" in concert with you trying to gain a position to attack the bandit.

== Responding to communications ==

'''Within the flight (VHF)''' when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Viper 1-4 unable, engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

'''Between flights (UHF)''', the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

Whenever you start a message not directed toward others you start with your callsign. On package comms where everyone will hear you, you use your full callsign.

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO give an "Engaged offensive" call followed by the BRAA or bullseye of the target when in a dogfight.

DO remain calm and speak clearly.

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture)

DON'T use "over" or "out".

DON'T use "break" to signal a pause. Break is a brevity word to perform a rapid turn.

''These are not the same as the [[:Category:Official Documentation|UO SOPs]] or the [http://forums.unitedoperations.net/index.php/topic/15344-uoaf-sops UOAF SOPs], which are the rules of the community. You've read [[:Category:Official Documentation|the rules]], right?''

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''second''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"Panther 1, '''Lobo 2''' engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are committing to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"Panther 1, '''Lobo 2'''"}}

Indicating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{red|"Lobo 2, '''Panther 1'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| AS FRAGGED
| Unit or element will be performing exactly as stated by the air tasking order (ATO).
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BANZAI
| Informative or directive call to execute launch-and-decide tactics.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| (system) BENT
| System indicated is inoperative.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BIRD
| Friendly surface-to-air missile (SAM).
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| BLOW THROUGH
| Directive or informative call that indicates aircraft will continue straight ahead at the merge and not become anchored with target/targets.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BOGEY DOPE
| Request for target information as requested or closest group in BRAA (with appropriate fill-ins).
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUGOUT (with direction)
| Separation from that particular engagement/attack/operation; no intent to reengage/return.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CEASE FIRE
| Discontinue firing/do not open fire. Complete intercept if weapons are in flight. Continue to track.
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CHERUBS || Hundreds of feet above ground level. (“CHERUBS 3” means 300 feet AGL)<ref>CHERUBS '''only''' means altitude above ground level, and is not to be used as a general codeword for hundreds of feet. Saying "ANGELS 20 CHERUBS 3" when meaning 20300 feet MSL is not allowed.</ref>
|-
| CHICKS
| Friendly aircraft.
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTINUE
| Continue present maneuver; does not imply a change in clearance to engage or expend ordnance.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| COVER
| Directive/informative call to assume a supporting position that will allow engagement of a specified track or threat to the flight if required.
|-
| CRANK [left/right] || Turn as far as possible left or right while keeping the target on your radar
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| DROP KICK
| Informative to the flight that an intentional deviation from any briefed action is being made.
|-
| DROPPING
| Informative call that a fighter has discontinued targeting responsibility.
|-
| ENGAGED
| Informative call used to establish engaged and support roles in the visual arena.
|-
| EXTEND (with direction)
| Short-term maneuver to gain energy, distance, or separation normally with the intent of reengaging.
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FAST
| Target speed is estimated to be 600 to 900 knots ground speed/Mach 1 to 1.5.
|-
| FEET WET/DRY
| Flying over water/land.
|-
| FENCE IN || Directive to prepare your aircraft for battle. See UOAF SOP Section
|-
| FLASH (system)
| Temporarily activate specified system for identification purposes (e.g., IFF, afterburner, flare, or chaff).
|-
| FLOW [direction] || Turn to and fly in the designated heading
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HIGH
| Target is between 25,000 and 40,000 feet MSL.
|-
| HOLDING HANDS
| Aircraft in visual formation
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOSTILE
| A contact identified as an enemy upon which clearance to fire is authorized IAW the theater rules of engagement (ROE).
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| IN
| Informative call indicating a turn toward a known threat, may imply a request for information.
|-
| JINK
| Directive call to perform an unpredictable maneuver to negate a gun tracking solution.
|-
| JOKER || Prebriefed fuel remaining when you should start heading home
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| KILL
| Directive call to fire on designated target.
|-
| KNOCK-IT-OFF
| Directive call to cease air combat maneuvers/attacks/activities.
|-
| LEAN (with direction)
| Directive/informative call to maneuver in a direction to avoid the threat.
|-
| LOCKED (with position)
| Radar lock-on; correct targeting is not assumed.
|-
| LOW
| Below 10,000 feet MSL
|-
| MAGNUM || With direction and type of target. Anti-radiation weapon launched
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. <ref>"Ducks on a pond" is also used in BMS (and the best RTB call).</ref>
|-
| MARKING
| Friendly aircraft leaving contrails.
|-
| MARSHAL(ING)
| Establish(ed) at a specific point.
|-
| MERGE(D)
| Informative call that friendlies and targets have arrived in the same visual arena.
|-
| MUD || RWR indication of SAM or AAA radar
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO FACTOR || Not a threat
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCH(ING)
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OFF (with direction)
| Informative call indicating attack is terminated and maneuvering to the indicated direction.
|-
| OFFSET (with direction)
| Informative call indicating maneuver in a specified direction with reference to the target.
|-
| OUT
| Informative call indicating a turn to a cold aspect relative to the known threat.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PADLOCKED
| Informative call indicating aircrew cannot take eyes off an aircraft or ground target without risk of losing tally/visual.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PINCE
| Threat maneuvering for a bracket attack.
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| POP
| Starting climb for A/S attack OR Max performance climb out of low-altitude structure.
|-
| POSIT
| Request for friendly position; response in terms of a geographic landmark or off a common reference point.
|-
| PRESS
| Directive call to continue the attack; mutual support will be maintained. Supportive role will be assumed by the speaker.
|-
| PUMP
| A briefed maneuver to low aspect to stop closure on the threat or geographical boundary with the intent to reengage. Will be used to initiate a Grinder tactic.
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RESET
| Proceed to a pre-briefed position or area of operation (AO).
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER''' (type with direction)
| Informative call of an RWR indication of SAM launch.
|-
| SKIP IT
| Veto of fighter commit call, usually followed with further directions.
|-
| SKOSH
| Aircraft is out of or unable to employ active radar missiles.
|-
| SLICE / SLICEBACK (LEFT/RIGHT)
| Directive call to perform a high-G descending turn in the stated direction, usually 180-degree turn.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| STRIPPED
| Informative call that aircraft is out of briefed formation
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VAMPIRE
| Hostile antiship missile launch.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WEEDS
| Indicates that aircraft are operating close to the surface.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}

=Final Reminders=

For a "complete" list of brevity terms, see '''OPERATIONAL BREVITY WORDS, DEFINITIONS, AND COUNTERAIR (AFTTP 3-1.1).pdf''' in the ''/docs/Operational Manuals/'' folder of your Falcon install.
:
==== ABCs ====
When communicating, especially in a combat situation, remember the ABCs of radio protocol:

'''Accuracy'''

Make sure what you are saying is accurate and think about what you need to say before you broadcast.

'''Brevity'''

Be brief and use brevity terms as much as possible. In a hectic situation there’s a lot of information that needs to be transmitted and processed, and only one person can talk on the radio at a time.

'''Clarity'''

Speak clearly and slowly enough that other people can understand you. The last part is particularly important if you’re not a native english speaker or speaking to a non-native speaker.
{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-19T10:19:07Z

Lexi: /* Brevity Code Masterlist */ MORE

[[File:F16-pilot.jpg||none|500px|left|]] 

== Learning Objectives ==
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
* [http://www.krauselabs.net/dump/Us_Marine_Corps---Multi_Service_Brevity_Codes_Mcrp_3-25B.pdf MULTI-SERVICE BREVITY CODES ]
*[https://en.wikipedia.org/wiki/Brevity_code Brevity_code]

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively, this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate their messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

==== Definitions ====
: '''Ship''': Single aircraft.
: '''Element''': Two ships working in tandem. This is the basic combat unit.
: '''Flight''': Two elements working in tandem. (Sometimes you can have three-ship flights).
: '''Package''': Two or more flights tasked with accomplishing a single mission.

====Types of radio messages====
There are two (main) kinds of messages: ''Advisories'' and ''directives''. 
An '''advisory''' is a message where you state what you are doing or intending to do. It is particularly important to remember if you're a flight lead or element lead to let other flights know when you're being engaged, or if you're engaging someone, or if you're running away from something.
Advisories do not need to be acknowledged, although they can be.

Examples:
* The flight lead can call out his altitude and speed when climbing from take-off to let his flight know if they’re going to fast or lagging behind.
* Giving an ''"IN"'' call when attacking a ground target.
* Giving an ''"Engaged defensive"'' call to the rest of the package if your flight finds itself engaged by enemy fighters.

A '''directive''' is an order to perform some action. They’re usually given by element-, flight-, or package leaders to their subordinates. However others can also give directives depending on the circumstances. E.g. you are supporting your element leader in a dogfight and you see a bandit about to fire on him, you would then direct your leader to "BREAK" in concert with you trying to gain a position to attack the bandit.

== Responding to communications ==

'''Within the flight (VHF)''' when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

'''Between flights (UHF)''', the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

Whenever you start a message not directed toward others you start with your callsign. On package comms where everyone will hear you, you use your full callsign.

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO give an "Engaged offensive" call followed by the BRAA or bullseye of the target when in a dogfight.

DO remain calm and speak clearly.

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture)

DON'T use "over" or "out".

DON'T use "break" to signal a pause. Break is a brevity word to perform a rapid turn.

''These are not the same as the [[:Category:Official Documentation|UO SOPs]] or the [http://forums.unitedoperations.net/index.php/topic/15344-uoaf-sops UOAF SOPs], which are the rules of the community. You've read [[:Category:Official Documentation|the rules]], right?''

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''second''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"Panther 1, '''Lobo 2''' engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are committing to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"Panther 1, '''Lobo 2'''"}}

Indicating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{red|"Lobo 2, '''Panther 1'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| AS FRAGGED
| Unit or element will be performing exactly as stated by the air tasking order (ATO).
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BANZAI
| Informative or directive call to execute launch-and-decide tactics.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| (system) BENT
| System indicated is inoperative.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BIRD
| Friendly surface-to-air missile (SAM).
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| BLOW THROUGH
| Directive or informative call that indicates aircraft will continue straight ahead at the merge and not become anchored with target/targets.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BOGEY DOPE
| Request for target information as requested or closest group in BRAA (with appropriate fill-ins).
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUGOUT (with direction)
| Separation from that particular engagement/attack/operation; no intent to reengage/return.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CEASE FIRE
| Discontinue firing/do not open fire. Complete intercept if weapons are in flight. Continue to track.
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CHERUBS || Hundreds of feet above ground level. (“CHERUBS 3” means 300 feet AGL)<ref>CHERUBS '''only''' means altitude above ground level, and is not to be used as a general codeword for hundreds of feet. Saying "ANGELS 20 CHERUBS 3" when meaning 20300 feet MSL is not allowed.</ref>
|-
| CHICKS
| Friendly aircraft.
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTINUE
| Continue present maneuver; does not imply a change in clearance to engage or expend ordnance.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| COVER
| Directive/informative call to assume a supporting position that will allow engagement of a specified track or threat to the flight if required.
|-
| CRANK [left/right] || Turn as far as possible left or right while keeping the target on your radar
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| DROP KICK
| Informative to the flight that an intentional deviation from any briefed action is being made.
|-
| DROPPING
| Informative call that a fighter has discontinued targeting responsibility.
|-
| ENGAGED
| Informative call used to establish engaged and support roles in the visual arena.
|-
| EXTEND (with direction)
| Short-term maneuver to gain energy, distance, or separation normally with the intent of reengaging.
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FAST
| Target speed is estimated to be 600 to 900 knots ground speed/Mach 1 to 1.5.
|-
| FEET WET/DRY
| Flying over water/land.
|-
| FENCE IN || Directive to prepare your aircraft for battle. See UOAF SOP Section
|-
| FLASH (system)
| Temporarily activate specified system for identification purposes (e.g., IFF, afterburner, flare, or chaff).
|-
| FLOW [direction] || Turn to and fly in the designated heading
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HIGH
| Target is between 25,000 and 40,000 feet MSL.
|-
| HOLDING HANDS
| Aircraft in visual formation
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOSTILE
| A contact identified as an enemy upon which clearance to fire is authorized IAW the theater rules of engagement (ROE).
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| IN
| Informative call indicating a turn toward a known threat, may imply a request for information.
|-
| JINK
| Directive call to perform an unpredictable maneuver to negate a gun tracking solution.
|-
| JOKER || Prebriefed fuel remaining when you should start heading home
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| KILL
| Directive call to fire on designated target.
|-
| KNOCK-IT-OFF
| Directive call to cease air combat maneuvers/attacks/activities.
|-
| LEAN (with direction)
| Directive/informative call to maneuver in a direction to avoid the threat.
|-
| LOCKED (with position)
| Radar lock-on; correct targeting is not assumed.
|-
| LOW
| Below 10,000 feet MSL
|-
| MAGNUM || With direction and type of target. Anti-radiation weapon launched
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. <ref>"Ducks on a pond" is also used in BMS (and the best RTB call).</ref>
|-
| MARKING
| Friendly aircraft leaving contrails.
|-
| MARSHAL(ING)
| Establish(ed) at a specific point.
|-
| MERGE(D)
| Informative call that friendlies and targets have arrived in the same visual arena.
|-
| MUD || RWR indication of SAM or AAA radar
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO FACTOR || Not a threat
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCH(ING)
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OFF (with direction)
| Informative call indicating attack is terminated and maneuvering to the indicated direction.
|-
| OFFSET (with direction)
| Informative call indicating maneuver in a specified direction with reference to the target.
|-
| OUT
| Informative call indicating a turn to a cold aspect relative to the known threat.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PADLOCKED
| Informative call indicating aircrew cannot take eyes off an aircraft or ground target without risk of losing tally/visual.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PINCE
| Threat maneuvering for a bracket attack.
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| POP
| Starting climb for A/S attack OR Max performance climb out of low-altitude structure.
|-
| POSIT
| Request for friendly position; response in terms of a geographic landmark or off a common reference point.
|-
| PRESS
| Directive call to continue the attack; mutual support will be maintained. Supportive role will be assumed by the speaker.
|-
| PUMP
| A briefed maneuver to low aspect to stop closure on the threat or geographical boundary with the intent to reengage. Will be used to initiate a Grinder tactic.
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RESET
| Proceed to a pre-briefed position or area of operation (AO).
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER''' (type with direction)
| Informative call of an RWR indication of SAM launch.
|-
| SKIP IT
| Veto of fighter commit call, usually followed with further directions.
|-
| SKOSH
| Aircraft is out of or unable to employ active radar missiles.
|-
| SLICE / SLICEBACK (LEFT/RIGHT)
| Directive call to perform a high-G descending turn in the stated direction, usually 180-degree turn.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| STRIPPED
| Informative call that aircraft is out of briefed formation
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VAMPIRE
| Hostile antiship missile launch.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WEEDS
| Indicates that aircraft are operating close to the surface.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}

=Final Reminders=

For a "complete" list of brevity terms, see '''OPERATIONAL BREVITY WORDS, DEFINITIONS, AND COUNTERAIR (AFTTP 3-1.1).pdf''' in the ''/docs/Operational Manuals/'' folder of your Falcon install.
:
==== ABCs ====
When communicating, especially in a combat situation, remember the ABCs of radio protocol:

'''Accuracy'''

Make sure what you are saying is accurate and think about what you need to say before you broadcast.

'''Brevity'''

Be brief and use brevity terms as much as possible. In a hectic situation there’s a lot of information that needs to be transmitted and processed, and only one person can talk on the radio at a time.

'''Clarity'''

Speak clearly and slowly enough that other people can understand you. The last part is particularly important if you’re not a native english speaker or speaking to a non-native speaker.
{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-19T10:16:58Z

Lexi: /* Brevity Code Masterlist */ Added more brevity terms that are BMS/DCS applicable.

[[File:F16-pilot.jpg||none|500px|left|]] 

== Learning Objectives ==
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
* [http://www.krauselabs.net/dump/Us_Marine_Corps---Multi_Service_Brevity_Codes_Mcrp_3-25B.pdf MULTI-SERVICE BREVITY CODES ]
*[https://en.wikipedia.org/wiki/Brevity_code Brevity_code]

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively, this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate their messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

==== Definitions ====
: '''Ship''': Single aircraft.
: '''Element''': Two ships working in tandem. This is the basic combat unit.
: '''Flight''': Two elements working in tandem. (Sometimes you can have three-ship flights).
: '''Package''': Two or more flights tasked with accomplishing a single mission.

====Types of radio messages====
There are two (main) kinds of messages: ''Advisories'' and ''directives''. 
An '''advisory''' is a message where you state what you are doing or intending to do. It is particularly important to remember if you're a flight lead or element lead to let other flights know when you're being engaged, or if you're engaging someone, or if you're running away from something.
Advisories do not need to be acknowledged, although they can be.

Examples:
* The flight lead can call out his altitude and speed when climbing from take-off to let his flight know if they’re going to fast or lagging behind.
* Giving an ''"IN"'' call when attacking a ground target.
* Giving an ''"Engaged defensive"'' call to the rest of the package if your flight finds itself engaged by enemy fighters.

A '''directive''' is an order to perform some action. They’re usually given by element-, flight-, or package leaders to their subordinates. However others can also give directives depending on the circumstances. E.g. you are supporting your element leader in a dogfight and you see a bandit about to fire on him, you would then direct your leader to "BREAK" in concert with you trying to gain a position to attack the bandit.

== Responding to communications ==

'''Within the flight (VHF)''' when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

'''Between flights (UHF)''', the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

Whenever you start a message not directed toward others you start with your callsign. On package comms where everyone will hear you, you use your full callsign.

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO give an "Engaged offensive" call followed by the BRAA or bullseye of the target when in a dogfight.

DO remain calm and speak clearly.

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture)

DON'T use "over" or "out".

DON'T use "break" to signal a pause. Break is a brevity word to perform a rapid turn.

''These are not the same as the [[:Category:Official Documentation|UO SOPs]] or the [http://forums.unitedoperations.net/index.php/topic/15344-uoaf-sops UOAF SOPs], which are the rules of the community. You've read [[:Category:Official Documentation|the rules]], right?''

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''second''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"Panther 1, '''Lobo 2''' engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are committing to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"Panther 1, '''Lobo 2'''"}}

Indicating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{red|"Lobo 2, '''Panther 1'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| AS FRAGGED
| Unit or element will be performing exactly as stated by the air tasking order (ATO).
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BANZAI
| Informative or directive call to execute launch-and-decide tactics.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| (system) BENT
| System indicated is inoperative.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BIRD
| Friendly surface-to-air missile (SAM).
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| BLOW THROUGH
| Directive or informative call that indicates aircraft will continue straight ahead at the merge and not become anchored with target/targets.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BOGEY DOPE
| Request for target information as requested or closest group in BRAA (with appropriate fill-ins).
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUGOUT (with direction)
| Separation from that particular engagement/attack/operation; no intent to reengage/return.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CEASE FIRE
| Discontinue firing/do not open fire. Complete intercept if weapons are in flight. Continue to track.
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CHERUBS || Hundreds of feet above ground level. (“CHERUBS 3” means 300 feet AGL)<ref>CHERUBS '''only''' means altitude above ground level, and is not to be used as a general codeword for hundreds of feet. Saying "ANGELS 20 CHERUBS 3" when meaning 20300 feet MSL is not allowed.</ref>
|-
| CHICKS
| Friendly aircraft.
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTINUE
| Continue present maneuver; does not imply a change in clearance to engage or expend ordnance.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| COVER
| Directive/informative call to assume a supporting position that will allow engagement of a specified track or threat to the flight if required.
|-
| CRANK [left/right] || Turn as far as possible left or right while keeping the target on your radar
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| DROP KICK
| Informative to the flight that an intentional deviation from any briefed action is being made.
|-
| DROPPING
| Informative call that a fighter has discontinued targeting responsibility.
|-
| ENGAGED
| Informative call used to establish engaged and support roles in the visual arena.
|-
| EXTEND (with direction)
| Short-term maneuver to gain energy, distance, or separation normally with the intent of reengaging.
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FAST
| Target speed is estimated to be 600 to 900 knots ground speed/Mach 1 to 1.5.
|-
| FEET WET/DRY
| Flying over water/land.
|-
| FENCE IN || Directive to prepare your aircraft for battle. See UOAF SOP Section
|-
| FLASH (system)
| Temporarily activate specified system for identification purposes (e.g., IFF, afterburner, flare, or chaff).
|-
| FLOW [direction] || Turn to and fly in the designated heading
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HIGH
| Target is between 25,000 and 40,000 feet MSL.
|-
| HOLDING HANDS
| Aircraft in visual formation
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOSTILE
| A contact identified as an enemy upon which clearance to fire is authorized IAW the theater rules of engagement (ROE).
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| IN
| Informative call indicating a turn toward a known threat, may imply a request for information.
|-
| JINK
| Directive call to perform an unpredictable maneuver to negate a gun tracking solution.
|-
| JOKER || Prebriefed fuel remaining when you should start heading home
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| KILL
| Directive call to fire on designated target.
|-
| KNOCK-IT-OFF
| Directive call to cease air combat maneuvers/attacks/activities.
|-
| LEAN (with direction)
| Directive/informative call to maneuver in a direction to avoid the threat.
|-
| LOCKED (with position)
| Radar lock-on; correct targeting is not assumed.
|-
| LOW
| Below 10,000 feet MSL
|-
| MAGNUM || With direction and type of target. Anti-radiation weapon launched
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. <ref>"Ducks on a pond" is also used in BMS (and the best RTB call).</ref>
|-
| MARKING
| Friendly aircraft leaving contrails.
|-
| MARSHAL(ING)
| Establish(ed) at a specific point.
|-
| MERGE(D)
| Informative call that friendlies and targets have arrived in the same visual arena.
|-
| MUD || RWR indication of SAM or AAA radar
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO FACTOR || Not a threat
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCH(ING)
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OFF (with direction)
| Informative call indicating attack is terminated and maneuvering to the indicated direction.
|-
| OFFSET (with direction)
| Informative call indicating maneuver in a specified direction with reference to the target.
|-
| OUT
| Informative call indicating a turn to a cold aspect relative to the known threat.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PADLOCKED
| Informative call indicating aircrew cannot take eyes off an aircraft or ground target without risk of losing tally/visual.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PINCE
| Threat maneuvering for a bracket attack.
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| POP
| Starting climb for A/S attack OR Max performance climb out of low-altitude structure.
|-
| POSIT
| Request for friendly position; response in terms of a geographic landmark or off a common reference point.
|-
| PRESS
| Directive call to continue the attack; mutual support will be maintained. Supportive role will be assumed by the speaker.
|-
| PUMP
| A briefed maneuver to low aspect to stop closure on the threat or geographical boundary with the intent to reengage. Will be used to initiate a Grinder tactic.
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RESET
| Proceed to a pre-briefed position or area of operation (AO).
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER''' (type with direction)
| Informative call of an RWR indication of SAM launch.
|-
| SKIP IT
| Veto of fighter commit call, usually followed with further directions.
|-
| SKOSH
| Aircraft is out of or unable to employ active radar missiles.
|-
| SLICE / SLICEBACK (LEFT/RIGHT)
| Directive call to perform a high-G descending turn in the stated direction, usually 180-degree turn.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| STRIPPED
| Informative call that aircraft is out of briefed formation
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VAMPIRE
| Hostile antiship missile launch.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}

=Final Reminders=

For a "complete" list of brevity terms, see '''OPERATIONAL BREVITY WORDS, DEFINITIONS, AND COUNTERAIR (AFTTP 3-1.1).pdf''' in the ''/docs/Operational Manuals/'' folder of your Falcon install.
:
==== ABCs ====
When communicating, especially in a combat situation, remember the ABCs of radio protocol:

'''Accuracy'''

Make sure what you are saying is accurate and think about what you need to say before you broadcast.

'''Brevity'''

Be brief and use brevity terms as much as possible. In a hectic situation there’s a lot of information that needs to be transmitted and processed, and only one person can talk on the radio at a time.

'''Clarity'''

Speak clearly and slowly enough that other people can understand you. The last part is particularly important if you’re not a native english speaker or speaking to a non-native speaker.
{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-19T09:40:52Z

Lexi: /* Types of radio messages */

[[File:F16-pilot.jpg||none|500px|left|]] 

== Learning Objectives ==
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
* [http://www.krauselabs.net/dump/Us_Marine_Corps---Multi_Service_Brevity_Codes_Mcrp_3-25B.pdf MULTI-SERVICE BREVITY CODES ]
*[https://en.wikipedia.org/wiki/Brevity_code Brevity_code]

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively, this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate their messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

==== Definitions ====
: '''Ship''': Single aircraft.
: '''Element''': Two ships working in tandem. This is the basic combat unit.
: '''Flight''': Two elements working in tandem. (Sometimes you can have three-ship flights).
: '''Package''': Two or more flights tasked with accomplishing a single mission.

====Types of radio messages====
There are two (main) kinds of messages: ''Advisories'' and ''directives''. 
An '''advisory''' is a message where you state what you are doing or intending to do. It is particularly important to remember if you're a flight lead or element lead to let other flights know when you're being engaged, or if you're engaging someone, or if you're running away from something.
Advisories do not need to be acknowledged, although they can be.

Examples:
* The flight lead can call out his altitude and speed when climbing from take-off to let his flight know if they’re going to fast or lagging behind.
* Giving an ''"IN"'' call when attacking a ground target.
* Giving an ''"Engaged defensive"'' call to the rest of the package if your flight finds itself engaged by enemy fighters.

A '''directive''' is an order to perform some action. They’re usually given by element-, flight-, or package leaders to their subordinates. However others can also give directives depending on the circumstances. E.g. you are supporting your element leader in a dogfight and you see a bandit about to fire on him, you would then direct your leader to "BREAK" in concert with you trying to gain a position to attack the bandit.

== Responding to communications ==

'''Within the flight (VHF)''' when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

'''Between flights (UHF)''', the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

Whenever you start a message not directed toward others you start with your callsign. On package comms where everyone will hear you, you use your full callsign.

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO give an "Engaged offensive" call followed by the BRAA or bullseye of the target when in a dogfight.

DO remain calm and speak clearly.

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture)

DON'T use "over" or "out".

DON'T use "break" to signal a pause. Break is a brevity word to perform a rapid turn.

''These are not the same as the [[:Category:Official Documentation|UO SOPs]] or the [http://forums.unitedoperations.net/index.php/topic/15344-uoaf-sops UOAF SOPs], which are the rules of the community. You've read [[:Category:Official Documentation|the rules]], right?''

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''second''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"Panther 1, '''Lobo 2''' engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are committing to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"Panther 1, '''Lobo 2'''"}}

Indicating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{red|"Lobo 2, '''Panther 1'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CHERUBS || Hundreds of feet above ground level. (“CHERUBS 3” means 300 feet AGL)<ref>CHERUBS '''only''' means altitude above ground level, and is not to be used as a general codeword for hundreds of feet. Saying "ANGELS 20 CHERUBS 3" when meaning 20300 feet MSL is not allowed.</ref>
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| CRANK [left/right] || Turn as far as possible left or right while keeping the target on your radar
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FENCE IN || Directive to prepare your aircraft for battle. See UOAF SOP Section
|-
| FLOW [direction] || Turn to and fly in the designated heading
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| JOKER || Prebriefed fuel remaining when you should start heading home
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| LOW
| Below 10,000 feet MSL
|-
| MAGNUM || With direction and type of target. Anti-radiation weapon launched
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).
|-
| MUD || RWR indication of SAM or AAA radar
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO FACTOR || Not a threat
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCH(ING)
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER'''
| Informative call of an RWR indication of SAM launch.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}

=Final Reminders=

For a "complete" list of brevity terms, see '''OPERATIONAL BREVITY WORDS, DEFINITIONS, AND COUNTERAIR (AFTTP 3-1.1).pdf''' in the ''/docs/Operational Manuals/'' folder of your Falcon install.
:
==== ABCs ====
When communicating, especially in a combat situation, remember the ABCs of radio protocol:

'''Accuracy'''

Make sure what you are saying is accurate and think about what you need to say before you broadcast.

'''Brevity'''

Be brief and use brevity terms as much as possible. In a hectic situation there’s a lot of information that needs to be transmitted and processed, and only one person can talk on the radio at a time.

'''Clarity'''

Speak clearly and slowly enough that other people can understand you. The last part is particularly important if you’re not a native english speaker or speaking to a non-native speaker.
{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-19T09:39:42Z

Lexi: /* Basic Principles of Brevity */

[[File:F16-pilot.jpg||none|500px|left|]] 

== Learning Objectives ==
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
* [http://www.krauselabs.net/dump/Us_Marine_Corps---Multi_Service_Brevity_Codes_Mcrp_3-25B.pdf MULTI-SERVICE BREVITY CODES ]
*[https://en.wikipedia.org/wiki/Brevity_code Brevity_code]

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively, this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate their messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

==== Definitions ====
: '''Ship''': Single aircraft.
: '''Element''': Two ships working in tandem. This is the basic combat unit.
: '''Flight''': Two elements working in tandem. (Sometimes you can have three-ship flights).
: '''Package''': Two or more flights tasked with accomplishing a single mission.

====Types of radio messages====
There are two (main) kinds of messages: ''Advisories'' and ''directives''. 
An '''advisory''' is a message where you state what you are doing or intending to do. It is particularly important to remember if you're a flight lead or element lead to let other flights know when you're being engaged, or if you're engaging someone, or if you're running away from something.
Advisories do not need to be acknowledged, although they can be.

Examples:
* The flight lead can call out his altitude and speed when climbing from take-off to let his flight know if they’re going to fast or lagging behind.
* Giving an ''"IN"'' call when attacking a ground target.
* Giving an ''"Engaged defensive"'' call to the rest of the package if your flight finds itself engaged by enemy fighters.

A '''directive''' is an order to perform some action. They’re usually given by element-, flight-, or package leaders to their subordinates. However others can also give directives depending on the circumstances. E.g. you are supporting your element leader in a dogfight and you see a bandit about to draw a bead on him, you would then direct your leader to break in concert with you trying to gain a position on the bandit.

== Responding to communications ==

'''Within the flight (VHF)''' when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

'''Between flights (UHF)''', the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

Whenever you start a message not directed toward others you start with your callsign. On package comms where everyone will hear you, you use your full callsign.

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO give an "Engaged offensive" call followed by the BRAA or bullseye of the target when in a dogfight.

DO remain calm and speak clearly.

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture)

DON'T use "over" or "out".

DON'T use "break" to signal a pause. Break is a brevity word to perform a rapid turn.

''These are not the same as the [[:Category:Official Documentation|UO SOPs]] or the [http://forums.unitedoperations.net/index.php/topic/15344-uoaf-sops UOAF SOPs], which are the rules of the community. You've read [[:Category:Official Documentation|the rules]], right?''

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''second''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"Panther 1, '''Lobo 2''' engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are committing to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"Panther 1, '''Lobo 2'''"}}

Indicating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{red|"Lobo 2, '''Panther 1'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CHERUBS || Hundreds of feet above ground level. (“CHERUBS 3” means 300 feet AGL)<ref>CHERUBS '''only''' means altitude above ground level, and is not to be used as a general codeword for hundreds of feet. Saying "ANGELS 20 CHERUBS 3" when meaning 20300 feet MSL is not allowed.</ref>
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| CRANK [left/right] || Turn as far as possible left or right while keeping the target on your radar
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FENCE IN || Directive to prepare your aircraft for battle. See UOAF SOP Section
|-
| FLOW [direction] || Turn to and fly in the designated heading
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| JOKER || Prebriefed fuel remaining when you should start heading home
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| LOW
| Below 10,000 feet MSL
|-
| MAGNUM || With direction and type of target. Anti-radiation weapon launched
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).
|-
| MUD || RWR indication of SAM or AAA radar
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO FACTOR || Not a threat
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCH(ING)
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER'''
| Informative call of an RWR indication of SAM launch.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}

=Final Reminders=

For a "complete" list of brevity terms, see '''OPERATIONAL BREVITY WORDS, DEFINITIONS, AND COUNTERAIR (AFTTP 3-1.1).pdf''' in the ''/docs/Operational Manuals/'' folder of your Falcon install.
:
==== ABCs ====
When communicating, especially in a combat situation, remember the ABCs of radio protocol:

'''Accuracy'''

Make sure what you are saying is accurate and think about what you need to say before you broadcast.

'''Brevity'''

Be brief and use brevity terms as much as possible. In a hectic situation there’s a lot of information that needs to be transmitted and processed, and only one person can talk on the radio at a time.

'''Clarity'''

Speak clearly and slowly enough that other people can understand you. The last part is particularly important if you’re not a native english speaker or speaking to a non-native speaker.
{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-19T09:38:45Z

Lexi: /* Basic Principles of Brevity */

[[File:F16-pilot.jpg||none|500px|left|]] 

== Learning Objectives ==
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
* [http://www.krauselabs.net/dump/Us_Marine_Corps---Multi_Service_Brevity_Codes_Mcrp_3-25B.pdf MULTI-SERVICE BREVITY CODES ]
*[https://en.wikipedia.org/wiki/Brevity_code Brevity_code]

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively (less important), this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate their messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

==== Definitions ====
: '''Ship''': Single aircraft.
: '''Element''': Two ships working in tandem. This is the basic combat unit.
: '''Flight''': Two elements working in tandem. (Sometimes you can have three-ship flights).
: '''Package''': Two or more flights tasked with accomplishing a single mission.

====Types of radio messages====
There are two (main) kinds of messages: ''Advisories'' and ''directives''. 
An '''advisory''' is a message where you state what you are doing or intending to do. It is particularly important to remember if you're a flight lead or element lead to let other flights know when you're being engaged, or if you're engaging someone, or if you're running away from something.
Advisories do not need to be acknowledged, although they can be.

Examples:
* The flight lead can call out his altitude and speed when climbing from take-off to let his flight know if they’re going to fast or lagging behind.
* Giving an ''"IN"'' call when attacking a ground target.
* Giving an ''"Engaged defensive"'' call to the rest of the package if your flight finds itself engaged by enemy fighters.

A '''directive''' is an order to perform some action. They’re usually given by element-, flight-, or package leaders to their subordinates. However others can also give directives depending on the circumstances. E.g. you are supporting your element leader in a dogfight and you see a bandit about to draw a bead on him, you would then direct your leader to break in concert with you trying to gain a position on the bandit.

== Responding to communications ==

'''Within the flight (VHF)''' when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

'''Between flights (UHF)''', the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

Whenever you start a message not directed toward others you start with your callsign. On package comms where everyone will hear you, you use your full callsign.

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO give an "Engaged offensive" call followed by the BRAA or bullseye of the target when in a dogfight.

DO remain calm and speak clearly.

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture)

DON'T use "over" or "out".

DON'T use "break" to signal a pause. Break is a brevity word to perform a rapid turn.

''These are not the same as the [[:Category:Official Documentation|UO SOPs]] or the [http://forums.unitedoperations.net/index.php/topic/15344-uoaf-sops UOAF SOPs], which are the rules of the community. You've read [[:Category:Official Documentation|the rules]], right?''

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''second''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"Panther 1, '''Lobo 2''' engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are committing to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"Panther 1, '''Lobo 2'''"}}

Indicating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{red|"Lobo 2, '''Panther 1'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CHERUBS || Hundreds of feet above ground level. (“CHERUBS 3” means 300 feet AGL)<ref>CHERUBS '''only''' means altitude above ground level, and is not to be used as a general codeword for hundreds of feet. Saying "ANGELS 20 CHERUBS 3" when meaning 20300 feet MSL is not allowed.</ref>
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| CRANK [left/right] || Turn as far as possible left or right while keeping the target on your radar
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FENCE IN || Directive to prepare your aircraft for battle. See UOAF SOP Section
|-
| FLOW [direction] || Turn to and fly in the designated heading
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| JOKER || Prebriefed fuel remaining when you should start heading home
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| LOW
| Below 10,000 feet MSL
|-
| MAGNUM || With direction and type of target. Anti-radiation weapon launched
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).
|-
| MUD || RWR indication of SAM or AAA radar
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO FACTOR || Not a threat
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCH(ING)
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER'''
| Informative call of an RWR indication of SAM launch.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}

=Final Reminders=

For a "complete" list of brevity terms, see '''OPERATIONAL BREVITY WORDS, DEFINITIONS, AND COUNTERAIR (AFTTP 3-1.1).pdf''' in the ''/docs/Operational Manuals/'' folder of your Falcon install.
:
==== ABCs ====
When communicating, especially in a combat situation, remember the ABCs of radio protocol:

'''Accuracy'''

Make sure what you are saying is accurate and think about what you need to say before you broadcast.

'''Brevity'''

Be brief and use brevity terms as much as possible. In a hectic situation there’s a lot of information that needs to be transmitted and processed, and only one person can talk on the radio at a time.

'''Clarity'''

Speak clearly and slowly enough that other people can understand you. The last part is particularly important if you’re not a native english speaker or speaking to a non-native speaker.
{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-19T09:38:22Z

Lexi: /* Being a good Flight Lead */

[[File:F16-pilot.jpg||none|500px|left|]] 

== Learning Objectives ==
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
* [http://www.krauselabs.net/dump/Us_Marine_Corps---Multi_Service_Brevity_Codes_Mcrp_3-25B.pdf MULTI-SERVICE BREVITY CODES ]
*[https://en.wikipedia.org/wiki/Brevity_code Brevity_code]

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively (less important), this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate critical messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

==== Definitions ====
: '''Ship''': Single aircraft.
: '''Element''': Two ships working in tandem. This is the basic combat unit.
: '''Flight''': Two elements working in tandem. (Sometimes you can have three-ship flights).
: '''Package''': Two or more flights tasked with accomplishing a single mission.

====Types of radio messages====
There are two (main) kinds of messages: ''Advisories'' and ''directives''. 
An '''advisory''' is a message where you state what you are doing or intending to do. It is particularly important to remember if you're a flight lead or element lead to let other flights know when you're being engaged, or if you're engaging someone, or if you're running away from something.
Advisories do not need to be acknowledged, although they can be.

Examples:
* The flight lead can call out his altitude and speed when climbing from take-off to let his flight know if they’re going to fast or lagging behind.
* Giving an ''"IN"'' call when attacking a ground target.
* Giving an ''"Engaged defensive"'' call to the rest of the package if your flight finds itself engaged by enemy fighters.

A '''directive''' is an order to perform some action. They’re usually given by element-, flight-, or package leaders to their subordinates. However others can also give directives depending on the circumstances. E.g. you are supporting your element leader in a dogfight and you see a bandit about to draw a bead on him, you would then direct your leader to break in concert with you trying to gain a position on the bandit.

== Responding to communications ==

'''Within the flight (VHF)''' when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

'''Between flights (UHF)''', the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

Whenever you start a message not directed toward others you start with your callsign. On package comms where everyone will hear you, you use your full callsign.

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO give an "Engaged offensive" call followed by the BRAA or bullseye of the target when in a dogfight.

DO remain calm and speak clearly.

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture)

DON'T use "over" or "out".

DON'T use "break" to signal a pause. Break is a brevity word to perform a rapid turn.

''These are not the same as the [[:Category:Official Documentation|UO SOPs]] or the [http://forums.unitedoperations.net/index.php/topic/15344-uoaf-sops UOAF SOPs], which are the rules of the community. You've read [[:Category:Official Documentation|the rules]], right?''

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''second''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"Panther 1, '''Lobo 2''' engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are committing to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"Panther 1, '''Lobo 2'''"}}

Indicating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{red|"Lobo 2, '''Panther 1'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CHERUBS || Hundreds of feet above ground level. (“CHERUBS 3” means 300 feet AGL)<ref>CHERUBS '''only''' means altitude above ground level, and is not to be used as a general codeword for hundreds of feet. Saying "ANGELS 20 CHERUBS 3" when meaning 20300 feet MSL is not allowed.</ref>
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| CRANK [left/right] || Turn as far as possible left or right while keeping the target on your radar
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FENCE IN || Directive to prepare your aircraft for battle. See UOAF SOP Section
|-
| FLOW [direction] || Turn to and fly in the designated heading
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| JOKER || Prebriefed fuel remaining when you should start heading home
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| LOW
| Below 10,000 feet MSL
|-
| MAGNUM || With direction and type of target. Anti-radiation weapon launched
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).
|-
| MUD || RWR indication of SAM or AAA radar
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO FACTOR || Not a threat
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCH(ING)
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER'''
| Informative call of an RWR indication of SAM launch.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}

=Final Reminders=

For a "complete" list of brevity terms, see '''OPERATIONAL BREVITY WORDS, DEFINITIONS, AND COUNTERAIR (AFTTP 3-1.1).pdf''' in the ''/docs/Operational Manuals/'' folder of your Falcon install.
:
==== ABCs ====
When communicating, especially in a combat situation, remember the ABCs of radio protocol:

'''Accuracy'''

Make sure what you are saying is accurate and think about what you need to say before you broadcast.

'''Brevity'''

Be brief and use brevity terms as much as possible. In a hectic situation there’s a lot of information that needs to be transmitted and processed, and only one person can talk on the radio at a time.

'''Clarity'''

Speak clearly and slowly enough that other people can understand you. The last part is particularly important if you’re not a native english speaker or speaking to a non-native speaker.
{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-18T22:48:41Z

Lexi: /* Do's and Don'ts */

[[File:F16-pilot.jpg||none|500px|left|]] 

== Learning Objectives ==
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
* [http://www.krauselabs.net/dump/Us_Marine_Corps---Multi_Service_Brevity_Codes_Mcrp_3-25B.pdf MULTI-SERVICE BREVITY CODES ]
*[https://en.wikipedia.org/wiki/Brevity_code Brevity_code]

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively (less important), this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate critical messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

==== Definitions ====
: '''Ship''': Single aircraft.
: '''Element''': Two ships working in tandem. This is the basic combat unit.
: '''Flight''': Two elements working in tandem. (Sometimes you can have three-ship flights).
: '''Package''': Two or more flights tasked with accomplishing a single mission.

====Types of radio messages====
There are two (main) kinds of messages: ''Advisories'' and ''directives''. 
An '''advisory''' is a message where you state what you are doing or intending to do. It is particularly important to remember if you're a flight lead or element lead to let other flights know when you're being engaged, or if you're engaging someone, or if you're running away from something.
Advisories do not need to be acknowledged, although they can be.

Examples:
* The flight lead can call out his altitude and speed when climbing from take-off to let his flight know if they’re going to fast or lagging behind.
* Giving an ''"IN"'' call when attacking a ground target.
* Giving an ''"Engaged defensive"'' call to the rest of the package if your flight finds itself engaged by enemy fighters.

A '''directive''' is an order to perform some action. They’re usually given by element-, flight-, or package leaders to their subordinates. However others can also give directives depending on the circumstances. E.g. you are supporting your element leader in a dogfight and you see a bandit about to draw a bead on him, you would then direct your leader to break in concert with you trying to gain a position on the bandit.

== Responding to communications ==

'''Within the flight (VHF)''' when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

'''Between flights (UHF)''', the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

Whenever you start a message not directed toward others you start with your callsign. On package comms where everyone will hear you, you use your full callsign.

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO give an "Engaged offensive" call followed by the BRAA or bullseye of the target when in a dogfight.

DO remain calm and speak clearly.

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture)

DON'T use "over" or "out".

DON'T use "break" to signal a pause. Break is a brevity word to perform a rapid turn.

''These are not the same as the [[:Category:Official Documentation|UO SOPs]] or the [http://forums.unitedoperations.net/index.php/topic/15344-uoaf-sops UOAF SOPs], which are the rules of the community. You've read [[:Category:Official Documentation|the rules]], right?''

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''second''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"Panther 1, '''Lobo 2''' engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are committing to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"Panther 1, '''Lobo 2'''"}}

Indicating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{red|"Lobo 2, '''Panther 1'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1-1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CHERUBS || Hundreds of feet above ground level. (“CHERUBS 3” means 300 feet AGL)<ref>CHERUBS '''only''' means altitude above ground level, and is not to be used as a general codeword for hundreds of feet. Saying "ANGELS 20 CHERUBS 3" when meaning 20300 feet MSL is not allowed.</ref>
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| CRANK [left/right] || Turn as far as possible left or right while keeping the target on your radar
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FENCE IN || Directive to prepare your aircraft for battle. See UOAF SOP Section
|-
| FLOW [direction] || Turn to and fly in the designated heading
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| JOKER || Prebriefed fuel remaining when you should start heading home
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| LOW
| Below 10,000 feet MSL
|-
| MAGNUM || With direction and type of target. Anti-radiation weapon launched
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).
|-
| MUD || RWR indication of SAM or AAA radar
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO FACTOR || Not a threat
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCH(ING)
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER'''
| Informative call of an RWR indication of SAM launch.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}

=Final Reminders=

For a "complete" list of brevity terms, see '''OPERATIONAL BREVITY WORDS, DEFINITIONS, AND COUNTERAIR (AFTTP 3-1.1).pdf''' in the ''/docs/Operational Manuals/'' folder of your Falcon install.
:
==== ABCs ====
When communicating, especially in a combat situation, remember the ABCs of radio protocol:

'''Accuracy'''

Make sure what you are saying is accurate and think about what you need to say before you broadcast.

'''Brevity'''

Be brief and use brevity terms as much as possible. In a hectic situation there’s a lot of information that needs to be transmitted and processed, and only one person can talk on the radio at a time.

'''Clarity'''

Speak clearly and slowly enough that other people can understand you. The last part is particularly important if you’re not a native english speaker or speaking to a non-native speaker.
{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-18T22:46:52Z

Lexi: /* Being a good Flight Lead */

[[File:F16-pilot.jpg||none|500px|left|]] 

== Learning Objectives ==
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
* [http://www.krauselabs.net/dump/Us_Marine_Corps---Multi_Service_Brevity_Codes_Mcrp_3-25B.pdf MULTI-SERVICE BREVITY CODES ]
*[https://en.wikipedia.org/wiki/Brevity_code Brevity_code]

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively (less important), this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate critical messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

==== Definitions ====
: '''Ship''': Single aircraft.
: '''Element''': Two ships working in tandem. This is the basic combat unit.
: '''Flight''': Two elements working in tandem. (Sometimes you can have three-ship flights).
: '''Package''': Two or more flights tasked with accomplishing a single mission.

====Types of radio messages====
There are two (main) kinds of messages: ''Advisories'' and ''directives''. 
An '''advisory''' is a message where you state what you are doing or intending to do. It is particularly important to remember if you're a flight lead or element lead to let other flights know when you're being engaged, or if you're engaging someone, or if you're running away from something.
Advisories do not need to be acknowledged, although they can be.

Examples:
* The flight lead can call out his altitude and speed when climbing from take-off to let his flight know if they’re going to fast or lagging behind.
* Giving an ''"IN"'' call when attacking a ground target.
* Giving an ''"Engaged defensive"'' call to the rest of the package if your flight finds itself engaged by enemy fighters.

A '''directive''' is an order to perform some action. They’re usually given by element-, flight-, or package leaders to their subordinates. However others can also give directives depending on the circumstances. E.g. you are supporting your element leader in a dogfight and you see a bandit about to draw a bead on him, you would then direct your leader to break in concert with you trying to gain a position on the bandit.

== Responding to communications ==

'''Within the flight (VHF)''' when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

'''Between flights (UHF)''', the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

Whenever you start a message not directed toward others you start with your callsign. On package comms where everyone will hear you, you use your full callsign.

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO remain calm and speak clearly!

DO give an "Engaged offensive" call followed by the BRAA or bullseye of the target when in a dogfight.

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture)

DON'T use "over" or "out".

DON'T use "break" to signal a pause. Break is a brevity word to perform a rapid turn.

''These are not the same as the [[:Category:Official Documentation|UO SOPs]] or the [http://forums.unitedoperations.net/index.php/topic/15344-uoaf-sops UOAF SOPs], which are the rules of the community. You've read [[:Category:Official Documentation|the rules]], right?''

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''second''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"Panther 1, '''Lobo 2''' engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are committing to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"Panther 1, '''Lobo 2'''"}}

Indicating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{red|"Lobo 2, '''Panther 1'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1-1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CHERUBS || Hundreds of feet above ground level. (“CHERUBS 3” means 300 feet AGL)<ref>CHERUBS '''only''' means altitude above ground level, and is not to be used as a general codeword for hundreds of feet. Saying "ANGELS 20 CHERUBS 3" when meaning 20300 feet MSL is not allowed.</ref>
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| CRANK [left/right] || Turn as far as possible left or right while keeping the target on your radar
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FENCE IN || Directive to prepare your aircraft for battle. See UOAF SOP Section
|-
| FLOW [direction] || Turn to and fly in the designated heading
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| JOKER || Prebriefed fuel remaining when you should start heading home
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| LOW
| Below 10,000 feet MSL
|-
| MAGNUM || With direction and type of target. Anti-radiation weapon launched
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).
|-
| MUD || RWR indication of SAM or AAA radar
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO FACTOR || Not a threat
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCH(ING)
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER'''
| Informative call of an RWR indication of SAM launch.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}

=Final Reminders=

For a "complete" list of brevity terms, see '''OPERATIONAL BREVITY WORDS, DEFINITIONS, AND COUNTERAIR (AFTTP 3-1.1).pdf''' in the ''/docs/Operational Manuals/'' folder of your Falcon install.
:
==== ABCs ====
When communicating, especially in a combat situation, remember the ABCs of radio protocol:

'''Accuracy'''

Make sure what you are saying is accurate and think about what you need to say before you broadcast.

'''Brevity'''

Be brief and use brevity terms as much as possible. In a hectic situation there’s a lot of information that needs to be transmitted and processed, and only one person can talk on the radio at a time.

'''Clarity'''

Speak clearly and slowly enough that other people can understand you. The last part is particularly important if you’re not a native english speaker or speaking to a non-native speaker.
{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-18T22:44:20Z

Lexi: /* Being a good Flight Lead */

[[File:F16-pilot.jpg||none|500px|left|]] 

== Learning Objectives ==
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
* [http://www.krauselabs.net/dump/Us_Marine_Corps---Multi_Service_Brevity_Codes_Mcrp_3-25B.pdf MULTI-SERVICE BREVITY CODES ]
*[https://en.wikipedia.org/wiki/Brevity_code Brevity_code]

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively (less important), this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate critical messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

==== Definitions ====
: '''Ship''': Single aircraft.
: '''Element''': Two ships working in tandem. This is the basic combat unit.
: '''Flight''': Two elements working in tandem. (Sometimes you can have three-ship flights).
: '''Package''': Two or more flights tasked with accomplishing a single mission.

====Types of radio messages====
There are two (main) kinds of messages: ''Advisories'' and ''directives''. 
An '''advisory''' is a message where you state what you are doing or intending to do. It is particularly important to remember if you're a flight lead or element lead to let other flights know when you're being engaged, or if you're engaging someone, or if you're running away from something.
Advisories do not need to be acknowledged, although they can be.

Examples:
* The flight lead can call out his altitude and speed when climbing from take-off to let his flight know if they’re going to fast or lagging behind.
* Giving an ''"IN"'' call when attacking a ground target.
* Giving an ''"Engaged defensive"'' call to the rest of the package if your flight finds itself engaged by enemy fighters.

A '''directive''' is an order to perform some action. They’re usually given by element-, flight-, or package leaders to their subordinates. However others can also give directives depending on the circumstances. E.g. you are supporting your element leader in a dogfight and you see a bandit about to draw a bead on him, you would then direct your leader to break in concert with you trying to gain a position on the bandit.

== Responding to communications ==

'''Within the flight (VHF)''' when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

'''Between flights (UHF)''', the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

Whenever you start a message not directed toward others you start with your callsign. On package comms where everyone will hear you, you use your full callsign.

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO remain calm and speak clearly!

DO give an "Engaged offensive" call followed by the BRAA or bullseye of the target when in a dogfight.

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture)

DON'T use "over" or "out".

DON'T use "break" to signal a pause. Break is a brevity word to perform a rapid turn.

''These are not the same as the [[:Category:Official Documentation|UO SOPs]] or the [http://forums.unitedoperations.net/index.php/topic/15344-uoaf-sops UOAF SOPs], which are the rules of the community. You've read [[:Category:Official Documentation|the rules]], right?''

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''second''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"'''Panther 1''', Lobo 2 engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are committing to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"'''Panther 1''', Lobo 2"}}

Indicating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{red|"Lobo 2''', Panther 1'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1-1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CHERUBS || Hundreds of feet above ground level. (“CHERUBS 3” means 300 feet AGL)<ref>CHERUBS '''only''' means altitude above ground level, and is not to be used as a general codeword for hundreds of feet. Saying "ANGELS 20 CHERUBS 3" when meaning 20300 feet MSL is not allowed.</ref>
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| CRANK [left/right] || Turn as far as possible left or right while keeping the target on your radar
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FENCE IN || Directive to prepare your aircraft for battle. See UOAF SOP Section
|-
| FLOW [direction] || Turn to and fly in the designated heading
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| JOKER || Prebriefed fuel remaining when you should start heading home
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| LOW
| Below 10,000 feet MSL
|-
| MAGNUM || With direction and type of target. Anti-radiation weapon launched
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).
|-
| MUD || RWR indication of SAM or AAA radar
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO FACTOR || Not a threat
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCH(ING)
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER'''
| Informative call of an RWR indication of SAM launch.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}

=Final Reminders=

For a "complete" list of brevity terms, see '''OPERATIONAL BREVITY WORDS, DEFINITIONS, AND COUNTERAIR (AFTTP 3-1.1).pdf''' in the ''/docs/Operational Manuals/'' folder of your Falcon install.
:
==== ABCs ====
When communicating, especially in a combat situation, remember the ABCs of radio protocol:

'''Accuracy'''

Make sure what you are saying is accurate and think about what you need to say before you broadcast.

'''Brevity'''

Be brief and use brevity terms as much as possible. In a hectic situation there’s a lot of information that needs to be transmitted and processed, and only one person can talk on the radio at a time.

'''Clarity'''

Speak clearly and slowly enough that other people can understand you. The last part is particularly important if you’re not a native english speaker or speaking to a non-native speaker.
{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-18T22:43:45Z

Lexi: /* Being a good Flight Lead */

[[File:F16-pilot.jpg||none|500px|left|]] 

== Learning Objectives ==
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
* [http://www.krauselabs.net/dump/Us_Marine_Corps---Multi_Service_Brevity_Codes_Mcrp_3-25B.pdf MULTI-SERVICE BREVITY CODES ]
*[https://en.wikipedia.org/wiki/Brevity_code Brevity_code]

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively (less important), this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate critical messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

==== Definitions ====
: '''Ship''': Single aircraft.
: '''Element''': Two ships working in tandem. This is the basic combat unit.
: '''Flight''': Two elements working in tandem. (Sometimes you can have three-ship flights).
: '''Package''': Two or more flights tasked with accomplishing a single mission.

====Types of radio messages====
There are two (main) kinds of messages: ''Advisories'' and ''directives''. 
An '''advisory''' is a message where you state what you are doing or intending to do. It is particularly important to remember if you're a flight lead or element lead to let other flights know when you're being engaged, or if you're engaging someone, or if you're running away from something.
Advisories do not need to be acknowledged, although they can be.

Examples:
* The flight lead can call out his altitude and speed when climbing from take-off to let his flight know if they’re going to fast or lagging behind.
* Giving an ''"IN"'' call when attacking a ground target.
* Giving an ''"Engaged defensive"'' call to the rest of the package if your flight finds itself engaged by enemy fighters.

A '''directive''' is an order to perform some action. They’re usually given by element-, flight-, or package leaders to their subordinates. However others can also give directives depending on the circumstances. E.g. you are supporting your element leader in a dogfight and you see a bandit about to draw a bead on him, you would then direct your leader to break in concert with you trying to gain a position on the bandit.

== Responding to communications ==

'''Within the flight (VHF)''' when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

'''Between flights (UHF)''', the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

Whenever you start a message not directed toward others you start with your callsign. On package comms where everyone will hear you, you use your full callsign.

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO remain calm and speak clearly!

DO give an "Engaged offensive" call followed by the BRAA or bullseye of the target when in a dogfight.

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture)

DON'T use "over" or "out".

DON'T use "break" to signal a pause. Break is a brevity word to perform a rapid turn.

''These are not the same as the [[:Category:Official Documentation|UO SOPs]] or the [http://forums.unitedoperations.net/index.php/topic/15344-uoaf-sops UOAF SOPs], which are the rules of the community. You've read [[:Category:Official Documentation|the rules]], right?''

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''second''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"'''Panther1''' Lobo 2 engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are commiting to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"'''Panther 1''', Lobo 2"}}

Indicating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{red|"Lobo 2,''' Panther 1'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1-1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CHERUBS || Hundreds of feet above ground level. (“CHERUBS 3” means 300 feet AGL)<ref>CHERUBS '''only''' means altitude above ground level, and is not to be used as a general codeword for hundreds of feet. Saying "ANGELS 20 CHERUBS 3" when meaning 20300 feet MSL is not allowed.</ref>
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| CRANK [left/right] || Turn as far as possible left or right while keeping the target on your radar
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FENCE IN || Directive to prepare your aircraft for battle. See UOAF SOP Section
|-
| FLOW [direction] || Turn to and fly in the designated heading
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| JOKER || Prebriefed fuel remaining when you should start heading home
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| LOW
| Below 10,000 feet MSL
|-
| MAGNUM || With direction and type of target. Anti-radiation weapon launched
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).
|-
| MUD || RWR indication of SAM or AAA radar
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO FACTOR || Not a threat
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCH(ING)
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER'''
| Informative call of an RWR indication of SAM launch.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}

=Final Reminders=

For a "complete" list of brevity terms, see '''OPERATIONAL BREVITY WORDS, DEFINITIONS, AND COUNTERAIR (AFTTP 3-1.1).pdf''' in the ''/docs/Operational Manuals/'' folder of your Falcon install.
:
==== ABCs ====
When communicating, especially in a combat situation, remember the ABCs of radio protocol:

'''Accuracy'''

Make sure what you are saying is accurate and think about what you need to say before you broadcast.

'''Brevity'''

Be brief and use brevity terms as much as possible. In a hectic situation there’s a lot of information that needs to be transmitted and processed, and only one person can talk on the radio at a time.

'''Clarity'''

Speak clearly and slowly enough that other people can understand you. The last part is particularly important if you’re not a native english speaker or speaking to a non-native speaker.
{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-18T21:41:43Z

Lexi:

[[File:F16-pilot.jpg||none|500px|left|]] 

== Learning Objectives ==
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
* [http://www.krauselabs.net/dump/Us_Marine_Corps---Multi_Service_Brevity_Codes_Mcrp_3-25B.pdf MULTI-SERVICE BREVITY CODES ]
*[https://en.wikipedia.org/wiki/Brevity_code Brevity_code]

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively (less important), this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate critical messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

==== Definitions ====
: '''Ship''': Single aircraft.
: '''Element''': Two ships working in tandem. This is the basic combat unit.
: '''Flight''': Two elements working in tandem. (Sometimes you can have three-ship flights).
: '''Package''': Two or more flights tasked with accomplishing a single mission.

====Types of radio messages====
There are two (main) kinds of messages: ''Advisories'' and ''directives''. 
An '''advisory''' is a message where you state what you are doing or intending to do. It is particularly important to remember if you're a flight lead or element lead to let other flights know when you're being engaged, or if you're engaging someone, or if you're running away from something.
Advisories do not need to be acknowledged, although they can be.

Examples:
* The flight lead can call out his altitude and speed when climbing from take-off to let his flight know if they’re going to fast or lagging behind.
* Giving an ''"IN"'' call when attacking a ground target.
* Giving an ''"Engaged defensive"'' call to the rest of the package if your flight finds itself engaged by enemy fighters.

A '''directive''' is an order to perform some action. They’re usually given by element-, flight-, or package leaders to their subordinates. However others can also give directives depending on the circumstances. E.g. you are supporting your element leader in a dogfight and you see a bandit about to draw a bead on him, you would then direct your leader to break in concert with you trying to gain a position on the bandit.

== Responding to communications ==

'''Within the flight (VHF)''' when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

'''Between flights (UHF)''', the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

Whenever you start a message not directed toward others you start with your callsign. On package comms where everyone will hear you, you use your full callsign.

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO remain calm and speak clearly!

DO give an "Engaged offensive" call followed by the BRAA or bullseye of the target when in a dogfight.

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture)

DON'T use "over" or "out".

DON'T use "break" to signal a pause. Break is a brevity word to perform a rapid turn.

''These are not the same as the [[:Category:Official Documentation|UO SOPs]] or the [http://forums.unitedoperations.net/index.php/topic/15344-uoaf-sops UOAF SOPs], which are the rules of the community. You've read [[:Category:Official Documentation|the rules]], right?''

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''first''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"'''Lobo 2''' to Panther 1 engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are commiting to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"'''Lobo 2''', Panther 1"}}

Indiciating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{red|"Panther 1,''' Lobo 2'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1-1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CHERUBS || Hundreds of feet above ground level. (“CHERUBS 3” means 300 feet AGL)<ref>CHERUBS '''only''' means altitude above ground level, and is not to be used as a general codeword for hundreds of feet. Saying "ANGELS 20 CHERUBS 3" when meaning 20300 feet MSL is not allowed.</ref>
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| CRANK [left/right] || Turn as far as possible left or right while keeping the target on your radar
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FENCE IN || Directive to prepare your aircraft for battle. See UOAF SOP Section
|-
| FLOW [direction] || Turn to and fly in the designated heading
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| JOKER || Prebriefed fuel remaining when you should start heading home
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| LOW
| Below 10,000 feet MSL
|-
| MAGNUM || With direction and type of target. Anti-radiation weapon launched
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).
|-
| MUD || RWR indication of SAM or AAA radar
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO FACTOR || Not a threat
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCH(ING)
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER'''
| Informative call of an RWR indication of SAM launch.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}

=Final Reminders=

For a "complete" list of brevity terms, see '''OPERATIONAL BREVITY WORDS, DEFINITIONS, AND COUNTERAIR (AFTTP 3-1.1).pdf''' in the ''/docs/Operational Manuals/'' folder of your Falcon install.
:
==== ABCs ====
When communicating, especially in a combat situation, remember the ABCs of radio protocol:

'''Accuracy'''

Make sure what you are saying is accurate and think about what you need to say before you broadcast.

'''Brevity'''

Be brief and use brevity terms as much as possible. In a hectic situation there’s a lot of information that needs to be transmitted and processed, and only one person can talk on the radio at a time.

'''Clarity'''

Speak clearly and slowly enough that other people can understand you. The last part is particularly important if you’re not a native english speaker or speaking to a non-native speaker.
{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-18T21:40:26Z

Lexi: /* Final Reminders */

{{wip}}[[File:F16-pilot.jpg||none|500px|left|]] 

== Learning Objectives ==
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
* [http://www.krauselabs.net/dump/Us_Marine_Corps---Multi_Service_Brevity_Codes_Mcrp_3-25B.pdf MULTI-SERVICE BREVITY CODES ]
*[https://en.wikipedia.org/wiki/Brevity_code Brevity_code]

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively (less important), this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate critical messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

==== Definitions ====
: '''Ship''': Single aircraft.
: '''Element''': Two ships working in tandem. This is the basic combat unit.
: '''Flight''': Two elements working in tandem. (Sometimes you can have three-ship flights).
: '''Package''': Two or more flights tasked with accomplishing a single mission.

====Types of radio messages====
There are two (main) kinds of messages: ''Advisories'' and ''directives''. 
An '''advisory''' is a message where you state what you are doing or intending to do. It is particularly important to remember if you're a flight lead or element lead to let other flights know when you're being engaged, or if you're engaging someone, or if you're running away from something.
Advisories do not need to be acknowledged, although they can be.

Examples:
* The flight lead can call out his altitude and speed when climbing from take-off to let his flight know if they’re going to fast or lagging behind.
* Giving an ''"IN"'' call when attacking a ground target.
* Giving an ''"Engaged defensive"'' call to the rest of the package if your flight finds itself engaged by enemy fighters.

A '''directive''' is an order to perform some action. They’re usually given by element-, flight-, or package leaders to their subordinates. However others can also give directives depending on the circumstances. E.g. you are supporting your element leader in a dogfight and you see a bandit about to draw a bead on him, you would then direct your leader to break in concert with you trying to gain a position on the bandit.

== Responding to communications ==

'''Within the flight (VHF)''' when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

'''Between flights (UHF)''', the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

Whenever you start a message not directed toward others you start with your callsign. On package comms where everyone will hear you, you use your full callsign.

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO remain calm and speak clearly!

DO give an "Engaged offensive" call followed by the BRAA or bullseye of the target when in a dogfight.

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture)

DON'T use "over" or "out".

DON'T use "break" to signal a pause. Break is a brevity word to perform a rapid turn.

''These are not the same as the [[:Category:Official Documentation|UO SOPs]] or the [http://forums.unitedoperations.net/index.php/topic/15344-uoaf-sops UOAF SOPs], which are the rules of the community. You've read [[:Category:Official Documentation|the rules]], right?''

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''first''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"'''Lobo 2''' to Panther 1 engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are commiting to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"'''Lobo 2''', Panther 1"}}

Indiciating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{red|"Panther 1,''' Lobo 2'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1-1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CHERUBS || Hundreds of feet above ground level. (“CHERUBS 3” means 300 feet AGL)<ref>CHERUBS '''only''' means altitude above ground level, and is not to be used as a general codeword for hundreds of feet. Saying "ANGELS 20 CHERUBS 3" when meaning 20300 feet MSL is not allowed.</ref>
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| CRANK [left/right] || Turn as far as possible left or right while keeping the target on your radar
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FENCE IN || Directive to prepare your aircraft for battle. See UOAF SOP Section
|-
| FLOW [direction] || Turn to and fly in the designated heading
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| JOKER || Prebriefed fuel remaining when you should start heading home
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| LOW
| Below 10,000 feet MSL
|-
| MAGNUM || With direction and type of target. Anti-radiation weapon launched
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).
|-
| MUD || RWR indication of SAM or AAA radar
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO FACTOR || Not a threat
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCH(ING)
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER'''
| Informative call of an RWR indication of SAM launch.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}

=Final Reminders=

For a "complete" list of brevity terms, see '''OPERATIONAL BREVITY WORDS, DEFINITIONS, AND COUNTERAIR (AFTTP 3-1.1).pdf''' in the ''/docs/Operational Manuals/'' folder of your Falcon install.
:
==== ABCs ====
When communicating, especially in a combat situation, remember the ABCs of radio protocol:

'''Accuracy'''

Make sure what you are saying is accurate and think about what you need to say before you broadcast.

'''Brevity'''

Be brief and use brevity terms as much as possible. In a hectic situation there’s a lot of information that needs to be transmitted and processed, and only one person can talk on the radio at a time.

'''Clarity'''

Speak clearly and slowly enough that other people can understand you. The last part is particularly important if you’re not a native english speaker or speaking to a non-native speaker.
{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-18T21:39:04Z

Lexi:

{{wip}}[[File:F16-pilot.jpg||none|500px|left|]] 

== Learning Objectives ==
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
* [http://www.krauselabs.net/dump/Us_Marine_Corps---Multi_Service_Brevity_Codes_Mcrp_3-25B.pdf MULTI-SERVICE BREVITY CODES ]
*[https://en.wikipedia.org/wiki/Brevity_code Brevity_code]

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively (less important), this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate critical messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

==== Definitions ====
: '''Ship''': Single aircraft.
: '''Element''': Two ships working in tandem. This is the basic combat unit.
: '''Flight''': Two elements working in tandem. (Sometimes you can have three-ship flights).
: '''Package''': Two or more flights tasked with accomplishing a single mission.

====Types of radio messages====
There are two (main) kinds of messages: ''Advisories'' and ''directives''. 
An '''advisory''' is a message where you state what you are doing or intending to do. It is particularly important to remember if you're a flight lead or element lead to let other flights know when you're being engaged, or if you're engaging someone, or if you're running away from something.
Advisories do not need to be acknowledged, although they can be.

Examples:
* The flight lead can call out his altitude and speed when climbing from take-off to let his flight know if they’re going to fast or lagging behind.
* Giving an ''"IN"'' call when attacking a ground target.
* Giving an ''"Engaged defensive"'' call to the rest of the package if your flight finds itself engaged by enemy fighters.

A '''directive''' is an order to perform some action. They’re usually given by element-, flight-, or package leaders to their subordinates. However others can also give directives depending on the circumstances. E.g. you are supporting your element leader in a dogfight and you see a bandit about to draw a bead on him, you would then direct your leader to break in concert with you trying to gain a position on the bandit.

== Responding to communications ==

'''Within the flight (VHF)''' when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

'''Between flights (UHF)''', the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

Whenever you start a message not directed toward others you start with your callsign. On package comms where everyone will hear you, you use your full callsign.

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO remain calm and speak clearly!

DO give an "Engaged offensive" call followed by the BRAA or bullseye of the target when in a dogfight.

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture)

DON'T use "over" or "out".

DON'T use "break" to signal a pause. Break is a brevity word to perform a rapid turn.

''These are not the same as the [[:Category:Official Documentation|UO SOPs]] or the [http://forums.unitedoperations.net/index.php/topic/15344-uoaf-sops UOAF SOPs], which are the rules of the community. You've read [[:Category:Official Documentation|the rules]], right?''

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''first''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"'''Lobo 2''' to Panther 1 engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are commiting to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"'''Lobo 2''', Panther 1"}}

Indiciating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{red|"Panther 1,''' Lobo 2'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1-1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CHERUBS || Hundreds of feet above ground level. (“CHERUBS 3” means 300 feet AGL)<ref>CHERUBS '''only''' means altitude above ground level, and is not to be used as a general codeword for hundreds of feet. Saying "ANGELS 20 CHERUBS 3" when meaning 20300 feet MSL is not allowed.</ref>
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| CRANK [left/right] || Turn as far as possible left or right while keeping the target on your radar
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FENCE IN || Directive to prepare your aircraft for battle. See UOAF SOP Section
|-
| FLOW [direction] || Turn to and fly in the designated heading
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| JOKER || Prebriefed fuel remaining when you should start heading home
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| LOW
| Below 10,000 feet MSL
|-
| MAGNUM || With direction and type of target. Anti-radiation weapon launched
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).
|-
| MUD || RWR indication of SAM or AAA radar
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO FACTOR || Not a threat
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCH(ING)
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER'''
| Informative call of an RWR indication of SAM launch.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}

=Final Reminders=

For a "complete" list of brevity terms, see '''OPERATIONAL BREVITY WORDS, DEFINITIONS, AND COUNTERAIR (AFTTP 3-1.1).pdf''' in the ''/docs/Operational Manuals/'' folder of your falcon install.
:
==== ABCs ====
When communicating, especially in a combat situation, remember the ABCs of radio protocol:

'''Accuracy'''

Make sure what you are saying is accurate and think about what you need to say before you broadcast.

'''Brevity'''

Be brief and use brevity terms as much as possible. In a hectic situation there’s a lot of information that needs to be transmitted and processed, and only one person can talk on the radio at a time.

'''Clarity'''

Speak clearly and slowly enough that other people can understand you. The last part is particularly important if you’re not a native english speaker or speaking to a non-native speaker.
{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-18T21:38:24Z

Lexi: /* Learning Files */

{{wip}}

[[File:F16-pilot.jpg||none|500px|left|]] 

== Learning Objectives ==
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
* [http://www.krauselabs.net/dump/Us_Marine_Corps---Multi_Service_Brevity_Codes_Mcrp_3-25B.pdf MULTI-SERVICE BREVITY CODES ]
*[https://en.wikipedia.org/wiki/Brevity_code Brevity_code]

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively (less important), this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate critical messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

==== Definitions ====
: '''Ship''': Single aircraft.
: '''Element''': Two ships working in tandem. This is the basic combat unit.
: '''Flight''': Two elements working in tandem. (Sometimes you can have three-ship flights).
: '''Package''': Two or more flights tasked with accomplishing a single mission.

====Types of radio messages====
There are two (main) kinds of messages: ''Advisories'' and ''directives''. 
An '''advisory''' is a message where you state what you are doing or intending to do. It is particularly important to remember if you're a flight lead or element lead to let other flights know when you're being engaged, or if you're engaging someone, or if you're running away from something.
Advisories do not need to be acknowledged, although they can be.

Examples:
* The flight lead can call out his altitude and speed when climbing from take-off to let his flight know if they’re going to fast or lagging behind.
* Giving an ''"IN"'' call when attacking a ground target.
* Giving an ''"Engaged defensive"'' call to the rest of the package if your flight finds itself engaged by enemy fighters.

A '''directive''' is an order to perform some action. They’re usually given by element-, flight-, or package leaders to their subordinates. However others can also give directives depending on the circumstances. E.g. you are supporting your element leader in a dogfight and you see a bandit about to draw a bead on him, you would then direct your leader to break in concert with you trying to gain a position on the bandit.

== Responding to communications ==

'''Within the flight (VHF)''' when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

'''Between flights (UHF)''', the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

Whenever you start a message not directed toward others you start with your callsign. On package comms where everyone will hear you, you use your full callsign.

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO remain calm and speak clearly!

DO give an "Engaged offensive" call followed by the BRAA or bullseye of the target when in a dogfight.

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture)

DON'T use "over" or "out".

DON'T use "break" to signal a pause. Break is a brevity word to perform a rapid turn.

''These are not the same as the [[:Category:Official Documentation|UO SOPs]] or the [http://forums.unitedoperations.net/index.php/topic/15344-uoaf-sops UOAF SOPs], which are the rules of the community. You've read [[:Category:Official Documentation|the rules]], right?''

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''first''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"'''Lobo 2''' to Panther 1 engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are commiting to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"'''Lobo 2''', Panther 1"}}

Indiciating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{red|"Panther 1,''' Lobo 2'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1-1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CHERUBS || Hundreds of feet above ground level. (“CHERUBS 3” means 300 feet AGL)<ref>CHERUBS '''only''' means altitude above ground level, and is not to be used as a general codeword for hundreds of feet. Saying "ANGELS 20 CHERUBS 3" when meaning 20300 feet MSL is not allowed.</ref>
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| CRANK [left/right] || Turn as far as possible left or right while keeping the target on your radar
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FENCE IN || Directive to prepare your aircraft for battle. See UOAF SOP Section
|-
| FLOW [direction] || Turn to and fly in the designated heading
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| JOKER || Prebriefed fuel remaining when you should start heading home
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| LOW
| Below 10,000 feet MSL
|-
| MAGNUM || With direction and type of target. Anti-radiation weapon launched
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).
|-
| MUD || RWR indication of SAM or AAA radar
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO FACTOR || Not a threat
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCH(ING)
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER'''
| Informative call of an RWR indication of SAM launch.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}

=Final Reminders=

For a "complete" list of brevity terms, see '''OPERATIONAL BREVITY WORDS, DEFINITIONS, AND COUNTERAIR (AFTTP 3-1.1).pdf''' in the ''/docs/Operational Manuals/'' folder of your falcon install.
:
==== ABCs ====
When communicating, especially in a combat situation, remember the ABCs of radio protocol:

'''Accuracy'''

Make sure what you are saying is accurate and think about what you need to say before you broadcast.

'''Brevity'''

Be brief and use brevity terms as much as possible. In a hectic situation there’s a lot of information that needs to be transmitted and processed, and only one person can talk on the radio at a time.

'''Clarity'''

Speak clearly and slowly enough that other people can understand you. The last part is particularly important if you’re not a native english speaker or speaking to a non-native speaker.
{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-18T21:38:09Z

Lexi: /* Learning Files */

{{wip}}

[[File:F16-pilot.jpg||none|500px|left|]] 

== Learning Objectives ==
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
* [http://www.krauselabs.net/dump/Us_Marine_Corps---Multi_Service_Brevity_Codes_Mcrp_3-25B.pdf MULTI-SERVICE BREVITY CODES ]
*[https://www.youtube.com/watch?v=IgdzvQ-YBng Example 1]
*[https://www.youtube.com/watch?v=zT1Dn91c9Zw Example 2]
*[https://www.youtube.com/watch?v=Yknk7uO51UU Example 3]
*[https://www.youtube.com/watch?v=PTtsCXTHHNU Example 4]
*[https://www.youtube.com/watch?v=2uh4yMAx2UA F-16 dodging 6 Iraqi SAM launches on Jan 19 1991]
*[https://en.wikipedia.org/wiki/Brevity_code Brevity_code]

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively (less important), this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate critical messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

==== Definitions ====
: '''Ship''': Single aircraft.
: '''Element''': Two ships working in tandem. This is the basic combat unit.
: '''Flight''': Two elements working in tandem. (Sometimes you can have three-ship flights).
: '''Package''': Two or more flights tasked with accomplishing a single mission.

====Types of radio messages====
There are two (main) kinds of messages: ''Advisories'' and ''directives''. 
An '''advisory''' is a message where you state what you are doing or intending to do. It is particularly important to remember if you're a flight lead or element lead to let other flights know when you're being engaged, or if you're engaging someone, or if you're running away from something.
Advisories do not need to be acknowledged, although they can be.

Examples:
* The flight lead can call out his altitude and speed when climbing from take-off to let his flight know if they’re going to fast or lagging behind.
* Giving an ''"IN"'' call when attacking a ground target.
* Giving an ''"Engaged defensive"'' call to the rest of the package if your flight finds itself engaged by enemy fighters.

A '''directive''' is an order to perform some action. They’re usually given by element-, flight-, or package leaders to their subordinates. However others can also give directives depending on the circumstances. E.g. you are supporting your element leader in a dogfight and you see a bandit about to draw a bead on him, you would then direct your leader to break in concert with you trying to gain a position on the bandit.

== Responding to communications ==

'''Within the flight (VHF)''' when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

'''Between flights (UHF)''', the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

Whenever you start a message not directed toward others you start with your callsign. On package comms where everyone will hear you, you use your full callsign.

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO remain calm and speak clearly!

DO give an "Engaged offensive" call followed by the BRAA or bullseye of the target when in a dogfight.

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture)

DON'T use "over" or "out".

DON'T use "break" to signal a pause. Break is a brevity word to perform a rapid turn.

''These are not the same as the [[:Category:Official Documentation|UO SOPs]] or the [http://forums.unitedoperations.net/index.php/topic/15344-uoaf-sops UOAF SOPs], which are the rules of the community. You've read [[:Category:Official Documentation|the rules]], right?''

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''first''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"'''Lobo 2''' to Panther 1 engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are commiting to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"'''Lobo 2''', Panther 1"}}

Indiciating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{red|"Panther 1,''' Lobo 2'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1-1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CHERUBS || Hundreds of feet above ground level. (“CHERUBS 3” means 300 feet AGL)<ref>CHERUBS '''only''' means altitude above ground level, and is not to be used as a general codeword for hundreds of feet. Saying "ANGELS 20 CHERUBS 3" when meaning 20300 feet MSL is not allowed.</ref>
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| CRANK [left/right] || Turn as far as possible left or right while keeping the target on your radar
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FENCE IN || Directive to prepare your aircraft for battle. See UOAF SOP Section
|-
| FLOW [direction] || Turn to and fly in the designated heading
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| JOKER || Prebriefed fuel remaining when you should start heading home
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| LOW
| Below 10,000 feet MSL
|-
| MAGNUM || With direction and type of target. Anti-radiation weapon launched
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).
|-
| MUD || RWR indication of SAM or AAA radar
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO FACTOR || Not a threat
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCH(ING)
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER'''
| Informative call of an RWR indication of SAM launch.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}

=Final Reminders=

For a "complete" list of brevity terms, see '''OPERATIONAL BREVITY WORDS, DEFINITIONS, AND COUNTERAIR (AFTTP 3-1.1).pdf''' in the ''/docs/Operational Manuals/'' folder of your falcon install.
:
==== ABCs ====
When communicating, especially in a combat situation, remember the ABCs of radio protocol:

'''Accuracy'''

Make sure what you are saying is accurate and think about what you need to say before you broadcast.

'''Brevity'''

Be brief and use brevity terms as much as possible. In a hectic situation there’s a lot of information that needs to be transmitted and processed, and only one person can talk on the radio at a time.

'''Clarity'''

Speak clearly and slowly enough that other people can understand you. The last part is particularly important if you’re not a native english speaker or speaking to a non-native speaker.
{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-18T21:37:10Z

Lexi: /* Final Reminders */

{{wip}}

[[File:F16-pilot.jpg||none|500px|left|]] 

== Learning Objectives ==
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
* [http://www.krauselabs.net/dump/Us_Marine_Corps---Multi_Service_Brevity_Codes_Mcrp_3-25B.pdf MULTI-SERVICE BREVITY CODES ]
*[https://www.youtube.com/watch?v=IgdzvQ-YBng Example 1]
*[https://www.youtube.com/watch?v=zT1Dn91c9Zw Example 2]
*[https://www.youtube.com/watch?v=Yknk7uO51UU Example 3]
*[https://www.youtube.com/watch?v=PTtsCXTHHNU Example 4]
*[https://www.youtube.com/watch?v=Eee2jXIksCs BMS Falcon Another day in the office]
*[https://www.youtube.com/watch?v=2uh4yMAx2UA F-16 dodging 6 Iraqi SAM launches on Jan 19 1991]
*[https://en.wikipedia.org/wiki/Brevity_code Brevity_code]

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively (less important), this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate critical messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

==== Definitions ====
: '''Ship''': Single aircraft.
: '''Element''': Two ships working in tandem. This is the basic combat unit.
: '''Flight''': Two elements working in tandem. (Sometimes you can have three-ship flights).
: '''Package''': Two or more flights tasked with accomplishing a single mission.

====Types of radio messages====
There are two (main) kinds of messages: ''Advisories'' and ''directives''. 
An '''advisory''' is a message where you state what you are doing or intending to do. It is particularly important to remember if you're a flight lead or element lead to let other flights know when you're being engaged, or if you're engaging someone, or if you're running away from something.
Advisories do not need to be acknowledged, although they can be.

Examples:
* The flight lead can call out his altitude and speed when climbing from take-off to let his flight know if they’re going to fast or lagging behind.
* Giving an ''"IN"'' call when attacking a ground target.
* Giving an ''"Engaged defensive"'' call to the rest of the package if your flight finds itself engaged by enemy fighters.

A '''directive''' is an order to perform some action. They’re usually given by element-, flight-, or package leaders to their subordinates. However others can also give directives depending on the circumstances. E.g. you are supporting your element leader in a dogfight and you see a bandit about to draw a bead on him, you would then direct your leader to break in concert with you trying to gain a position on the bandit.

== Responding to communications ==

'''Within the flight (VHF)''' when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

'''Between flights (UHF)''', the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

Whenever you start a message not directed toward others you start with your callsign. On package comms where everyone will hear you, you use your full callsign.

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO remain calm and speak clearly!

DO give an "Engaged offensive" call followed by the BRAA or bullseye of the target when in a dogfight.

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture)

DON'T use "over" or "out".

DON'T use "break" to signal a pause. Break is a brevity word to perform a rapid turn.

''These are not the same as the [[:Category:Official Documentation|UO SOPs]] or the [http://forums.unitedoperations.net/index.php/topic/15344-uoaf-sops UOAF SOPs], which are the rules of the community. You've read [[:Category:Official Documentation|the rules]], right?''

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''first''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"'''Lobo 2''' to Panther 1 engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are commiting to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"'''Lobo 2''', Panther 1"}}

Indiciating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{red|"Panther 1,''' Lobo 2'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1-1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CHERUBS || Hundreds of feet above ground level. (“CHERUBS 3” means 300 feet AGL)<ref>CHERUBS '''only''' means altitude above ground level, and is not to be used as a general codeword for hundreds of feet. Saying "ANGELS 20 CHERUBS 3" when meaning 20300 feet MSL is not allowed.</ref>
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| CRANK [left/right] || Turn as far as possible left or right while keeping the target on your radar
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FENCE IN || Directive to prepare your aircraft for battle. See UOAF SOP Section
|-
| FLOW [direction] || Turn to and fly in the designated heading
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| JOKER || Prebriefed fuel remaining when you should start heading home
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| LOW
| Below 10,000 feet MSL
|-
| MAGNUM || With direction and type of target. Anti-radiation weapon launched
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).
|-
| MUD || RWR indication of SAM or AAA radar
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO FACTOR || Not a threat
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCH(ING)
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER'''
| Informative call of an RWR indication of SAM launch.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}

=Final Reminders=

For a "complete" list of brevity terms, see '''OPERATIONAL BREVITY WORDS, DEFINITIONS, AND COUNTERAIR (AFTTP 3-1.1).pdf''' in the ''/docs/Operational Manuals/'' folder of your falcon install.
:
==== ABCs ====
When communicating, especially in a combat situation, remember the ABCs of radio protocol:

'''Accuracy'''

Make sure what you are saying is accurate and think about what you need to say before you broadcast.

'''Brevity'''

Be brief and use brevity terms as much as possible. In a hectic situation there’s a lot of information that needs to be transmitted and processed, and only one person can talk on the radio at a time.

'''Clarity'''

Speak clearly and slowly enough that other people can understand you. The last part is particularly important if you’re not a native english speaker or speaking to a non-native speaker.
{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-18T21:34:21Z

Lexi: /* Do's and Don'ts */

{{wip}}

[[File:F16-pilot.jpg||none|500px|left|]] 

== Learning Objectives ==
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
* [http://www.krauselabs.net/dump/Us_Marine_Corps---Multi_Service_Brevity_Codes_Mcrp_3-25B.pdf MULTI-SERVICE BREVITY CODES ]
*[https://www.youtube.com/watch?v=IgdzvQ-YBng Example 1]
*[https://www.youtube.com/watch?v=zT1Dn91c9Zw Example 2]
*[https://www.youtube.com/watch?v=Yknk7uO51UU Example 3]
*[https://www.youtube.com/watch?v=PTtsCXTHHNU Example 4]
*[https://www.youtube.com/watch?v=Eee2jXIksCs BMS Falcon Another day in the office]
*[https://www.youtube.com/watch?v=2uh4yMAx2UA F-16 dodging 6 Iraqi SAM launches on Jan 19 1991]
*[https://en.wikipedia.org/wiki/Brevity_code Brevity_code]

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively (less important), this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate critical messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

==== Definitions ====
: '''Ship''': Single aircraft.
: '''Element''': Two ships working in tandem. This is the basic combat unit.
: '''Flight''': Two elements working in tandem. (Sometimes you can have three-ship flights).
: '''Package''': Two or more flights tasked with accomplishing a single mission.

====Types of radio messages====
There are two (main) kinds of messages: ''Advisories'' and ''directives''. 
An '''advisory''' is a message where you state what you are doing or intending to do. It is particularly important to remember if you're a flight lead or element lead to let other flights know when you're being engaged, or if you're engaging someone, or if you're running away from something.
Advisories do not need to be acknowledged, although they can be.

Examples:
* The flight lead can call out his altitude and speed when climbing from take-off to let his flight know if they’re going to fast or lagging behind.
* Giving an ''"IN"'' call when attacking a ground target.
* Giving an ''"Engaged defensive"'' call to the rest of the package if your flight finds itself engaged by enemy fighters.

A '''directive''' is an order to perform some action. They’re usually given by element-, flight-, or package leaders to their subordinates. However others can also give directives depending on the circumstances. E.g. you are supporting your element leader in a dogfight and you see a bandit about to draw a bead on him, you would then direct your leader to break in concert with you trying to gain a position on the bandit.

== Responding to communications ==

'''Within the flight (VHF)''' when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

'''Between flights (UHF)''', the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

Whenever you start a message not directed toward others you start with your callsign. On package comms where everyone will hear you, you use your full callsign.

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO remain calm and speak clearly!

DO give an "Engaged offensive" call followed by the BRAA or bullseye of the target when in a dogfight.

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture)

DON'T use "over" or "out".

DON'T use "break" to signal a pause. Break is a brevity word to perform a rapid turn.

''These are not the same as the [[:Category:Official Documentation|UO SOPs]] or the [http://forums.unitedoperations.net/index.php/topic/15344-uoaf-sops UOAF SOPs], which are the rules of the community. You've read [[:Category:Official Documentation|the rules]], right?''

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''first''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"'''Lobo 2''' to Panther 1 engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are commiting to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"'''Lobo 2''', Panther 1"}}

Indiciating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{red|"Panther 1,''' Lobo 2'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1-1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CHERUBS || Hundreds of feet above ground level. (“CHERUBS 3” means 300 feet AGL)<ref>CHERUBS '''only''' means altitude above ground level, and is not to be used as a general codeword for hundreds of feet. Saying "ANGELS 20 CHERUBS 3" when meaning 20300 feet MSL is not allowed.</ref>
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| CRANK [left/right] || Turn as far as possible left or right while keeping the target on your radar
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FENCE IN || Directive to prepare your aircraft for battle. See UOAF SOP Section
|-
| FLOW [direction] || Turn to and fly in the designated heading
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| JOKER || Prebriefed fuel remaining when you should start heading home
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| LOW
| Below 10,000 feet MSL
|-
| MAGNUM || With direction and type of target. Anti-radiation weapon launched
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).
|-
| MUD || RWR indication of SAM or AAA radar
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO FACTOR || Not a threat
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCH(ING)
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER'''
| Informative call of an RWR indication of SAM launch.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}

=Final Reminders=

'''Brevity terms'''

For a "complete" list, see '''OPERATIONAL BREVITY WORDS, DEFINITIONS, AND COUNTERAIR (AFTTP 3-1.1).pdf''' in the ''/docs/Operational Manuals/'' folder of your falcon install.
:
==== ABCs ====
When communicating, especially in a combat situation, remember the ABCs of radio protocol:
; Accuracy
:: Make sure what you are saying is accurate and think about what you need to say before you broadcast.
:; Brevity
:: Be brief and use brevity terms as much as possible. In a hectic situation there’s a lot of information that needs to be transmitted and processed, and only one person can talk on the radio at a time.
:; Clarity
:: Speak clearly and slowly enough that other people can understand you. The last part is particularly important if you’re not a native english speaker or speaking to a non-native speaker.

{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-18T21:32:41Z

Lexi: /* Types of radio messages= */

{{wip}}

[[File:F16-pilot.jpg||none|500px|left|]] 

== Learning Objectives ==
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
* [http://www.krauselabs.net/dump/Us_Marine_Corps---Multi_Service_Brevity_Codes_Mcrp_3-25B.pdf MULTI-SERVICE BREVITY CODES ]
*[https://www.youtube.com/watch?v=IgdzvQ-YBng Example 1]
*[https://www.youtube.com/watch?v=zT1Dn91c9Zw Example 2]
*[https://www.youtube.com/watch?v=Yknk7uO51UU Example 3]
*[https://www.youtube.com/watch?v=PTtsCXTHHNU Example 4]
*[https://www.youtube.com/watch?v=Eee2jXIksCs BMS Falcon Another day in the office]
*[https://www.youtube.com/watch?v=2uh4yMAx2UA F-16 dodging 6 Iraqi SAM launches on Jan 19 1991]
*[https://en.wikipedia.org/wiki/Brevity_code Brevity_code]

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively (less important), this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate critical messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

==== Definitions ====
: '''Ship''': Single aircraft.
: '''Element''': Two ships working in tandem. This is the basic combat unit.
: '''Flight''': Two elements working in tandem. (Sometimes you can have three-ship flights).
: '''Package''': Two or more flights tasked with accomplishing a single mission.

====Types of radio messages====
There are two (main) kinds of messages: ''Advisories'' and ''directives''. 
An '''advisory''' is a message where you state what you are doing or intending to do. It is particularly important to remember if you're a flight lead or element lead to let other flights know when you're being engaged, or if you're engaging someone, or if you're running away from something.
Advisories do not need to be acknowledged, although they can be.

Examples:
* The flight lead can call out his altitude and speed when climbing from take-off to let his flight know if they’re going to fast or lagging behind.
* Giving an ''"IN"'' call when attacking a ground target.
* Giving an ''"Engaged defensive"'' call to the rest of the package if your flight finds itself engaged by enemy fighters.

A '''directive''' is an order to perform some action. They’re usually given by element-, flight-, or package leaders to their subordinates. However others can also give directives depending on the circumstances. E.g. you are supporting your element leader in a dogfight and you see a bandit about to draw a bead on him, you would then direct your leader to break in concert with you trying to gain a position on the bandit.

== Responding to communications ==

'''Within the flight (VHF)''' when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

'''Between flights (UHF)''', the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

Whenever you start a message not directed toward others you start with your callsign. On package comms where everyone will hear you, you use your full callsign.

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO remain calm and speak clearly!

DO give an "Engaged offensive" call followed by the BRAA or bullseye of the target when in a dogfight.

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture)

DON'T use "over" or "out".

DON'T use "break" to signal a pause. Break is a brevity word to perform a rapid turn.

Note that these are not the same as the [[:Category:Official Documentation|UO SOPs]] or the [http://forums.unitedoperations.net/index.php/topic/15344-uoaf-sops UOAF SOPs], which are the rules of the community.

You've read [[:Category:Official Documentation|the rules]], right?

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''first''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"'''Lobo 2''' to Panther 1 engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are commiting to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"'''Lobo 2''', Panther 1"}}

Indiciating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{red|"Panther 1,''' Lobo 2'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1-1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CHERUBS || Hundreds of feet above ground level. (“CHERUBS 3” means 300 feet AGL)<ref>CHERUBS '''only''' means altitude above ground level, and is not to be used as a general codeword for hundreds of feet. Saying "ANGELS 20 CHERUBS 3" when meaning 20300 feet MSL is not allowed.</ref>
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| CRANK [left/right] || Turn as far as possible left or right while keeping the target on your radar
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FENCE IN || Directive to prepare your aircraft for battle. See UOAF SOP Section
|-
| FLOW [direction] || Turn to and fly in the designated heading
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| JOKER || Prebriefed fuel remaining when you should start heading home
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| LOW
| Below 10,000 feet MSL
|-
| MAGNUM || With direction and type of target. Anti-radiation weapon launched
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).
|-
| MUD || RWR indication of SAM or AAA radar
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO FACTOR || Not a threat
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCH(ING)
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER'''
| Informative call of an RWR indication of SAM launch.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}

=Final Reminders=

'''Brevity terms'''

For a "complete" list, see '''OPERATIONAL BREVITY WORDS, DEFINITIONS, AND COUNTERAIR (AFTTP 3-1.1).pdf''' in the ''/docs/Operational Manuals/'' folder of your falcon install.
:
==== ABCs ====
When communicating, especially in a combat situation, remember the ABCs of radio protocol:
; Accuracy
:: Make sure what you are saying is accurate and think about what you need to say before you broadcast.
:; Brevity
:: Be brief and use brevity terms as much as possible. In a hectic situation there’s a lot of information that needs to be transmitted and processed, and only one person can talk on the radio at a time.
:; Clarity
:: Speak clearly and slowly enough that other people can understand you. The last part is particularly important if you’re not a native english speaker or speaking to a non-native speaker.

{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-18T21:31:39Z

Lexi:

{{wip}}

[[File:F16-pilot.jpg||none|500px|left|]] 

== Learning Objectives ==
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
* [http://www.krauselabs.net/dump/Us_Marine_Corps---Multi_Service_Brevity_Codes_Mcrp_3-25B.pdf MULTI-SERVICE BREVITY CODES ]
*[https://www.youtube.com/watch?v=IgdzvQ-YBng Example 1]
*[https://www.youtube.com/watch?v=zT1Dn91c9Zw Example 2]
*[https://www.youtube.com/watch?v=Yknk7uO51UU Example 3]
*[https://www.youtube.com/watch?v=PTtsCXTHHNU Example 4]
*[https://www.youtube.com/watch?v=Eee2jXIksCs BMS Falcon Another day in the office]
*[https://www.youtube.com/watch?v=2uh4yMAx2UA F-16 dodging 6 Iraqi SAM launches on Jan 19 1991]
*[https://en.wikipedia.org/wiki/Brevity_code Brevity_code]

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively (less important), this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate critical messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

==== Definitions ====
: '''Ship''': Single aircraft.
: '''Element''': Two ships working in tandem. This is the basic combat unit.
: '''Flight''': Two elements working in tandem. (Sometimes you can have three-ship flights).
: '''Package''': Two or more flights tasked with accomplishing a single mission.

====Types of radio messages=====
There are two (main) kinds of messages: ''Advisories'' and ''directives''. 
An '''advisory''' is a message where you state what you are doing or intending to do. It is particularly important to remember if you're a flight lead or element lead to let other flights know when you're being engaged, or if you're engaging someone, or if you're running away from something.
Advisories do not need to be acknowledged, although they can be.

Examples:
* The flight lead can call out his altitude and speed when climbing from take-off to let his flight know if they’re going to fast or lagging behind.
* Giving an ''"IN"'' call when attacking a ground target.
* Giving an ''"Engaged defensive"'' call to the rest of the package if your flight finds itself engaged by enemy fighters.

A '''directive''' is an order to perform some action. They’re usually given by element-, flight-, or package leaders to their subordinates. However others can also give directives depending on the circumstances. E.g. you are supporting your element leader in a dogfight and you see a bandit about to draw a bead on him, you would then direct your leader to break in concert with you trying to gain a position on the bandit.

== Responding to communications ==

'''Within the flight (VHF)''' when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

'''Between flights (UHF)''', the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

Whenever you start a message not directed toward others you start with your callsign. On package comms where everyone will hear you, you use your full callsign.

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO remain calm and speak clearly!

DO give an "Engaged offensive" call followed by the BRAA or bullseye of the target when in a dogfight.

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture)

DON'T use "over" or "out".

DON'T use "break" to signal a pause. Break is a brevity word to perform a rapid turn.

Note that these are not the same as the [[:Category:Official Documentation|UO SOPs]] or the [http://forums.unitedoperations.net/index.php/topic/15344-uoaf-sops UOAF SOPs], which are the rules of the community.

You've read [[:Category:Official Documentation|the rules]], right?

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''first''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"'''Lobo 2''' to Panther 1 engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are commiting to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"'''Lobo 2''', Panther 1"}}

Indiciating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{red|"Panther 1,''' Lobo 2'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1-1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CHERUBS || Hundreds of feet above ground level. (“CHERUBS 3” means 300 feet AGL)<ref>CHERUBS '''only''' means altitude above ground level, and is not to be used as a general codeword for hundreds of feet. Saying "ANGELS 20 CHERUBS 3" when meaning 20300 feet MSL is not allowed.</ref>
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| CRANK [left/right] || Turn as far as possible left or right while keeping the target on your radar
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FENCE IN || Directive to prepare your aircraft for battle. See UOAF SOP Section
|-
| FLOW [direction] || Turn to and fly in the designated heading
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| JOKER || Prebriefed fuel remaining when you should start heading home
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| LOW
| Below 10,000 feet MSL
|-
| MAGNUM || With direction and type of target. Anti-radiation weapon launched
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).
|-
| MUD || RWR indication of SAM or AAA radar
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO FACTOR || Not a threat
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCH(ING)
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER'''
| Informative call of an RWR indication of SAM launch.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}

=Final Reminders=

'''Brevity terms'''

For a "complete" list, see '''OPERATIONAL BREVITY WORDS, DEFINITIONS, AND COUNTERAIR (AFTTP 3-1.1).pdf''' in the ''/docs/Operational Manuals/'' folder of your falcon install.
:
==== ABCs ====
When communicating, especially in a combat situation, remember the ABCs of radio protocol:
:; Accuracy
:: Make sure what you are saying is accurate and think about what you need to say before you broadcast.
:; Brevity
:: Be brief and use brevity terms as much as possible. In a hectic situation there’s a lot of information that needs to be transmitted and processed, and only one person can talk on the radio at a time.
:; Clarity
:: Speak clearly and slowly enough that other people can understand you. The last part is particularly important if you’re not a native english speaker or speaking to a non-native speaker.

{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-18T21:28:51Z

Lexi: /* Final Reminders */

{{wip}}

[[File:F16-pilot.jpg||none|500px|left|]] 

== Learning Objectives ==
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
* [http://www.krauselabs.net/dump/Us_Marine_Corps---Multi_Service_Brevity_Codes_Mcrp_3-25B.pdf MULTI-SERVICE BREVITY CODES ]
*[https://www.youtube.com/watch?v=IgdzvQ-YBng Example 1]
*[https://www.youtube.com/watch?v=zT1Dn91c9Zw Example 2]
*[https://www.youtube.com/watch?v=Yknk7uO51UU Example 3]
*[https://www.youtube.com/watch?v=PTtsCXTHHNU Example 4]
*[https://www.youtube.com/watch?v=Eee2jXIksCs BMS Falcon Another day in the office]
*[https://www.youtube.com/watch?v=2uh4yMAx2UA F-16 dodging 6 Iraqi SAM launches on Jan 19 1991]
*[https://en.wikipedia.org/wiki/Brevity_code Brevity_code]

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively (less important), this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate critical messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

==== Definitions ====
: '''Ship''': Single aircraft.
: '''Element''': Two ships working in tandem. This is the basic combat unit.
: '''Flight''': Two elements working in tandem. (Sometimes you can have three-ship flights).
: '''Package''': Two or more flights tasked with accomplishing a single mission.

== Responding to communications ==

'''Within the flight (VHF)''' when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

'''Between flights (UHF)''', the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

Whenever you start a message not directed toward others you start with your callsign. On package comms where everyone will hear you, you use your full callsign.

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO remain calm and speak clearly!

DO give an "Engaged offensive" call followed by the BRAA or bullseye of the target when in a dogfight.

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture)

DON'T use "over" or "out".

DON'T use "break" to signal a pause. Break is a brevity word to perform a rapid turn.

Note that these are not the same as the [[:Category:Official Documentation|UO SOPs]] or the [http://forums.unitedoperations.net/index.php/topic/15344-uoaf-sops UOAF SOPs], which are the rules of the community.

You've read [[:Category:Official Documentation|the rules]], right?

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''first''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"'''Lobo 2''' to Panther 1 engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are commiting to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"'''Lobo 2''', Panther 1"}}

Indiciating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{red|"Panther 1,''' Lobo 2'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1-1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CHERUBS || Hundreds of feet above ground level. (“CHERUBS 3” means 300 feet AGL)<ref>CHERUBS '''only''' means altitude above ground level, and is not to be used as a general codeword for hundreds of feet. Saying "ANGELS 20 CHERUBS 3" when meaning 20300 feet MSL is not allowed.</ref>
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| CRANK [left/right] || Turn as far as possible left or right while keeping the target on your radar
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FENCE IN || Directive to prepare your aircraft for battle. See UOAF SOP Section
|-
| FLOW [direction] || Turn to and fly in the designated heading
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| JOKER || Prebriefed fuel remaining when you should start heading home
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| LOW
| Below 10,000 feet MSL
|-
| MAGNUM || With direction and type of target. Anti-radiation weapon launched
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).
|-
| MUD || RWR indication of SAM or AAA radar
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO FACTOR || Not a threat
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCH(ING)
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER'''
| Informative call of an RWR indication of SAM launch.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}

=Final Reminders=

'''Brevity terms'''

For a "complete" list, see '''OPERATIONAL BREVITY WORDS, DEFINITIONS, AND COUNTERAIR (AFTTP 3-1.1).pdf''' in the ''/docs/Operational Manuals/'' folder of your falcon install.
:
==== ABCs ====
When communicating, especially in a combat situation, remember the ABCs of radio protocol:
:; Accuracy
:: Make sure what you are saying is accurate and think about what you need to say before you broadcast.
:; Brevity
:: Be brief and use brevity terms as much as possible. In a hectic situation there’s a lot of information that needs to be transmitted and processed, and only one person can talk on the radio at a time.
:; Clarity
:: Speak clearly and slowly enough that other people can understand you. The last part is particularly important if you’re not a native english speaker or speaking to a non-native speaker.

=====Types of radio messages=====
There are two (main) kinds of messages: ''Advisories'' and ''directives''. 
An '''advisory''' is a message where you state what you are doing or intending to do. It is particularly important to remember if you're a flight lead or element lead to let other flights know when you're being engaged, or if you're engaging someone, or if you're running away from something.
Advisories do not need to be acknowledged, although they can be.

Examples:
* The flight lead can call out his altitude and speed when climbing from take-off to let his flight know if they’re going to fast or lagging behind.
* Giving an ''"IN"'' call when attacking a ground target.
* Giving an ''"Engaged defensive"'' call to the rest of the package if your flight finds itself engaged by enemy fighters.

A '''directive''' is an order to perform some action. They’re usually given by element-, flight-, or package leaders to their subordinates. However others can also give directives depending on the circumstances. Say you are supporting your element leader in a dogfight, and you see a bandit about to draw a bead on him. You would then direct your leader to break in concert with you trying to gain a position on the bandit.

{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-18T21:24:43Z

Lexi: /* Tinal Reminderso be integrated */

{{wip}}

[[File:F16-pilot.jpg||none|500px|left|]] 

== Learning Objectives ==
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
* [http://www.krauselabs.net/dump/Us_Marine_Corps---Multi_Service_Brevity_Codes_Mcrp_3-25B.pdf MULTI-SERVICE BREVITY CODES ]
*[https://www.youtube.com/watch?v=IgdzvQ-YBng Example 1]
*[https://www.youtube.com/watch?v=zT1Dn91c9Zw Example 2]
*[https://www.youtube.com/watch?v=Yknk7uO51UU Example 3]
*[https://www.youtube.com/watch?v=PTtsCXTHHNU Example 4]
*[https://www.youtube.com/watch?v=Eee2jXIksCs BMS Falcon Another day in the office]
*[https://www.youtube.com/watch?v=2uh4yMAx2UA F-16 dodging 6 Iraqi SAM launches on Jan 19 1991]
*[https://en.wikipedia.org/wiki/Brevity_code Brevity_code]

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively (less important), this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate critical messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

==== Definitions ====
: '''Ship''': Single aircraft.
: '''Element''': Two ships working in tandem. This is the basic combat unit.
: '''Flight''': Two elements working in tandem. (Sometimes you can have three-ship flights).
: '''Package''': Two or more flights tasked with accomplishing a single mission.

== Responding to communications ==

'''Within the flight (VHF)''' when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

'''Between flights (UHF)''', the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

Whenever you start a message not directed toward others you start with your callsign. On package comms where everyone will hear you, you use your full callsign.

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO remain calm and speak clearly!

DO give an "Engaged offensive" call followed by the BRAA or bullseye of the target when in a dogfight.

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture)

DON'T use "over" or "out".

DON'T use "break" to signal a pause. Break is a brevity word to perform a rapid turn.

Note that these are not the same as the [[:Category:Official Documentation|UO SOPs]] or the [http://forums.unitedoperations.net/index.php/topic/15344-uoaf-sops UOAF SOPs], which are the rules of the community.

You've read [[:Category:Official Documentation|the rules]], right?

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''first''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"'''Lobo 2''' to Panther 1 engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are commiting to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"'''Lobo 2''', Panther 1"}}

Indiciating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{red|"Panther 1,''' Lobo 2'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1-1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CHERUBS || Hundreds of feet above ground level. (“CHERUBS 3” means 300 feet AGL)<ref>CHERUBS '''only''' means altitude above ground level, and is not to be used as a general codeword for hundreds of feet. Saying "ANGELS 20 CHERUBS 3" when meaning 20300 feet MSL is not allowed.</ref>
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| CRANK [left/right] || Turn as far as possible left or right while keeping the target on your radar
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FENCE IN || Directive to prepare your aircraft for battle. See UOAF SOP Section
|-
| FLOW [direction] || Turn to and fly in the designated heading
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| JOKER || Prebriefed fuel remaining when you should start heading home
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| LOW
| Below 10,000 feet MSL
|-
| MAGNUM || With direction and type of target. Anti-radiation weapon launched
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).
|-
| MUD || RWR indication of SAM or AAA radar
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO FACTOR || Not a threat
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCH(ING)
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER'''
| Informative call of an RWR indication of SAM launch.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}
 

=Final Reminders=
===Communication===

'''Brevity terms'''

For a complete list, see '''OPERATIONAL BREVITY WORDS, DEFINITIONS, AND COUNTERAIR (AFTTP 3-1.1).pdf''' in the ''/docs/Operational Manuals/'' folder of your falcon install.
:
==== Radio protocol ====

===== ABCs =====
When communicating, especially in a combat situation, remember the ABCs of radio protocol:
:; Accuracy
:: Make sure what you are saying is accurate and think about what you need to say before you broadcast.
:; Brevity
:: Be brief and use brevity terms as much as possible. In a hectic situation there’s a lot of information that needs to be transmitted and processed, and only one person can talk on the radio at a time.
:; Clarity
:: Speak clearly and slowly enough that other people can understand you. The last part is particularly important if you’re not a native english speaker or speaking to a non-native speaker.

=====Types of radio messages=====
There are two (main) kinds of messages: ''Advisories'' and ''directives''. 
An '''advisory''' is a message where you state what you are doing or intending to do. It is particularly important to remember if you're a flight lead or element lead to let other flights know when you're being engaged, or if you're engaging someone, or if you're running away from something.
Advisories do not need to be acknowledged, although they can be.

Examples:
* The flight lead can call out his altitude and speed when climbing from take-off to let his flight know if they’re going to fast or lagging behind.
* Giving an ''"IN"'' call when attacking a ground target.
* Giving an ''"Engaged defensive"'' call to the rest of the package if your flight finds itself engaged by enemy fighters.

A '''directive''' is an order to perform some action. They’re usually given by element-, flight-, or package leaders to their subordinates. However others can also give directives depending on the circumstances. Say you are supporting your element leader in a dogfight, and you see a bandit about to draw a bead on him. You would then direct your leader to break in concert with you trying to gain a position on the bandit.

{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-18T21:24:17Z

Lexi: /* Responding to communications */

{{wip}}

[[File:F16-pilot.jpg||none|500px|left|]] 

== Learning Objectives ==
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
* [http://www.krauselabs.net/dump/Us_Marine_Corps---Multi_Service_Brevity_Codes_Mcrp_3-25B.pdf MULTI-SERVICE BREVITY CODES ]
*[https://www.youtube.com/watch?v=IgdzvQ-YBng Example 1]
*[https://www.youtube.com/watch?v=zT1Dn91c9Zw Example 2]
*[https://www.youtube.com/watch?v=Yknk7uO51UU Example 3]
*[https://www.youtube.com/watch?v=PTtsCXTHHNU Example 4]
*[https://www.youtube.com/watch?v=Eee2jXIksCs BMS Falcon Another day in the office]
*[https://www.youtube.com/watch?v=2uh4yMAx2UA F-16 dodging 6 Iraqi SAM launches on Jan 19 1991]
*[https://en.wikipedia.org/wiki/Brevity_code Brevity_code]

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively (less important), this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate critical messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

==== Definitions ====
: '''Ship''': Single aircraft.
: '''Element''': Two ships working in tandem. This is the basic combat unit.
: '''Flight''': Two elements working in tandem. (Sometimes you can have three-ship flights).
: '''Package''': Two or more flights tasked with accomplishing a single mission.

== Responding to communications ==

'''Within the flight (VHF)''' when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

'''Between flights (UHF)''', the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

Whenever you start a message not directed toward others you start with your callsign. On package comms where everyone will hear you, you use your full callsign.

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO remain calm and speak clearly!

DO give an "Engaged offensive" call followed by the BRAA or bullseye of the target when in a dogfight.

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture)

DON'T use "over" or "out".

DON'T use "break" to signal a pause. Break is a brevity word to perform a rapid turn.

Note that these are not the same as the [[:Category:Official Documentation|UO SOPs]] or the [http://forums.unitedoperations.net/index.php/topic/15344-uoaf-sops UOAF SOPs], which are the rules of the community.

You've read [[:Category:Official Documentation|the rules]], right?

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''first''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"'''Lobo 2''' to Panther 1 engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are commiting to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"'''Lobo 2''', Panther 1"}}

Indiciating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{red|"Panther 1,''' Lobo 2'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1-1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CHERUBS || Hundreds of feet above ground level. (“CHERUBS 3” means 300 feet AGL)<ref>CHERUBS '''only''' means altitude above ground level, and is not to be used as a general codeword for hundreds of feet. Saying "ANGELS 20 CHERUBS 3" when meaning 20300 feet MSL is not allowed.</ref>
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| CRANK [left/right] || Turn as far as possible left or right while keeping the target on your radar
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FENCE IN || Directive to prepare your aircraft for battle. See UOAF SOP Section
|-
| FLOW [direction] || Turn to and fly in the designated heading
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| JOKER || Prebriefed fuel remaining when you should start heading home
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| LOW
| Below 10,000 feet MSL
|-
| MAGNUM || With direction and type of target. Anti-radiation weapon launched
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).
|-
| MUD || RWR indication of SAM or AAA radar
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO FACTOR || Not a threat
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCH(ING)
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER'''
| Informative call of an RWR indication of SAM launch.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}
 

=Tinal Reminderso be integrated=
===Communication===

'''Brevity terms'''

For a complete list, see '''OPERATIONAL BREVITY WORDS, DEFINITIONS, AND COUNTERAIR (AFTTP 3-1.1).pdf''' in the ''/docs/Operational Manuals/'' folder of your falcon install.
:
==== Radio protocol ====

===== ABCs =====
When communicating, especially in a combat situation, remember the ABCs of radio protocol:
:; Accuracy
:: Make sure what you are saying is accurate and think about what you need to say before you broadcast.
:; Brevity
:: Be brief and use brevity terms as much as possible. In a hectic situation there’s a lot of information that needs to be transmitted and processed, and only one person can talk on the radio at a time.
:; Clarity
:: Speak clearly and slowly enough that other people can understand you. The last part is particularly important if you’re not a native english speaker or speaking to a non-native speaker.

=====Types of radio messages=====
There are two (main) kinds of messages: ''Advisories'' and ''directives''. 
An '''advisory''' is a message where you state what you are doing or intending to do. It is particularly important to remember if you're a flight lead or element lead to let other flights know when you're being engaged, or if you're engaging someone, or if you're running away from something.
Advisories do not need to be acknowledged, although they can be.

Examples:
* The flight lead can call out his altitude and speed when climbing from take-off to let his flight know if they’re going to fast or lagging behind.
* Giving an ''"IN"'' call when attacking a ground target.
* Giving an ''"Engaged defensive"'' call to the rest of the package if your flight finds itself engaged by enemy fighters.

A '''directive''' is an order to perform some action. They’re usually given by element-, flight-, or package leaders to their subordinates. However others can also give directives depending on the circumstances. Say you are supporting your element leader in a dogfight, and you see a bandit about to draw a bead on him. You would then direct your leader to break in concert with you trying to gain a position on the bandit.

{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-18T21:18:40Z

Lexi: /* Do's and Don'ts */

{{wip}}

[[File:F16-pilot.jpg||none|500px|left|]] 

== Learning Objectives ==
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
* [http://www.krauselabs.net/dump/Us_Marine_Corps---Multi_Service_Brevity_Codes_Mcrp_3-25B.pdf MULTI-SERVICE BREVITY CODES ]
*[https://www.youtube.com/watch?v=IgdzvQ-YBng Example 1]
*[https://www.youtube.com/watch?v=zT1Dn91c9Zw Example 2]
*[https://www.youtube.com/watch?v=Yknk7uO51UU Example 3]
*[https://www.youtube.com/watch?v=PTtsCXTHHNU Example 4]
*[https://www.youtube.com/watch?v=Eee2jXIksCs BMS Falcon Another day in the office]
*[https://www.youtube.com/watch?v=2uh4yMAx2UA F-16 dodging 6 Iraqi SAM launches on Jan 19 1991]
*[https://en.wikipedia.org/wiki/Brevity_code Brevity_code]

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively (less important), this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate critical messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

==== Definitions ====
: '''Ship''': Single aircraft.
: '''Element''': Two ships working in tandem. This is the basic combat unit.
: '''Flight''': Two elements working in tandem. (Sometimes you can have three-ship flights).
: '''Package''': Two or more flights tasked with accomplishing a single mission.

== Responding to communications ==

===== Basic protocol =====
* Whenever you start a mesage not directed toward others you start with your callsign. On flight comms (where only 3 other players will hear you) you use your number 1-4, on package comms, where everyone will hear you, you use your full callsign.
* Whenever you send a message to someone else, start with their callsign, followed by your callsign. {{Green|"Python 2, this is Serpent 5, anchored at bullseye 040 for 63, awaiting your go"}}.

<nowiki> </nowiki>Within the flight (VHF) when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

Between flights (UHF), the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

* t.

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO remain calm and speak clearly!

DO give an "Engaged offensive" call followed by the BRAA or bullseye of the target when in a dogfight.

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture)

DON'T use "over" or "out".

DON'T use "break" to signal a pause. Break is a brevity word to perform a rapid turn.

Note that these are not the same as the [[:Category:Official Documentation|UO SOPs]] or the [http://forums.unitedoperations.net/index.php/topic/15344-uoaf-sops UOAF SOPs], which are the rules of the community.

You've read [[:Category:Official Documentation|the rules]], right?

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''first''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"'''Lobo 2''' to Panther 1 engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are commiting to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"'''Lobo 2''', Panther 1"}}

Indiciating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{red|"Panther 1,''' Lobo 2'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1-1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CHERUBS || Hundreds of feet above ground level. (“CHERUBS 3” means 300 feet AGL)<ref>CHERUBS '''only''' means altitude above ground level, and is not to be used as a general codeword for hundreds of feet. Saying "ANGELS 20 CHERUBS 3" when meaning 20300 feet MSL is not allowed.</ref>
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| CRANK [left/right] || Turn as far as possible left or right while keeping the target on your radar
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FENCE IN || Directive to prepare your aircraft for battle. See UOAF SOP Section
|-
| FLOW [direction] || Turn to and fly in the designated heading
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| JOKER || Prebriefed fuel remaining when you should start heading home
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| LOW
| Below 10,000 feet MSL
|-
| MAGNUM || With direction and type of target. Anti-radiation weapon launched
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).
|-
| MUD || RWR indication of SAM or AAA radar
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO FACTOR || Not a threat
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCH(ING)
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER'''
| Informative call of an RWR indication of SAM launch.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}
 

=Tinal Reminderso be integrated=
===Communication===

'''Brevity terms'''

For a complete list, see '''OPERATIONAL BREVITY WORDS, DEFINITIONS, AND COUNTERAIR (AFTTP 3-1.1).pdf''' in the ''/docs/Operational Manuals/'' folder of your falcon install.
:
==== Radio protocol ====

===== ABCs =====
When communicating, especially in a combat situation, remember the ABCs of radio protocol:
:; Accuracy
:: Make sure what you are saying is accurate and think about what you need to say before you broadcast.
:; Brevity
:: Be brief and use brevity terms as much as possible. In a hectic situation there’s a lot of information that needs to be transmitted and processed, and only one person can talk on the radio at a time.
:; Clarity
:: Speak clearly and slowly enough that other people can understand you. The last part is particularly important if you’re not a native english speaker or speaking to a non-native speaker.

=====Types of radio messages=====
There are two (main) kinds of messages: ''Advisories'' and ''directives''. 
An '''advisory''' is a message where you state what you are doing or intending to do. It is particularly important to remember if you're a flight lead or element lead to let other flights know when you're being engaged, or if you're engaging someone, or if you're running away from something.
Advisories do not need to be acknowledged, although they can be.

Examples:
* The flight lead can call out his altitude and speed when climbing from take-off to let his flight know if they’re going to fast or lagging behind.
* Giving an ''"IN"'' call when attacking a ground target.
* Giving an ''"Engaged defensive"'' call to the rest of the package if your flight finds itself engaged by enemy fighters.

A '''directive''' is an order to perform some action. They’re usually given by element-, flight-, or package leaders to their subordinates. However others can also give directives depending on the circumstances. Say you are supporting your element leader in a dogfight, and you see a bandit about to draw a bead on him. You would then direct your leader to break in concert with you trying to gain a position on the bandit.

{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-18T18:03:34Z

Lexi: /* To be integrated */

{{wip}}

[[File:F16-pilot.jpg||none|500px|left|]] 

== Learning Objectives ==
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
* [http://www.krauselabs.net/dump/Us_Marine_Corps---Multi_Service_Brevity_Codes_Mcrp_3-25B.pdf MULTI-SERVICE BREVITY CODES ]
*[https://www.youtube.com/watch?v=IgdzvQ-YBng Example 1]
*[https://www.youtube.com/watch?v=zT1Dn91c9Zw Example 2]
*[https://www.youtube.com/watch?v=Yknk7uO51UU Example 3]
*[https://www.youtube.com/watch?v=PTtsCXTHHNU Example 4]
*[https://www.youtube.com/watch?v=Eee2jXIksCs BMS Falcon Another day in the office]
*[https://www.youtube.com/watch?v=2uh4yMAx2UA F-16 dodging 6 Iraqi SAM launches on Jan 19 1991]
*[https://en.wikipedia.org/wiki/Brevity_code Brevity_code]

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively (less important), this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate critical messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

==== Definitions ====
: '''Ship''': Single aircraft.
: '''Element''': Two ships working in tandem. This is the basic combat unit.
: '''Flight''': Two elements working in tandem. (Sometimes you can have three-ship flights).
: '''Package''': Two or more flights tasked with accomplishing a single mission.

== Responding to communications ==

===== Basic protocol =====
* Whenever you start a mesage not directed toward others you start with your callsign. On flight comms (where only 3 other players will hear you) you use your number 1-4, on package comms, where everyone will hear you, you use your full callsign.
* Whenever you send a message to someone else, start with their callsign, followed by your callsign. {{Green|"Python 2, this is Serpent 5, anchored at bullseye 040 for 63, awaiting your go"}}.

<nowiki> </nowiki>Within the flight (VHF) when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

Between flights (UHF), the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO remain calm and speak clearly!

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture) 
* Don't use "over" or "out".
* Don't use "break" to signal a pause. Break is a brevity word to perform a rapid turn.
* Don't obsess over the brevity terms. If you don't know the terms say it in English, just remember to be clear and concise.
* Whenever lead gives you an order, respond with your callsign - and respond in order, only skip someone's turn if the guy before you did not check in after 5 seconds or so.
* When you’re being attacked give an engaged defensive call (mainly for flight/element leaders).
* When you are attacking give an engaging call followed by the BRAA or bullseye of the target.

Note that these are not the same as the [[:Category:Official Documentation|UO SOPs]] or the [http://forums.unitedoperations.net/index.php/topic/15344-uoaf-sops UOAF SOPs], which are the rules of the community.

You've read [[:Category:Official Documentation|the rules]], right?

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''first''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"'''Lobo 2''' to Panther 1 engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are commiting to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"'''Lobo 2''', Panther 1"}}

Indiciating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{red|"Panther 1,''' Lobo 2'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1-1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CHERUBS || Hundreds of feet above ground level. (“CHERUBS 3” means 300 feet AGL)<ref>CHERUBS '''only''' means altitude above ground level, and is not to be used as a general codeword for hundreds of feet. Saying "ANGELS 20 CHERUBS 3" when meaning 20300 feet MSL is not allowed.</ref>
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| CRANK [left/right] || Turn as far as possible left or right while keeping the target on your radar
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FENCE IN || Directive to prepare your aircraft for battle. See UOAF SOP Section
|-
| FLOW [direction] || Turn to and fly in the designated heading
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| JOKER || Prebriefed fuel remaining when you should start heading home
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| LOW
| Below 10,000 feet MSL
|-
| MAGNUM || With direction and type of target. Anti-radiation weapon launched
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).
|-
| MUD || RWR indication of SAM or AAA radar
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO FACTOR || Not a threat
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCH(ING)
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER'''
| Informative call of an RWR indication of SAM launch.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}
 

=Tinal Reminderso be integrated=
===Communication===

'''Brevity terms'''

For a complete list, see '''OPERATIONAL BREVITY WORDS, DEFINITIONS, AND COUNTERAIR (AFTTP 3-1.1).pdf''' in the ''/docs/Operational Manuals/'' folder of your falcon install.
:
==== Radio protocol ====

===== ABCs =====
When communicating, especially in a combat situation, remember the ABCs of radio protocol:
:; Accuracy
:: Make sure what you are saying is accurate and think about what you need to say before you broadcast.
:; Brevity
:: Be brief and use brevity terms as much as possible. In a hectic situation there’s a lot of information that needs to be transmitted and processed, and only one person can talk on the radio at a time.
:; Clarity
:: Speak clearly and slowly enough that other people can understand you. The last part is particularly important if you’re not a native english speaker or speaking to a non-native speaker.

=====Types of radio messages=====
There are two (main) kinds of messages: ''Advisories'' and ''directives''. 
An '''advisory''' is a message where you state what you are doing or intending to do. It is particularly important to remember if you're a flight lead or element lead to let other flights know when you're being engaged, or if you're engaging someone, or if you're running away from something.
Advisories do not need to be acknowledged, although they can be.

Examples:
* The flight lead can call out his altitude and speed when climbing from take-off to let his flight know if they’re going to fast or lagging behind.
* Giving an ''"IN"'' call when attacking a ground target.
* Giving an ''"Engaged defensive"'' call to the rest of the package if your flight finds itself engaged by enemy fighters.

A '''directive''' is an order to perform some action. They’re usually given by element-, flight-, or package leaders to their subordinates. However others can also give directives depending on the circumstances. Say you are supporting your element leader in a dogfight, and you see a bandit about to draw a bead on him. You would then direct your leader to break in concert with you trying to gain a position on the bandit.

{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-18T18:02:16Z

Lexi: /* Responding to communications */

{{wip}}

[[File:F16-pilot.jpg||none|500px|left|]] 

== Learning Objectives ==
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
* [http://www.krauselabs.net/dump/Us_Marine_Corps---Multi_Service_Brevity_Codes_Mcrp_3-25B.pdf MULTI-SERVICE BREVITY CODES ]
*[https://www.youtube.com/watch?v=IgdzvQ-YBng Example 1]
*[https://www.youtube.com/watch?v=zT1Dn91c9Zw Example 2]
*[https://www.youtube.com/watch?v=Yknk7uO51UU Example 3]
*[https://www.youtube.com/watch?v=PTtsCXTHHNU Example 4]
*[https://www.youtube.com/watch?v=Eee2jXIksCs BMS Falcon Another day in the office]
*[https://www.youtube.com/watch?v=2uh4yMAx2UA F-16 dodging 6 Iraqi SAM launches on Jan 19 1991]
*[https://en.wikipedia.org/wiki/Brevity_code Brevity_code]

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively (less important), this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate critical messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

==== Definitions ====
: '''Ship''': Single aircraft.
: '''Element''': Two ships working in tandem. This is the basic combat unit.
: '''Flight''': Two elements working in tandem. (Sometimes you can have three-ship flights).
: '''Package''': Two or more flights tasked with accomplishing a single mission.

== Responding to communications ==

===== Basic protocol =====
* Whenever you start a mesage not directed toward others you start with your callsign. On flight comms (where only 3 other players will hear you) you use your number 1-4, on package comms, where everyone will hear you, you use your full callsign.
* Whenever you send a message to someone else, start with their callsign, followed by your callsign. {{Green|"Python 2, this is Serpent 5, anchored at bullseye 040 for 63, awaiting your go"}}.

<nowiki> </nowiki>Within the flight (VHF) when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

Between flights (UHF), the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO remain calm and speak clearly!

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture) 
* Don't use "over" or "out".
* Don't use "break" to signal a pause. Break is a brevity word to perform a rapid turn.
* Don't obsess over the brevity terms. If you don't know the terms say it in English, just remember to be clear and concise.
* Whenever lead gives you an order, respond with your callsign - and respond in order, only skip someone's turn if the guy before you did not check in after 5 seconds or so.
* When you’re being attacked give an engaged defensive call (mainly for flight/element leaders).
* When you are attacking give an engaging call followed by the BRAA or bullseye of the target.

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''first''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"'''Lobo 2''' to Panther 1 engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are commiting to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"'''Lobo 2''', Panther 1"}}

Indiciating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{red|"Panther 1,''' Lobo 2'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1-1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CHERUBS || Hundreds of feet above ground level. (“CHERUBS 3” means 300 feet AGL)<ref>CHERUBS '''only''' means altitude above ground level, and is not to be used as a general codeword for hundreds of feet. Saying "ANGELS 20 CHERUBS 3" when meaning 20300 feet MSL is not allowed.</ref>
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| CRANK [left/right] || Turn as far as possible left or right while keeping the target on your radar
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FENCE IN || Directive to prepare your aircraft for battle. See UOAF SOP Section
|-
| FLOW [direction] || Turn to and fly in the designated heading
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| JOKER || Prebriefed fuel remaining when you should start heading home
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| LOW
| Below 10,000 feet MSL
|-
| MAGNUM || With direction and type of target. Anti-radiation weapon launched
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).
|-
| MUD || RWR indication of SAM or AAA radar
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO FACTOR || Not a threat
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCH(ING)
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER'''
| Informative call of an RWR indication of SAM launch.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}
 

=To be integrated=
===Communication===

'''Brevity terms'''

For a complete list, see '''OPERATIONAL BREVITY WORDS, DEFINITIONS, AND COUNTERAIR (AFTTP 3-1.1).pdf''' in the ''/docs/Operational Manuals/'' folder of your falcon install.
:
==== Radio protocol ====

===== ABCs =====
When communicating, especially in a combat situation, remember the ABCs of radio protocol:
:; Accuracy
:: Make sure what you are saying is accurate and think about what you need to say before you broadcast.
:; Brevity
:: Be brief and use brevity terms as much as possible. In a hectic situation there’s a lot of information that needs to be transmitted and processed, and only one person can talk on the radio at a time.
:; Clarity
:: Speak clearly and slowly enough that other people can understand you. The last part is particularly important if you’re not a native english speaker or speaking to a non-native speaker.

=====Types of radio messages=====
There are two (main) kinds of messages: ''Advisories'' and ''directives''. 
An '''advisory''' is a message where you state what you are doing or intending to do. It is particularly important to remember if you're a flight lead or element lead to let other flights know when you're being engaged, or if you're engaging someone, or if you're running away from something.
Advisories do not need to be acknowledged, although they can be.

Examples:
* The flight lead can call out his altitude and speed when climbing from take-off to let his flight know if they’re going to fast or lagging behind.
* Giving an ''"IN"'' call when attacking a ground target.
* Giving an ''"Engaged defensive"'' call to the rest of the package if your flight finds itself engaged by enemy fighters.

A '''directive''' is an order to perform some action. They’re usually given by element-, flight-, or package leaders to their subordinates. However others can also give directives depending on the circumstances. Say you are supporting your element leader in a dogfight, and you see a bandit about to draw a bead on him. You would then direct your leader to break in concert with you trying to gain a position on the bandit.

===Standard Operating Procedures===
This section discusses the "always do"s and "always don't"s when we're playing BMS.

Note that these are not the same as the [[:Category:Official Documentation|UO SOPs]] or the [http://forums.unitedoperations.net/index.php/topic/15344-uoaf-sops UOAF SOPs], which are the rules of the community.

You've read [[:Category:Official Documentation|the rules]], right?

{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-18T18:00:38Z

Lexi: /* To be integrated */

{{wip}}

[[File:F16-pilot.jpg||none|500px|left|]] 

== Learning Objectives ==
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
* [http://www.krauselabs.net/dump/Us_Marine_Corps---Multi_Service_Brevity_Codes_Mcrp_3-25B.pdf MULTI-SERVICE BREVITY CODES ]
*[https://www.youtube.com/watch?v=IgdzvQ-YBng Example 1]
*[https://www.youtube.com/watch?v=zT1Dn91c9Zw Example 2]
*[https://www.youtube.com/watch?v=Yknk7uO51UU Example 3]
*[https://www.youtube.com/watch?v=PTtsCXTHHNU Example 4]
*[https://www.youtube.com/watch?v=Eee2jXIksCs BMS Falcon Another day in the office]
*[https://www.youtube.com/watch?v=2uh4yMAx2UA F-16 dodging 6 Iraqi SAM launches on Jan 19 1991]
*[https://en.wikipedia.org/wiki/Brevity_code Brevity_code]

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively (less important), this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate critical messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

==== Definitions ====
: '''Ship''': Single aircraft.
: '''Element''': Two ships working in tandem. This is the basic combat unit.
: '''Flight''': Two elements working in tandem. (Sometimes you can have three-ship flights).
: '''Package''': Two or more flights tasked with accomplishing a single mission.

== Responding to communications ==

===== Basic protocol =====
* Whenever you start a mesage not directed toward others you start with your callsign. On flight comms (where only 3 other players will hear you) you use your number 1-4, on package comms, where everyone will hear you, you use your full callsign.
* Whenever you send a message to someone else, start with their callsign, followed by your callsign. {{Green|"Python 2, this is Serpent 5, anchored at bullseye 040 for 63, awaiting your go"}}.
* Don't use "over" or "out".
* Don't use "break" to signal a pause. Break is a brevity word to perform a rapid turn.
* Don't obsess over the brevity terms. If you don't know the terms say it in English, just remember to be clear and concise.
* Whenever lead gives you an order, respond with your callsign - and respond in order, only skip someone's turn if the guy before you did not check in after 5 seconds or so.
* When you’re being attacked give an engaged defensive call (mainly for flight/element leaders).
* When you are attacking give an engaging call followed by the BRAA or bullseye of the target.

<nowiki> </nowiki>Within the flight (VHF) when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

Between flights (UHF), the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO remain calm and speak clearly!

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture) 

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''first''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"'''Lobo 2''' to Panther 1 engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are commiting to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"'''Lobo 2''', Panther 1"}}

Indiciating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{red|"Panther 1,''' Lobo 2'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1-1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CHERUBS || Hundreds of feet above ground level. (“CHERUBS 3” means 300 feet AGL)<ref>CHERUBS '''only''' means altitude above ground level, and is not to be used as a general codeword for hundreds of feet. Saying "ANGELS 20 CHERUBS 3" when meaning 20300 feet MSL is not allowed.</ref>
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| CRANK [left/right] || Turn as far as possible left or right while keeping the target on your radar
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FENCE IN || Directive to prepare your aircraft for battle. See UOAF SOP Section
|-
| FLOW [direction] || Turn to and fly in the designated heading
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| JOKER || Prebriefed fuel remaining when you should start heading home
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| LOW
| Below 10,000 feet MSL
|-
| MAGNUM || With direction and type of target. Anti-radiation weapon launched
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).
|-
| MUD || RWR indication of SAM or AAA radar
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO FACTOR || Not a threat
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCH(ING)
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER'''
| Informative call of an RWR indication of SAM launch.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}
 

=To be integrated=
===Communication===

'''Brevity terms'''

For a complete list, see '''OPERATIONAL BREVITY WORDS, DEFINITIONS, AND COUNTERAIR (AFTTP 3-1.1).pdf''' in the ''/docs/Operational Manuals/'' folder of your falcon install.
:
==== Radio protocol ====

===== ABCs =====
When communicating, especially in a combat situation, remember the ABCs of radio protocol:
:; Accuracy
:: Make sure what you are saying is accurate and think about what you need to say before you broadcast.
:; Brevity
:: Be brief and use brevity terms as much as possible. In a hectic situation there’s a lot of information that needs to be transmitted and processed, and only one person can talk on the radio at a time.
:; Clarity
:: Speak clearly and slowly enough that other people can understand you. The last part is particularly important if you’re not a native english speaker or speaking to a non-native speaker.

=====Types of radio messages=====
There are two (main) kinds of messages: ''Advisories'' and ''directives''. 
An '''advisory''' is a message where you state what you are doing or intending to do. It is particularly important to remember if you're a flight lead or element lead to let other flights know when you're being engaged, or if you're engaging someone, or if you're running away from something.
Advisories do not need to be acknowledged, although they can be.

Examples:
* The flight lead can call out his altitude and speed when climbing from take-off to let his flight know if they’re going to fast or lagging behind.
* Giving an ''"IN"'' call when attacking a ground target.
* Giving an ''"Engaged defensive"'' call to the rest of the package if your flight finds itself engaged by enemy fighters.

A '''directive''' is an order to perform some action. They’re usually given by element-, flight-, or package leaders to their subordinates. However others can also give directives depending on the circumstances. Say you are supporting your element leader in a dogfight, and you see a bandit about to draw a bead on him. You would then direct your leader to break in concert with you trying to gain a position on the bandit.

===Standard Operating Procedures===
This section discusses the "always do"s and "always don't"s when we're playing BMS.

Note that these are not the same as the [[:Category:Official Documentation|UO SOPs]] or the [http://forums.unitedoperations.net/index.php/topic/15344-uoaf-sops UOAF SOPs], which are the rules of the community.

You've read [[:Category:Official Documentation|the rules]], right?

{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-18T17:57:43Z

Lexi: /* To be integrated */

{{wip}}

[[File:F16-pilot.jpg||none|500px|left|]] 

== Learning Objectives ==
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
* [http://www.krauselabs.net/dump/Us_Marine_Corps---Multi_Service_Brevity_Codes_Mcrp_3-25B.pdf MULTI-SERVICE BREVITY CODES ]
*[https://www.youtube.com/watch?v=IgdzvQ-YBng Example 1]
*[https://www.youtube.com/watch?v=zT1Dn91c9Zw Example 2]
*[https://www.youtube.com/watch?v=Yknk7uO51UU Example 3]
*[https://www.youtube.com/watch?v=PTtsCXTHHNU Example 4]
*[https://www.youtube.com/watch?v=Eee2jXIksCs BMS Falcon Another day in the office]
*[https://www.youtube.com/watch?v=2uh4yMAx2UA F-16 dodging 6 Iraqi SAM launches on Jan 19 1991]
*[https://en.wikipedia.org/wiki/Brevity_code Brevity_code]

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively (less important), this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate critical messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

== Responding to communications ==
Within the flight (VHF) when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

Between flights (UHF), the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO remain calm and speak clearly!

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture) 

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''first''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"'''Lobo 2''' to Panther 1 engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are commiting to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"'''Lobo 2''', Panther 1"}}

Indiciating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{red|"Panther 1,''' Lobo 2'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1-1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CHERUBS || Hundreds of feet above ground level. (“CHERUBS 3” means 300 feet AGL)<ref>CHERUBS '''only''' means altitude above ground level, and is not to be used as a general codeword for hundreds of feet. Saying "ANGELS 20 CHERUBS 3" when meaning 20300 feet MSL is not allowed.</ref>
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| CRANK [left/right] || Turn as far as possible left or right while keeping the target on your radar
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FENCE IN || Directive to prepare your aircraft for battle. See UOAF SOP Section
|-
| FLOW [direction] || Turn to and fly in the designated heading
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| JOKER || Prebriefed fuel remaining when you should start heading home
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| LOW
| Below 10,000 feet MSL
|-
| MAGNUM || With direction and type of target. Anti-radiation weapon launched
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).
|-
| MUD || RWR indication of SAM or AAA radar
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO FACTOR || Not a threat
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCH(ING)
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER'''
| Informative call of an RWR indication of SAM launch.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}
 

=To be integrated=
===Communication===
====Definitions====

:'''Ship''': Single aircraft.
:'''Element''': Two ships working in tandem. This is the basic combat unit.
:'''Flight''': Two elements working in tandem. (Sometimes you can have three-ship flights).
:'''Package''': Two or more flights tasked with accomplishing a single mission.

'''Brevity terms'''

For a complete list, see '''OPERATIONAL BREVITY WORDS, DEFINITIONS, AND COUNTERAIR (AFTTP 3-1.1).pdf''' in the ''/docs/Operational Manuals/'' folder of your falcon install.

====Radio protocol====
=====ABCs=====
When communicating, especially in a combat situation, remember the ABCs of radio protocol:
;Accuracy: Make sure what you are saying is accurate and think about what you need to say before you broadcast.
;Brevity: Be brief and use brevity terms as much as possible. In a hectic situation there’s a lot of information that needs to be transmitted and processed, and only one person can talk on the radio at a time.
;Clarity: Speak clearly and slowly enough that other people can understand you. The last part is particularly important if you’re not a native english speaker or speaking to a non-native speaker.

=====Basic protocol=====
* Whenever you start a mesage not directed toward others you start with your callsign. On flight comms (where only 3 other players will hear you) you use your number 1-4, on package comms, where everyone will hear you, you use your full callsign.
* Whenever you send a message to someone else, start with their callsign, followed by your callsign. {{Green|"Python 2, this is Serpent 5, anchored at bullseye 040 for 63, awaiting your go"}}.
* Don't use "over" or "out".
* Don't use "break" to signal a pause. Break is a brevity word to perform a rapid turn.
* Don't obsess over the brevity terms. If you don't know the terms say it in English, just remember to be clear and concise.
* Whenever lead gives you an order, respond with your callsign - and respond in order, only skip someone's turn if the guy before you did not check in after 5 seconds or so.
* When you’re being attacked give an engaged defensive call (mainly for flight/element leaders).
* When you are attacking give an engaging call followed by the BRAA or bullseye of the target.

=====Types of radio messages=====
There are two (main) kinds of messages: ''Advisories'' and ''directives''. 
An '''advisory''' is a message where you state what you are doing or intending to do. It is particularly important to remember if you're a flight lead or element lead to let other flights know when you're being engaged, or if you're engaging someone, or if you're running away from something.
Advisories do not need to be acknowledged, although they can be.

Examples:
* The flight lead can call out his altitude and speed when climbing from take-off to let his flight know if they’re going to fast or lagging behind.
* Giving an ''"IN"'' call when attacking a ground target.
* Giving an ''"Engaged defensive"'' call to the rest of the package if your flight finds itself engaged by enemy fighters.

A '''directive''' is an order to perform some action. They’re usually given by element-, flight-, or package leaders to their subordinates. However others can also give directives depending on the circumstances. Say you are supporting your element leader in a dogfight, and you see a bandit about to draw a bead on him. You would then direct your leader to break in concert with you trying to gain a position on the bandit.

===Standard Operating Procedures===
This section discusses the "always do"s and "always don't"s when we're playing BMS.

Note that these are not the same as the [[:Category:Official Documentation|UO SOPs]] or the [http://forums.unitedoperations.net/index.php/topic/15344-uoaf-sops UOAF SOPs], which are the rules of the community.

You've read [[:Category:Official Documentation|the rules]], right?

{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-18T17:53:10Z

Lexi: /* To be integrated */

{{wip}}

[[File:F16-pilot.jpg||none|500px|left|]] 

== Learning Objectives ==
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
* [http://www.krauselabs.net/dump/Us_Marine_Corps---Multi_Service_Brevity_Codes_Mcrp_3-25B.pdf MULTI-SERVICE BREVITY CODES ]
*[https://www.youtube.com/watch?v=IgdzvQ-YBng Example 1]
*[https://www.youtube.com/watch?v=zT1Dn91c9Zw Example 2]
*[https://www.youtube.com/watch?v=Yknk7uO51UU Example 3]
*[https://www.youtube.com/watch?v=PTtsCXTHHNU Example 4]
*[https://www.youtube.com/watch?v=Eee2jXIksCs BMS Falcon Another day in the office]
*[https://www.youtube.com/watch?v=2uh4yMAx2UA F-16 dodging 6 Iraqi SAM launches on Jan 19 1991]
*[https://en.wikipedia.org/wiki/Brevity_code Brevity_code]

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively (less important), this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate critical messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

== Responding to communications ==
Within the flight (VHF) when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

Between flights (UHF), the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO remain calm and speak clearly!

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture) 

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''first''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"'''Lobo 2''' to Panther 1 engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are commiting to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"'''Lobo 2''', Panther 1"}}

Indiciating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{red|"Panther 1,''' Lobo 2'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1-1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CHERUBS || Hundreds of feet above ground level. (“CHERUBS 3” means 300 feet AGL)<ref>CHERUBS '''only''' means altitude above ground level, and is not to be used as a general codeword for hundreds of feet. Saying "ANGELS 20 CHERUBS 3" when meaning 20300 feet MSL is not allowed.</ref>
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| CRANK [left/right] || Turn as far as possible left or right while keeping the target on your radar
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FENCE IN || Directive to prepare your aircraft for battle. See UOAF SOP Section
|-
| FLOW [direction] || Turn to and fly in the designated heading
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| JOKER || Prebriefed fuel remaining when you should start heading home
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| LOW
| Below 10,000 feet MSL
|-
| MAGNUM || With direction and type of target. Anti-radiation weapon launched
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).
|-
| MUD || RWR indication of SAM or AAA radar
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO FACTOR || Not a threat
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCH(ING)
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER'''
| Informative call of an RWR indication of SAM launch.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}
 

=To be integrated=
===Communication===
====Definitions====

:'''Ship''': Single aircraft.
:'''Element''': Two ships working in tandem. This is the basic combat unit.
:'''Flight''': Two elements working in tandem. (Sometimes you can have three-ship flights).
:'''Package''': Two or more flights tasked with accomplishing a single mission.

====Brevity terms====
For a complete list, see '''OPERATIONAL BREVITY WORDS, DEFINITIONS, AND COUNTERAIR (AFTTP 3-1.1).pdf''' in the ''/docs/Operational Manuals/'' folder of your falcon install.

====Radio protocol====
=====ABCs=====
When communicating, especially in a combat situation, remember the ABCs of radio protocol:
;Accuracy: Make sure what you are saying is accurate and think about what you need to say before you broadcast.
;Brevity: Be brief and use brevity terms as much as possible. In a hectic situation there’s a lot of information that needs to be transmitted and processed, and only one person can talk on the radio at a time.
;Clarity: Speak clearly and slowly enough that other people can understand you. The last part is particularly important if you’re not a native english speaker or speaking to a non-native speaker.

=====Basic protocol=====
* Whenever you start a mesage not directed toward others you start with your callsign. On flight comms (where only 3 other players will hear you) you use your number 1-4, on package comms, where everyone will hear you, you use your full callsign.
* Whenever you send a message to someone else, start with their callsign, followed by your callsign. {{Green|"Python 2, this is Serpent 5, anchored at bullseye 040 for 63, awaiting your go"}}.
* Don't use "over" or "out".
* Don't use "break" to signal a pause. Break is a brevity word to perform a rapid turn.
* Don't obsess over the brevity terms. If you don't know the terms say it in English, just remember to be clear and concise.
* Whenever lead gives you an order, respond with your callsign - and respond in order, only skip someone's turn if the guy before you did not check in after 5 seconds or so.
* When you’re being attacked give an engaged defensive call (mainly for flight/element leaders).
* When you are attacking give an engaging call followed by the BRAA or bullseye of the target.

=====Types of radio messages=====
There are two (main) kinds of messages: ''Advisories'' and ''directives''. 
An '''advisory''' is a message where you state what you are doing or intending to do. It is particularly important to remember if you're a flight lead or element lead to let other flights know when you're being engaged, or if you're engaging someone, or if you're running away from something.
Advisories do not need to be acknowledged, although they can be.

Examples:
* The flight lead can call out his altitude and speed when climbing from take-off to let his flight know if they’re going to fast or lagging behind.
* Giving an ''"IN"'' call when attacking a ground target.
* Giving an ''"Engaged defensive"'' call to the rest of the package if your flight finds itself engaged by enemy fighters.

A '''directive''' is an order to perform some action. They’re usually given by element-, flight-, or package leaders to their subordinates. However others can also give directives depending on the circumstances. Say you are supporting your element leader in a dogfight, and you see a bandit about to draw a bead on him. You would then direct your leader to break in concert with you trying to gain a position on the bandit.

===Standard Operating Procedures===
This section discusses the "always do"s and "always don't"s when we're playing BMS.

Note that these are not the same as the [[:Category:Official Documentation|UO SOPs]] or the [http://forums.unitedoperations.net/index.php/topic/15344-uoaf-sops UOAF SOPs], which are the rules of the community.

You've read [[:Category:Official Documentation|the rules]], right?

{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-18T17:52:35Z

Lexi:

{{wip}}

[[File:F16-pilot.jpg||none|500px|left|]] 

== Learning Objectives ==
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
* [http://www.krauselabs.net/dump/Us_Marine_Corps---Multi_Service_Brevity_Codes_Mcrp_3-25B.pdf MULTI-SERVICE BREVITY CODES ]
*[https://www.youtube.com/watch?v=IgdzvQ-YBng Example 1]
*[https://www.youtube.com/watch?v=zT1Dn91c9Zw Example 2]
*[https://www.youtube.com/watch?v=Yknk7uO51UU Example 3]
*[https://www.youtube.com/watch?v=PTtsCXTHHNU Example 4]
*[https://www.youtube.com/watch?v=Eee2jXIksCs BMS Falcon Another day in the office]
*[https://www.youtube.com/watch?v=2uh4yMAx2UA F-16 dodging 6 Iraqi SAM launches on Jan 19 1991]
*[https://en.wikipedia.org/wiki/Brevity_code Brevity_code]

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively (less important), this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate critical messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

== Responding to communications ==
Within the flight (VHF) when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

Between flights (UHF), the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO remain calm and speak clearly!

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture) 

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''first''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"'''Lobo 2''' to Panther 1 engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are commiting to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"'''Lobo 2''', Panther 1"}}

Indiciating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{red|"Panther 1,''' Lobo 2'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1-1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CHERUBS || Hundreds of feet above ground level. (“CHERUBS 3” means 300 feet AGL)<ref>CHERUBS '''only''' means altitude above ground level, and is not to be used as a general codeword for hundreds of feet. Saying "ANGELS 20 CHERUBS 3" when meaning 20300 feet MSL is not allowed.</ref>
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| CRANK [left/right] || Turn as far as possible left or right while keeping the target on your radar
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FENCE IN || Directive to prepare your aircraft for battle. See UOAF SOP Section
|-
| FLOW [direction] || Turn to and fly in the designated heading
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| JOKER || Prebriefed fuel remaining when you should start heading home
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| LOW
| Below 10,000 feet MSL
|-
| MAGNUM || With direction and type of target. Anti-radiation weapon launched
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).
|-
| MUD || RWR indication of SAM or AAA radar
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO FACTOR || Not a threat
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCH(ING)
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER'''
| Informative call of an RWR indication of SAM launch.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}
 

=To be integrated=
===Communication===
====Definitions====

:'''Ship''': Single aircraft.
:'''Element''': Two ships working in tandem. This is the basic combat unit.
:'''Flight''': Two elements working in tandem. (Sometimes you can have three-ship flights).
:'''Package''': Two or more flights tasked with accomplishing a single mission.

====Brevity terms====
For a complete list, see '''OPERATIONAL BREVITY WORDS, DEFINITIONS, AND COUNTERAIR (AFTTP 3-1.1).pdf''' in the ''/docs/Operational Manuals/'' folder of your falcon install.

{| class="wikitable"
! Brevity term || Meaning
|-
| ANGELS || Thousands of feet. (“Angels 20” means 20000 feet)
|-
| ARIZONA || Aircraft out of anti-radiation missiles
|-
| BANDIT || Aircraft confirmed to be hostile
|-
| BINGO || Only enough fuel left to return to base
|-
| BLIND || Can’t see a friendly aircraft. Opposite of VISUAL
|-
| BOGEY || Aircraft of unknown identity (not know if friend/hostile/neutral)
|-
| BREAK [direction] || Do an immediate high-G turn in the specified direction
|-
| BUDDY SPIKE || A friendly is locking you up. Say with your bullseye position
|-
| BUSTER || Go to full throttle without afterburning
|-
| CHECK [direction] || Turn to the designated direction in formation with your element leader
|-
| CHERUBS || Hundreds of feet above ground level. (“CHERUBS 3” means 300 feet AGL)<ref>CHERUBS '''only''' means altitude above ground level, and is not to be used as a general codeword for hundreds of feet. Saying "ANGELS 20 CHERUBS 3" when meaning 20300 feet MSL is not allowed.</ref>
|-
| CONTACT || Sighting a target using sensors (Radar or TGP etc)
|-
| CRANK [left/right] || Turn as far as possible left or right while keeping the target on your radar
|-
| FENCE IN || Directive to prepare your aircraft for battle. See UOAF SOP Section
|-
| FLOW [direction] || Turn to and fly in the designated heading
|-
| FOX [type] || A/A weapon launched
|-
| GATE (or BURNER) || Go to full afterburning throttle
|-
| IN (from heading) || Starting an attack run against a ground target. Opposite of OFF
|-
| JOKER || Prebriefed fuel remaining when you should start heading home
|-
| MAGNUM || With direction and type of target. Anti-radiation weapon launched
|-
| MUD || RWR indication of SAM or AAA radar
|-
| NAILS || RWR indication of an (enemy) aircraft radar
|-
| NAKED || No RWR indications or cannot identify a NAILS/MUD call
|-
| NO FACTOR || Not a threat
|-
| NO JOY || Opposite of TALLY. Can’t see the target
|-
| NOTCH [left/right] || Turn left or right to place the target at your 3 or 9 position.
|-
| OUTLAW || Aircraft that has taken off from a hostile airfield, but not positively identified
|-
| PITBULL || Your AIM-120 AMRAAM has activated its own radar
|-
| PUSH || Switch to the designated radio channel or frequency
|-
| RIFLE || A/G missile (Maverick) launched
|-
| RAYGUN [position] || Request for reply from friendly at given bullseye position and heading
|-
| SAM [direction] || Visual on a SAM in flight
|-
| SINGER [type and direction] || RWR indication of SAM launch
|-
| SPIKE || RWR indication of aircraft radar in tracking mode (locking you up)
|-
| TALLY || Sighting a non-friendly aircraft visually. Opposite of NO JOY
|-
| TUMBLEWEED || You’ve lost situational awareness
|-
| VISUAL || Sighting a friendly aircraft visually. Opposite of BLIND
|-
| WINCHESTER || Out of all ordnance
|}

====Radio protocol====
=====ABCs=====
When communicating, especially in a combat situation, remember the ABCs of radio protocol:
;Accuracy: Make sure what you are saying is accurate and think about what you need to say before you broadcast.
;Brevity: Be brief and use brevity terms as much as possible. In a hectic situation there’s a lot of information that needs to be transmitted and processed, and only one person can talk on the radio at a time.
;Clarity: Speak clearly and slowly enough that other people can understand you. The last part is particularly important if you’re not a native english speaker or speaking to a non-native speaker.

=====Basic protocol=====
* Whenever you start a mesage not directed toward others you start with your callsign. On flight comms (where only 3 other players will hear you) you use your number 1-4, on package comms, where everyone will hear you, you use your full callsign.
* Whenever you send a message to someone else, start with their callsign, followed by your callsign. {{Green|"Python 2, this is Serpent 5, anchored at bullseye 040 for 63, awaiting your go"}}.
* Don't use "over" or "out".
* Don't use "break" to signal a pause. Break is a brevity word to perform a rapid turn.
* Don't obsess over the brevity terms. If you don't know the terms say it in English, just remember to be clear and concise.
* Whenever lead gives you an order, respond with your callsign - and respond in order, only skip someone's turn if the guy before you did not check in after 5 seconds or so.
* When you’re being attacked give an engaged defensive call (mainly for flight/element leaders).
* When you are attacking give an engaging call followed by the BRAA or bullseye of the target.

=====Types of radio messages=====
There are two (main) kinds of messages: ''Advisories'' and ''directives''. 
An '''advisory''' is a message where you state what you are doing or intending to do. It is particularly important to remember if you're a flight lead or element lead to let other flights know when you're being engaged, or if you're engaging someone, or if you're running away from something.
Advisories do not need to be acknowledged, although they can be.

Examples:
* The flight lead can call out his altitude and speed when climbing from take-off to let his flight know if they’re going to fast or lagging behind.
* Giving an ''"IN"'' call when attacking a ground target.
* Giving an ''"Engaged defensive"'' call to the rest of the package if your flight finds itself engaged by enemy fighters.

A '''directive''' is an order to perform some action. They’re usually given by element-, flight-, or package leaders to their subordinates. However others can also give directives depending on the circumstances. Say you are supporting your element leader in a dogfight, and you see a bandit about to draw a bead on him. You would then direct your leader to break in concert with you trying to gain a position on the bandit.

===Standard Operating Procedures===
This section discusses the "always do"s and "always don't"s when we're playing BMS.

Note that these are not the same as the [[:Category:Official Documentation|UO SOPs]] or the [http://forums.unitedoperations.net/index.php/topic/15344-uoaf-sops UOAF SOPs], which are the rules of the community.

You've read [[:Category:Official Documentation|the rules]], right?

{{Nav UOAF}}

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

User:DarkFib3r

2017-03-05T10:23:37Z

Lexi:

Canadian vpilot who has good taste in books/movies and overall nice guy. Acted as an emissary for UOAF since ~2013/2014 visiting other squadrons and spreading the [https://www.youtube.com/watch?v=rDs4-P6P6r0 good word].

User:DarkFib3r

2017-03-05T10:23:08Z

Lexi: Created page with "Canadian vpilot who has good taste in books/movies and overall nice guy. Acted as an emissary for UOAF since ~2013/2014 visiting other squadrons and spreading the good word."

Canadian vpilot who has good taste in books/movies and overall nice guy. Acted as an emissary for UOAF since ~2013/2014 visiting other squadrons and spreading the good word.

Communications and brevity

2017-03-05T10:15:22Z

Lexi: /* Being a good Flight Lead */

{{wip}}

== Learning Objectives ==
#Learn how to use VHF and UHF communications in BMS.
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
''Video Outlining Communications in Combat.''

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively (less important), this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate critical messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

== Responding to communications ==
Within the flight (VHF) when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

Between flights (UHF), the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO remain calm and speak clearly!

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture) 

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''first''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"'''Lobo 2''' to Panther 1 engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are commiting to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"'''Lobo 2''', Panther 1"}}

Indiciating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{red|"Panther 1,''' Lobo 2'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1-1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| LOW
| Below 10,000 feet MSL
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCHING
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER'''
| Informative call of an RWR indication of SAM launch.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}
 

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-05T10:14:55Z

Lexi: /* Being a good Flight Lead */

{{wip}}

== Learning Objectives ==
#Learn how to use VHF and UHF communications in BMS.
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
''Video Outlining Communications in Combat.''

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively (less important), this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate critical messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

== Responding to communications ==
Within the flight (VHF) when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

Between flights (UHF), the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO remain calm and speak clearly!

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture) 

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''first''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"'''Lobo 2''' to Panther 1 engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are commiting to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"'''Lobo 2''', Panther 1"}}

Indiciating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{blue|"Panther 1,''' Lobo 2'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1-1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| LOW
| Below 10,000 feet MSL
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCHING
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER'''
| Informative call of an RWR indication of SAM launch.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}
 

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-05T10:14:36Z

Lexi: /* Being a good Flight Lead */

Communications and brevity

2017-03-05T10:14:14Z

Lexi: /* Being a good Flight Lead */

{{wip}}

== Learning Objectives ==
#Learn how to use VHF and UHF communications in BMS.
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
''Video Outlining Communications in Combat.''

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively (less important), this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate critical messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

== Responding to communications ==
Within the flight (VHF) when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

Between flights (UHF), the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO remain calm and speak clearly!

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture) 

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''first''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"'''Lobo 2''' to Panther 1 engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are commiting to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"'''Lobo 2''', Panther 1"}}

Indiciating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{green|"Panther 1,''' Lobo 2'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1-1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| LOW
| Below 10,000 feet MSL
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCHING
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER'''
| Informative call of an RWR indication of SAM launch.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}
 

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-05T10:14:04Z

Lexi: /* Being a good Flight Lead */

{{wip}}

== Learning Objectives ==
#Learn how to use VHF and UHF communications in BMS.
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
''Video Outlining Communications in Combat.''

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively (less important), this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate critical messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

== Responding to communications ==
Within the flight (VHF) when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

Between flights (UHF), the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO remain calm and speak clearly!

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture) 

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''first''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"'''Lobo 2''' to Panther 1 engaging bandits over steer 5, 20 thousand, nose hot".}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are commiting to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"'''Lobo 2''', Panther 1"}}

Indiciating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{green|"Panther 1,''' Lobo 2'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1-1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| LOW
| Below 10,000 feet MSL
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCHING
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER'''
| Informative call of an RWR indication of SAM launch.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}
 

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-05T10:13:07Z

Lexi: /* Being a good Flight Lead */

{{wip}}

== Learning Objectives ==
#Learn how to use VHF and UHF communications in BMS.
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
''Video Outlining Communications in Combat.''

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively (less important), this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate critical messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

== Responding to communications ==
Within the flight (VHF) when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

Between flights (UHF), the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO remain calm and speak clearly!

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture) 

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''first''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

{{green|"'''Lobo 2''' to Panther 1 engaging bandits over steer 5, 20 thousand, nose hot".}}

In this example we see that''' Lobo 2''' is informing Panther 1 that they are commiting to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

{{green|"'''Lobo 2''', Panther 1"}}

Indiciating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

{{green|"Panther 1,''' Lobo 2'''"}}

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

{{green|"Cowboy 1-1 Go Trail"}}

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| LOW
| Below 10,000 feet MSL
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCHING
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER'''
| Informative call of an RWR indication of SAM launch.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}
 

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-05T10:07:53Z

Lexi: /* Brevity Code Masterlist */

{{wip}}

== Learning Objectives ==
#Learn how to use VHF and UHF communications in BMS.
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
''Video Outlining Communications in Combat.''

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively (less important), this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate critical messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

== Responding to communications ==
Within the flight (VHF) when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

Between flights (UHF), the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO remain calm and speak clearly!

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture) 

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''first''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

"'''Lobo 2''' to Panther 1 engaging bandits over steer 5, 20 thousand, nose hot".

In this example we see that''' Lobo 2''' is informing Panther 1 that they are commiting to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

"'''Lobo 2''', Panther 1"

Indiciating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

"Panther 1,''' Lobo 2'''"

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

"Cowboy 1-1 Go Trail"

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| '''FOX'''
| A-A weapons employment (most should know this one already!) Fox One indicates a [[wikipedia:Semi-active_radar_homing|semi-active radar-guided]] missile (AIM-7), Fox Two indicates an [[wikipedia:Infrared_homing|infrared-guided]] missile (AIM-9) and Fox Three, indicating an [[wikipedia:Active_radar_homing|active radar-guided]] missile (AIM-120/AIM-54)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| LOW
| Below 10,000 feet MSL
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCHING
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER'''
| Informative call of an RWR indication of SAM launch.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}
 

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-05T10:02:01Z

Lexi: /* Responding to communications */

{{wip}}

== Learning Objectives ==
#Learn how to use VHF and UHF communications in BMS.
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
''Video Outlining Communications in Combat.''

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively (less important), this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate critical messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

== Responding to communications ==
Within the flight (VHF) when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

Between flights (UHF), the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "My TrackIR just f***ed up"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO remain calm and speak clearly!

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture) 

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''first''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

"'''Lobo 2''' to Panther 1 engaging bandits over steer 5, 20 thousand, nose hot".

In this example we see that''' Lobo 2''' is informing Panther 1 that they are commiting to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

"'''Lobo 2''', Panther 1"

Indiciating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

"Panther 1,''' Lobo 2'''"

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

"Cowboy 1-1 Go Trail"

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FOX
| A-A weapons employment (most should know this one already!)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| LOW
| Below 10,000 feet MSL
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCHING
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER'''
| Informative call of an RWR indication of SAM launch.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}
 

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-05T10:01:04Z

Lexi: /* Responding to communications */

{{wip}}

== Learning Objectives ==
#Learn how to use VHF and UHF communications in BMS.
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
''Video Outlining Communications in Combat.''

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively (less important), this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate critical messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

== Responding to communications ==
Within the flight (VHF) when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

Between flights (UHF), the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

The flight does not need to respond to any informative calls (e.g. "Falcon 1 traffic 9 o'clock level) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "Traffic 12 o'clock level"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO remain calm and speak clearly!

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture) 

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''first''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

"'''Lobo 2''' to Panther 1 engaging bandits over steer 5, 20 thousand, nose hot".

In this example we see that''' Lobo 2''' is informing Panther 1 that they are commiting to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

"'''Lobo 2''', Panther 1"

Indiciating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

"Panther 1,''' Lobo 2'''"

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

"Cowboy 1-1 Go Trail"

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FOX
| A-A weapons employment (most should know this one already!)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| LOW
| Below 10,000 feet MSL
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCHING
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER'''
| Informative call of an RWR indication of SAM launch.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}
 

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]

Communications and brevity

2017-03-05T09:59:57Z

Lexi: /* Responding to communications */

{{wip}}

== Learning Objectives ==
#Learn how to use VHF and UHF communications in BMS.
#Understand the syntax used when communicating between fighter aircraft.
#Brevity code words. 

=== Learning Files ===
''Video Outlining Communications in Combat.''

== Basic Principles of Brevity ==
* '''Know when to speak (and when to be silent).'''
Pilots should speak up when engaged either defensively (most important) or offensively (less important), this is so the rest of the flight can adjust accordingly to help you out! When in a high-stress environment it becomes more critical that you allow other pilots to communicate critical messages; don't be yapping about your speed and thus step on your flight who are trying to tell you they are in danger!
* '''Know what to say.'''
Pilots should try to get their point across with all the necessary information, avoiding unnecessary fluff. Avoid raising your voice as this tends to escalate the volume of communication and demoralise pilots under stress.
* '''Accuracy and clarity.'''
No-one will mind if you don't know all the brevity words used for every situation. Remain calm, speak clearly and don't clog up the comms!

== Responding to communications ==
Within the flight (VHF) when a flight lead gives a directive the''' entire flight must respond in correct form'''; this is done by giving your flight number and pilots most respond in ascending order (e.g. Cowboy 1-1: "Flight go trail" Cowboy 1-2: "TWO" Cowboy 1-3: "THREE" Cowboy 1-4: "FOUR"). This makes it clear for the flight lead to understand who has heard them and has intent to carry out the order. If someone is silent, it's OK to skip them and allow them to respond later, however the flight lead(s) will be the one to investigate any silence in comms.

When you are unable to carry out the order you should say "unable" and elaborate should the situation require it. In some situations you may find you are engaged offensive or defensive and can add this, i.e. "Unable. Viper 1-4 engaged defensive". The amount of information you give should be reasonable; let the flight know if you're in a dogfight or defending missiles if they don't already.

Between flights (UHF), the flight lead will need to use the flight callsign as an identifier as multiple flights have access to this method of communication (e.g. "Falcon 1, Panther 2 we have entered the AO, looking for targets" "Panther 2, Falcon 1, roger that").

The flight does not need to respond to any informative calls (e.g. "Falcon 1-1, looking for 350 knots, climbing 10 degrees) which differ from directive calls in that the flight is not being requested to take action but merely being given supplemental information to improve flight efficiency and cohesiveness.

Directives e.g. "Flight fence in" , "Element 2 go trail"

Informatives e.g. "My altitude, Angels 10" , "Traffic 12 o'clock level"

== Do's and Don'ts ==
DO speak up if you're in immediate danger!

DO remain calm and speak clearly!

DON'T use "ground combat terms" for Flight Comms (e.g. "Lobo this is Panther, message", "Panther this is Lobo, go ahead, over." "Lobo, be advised you have bandits over the target area time now.", "Panther, we copy all, out.")

DON'T give informatives out during high-workload periods of flight (e.g. talk about your fuel consumption during a furball)

DON'T repeat communications. (e.g. "MAGNUM SA-2, I REPEAT, MAGNUM SA-2).

DON'T comply with a directive that is sure to kill you; you are the best judge of this.

DON'T clog up the communications with pointless information. (e.g. let other flights know about bandits 200 miles away over UHF OR repeatedly ask AWACS for picture) 

== Being a good Flight Lead ==
A good flight lead completes their mission and brings everyone home; to accomplish this it is their responsibility to utilize both elements and all pilots without micromanaging them heavily.

Flight Leads should endeavor to ensure understanding in the pilots in the briefing: pilots must understand the intent of the package and be aware of the threats they must deal with.

Flight Leads are the primary communicator for the flight with other flights in the package, it is their responsibility to update the package with the flight's status as appropriate. The Flight Lead should make sure other flights are aware of their presence (whether on ingress or egress from the target) to avoid collisions and blue-on-blue incidents, however, all pilots are expected to respond to RAYGUN calls over UHF and maintain general Situational Awareness of the rest of the package.

It is important in inter-flight communications that you'' identify your own flight '''first''''', as well as your flight number where appropriate. Communication to other flights does not need to be requested; Flight Leads just give their information accurately and clearly directly over UHF e.g.

"'''Lobo 2''' to Panther 1 engaging bandits over steer 5, 20 thousand, nose hot".

In this example we see that''' Lobo 2''' is informing Panther 1 that they are commiting to bandits over (a presumed shared) steerpoint 5, these bandits are at 20,000ft and are "nose hot" or turned towards''' Lobo 2'''. However, when asking for information it may be courteous to simply ask for a response e.g.

"'''Lobo 2''', Panther 1"

Indiciating that '''Lobo 2''' is requesting Panther 1 to respond, which they would do by saying the reverse:

"Panther 1,''' Lobo 2'''"

Some people may add "go" or "send it" or another addition in order to increase the ''clarity of the response'' by ensuring the other flight understands they are listening.

As a Flight Lead you need to ensure you control the flight's formation;'' ensure you don't fly too fast and create fuel problems for everyone trying to catch up!'' A Flight Lead should know the best formations for the situations that may arise spontaneously but generally formations are discussed during the briefing. The Flight Lead will make a directive to change formation when appropriate e.g.

"Cowboy 1-1 Go Trail"

If no formation call is briefed or directed, assume a Finger 4 formation is in affect.

The Flight Lead must also designate targets for the flight, when this luxury is available to them, the Flight Lead must manage the resources of the flight to ensure all aircraft remain combat effective for as long as possible. Don't be a hero and shoot off all your missiles for one kill, try to designate targets and keep those missiles for more pressing targets.

Other information the Flight Lead must consider communicating to their flight are: MUSIC (ECM jamming), changing steerpoints, calculated airspeed, flight altitude, equipment configuration, Air-to-Air TACAN, Datalink, etc.

== Brevity Code Masterlist ==
{| class="wikitable"
|-
! Term
! Meaning
|-
| '''ANGELS'''
| Height of FRIENDLY aircraft in thousands of feet mean sea level (MSL)
|-
| ARIZONA
| No ARM ordnance remaining. (HARMS for you BMS pilots)
|-
| '''BANDIT'''
| Identified enemy aircraft. Does not neccesarily imply direction or authority to engage.
|-
| BEAMING
| Moving towards a target at a perpendicular angle OR close to radar gimbal limits.
|-
| BINGO
| Fuel state needed for recovery (to RTB)
|-
| BLIND
| No visual contact with friendly aircraft / ground position. Opposite of VISUAL.
|-
| '''BOGEY'''
| Radar or visual contact whose identity is unknown.
|-
| BRAA
| Bearing Range Altitude and Aspect. Aspect only required if other than HOT.
|-
| BREAK
| Directive call to perform an immediate maximum performance 180-degree turn (or as directed) in the indicated direction. Assumes a defensive situation requiring infrared missile defense (IRMD).
|-
| BREVITY
| Radio frequency is becoming saturated/degraded or jammed and briefer transmissions must follow.
|-
| BROKE LOCK
| Advisory call regarding loss of radar/IR lock-on.
|-
| '''BUDDY LOCK'''
| Locked on to a friendly aircraft, often a response to SPIKE or BUDDY SPIKE. Generally a good idea if you identify yourself as well.
|-
| '''BUDDY SPIKE'''
| Friendly aircraft A-A radar track on the RWR, can be a response to RAYGUN or general advisory call. Generally a good idea if you identify yourself as well.
|-
| BUSTER
| Directive call to fly at max continuous speed (Mil power).
|-
| CHECK
| (number, left/right) Turn (number) degrees left or right and maintain new heading.
|-
| CLEAN
| No sensor information on non-friendly aircraft of interest / no visible battle damage.
|-
| CLEARED
| Flight lead response: requested action is authorised.
|-
| CLEARED HOT
| Flight lead response: release of ordinance is authorised.
|-
| COLD
| Essentially means "turned away". Can be used as a direction or description e.g. "Bandit nose cold"
|-
| '''COMMIT'''
| Directive call to intercept.
|-
| CONTACT
| Similar to TALLY, relating specifically to acquisition of target via radar.
|-
| '''DEFENSIVE'''
| The speaker is under attack, moving defensively and unable to support others.
|-
| DELOUSE
| Directive call to detect, identify and engage (if required) unknown aircraft trailing friendly aircraft.
|-
| DOLLY
| LINK-4A/TADIL-C. Aka. "The data link" in BMS
|-
| FADED
| Radar contact (temporally) is lost on a non-friendly aircraft/surface contact and any positional information given is estimated.
|-
| FOX
| A-A weapons employment (most should know this one already!)
|-
| FURBALL
| Known bandits and friendlies in close proximity.
|-
| GATE
| Directive/informative call to fly as quickly as possible, using afterburner/max power.
|-
| GORILLA
| A large force of indeterminable numbers and formation i.e. a metric shit ton.
|-
| HOOK
| (with direction) Directive call to perform an in-place 180-degree turn.
|-
| HOT
| Meaning "turned towards"; the opposite of COLD.
|-
| HOUND DOG
| I see something I want to shoot / I see the target you are referring to.
|-
| JUDY
| Aircrew has radar or visual contact of the correct target, only requires situational awareness information and the weapon director will minimise radio transmissions. In practice, this is an "I got this" call from the flight to an AWACS.
|-
| LOW
| Below 10,000 feet MSL
|-
| '''MILLER TIME'''
| Informative call indicating completion of A-G ordnance delivery. Generally used by the last striker in conjuction with the egress plan. In practice, used by the package lead as an RTB call. "Ducks on a pond" is also used in BMS (and the best RTB call).
|-
| MUSIC
| Electronic radar jamming. E.g. "Flight, music on"
|-
| '''NAILS'''
| (with direction) RWR indication of radar in search. E.g. "Nails 29, left 10" (I have a MiG-29 on my RWR, from my nose left, 10 o'clock)
|-
| NAKED
| No RWR indications.
|-
| NO JOY
| No visual contact with target/landmark, opposite of TALLY.
|-
| NOTCHING
|(Left/Right): Moving on a beam away from the target, usually done to support a radar-guided missile in order to reduce the closure rate whilst maintaining a radar lock.
|-
| OUTLAW
| Similar to Bogey but assumed hostile due to point of origin i.e. unknown aircraft flying from enemy airspace.
|-
| PID
|(Positive Identification) The ability to confirm the nature of a target (friendly hostile) via means that could include by radar or visually (through the TGP or with the MK1 eyeball).
|-
| PITBULL
| AIM-120 missile has reached MPRF active range (gone active).
|-
| PUSH
| Go to designated frequency, no acknowledgement required.
|-
| PLAYTIME
| Amount of time aircraft can remain on station.
|-
| '''RAYGUN'''
| Indicating a radar lock on unknown aircraft. A request for BUDDY SPIDE reply from friendly aircraft.
|-
| RIFLE
| Friendly A-G missile launch.
|-
| ROGER
| Indicates aircrew understands the radio transmission, ''DOES NOT INDICATE COMPLIANCE OR REACTION.''
|-
| ROLEX
| Time adjustment in minutes, references from the original planned time. Plus means later, minus means earlier.
|-
| '''SAM'''
| Visual acquisition of a SAM in flight or SAM launch, should include position and type if known.
|-
| SAUNTER
| Fly at best endurance.
|-
| '''SINGER'''
| Informative call of an RWR indication of SAM launch.
|-
| SORT
| Directive call to assign responsibility within a GROUP; criteria can be met visually, electronically (radar), or both.
|-
| TALLY
| Sighting of a target. Opposite of NO JOY.
|-
| TUMBLEWEED
| Indicates limited situational awareness, NO JOY and BLIND. A request for information.
|-
| '''UNABLE'''
| Cannot comply as requested or directed (preferably with reason if possible).
|-
| UNIFORM
| UHF/AM radio.
|-
| VICTOR
| VHF/AM radio.
|-
| VISUAL
| Sighting of a FRIENDLY aircraft or ground position. Opposite of BLIND.
|-
| WHAT LUCK
| Request for results of mission or tasks.
|-
| WHAT STATE
| Report amount of fuel and missiles. Ammunition and oxygen are reported only when specifically requested or critical. "Weapon state" and "Fuel state" also used at UOAF.
|-
| '''WILCO'''
| Will comply (with received instructions).
|-
| WINCHESTER
| No ordinance remaining.
|}
 

[[Category:UOAF]]
[[Category:UOAF: BMS Codex]]