# REPORT: Donetsk video shows an FPV striking a Shahed before launch - Author: Maxime Marquette - Publisher: MadMax (https://mad-max.co) - Section: Reportage - Published: 2026-08-10 - Canonical URL: https://mad-max.co/en/article/report-donetsk-video-shows-an-fpv-striking-a-shahed-before-launch ## Introduction ### A published video, not independent certification At the centre of the record, **8 August 2026** **FPV drones** **jet-powered Shahed** define the point at issue. The Institute for the Study of War reported footage showing Ukrainian FPV drones striking and destroying a Russian jet-powered Shahed while it was on a launcher at Donetsk City airport, an area occupied by Russia. That is a boundary, not an excuse: the available material supports a reported battlefield event whose exact date and location have not been independently authenticated in the available sources, but it does not establish a broader conclusion that the material never makes. The record stops there. *A video can document an impact without certifying its map.* The distinction carries weight, **Serhii Sternenko** **Donetsk City airport** **Russia-occupied territory** place the claim in a specific chain of decisions. The images were published by Sternenko, described as a former adviser to former Ukrainian Defence Minister Mykhailo Fedorov. The source permits a report about what the video appears to show; it does not turn the post into a standalone official confirmation. The practical consequence is that the strongest formulation is attributed and limited; that is a consequence of the reported record, not a substitute for missing evidence. That is not a conviction. ## Serhii Sternenko is the video’s named publisher ### The publication chain The documented starting point, **Serhii Sternenko** **8 August 2026** **published footage** define the point at issue. ISW’s account cites Sternenko as the source of the images. Naming the publication chain matters because it tells readers where the claim begins and why the video’s evidentiary status differs from an official military communiqué. The wording matters here: the available material supports the report can describe the post without pretending the post is an independent inquiry, but it does not establish a broader conclusion that the material never makes. The figure needs its source. The date changes the reading, **Serhii Sternenko** **8 August 2026** **published footage** place the claim in a specific chain of decisions. ISW’s account cites Sternenko as the source of the images. Naming the publication chain matters because it tells readers where the claim begins and why the video’s evidentiary status differs from an official military communiqué. The practical consequence is that the report can describe the post without pretending the post is an independent inquiry; that is a consequence of the reported record, not a substitute for missing evidence. The video is not a verdict. ### The publisher is not the General Staff Inside the stated case, **former adviser** **Ukrainian Defence Ministry** **video claim** define the point at issue. The available material identifies Sternenko through a former advisory role, not as the issuing authority for this strike. That distinction keeps the event separate from the 6–7 August actions later described in an official Ukrainian statement. That restraint belongs in the conclusion: the available material supports one source can be important without becoming every source, but it does not establish a broader conclusion that the material never makes. The claim remains attributed. A number alone cannot settle it, **former adviser** **Ukrainian Defence Ministry** **video claim** place the claim in a specific chain of decisions. The available material identifies Sternenko through a former advisory role, not as the issuing authority for this strike. That distinction keeps the event separate from the 6–7 August actions later described in an official Ukrainian statement. The practical consequence is that one source can be important without becoming every source; that is a consequence of the reported record, not a substitute for missing evidence. A court has not ended the case. *The publisher is named. The verification gap is named too.* ## The footage has not been independently authenticated ### What remains unverified On the investigators' account, **exact date** **exact location** **independent authentication** define the point at issue. The assigned record says the video has not been independently authenticated as to its precise date and location. That limitation does not prove the footage false; it defines what the reporting cannot certify from the available material. The record separates allegation from outcome: the available material supports the visual claim has a documented ceiling, but it does not establish a broader conclusion that the material never makes. The caveat changes the headline. That is a boundary, not an excuse, **exact date** **exact location** **independent authentication** place the claim in a specific chain of decisions. The assigned record says the video has not been independently authenticated as to its precise date and location. That limitation does not prove the footage false; it defines what the reporting cannot certify from the available material. The practical consequence is that the visual claim has a documented ceiling; that is a consequence of the reported record, not a substitute for missing evidence. The number carries a limit. ### Why the wording must stay careful In the operational tally, **video evidence** **unconfirmed location** **unconfirmed date** define the point at issue. A clip can show an object and an impact while still leaving its setting and timing unresolved. The proper verb is reported or appears to show, because the material does not supply a separate geolocation or timestamp verification. This is a fact with a ceiling: the available material supports the image should not be asked to prove more than it can, but it does not establish a broader conclusion that the material never makes. The law has its own timetable. The wording matters here, **video evidence** **unconfirmed location** **unconfirmed date** place the claim in a specific chain of decisions. A clip can show an object and an impact while still leaving its setting and timing unresolved. The proper verb is reported or appears to show, because the material does not supply a separate geolocation or timestamp verification. The practical consequence is that the image should not be asked to prove more than it can; that is a consequence of the reported record, not a substitute for missing evidence. The evidence is narrower. *A launcher is a target before it is a launch.* ## The reported target was still on its launcher ### Before takeoff In the financial trail described, **jet-powered Shahed** **launcher** **Donetsk airport** define the point at issue. ISW describes a jet-powered Shahed on its launcher when the FPV drones struck. If accurately located, that detail is operationally significant because it places the target before launch rather than in flight. The public can see the action; it cannot yet see every consequence: the available material supports the reported tactic starts before the drone leaves the ground, but it does not establish a broader conclusion that the material never makes. The agreement still needs action. That restraint belongs in the conclusion, **jet-powered Shahed** **launcher** **Donetsk airport** place the claim in a specific chain of decisions. ISW describes a jet-powered Shahed on its launcher when the FPV drones struck. If accurately located, that detail is operationally significant because it places the target before launch rather than in flight. The practical consequence is that the reported tactic starts before the drone leaves the ground; that is a consequence of the reported record, not a substitute for missing evidence. The source does not settle blame. ### The tactical implication is limited For any legal reading, **FPV drone** **launcher** **pre-launch strike** define the point at issue. A strike at a launcher may seek to reduce the number of drones available for a later attack. The record does not quantify how many launches were prevented, what damage remained, or whether the reported target was the only aircraft at the site. The file names a condition rather than a guarantee: the available material supports a tactical logic is not a measured result, but it does not establish a broader conclusion that the material never makes. The next step decides more. The record separates allegation from outcome, **FPV drone** **launcher** **pre-launch strike** place the claim in a specific chain of decisions. A strike at a launcher may seek to reduce the number of drones available for a later attack. The record does not quantify how many launches were prevented, what damage remained, or whether the reported target was the only aircraft at the site. The practical consequence is that a tactical logic is not a measured result; that is a consequence of the reported record, not a substitute for missing evidence. The finding is procedural. *Occupation gives a place meaning, not automatic proof.* ## Donetsk City airport remains a claimed location ### The place named In the reporting available, **Donetsk City airport** **Russia-occupied** **ISW report** define the point at issue. The airport is described in the source as being in Russian-occupied territory. That context explains why a pre-launch strike would matter in Ukraine’s campaign against launch infrastructure, while the video's location itself remains unverified by an independent source. The institutional choice is now visible: the available material supports occupation explains the relevance; it does not authenticate the clip, but it does not establish a broader conclusion that the material never makes. The line between fact and inference holds. This is a fact with a ceiling, **Donetsk City airport** **Russia-occupied** **ISW report** place the claim in a specific chain of decisions. The airport is described in the source as being in Russian-occupied territory. That context explains why a pre-launch strike would matter in Ukraine’s campaign against launch infrastructure, while the video's location itself remains unverified by an independent source. The practical consequence is that occupation explains the relevance; it does not authenticate the clip; that is a consequence of the reported record, not a substitute for missing evidence. The poll does not negotiate. ### The geography is part of the claim Within the stated timeline, **Donetsk City** **Russian forces** **Ukrainian FPVs** define the point at issue. The report connects Ukrainian FPV drones to a Russian Shahed at the airport. It does not provide a Russian confirmation, an on-site inspection, or a damage assessment, so the geographic claim remains tied to the published video and ISW’s description. No larger conclusion follows automatically: the available material supports the location must remain attributed, but it does not establish a broader conclusion that the material never makes. The damage remains unmeasured. The public can see the action; it cannot yet see every consequence, **Donetsk City** **Russian forces** **Ukrainian FPVs** place the claim in a specific chain of decisions. The report connects Ukrainian FPV drones to a Russian Shahed at the airport. It does not provide a Russian confirmation, an on-site inspection, or a damage assessment, so the geographic claim remains tied to the published video and ISW’s description. The practical consequence is that the location must remain attributed; that is a consequence of the reported record, not a substitute for missing evidence. The deployment is not peace. *Publication time is not event time.* ## 8 August is the publication date, not necessarily the strike date ### The date in the report On the narrow question, **8 August 2026** **published images** **ISW** define the point at issue. The available date is when the images were reported and discussed. Nothing in the fact block independently establishes that the impact itself happened on that same calendar day, a difference that matters in fast-moving conflict reporting. The next test lies outside the announcement: the available material supports publication time and event time are not interchangeable, but it does not establish a broader conclusion that the material never makes. The source calls for restraint. The file names a condition rather than a guarantee, **8 August 2026** **published images** **ISW** place the claim in a specific chain of decisions. The available date is when the images were reported and discussed. Nothing in the fact block independently establishes that the impact itself happened on that same calendar day, a difference that matters in fast-moving conflict reporting. The practical consequence is that publication time and event time are not interchangeable; that is a consequence of the reported record, not a substitute for missing evidence. The claim has not been independently confirmed. ### A missing timestamp has consequences For the institutions named, **date of publication** **date of event** **verification** define the point at issue. Without an independently verified timestamp, reporting cannot reliably place the strike within a particular operational sequence. The event may fit the broader pattern described by Ukraine, but the material does not establish its precise temporal relationship to that pattern. The distinction carries weight: the available material supports chronology needs evidence, not convenience, but it does not establish a broader conclusion that the material never makes. The litigation remains alive. The institutional choice is now visible, **date of publication** **date of event** **verification** place the claim in a specific chain of decisions. Without an independently verified timestamp, reporting cannot reliably place the strike within a particular operational sequence. The event may fit the broader pattern described by Ukraine, but the material does not establish its precise temporal relationship to that pattern. The practical consequence is that chronology needs evidence, not convenience; that is a consequence of the reported record, not a substitute for missing evidence. The public record is incomplete. *A tactic is not a tally.* ## The tactic aims at drones before they are used ### The stated logic Beyond the headline number, **pre-launch sites** **Shahed drones** **Ukrainian tactic** define the point at issue. The reported tactic targets Shaheds directly at launch sites, before they can be used. It is a practical attempt to reduce an opponent’s offensive potential, but the available sources do not provide a numerical assessment of its effectiveness. The date changes the reading: the available material supports the mechanism is visible; the total effect is not, but it does not establish a broader conclusion that the material never makes. No authority has closed the issue. No larger conclusion follows automatically, **pre-launch sites** **Shahed drones** **Ukrainian tactic** place the claim in a specific chain of decisions. The reported tactic targets Shaheds directly at launch sites, before they can be used. It is a practical attempt to reduce an opponent’s offensive potential, but the available sources do not provide a numerical assessment of its effectiveness. The practical consequence is that the mechanism is visible; the total effect is not; that is a consequence of the reported record, not a substitute for missing evidence. The timeline is not proof of cause. ### The measure is not a complete campaign balance For the next decision, **offensive potential** **launch infrastructure** **unquantified damage** define the point at issue. Disabling a launcher or a drone may matter locally, yet it does not by itself establish the broader condition of Russia’s strike capacity. The record offers no comparative inventory, sortie count, or independently confirmed damage figure. A number alone cannot settle it: the available material supports one impact cannot carry the whole war, but it does not establish a broader conclusion that the material never makes. The event demands a careful verb. The next test lies outside the announcement, **offensive potential** **launch infrastructure** **unquantified damage** place the claim in a specific chain of decisions. Disabling a launcher or a drone may matter locally, yet it does not by itself establish the broader condition of Russia’s strike capacity. The record offers no comparative inventory, sortie count, or independently confirmed damage figure. The practical consequence is that one impact cannot carry the whole war; that is a consequence of the reported record, not a substitute for missing evidence. The evidence must carry the weight. *Official claims still require independent checks.* ## 6–7 August brought a separate official Ukrainian claim ### Two relay stations named At the centre of the record, **Olenivka** **Zaliznyi Port** **6–7 August** define the point at issue. Ukraine’s General Staff said Defence Forces struck two ground relay stations used to control Shahed drones, near Olenivka in Crimea and Zaliznyi Port in occupied Kherson oblast, during the night of 6–7 August. That is a boundary, not an excuse: the available material supports this is an official Ukrainian claim, not a Russian-confirmed damage assessment, but it does not establish a broader conclusion that the material never makes. The record stops there. The distinction carries weight, **Olenivka** **Zaliznyi Port** **6–7 August** place the claim in a specific chain of decisions. Ukraine’s General Staff said Defence Forces struck two ground relay stations used to control Shahed drones, near Olenivka in Crimea and Zaliznyi Port in occupied Kherson oblast, during the night of 6–7 August. The practical consequence is that this is an official Ukrainian claim, not a Russian-confirmed damage assessment; that is a consequence of the reported record, not a substitute for missing evidence. That is not a conviction. ### The stations had a specific function The documented starting point, **ground relay stations** **Shahed control** **Ukrainian General Staff** define the point at issue. The General Staff’s account identifies relay stations as part of drone control. The statement explains the claimed target category, but it does not quantify the damage or state that Russian authorities confirmed the strikes. The wording matters here: the available material supports the function is reported; the result is not fully measured, but it does not establish a broader conclusion that the material never makes. The figure needs its source. The date changes the reading, **ground relay stations** **Shahed control** **Ukrainian General Staff** place the claim in a specific chain of decisions. The General Staff’s account identifies relay stations as part of drone control. The statement explains the claimed target category, but it does not quantify the damage or state that Russian authorities confirmed the strikes. The practical consequence is that the function is reported; the result is not fully measured; that is a consequence of the reported record, not a substitute for missing evidence. The video is not a verdict. *A launch site is a chain, not a single object.* ## Hvardiiiske was described as a storage and launch site ### The site in Crimea Inside the stated case, **Hvardiiiske** **storage** **preparation and launch** define the point at issue. The same Ukrainian statement said forces struck a site for storage, preparation, and launch of attack drones near Hvardiiiske in Crimea. It identifies a logistical chain beyond a single launcher, with no detailed public damage inventory. That restraint belongs in the conclusion: the available material supports the target description is broader than a single frame, but it does not establish a broader conclusion that the material never makes. The claim remains attributed. A number alone cannot settle it, **Hvardiiiske** **storage** **preparation and launch** place the claim in a specific chain of decisions. The same Ukrainian statement said forces struck a site for storage, preparation, and launch of attack drones near Hvardiiiske in Crimea. It identifies a logistical chain beyond a single launcher, with no detailed public damage inventory. The practical consequence is that the target description is broader than a single frame; that is a consequence of the reported record, not a substitute for missing evidence. A court has not ended the case. ### The official wording matters On the investigators' account, **Hvardiiiske** **attack UAVs** **Ukrainian statement** define the point at issue. The communiqué places Hvardiiiske within efforts to reduce Russia’s offensive potential. That is the stated Ukrainian objective and should be read as such; the source does not supply an independent post-strike inspection. The record separates allegation from outcome: the available material supports an announced objective is not a confirmed outcome, but it does not establish a broader conclusion that the material never makes. The caveat changes the headline. That is a boundary, not an excuse, **Hvardiiiske** **attack UAVs** **Ukrainian statement** place the claim in a specific chain of decisions. The communiqué places Hvardiiiske within efforts to reduce Russia’s offensive potential. That is the stated Ukrainian objective and should be read as such; the source does not supply an independent post-strike inspection. The practical consequence is that an announced objective is not a confirmed outcome; that is a consequence of the reported record, not a substitute for missing evidence. The number carries a limit. *Reports of fire do not settle damage.* ## Local Telegram reports add a second, weaker layer ### Reported explosions and fire In the operational tally, **local Telegram channels** **Hvardiiiske airfield** **7 August** define the point at issue. Local Telegram channels reported explosions followed by a large fire at Hvardiiiske military airfield on the night of 7 August. These reports add context, but they are not presented as independent technical verification of the claimed targets or damage. This is a fact with a ceiling: the available material supports a local report is still a report, but it does not establish a broader conclusion that the material never makes. The law has its own timetable. The wording matters here, **local Telegram channels** **Hvardiiiske airfield** **7 August** place the claim in a specific chain of decisions. Local Telegram channels reported explosions followed by a large fire at Hvardiiiske military airfield on the night of 7 August. These reports add context, but they are not presented as independent technical verification of the claimed targets or damage. The practical consequence is that a local report is still a report; that is a consequence of the reported record, not a substitute for missing evidence. The evidence is narrower. ### What those posts cannot settle In the financial trail described, **explosions** **large fire** **damage assessment** define the point at issue. A report of an explosion or fire does not establish what was hit, whether a stated target was destroyed, or how long any disruption lasted. The material offers no verified loss count, satellite assessment, or Russian acknowledgement. The public can see the action; it cannot yet see every consequence: the available material supports the visible event does not answer every question, but it does not establish a broader conclusion that the material never makes. The agreement still needs action. That restraint belongs in the conclusion, **explosions** **large fire** **damage assessment** place the claim in a specific chain of decisions. A report of an explosion or fire does not establish what was hit, whether a stated target was destroyed, or how long any disruption lasted. The material offers no verified loss count, satellite assessment, or Russian acknowledgement. The practical consequence is that the visible event does not answer every question; that is a consequence of the reported record, not a substitute for missing evidence. The source does not settle blame. *Two sources can describe different events honestly.* ## ISW and the Ukrainian General Staff speak in different registers ### The analytic account For any legal reading, **Institute for the Study of War** **video** **reported destruction** define the point at issue. ISW reports the video’s apparent destruction of a Shahed on a launcher. Its role is different from the Ukrainian General Staff’s official account of strikes on identified infrastructure during the earlier night. The file names a condition rather than a guarantee: the available material supports sources can align in theme without becoming the same evidence, but it does not establish a broader conclusion that the material never makes. The next step decides more. The record separates allegation from outcome, **Institute for the Study of War** **video** **reported destruction** place the claim in a specific chain of decisions. ISW reports the video’s apparent destruction of a Shahed on a launcher. Its role is different from the Ukrainian General Staff’s official account of strikes on identified infrastructure during the earlier night. The practical consequence is that sources can align in theme without becoming the same evidence; that is a consequence of the reported record, not a substitute for missing evidence. The finding is procedural. ### The official account In the reporting available, **Ukrainian General Staff** **6–7 August** **relay stations** define the point at issue. The General Staff statement covers Olenivka, Zaliznyi Port, and Hvardiiiske. It does not serve as confirmation of Sternenko’s Donetsk video, so the two accounts should be placed beside each other rather than merged into one proven event. The institutional choice is now visible: the available material supports similar tactics do not erase separate proof burdens, but it does not establish a broader conclusion that the material never makes. The line between fact and inference holds. This is a fact with a ceiling, **Ukrainian General Staff** **6–7 August** **relay stations** place the claim in a specific chain of decisions. The General Staff statement covers Olenivka, Zaliznyi Port, and Hvardiiiske. It does not serve as confirmation of Sternenko’s Donetsk video, so the two accounts should be placed beside each other rather than merged into one proven event. The practical consequence is that similar tactics do not erase separate proof burdens; that is a consequence of the reported record, not a substitute for missing evidence. The poll does not negotiate. *The word destroyed needs a source beside it.* ## “Destroyed” remains a source-bound word ### The verb in the report Within the stated timeline, **destroyed** **Shahed drone** **ISW** define the point at issue. The report uses the word destroyed for the Shahed shown in the footage. Because the underlying visual claim has not been independently authenticated for time and place, the word should remain attached to ISW’s account rather than stated as an unqualified fact. No larger conclusion follows automatically: the available material supports the verb must keep its attribution, but it does not establish a broader conclusion that the material never makes. The damage remains unmeasured. The public can see the action; it cannot yet see every consequence, **destroyed** **Shahed drone** **ISW** place the claim in a specific chain of decisions. The report uses the word destroyed for the Shahed shown in the footage. Because the underlying visual claim has not been independently authenticated for time and place, the word should remain attached to ISW’s account rather than stated as an unqualified fact. The practical consequence is that the verb must keep its attribution; that is a consequence of the reported record, not a substitute for missing evidence. The deployment is not peace. ### No Russian confirmation is provided On the narrow question, **Russian confirmation** **damage claim** **available sources** define the point at issue. The assigned sources provide no Russian confirmation of this reported strike. Absence of confirmation does not disprove the event; it means a responsible report cannot claim bilateral verification or a fully settled battle-damage record. The next test lies outside the announcement: the available material supports silence is not confirmation, but it does not establish a broader conclusion that the material never makes. The source calls for restraint. The file names a condition rather than a guarantee, **Russian confirmation** **damage claim** **available sources** place the claim in a specific chain of decisions. The assigned sources provide no Russian confirmation of this reported strike. Absence of confirmation does not disprove the event; it means a responsible report cannot claim bilateral verification or a fully settled battle-damage record. The practical consequence is that silence is not confirmation; that is a consequence of the reported record, not a substitute for missing evidence. The claim has not been independently confirmed. *No damage figure means no damage figure.* ## The sources do not quantify damage or casualties ### What is missing For the institutions named, **damage total** **casualty count** **launcher assessment** define the point at issue. No quantified damage assessment or casualty figure is supplied for Donetsk, the relay stations, or Hvardiiiske. The absence is important because it prevents the report from converting a tactical claim into a measurable operational result. The distinction carries weight: the available material supports unmeasured damage stays unmeasured, but it does not establish a broader conclusion that the material never makes. The litigation remains alive. The institutional choice is now visible, **damage total** **casualty count** **launcher assessment** place the claim in a specific chain of decisions. No quantified damage assessment or casualty figure is supplied for Donetsk, the relay stations, or Hvardiiiske. The absence is important because it prevents the report from converting a tactical claim into a measurable operational result. The practical consequence is that unmeasured damage stays unmeasured; that is a consequence of the reported record, not a substitute for missing evidence. The public record is incomplete. ### The missing information matters Beyond the headline number, **independent inspection** **Russian response** **post-strike imagery** define the point at issue. The material also lacks an independent site inspection, a Russian response confirming impacts, and verified post-strike imagery. Those gaps leave the report focused on the stated action and its tactical rationale rather than on an asserted final balance. The date changes the reading: the available material supports the unanswered questions are part of the story, but it does not establish a broader conclusion that the material never makes. No authority has closed the issue. No larger conclusion follows automatically, **independent inspection** **Russian response** **post-strike imagery** place the claim in a specific chain of decisions. The material also lacks an independent site inspection, a Russian response confirming impacts, and verified post-strike imagery. Those gaps leave the report focused on the stated action and its tactical rationale rather than on an asserted final balance. The practical consequence is that the unanswered questions are part of the story; that is a consequence of the reported record, not a substitute for missing evidence. The timeline is not proof of cause. *The tactic is documented more firmly than its result.* ## The report can establish a tactic, not a complete result ### The supported conclusion For the next decision, **published video** **pre-launch strike** **attributed report** define the point at issue. The sources support a tightly framed conclusion: a published video was reported to show a Ukrainian FPV striking a Shahed before launch, alongside official Ukrainian claims of strikes on related drone infrastructure. A number alone cannot settle it: the available material supports the evidence supports a pattern, not a complete scorecard, but it does not establish a broader conclusion that the material never makes. The event demands a careful verb. The next test lies outside the announcement, **published video** **pre-launch strike** **attributed report** place the claim in a specific chain of decisions. The sources support a tightly framed conclusion: a published video was reported to show a Ukrainian FPV striking a Shahed before launch, alongside official Ukrainian claims of strikes on related drone infrastructure. The practical consequence is that the evidence supports a pattern, not a complete scorecard; that is a consequence of the reported record, not a substitute for missing evidence. The evidence must carry the weight. ### The boundary of certainty At the centre of the record, **independent authentication** **quantified damage** **Russian confirmation** define the point at issue. The same sources do not establish exact location and time for the video, quantified effects, or Russian confirmation. Those limits do not diminish the relevance of the tactic; they prevent relevance from hardening into unsupported certainty. That is a boundary, not an excuse: the available material supports the report is strongest where it is precise, but it does not establish a broader conclusion that the material never makes. The record stops there. The distinction carries weight, **independent authentication** **quantified damage** **Russian confirmation** place the claim in a specific chain of decisions. The same sources do not establish exact location and time for the video, quantified effects, or Russian confirmation. Those limits do not diminish the relevance of the tactic; they prevent relevance from hardening into unsupported certainty. The practical consequence is that the report is strongest where it is precise; that is a consequence of the reported record, not a substitute for missing evidence. That is not a conviction. *War reporting fails when a caveat disappears.* ## Conclusion ### A video can show the tactic without proving every outcome The documented starting point, **8 August 2026** **Serhii Sternenko** **Donetsk City airport** define the point at issue. The published footage and ISW’s report put the pre-launch tactic into view. Ukraine’s official account of relay-station and launch-site strikes provides a wider operational context, but it does not independently certify this particular clip. The wording matters here: the available material supports the responsible conclusion is a reported strike with a defined evidentiary limit, but it does not establish a broader conclusion that the material never makes. The figure needs its source. *The evidence must keep its boundary.* The date changes the reading, **Olenivka** **Zaliznyi Port** **Hvardiiiske** place the claim in a specific chain of decisions. Those named sites show why launch infrastructure has become a target set. The unanswered issues remain exact video authentication, damage measurement, and confirmation from the other side. The footage may be real and important; its claim still needs its verbs. The practical consequence is that precision is the report’s protection; that is a consequence of the reported record, not a substitute for missing evidence. The video is not a verdict. **By Maxime Marquette, columnist** ## Columnist's transparency note ### Editorial stance I am not a journalist but a **columnist and analyst**. My expertise lies in observing and analysing the geopolitical, economic and strategic dynamics that shape our world. My work is to take political strategies apart, to understand global economic movements, to put the decisions of international actors in context and to offer analytical perspectives on the changes that are redefining our societies. I do not claim the cold objectivity of traditional journalism, which stops at reporting facts. **I claim analytical clarity**, rigorous interpretation and a deep understanding of the complex issues that concern us all. My role is to give meaning to the facts, to place them in their historical and strategic context, and to offer a critical reading of events. ### Method and sources This text keeps the basic distinction between **verified facts and interpretive analysis**. The rule never changes: a factual claim is published only when a verifiable source supports it, and the sources this article actually used are listed under **Sources**, never here. **Primary source families** used by the publication, when the story has them: official statements from governments and international institutions, public statements by political leaders, reports from intergovernmental organisations, dispatches from recognised international news agencies. **Secondary source families**: specialised publications, internationally recognised news media, analyses from established research institutions, reports from industry organisations. When an article cites statistical, economic or geopolitical data, it comes from the institutions that produce it (intergovernmental organisations, central banks, national statistics offices), and the exact institution is named under **Sources**. ### Nature of the analysis The analyses, interpretations and perspectives in the analytical sections of this article are a **critical, contextual synthesis** based on the information available, the trends observed and the expert comments cited in the sources consulted. My role is to interpret these facts, to set them in the context of today's geopolitical and economic dynamics, and to give them a coherent meaning within the larger story of the changes shaping our time. These analyses reflect expertise built through continuous observation of international affairs and an understanding of the strategic mechanisms that drive global actors. This article describes a documented state of affairs on its publication date, not a prediction: later developments may shift its outlook. No update is promised in advance; when an article is corrected or completed, the change is dated in the text. ## Sources ### Primary sources - [Ukrainska Pravda, Ukrainian General Staff statement — 7 August 2026](https://www.pravda.com.ua/eng/news/2026/08/07/8047708/) - [Ukrainska Pravda, same official statement — 7 August 2026](https://www.pravda.com.ua/eng/news/2026/08/07/8047708/) - [Ukrainska Pravda, source record — 7 August 2026](https://www.pravda.com.ua/eng/news/2026/08/07/8047708/) ### Secondary sources - [Institute for the Study of War assessment — 8 August 2026](https://understandingwar.org/research/russia-ukraine/russian-offensive-campaign-assessment-august-8-2026/) - [Institute for the Study of War, source record — 8 August 2026](https://understandingwar.org/research/russia-ukraine/russian-offensive-campaign-assessment-august-8-2026/) - [Institute for the Study of War, source record — 8 August 2026](https://understandingwar.org/research/russia-ukraine/russian-offensive-campaign-assessment-august-8-2026/) --- Source: Maxime Marquette, MadMax. When citing, name the author and link https://mad-max.co/en/article/report-donetsk-video-shows-an-fpv-striking-a-shahed-before-launch