¶ Introduction
Close Air Support (CAS) is defined as “…air action by fixed-wing (FW) and rotary-wing (RW) aircraft against hostile targets that are in close proximity to friendly forces and requires detailed integration of each air mission with the fire and movement of those forces.”
Joint Terminal Attack Controllers (JTACs) are the individuals responsible for directing these actions while mainting the safety of both the ground forces and aviation assets, as well as assessing the effects of the action. These personnel may also be known as Forward Air Controllers (FACs), Forward Air Controller - Airborne (FAC-A), and could be in groups such as Tactical Air Control Partys (TACPs) and Fire Support Teams (FiSTs).
The purpose of this page is to walk aircrew through the process of CAS with a JTAC and how to work in conjunction with one to accomplish the mission.
¶ Close Air Support Process
The CAS process is comrpised of 12 steps:
- Routing and safety of flight
- CAS aircraft check-in
- Situation update
- Game Plan
- CAS brief
- Remarks and restrictions
- Readbacks
- Correlation
- Attack
- Assess effects
- Battle damage assessment
- Routing and safety of flight
¶ Routing and Safety of Flight
This is the initial step in the process, and generally the first point aircrew will contact the JTAC. JTACs will direct flights to a hold area, either by using pre-briefed Initial Points (IPs) and Holding Areas (HAs), or by using the Keyhole method.
Keyhole method is the process of using a geographic reference point (lakes, mountains, cities, etc.) or the target area itself as a reference point to establish the hold area. In this process, the reference point or target area will be known as the Echo Point. Alpha will be directly North of the Echo Point, Bravo will be East, Charlie will be South, and Delta will be East. A number followed by one of these directions will represent the distance at which to hold, for example, Charlie 15 means to hold 15 miles south of the Echo Point. Echo 15 will mean to hold anywhere 15 miles outside of the echo point.
Note: When dealing with rotary-wing assets, the distance will be in kilometers, rather than miles
This initial exchange will look like this (if there is a need for authentication, this will also occur before any information is exchanged):
RIPPER11: “RAZOR1, RIPPER1, en route to your area, eta 20 mikes.”
RAZOR1: “RIPPER1, RAZOR1, roger, keyhole in effect, Echo Point is your target point, procede to Charlie 15, blocks 24-27. You are the only aircraft on station, send check in when established.”
RAZOR1 has now sent RIPPER11 to the hold area, and they will check in once established.
¶ Aircraft Check In
This is the stage where an aircraft will inform the JTAC about their flight, ordnance, time on station, and capabilities
This exchange can look like this:
RIPPER11: “RAZOR1, RIPPER1 check-in ready”
RAZOR1: “RIPPER1, RAZOR1, send check-in”
RIPPER11: “RAZOR1, Mission Number 010101, 2 by F-14 Tomcat, established Charlie 15 blocks 24 through 27. 4 by GBU-12, 670 rounds of 20 mike mike each. 60 minute of playtime, LANTIRN equipped. Abort code is REVERE.”
RAZOR1: “RIPPER1, roger check in, standby for situation update.”
¶ Situation Update
JTACs will provide a situation update to the aircraft. This update will contain contextual information as well as threats and restrictions important to the aircrew to be aware of during the mission.
RAZOR1: “RIPPER1, RAZOR1, situation update as follows:”
RAZOR1: “The current surface-to-air threat is an unlocated ZSU 23-4, last seen west of MSR 5.”
RAZOR1: "The enemy situation is a light armored company attempting to flank us to the north and two companies dug in three klicks to our west, break.”
RAZOR1: “Friendlies are two companies in the vicinity of OP 2, one on the high ground and the other in a blocking position to the east. I am with the company on the high ground. There is also a team at the northwest tip of Blue Mountain.”
RAZOR1: “81mm mortars are firecapped south of OP 2, firing generally northwest, break.”
RAZOR1: “Winds on the deck are 15–20 knots out of the northwest.”
RAZOR1: “I have laser.”
This update has provided the flight with threats, enemy composition, as well as the friendly situation. Importantly the example update has also provided the caveat that the flight should provide their heading for all inbound calls under type 2 controls.
¶ Game Plan
The game plan will go over the way in which the aircraft will be used and employed, as follows:
Controls:
- Type 1: JTAC requires tally on the target and a visual on the aircraft conducting the attack.
- Type 2: JTAC requires a visual on the aircraft OR a tally on the target.
- Type 3: JTAC does not require a visual or tally, typically used to approve multiple attacks at a time while mainting attack restrictions.
Method of Attack:
- Bomb on Coordinate (BoC): Aircraft employs weapons on coordinate
- Bomb on Target (BoT): Aircraft employs weapons on a target, and may require a talk on to achieve the required TALLY/CONTACT/CAPTURED call.
Ordnance/Effect
- Very simply the bomb needed or the desired effect
Interval between Aircraft Attacks
- Typically between members of a flight
This exchange can look as follows:
RAZOR1: “RIPPER1, RAZOR1, gameplan: Type 2 control, bomb on target, request 1xGBU12 per aircraft, 15 second interval. Advise when ready for 9 line”
RIPPER1: “RAZOR1, copy, ready for 9 line.”
¶ Fixed Wing 9 Line
The 9 line is a concise format in which to deliver the required information to the aircraft to conduct the attack. If lines are not needed, they are omitted, and line numbers are not said otherwise. If using the keyhole method, you may use that to describe an IP. The format is as below:
- IP/BP: “__________________.”
- Heading: “__________________.” (degrees magnetic or IP/BP position-to-target) | Offset: “-----------.” (left or right, when requested)
- Distance: “__________________.” (IP-to-target in NM, BP-to-target in meters)
- Target elevation: “__________________.” (in feet, mean sea level)
- Target description: “__________________.”
- Target location: “__________________.” (Lat/Long, MGRS, or offsets)
- Type mark/terminal guidance: “__________________.” (omitted if BOC, description of the mark; if laser, callsign of lasing platform & code)
- Location of friendlies: "__________________. (from target, cardinal direction and distance in meters) | Position marked by “--------.”
- Egress: “__________________.” (cardinal direction or keyhole routing)
Most commonly, lines 1 through 3 will be ommitted if the JTAC wants the aircraft to come direct from the stack. This can be called as “Lines 1 through 3, N/A” or “FROM THE OVERHEAD.”
RAZOR1: “RIPPER1, 9 line to follow:”
RAZOR1: “RIPPER1, Lines 1 through 4, N/A.”
RAZOR1: “Target is a T72 platoon in the open.”
RAZOR1: “Grid 37S BS 12345 67890”
RAZOR1: “Mark is LASER, CODE: 1688”
RAZOR1: “Friendlies are 800 meters east of the target, no mark”
RAZOR1: “Egress East”
RAZOR1: “Advise when ready for remarks and further talk on”
RIPPER11: “RAZOR1, ready for remarks”
¶ Remarks
Remarks encompass anything the JTAC may require or decide is relevant to the attack. This can include:
- Surface to air threat position
- Weather/hazards
- Any additional calls requested for the aircraft to make.
Restrictions may include:
- Final Attack Heading
- Danger close and approval initials
- Time on target requirement
RAZOR1: “RIPPER1, request IN with heading, final attack heading will be 345-015.”
¶ Readback
Lines 4 and 6 for the fixed wing 9 line as well as any restrictions are mandatory readbacks. JTACs may require additional readbacks if necessary
RIPPER11: “RAZOR1, target grid 37S BS 1234 6789, will call IN with heading, final attack heading 345-015.”
RAZOR1: “RIPPER1, readback correct”
¶ Correlation
For Bomb on Coordinate employment, this stage is complete at the conclusion of the readback. For Bomb on Target, continue.
This stage is known as the talk on, and encompasses the process the JTAC takes to get the aircrew looking at the correct target. Generally, this will start with the JTAC requesting the crew to call CONTACT on a recogizable point near the target, then walking the sensors to the target. JTACs may ask questions to confirm what the aircrew is seeing is correct (i.e. “is the courtyard opening to the street?”).
Once the JTAC walks the aircrew to the target, they should call CAPTURED if spotted via sensor, or TALLY if spotted out of the cockpit with their eyes.
A JTAC may also direct STARE, which means to enable a laser spot track to direct the sensor to the target off the JTAC’s laser. In this case, the JTAC may ask “What do you have in your pod?” and if the description is correct, the JTAC will say “That is your target” and the aircrew will reply CAPTURED.
Some notes, there are requests aircrew can make of the JTAC at this point. They are the following:
- LASER ON: This directs the JTAC to turn on their laser, enabling a laser spot track
- LASER OFF: This directs the JTAC to turn off their laser
- SPARKLE: this directs the JTAC to turn on the infrared laser, only visible under NODs
- SNAKE: this directs the JTAC to perform a figure 8 with the infrared laser to enable spotting
An example talk on can look as follows:
RAZOR1: “RIPPER1, call CONTACT the river north of the town”
RIPPER11: “CONTACT”
RAZOR1: “Track east along the river to a road crossing, call CONTACT”
RIPPER11: “CONTACT”
RAZOR1: “What do you see in your pod?”
RIPPER11: “I see a group of 4 tanks in the open south of the crossing”
RAZOR1: “That is your target”
RIPPER11: “CAPTURED”
¶ Attack
At this point, the aicrew begins their attack. Aircrew should not employ their weapons unless they are given the CLEARED HOT directive, typically given after the inbound once the JTAC is satisfied with the conditions.
RIPPER11: “RIPPER1, IN with heading 355”
RAZOR1: “CONTINUE”
RAZOR1: “RIPPER1, CLEARED HOT”
Should the JTAC need to call an abort, they will do so simply by saying ABORT ABORT ABORT or using the abort code for the flight as pre agreed.
RAZOR1: “RIPPER1, RAZOR1, ABORT REVERE, ABORT REVERE, ABORT REVERE”
¶ Post Attack
After the attack, the JTAC will assess the damage, providing feedback to the aircraft. Afterwards, unless otherwise instructed, they egress and return to the holding area.
Should the JTAC request an immediate re-attack, these aircraft should repeat the same pattern they originally did to re-attack. Use the same IP and route as before, and repeat the attack with IN calls and such. Immediate re-attack DOES NOT mean to immediately whip a U-turn and attack ignoring the final attack heading (unless they are not present).
¶ 5 Line Rotary Wing Call for CAS
This section will go over the main differences for a rotary call for CAS. To note, this is NOT the same as a 5 Line Call for Close Combat Attack (and still requires a JTAC to call it). It is significantly shortened compared to the 9 line, skips the initial game plan call and integrates it as line 1. It is composed of the following lines:
-
Game plan/WARNO
- “[Aircraft C/S], [Observer C/S], 5 line, [Type], [Method of Attack, BOC/BOT], [Ordnance requested]”
-
Friendly Position and Mark
- “My position [Reference from target location/Grid/reference point], marked by [Mark type]”
-
Target Location
- “Target location, [Grid/reference from friendly location/reference point]”
-
Target Description and Mark Type
- “Target is [Target Description], marked by [Mark Type]”
-
Remarks and Restrictions
-> Can include:
–> Final Attack Heading
–> Danger Close and approval initials
–> Time on Target
–> Surface to air threats
–> “On my command” restriction
This exchange can look like:
RAZOR1: “BLACKJACK1, RAZOR1, 5 line, Type 1 Control, Bombs on Target, request Hellfire and Guns”
RAZOR1: “Friendly forces located 300 meters east of enemy forces, spread 100 meters along the treeline, marked by IR strobe”
RAZOR1: “Target is at Grid 37S BS 1234 5678”
RAZOR1: “Target is enemy armored vehicles in the open, marked by IR laser”
RAZOR1: “Request in with heading, Final Attack Heading 345-015, Danger Close, commander’s initials RGB”. Call inbound"
BLACKJACK11: “RAZOR1, BLACKJACK1, VISUAL your strobe, CONTACT IR SPARKLE, SNAKE on my command to confirm target…SNAKE”
RAZOR1: “RAZOR1 copies, SNAKING”
BLACKJACK1: “RAZOR1, BLACKJACK1, confirm TALLY, CEASE SPARKLE IN on heading 355”
RAZOR1: “BLACKJACK1, RAZOR1 has ceased SPARKLE, you are CLEARED HOT, call engaging”
BLACKJACK1: “RAZOR1, BLACKJACK1, ENGAGING”
To note, there also exists the 5 line Call for Close Combat Attack. This does not require a JTAC, and largely consists of the exact same lines as the RW 5 line Call for CAS. The largest difference is that line 1 will only contain the phrase “CCA Fire Mission, break” after the callsigns. Effect and ordnance used is up to the discretion of the aircrew, as well as the responsibility for the fire mission
¶ Conclusion
In the example provided throughout this page, this will terminate in 2 bomb drops from the F-14 Tomcats in a 15 second interval between the flight members. Target sorting on the tank platoon is at the discretion of the flight leader, as long as the targets are the designated tank platoon. Once these drops are complete, they egress east and return to the holding area unless otherwise instructed.
RAZOR1: “RIPPER11, good effect on target, return to the hold area”
RIPPER11: “RAZOR1, roger”