Operation Odin's Fury with 303rd RAMBO 2 After Action Report

[Turtle]

1. MISSION​

Rambo was tasked to establish and maintain TARCAP west of Ivalo Airbase in support of the 303rd Fighter Squadron while it conducted CAS for NATO forces.

The flight’s primary responsibility was to detect, intercept, and destroy hostile fixed-wing aircraft before they could interfere with the CAS package or enter the protected operating area.

---

2. EXECUTIVE SUMMARY​

Rambo successfully completed its assigned TARCAP mission and engaged multiple hostile fighter groups consisting of MiG-29S, Su-30, and Su-33 aircraft.

The flight employed 10 AIM-120Cs and achieved six confirmed air-to-air kills:

• MiG-29S destroyed by Rambo 23 near Bullseye 052/70
• MiG-29S destroyed by Rambo 23 near Bullseye 059/78
• Su-33 destroyed by Rambo 24 near Bullseye 049/75
• Su-33 destroyed by Rambo 21 near Bullseye 047/85
• Su-30 destroyed by Rambo 23 near Bullseye 088/70
• Su-30 destroyed by Rambo 22 near Bullseye 082/55

Enemy fighters employed four observed R-27-series radar-guided missiles. All hostile air-to-air shots missed or were defeated.

Earlier in the sortie, an SA-15 near Bullseye 036/35 launched against Rambo 24 while the aircraft was near Bullseye 036/27. Rambo 14 successfully defeated the missile and remained combat effective.

Rambo 14 subsequently experienced a serious near-midair with Wing near Bullseye 030/15. No collision or aircraft damage occurred. Details below.

Following that event, additional friendly aircraft operating at or above FL280 within or immediately above Rambo’s assigned block, later identified breifly by Phoenix 1 flight, a Finnish FA/18 flight, and and MQ-9. No second near-midair or confirmed friendly crossing of a missile flight path was identified, but the overlapping traffic increased workload during commits and created legitimate deconfliction and CAF concerns.

Rambo suffered no confirmed combat losses, prevented the engaged hostile fighters from reaching the supported force, and maintained control of the assigned TARCAP area.

Upon entering EFRO airspace, Rambo 21 had a DCS Server disconnect error (Not CTD, but a "Connection Lost" issue and was kicked to the MP menu screen. Rest of flight recovered without issue.

---

3. PRE-ENGAGEMENT EVENTS​

SA-15 Engagement Against Rambo 24​

At approximately 1015:53Z, an SA-15/Tor-M2 near Bullseye 036/35 launched a 9M338K surface-to-air missile against Rambo 24.

At missile launch:

• Rambo 24 was near Bullseye 036/27
• Rambo 24 was approximately 28,400 feet MSL
• Estimated launch slant range was approximately 9.1 NM

Rambo 24 initiated an aggressive defensive reaction and descended rapidly. The missile reached its closest recorded approach approximately 25 seconds after launch.

At closest approach:

• Rambo 24 was approximately 16,800 feet MSL
• Missile separation was approximately 1.47 NM
• Rambo 14 remained combat effective

Result: SA-15 missile defeated with no damage to Rambo 24.

The engagement confirmed the presence of an active surface-to-air threat near the flight’s operating area and forced Rambo 24 into a significant altitude and flightpath change. This threat was called out and later prosecuted.

---

Near-Midair Between Rambo 24 and Archer 1-1​

At approximately 1018:06Z, shortly after the SA-15 engagement, Rambo 24 and ARCHER 21 passed extremely close near Bullseye 030/15.

Tacview-derived minimum separation was approximately:

• 144 feet total three-dimensional separation
• 31 feet horizontal separation
• 141 feet vertical separation
• Both aircraft near 22,700 feet MSL

Even accounting for telemetry limitations, the event constituted a serious near-midair collision hazard.

Result: No collision or aircraft damage.

The event occurred following Rambo 24’s defensive reaction and rapid altitude changes. The maneuvering associated with defeating the SA-15 likely increased the difficulty of maintaining awareness of nearby friendly aircraft. Thankfully ARCHER 1-1 had Situational Awareness and was able to prevent the possible midair.

---

4. AIRSPACE DECONFLICTION CONCERNS​

Following the near-midair, several additional friendly aircraft were observed at or above FL280 within the same general TARCAP and commit airspace. Rambo flight was not aware that additional airborne AI assets would be operating in the area.

• At approximately 1027:56Z, Phoenix 1-2 operated near Bullseye 011/21 at FL280-FL300, passing approximately 4.7 NM laterally from Rambo 21 with minimal vertical separation. No immediate risk of midair, but a good reminder to check blocks.
• At approximately 1029:56Z, a Recce Charlie MQ-9 near Bullseye 034/27 at FL290 passed approximately 0.93 NM laterally and 235 feet vertically from Rambo 24.
• At approximately 1031:30–1031:52Z, two Enontekio CAP F/A-18s operated near Bullseye 046/34 and 051/34 at FL316–317. The aircraft passed within approximately 0.4–0.6 NM laterally of Rambo aircraft, although approximately 3,400 feet of vertical separation remained, this was affecting commit mechanics.
• During the primary air-to-air engagement, the Recce Charlie MQ-9 remained near FL290 and came within approximately 12.8 NM laterally and 130 feet vertically of Rambo 24 near Bullseye 030/31. No factor but we did see it and didn't know who was operating in our blocks.

Tacview did not show another near-midair or a friendly aircraft directly crossing the recorded path of a Rambo AIM-120C. However, the repeated presence of friendly aircraft within or immediately at or above Rambo’s assigned altitude block created a legitimate tactical concern.

The traffic required Rambo pilots to divide attention between:

• Hostile fighter groups
• Missile support requirements
• Defensive maneuvering
• Friendly-aircraft deconfliction
• Positive track correlation
• CAF verification before weapons employment

Even where technical separation existed, uncertainty regarding friendly position and altitude reduced Rambo’s maneuvering freedom and added avoidable workload during commit profiles.

This was particularly concerning while aircraft were climbing, descending, cranking, supporting missiles, or maneuvering to place hostile groups inside weapons parameters.

---

5. AIR-TO-AIR ENGAGEMENT SUMMARY​

Initial MiG-29S Engagement — Bullseye 052/70​

At 1039:49Z, Rambo 23 employed an AIM-120C against a MiG-29S near Bullseye 052/70 from approximately 26.0 NM.

Nine seconds later, Rambo 24 employed a second AIM-120C against the same aircraft from approximately 23.4 NM.

Rambo 23’s missile intercepted and destroyed the MiG-29S. Rambo 14’s missile remained in flight after the target had already been destroyed and produced no additional effect.

Result:
1 × MiG-29S destroyed by Rambo 23

The engagement achieved the desired tactical result but resulted in an unnecessary second missile being expended against the same target.

---

Su-30 Engagement — Bullseye 077/77​

At approximately 1042:05Z, Rambo 21 employed an AIM-120C against a Su-30 near Bullseye 077/77 from approximately 31 NM.

The Su-30 recognized the threat, turned to place the missile near the beam, and continued defensive until cold. The maneuver degraded the intercept geometry and forced the AIM-120C to expend energy. The missile closed to approximately 6.5 NM before falling behind and terminating without effect.

Result: Su-30 defeated the AIM-120C through effective defensive maneuvering; no damage confirmed.

---

Second MiG-29S Engagement — Bullseye 059/78​

At 1045:37Z, Rambo 23 employed an AIM-120C against a second MiG-29S near Bullseye 059/78.

The missile was released from approximately 20.7 NM and successfully intercepted the aircraft.

The MiG-29S employed an R-27-series missile shortly after Rambo’s shot. The hostile missile failed to impact a Rambo aircraft.

Result:
1 × MiG-29S destroyed by Rambo 13

---

First Su-33 Engagement — Bullseye 049/75​

At 1045:46Z, Rambo 14 employed an AIM-120C against a Su-33 near Bullseye 049/75.

The missile was released from approximately 23.3 NM and successfully intercepted the aircraft.

At 1046:31Z, Rambo 21 employed an AIM-120C from approximately 34.9 NM with the target near Bullseye 045/88. This was a 2nd shot at the SU-33 which RAMBO 24 had just barely destroyed.

Result:
1 × Su-33 destroyed by Rambo 24

The employment removed the threat before it could close with the formation or supported package.

---

Second Su-33 Engagement — Bullseye 047/85​

Rambo 21 engaged a second Su-33 as it maneuvered southwest toward the defended area.

At 1047:04Z, Rambo 21 employed a second AIM-120C from approximately 26.1 NM. The target had progressed to approximately Bullseye 047/85.

The missile successfully intercepted and destroyed the Su-33.

Result:
1 × Su-33 destroyed by Rambo 11

---

First Su-30 Engagement — Bullseye 088/70​

At 1047:19Z, Rambo 23 employed an AIM-120C against a Su-30 near Bullseye 088/70.

The missile was released from approximately 21.9 NM and successfully intercepted the aircraft.

Result:
1 × Su-30 destroyed by Rambo 13

This was Rambo 13’s third AIM-120C employment and third confirmed kill.

---

Second Su-30 Engagement — Bullseye 084/64 to 082/55​

At 1047:39Z, Rambo 24 employed an AIM-120C against a second Su-30 near Bullseye 084/64.

The missile was released from approximately 19.3 NM and reached the aircraft. The Su-30 remained airborne and capable following the intercept, indicating probable damage without immediate destruction.

At 1048:49Z, Rambo 12 employed an AIM-120C from approximately 17.7 NM, with the target near Bullseye 082/55.

Rambo 22’s missile successfully intercepted and destroyed the Su-30.

Result:

• Probable damage by Rambo 24
• 1 × Su-30 destroyed by Rambo 22

The follow-up employment ensured the damaged aircraft was removed from the fight rather than being prematurely assessed as destroyed.

---

6. ENEMY WEAPONS EMPLOYMENT​

Surface-to-Air Threat​

• 1 × SA-15/9M338K launched against Rambo 24
• Missile missed or was defeated
• No damage to Rambo 24

Air-to-Air Threats​

Enemy fighters employed four observed R-27-series radar-guided missiles:

• 1 × R-27-series missile employed by a MiG-29S
• 3 × R-27-series missiles employed by Su-30 aircraft

All four hostile air-to-air missiles missed or were defeated.

No hostile weapon impacted a Rambo aircraft.

No air-to-air engagement progressed to a visual merge, and no AIM-9 or gun employment was required.

---

7. WEAPONS AND KILL SUMMARY​

Rambo 21​

• AIM-120Cs employed: 3
• Confirmed kills: 1
• Result: 1 × Su-33

Rambo 22​

• AIM-120Cs employed: 1
• Confirmed kills: 1
• Result: 1 × Su-30

Rambo 23​

• AIM-120Cs employed: 3
• Confirmed kills: 3
• Results:
  • 2 × MiG-29S
  • 1 × Su-30

Rambo 24​

• AIM-120Cs employed: 3
• Confirmed kills: 1
• Additional result:
  • 1 × Su-33 destroyed
  • Probable damage to 1 × Su-30

Flight Total​

• AIM-120Cs employed: 10
• Confirmed kills: 6
• Observed missile-to-kill ratio: 60 percent

All four flight members achieved at least one confirmed air-to-air kill.

Successful Launch Ranges​

• Longest confirmed kill: 26.1 NM — Rambo 11 against Su-33
• Shortest confirmed kill: 17.7 NM — Rambo 12 against Su-30
• Average successful launch range: Approximately 22.6 NM
• All six confirmed kills occurred from approximately 18–26 NM

---

8. WHAT WENT WELL​

Mission Accomplishment​

Rambo completed the assigned TARCAP mission and destroyed six hostile fighters before they could effectively interfere with the supported CAS package.

BVR Lethality​

The flight rapidly reduced multiple hostile fighter groups during an engagement lasting less than ten minutes.

Defensive Survival
Rambo defeated:

• Four hostile air-to-air missiles
• One SA-15 surface-to-air missile

No blue aircraft were lost to hostile A/A fire.

Prevention of the Merge​

All six kills occurred beyond visual range. The enemy was unable to force Rambo into a visual engagement or gain unrestricted access to the protected CAS force.

Kill Confirmation and Follow-Through​

The flight did not assume the second Su-30 was destroyed following Rambo 24’s missile intercept.

Rambo 12 maintained engagement responsibility and secured the kill with a follow-up shot.

---

9. AREAS FOR IMPROVEMENT​

Friendly-Aircraft Deconfliction​

The near-midair between Rambo 24 and Falcon 11 was the most serious safety event of the sortie.

The event, combined with additional friendly aircraft operating within or immediately above Rambo’s block, demonstrated the need for stronger package-level altitude and airspace discipline.

Flights should communicate before:

• Entering another flight’s altitude block
• Crossing an established CAP or TARCAP station
• Climbing or descending through another flight
• Maneuvering through an active commit corridor
• Operating near a known weapons-employment lane

Defensive calls should include:

• Callsign
• Bullseye or geographic position
• Current altitude
• Direction of maneuver
• Expected altitude change
• Threat being defended

CAF and Weapons-Corridor Awareness​

Friendly traffic operating near the commit area increased the requirement for positive track correlation and CAF verification.

Flights operating near TARCAP should remain clear of anticipated commit and weapons-employment corridors unless specifically coordinated.

Target Sorting and Shot Deconfliction​

The opening engagement resulted in Rambo 23 and Rambo 24 employing against the same MiG-29S within nine seconds.
Additionally, Rambo 21 fired an Aim-120 at a target that was already targeted and destroyed as the missile came off the rail.

Future commits should clearly establish:

• Assigned hostile group
• Individual target within the group
• Shooter
• Supporting aircraft
• Recommit responsibility

Communications Discipline​

Immediate and concise calls would improve flight awareness and reduce duplicate employment:

• Fox
• Pitbull
• Timeout
• Splash
• Defensive
• Altitude change

Weapons Conservation​

Rambo achieved the desired tactical result but expended four missiles that did not produce confirmed kills.

Improved sorting and shot discipline could have retained additional weapons for follow-on fighters or protection during egress.

Surface-Threat Awareness​

The SA-15 engagement forced Rambo 24 into a significant defensive maneuver and altitude change.

TARCAP positioning should account for known or suspected surface-to-air engagement zones whenever mission geometry permits.

---

10. LESSONS LEARNED​

• Stick to targeting contracts before entering weapons parameters.
• Sort hostile groups and individual aircraft before weapons release whenever tactical conditions permit.
• Make immediate Fox and missile-status calls to prevent duplicate employment.
• Continue supporting missiles until active, target destruction, or a contracted or directed abort.
• Do not assess a target as destroyed solely because a missile reached it.
• Coordinate follow-up shots and positively transfer targeting responsibility.
• Preserve missile inventory when a shot does not provide sufficient tactical value.
• Maintain element mutual support during commits, defensive reactions, and recommits.
• Communicate defensive maneuvers and altitude changes immediately.
• Maintain positive awareness of nearby friendly formations during high-G maneuvering.
• Enforce altitude blocks and coordinate all transitions through another flight’s airspace.
• Keep nonparticipating aircraft clear of active commit and weapons-employment corridors.
• Confirm CAF before employment when friendly traffic is operating near the hostile group.

---

11. OVERALL ASSESSMENT​

Mission Result: SUCCESSFUL

Rambo successfully completed its TARCAP mission in support of the 303rd Fighter Squadron.

The flight demonstrated strong beyond-visual-range lethality, effective defensive reactions, and meaningful participation by all four aircraft.

Thanks for having us again. That was a blast!!