Russian Su-35 air-to-air duels over Sumy Oblast: what three unconfirmed intercept attempts tell us about the air war's northern edge

At 07:26 UTC on 16 July 2026, the Telegram channel AMK_Mapping posted a short, urgent dispatch: a Russian Sukhoi Su-35 was attempting to shoot down a Ukrainian tactical aircraft near the village of Putvyl in Sumy Oblast, using what the channel identified as an R-37 or R-77 air-to-air missile. Fourteen minutes later, the same channel repeated the report almost verbatim. By 07:52 UTC it had posted a third item, this time describing a second interception attempt near Buryn, also in Sumy Oblast, accompanied by an explosion heard in the nearby city of Bilopillya whose cause the channel itself said it could not confirm.

The two near-identical first posts and the third follow-up amount to the entirety of what is publicly verifiable about the incident at this hour. That thinness is itself the story. Across the northern edge of the Sumy front, where Ukrainian forces have spent months fighting to push Russian troops back from the border, the air war has been conducted largely out of view of independent observers. Most reporting on individual engagements passes through a handful of Russian-aligned mapping channels and the daily summary briefings of the Ukrainian Air Force, neither of which provides a complete picture on its own. Monexus has read three dispatches from AMK_Mapping on 16 July 2026 and can neither confirm nor deny the underlying events from those sources alone.

What the three dispatches actually say

The first two items, posted at 07:26 UTC and 07:40 UTC, are textually almost identical. Each describes a Russian Su-35 attempting to engage a Ukrainian tactical aircraft near Putvyl with an R-37 or R-77 air-to-air missile. The repetition is unusual for a real-time operational channel and suggests either a copy-paste artefact, an evolving situation being updated in place rather than replaced, or a deliberate framing choice by the channel's operator to keep the alert pinned at the top of subscriber feeds. Neither post names the Ukrainian aircraft type, the pilot, the unit, or the outcome of the engagement.

The third item, at 07:52 UTC, shifts the geography. It places a second interception attempt near Buryn, a town roughly 25 kilometres north of Putvyl on the rail line between Sumy and Konotop, and reports an explosion heard in Bilopillya, a border town about 40 kilometres northwest of Buryn. The channel explicitly states that it is unclear whether the sound was caused by an air-to-air engagement, by air-defence activity, or by something else entirely.

In aggregate, the three posts describe a thirty-minute window in which Russian fighters operating from bases inside Russian airspace or from forward strips near the border allegedly launched long-range missile shots at Ukrainian tactical aircraft over the northern Sumy sector. They do not confirm a kill, do not identify the targets, and do not address the explosion in Bilopillya.

Why the weapon pairing matters, and what we do not know

The R-37, designated RVV-BD by its manufacturer, is a heavyweight long-range air-to-air missile developed by Vympel and carried principally by the Su-35S and MiG-31. Public specification sheets, drawn from Russian marketing materials and from prior reporting by open-source intelligence analysts on the Oryx blog and at the International Institute for Strategic Studies, put its maximum engagement range in the high hundreds of kilometres against bomber-sized targets and in the order of 200 kilometres against manoeuvring fighters at high altitude. The R-77, marketed as RVV-AE, is a medium-range active-radar missile in the same general class as the American AIM-120 AMRAAM, with a published range of roughly 40 to 100 kilometres depending on the variant.

The pairing matters because the R-37 in particular is the weapon that has, in prior reporting by outlets including Reuters and the Kyiv Independent, been credibly associated with at least two confirmed long-range kills of Ukrainian aircraft since 2024, including the downing of Ukrainian MiG-29s and Su-25s flying low over the eastern front. Russian pilots have used Su-35s and MiG-31s as launch platforms for the missile in part because its size limits carriage to those larger types. AMK_Mapping's claim that an Su-35 is the launch aircraft is therefore consistent with the known employment pattern of the weapon.

What the three dispatches do not tell us is any of the things that would convert them from an unverified alert into a corroborated engagement report: no wreckage coordinates, no Ukrainian acknowledgement, no Russian Ministry of Defence confirmation, no flight-tracking data from open networks such as ADS-B Exchange, and no imagery from the ground in Putvyl, Buryn or Bilopillya. The explosion in Bilopillya in particular is an open question. The town sits within range of Ukrainian and Russian tube and rocket artillery, and within the operating radius of Iranian-designed Shahed-series one-way attack drones that have been used extensively on both sides of the border throughout 2025 and 2026. The sound could equally have been caused by an air-defence intercept, a glide-bomb strike, or a drone impact.

What we verified and what we could not

Monexus verified the following. Three items were posted to the AMK_Mapping Telegram channel on 16 July 2026, at 07:26 UTC, 07:40 UTC and 07:52 UTC respectively. The first two are textually near-identical and concern a Russian Su-35 allegedly attempting to engage a Ukrainian tactical aircraft near Putvyl in Sumy Oblast with an R-37 or R-77 air-to-air missile. The third concerns a separate alleged interception attempt near Buryn in the same oblast, accompanied by an explosion in Bilopillya whose cause the channel itself does not confirm.

Monexus could not verify, from the sources available, the following: that a Russian Su-35 was in fact airborne over Putvyl at the times stated; that any Ukrainian tactical aircraft was operating in the area; that an R-37 or R-77 missile was launched; that an interception attempt took place; that any engagement occurred near Buryn; that the explosion in Bilopillya was caused by an air-to-air engagement or by air-defence activity; that any aircraft was shot down; and that either side sustained loss. None of these propositions is supported or refuted by the three Telegram items alone.

The sources also do not specify the type of the Ukrainian aircraft involved, the unit to which it belonged, the identity of the Su-35 pilot or unit, the launch point of the missile, the direction of the engagement, or the outcome. There is no independent reporting in the source set from the Ukrainian Air Force, the Ukrainian General Staff, the Russian Ministry of Defence, or any Western wire service covering the alleged events within the relevant time window.

Why the air war over Sumy has stayed out of view

The structural reason such incidents are hard to verify is the geography and the platform mix. Sumy Oblast borders Russia directly across a long, lightly populated frontier. Most Russian combat-air sorties over the northern Sumy sector are launched from bases well inside Russian airspace, often beyond the reach of Ukrainian surface-to-air missile systems, which has historically allowed Su-35s and MiG-31s to position themselves for long-range shots with minimal exposure. Ukrainian tactical aviation, much of it Soviet-era MiG-29s and Su-25s, operates from a small number of forward airfields in the oblast and further west, and has been increasingly required to fly low and fast to avoid Russian surface-to-air missile engagement zones.

Reporting on individual air-to-air engagements has therefore passed through a small number of channels, of which AMK_Mapping is one of the most prolific but also one of the most openly partisan. The channel is widely cited by both Ukrainian and Western analysts as a useful but partial source: useful for near-real-time situational awareness, partial because its operators are sympathetic to Russian framing and have at times overstated Russian successes and understated Russian losses. The near-duplicate posts on 16 July are consistent with that pattern: an alert designed to travel quickly through subscriber networks, repeated to keep it visible, and not accompanied by the kind of corroborating evidence that would convert it from a claim into a finding.

What it would take to confirm

A confirmed engagement report would require, at minimum, one of the following: a statement from the Ukrainian Air Force or the General Staff of the Armed Forces of Ukraine acknowledging a loss or an engagement; a statement from the Russian Ministry of Defence claiming a kill; radar-track reconstruction from open networks such as ADS-B Exchange or from commercial satellite imagery providers; imagery of wreckage or impact craters with geolocation; or independent reporting from wire services or from Western defence outlets with on-the-ground correspondents in the relevant towns. None of these is present in the sources Monexus has reviewed for this article.

The Bilopillya explosion in particular is the kind of event that may be clarified within hours, as local Ukrainian authorities typically post on the incident within the day and regional military administrations publish morning summaries. If those sources confirm an air-defence intercept or a drone strike, the framing changes; if they remain silent, the silence itself is a partial but not conclusive data point.

The larger pattern this episode sits inside is not in doubt. Russian combat aviation has, over the past two years, increasingly used long-range air-to-air missiles to contest Ukrainian airspace over the eastern and northern fronts, and has achieved at least a small number of confirmed kills of Ukrainian fixed-wing aircraft at distances and altitudes that would have been implausible in earlier phases of the war. Whether the events of 07:26 to 07:52 UTC on 16 July 2026 belong to that pattern, or are something else entirely, the public record cannot yet say.

Stakes if the pattern holds

If the claims in the three dispatches are accurate, the operational stakes for Ukraine are real. Loss of even one tactical aircraft to a long-range air-to-air engagement over Sumy Oblast would compound an existing pressure on a fleet that has been progressively thinned since 2022, and would push Ukrainian pilots further towards low-altitude, short-duration sortie profiles that limit their effectiveness against Russian ground forces. If the claims are inaccurate, the incident is still a useful illustration of how the air war over the northern border is reported, contested and remembered: through a small number of partisan channels whose near-real-time alerts travel faster than the verification apparatus that would convert them into facts.

The honest answer, for now, is that the public evidence base consists of three Telegram items from a single Russian-aligned channel, posted within half an hour of one another, with no independent corroboration. The episode may yet resolve into a confirmed engagement with a confirmed outcome. It may resolve into a drone strike on Bilopillya, or an air-defence intercept of a Russian missile, or nothing at all. Until one of those resolutions lands, the lede is the verification problem itself.

Desk note: Monexus is publishing this as an investigation rather than a news piece because the source set is a single partisan channel and the underlying events are unverified. We have led with the dispatch itself rather than the alleged events inside it, and have separated the ledger of what we could verify from what we could not. If and when the Ukrainian Air Force, the General Staff, or a Western wire service confirms or denies the engagements, we will update this piece accordingly.

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
• https://t.me/s/AMK_Mapping
• https://en.wikipedia.org/wiki/R-37_(missile)
• https://en.wikipedia.org/wiki/Sukhoi_Su-35
• https://en.wikipedia.org/wiki/Sumy_Oblast