Malaysia Airlines Flight MH17 was shot down over eastern Ukraine in 2014 by a Russian-supplied Buk surface-to-air missile, killing all 298 people on board
Where the evidence lands: SupportedThat MH17 was not brought down by accident or by any Ukrainian action, but by a Buk surface-to-air missile supplied by the Russian military and fired from a field controlled by Russian-backed separatists; and, in the fuller attribution advanced by investigators, that the specific launcher belonged to a Russian army brigade, was moved into Ukraine for the operation, and was returned to Russia once the plane was down.
Believed by: The Buk cause and the Russian-supplied launcher are the mainstream conclusion of the Dutch Safety Board, the Joint Investigation Team, a Dutch criminal court, and the European Court of Human Rights. The competing Russian accounts are rejected by those bodies and by independent open-source analysts, but continue to circulate through Russian state media and online.
On the 12th anniversary of the downing, marked on 17 July 2026, families gathered at the national MH17 monument in Vijfhuizen while European governments renewed pressure on Russia over accountability and reparations. In a statement, the EU High Representative welcomed the July 2025 European Court of Human Rights judgment and the May 2025 decision by the Council of the International Civil Aviation Organization, both finding Russia responsible for the downing and the deaths of the 298 people aboard, and reiterated the call for Russia to accept responsibility and provide full reparation; a parallel joint statement to the OSCE by the Netherlands, Australia and other states made the same demand. The commemorations and diplomatic pressure reinforce, and do not alter, the substantiated attribution set out in this file. source →
The full story
What is documented
Start with what is not in dispute. On the afternoon of 17 July 2014, Malaysia Airlines Flight MH17, a Boeing 777 flying from Amsterdam to Kuala Lumpur, broke apart in the air over eastern Ukraine and fell in fields near the village of Hrabove, in a region then held by pro-Russian separatists. Everyone on board was killed: 298 people, 283 passengers and 15 crew, among them 196 Dutch nationals, along with Malaysian, Australian and other citizens.
The Dutch Safety Board, which leads air-crash investigations in cases like this, published its final report in October 2015. It concluded that the aircraft was destroyed by a Buk surface-to-air missileof the 9M38 series, carrying a 9N314M warhead, which detonated just outside and above the left side of the cockpit. The distinctive fragment pattern, the crew's injuries, and the way the aircraft came apart in flight all pointed the same way. The Board examined and excluded the obvious alternatives: a bomb on board, a technical or structural failure, a meteor, and an attack by another aircraft.
So the question this file weighs is not whether MH17 was shot down by a Buk. On the physical cause, the record is firm. It is who supplied and operated that missile, how much of that has been established rather than alleged, and what to make of the competing accounts that Russia has offered since the first day.
Tracing the launcher
The criminal side of the case was handled by the Joint Investigation Team (JIT), led by the Netherlands and joined by Australia, Belgium, Malaysia and Ukraine. Its task was narrower and harder than establishing the cause: to reconstruct where the missile came from and who moved it.
In 2016 the JIT presented its first findings. The Buk had been fired from a farm field near Pervomaiskyi, in territory held by separatists at the time, and the launcher had been brought in from Russia and taken back across the border the same night. Two years later, in May 2018, the JIT went further and named the source: the launcher belonged to the 53rd Anti-Aircraft Missile Brigadeof the Russian armed forces, based in Kursk. Investigators identified seven distinguishing “fingerprints”, a particular wheel, a marking, a partly obscured side number, that matched the vehicle filmed in Ukraine to a specific launcher from a Russian military convoy.
A striking feature of this case is how much of it was open. The investigative collective Bellingcat and reporters geolocated photographs and videos of the Buk moving through eastern Ukraine from public social-media posts, and independently reconstructed the same convoy and route. The official conclusions did not rest on secret intelligence alone; they could be, and were, checked against a public trail of imagery.
The launcher was traced to a Russian army brigade, filmed on its way in, and reconstructed from public imagery. That trail is the anchor.
The court, and what it found
Findings by investigators are not the same as findings by a court, and this case has both. The District Court of The Hague tried four men, all in absentia: the Russians Igor Girkin (a former separatist military commander, also known as Strelkov), Sergey Dubinskiy and Oleg Pulatov, and the Ukrainian separatist Leonid Kharchenko. Only Pulatov had defence lawyers in the room.
On 17 November 2022, the court convicted Girkin, Dubinskiy and Kharchenko of causing the crash and of the murder of all 298 people aboard, sentencing them to life imprisonment, and acquitted Pulatov. Its reasoning is worth stating precisely. The men were found to have played key roles in bringing the Buk into Ukraine and into firing position, and the court held that the separatist-held area was under the overall control of the Russian Federation from mid-May 2014, making the conflict an international one. It also found that firing on the aircraft was a deliberate act intended to bring down a plane.
The court was equally clear about a limit. It said there was insufficient evidence to establish who physically fired the missile. The convictions attach to the men who organised the weapon's movement and deployment, not to a named crew who pressed the button. That distinction is part of the record, and this file keeps it.
The court convicted three men of the killing and placed the area under Russian control, while saying plainly it could not name who fired.
The Russian counter-narratives, examined and rejected
From the first day, Russia offered a different story, and it is worth setting out fairly, because it is what the attribution had to overcome. The accounts did not stay fixed; they arrived in sequence and were revised as each ran into difficulty.
The earliest was that a Ukrainian Su-25 fighter jet had been tracked near MH17 and had shot it down. This did not survive scrutiny: the Su-25 is a ground-attack aircraft whose service ceiling sits well below MH17's cruising altitude of around 10,000 metres, it was not armed to reach an airliner at that height, radar showed no other aircraft nearby, and the damage was that of a Buk warhead, not cannon fire. The jet's own chief designer publicly dismissed the idea, and Russia itself largely dropped it.
A second account came from Almaz-Antey, the Russian manufacturer of the Buk. It accepted that a Buk had downed MH17 but argued the missile was an older variant used by Ukraine and had been fired from Zaroshchenske, a site it claimed Ukraine controlled. Investigators found the opposite: the claimed area was in separatist hands, the warhead fragments matched the 9N314M type, and the forensic reconstruction pointed to the Pervomaiskyi field. Around these ran further claims, of doctored satellite images, of a staged scene, even that the wreck was really the missing MH370. None had evidentiary support, and no investigating body entertained them.
The honest way to hold all of this is not to pretend these were evenly matched theories. They were examined by the Safety Board, the JIT, and the court, and rejected. What they represent is the record of how the attribution was contested, and, in the shifting from one explanation to the next, part of why the official conclusions came to look as solid as they do.
Where the evidence lands
Keep the layers apart. The event is documented: MH17 and all 298 people aboard were destroyed by a Buk missile over eastern Ukraine on 17 July 2014, a conclusion the Dutch Safety Board reached after excluding every other cause. The attribution is substantiated: the launcher was traced to a Russian army brigade, a Dutch court convicted three men of the killing and found the area under Russian control, and an international human-rights court held Russia responsible. On these points the record is firm, which is why this file is rated Substantiated.
What substantiated does not mean is that every question is closed. The court said it could not identify who fired. The finding that the decision to supply the Buk reached the top of the Russian state is stated by investigators only as a “strong indication” that fell short of a prosecutable case. And no one convicted has been arrested or served a day, because Russia rejects the findings and does not surrender its nationals. Those are real limits, and this file names them rather than papering over them.
The right posture is to report exactly what the record supports and to resist letting Moscow's continued denial reopen what the evidence settled. MH17 was shot down by a Russian-supplied Buk; a Dutch court found named men responsible for the killing; who physically fired, and how high in the Russian state the decision ran, are the pieces that remain open. Holding those statements together is not hedging. It is the difference between reporting what four investigating and judicial bodies concluded and either overstating it or surrendering it to a counter-narrative that those bodies examined and set aside.
What's still unexplained
- Who physically fired the missile has not been established. The Hague court convicted three men of organising the transport of the Buk into position but expressly said it could not determine which individuals crewed the launcher and pressed the button, so the operational identity of the shooter remains formally open.
- How high the decision went is stated only as an indication. The JIT's 2023 conclusion that there were 'strong indications' the Russian president approved supplying the Buk was explicitly short of the standard for a prosecution, and the investigation was closed without charges reaching the Russian command level.
- No one has been arrested. All the convictions are in absentia, Russia does not extradite its nationals, and Igor Girkin is imprisoned in Russia on unrelated charges, so the prospect of any convicted person serving the MH17 sentence is remote.
- Russia's continued denial keeps the case politically contested. Even after the Dutch Safety Board, the JIT, the Hague court and the European Court of Human Rights, Moscow rejects the findings, which sustains the counter-narratives among audiences that treat the Russian state as the authoritative source.
Point by point
The claim: MH17 was destroyed in flight by a Buk surface-to-air missile, not by a bomb, a technical fault, or a mid-air collision.
What the record shows: This is established by the Dutch Safety Board's 2015 final report. The pattern of high-energy fragment damage, including bowtie- and cube-shaped perforations consistent with a 9N314M warhead, the detonation point outside and above the left of the cockpit, and the in-flight break-up all point to a Buk 9M38-series missile. The Board specifically examined and ruled out a bomb on board, a structural or technical failure, a meteor strike, and an air-to-air attack.
The claim: The missile came from a Russian military launcher, not a Ukrainian one.
What the record shows: The JIT traced the launcher to the 53rd Anti-Aircraft Missile Brigade, a unit of the Russian armed forces based in Kursk. Investigators matched the vehicle filmed in eastern Ukraine to a specific launcher from a Russian military convoy using seven distinguishing features, including a unique wheel, a marking, and a partly obscured side number. Open-source researchers at Bellingcat independently reconstructed the same convoy and route from social-media imagery.
The claim: The Buk was fired from territory controlled by the Ukrainian army, as Russia later argued.
What the record shows: The JIT placed the launch at a farm field near Pervomaiskyi that was in separatist hands at the time, corroborated by intercepted communications, witness accounts, photographs and a smoke-trail image. Almaz-Antey's alternative site, Zaroshchenske, was assessed by investigators to have been under separatist, not Ukrainian, control, and the Board's forensic analysis did not support a launch from there.
The claim: A Ukrainian Su-25 fighter jet shot MH17 down, as the Russian Defence Ministry initially suggested.
What the record shows: This account was examined and rejected. The Su-25 is a ground-attack aircraft with a service ceiling well below MH17's cruising altitude of around 10,000 metres and was not armed to reach it; radar data showed no other aircraft near MH17; and the damage signature matched a Buk warhead, not cannon fire or an air-to-air missile. The Su-25's own chief designer publicly dismissed the claim, and Russia itself largely abandoned it in later years.
The claim: A Dutch court, not just investigators, tested the case and reached a verdict.
What the record shows: Correct, and it is that judicial record this file treats as authoritative. After a trial running from 2020 to 2022, the District Court of The Hague convicted Igor Girkin, Sergey Dubinskiy and Leonid Kharchenko of causing the crash and murdering the 298 people aboard, sentencing them to life imprisonment in absentia, and acquitted Oleg Pulatov. The court found the men had organised bringing the Buk into Ukraine, and that the area was under Russian overall control.
The claim: Because the trial was held in absentia and no one is in custody, the verdict is meaningless.
What the record shows: That conflates enforcement with adjudication. It is true that none of the convicted men were ever arrested, that the trial ran in their absence, and that no sentence has been served, which is a genuine limit. But a conviction by a Dutch criminal court after a full trial is a formal judicial finding, not a rumour, and it was reinforced in 2025 when the European Court of Human Rights held Russia responsible for the downing.
The claim: The whole scene was staged or the plane was not really MH17, as fringe accounts allege.
What the record shows: There is no support for this. The wreckage, flight recorders, passenger manifests and human remains were recovered and identified through an international disaster-victim identification process, and the black boxes were analysed by international investigators. The Dutch Safety Board and the JIT worked from physical wreckage, radar, telephone intercepts and forensic pathology; the 'staged' and 'it was really MH370' claims rest on assertion rather than evidence and are not entertained by any investigating body.
The claim: Investigators found that the decision to supply the Buk reached the top of the Russian state.
What the record shows: This is the newest and most carefully hedged finding. In February 2023 the JIT said there were 'strong indications' that the Russian president personally approved supplying the Buk system to the separatists, but it added that the evidentiary threshold for a criminal prosecution had not been met and that it was ending the investigation for lack of prospects of prosecuting further suspects. This file reports that as an attributed indication, not a proven fact.
Other readings
Angles that don't fit neatly into the claim or its rebuttal, laid out and weighed, not endorsed.
The 'wrong target' reading
A widely held interpretation, consistent with the court's findings, is that MH17 was never the intended target: the crew that fired believed they were engaging a Ukrainian military aircraft in a week when separatist forces had shot down several, and hit a civilian airliner by catastrophic error. The Hague court found the firing was a deliberate act aimed at bringing down a plane, while stopping short of finding the operators knew it was a civilian flight. This mistaken-identity reading does not excuse the killing, and it does not change the attribution of the launcher; it is offered as the most evidence-consistent account of intent, not as a competing theory of who was responsible.
The shifting Russian counter-narratives
Rather than a single alternative, Russia advanced a sequence of them: a Ukrainian Su-25 shadowing the airliner, a Ukrainian Buk battery, doctored radar and satellite images, and disputes over the launch site. Independent analysts and the investigators treated these as a case study in reactive disinformation, noting that several were mutually inconsistent and were revised as each was rebutted. They are reported here not as serious rival explanations, all having been examined and rejected, but as part of the record of how the attribution was contested.
Timeline
- 2014-07-17Malaysia Airlines Flight MH17, a Boeing 777 en route from Amsterdam Schiphol to Kuala Lumpur, disappears from radar and crashes in fields near Hrabove in the Donetsk region of eastern Ukraine, an area held by pro-Russian separatists. All 298 people on board, 283 passengers and 15 crew, are killed; 196 are Dutch nationals.
- 2014-07-17Within hours, competing accounts emerge. Ukrainian officials and open-source researchers say a Buk missile was fired from separatist-held territory; a since-deleted social-media post attributed to separatist commander Igor Girkin claims a Ukrainian military aircraft has been downed, before the civilian identity of the wreck becomes clear.
- 2014-07Russia's Defence Ministry offers alternative explanations at a press briefing, including that a Ukrainian Su-25 fighter jet was tracked near MH17 and that a Ukrainian Buk battery was in the area. These accounts will shift over the following years.
- 2015-06Almaz-Antey, the Russian state manufacturer of the Buk system, holds a press conference accepting that a Buk downed MH17 but arguing it was an older 9M38M1 missile fired from Zaroshchenske, a site it says was under Ukrainian control. Investigators later dispute both the missile variant and the claimed launch location.
- 2015-10-13The Dutch Safety Board publishes its final report: MH17 was destroyed by a Buk 9M38-series missile with a 9N314M warhead that detonated just outside and above the left of the cockpit, causing an in-flight break-up. The Board explicitly excludes a bomb, technical failure, a meteor, and an air-to-air attack.
- 2016-09-28The Joint Investigation Team (JIT), led by the Netherlands with Australia, Belgium, Malaysia and Ukraine, presents its first criminal findings: the Buk was fired from a farm field near Pervomaiskyi, in separatist-held territory, and the launcher was brought in from Russia and taken back across the border the same night.
- 2018-05-24The JIT announces that the launcher has been traced to the 53rd Anti-Aircraft Missile Brigade of the Russian armed forces, based in Kursk, identifying seven distinguishing 'fingerprints' matching the vehicle filmed in Ukraine to Buk systems from a Russian military convoy.
- 2020-03-09The criminal trial of four suspects, Igor Girkin, Sergey Dubinskiy, Oleg Pulatov (all Russian) and Leonid Kharchenko (Ukrainian), opens at the District Court of The Hague. All are tried in absentia; only Pulatov is represented by defence lawyers.
- 2022-11-17The Hague court convicts Girkin, Dubinskiy and Kharchenko of causing the crash and the murder of all 298 aboard, sentencing them to life imprisonment in absentia, and acquits Pulatov. It finds the separatist area was under Russian overall control and that the men organised the transport of the Buk, though it could not establish who fired it.
- 2025-07-09The European Court of Human Rights, ruling in the inter-state cases brought by Ukraine and the Netherlands, holds Russia responsible for the downing of MH17 and for the deaths of everyone on board, the first time an international court has attributed the disaster to the Russian state.
Supported. That MH17 was destroyed in flight by a Buk 9M38-series missile is established by the Dutch Safety Board, which ruled out every other cause. The rated claim is the source of that missile, and it rests on a long chain of official findings rather than inference. The Dutch-led Joint Investigation Team traced the specific Buk launcher to Russia's 53rd Anti-Aircraft Missile Brigade in Kursk, established that it was trucked into a separatist-held field and back to Russia the next day, and in 2022 the District Court of The Hague convicted three men, in absentia, of causing the crash and murdering the 298 aboard, finding that the Donetsk separatist area was under Russian overall control. In 2025 the European Court of Human Rights held Russia responsible for the downing. The core attribution is therefore substantiated. Two honest limits stay attached: the court found it could not determine who physically pressed the button, and Russia has never accepted the findings, instead advancing a series of counter-narratives (a Ukrainian fighter jet, a Ukrainian Buk, a staged scene) that the investigators examined and rejected.
Reviewed by The Conspiratory Editors · Last reviewed July 19, 2026 · How we rate
Sources
- 1.Crash of Malaysia Airlines flight MH17 (final report), Dutch Safety Board (2015)
- 2.MH17 Findings: Dutch Safety Board Says Russian Buk Missile Took Down Plane, NPR (2015)
- 3.The criminal investigation by the Joint Investigation Team (JIT), Public Prosecution Service (Netherlands)
- 4.JIT MH17: strong indications that Russian president decided on supplying Buk, Public Prosecution Service (Netherlands) (2023)
- 5.Linking MH17 To Russia's 53rd Brigade, Radio Free Europe/Radio Liberty (2018)
- 6.Summary of the day in court: 17 November 2022 – Judgment, District Court of The Hague (courtmh17.com) (2022)
- 7.MH17 trial verdict: Dutch court finds two Russians, one Ukrainian separatist guilty, CNN (2022)
- 8.European Court of Human Rights: Russia responsible for downing of flight MH17, Government of the Netherlands (2025)
- 9.The Kremlin's Many Versions of the MH17 Story, Voice of America (2022)
- 10.Malaysia Airlines Flight 17, Wikipedia
Help us investigate
This is a living case file. If you spot an error or know evidence we missed, tell us, and weigh in on where you land.
Where do you land?
Cast your read on this one.
Comments
Add your take. Comments are read and approved by a human before they appear, so keep it on topic and civil. Please do not accuse named, living people of crimes.