Drone strike at Belbek: how Ukraine's intelligence service keeps reaching into Crimea

The footage, posted on 4 July 2026 by operators who have hit Belbek before, shows a low drone track over the airfield on Crimea's southern coast, a flash, and a column of black smoke climbing over the parking apron. Within hours the same material had been relayed by two independent English-language channels, with no Russian acknowledgement either confirming or denying the strike. Belbek is no ordinary Russian airbase. Sitting about nine kilometres northwest of Sevastopol, it has hosted fighters, bombers and, by multiple open-source accounts, the surveillance aircraft that have guided Russian strikes into southern Ukraine. Every Ukrainian attempt to reach it is also, by design, an attempt to reach the machinery that makes those strikes possible.

The pattern of the operation is now familiar. Ukraine's military intelligence service, the HUR, claims or is widely credited with a string of long-range strikes into Russian-occupied territory, and Belbek has been one of the recurring targets since the war's first summer. The 4 July episode, as far as the open-source record on the day goes, rests on the operators' own video, the two relay channels, and corroboration that, by long-standing open-source habit, comes through Russian military bloggers rather than Russian officialdom. Russian milbloggers described something hitting the base. The Russian Ministry of Defence did not.

What is being struck, and why

Belbek's role inside the invasion's air war is unusually well documented. Satellite imagery and open-source flight tracking have repeatedly placed reconnaissance assets and strike aircraft at the base, including platforms involved in attacks on Ukrainian port infrastructure and the energy grid. A strike there is not symbolic. It pulls aircraft out of service, forces dispersal, and burns fuel and munitions. Each successful attempt tightens the operating tempo for Russian crews flying sorties over Mykolaiv, Kherson and Odesa.

The targeting choices also reveal a tactical bet. Ukraine has chosen to invest in long-range strike capacity rather than rely on donations of Western airframes alone. The Belbek attempts, alongside earlier strikes on Saky, on Kerch bridge approaches, and on the Russian Black Sea Fleet's logistics in Sevastopol, form a coherent campaign to attrit the Crimean basing complex that has made the southern theatre sustainable for Moscow. Crimea, in this read, is treated less as territory to be liberated in a single operation and more as a node whose value to Russia can be degraded until it becomes indefensible.

The record on the day, and where it thins

What is verifiable from the 4 July material is limited. The footage is dated, the location is consistent with the published geometry of Belbek's apron, and the two relay channels carried it within hours. What is not verifiable is the result. Independent geolocation of fresh craters, satellite confirmation of destroyed airframes, and Russian official comment are all absent on the day. Two of the relay channels have a record of carrying Ukrainian and sympathetic-source material. None of this means the strike did not happen; it means the visual record is doing the work that independent imagery cannot yet corroborate.

A second sourcing layer comes from the Russian milblogger ecosystem. Rybar, Two Majors and WarGonzo, all of which have been cited by international open-source analysts for tipping the location of Russian strikes before Russian officialdom does, were reporting around the time the footage circulated. The milbloggers describe a strike. They do not, in the material available on the day, give a damage assessment. The combination is typical: Ukrainian operators release footage of the inbound, milbloggers confirm the inbound landed, and damage assessment is settled days later by analysts or by satellite.

Why the silence matters

Russian silence on individual strikes in Crimea has become the norm since 2022. The pattern is well documented. Moscow confirms what it wants to be known, disputes what suits the battlefield narrative, and ignores the rest. Belbek is a politically sensitive target. Confirmation would concede that Ukrainian drones are reaching into the peninsula with regular effect. Denial is impossible once satellite analysts and milbloggers have accepted the location. The third path, which is the one observed, is to say nothing and let the footage do its own work.

That silence also shapes how the strike will be absorbed by Russian domestic audiences. State-aligned channels have, over the war, leaned heavily on the framing that Crimea is secure and that the peninsula's air defence is intact. Each unacknowledged strike forces the framing to do more work. Belbek is, in this sense, a small propaganda cost on top of a small material cost.

The structural read

The campaign around Belbek is best understood not as a series of one-off raids but as a sustained investment in a specific operational problem: how to make Russian basing in Crimea expensive enough to compress the sortie rate over southern Ukraine. The strikes are being layered with attempts on logistics nodes in occupied Kherson, on radar and air defence positions around the peninsula, and on the Russian naval infrastructure in Sevastopol. None of the layers on its own is decisive. Their cumulative effect is to convert Crimea from a fortress into a forward operating base under constant pressure.

The investment also tells a story about Ukrainian force design. Western airframes have arrived, but they have arrived slowly and in limited numbers. Kyiv has, in parallel, built and bought a deep strike complex that mixes Ukrainian-produced long-range drones, modified aircraft and loitering munitions. Belbek is the kind of target that complex is built to hit. The 4 July attempt, in this read, is less about a single airframe destroyed and more about keeping the option open: that another Belbek strike can be flown, at this range, on this timeline, with this kind of evidence package.

What to watch next

Three indicators will tell readers whether the 4 July strike landed the blow its operators intended. First, satellite imagery of the parking apron in the 72 hours after the strike, which will either show fresh damage or no damage at all. Second, the rhythm of Russian sorties over Odesa and Mykolaiv in the week that follows, which will reveal whether a meaningful number of aircraft have been pulled off the line. Third, the next iteration of the milblogger damage assessment, which has tended, on Belbek strikes past, to revise upwards over several days as analysts work through the imagery.

Until those markers land, the 4 July strike sits where most Belbek strikes have sat since the war began: in the gap between an operator's claim, a relay channel's broadcast, and a silence from Moscow that is itself part of the story.

Sources

• TSN Ukraine, Telegram channel: https://t.me/TSN_ua
• WarTranslated, Telegram channel: https://t.me/wartranslated
• Clash Report, Telegram channel: https://t.me/ClashReport
• Belbek airbase, Wikipedia: https://en.wikipedia.org/wiki/Belbek_airbase
• Russian invasion of Crimea, Wikipedia: https://en.wikipedia.org/wiki/Russian_invasion_of_Crimea

Desk note: Monexus ran this story on the operators' own footage and on two independent English-language channels that relayed the same material within hours. The Russian side has not, at the time of writing, confirmed or denied the strike. Where the reporting relies solely on Ukrainian and sympathetic-channel sources, that sourcing is named in the body, readers should weight the claim accordingly until independent geolocation or Russian official acknowledgement appears.