Doctrine

Brief description of squadron SoPs and expectations for roles within a package.

Briefing

Ground attacks require a Fighter to Fighter brief, to cover the following topics (FROTIES):

Formation: Flight formation. Default is trail.

Roles: For each callsign whether they are shooter (employing ordnance) or cover (Guaranteeing mutual support with visual and comm)

Ordnance: Weapons to use.

Timing: Separation By x seconds or nautical miles

Ingress Direction: Magnetic bearing to target from IP

Egress Direction: Magnetic bearing from target to recovery

Sort: Who is attacking what on the target. Default sort is north to south from #1-4 or by element (north half by 1st element, south half 2nd element).

Sounds like this: "Trail, shooter, cover, shooter, cover. AGM-65D. 15 second separation by callsign. Ingress from IP 1, right to 060, egress to IP 1, left to 270. Lead sorted BMP north of the road, 3 sort T-80 south of the road"

Fighter to fighter briefs should be done for each pre-planned target and for attacks mid-flight, following this best practice flow:

1. Flight lead capture/tally target and create mark point

2. Plan fighter brief, write down on scratch pad

3. Transmit mark point to flight and confirm flight capture/tally target of each flight member, possible talk-on

4. Perform fighter-to-fighter brief

5. Perform attack, re-issue new fighter brief as situation develops

Cover Aircraft's priorities for lookout

The numbers here are in order of what's most important to look at while covering the shooter. 1 = highest priority, 4 = lowest

to do: embed image onto this wiki, once WYSWIG editor is up. https://drive.google.com/open?id=1-VkmqOwioYQO9SBYmkRSm9hEZcnIoszH&authuser=krause%40krauselabs.net&usp=drive_fs

Control + Comm

1. Copy FROTIES brief, perform pre-attack capture/tally and/or talk-on

2. Fly indicated formation (See FROTIES). Shooters at IP comm "[C/S] IP inbound" this lets everyone know you're lining up for the attack from the IP and so that others can ensure timing separation. Fly indicated ingress direction (See FROTIES). If there's no IP indicated, skip this line.

3. On final (or 10 seconds from weapon release) comm "[C/S] in from the [ingress direction]", dispense countermeasures

4. Recover the aircraft to the indicated egress direction (See FROTIES), dispense countermeasures and manage ECM. Comm: "Off [egress direction] [attack status]" where attack status can be: didn't attack: "dry, [optional: reason]" e.g. "Off dry 060, parameters" means i'm egressing to 060, I couldn't get the correct weapon parameters. or "Off dry 060, defending AAA south" Did attack: "[# of weapons + type] away" e.g. "Off 060, 2 long rifle away"

5. Rejoin formation, get visual. prepare for possible re-attack, resort targets as per FROTIES.

Complete example:

"Nail31 IP inbound"

"Nail31 in from the south west"

"Nail31 off to the west, two CBU away"

Laser Search Track + Comm

Tomcat: "10 seconds"/"30 seconds" = i need your laser in 10/30 seconds. This is a call to prepare the lasing aircraft to turn in for laser parameters.

Tomcat: "laser on" = turn your laser on now

A-10: "Lasing XXXX" = i'm lasing xxxx PRF code

Tomcat: "Spot" (i have contact with your laser) Or "negative laser" (i don't have contact with your laser)

if its type1/2 control (JTAC shit): A-10: Cleared hot or abort

Optional: "Stare xxxx" means use LST on indicated laser code

Israeli

see here: https://codex.uoaf.net/index.php/Israel_DEAD_SOP

How to kill a site

1. The site either needs to be continuously suppressed or attacking flights need to be continuously terrain masked while inside WEZ

2. Use HARM