Close air support (CAS) - UNITAF Force Manual (FM)


Group

Close air support (CAS)
This group is not in a published chapter and should not be relied upon.



FM/BS-1800 - Request Close Air Support

Line 1: Handshake

  • Establish communications with the aircraft
  • Identify yourself and declare a CAS request

Format:

[Aircraft Callsign], this is [FAC Callsign], CAS request

Example:

HAMMER 1-1, this is SIERRA 1, CAS request

Aircraft response:

HAMMER 1-1, send CAS request

Line 2: Target Location

  • Provide the target location using the most appropriate reference method

Format:

  • GRID [grid reference]
  • SHIFT TRP [name], NORTH/SOUTH xx, EAST/WEST xx
  • TRP [name]

Examples:

GRID 118094

SHIFT TRP ALPHA, NORTH 150, EAST 75

TRP ALPHA

Line 3: Target Description and Marking

  • Briefly describe the target
  • Include target size, type, environment, and marking method

Format:

[target type/size], [environment/cover], (marked by [method], [laser code if applicable])

Examples:

Infantry in treeline

Squad in compound, marked by red smoke

Single vehicle in open, marked by sparkle

Infantry in treeline, marked by laser, code 1688

Line 4: Friendly Positions

  • Identify friendly positions relative to the target
  • Include friendly marking methods where applicable

Format:

Friendlies [distance] [direction] of target, (marked by [method])

Examples:

Friendlies 200 metres south of target

Friendlies 150 metres east of target, marked by blue smoke

Friendlies no factor

Line 5: Attack Guidance, Restrictions & Ordnance

  • Specify attack direction and restrictions
  • Request desired ordnance
  • State danger close where applicable

Format:

[attack direction], [restrictions], Request [ordnance], (danger close if applicable)

Examples:

Attack north to south, Request HE Rocket

Attack south to north, no fires west of target, Request Bomb

Attack east to west, remain north of friendlies, Request guns danger close

Attack north to south, light AA threat from compound west of target, Request Maverick

Aircraft response:

  • Readback of lines 2-5
FM/BG-1801 - CAS request quick guide
  • Line 1: [Aircraft Callsign], this is [FAC Callsign], CAS request
    • Aircraft response: [Aircraft Callsign], send CAS request
  • Line 2: GRID [grid reference] OR TRP [name] OR SHIFT TRP [name], NORTH/SOUTH [Distance in metres], EAST/WEST [Distance in metres]
  • Line 3: [target type/size], [environment/cover], marked by [method], [laser code if applicable]
  • Line 4: Friendlies [distance] [direction] of target, (marked by [method])
  • Line 5: [attack direction], [restrictions], Request [ordnance], danger close (if applicable)
    • Aircraft response: Readback of lines 2-5
FM/BG-1802 - CAS clearance types

Following a correct readback, the FAC may issue a clearance. The clearance type defines the level of engagement authority granted to the aircraft against the designated target or target area.

  • Type II
    • Authorises a single engagement against the designated target.
  • Type III
    • Authorises multiple engagements against the designated target or target area until:
      • The FAC terminates the engagement, or
      • The aircraft assesses the target has been neutralised

 

The FAC retains authority to adjust, restrict, or abort the attack at any time.

Aircraft may refuse a CAS request if they assess it creates unacceptable risk to the airframe or mission.

FM/BS-1803 - Correct an incorrect readback
  • Receive the aircraft readback.
  • Confirm the aircraft has correctly read back all required information.
  • If the readback is incorrect:
    • State "Negative Readback".
    • Identify the incorrect line.
    • State the correct information for that line.
    • Direct the aircraft to read back the corrected line.
    • Verify the corrected readback.
    • Repeat as required until all information is correct.
  • Proceed with clearance FM/BS-1804 - Clear an aircraft to engage

Example

Aircraft:

Friendlies 200 metres north of target.

FAC:

Negative Readback. Line 4. Friendlies 200 metres south of target. Read back Line 4.

Aircraft:

Line 4, friendlies 200 metres south of target.

 

FM/BS-1804 - Clear an aircraft to engage
  • Confirm a correct readback has been received.
  • Select the appropriate clearance type.
  • Restate danger close if applicable
  • Monitor the engagement and adjust, restrict, or terminate the attack as required.

Format

Readback correct, Cleared In Type II

Readback correct, Cleared In Type III

Alternative Format

Cleared Hot Type X

Cleared to Engage Type X

Danger Close Example

Readback correct, Cleared Hot Type II, Danger Close

FM/BS-1805 - Control an ongoing CAS engagement
  • Monitor aircraft attacks and battlefield changes
  • Update target information when required
  • Adjust restrictions as necessary
  • Terminate the attack if conditions become unsafe

Abort Command 

STOP STOP STOP

Immediately terminates the current attack run

Evasive Action 

EVADE

Directs the aircraft to break off and prioritise aircraft safety

FM/BG-1806 - Follow on CAS actions

Aircraft should confirm target identification before engagement.
Examples:

Visual infantry in treeline

Visual red smoke

Following each attack:

  • Aircraft report observed effects
  • FAC assesses results
  • FAC may re-clear, adjust, redirect, or terminate the engagement
FM/BS-1807 - Check in as a CAS aircraft
  • When entering or re-entering an AO
    • Establish communications with the supported element
    • Provide aircraft capabilities and limitations

Format

[FAC Callsign], this is [Aircraft Callsign],

Include:

  • Aircraft team composition
  • Current location
  • Available ordnance
    • Rockets
    • Guns
    • Missiles
    • Bombs
      • Skip if not applicable
  • Night vision capability (if applicable)
  • Available station time in minutes (if required)

Example

  • SIERRA 1, this is HAMMER 1-1. 
  • We are a flight of two A-10s, currently orbiting GRID 042167. 
  • Ordnance available:
    • 38 HE Rockets
    • 2,400 rounds 30mm
    • 6 GBU12
  • Night vision capable.
  • 40 minutes station time remaining.
This page generated 1.26MB in 0.1378 seconds.