Two Su-34s over the Black Sea: how a six-minute Telegram thread reshaped the morning's air-picture

At 13:42 UTC on 11 July 2026, the open-source aviation channel AMK Mapping logged two Su-34 Fullback strike aircraft lifting out of Kerch, on the eastern Crimean peninsula, and tracking west across the Black Sea toward Odesa Oblast. Six minutes later the same channel had changed the story twice: a Su-35 Flanker-E had joined as escort, and the pair had bent their course northwest toward Armyansk in northern Crimea, with the working assessment that they would press on into Russian-occupied Kherson Oblast to drop KAB-series glide bombs on Ukrainian-held positions across the Dnipro.

The thread is small, technical and provisional. It is also the single clearest public read of the day's air-picture over the western Black Sea, and it captures something the war in southern Ukraine has turned into routine: the flight path of a Russian strike package, narrated in near-real-time by observers outside the cockpit, and consumed by a Ukrainian and Western audience that now reads Telegram channels the way earlier wars read radar displays.

What AMK actually saw

The first message, posted at 13:42 UTC, was blunt: "2 Su-34s are flying from Kerch, Crimea, to the western Black Sea. They may launch cruise missiles at Odesa Oblast." A second update at 13:44 UTC added the Su-35 escort, retaining the Odesa framing. The third update, at 13:46 UTC, broke with the cruise-missile hypothesis. The formation had turned, and was now "flying northwest to Armyansk, Crimea," with the channel's revised expectation that the bombers would continue into Russian-controlled Kherson Oblast and release KAB guided glide bombs against Ukrainian-controlled Kherson Oblast.

Each step is a working hypothesis, not a confirmed strike. AMK Mapping is an OSINT outlet reading transponder and commercial-flight data, not an intelligence service with ground confirmation. But the trajectory is consistent with a well-documented Russian pattern: Su-34s based on the Crimean peninsula, staging out of Kerch or nearby airfields, running either sea-launched Kh-35/Kh-31 strikes against Odesa Oblast infrastructure, or inland bombing runs using the KAB family against Ukrainian defensive lines in southern Kherson Oblast. The KAB-tipped sortie is the more dangerous one for ground troops; the cruise-missile variant is the one that hits ports, grain terminals and energy infrastructure further inland.

The state of the evidence at 13:46 UTC was that the aircraft had not yet crossed into Kherson airspace, had not yet released ordnance, and had not been intercepted by Ukrainian air defence in the visible reporting. What the channel had was a flight path, a hypothesis about payload, and a destination.

Why this thread matters more than the flight

The flight itself is not the news. Russia has flown hundreds of similar strike packages since the full-scale invasion began in February 2022, and the Su-34/Su-35 combination is the standard strike-and-escort pairing of the Russian Aerospace Forces' southern axis. The news is that the flight was legible to a public channel before it produced a detonation, splash or plume.

That legibility is the product of three convergent shifts. Commercial ADS-B receivers, military-band listeners and open-source flight-tracking communities have widened the aperture of what civilians can see in contested airspace. Telegram has become the publishing layer of choice for Ukrainian and Russian-adjacent OSINT, with channels like AMK Mapping functioning as low-latency newsrooms. And the war in southern Ukraine has settled into a tempo in which a single formation of two bombers is not a tactical footnote but a meaningful input into Ukrainian air-defence tasking, civilian early-warning apps and shipping decisions in the western Black Sea grain corridor.

The result is a feedback loop the public rarely gets to watch this closely. A reader of the thread at 13:46 UTC could see, in three short paragraphs, an airborne Russian package reinterpreted twice in four minutes as new telemetry arrived: first as a probable cruise-missile sortie, then as a probable KAB glide-bomb run. That is closer to the speed of operational decision-making than any official Ukrainian Air Force briefing is likely to land.

What the Western wire has not yet said

By the time the thread went quiet, no major Western wire had reported the formation. Reuters, the Associated Press, the BBC and Bloomberg have, across the war, generally waited for confirmed impacts, official statements from the Ukrainian General Staff or verified video before publishing on Russian strike packages. That caution is correct for casualty reporting. It also produces a lag in which the public conversation about a given sortie is shaped almost entirely by Telegram OSINT, with all of its sourcing caveats built in.

The counter-read on AMK's thread is the one any careful reader should hold in mind: the channel's hypotheses are extrapolations from a flight track and a known basing pattern, not confirmed strikes. The Odesa reading at 13:42 may yet prove right if the bombers reversed course; the KAB/Kherson reading at 13:46 may yet prove wrong if the package diverted, jettisoned, or was recalled to base. Open-source flight tracking in the Black Sea is also degraded by routine Russian transponder-off operations and by gaps in civilian receiver coverage over the sea surface itself.

What the thread does do, fairly, is constrain the space of plausible outcomes. A reader who has watched the three updates can already weigh where Ukrainian air defence is most likely to be active, where civilians in southern Kherson Oblast should be moving to shelter, and where Russian ground commanders are signalling they intend to apply pressure next. That is information with real value, even before any bomb falls.

What to watch next

The first confirmation will come from the ground. If the bombers were KAB-tipped, reports of guided-bomb impacts in Ukrainian-controlled Kherson Oblast should surface within hours from Ukrainian regional authorities, the Kherson Oblast Military Administration or independent Ukrainian outlets covering the southern front. If the cruise-missile hypothesis was right, expect the first indicators in Odesa: air-raid alerts, port or energy-infrastructure damage reports, and updates from the Ukrainian Air Force's southern command. A third possibility is the absence of any strike at all, which would suggest the formation was a feint, a repositioning flight, or a package recalled mid-mission.

The deeper question, beyond the flight, is structural. Russian strike aviation out of Crimea has now been operating openly enough for an independent OSINT channel to track individual Su-34s in near-real-time for more than a year. That visibility is itself a form of pressure on the Russian Aerospace Forces: every sortie is consumed by an audience that includes the Ukrainian military, foreign partners running fusion cells in Poland, Romania and the Baltic states, and a global public that now reads Telegram channels the way earlier generations read Reuters tickers. The Su-34s over the Black Sea are still flying. The picture of them is no longer Moscow's alone to shape.

Desk note: Monexus leads this piece with the OSINT channel because that is the only source producing real-time reporting on the formation; Western wires had not yet published at the time of writing, and we have flagged that lag rather than pretended it did not exist.

Wire provenance

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

• https://t.me/AMK_Mapping/1
• https://t.me/AMK_Mapping/2
• https://t.me/AMK_Mapping/3
• https://en.wikipedia.org/wiki/Sukhoi_Su-34
• https://en.wikipedia.org/wiki/Sukhoi_Su-35
• https://en.wikipedia.org/wiki/KAB-500
• https://en.wikipedia.org/wiki/Kerch