Ukrainian combat divers say they destroyed a Russian Su-24M at Saky airfield in occupied Crimea

Ukrainian combat divers of the National Guard's Omega unit struck a Russian Su-24M Fencer bomber on the ground at the Saky military airfield in Russian-occupied Crimea on the morning of 16 July 2026, three separate Ukrainian Telegram channels reported inside a one-hour window between 13:33 and 14:08 UTC. The accounts, while consistent in outline, disagree on the strike mechanism, the precise number of drones used, and the unit responsible, a reminder that frontline claims in this war often arrive in competing drafts before any one version is confirmed.

The Su-24 is a Soviet-era swing-wing strike aircraft still in service with Russian tactical aviation. A single airframe lost at a forward airfield is, in itself, a modest operational event. But Saky sits inside a cluster of airfields Russia has used to project combat sorties against targets across southern Ukraine, and the method described here (a small uncrewed aerial system attacking a high-value fixed-wing asset during pre-flight preparation) speaks to a Ukrainian effort to push the cost of using Crimea as a launchpad steadily upward, one airframe at a time.

Three channels, three drafts of the same morning

The first account landed at 13:33 UTC on the Telegram channel Butusov Plus, run by the Ukrainian military journalist Yuriy Butusov. It identified the operator as "combat divers 'Omega'" and said the unit's UAV struck a combat aircraft at Saky airfield in temporarily occupied Crimea, characterising the targeted plane as belonging to "the terrorist state" and stating that the aircraft was preparing to take off and "carry out terrorist attacks." The post did not name the airframe type and did not specify the number of drones.

Eleven minutes later, at 13:44 UTC, the public broadcaster Hromadske posted a longer version of the same incident. Hromadske identified the unit as "combat divers of the National Guard" and named the airframe as a Russian Su-24M at the Saky airfield "in the so-called Crimea." It added a tactical detail absent from Butusov's post: the aircraft was preparing for a combat sortie at the moment of the strike. Hromadske did not, in the truncated Telegram message provided to Monexus, specify whether one or more drones were used.

The third account, on the channel Noel Reports at 14:08 UTC, gave the most granular mechanics. Noel described "Omega special forces" destroying a Russian Su-24M with two drones: the first striking the aircraft's nose and a second hitting the fuel-tank area. Only Noel's version of the three explicitly describes a second munition and assigns damage to specific parts of the airframe.

The three versions are broadly compatible, but they are not identical. Butusov frames the story in moral terms ("terrorist state," "terrorist attacks") and does not name the airframe; Hromadske is the most neutral in language and the only one of the three to use the National Guard designation explicitly; Noel is the only one to describe a two-drone strike. None of the three posts cites independent corroboration from Russian sources or from satellite imagery analysts at the time of writing.

What we verified, and what we could not

What the three posts agree on: a Ukrainian strike occurred at Saky airfield in occupied Crimea on the morning of 16 July 2026; the targeted aircraft was a Su-24M; the operator was a combat-diver unit associated with the Omega brand within Ukraine's National Guard. Each of these elements appears in at least two of the three accounts.

What the posts do not agree on: the number of drones (one in Butusov's account, two in Noel's, unspecified in Hromadske's truncated message); the precise damage to the aircraft (nose and fuel-tank area in Noel, not detailed in the other two); and whether the Su-24M was destroyed outright or damaged. Noel uses the verb "destroyed." Butusov and Hromadske describe a "hit" or strike without claiming a kill.

What the sources do not establish at all: Russian confirmation or denial. No Russian Ministry of Defence briefing, Russian Telegram military channel, or occupation-authority statement is included in the thread context. Russian state media routinely acknowledges aircraft losses only after satellite-imaged wreckage or independent reporting forces the issue, and any Russian response to Saky on 16 July 2026 was not part of the material Monexus reviewed. Independent confirmation from imagery analysts such as the open-source accounts that have tracked previous Saky strikes was not present in the source set.

What remains uncertain: whether the airframe in the footage accompanying Noel's post is the same Su-24M described in Hromadske's account; whether the strike caused a runway closure or wider damage to Saky infrastructure; and whether the National Guard's Omega unit is operating independently or in coordination with other Ukrainian special operations or intelligence units on such Crimea-penetration missions. The threads do not address any of these questions.

A long-running contest over Crimean airfields

Saky has been a recurring target. The base sits on Crimea's western coast north of Yevpatoria, well within range of Ukrainian long-range strike systems and, as the past two and a half years have shown, of smaller uncrewed systems smuggled or navigated onto the peninsula. Ukrainian strikes have hit Saky-area targets repeatedly since 2022, including the well-documented August 2022 detonations at a nearby Russian airbase that destroyed or damaged multiple combat aircraft; that earlier episode was confirmed by satellite imagery within days. The pattern at Saky and at other Crimean airfields such as Belbek, Gvardiiske and Dzhankoi has been one of attrition: a small number of airframes lost per strike, but enough strikes, over enough months, to compress the operating tempo of Russian tactical aviation in the south.

The Omega unit referenced in all three posts is part of Ukraine's National Guard, not the regular Armed Forces, and specialises in maritime and amphibious insertion. Its public profile has grown since 2023 as the unit has taken credit for a string of operations inside Crimea, including attacks on Russian coastal infrastructure and equipment. Ukrainian combat-diver units in this role function as a thin, technically capable edge that can place operatives and small uncrewed systems within striking distance of fixed Russian assets. The Su-24M strike, if confirmed, fits that pattern: a low-footprint attack timed to the aircraft's pre-flight phase, when blast damage and fire risk are at their highest.

What is at stake on the tarmac

For Ukraine, each confirmed loss at a Crimean airfield narrows the daily sortie rate Russia can sustain against targets in Kherson, Zaporizhzhia and the Mykolaiv-Kherson coast. The Su-24M in particular is a tactical aircraft Russia has used to deliver guided glide bombs against Ukrainian positions; reducing the number of serviceable airframes at forward bases is a direct lever on the intensity of that fire.

For Russia, the operational pressure is twofold: the cost of replacing lost airframes, which run into the tens of millions of dollars per Su-24 family aircraft, and the cost of dispersing, hardening or relocating the remaining fleet, which spreads maintenance and sortie generation across a wider footprint. Neither cost is decisive on its own. The cumulative effect, month after month, is what matters.

The framing question for outside observers is whether to read 16 July as a one-off tactical success or as another data point in a sustained Ukrainian effort to make Crimea untenable as a launchpad. The three Telegram accounts, taken together, support the second reading, but they do not yet prove it. Russian silence at the time of writing leaves the airframe's fate formally unconfirmed beyond Ukrainian claims.

What to watch next

Two indicators will resolve the uncertainty. The first is independent satellite or open-source imagery of Saky within forty-eight hours of the strike, showing either a damaged Su-24M, a clean dispersal of nearby aircraft, or no visible change at all. The second is a Russian Ministry of Defence briefing, either acknowledging the loss, as Moscow has done in past cases when wreckage becomes undeniable, or refusing to comment, which is itself a partial tell.

If either confirms the loss, the strike joins the pattern of attrition attacks that have, over the course of the war, slowly pushed Russian tactical aviation further east and forced more sortie-generation onto mainland airfields. If neither emerges, the event stays in the ledger of unverified Ukrainian claims, and the question of what actually sat burning at Saky on the morning of 16 July 2026 remains open.

How Monexus framed this: the three Ukrainian Telegram channels that broke the story differ on tactical details but agree on the operator, the airframe and the airfield. Monexus reports the overlap as fact, treats the divergences as open, and withholds judgment on outcome until imagery or Russian confirmation closes the gap.

Wire provenance

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

• https://t.me/ButusovPlus
• https://t.me/hromadske_ua
• https://t.me/noel_reports