Ukraine Waited for Russia’s Fighter Jet to ATTACK — Then Blew It Up

Overview

The video provides a tactical, step-by-step account (presented as a near “scenario breakdown”) of how Ukrainian and American air assets allegedly set up and executed an ambush against a Russian Su-35 pilot over/near Luhansk.

Alleged sequence of events

1) Patriot radar cueing and tracking

• An American Patriot air-defense radar is described as detecting and tracking the Su-35’s maneuvers for an extended period (about 20 minutes).
• The key claim is that the radar never “reveals itself” in a way the Russian aircraft can reliably detect.
• Meanwhile, it continuously updates missile crews and connected fighters with targeting data.

2) Ukrainian “bait” and geometry

• A MiG-29 is portrayed as intentionally flying in a way that looks like easy, isolated prey.
• The lure is said to be timed to the Su-35 pilot’s habitual flight window.
• The geometry is described as engineered so the Su-35 enters a predictable engagement envelope.

3) First missile engagement fails

• The Russian fires an R-77 air-to-air missile (described as active radar-capable, with effective range heavily dependent on engagement geometry).
• Because the MiG escapes and because American tracking allegedly predicted the shot, the missile is portrayed as missing and becoming essentially ineffective—likened to an “expensive lawn dart.”

4) Networked multi-aircraft kill chain (Link-16 concept)

• The video emphasizes that multiple F-16s can engage without illuminating targets using their own radars.
• Instead, they reportedly use shared data from the Patriot track via a network (described as Link-16).
• This allows the F-16s to fly to an optimal missile-employment position.

5) “Hiding in the notch” using terrain/background clutter

• The F-16s allegedly approach low altitude with a crossing geometry relative to the Su-35.
• The claim is that the Russian radar filters them out as ground clutter.
• The video describes maintaining closure rates within a radar clutter-rejection band to reduce detection until it’s too late.

6) Second engagement: AMRAAM shots

• The F-16 lead launches AMRAAM, specifically described as AIM-120C AMRAAM.
• The video claims reduced effective range for head-on vs. tail-chase configurations, making altitude and position critical.
• It also asserts that the Su-35 evades at least one incoming missile using thrust-vectoring and maneuverability.

7) Moscow map error / contested-ground shift claim

• A central “why it worked” explanation is that the Su-35 pilot’s situation map was wrong.
• The video alleges contested ground was marked as captured where it actually wasn’t.
• This purportedly led him to believe an exit direction/area was safe, resulting in him flying into an additional Patriot coverage zone/launcher emplacement.

8) Su-35 ultimately shot down (and impact confirmation)

• The video then claims a second missile engagement finishes the Su-35.
• It describes two AMRAAMs converging within tight timing windows.
• It concludes the Su-35 is destroyed, adding that the pilot may have ejected, but that proof was not shown publicly.
• It further describes use of a Ukrainian quadcopter to confirm the crash/impact location.

9) Verification by imagery

• The video asserts the wreck was geolocated near the village of Moski (about 26 miles from the front line).
• This is presented as evidence against the Russian side’s narrative about what happened.

Presenters or contributors

• The video narrator/creator (not individually named in the subtitles)
• No other named presenters or contributors are listed in the provided subtitle text.