Difference between revisions of "Doctrine"
| Line 10: | Line 10: | ||
Roles: For each callsign whether they are shooter (employing ordnance) or cover (Guaranteeing mutual support with visual and comm) | Roles: For each callsign whether they are shooter (employing ordnance) or cover (Guaranteeing mutual support with visual and comm) | ||
Ordnance: Weapons to use. | Ordnance: Weapons to use. | ||
| − | Timing: By x seconds or nautical miles | + | Timing: Separation By x seconds or nautical miles |
Ingress Direction: Magnetic bearing to target from IP | Ingress Direction: Magnetic bearing to target from IP | ||
Egress Direction: Magnetic bearing from target to recovery | 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. | + | 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" | 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: | 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 | + | 1. Flight lead capture/tally target and create mark point |
2. Plan fighter brief, write down on scratch pad | 2. Plan fighter brief, write down on scratch pad | ||
| − | 3. Transmit mark point to flight and confirm flight capture | + | 3. Transmit mark point to flight and confirm flight capture/tally target |
4. Perform fighter-to-fighter brief | 4. Perform fighter-to-fighter brief | ||
5. Perform attack, re-issue new fighter brief as situation develops | 5. Perform attack, re-issue new fighter brief as situation develops | ||
Revision as of 07:23, 29 November 2020
Brief description of squadron SoPs and expectations for roles within a package.
Air-to-air
Air-to-ground
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 4. Perform fighter-to-fighter brief 5. Perform attack, re-issue new fighter brief as situation develops
