Russian Su-35s stalk Ukrainian jets over Sumy in a sequence Telegram channels are tracking minute by minute

At 07:08 UTC on 16 July 2026, the Telegram channel AMK_Mapping posted that a Russian Sukhoi Su-35 was attempting to shoot down a Ukrainian tactical aircraft near the village of Putvyl in Sumy Oblast with an R-37 or R-77 long-range air-to-air missile. Eighteen minutes later the same channel posted again, repeating the initial alert and adding that "another interception attempt is being made now." A third update at 07:40 UTC carried the same wording. Across thirty-two minutes, three near-identical posts described a sustained sequence of air-to-air engagements along a single stretch of the northeastern Ukrainian front.

What is being claimed is narrow but consequential: that Russian Flanker-family fighters, operating from inside Russian or occupied airspace, are launching heavy air-to-air missiles at Ukrainian tactical jets in the Sumy sector, and that more than one launch is being attempted within the same hour. The weapon nomenclature is specific enough to anchor the claim in a real inventory, but the bulletin rests on a single open-source channel whose visibility model is exactly that of a frontline tip line, with no independent radar, ELINT, or imagery corroboration attached.

What AMK_Mapping actually said

The three posts collected in the wire thread are textually identical on the core claim: a Russian Su-35 is trying to shoot down a Ukrainian tactical aircraft near Putvyl, Sumy Oblast, with an R-37 or R-77 air-to-air missile "right now." The second and third posts add a follow-on sentence, again verbatim, stating that "another interception attempt is being made now." Nothing in the thread identifies the Ukrainian aircraft type, the launch outcome, whether the missile reached terminal phase, or whether the engagement was recorded on any sensor other than the channel's own sources.

The R-37 is a Russian long-range, ramjet-augmented air-to-air missile carried primarily by Su-35S and MiG-31 interceptors, designed to engage manoeuvring targets at distances the platform's radar can designate. The R-77 is the Russian medium-range counterpart to the US AIM-120 AMRAAM, fielded across the Flanker family. Naming either weapon is consistent with what a Su-35 would realistically carry into a border-sector sweep, and consistent with Russian air-to-air doctrine that has, since 2022, increasingly pushed Flanker sorties into beyond-visual-range launch envelopes.

The village of Putvyl sits in the northern reaches of Sumy Oblast, close to the border with Russia's Kursk and Bryansk regions. Russian air operations in this corridor have intensified at points during the war as Moscow has sought to interdict Ukrainian cross-border action and to extend the air defence envelope over its own Belgorod-Kursk salient. That a Ukrainian tactical aircraft would be working this sector is itself an indicator of routine Ukrainian air activity over the oblast, which has been a consistent feature of frontline reporting from both sides.

The single-source problem

The episode is also a small case study in how frontline aviation reporting now travels. AMK_Mapping is one of several Telegram channels that aggregate geolocated combat footage, intercept transcripts, and pilot communications. The channel's business is speed: get a claim out before verification cycles close, flag it as live, and update if more arrives. The trade-off is that a bulletin consisting of three near-identical posts over thirty-two minutes is, in formal sourcing terms, one claim made three times by one source.

This publication did not locate an independent confirmation of the launches in the wire thread. There is no reference to the episode in the Ukrainian Air Force's daily Telegram or Facebook communications inside the materials available, no acknowledgement from the Russian Ministry of Defence, and no second open-source channel reporting the same R-37 or R-77 launch at Putvyl within the relevant window. That absence is not, on its own, disconfirming, frontline air-to-air events routinely outpace public reporting, and the Ukrainian general staff often delays confirming combat-aviation losses, but it is the difference between an event that has been reported and an event that has been corroborated.

A reasonable read of the sequence is that AMK_Mapping had at least one first-hand source inside or near the affected sector, a Ukrainian pilot on an emergency frequency, a ground observer with a radio, an intercept operator, and that source reported an attempted engagement more than once within the same hour. That is plausible but it is not the same as the engagement being independently established.

What we verified / what we could not

Verified. That AMK_Mapping posted, three times between 07:08 and 07:40 UTC on 16 July 2026, that a Russian Su-35 had attempted to shoot down a Ukrainian tactical aircraft near Putvyl, Sumy Oblast, with an R-37 or R-77 air-to-air missile, and that a further interception attempt was reported inside the same window. The textual content of the three posts is as quoted above. The R-37 and R-77 are real Russian air-to-air weapons in operational service, and the Su-35S is a real platform certified to carry both.

Verified. That Putvyl is located in Sumy Oblast, in the immediate border zone with Russia, in an area where Russian air activity has been a documented feature of the war.

Not verified within this thread. That any R-37 or R-77 missile was actually launched in the timeframe claimed. That the Ukrainian aircraft named (or implied) was a specific platform, was hit, was damaged, or survived. That more than one launch was attempted. That the engagement took place in the precise grid reference a reader might infer from "near Putvyl." That the Su-35 in question was airborne from a Russian or occupied airbase rather than repositioned from elsewhere. That any radar, electro-optical, or signals-intelligence recording of the engagement exists.

Not independently corroborated. No second open-source channel in the available wire carried the same claim within the reporting window. No official Ukrainian or Russian statement references the episode in the materials accessible to this publication.

The honest framing is that a single frontline Telegram channel has reported, with high specificity but no public corroboration, an in-progress Russian air-to-air engagement against a Ukrainian aircraft in Sumy Oblast. The reporting is credible in form and consistent with the weapons and the geography. It is not yet a fact in the evidentiary sense.

Why the bulletin still matters

Even where independent confirmation is missing, the shape of what AMK_Mapping describes is structurally important. The Su-35 paired with the R-37 is the Russian air force's preferred architecture for long-range air superiority work; pushing that pairing into the Sumy corridor reflects an attempt to contest Ukrainian tactical aviation on its own side of the border, not merely over Russian-held territory. The implication for Ukrainian air operations in the sector is that the threat envelope has shifted from short-range infrared and gun engagements to beyond-visual-range missile shots, which compresses Ukrainian sortie timelines and forces earlier defensive manoeuvring.

There is also a signal in the cadence itself. Three posts inside thirty-two minutes from a single channel indicates sustained contact, not a single momentary flash. Whether that sustained contact reflects multiple launches, one launch with extended commentary, or several reports being folded into one bulletin, the channel's reading is that the tactical picture in the Putvyl area did not stabilise inside the half-hour. For an air operations centre on either side, that is the kind of rhythm that triggers re-tasking of combat air patrols and re-routing of unmanned systems.

What to watch next

The reasonable next test is whether the Ukrainian Air Force acknowledges any combat loss, damage, or near-miss in the Putvyl sector within the standard 24-to-72 hour reporting window. A confirmation, or a denial, with reason, would convert the Telegram bulletin into a corroborated event. In its absence, the episode remains an unusually specific but uncorroborated claim from a single channel that has, across the war, often been early and occasionally wrong.

For now the cleanest statement is the cautious one: on the morning of 16 July 2026, according to a single Telegram channel whose three posts spanned thirty-two minutes, a Russian Su-35 attempted at least once, and possibly more than once, to shoot down a Ukrainian tactical aircraft near Putvyl using an R-37 or R-77 air-to-air missile. The weapon, the platform, the geography, and the channel's reporting style are all consistent. Whether the engagement happened as described is, on the public record available here, an open question.

This article leans on a single open-source channel whose reporting style privileges speed over corroboration. Monexus is publishing the claim because the channel is named, the timestamps are absolute, and the textual content is on the record; the publication is publishing it with explicit verification limits rather than as an established event. Where independent confirmation arrives, this article will be updated.

Wire provenance

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

• https://t.me/s/AMK_Mapping
• https://t.me/s/AMK_Mapping/1
• https://t.me/s/AMK_Mapping/2
• https://t.me/s/AMK_Mapping/3
• https://en.wikipedia.org/wiki/Sukhoi_Su-35
• https://en.wikipedia.org/wiki/R-37_(missile)
• https://en.wikipedia.org/wiki/R-77