A $500 drone, a Mi-28, and 87 km of front: how cheap airframes are rewriting the deep-strike math

Footage circulated on 15 July 2026 purporting to show a Ukrainian first-person-view (FPV) drone striking a Russian Mi-28 attack helicopter mid-air near the village of Vyazovoe in Russia's Belgorod region. The clip, posted by the Telegram channel Clash Report at 08:33 UTC, shows a small quadcopter-type airframe closing on a rotorcraft from above and behind; the impact is visible, but the final state of the airframe is not. By 10:27 UTC the channel War Translated, summarising Ukrainian reporting, stated the strike occurred "at around 10:00 a.m." and described the Mi-28 as shot down. AMK_Mapping, a conflict-mapping account, put the distance from the frontline at roughly 87 km.

What the footage actually proves is narrower than either the more enthusiastic Ukrainian channels or the dismissive Russian counter-narrative would like. A FPV drone is on screen. A helicopter is on screen. A collision is on screen. Whether the crew survived, whether the rotorcraft crashed in a controlled descent or an uncontrolled one, and whether this was a one-off intercept or part of a deliberate hunt, are questions the public record cannot yet answer. Those caveats matter, because the framing is doing as much work as the video.

A new depth of reach

The 87 km figure is the headline. Russian attack helicopters have, until this year, operated with relative impunity in a band 30 to 60 km behind the forward edge of the battlefield, where they sit just outside the envelope of most Ukrainian tube and rocket artillery but inside their own Loitering Munition and Krasnopol engagement zone. Pushing the Mi-28 out to 87 km suggests either a deeper Ukrainian launch, a redirected munition, or a helicopter operating closer to the line than doctrine would prefer. The Mi-28N, the export-standard variant in Russian service, has a ceiling useful for the kind of low-level pop-up attack profile it favours, but it is not fast, and it is not stealthy. In other words: it is the kind of platform that an FPV drone, once vectored, can find.

The asymmetry is the story. A frontline Mi-28 costs in the high tens of millions of dollars. An FPV quadcopter, even a militarised one with a shaped-charge warhead, costs roughly the price of a used motorcycle. Reports from inside the Ukrainian defence-tech ecosystem put individual airframes at a few hundred dollars apiece; warheads and ground stations add a multiple on top, but the unit economics still run the wrong way for the side flying the helicopters. Defence ministries have absorbed this arithmetic on the ground, where drones have eaten the minefield and the trench. The new question raised by the Belgorod footage is whether the same substitution is now reaching into the rotary-wing domain over hostile territory.

The Russian counter-read

Russian-aligned channels have, predictably, framed the footage as either a fabrication, a strike on a decoy, or a hit on a friendly helicopter mistakenly engaged by Russian air defence. That third reading is plausible in the abstract: Russian SHORAD and MANPADS units have shot down Russian aircraft before, including helicopters, and the airspace over Belgorod has been crowded with friendly and hostile drones since the cross-border campaign began. None of the Russian-aligned channels cited in open-source reporting have produced primary footage showing the helicopter on the ground intact, which is what would be required to make the decoy or friendly-fire claims stick. The more parsimonious reading, given the angle of the strike and the absence of any visible countermeasure deployment, is that the helicopter was struck by the drone and that the airframe's fate is, for now, genuinely unknown.

This is a pattern worth naming. Russian military communications have become structurally conservative about acknowledging aircraft losses. In the early phase of the full-scale invasion, fixed-wing losses were sometimes denied for days before surfacing in third-party OSINT. Helicopter losses are easier to hide because they tend to occur closer to friendly airfields and the wreckage can be recovered. The result is a reporting environment in which the burden of proof effectively inverts: footage of a strike is treated as inconclusive until Russian channels confirm the loss, even though confirmation is, by custom, slow.

Why this matters beyond one airframe

The single helicopter is a rounding error. What matters is the trajectory. If FPV-class drones can credibly reach helicopters operating 80 to 100 km behind the line, the Russian helicopter force has to either (a) fly farther back and forfeit its usefulness in close air support, (b) fly higher and forfeit its concealment from optical sensors, or (c) accept higher loss rates and price them into sortie planning. None of those options is free. Close air support for Russian motor rifle units on the line is one of the few remaining organic fire-support multipliers that does not depend on glide-bomb aviation or expensive one-way missile strikes. Eroding it changes the math for any Russian ground offensive that depends on rotary-wing top-cover.

The same dynamic is playing out, more quietly, on the Ukrainian side. Helicopter losses to Russian Lancet-type loitering munitions have been a recurring feature of the air war since 2024. The novelty in the Belgorod footage is the direction of the exchange: a small Ukrainian drone reaching into Russian helicopter operating airspace, rather than a Russian drone reaching into Ukrainian helicopter operating airspace. The defensive advantage has flipped on at least one axis.

What remains genuinely uncertain

The sources do not specify how the FPV drone was vectored onto the target: whether it was guided by a forward observer with line of sight, by a relay chain, by an autonomous terminal phase, or by signals intelligence cueing onto the helicopter's radar or radio emissions. They do not specify which unit launched the drone, which Ukrainian formation claimed the engagement, or whether any Russian authorities acknowledged the loss within hours of the strike. They do not specify whether the helicopter was carrying ordnance at the time, which would have implications for the kill chain regardless of airframe survival. Each of these unknowns is real, and each will probably be resolved in fragments over the coming weeks: obituary posts from Russian municipal channels, satellite imagery of the crash site if it can be located, and the slow accumulation of flight-log data from open-source aviation trackers.

For now, the conservative read is this: a helicopter was struck, the airframe's fate is unconfirmed, and the operating assumptions behind Russian rotary-wing employment near the border are about to be tested harder than they have been at any point in this war.

This article was written in Monexus's defence desk voice: source-restraint first, framing second. Where the public footage and the Russian-aligned channels disagree, both are named and the disagreement itself is the story.

Wire provenance

This editorial synthesis draws on the following public wire/social posts:

• https://t.me/ClashReport
• https://t.me/AMK_Mapping
• https://t.me/wartranslated