Close Air Support

Home >> Tactical Guides >> Close Air Support

What is close air support?

Close Air Support (CAS) the direct support of troops on the ground by air assets. It can be done by performed by both fixed wing aircraft and helicopters. Typically, there is an aircraft involved to deliver the weapons, and controller to direct the fire. In general, the Master Arms CAS procedures are, while based on real life concepts, a bit simplified and streamlined. Most notably, we're currently focusing on one single way of doing it, being the Keyhole, Type 2 procedure.

A controller is typically on the ground, and called a JTAC (Joint Terminal Attack Controller) or a FAC (Forward Air Controller). He can also be airborne, and is then called a FAC(A) (Forward Air Controller Airborne). For the sake of simplicity we will just refer to the controller as JTAC.

In real life, another key player is the ground commander, responsible for ground operations, but in our context it's not a role that is present, so you can disregard from that.

Flow overview

• CAS Request - The JTAC contacts the commander requesting Close Air Support.
• CAS Check-in - The CAS flight provides the JTAC with its capabilities.
• Situation Update - The JTAC provides some information to give the aircrew some SA.
• CAS-brief
  • Gameplan - The JTAC provides broad term info for the upcoming attack.
  • 9-line - The JTAC provides the necessary details for the attack in a standard format.
  • Remarks/Restrictions - The JTAC provides additional optional details.
• Readback - The pilot reads back the mandatory info from the 9-line and the remarks/restrictions.
• Correlation - The JTAC confirms that the pilot has acquired the correct target.
• Attack - The pilot attacks the target.
• Assessment - The JTAC provides an evaluation of the attack.
• BDA - The JTAC or the pilot summarizes the final result of the CAS.

Flow details

CAS Request

The JTAC have identified a situation in which he needs air support. He contacts the commander to request an asset. In our context, this would typically be the AWACS controller. He should specify if he has any certain requirements when it comes to aircraft type, capabilities (sensors, weapons), play time and such. The commander will let the JTAC know if there's a flight available, provide the callsign for that flight and, if possible, and ETA when they will arrive. The commander will provide the CAS flight with the JTAC callsign, a frequency (or channel), and a location to go (can be a waypoint, a coordinate or some other instruction). It can be the target area or the location of an IP (a holding point to anchor at before the attack).

CAS Check-in

When the flight is enroute to the location, they will contact the JTAC, letting them know they are on their way, and provide the details on the flight's capabilities. The following info should be included:

1. Number and type of aircraft
2. Position and altitude
3. Ordnance
4. Playtime
5. Relevant sensors (typically targeting pod)

If the flight is not able to work with MGRS coordinates (which is standard), and need some other format (typically DD:MM:DEC coordinates), this should be mentioned.

Situation Update

The JTAC provides a short overview on what's happening, and if there is anything the flight needs to know, like and hazards (air defenses, other CAS flights) or so.

CAS-brief

The pilot writes this down. Typically in a printed CAS sheet. The CAS brief contains three parts:

Gameplan

The JTAC provides a short summary of how the attack is going to be performed. At the least, two items need to be communicated (and typically, this is enough):

• Type of control - There is Type 1, Type 2 and Type 3 attacks.
• Method - "Bomb on target" (BOT) or "Bomb on coordinate" (BOC). With BOT, the pilot will need to acquire the target visually or with a sensor. With BOC, this is not needed, but he will instead attack a certain location on the ground.

The gameplan may include a requested ordnance type/number.

9-line

The 9-line is a standard format describing the attack details. The JTAC reads every line (some of them might be "not applicable", and are then explicitly communicated that way). The lines are always read in a certain order and should be as short/to-the-point as possible. It's encouraged that the JTAC reads the line headers ("IP", "Heading" etc) out loud, to make it easier for less experienced pilots.

1. IP (Intitial point) - This starting point from which the attack. Could be a waypoint or a geographic position. Can be pre-briefed or set up by the JTAC. Not always needed.
2. Heading - The magnetic heading from the IP to the target. Not used if there's no IP.
3. Distance - The distance from the IP to the target. Not used if there's no IP.
4. Elevation - The target altitude in feet MSL (above mean sea level).
5. Target - A concise description, for instance "T-72 tank".
6. Location - Can be communicated by grid position (most common), talk-on, or lat/long.
7. Mark - The JTAC can mark the target with smoke, laser or IR. If laser is used, the laser code should also be provided.
8. Friendles - The distance (in meters) and cardinal/subcardinal ("North-west") direction from the target to the nearest friendles.
9. Egress - The cardinal/subcardinal direction for the pilot to egress after weapon employment.

The bold lines are mandatory for the pilot readback below.

Remarks/Restrictions

Remarks are additional info items to help the pilot. Typical remarks are:

• Type/number or ordnance (if not already specified in gameplan).
• Laser-to-target line - The direction of the laser (for instance "south to north").
• Threats - AAA, manpads etc.
• Weather - Cloud ceiling etc.
• Friendly mark - If the friendlies have marked themselves with smoke or IR.

Restrictions are things that need to be followed, and always require readback. Typical restrictions are:

• Final attack heading - If the attack needs to be performed at a certain heading (for instance "090 plus/minus 20").
• Danger close - If the attack is intended to hit very close to friendlies (inside of the weapon's "0.1% probability of incapacitation" radius).
• TOT - If there is a certain time-on-target when the weapons is intended to hit the target.

Readback

After the JTAC's CAS brief is finished, the pilot should read back the following things:

• Line 4, 6 and 8 from the 9-line brief.
• Any restrictions.

Correlation

The JTAC needs to make sure the pilot is acquiring the correct target. It can be done in many ways. Typically through a talk-on, guiding the pilot from a reference point, through distinguishable landmarks, to the target. This is a back-and-forth talk between the JTAC and the pilot, and can be very different depending on the situation.

Attack

When the correlation has been completed, the JTAC clears the pilot to approach by asking him to advice when he's leaving the IP. When the pilot has completed his preparations, and has turned towards the target, he calls "in", meaning he has left the IP and is inbound towards the target.

• If the JTAC wants the pilot to continue, but he's not ready to let him open fire just yet, he calls "continue".
• If the JTAC wants to cancel the attack, he calls "abort, abort, abort!".
• When the JTAC is confident everything looks good, he calls "cleared hot!".

Note 1: For safety, "cleared hot!" are words ONLY to be said by the JTAC, ever. You are not allowed to asked "am I cleared hot". Just say "in", or "in, 4 miles" or such if you need to make the JTAC aware that your delivery window is closing.

Note 2: In a Type 3 scenario, the JTAC will call "cleared to engage" instead of "cleared hot".

When the pilot fires, he should call out the appropriate weapon release term. For instance "Pickle" (all bombs) or Rifle (air-to-ground missile, like a Maverick). No callout is needed for gun strafe.

Laser considerations

If the pilot has released a laser guided weapon, and the JTAC should guide it, the pilot should call "laser on" when he wants the JTAC to start lasing.

• For a Laser Maverick delivery, laser should be on before launch.
• For a LGB drop, it's generally better to let the bomb fall a while, building up energy before the laser is turned on, causing the bomb to maneuver.

When the JTAC has turned on the laser, he acknowledges this by calling "lasing".

Assessment/BDA

After the weapon has impacted, the JTAC should let the pilot know whether it was a hit or miss. Many times, a re-attack is needed. In this case, the JTAC simply asks for a re-attack. The instructions and restrictions from the first attack still apply, so no new CAS brief is needed. The JTAC may give additional instructions when the pilot is maneuvering, typically an target position adjustment. This is typically given with reference to where the previous attack hit ("from your hits, north 100").

BDA

WIP

Control types

WIP

Type 1

WIP

Type 2

WIP

Type 3

WIP

Example

WIP In our example, a JTAC called Bowser5 has found a group of T-72 tanks that he needs to see destroyed. He has requested air support from his commander (in our case, the mission commander, or the AWACS). A flight of two F/A-18C Hornets called Arctic1 has been dispatched and is enroute to the area where Bowser5 is operating.

...

Glossary

WIP