Bomb on Target (1) BOT and BOC. JTACs/FAC(A)s will state the method of attack, whether BOT or BOC, as part of the game plan prior to the CAS brief. These methods of attack apply to all types of control and all ordnance employed in CAS missions. JTACs/FAC(A)s and CAS aircrews should think of and use these methods of attack as a clear, concise, effective manner to communicate the requirements for correlation from CAS aircraft employing ordnance. Effective use of BOT and BOC constructs to clarify JTAC/FAC(A) and CAS requirements for a CAS engagement will result in more expeditious attacks and help mitigate friendly fire and collateral damage. The misapplication of BOT and BOC in tactical scenarios will often result in confusion between CAS aircraft and JTAC/FAC(A), increased time to kill, and potentially cause friendly fire or collateral damage. ForBOTmissions,onlytheleadaircraftisrequiredtoreadbackLine4and Line 6, in conjunction with other required restrictions. All attack aircraft will conduct readbacks if requested by the JTAC/ FAC(A). (b) ForBOCmissions,allaircraftdeliveringordnancemustreadbackLine4 and Line 6 from their system or weapon, as appropriate, in conjunction with other required restrictions. (2) A BOC attack is used when the JTAC/FAC(A) determines that the desired effects can be created against the target with CAS aircraft employing ordnance on a specified set of coordinates. The coordinates must be of sufficient fidelity/mensuration to produce the desired effect on the target and be used for fires approval. If the aircraft is never required to be TALLY/CAPTURED the target or CONTACT the mark, it is a BOC attack The JTAC/FAC(A) does not need to delay the CAS attack in order to build CAS aircraft awareness to achieve target TALLY/CAPTURE. If a BOC attack is planned based on the tactical scenario, then unnecessary exposure to the threat by CAS platforms is avoided and time is not wasted conducting targeting confirmation. Great care must be taken to ensure that the target location with the required precision and accuracy determined in the commander’s tactical risk assessment is obtained and entered into the weapon/navigation system. Aircrew will not modify coordinates once read back. For a BOC attack, aircrew readback will be from the weapon or aircraft system.

Bomb on Target (1) BOT and BOC. JTACs/FAC(A)s will state the method of attack, whether BOT or BOC, as part of the game plan prior to the CAS brief. These methods of attack apply to all types of control and all ordnance employed in CAS missions. JTACs/FAC(A)s and CAS aircrews should think of and use these methods of attack as a clear, concise, effective manner to communicate the requirements for correlation from CAS aircraft employing ordnance. Effective use of BOT and BOC constructs to clarify JTAC/FAC(A) and CAS requirements for a CAS engagement will result in more expeditious attacks and help mitigate friendly fire and collateral damage. The misapplication of BOT and BOC in tactical scenarios will often result in confusion between CAS aircraft and JTAC/FAC(A), increased time to kill, and potentially cause friendly fire or collateral damage. ForBOTmissions,onlytheleadaircraftisrequiredtoreadbackLine4and Line 6, in conjunction with other required restrictions. All attack aircraft will conduct readbacks if requested by the JTAC/ FAC(A). (b) ForBOCmissions,allaircraftdeliveringordnancemustreadbackLine4 and Line 6 from their system or weapon, as appropriate, in conjunction with other required restrictions. (2) A BOC attack is used when the JTAC/FAC(A) determines that the desired effects can be created against the target with CAS aircraft employing ordnance on a specified set of coordinates. The coordinates must be of sufficient fidelity/mensuration to produce the desired effect on the target and be used for fires approval. If the aircraft is never required to be TALLY/CAPTURED the target or CONTACT the mark, it is a BOC attack The JTAC/FAC(A) does not need to delay the CAS attack in order to build CAS aircraft awareness to achieve target TALLY/CAPTURE. If a BOC attack is planned based on the tactical scenario, then unnecessary exposure to the threat by CAS platforms is avoided and time is not wasted conducting targeting confirmation. Great care must be taken to ensure that the target location with the required precision and accuracy determined in the commander’s tactical risk assessment is obtained and entered into the weapon/navigation system. Aircrew will not modify coordinates once read back. For a BOC attack, aircrew readback will be from the weapon or aircraft system.

FLIGHT 1 FLIGHT 2

Type 2 Control The JTAC/FAC(A) must visually acquire the target or utilize targeting data from another asset with accurate real-time targeting information. Type 2 control requires control of individual attacks. Examples of when Type 2 control may be applicable are troops in contact, night, adverse weather, and high altitude or standoff weapons employment. Type 2 control procedures are as follows: 1. The JTAC/FAC(A) visually acquires the target or acquires targeting data from another asset with accurate real-time targeting information. 2. The JTAC/FAC(A) passes the game plan and CAS brief to the attacking aircrew. 3. The attack aircrew validates target location by cross-checking that the position is coincident with the expected target area, using all appropriate means. 4. TheaircrewwillreadbackLine4,Line6,andanyrestrictionsprovided by the JTAC/FAC(A). 5. The JTAC/FAC(A) will conduct correlation as required. 6. The aircrew will provide an “IP INBOUND” call if requested. 7. The attack aircrew will provide the JTAC/FAC(A) with an “IN” call, indicating entering terminal phase of air-to-ground attack, prior to weapons release. Aircrew should make this call at the appropriate time to allow clearance before entering the release window. If a restriction in the form of a direction or final attack heading (FAH) was given in the CAS brief, then it will be included with the IN call. Example: “IN from the South” or “IN heading 360.” All attacking aircraft are required to provide an IN call unless coordinated otherwise. 8. JTAC/FAC(A) will provide a “CLEARED HOT,” “CONTINUE DRY,” or “ABORT” based on the above procedures being met. In the case of a flight conducting attacks together, the JTAC/FAC(A) may elect to either provide a single clearance for the flight or each attack aircraft individually, based upon the tactical scenario.

CHECK IN / ROUTING / STACKING SITUATION UPDATE GAME PLANE 9-LINE ATTACKS CHECK OUT BDA

(1) Line 1―IP or BP. The IP is the starting point for the run-in to the target. For RW aircraft, the BP is where attacks on the target are commenced. (2) Line 2―Heading and Offset. The heading is given in degrees magnetic from the IP to the target or from the center of the BP to the target. The offset is the side of the IP- to-target line on which aircrews can maneuver for the attack. (3) Line 3―Distance. The distance is given from the IP/BP to the target. (4) Line4―TargetElevation.Thetargetelevationisgiveninfeetmeansealevel (MSL) unless otherwise specified. (5) Line5―TargetDescription.Thetargetdescriptionshouldbespecificenough for the aircrew to recognize the target. (6) Line 6―Target Location. The JTAC/FAC(A) provides the target location. (7) Line7―MarkType/Terminal Guidance.The type of mark the JTAC/FAC(A) will use (for example, smoke, laser, or IR). If using a laser, the JTAC/FAC(A) will also pass the call sign of the platform/ individual that will provide terminal guidance for the weapon and laser code. (8) Line 8―Friendlies. Cardinal/sub-cardinal heading from the target (N, NE, E, SE, S, SW, W, or NW) and distance of closest friendlies from the target in meters (e.g., “South 300”). (9) Line 9―Egress. These are the instructions the aircrews use to exit the target area. (10) Remarks/Restrictions. Supplies additional information important to the conduct of the attack.

Talon1, Hold check in, attack in progress Talon1, Hold check in, attack in progress. Hold at Sinatra, block 20 to 22 Talon 1, Go with Check In Keyhole in effect N 38.24.210 E 127.11.05 How copy Proceed Bravo 8, block 17-19, We have another Viper flight in the stack, callsign Falcon1, advise when ready game plan. Advise when ready for situation update. CAS: “Current surface-to-air threat is an unlocated ZSU 23-4, last reported NE of echo point. 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. Friendlies are a recon team SW of Sinatra. There is also a STA team at the northwest tip of Blue Mountain; 81mm mortars are firecapped south of OP 2, firing generally northwest, break. Winds on the deck are 5 knots out of the northwest, I have a Sniper pod. I plan on using you to disrupt the light armor so the recon team can push up closer to the DMZ for a better line of site, cleared into the wheel at your assigned block, advise when ready for game plan.” “Talon1, this is Elvis 51, Type 2 control, bomb on coordinate, 2 Mk-82s each, simultaneous impacts, running a race track in and off target single ship passes. advise when ready to copy 9-line.” Seconds to impact if you can or just say 30 seconds to impact. How many dropped and where you going ie. Talon 11, 2 away, 30 seconds to impact, proceeding to charlie 10 Situagtion up date is for fun - don

Charlie 10 Elevation: 1300ft BMP Infantry Vehicles N 38.27.232 E 129.38.066 No Mark South 1100 Egress, left pull, back to charlie 10 block 20-22 Advise when ready for remarks Final attack heading 360 plus or minus 30, no other restrictions at this time how copy? Good readback. Talon1, Report IP inbound on your first pass. Call in with heading, Expect clearance as a flight. Continue (IP inbound) Cleared hot Good impacts standby BDA (say if good or not) Talon12 are you tally on Talon11 last impact? Request reattack. Change to game plan, bomb on target. Same ordnance, same 9-line, same restrictions. From Talon1 last impacts, adjust east 25 meters. There is a second command BMP there, how copy”

Don’t need to acknowledge continue or cleared hot