Opposed Strike Package - AAR and Desired Focus Points

[Trigger]

To add my thoughts:

Loadout

• Strike flight even heavier/draggier than OCA flight. Unable to achieve A/A acceleration/maneuverability assumptions without jettisoning external stores. When operating in NTTR, stores jettison only for IFEs or over target. Weapon load was appropriate for DLOs but not for self-escorted strike with continual Red Air presence.

Mission Planning:

• Briefing focused on DLOs that were A/G related. As a package, we didn't brief collective reactions to A/A threats, flows and contingencies. Lack of A/A gameplan exploited by a quickly re-generating hostile. I certainly entered the mission with the wrong mindset for what subsequently evolved. Better to focus on fewer DLOs and do them well.
• 480GS with heavy/draggy configurations is possible but little smash available to recover if behind the timeline. Planning 450GS would allow greater flexibility.

ALR Criteria

• We have separate ALR criteria for A/A and A/G missions. For self-escorted strikes, we need to stop treating A/A and A/G as separate entities and consider a combined ALR matrix/table.

Mission Execution:

• With OCA element shot down, strike element would have aborted and/or jettisoned A/G stores if a combat operation. In a training scenario stores were retained.
• 2nd strike flight SPUN on directive from Package Cdr putting element out of position with respect to evolving fight. Discussion on Package Cdr assignment has already been captured earlier in thread. What I would highlight is that Element leads should be prepared to take initiative and react if situation deteriorates rather than waiting for a directive call from someone else.

Red Air:

• For training, Red Air should also be reactive to unfolding situation and consider whether to press in light of briefed DLOs. Mission ended up as a series of A/A engagements rather than briefed A/G-orientated DLOs.