The Drone War Is Now a Logistics War

At 11:46 UTC on 20 July 2026, the Telegram channel AMK Mapping reported that Ukrainian mid-range drones had hit several air-defence and radar targets across Krasnodar Krai and Russian-controlled Zaporizhzhia Oblast. The strike package, according to the channel's running tally, included two Nebo-SV radar installations and one Nebo-U radar system. An hour later, the same channel logged three Ukrainian locomotives struck by Russian Geran-2 drones in Zaporizhzhia Oblast. By 11:50 UTC, it was reporting a separate SBU drone package, thirteen airframes in all, on a large complex in Russian-controlled Kherson Oblast that Kyiv says the FSB has been using as a forward operating site.

Three incidents, ninety minutes apart, all on the same rail-and-radar axis. Read together, they sketch a war that is no longer primarily about who holds which village. It is about who can still move.

The targets are not symbolic

Nebo-SV and Nebo-U radars are not prestige items. They are the eyes of Russia's medium- and high-altitude air-defence network, the systems that cue S-300 and S-400 batteries onto incoming jets and cruise missiles. Hitting two of one type and one of the other in a single morning is not harassment. It is degradation of a sensor chain that takes years to reconstitute and that cannot be hidden in a forest, because the radar horizon is the radar horizon.

The locomotive strike sits in the same category. Rail capacity inside the occupied south has been Russia's principal answer to the problem of moving troops, ammunition and fuel along a front that now runs roughly 1,200 kilometres. Three locomotives taken out in one pass is the kind of loss that does not register on a map but registers immediately inside a rail-traffic control room. Ukrainian services have been hunting Russian locomotives with long-range drones since at least 2024; what is striking here is the simultaneity, the implication that strikes on radar and strikes on rolling stock are now being choreographed from the same planning cycle.

The FSB compound, and what Kyiv is signalling

The Kherson complex is the more politically loaded of the three hits. Striking a site the SBU says is being used by Russian domestic-security forces extends the logic of previous Ukrainian strikes on command nodes, but it also draws a line under the way Ukraine has framed the war since the early months of the full-scale invasion: this is not a conflict between two uniformed militaries, it is a contest with a state apparatus that uses intelligence services as frontline operators.

There is a counter-reading worth airing. Russian-aligned channels have, in past incidents, disputed Ukrainian claims about which agency controls a struck site, and the SBU does not publish the imagery on which its attribution rests. Kyiv's framing is consistent with its political project; that does not make it wrong, but it does mean the site has messaging value independent of its military value, and the two should not be conflated. The sources available to this publication do not specify casualty figures or the precise function of the complex.

What the pattern reveals

Taken as a series rather than as headlines, the morning's three reports describe a doctrine that has matured faster than the public commentary around it. The logic is straightforward and unglamorous. To pressure a larger army dug into prepared positions, you do not need to defeat its infantry. You need to deny it the ability to see, to move, and to coordinate. Radar degradation and locomotive attrition are the upstream interventions that make everything downstream possible.

This is not a new insight. Industrial-age warfare has always been a contest over logistics and reconnaissance. What is new is the price of admission. The platforms doing this work in July 2026 are mid-range Ukrainian drones whose unit cost is a small fraction of the systems they are destroying. That asymmetry, more than any individual strike, is the structural story of the war right now, and it is the reason the fighting has begun to look less like a grinding land campaign and more like a slow strangulation of the deeper supply chain.

What remains uncertain

The hard limits of this picture are worth naming. AMK Mapping aggregates open-source reporting and Telegram claims, and its tallies are best understood as a near-real-time ledger rather than a verified battle damage assessment. Russian sources have not, as of publication, publicly confirmed the radar losses in Krasnodar Krai, and Russian reporting on the Kherson strike is consistent with a pattern in which damage is initially understated and later acknowledged only when replacement imagery surfaces. The locomotive strike in Zaporizhzhia is corroborated in direction (Russian Geran-2 loitering munitions operating in that oblast) but the sources do not specify the operational status of the three engines after impact.

For readers tracking the war, the date to watch is not the next territorial exchange but the next window in which Russian rail traffic through southern Ukraine can or cannot be sustained at current tempo. That is the metric the morning's strikes were designed to move, and it is the metric by which they will ultimately be judged.

This publication framed the morning's three strikes as a single logistical campaign rather than as discrete events, on the reasoning that the simultaneity across Krasnodar, Zaporizhzhia and Kherson is itself the news. Western wires led with the SBU FSB-site claim; Russian-aligned channels led with the locomotive strike. Both emphases miss the rail-and-radar axis that ties them together.

Wire provenance

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

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