14th VSFS/Close Air Support (CAS)
More actions
What is CAS?
Close Air Support (CAS) is when fixed or rotary-wing aircraft attack hostile targets that pose a threat and is in close proximity to nearby friendlies, with each mission requiring detailed coordination with the fire and movement of those forces on the ground. It's not just about dropping bombs near the front line. Every turn, every trigger squeeze, every weapon employed is deliberate.
The person who makes that happen is the JTAC (Joint Terminal Attack Controller), a specially trained operator who spots the target, radios the pilot with everything they need to know, and gives the final word to fire. While a JTAC is typically on the ground, a qualified JTAC pilot can also control from the air in a role known as FAC(A), or Forward Air Controller (Airborne).
Every attack has to be carefully coordinated so that airpower and ground forces are working as one, which is what separates CAS from other air-to-ground missions like Air Interdiction. It's considered one of the most demanding missions in military aviation precisely because the margin for error is essentially zero.
Order of Events (12-Step CAS Procedure)
The "12-step CAS Procedure" is a simplified way to breakdown the general order of events that occur in a standard CAS mission.
1. Routing/Safety of Flight
Before anything tactical happens, the CAS aircraft has to get from it's current position to a holding point near the fight without getting shot down or running into someone else's traffic. The controlling agency (JTAC, FAC(A), or C2) will pass to the aircraft:
- 6, 8, or 10 digit MGRS grid coordinates for the Echo point (target)
- Holding point and altitude, and which agency to contact once established (will be same frequency if already with JTAC)
- Other aircraft already on station
- Surface-to-air threats that could immediately affect the aircraft
- Any other safety-of-flight issue
This step exists purely to deconflict airspace and keep the aircraft in a safe and predictable position before the tactical conversation even starts.
The CAS Keyhole
IP selection often uses the CAS keyhole template (refer to image on the right), a standard geometric method for building a holding area around a reference point (Echo point) when no preplanned IP exists.
| Alpha Point | North in reference to the Echo Point |
| Bravo Point | East in reference to the Echo Point |
| Charlie Point | South in reference to the Echo Point |
| Delta Point | West in reference to the Echo Point |
| Echo Point | The target, or target area |
"Hawg 3-2, establish D7 block 8-10"
With this one short sentence, JTAC has instructed Hawg 3-2 to fly to and establish a hold west of the target (Echo point) and proceed no closer than 7nm. The altitude of the hold should be between 8,000ft and 10,000ft.
The Overhead
Flights may just be pushed into the overhead, also known as the CAS wheel. The overhead is a circular orbit established about the Echo. Generally the orbit is flown within 5nm of the Echo and the rotation depends on the aircraft and military branch. Navy aircraft tend to orbit counter-clockwise as most aircraft have their TGP mounted on the left side of the aircraft. Airforce aircraft tend to orbit clockwise as most aircraft have their TGP mounted on the right side of the aircraft.
The altitude is usually given by JTAC. A call for example would be "Hawg 3-2, push overhead block 8-12". But if no block was assigned, fly an altitude where you are not too low that you can't see the Echo point and the area surrounding it, and not too high that it will take a long time for you to get a run-in and get weapons on target. If you were pushed to the overhead, it usually means the situation on the ground is urgent and will require immediate support and reattacks, provided there are little to no surface to air threats.
2. Aircraft Check-in
Do NOT check in until the JTAC tells you to do so.
Once the aircraft has been instructed to check in, they will check in with the controller using a standardized brief so the JTAC knows exactly what capability just showed up. The check-in brief covers:
| Mission number | If tasked with mission. "mission number ____" |
| Number and type of aircraft | "two ship F-14s" or "two by F-16s" |
| Position and altitude | Current location "35nm north of Echo at FL250" or "15nm east of Adana at 9,000ft" |
| Ordnance | Full loadout "2 by gbu12, 2 by mk82, 360 round of 20 mike mike" |
| Playtime / time on station | How long you can stay "playtime 90 mike" or "playtime 1+30" |
| Capabilities | Sensor types, lase capabilities, laser code, and any additional info |
| Abort code | Default is "In the clear" (see text below) |
"Abort code in the clear" means the standard "Abort, Abort, Abort" calls will be used to terminate run-ins. This is the default when there's no operational security concern about unsecure comms.
Any other pre-briefed abort codes will override the standard "Abort, Abort, Abort". Pre-briefed abort codes are usually found in the ATO under SPINS as a RAMROD code.
3. Situation Update (SITUP)
The JTAC or FAC(A) now paints the tactical picture using the TEFACHR format (Threat, Enemy situation, Friendly update, Artillery, Clearance authority, Hazards, Remarks/Restrictions).
| Line | Content |
|---|---|
| Threat | General surface-to-air threat locations, time of last observed SAM/AAA fire |
| Enemy situation | General enemy disposition (grids saved for the 9-line itself) |
| Friendly update | General friendly scheme of maneuver, using terrain references rather than grids where possible |
| Artillery | Factor indirect fire assets and general direction of fire |
| Clearance authority | Who has authority for brief/stack/mark/control, especially if multiple voices are on freq |
| Hazards | Towers, minimum safe altitude, weather (including surface winds), CBRN, explosives |
| Remarks/Restrictions | Ordnance restrictions, JTAC capabilities (laser, IR, VDL), airspace coordination measures, required radio calls, intent for the aircraft |
The aircrew should reciprocate with any threat info they have. This step ends with the JTAC's line, "advise when ready for game plan," which is the aircrew's cue to move to Step 4.
Alternatively if both JTAC and CAS aircraft are experienced, game plane and 9-line will be given together (steps 4 and 5). JTAC will say something along the lines of "...advise ready game plan and 9-line". Both will be read to the pilot with sufficient breaks between the two sections to allow the pilots time to write down what is necessary.
4. Game Plan
Short and simple by design. The JTAC states the type of control (Type 1, 2, or 3) and the method of attack (effects desired, ordnance, attack interval). Example:
JTAC: "Hawg 3-2, Type 2 control, Bomb On Target, 2 x GBU-38 in trail, 30 second spacing. Advise when ready for 9-line."
| TYPE 1 | Each attack run is cleared individually, target and aircraft has to be visual to JTAC before cleared hot |
| TYPE 2 | Each attack run is cleared individually but no need visual with target or aircraft |
| TYPE 3 | The JTAC can clear multiple attacks for a single target or group of targets |
| Bomb On Target (BOT) | Bomb on Target authorizes an attack against a specific target identified by the JTAC. The pilot is required to have sensor or visual contact with the target. (refer to step 8) |
| Bomb On Coordinate (BOC) | Bomb on Coordinate authorizes an attack on a specific set of coordinates provided by the JTAC. The pilot is not required to have sensor or visual contact with the target. |
5. 9-line
The standard CAS briefing form, used for every type of fixed wing CAS aircraft. Line numbers are not transmitted, the JTAC reads the content only in a fixed sequence:
| Line | Field | Content |
|---|---|---|
| 1 | IP/BP | Initial point or battle position |
| 2 | Heading | Degrees magnetic, IP/BP to target, plus offset (L/R) if requested |
| 3 | Distance | IP-to-target in nautical miles (fixed-wing) or BP-to-target in meters (rotary-wing) |
| 4 | Target elevation | Feet MSL — mandatory readback |
| 5 | Target description | What it is |
| 6 | Target location | Lat/long, grid, or offsets — mandatory readback |
| 7 | Type mark/terminal guidance | Mark description; if laser, lasing platform call sign and code |
| 8 | Location of friendlies | Cardinal direction and distance in meters from target, plus how friendly position is marked |
| 9 | Egress | Egress direction/route |
6. Remarks/Restrictions
Functionally part of the 9-line transmission above, but worth treating as its own teaching point because this is where friendly-fire incidents get prevented or caused. This is the JTAC's last chance to constrain how the attack physically happens: attack heading, danger-close authorization with JTAC initials, abort criteria, airspace boundaries, and timing windows. New pilots should be taught to treat every restriction as a hard limit, not a suggestion, because it's the one part of the brief legally tied to accountability (the danger-close initials exist specifically so there's a record of who accepted the risk).
Examples of possible remarks and restrictions
- Final attack headings/directions (FAH and FAD) (highly recommended to use this)
- Laser-to-target line/pointer-target line
- Airspace coordination areas
- Danger close
- Post-launch abort restrictions
- Additional remarks (gun-target line, weather, hazards)
- Desired ordnance/weapons effects
- Time on target/time to target
- Additional requested calls
7. Readbacks
The aircrew reads back Line 4 (target elevation), Line 6 (target location), and any restrictions given. This is mandatory under JP 3-09.3, full stop, regardless of aircraft type or control type. The JTAC may request additional readback of any other line if they want extra confidence. This step is a hard gate: if the readback doesn't match what was briefed, the JTAC corrects it before anyone proceeds to Step 8.
8. Correlation
Before weapons come off the rail, the aircrew has to positively correlate and identify (PID) what they're looking at (sensor picture, sensor talk-on, or visual talk-on) is the actual intended target. Skipping or rushing correlation is the single most common root cause of CAS friendly-fire incidents in the real world by a large margin, so it's worth spending real training time on this step specifically rather than treating it as a formality between the 9-line and weapons release.
Once the target has been correctly identified with utmost confidence, the JTAC will say "(callsign), THAT is your target". It is at this point that the target is now considered hostile.
Correlation is NOT required for Bomb On Coordinate.
Refer to the "Standard CAS Mission Examples" at the bottom of the page for more detail.
9. Attack Phase
Aircraft are required to call “In” with heading when on the final attack course and shortly prior to weapon release or employing effect.
Example: “Hawg 3-2 is IN, 270”
Note that the heading called is the direction the aircraft is travelling in, calling 270 means you are attacking from east to west.
Weapons release, employment, and immediate post-release calls such as "rifle" or "two away" are required per type of control.
10. Asses Effects
Right after the attack, the aircrew or JTAC (whoever has the best view) makes an immediate call on what just happened. At minimum, a munitions effectiveness assessment. This step feeds directly into whether the JTAC sends the aircraft back for a re-attack, or move to a new target by repeating steps 4-9 again.
Examples:
"Hawg 3-2, good effect on target"
"Hawg 3-2, good hits, good hits, structure severely damaged"
"Hawg 3-2, guns hit north of target, adjust south 40 meters, cleared re-attack, same remarks and restrictions, call in"
11. Final BDA (Mission summary BDA)
Once the engagement sequence for that mission is fully complete, a final consolidated BDA report goes out regarding the entire CAS mission in general. The SALTR BDA format should be used:
| Size | Number and type of target equipment/personnel |
| Activity | Movement direction, stationary, or neutralized |
| Location | Where it is |
| Time | When observed (zulu) |
| Remarks | Observed damage, mission number, mission succesful/unsuccesful |
12. Routing/Safety of Flight
Once BDA is complete, the same safety-of-flight considerations from Step 1 apply again in reverse: routing the aircraft back out of the area, deconfliction from other traffic and surface fires on egress, and handoff to the next controlling agency if the aircraft is continuing on to another tasking or returning to base/carrier.
Standard CAS Mission Examples
| Station | Message | Notes |
| Hawg 3-3 (CAS A/C) | "Rocky 2-1, Hawg 3-3, 20nm north east of Beirut, FL130, ready for tasking" | Step 1 |
| Rocky 2-1 (JTAC) | "Hawg 3-3, Rocky 2-1, report ready to copy grid" | |
| Hawg 3-3 (CAS A/C) | “Hawg 3-3, ready” | |
| Rocky 2-1 (JTAC) | “Hawg 3-3, 6 digit grid as follows, 37S WG 847829, 57 feet” | |
| Hawg 3-3 | “37S WG 847829, 57 feet” | |
| Rocky 2-1 | “Hawg 3-3 read back correct, establish Bravo 5 block 10-12 and send your check-in when ready” | Step 2 |
| Hawg 3-3 | “Bravo 5 block 10-12”
”Mission number 1234, 2xA10C, 14 miles south of Echo at 8,000ft. Playtime 45 minutes. 8xGBU-12, 4xAGM-65E, 1300 rounds of 30MM, equipped with TGP, LST and LSS codes selectable. Abort code in the clear." |
|
| Rocky 2-1 | "Rocky 2-1 copies all, abort code in the clear, report ready for SITUP (situation update)" | Step 3 |
| Hawg 3-3 | "Rocky 2-1 Send it" | |
| Rocky 2-1 | "There's potential MANPADS in the AO, targets are a stationary convoy of light technicals. Friendlies are scattered around the village next to the lake and will stay in position. No artillery at this time. Clearance authority is with Rocky 2-1. Suggest GBU-12 or as desired. No remarks or restrictions. Report ready to copy gameplan" | |
| Hawg 3-3 | "Hawg 3-3 ready to copy" | |
| Rocky 2-1 | "Hawg 3-3 this will be a type 2 control BOT requesting 2xGBU-12, 30 second interval, report ready to copy 9-line" | Step 4 |
| Hawg 3-3 | "Type 2 control BOT, 2xGBU-12 30 second interval, send 9-line" | |
| Rocky 2-1 | "Line 1, 2, and 3: Bravo 5, elevation 57 feet, convoy of light technicals, Echo point, sensor talk-on, friendlies east 500 marked by green smoke, egress right turn back to Bravo 5, report ready remarks" | Step 5 |
| Hawg 3-3 | "Send it" | |
| Rocky 2-1 | "Final attack heading is 270, +/- 10 degrees, read back lines 4, 6, and remarks" | Step 6 |
| Hawg 3-3 | "Convoy of light technicals, Echo point, FAH 270 +/- 10 degrees." | Step 7 |
| Rocky 2-1 | "Readback correct, report position and ready sensor talk-on" | |
| Hawg 3-3 | "Hawg 3-3 is establish Bravo 5 ready for sensor talk-on" | |
| Rocky 2-1 | "Hawg 3-3 push sensors to Echo and describe to me the largest feature you see" | Step 8 |
| Hawg 3-3 | "I see a small village next to a large C-shape lake" | |
| Rocky 2-1 | "Hawg 3-3, in that small village there is a road that runs straight through oriented West-East, call contact" | |
| Hawg 3-3 | "Hawg 3-3 contact" | |
| Rocky 2-1 | "From the town, follow the road WEST by 300 meters you should see a Y-shape split in the road call contact" | |
| Hawg 3-3 | "Hawg 3-3 contact" | |
| Rocky 2-1 | "From the split, follow the northern road west by 200 meters, there's a small convoy of technicals now moving east on that same road, call contact" | |
| Hawg 3-3 | "Hawg 3-3 contact" | |
| Rocky 2-1 | "Hawg 3-3, how many technicals do you observe in that convoy?" | |
| Hawg 3-3 | "4 technicals in total, front two vehicles have weapons mounted on the truck bed and rear two vehicles are carrying bombs and ammunition" | |
| Rocky 2-1 | "Hawg 3-3, that is your target, call in with heading" | |
| Hawg 3-3 | "Hawg 3-3 CAPTURED, wilco" *1 minute later* "Hawg 3-3, IN, 275" | Step 9 |
| Rocky 2-1 | "Hawg 3-3, CLEARED HOT, CLEARED HOT" | |
| Hawg 3-3 | "Hawg 3-3, one away" | |
| *30 seconds later, Hawg 3-4 who is in trail is running in* | ||
| Hawg 3-4 | "Hawg 3-4, IN, 260" | |
| Rocky 2-1 | "Hawg 3-4, CLEARED HOT, CLEARED HOT" | |
| Hawg 3-4 | "Hawg 3-4, one away" | |
| Rocky 2-1 | "Hawg flight, good hits, good hits, egress Bravo 5" | Step 10 |
| Hawg 3-3 | "Bravo 5, Hawg 3-3" | |
| Rocky 2-1 | "Hawg 3-3, report ready to copy final BDA" | Step 11 |
| Hawg 3-3 | "Send it" | |
| Rocky 2-1 | "Hawg 3-3, tasking complete, final BDA as follows: Lead and trail technical in the convoy destroyed, 2 remaining technicals immobilized, commanders intent has been met, mission successful at time 1907z" | |
| Hawg 3-3 | "Hawg 3-3 copies all" | |
| Rocky 2-1 | "Hawg 3-3, flow south, climb to 12,000ft or above, push Magic on button 7, thanks for all the help. | Step 12 |
| Hawg 3-3 | "Flow south, climb 12,000ft or above, push Magic button 7, Hawg 3-3 SEE YUH"
*See yuh is optional but recommended for team morale :) |
Sources: ATP 3-09.32/MCRP 3-31.6/NTTP 3-09.2/AFTTP 3-2.6 (JFIRE), 29 November 2023, Chapter II, Tables 27-33; JP 3-09.3, Joint Tactics, Techniques, and Procedures for Close Air Support.