Malaysia Airlines Flight MH17

Overview

On July 17, 2014, Malaysia Airlines Flight 17 — a Boeing 777-200ER carrying 298 people from Amsterdam to Kuala Lumpur — was blown out of the sky over eastern Ukraine. The aircraft disintegrated at 33,000 feet, scattering wreckage and human remains across sunflower fields near the village of Hrabove in Donetsk Oblast. Everyone on board was killed: 283 passengers, including 80 children, and 15 crew members. It was the deadliest civilian aircraft shootdown since Korean Air Lines Flight 007 in 1983, and the worst aviation disaster in the history of the Netherlands, which lost 196 citizens in a single afternoon.

Within hours, the outlines of what had happened were already becoming clear. The plane went down in territory controlled by Russian-backed separatists who were fighting the Ukrainian military in the War in Donbass. Intercepted phone calls, social media posts, and physical evidence all pointed in one direction: a surface-to-air missile, fired by people who thought they were targeting a Ukrainian military transport and didn’t realize they’d just murdered 298 civilians.

What makes MH17 unique in the annals of conspiracy theories is that the conspiracy isn’t some suppressed truth fighting to get out. The truth got out. It got out thoroughly, painstakingly, and through one of the most rigorous multinational investigations in modern history. The conspiracy, in this case, was the cover-up — a sprawling, state-sponsored disinformation campaign run by the Russian Federation that became a textbook case study in how a modern authoritarian government lies, not to convince anyone, but to exhaust them.

The Flight

Malaysia Airlines Flight 17 departed Amsterdam Schiphol Airport at 12:14 p.m. local time on July 17, 2014, bound for Kuala Lumpur International Airport. It was a routine long-haul flight on a well-traveled route — one that passed over Ukrainian airspace, as hundreds of commercial flights did every day.

The Boeing 777-200ER, registration 9M-MRD, was one of the most reliable aircraft in commercial aviation. The same airframe type as the vanished MH370, which had disappeared four months earlier in one of aviation’s greatest mysteries, MH17’s aircraft had been in service since 1997 with a spotless safety record. The 777 had never suffered a hull loss due to mechanical failure in its entire history as of that date.

The passengers represented a cross-section of ordinary life. There were Dutch families heading to Southeast Asian holidays. Malaysian students returning home. An Australian family of five. A group of AIDS researchers and activists heading to an international conference in Melbourne — their deaths would be mourned by the global public health community for years. There were six delegates to the 20th International AIDS Conference, including Joep Lange, one of the world’s leading HIV/AIDS researchers. There were children. Infants. Grandparents. The youngest passenger was less than a year old.

The crew of fifteen was entirely Malaysian — experienced, professional, unremarkable in the best possible sense. Captain Wan Amran Wan Hussin, 52, had logged more than 13,000 flight hours. First Officer Mohd Ghafar Abu Bakar had over 12,000.

At the time of the shootdown, the war in eastern Ukraine was roughly four months old. Russia had annexed Crimea in March 2014, and pro-Russian separatists — armed, equipped, and in many cases directly commanded by Russian military intelligence — had seized government buildings across the Donetsk and Luhansk oblasts. Full-scale fighting was underway between Ukrainian military forces and the self-declared “Donetsk People’s Republic” and “Luhansk People’s Republic.” In the days before MH17, the separatists had shot down multiple Ukrainian military aircraft, including an An-26 transport plane on July 14 at an altitude of 6,500 meters. They were bragging about it openly on social media.

Ukrainian authorities had closed the airspace below 32,000 feet over the conflict zone. MH17 was flying at 33,000 feet — just above the restricted altitude. The crew had no reason to think they were in danger. Neither did the airlines that continued routing flights through the area. In hindsight, the altitude restriction was catastrophically insufficient. A Buk missile system, the kind of weapon the separatists had been requesting and receiving from Russia, can reach targets well above 70,000 feet.

At 1:20 p.m. UTC — 4:20 p.m. local time — MH17’s transponder signal vanished from radar screens. The aircraft’s flight data recorder captured a massive decompression event. The cockpit voice recorder captured a brief spike of noise — and then nothing. The 777 broke apart in midair, its wreckage falling across roughly fifty square kilometers of farmland. Some debris was found more than eight kilometers from the main crash site, indicating the aircraft came apart at altitude, not on impact.

On the ground, the scene was apocalyptic. Bodies and body parts lay in sunflower fields. Personal belongings — passports, stuffed animals, luggage — were scattered across the landscape. The fuselage was shattered. Local residents, who had already been living through a war, now found themselves walking through the remains of an international disaster.

And then the looting started.

The Crime Scene

The crash site was in separatist-controlled territory, and access was a nightmare from the beginning. International investigators, journalists, and OSCE monitors who attempted to reach the site were obstructed, delayed, and in some cases physically prevented from entering by armed separatist fighters. Bodies lay in the July heat for days. Evidence was tampered with. The black boxes were recovered by separatist forces and held for several days before being handed over — reportedly under pressure from the Malaysian government, which had quietly negotiated with separatist leaders.

Journalists who did reach the site described a scene of casual horror. Armed men in mismatched camouflage picked through wreckage. Local emergency workers collected bodies with no forensic protocols. Personal belongings of the dead were piled on the roadside. One widely circulated photograph showed a separatist fighter holding up a child’s stuffed animal.

The separatists initially restricted access so severely that Dutch and Australian forensic teams — whose citizens made up the majority of the dead — couldn’t reach the site for days. When they finally arrived, key evidence had been disturbed or removed entirely. Parts of the aircraft were missing. The separatists had loaded some remains onto refrigerated railcars, ostensibly for preservation, but the chaotic handling made forensic identification far more difficult.

Despite all of this, the physical evidence was overwhelming. Hundreds of high-energy impact fragments were recovered from the wreckage and from the bodies of crew members in the cockpit. The fragments bore markings consistent with a Buk 9M38 missile warhead — a weapon designed to destroy aircraft by detonating nearby and shredding them with a cloud of preformed metal fragments, each shaped like a small bowtie.

The Investigation

The formal investigation into MH17 was split into two parallel tracks. The Dutch Safety Board (Onderzoeksraad voor Veiligheid, or OVV) led the accident investigation — what happened and how. The Joint Investigation Team (JIT), a criminal investigation led by the Netherlands and including prosecutors from Australia, Belgium, Malaysia, and Ukraine, pursued the question of who was responsible.

The Dutch Safety Board Report

The DSB published its final report in October 2015, fourteen months after the crash. The findings were unequivocal: Malaysia Airlines Flight 17 was destroyed by a 9N314M warhead carried on a 9M38 series missile, launched by a Buk surface-to-air missile system. The warhead detonated above and to the left of the cockpit, killing the flight crew instantly and causing the aircraft to break apart in flight. The passengers in the rear sections of the aircraft were likely alive for up to 90 seconds as the fuselage fell, though most would have lost consciousness immediately due to explosive decompression and hypoxia.

The DSB reconstructed a large section of the aircraft fuselage in a hangar at Gilze-Rijen Air Base in the Netherlands. The reconstruction showed the devastating damage pattern: hundreds of penetrations in the cockpit area, consistent with a directed-fragmentation warhead designed to produce a cone of shrapnel at close range. The bowtie-shaped fragments recovered from the wreckage and from bodies matched those used exclusively in the Buk 9M38 missile.

The Joint Investigation Team

The JIT’s criminal investigation went further — and deeper. Over the course of several years, the team analyzed thousands of intercepted phone calls, social media posts, photographs, and videos. They interviewed hundreds of witnesses. They collaborated extensively with Bellingcat, the open-source investigation group, and incorporated signals intelligence from multiple allied nations.

In September 2016, the JIT published its first major findings. The Buk missile had been fired from a field near Pervomaysk, in territory controlled by the Russian-backed separatists. The missile launcher had been transported into Ukraine from Russia and returned to Russia after the shootdown — one missile short.

The JIT established the exact route the Buk convoy took. Using geolocated photographs and video from social media, dashcam footage, and satellite imagery, investigators traced the Buk TELAR (transporter erector launcher and radar) from the Russian border, through separatist-held territory, to the launch site near Pervomaysk, and back. The convoy included a low-loader truck carrying the Buk launcher, escorted by military vehicles. In photographs taken as it entered Ukraine, the launcher carried four missiles. In photographs taken as it left, it carried three.

In June 2019, the JIT announced murder charges against four individuals:

• Igor Girkin (also known as Strelkov), a Russian FSB officer who served as the self-proclaimed “Minister of Defense” of the Donetsk People’s Republic. Girkin had been the separatists’ military commander at the time of the shootdown.
• Sergey Dubinsky (call sign “Khmuryi”), a former GRU officer who served as head of intelligence for the separatist forces.
• Leonid Kharchenko, a Ukrainian who commanded a separatist combat unit.
• Volodymyr Pulatov, a former Russian military intelligence officer who served as Dubinsky’s deputy.

None of the four were accused of physically pressing the button. The charges were for their roles in acquiring, transporting, and deploying the weapon system that killed 298 people.

The Trial and Verdict

The trial of the four accused began on March 9, 2020, at the Schiphol Judicial Complex — a high-security courthouse built adjacent to the airport from which MH17 had departed. Only Pulatov was represented by defense counsel; Girkin, Dubinsky, and Kharchenko did not participate and were tried in absentia. Russia refused all extradition requests and denied any involvement.

The trial lasted over two and a half years. The prosecution presented thousands of pieces of evidence, including intercepted communications in which the defendants discussed acquiring air defense systems from Russia, coordinated the transport of the Buk launcher, and — in the immediate aftermath of the shootdown — scrambled to conceal what had happened. In one intercepted call from shortly after 4:20 p.m. on July 17, a separatist fighter was heard exclaiming that they had shot down a plane. When they realized it was a civilian aircraft, the tone changed. “It’s a passenger plane,” another voice said. The calls became frantic.

On November 17, 2022, the Dutch court delivered its verdict. Igor Girkin, Sergey Dubinsky, and Leonid Kharchenko were convicted of murder — all 298 counts — and sentenced to life imprisonment. Volodymyr Pulatov was acquitted, not because the court doubted his involvement, but because the evidence did not meet the standard required for conviction beyond a reasonable doubt. The court explicitly found that MH17 had been shot down by a Buk missile from the 53rd Anti-Aircraft Missile Brigade of the Russian armed forces, and that the missile had been fired from the field near Pervomaysk identified by both the JIT and Bellingcat.

The convicted men remain free. Russia will not extradite them. Girkin was subsequently arrested in Russia in 2023 and sentenced to four years in prison — not for his role in killing 298 civilians, but for criticizing Russia’s military leadership during the full-scale invasion of Ukraine. The irony was not lost on the families of the dead.

Russia’s Disinformation Campaign

If the investigation of MH17 represented the best of multinational cooperation and meticulous evidence-gathering, Russia’s response represented the worst of state-sponsored deception. Moscow’s disinformation campaign around MH17 became — alongside its election interference operations — one of the most extensively documented examples of what analysts call the “firehose of falsehood”: a propaganda strategy that doesn’t try to advance a single alternative narrative but instead floods the information space with contradictory claims, sowing confusion and apathy.

The point was never to convince anyone that Russia was innocent. The point was to make people throw up their hands and say, “Who really knows what happened?”

Here’s what they tried.

Theory 1: The Ukrainian Fighter Jet

The earliest and most persistent Russian alternative theory claimed that MH17 was shot down not by a surface-to-air missile but by a Ukrainian Sukhoi Su-25 ground attack aircraft. This theory was promoted heavily by Russian state media beginning within 24 hours of the shootdown.

There were several problems with this claim, all of them fatal.

The Su-25 is a close air support aircraft — the Soviet equivalent of an A-10 Warthog. It is designed to fly low and slow over battlefields, attacking ground targets. Its service ceiling is approximately 7,000 meters (23,000 feet). MH17 was flying at approximately 10,000 meters (33,000 feet). The Su-25 physically cannot reach that altitude, let alone maneuver and engage a target there. Even with extraordinary modifications, the aircraft lacks the pressurized cockpit, engine performance, and weapons systems necessary to intercept a Boeing 777 at cruising altitude.

The Su-25’s standard air-to-air armament consists of R-60 heat-seeking missiles — short-range weapons designed for self-defense against helicopters and slow-moving aircraft. The R-60’s 3-kilogram warhead could not produce the damage pattern observed on MH17’s fuselage. The bowtie-shaped fragments recovered from the wreckage are unique to Buk missile warheads and do not match any air-to-air weapon in the Ukrainian inventory.

Russia’s Ministry of Defense initially claimed to have radar data showing a “second object” — a fighter jet — near MH17 at the time of the shootdown. When independent analysts examined the data, it turned out the “second object” was a ghost return, a common radar artifact. The Russian MoD quietly stopped referencing this claim but never retracted it.

Despite all of this, the Su-25 theory persisted for years on RT, Sputnik, and Russian-language social media. It was cited by Russian diplomats at the United Nations. It was repeated by Russian officials who knew perfectly well it was false. It remains in circulation today on conspiracy forums, where it is treated as a legitimate alternative explanation by people who have never looked into the technical specifications of the aircraft they’re talking about.

Theory 2: Ukraine Fired the Buk

When the fighter jet theory became too embarrassing to maintain — though Russia never formally abandoned it — a second theory emerged: perhaps it was a Buk missile, but a Ukrainian Buk, not a Russian one. Ukraine operated the same Buk missile system, after all. Maybe the Ukrainians had fired it by mistake. Or on purpose.

This theory required ignoring the JIT’s trajectory analysis, which established the missile’s launch point as a field near Pervomaysk — deep in separatist-controlled territory, nowhere near any Ukrainian military position. It required ignoring the convoy evidence, including dozens of photographs and videos showing a Buk launcher being transported through separatist territory, escorted by separatist military vehicles. It required ignoring the intercepted communications in which separatist commanders discussed acquiring the weapon and coordinating its transport.

Russia’s Ministry of Defense held a press conference in 2015 at which it presented what it claimed was radar data proving the missile came from Ukrainian-controlled territory. The presentation included a computer-generated graphic purporting to show the missile’s trajectory. Independent analysts, including those at Bellingcat, demonstrated that the radar data was selectively presented and that the trajectory shown was physically inconsistent with the known impact pattern on the aircraft.

In a particularly brazen move, the Russian MoD presented satellite imagery that it claimed showed Ukrainian Buk systems deployed near the crash site. Bellingcat and other open-source analysts proved the images had been digitally altered — shadows were inconsistent with the claimed date and time, and metadata analysis showed the images had been processed through editing software. Russia’s own satellite photos were forgeries.

Theory 3: The Bodies Were Already Dead

This one deserves its own special category because of its sheer grotesqueness.

Within days of the crash, a theory began circulating on Russian social media — and was subsequently picked up by Russian state-adjacent media outlets — claiming that the bodies recovered from the crash site showed signs of having been dead for days before the crash. The claim alleged that the passengers had been killed beforehand and loaded onto the plane as part of an elaborate false flag operation.

The “evidence” cited was that some of the bodies appeared decomposed. This was because they lay in open fields in the July Ukrainian sun for days before recovery teams could access them, because armed separatists controlled the site and restricted access.

The theory was too deranged even for RT’s prime-time coverage, but it proliferated widely on Russian-language internet forums and was referenced by some separatist leaders in press statements. It served its purpose not by being believed, but by existing — another piece of noise in the information environment, another insane claim to be sorted through, another thing making reasonable people exhausted with the entire topic.

Theory 4: The CIA Did It

A subset of the Russian disinformation campaign alleged that the shootdown was a CIA false flag operation designed to frame Russia and justify Western sanctions. This theory offered no mechanism, no evidence, and no coherent motive, but it plugged into a well-established template of anti-American conspiracy thinking that has a reliable audience in Russia and in parts of the Western conspiracy community.

The CIA theory was typically presented alongside vague references to other alleged American false flag operations and was designed to appeal to audiences already primed to see American intelligence agencies behind every global event.

Theory 5: They Were Trying to Shoot Down Putin’s Plane

In the immediate aftermath of the crash, Russian state media floated the theory that MH17 was shot down by Ukrainian forces who were actually trying to assassinate Vladimir Putin. Putin’s presidential plane, it was claimed, had been in the area at the same time, and the two aircraft were supposedly similar in appearance.

This was false. Putin’s plane was not in the area. A Boeing 777 looks nothing like the Ilyushin Il-96 used by the Russian president. The two aircraft fly at different altitudes, different speeds, and have entirely different radar signatures. The claim was debunked within hours but continued to circulate on Russian media for weeks.

Theory 6: It Was Actually MH370

The strangest of all the Russian-promoted theories suggested that MH17 was not actually MH17 at all, but rather MH370 — the Malaysia Airlines 777 that had vanished over the Indian Ocean four months earlier. According to this theory, MH370 had been secretly landed somewhere, loaded with already-dead passengers (see Theory 3), and flown over Ukraine to be shot down as part of a false flag operation.

This theory combined elements of the “dead bodies” claim with the ongoing mystery of MH370 and added a layer of baroque complexity that made it irresistible to a certain strain of conspiracy enthusiast. It was physically impossible — the two aircraft had different registration numbers, different configurations, and different maintenance histories, all of which were verified from the wreckage — but impossibility has never been a barrier to a determined conspiracy theorist.

The Method Behind the Madness

The important thing to understand about Russia’s MH17 disinformation is that these theories were not presented as a coherent alternative narrative. They contradicted each other. A Ukrainian fighter jet can’t have shot down the plane if a Ukrainian Buk did it. The CIA can’t have orchestrated a false flag if Ukraine was trying to assassinate Putin. The bodies can’t have been dead for days if the plane was actually MH370 that had been secretly flown over Ukraine.

This wasn’t a bug. It was the feature.

The Russian disinformation strategy — documented extensively by researchers at the RAND Corporation, the EU’s East StratCom Task Force, and academic institutions worldwide — operates on the principle that coherence is irrelevant. The goal is volume. Flood the zone with enough competing narratives that people stop trying to figure out which one is true. Make the whole subject feel impossibly complicated. Make people disengage.

It worked, to an extent. Public polling in Russia consistently showed that a majority of Russians either believed that Ukraine was responsible for shooting down MH17 or were unsure what had happened. In parts of the Western conspiracy community, MH17 became “controversial” — a matter of “debate” — despite the evidence being as close to conclusive as any international investigation has ever produced.

The Bellingcat Revolution

If MH17 was a landmark in state-sponsored disinformation, it was equally a landmark in the emerging field of open-source intelligence. And no organization was more central to that development than Bellingcat.

Bellingcat was founded in 2014 by Eliot Higgins, a British blogger and self-taught analyst who had previously operated under the pseudonym “Brown Moses.” Higgins had made his name by analyzing weapons used in the Syrian civil war through YouTube videos and social media photographs. He had no intelligence background, no military training, and no institutional affiliation. He had a laptop, an internet connection, and an obsessive attention to detail.

The MH17 investigation became Bellingcat’s defining project. Starting with photographs and videos posted on Russian social media — VKontakte, Odnoklassniki, and other platforms — Bellingcat’s team of volunteer analysts began tracking the Buk missile launcher that had shot down MH17.

They found it. They found all of it.

Social media users in separatist-controlled eastern Ukraine had photographed and filmed the Buk convoy as it passed through towns on its way to the launch site. Some had posted the images publicly, not realizing their significance. Others had uploaded dashcam footage showing the low-loader truck carrying the Buk launcher through intersections. Russian soldiers had posted selfies geotagged near the Ukrainian border. Separatist fighters had bragged about receiving new air defense equipment.

Bellingcat’s analysts geolocated each photograph using building landmarks, road layouts, shadows, and background features. They established a precise timeline of the Buk launcher’s journey: from the Russian border, through the cities of Donetsk and Torez, to the field near Pervomaysk where it was launched, and back again. They identified the exact Buk TELAR unit — a vehicle with a specific set of identifying features, including bent side skirts and a particular arrangement of equipment on its chassis.

Most remarkably, Bellingcat identified the Buk launcher’s parent unit. Using Russian military vehicle registration databases, unit photographs posted online by Russian soldiers, and satellite imagery of Russian military bases, they determined that the launcher belonged to the 53rd Anti-Aircraft Missile Brigade, based in Kursk, Russia. The JIT subsequently confirmed this finding.

Bellingcat also proved that Russia’s official evidence was fabricated. When Russia’s Ministry of Defense presented satellite images purporting to show Ukrainian Buk systems near the crash site, Bellingcat’s analysts demonstrated that the images had been doctored — shadows were inconsistent, resolution was selectively altered, and the images contained artifacts consistent with digital manipulation. When Russia presented radar data, Bellingcat showed it was incomplete and misleading.

The MH17 investigation established Bellingcat as a serious intelligence actor and demonstrated that open-source investigation — using publicly available information rather than classified sources — could produce results as rigorous as any state intelligence service. The methodology Bellingcat developed during the MH17 investigation has since been applied to chemical weapons attacks in Syria, the poisoning of Sergei and Yulia Skripal in Salisbury, the attempted assassination of Alexei Navalny, and countless other cases.

Higgins himself became one of the most consequential figures in twenty-first-century journalism — a hobbyist who helped build a new discipline of accountability.

Evidence and Analysis

The evidence that MH17 was shot down by a Russian Buk missile from the 53rd Anti-Aircraft Missile Brigade is not a matter of interpretation or debate. It has been established through multiple independent lines of investigation, each of which would be sufficient on its own. Together, they constitute one of the most thoroughly proven cases in the history of international criminal investigation.

Physical evidence: Hundreds of bowtie-shaped metal fragments recovered from the aircraft wreckage and from the bodies of crew members were identified as components of a 9N314M warhead, used exclusively in the Buk 9M38 missile. The damage pattern on the reconstructed fuselage was consistent with a Buk warhead detonating above and to the left of the cockpit. No evidence consistent with any other weapon type — including air-to-air missiles or aircraft cannon fire — was found.

Trajectory analysis: Both the DSB and the JIT established the missile’s launch point through independent analysis of the fragmentation pattern, the damage distribution, and the recovered warhead components. Both analyses pointed to the same area: a field near Pervomaysk, in separatist-controlled territory.

Digital evidence: Dozens of photographs and videos, posted on social media by civilians and separatist fighters, documented the Buk convoy’s journey through eastern Ukraine. These images were geolocated, time-stamped, and verified by both Bellingcat and the JIT. The convoy’s route, from the Russian border to the launch site and back, was established with minute-by-minute precision.

Intercepted communications: The JIT obtained and analyzed thousands of intercepted phone calls between separatist commanders, Russian military officials, and local fighters. These calls documented the request for and delivery of air defense systems, the transport of the Buk launcher, and the immediate aftermath of the shootdown — including panicked conversations in which participants realized they had destroyed a civilian aircraft.

Satellite imagery: Commercial satellite imagery corroborated the convoy route and the launch site. Images showing a smoke plume consistent with a missile launch were captured by satellites passing over the area at the relevant time.

Forensic identification: Dutch forensic teams eventually identified all 298 victims through DNA analysis, dental records, and other methods. The identification process took over two years due to the condition of the remains and the compromised crime scene.

Cultural Impact

MH17 was a hinge point — one of those events that sits at the intersection of several larger shifts in how the world works.

For the Netherlands, it was a national trauma comparable in scale and emotional impact to a terrorist attack. The country lost 196 citizens — a staggering number for a nation of 17 million people. The repatriation of remains became a national ceremony. Military transport planes carrying coffins landed at Eindhoven Air Base, where they were met by the Dutch royal family, the prime minister, and thousands of grieving citizens lining the roads of the motorcade route from the airport to a military barracks converted into a forensic identification center. The procession recurred, flight after flight, over the course of weeks. The Netherlands, a country not prone to public displays of collective grief, was fundamentally changed.

For the families of the dead — Dutch, Malaysian, Australian, British, Indonesian, German, Belgian, and a dozen other nationalities — MH17 became a years-long ordeal of delayed justice, obstructed investigations, and the particular cruelty of having a foreign government systematically deny and ridicule the circumstances of their loved ones’ deaths.

For international aviation, MH17 exposed a catastrophic failure of risk assessment. The fact that commercial flights were routed over an active war zone where military aircraft were already being shot down was a systemic failure involving airlines, air navigation service providers, and national aviation authorities. The International Civil Aviation Organization subsequently developed new protocols for conflict zone risk assessment and information sharing.

For the study of propaganda and disinformation, MH17 became a foundational case study. Russia’s response — the multiple contradictory theories, the fabricated evidence, the aggressive denial in the face of overwhelming proof — was analyzed by researchers as a prototype of the modern authoritarian disinformation playbook. The RAND Corporation’s influential 2016 report on the “firehose of falsehood” propaganda model drew heavily on the MH17 case. The EU established the East StratCom Task Force in part because of Russia’s MH17 disinformation campaign.

And for open-source intelligence, MH17 was the proving ground. Before MH17, the idea that a group of volunteer analysts working from their laptops could track a Russian military weapon system across an international border, identify its parent unit, and prove a sovereign nation was lying about its involvement in a mass killing — that idea would have sounded like fantasy. After MH17, it was demonstrated fact. Bellingcat’s methodology became the gold standard for accountability journalism and was adopted, adapted, and expanded by news organizations, human rights groups, and intelligence agencies worldwide.

Timeline

• July 17, 2014: MH17 departs Amsterdam at 12:14 p.m. local time. At 4:20 p.m. local time, the aircraft is struck by a Buk missile over eastern Ukraine and crashes near Hrabove. All 298 people aboard are killed.
• July 17, 2014 (evening): Igor Girkin’s social media accounts post a message claiming separatist forces have shot down an An-26 transport. The post is deleted when it becomes clear the target was a civilian airliner.
• July 18, 2014: Armed separatists restrict access to the crash site. International monitors from the OSCE are blocked from conducting a full inspection.
• July 21, 2014: The flight data and cockpit voice recorders are recovered by separatist forces and handed over to Malaysian officials.
• July 23, 2014: The Netherlands assumes lead responsibility for the investigation, given the majority of victims were Dutch citizens.
• August 2014: The Joint Investigation Team is formally established, including the Netherlands, Australia, Belgium, Malaysia, and Ukraine.
• October 2014: Bellingcat publishes its first report identifying the Buk missile launcher and tracing its route through eastern Ukraine.
• October 13, 2015: The Dutch Safety Board publishes its final report, concluding MH17 was destroyed by a 9M38 Buk missile warhead.
• September 28, 2016: The JIT announces its criminal investigation findings: the Buk missile was fired from separatist-controlled territory near Pervomaysk, and the launcher was transported from Russia.
• May 24, 2018: The JIT announces the Buk launcher belonged to Russia’s 53rd Anti-Aircraft Missile Brigade, based in Kursk.
• June 19, 2019: The JIT announces murder charges against Igor Girkin, Sergey Dubinsky, Leonid Kharchenko, and Volodymyr Pulatov.
• March 9, 2020: The trial begins at the Schiphol Judicial Complex in the Netherlands.
• November 17, 2022: The Dutch court convicts Girkin, Dubinsky, and Kharchenko of murder and sentences them to life imprisonment. Pulatov is acquitted.
• July 2023: Igor Girkin is arrested in Russia — not for MH17, but for criticizing Russia’s military leadership. He is subsequently sentenced to four years in prison.

Sources & Further Reading

• Dutch Safety Board (OVV), Crash of Malaysia Airlines Flight MH17, Final Report, October 2015
• Joint Investigation Team (JIT), Criminal Investigation MH17, Public Presentations 2016–2022
• Bellingcat, MH17: The Open Source Evidence, Investigative Reports 2014–2022
• Higgins, Eliot, We Are Bellingcat: Global Crime, Online Sleuths, and the Bold Future of News (Bloomsbury, 2021)
• Paul, Christopher and Miriam Matthews, The Russian “Firehose of Falsehood” Propaganda Model, RAND Corporation, 2016
• District Court of The Hague, Judgment in the MH17 Case, November 17, 2022
• International Civil Aviation Organization, Conflict Zone Information Repository, Post-MH17 Protocols
• de Mos, Max, MH17: In Search of Justice, Documentary, 2019
• European External Action Service, EUvsDisinfo Database, MH17-related Disinformation Cases

Related Theories

The MH17 shootdown intersects with several other documented conspiracy narratives. The disappearance of Malaysia Airlines Flight MH370 four months earlier — involving the same airline and the same aircraft type — created a bizarre resonance that conspiracy theorists exploited to link the two events. Russia’s MH17 disinformation campaign was part of a broader pattern of state-sponsored information warfare that has been documented extensively by Western intelligence agencies and media researchers. The case also echoes historical controversies over aviation disasters like TWA Flight 800, though in that case the conspiracy theories challenged the official explanation rather than defending it. And the Russian government’s willingness to deny proven facts and fabricate evidence mirrors patterns seen in other cases of Kremlin-linked violence, including the 1999 apartment bombings that launched Putin’s political career.