the home of online investigations
MH17 – The Open Source Investigation, Two Years Later
By Bellingcat Investigation Team
Translations: Русский
Today Bellingcat releases its latest report, "MH17 – The Open Source Investigation, Two Years Later", bringing together two years of research by Bellingcat into the fate of Malaysia Airlines Flight 17 on July 17, 2014. As part of this release Bellingcat communicated with experts in various fields for their analysis and opinions of MH17 related evidence.
Of particular interest is the work of The James Martin Center for Non-Proliferation Studies at the Middlebury Institute of International Studies at Monterey. The Center used the forensic image analysis software Tungstene to examine various images related to MH17, including photographs of smoke believed to be from the missile launch, images of the Buk missile launcher travelling through separatist territory on July 17, 2014, and satellite images presented by the Russian Defence Ministry on July 21, 2014. These are the significant findings from this analysis:
Images showing the Buk missile launcher and what is believed to be smoke from the launch of a Buk missile show no signs of digital alteration,
Satellite imagery presented by the Russian Defence Ministry of July 21, 2014 was "so heavily manipulated that it lacks any credibility as evidence."
The quality of the satellite images that Russia released is poor and appear altered. Therefore they recommend Russia should release the originals to the Joint Investigation Team.
Additional expert analysis and Bellingcat's own analysis shows further evidence that the satellite imagery presented by the Russian Defence Ministry on July 21, 2014 were a clear attempt to present fake evidence to the world in the case of MH17.
Based on Bellingcat's online open source investigation we believe the following events occurred:
Between June 23-25 2014 the 53rd Anti-Aircraft Missile Brigade transported vehicles within Russia to positions close to the Russian border with Ukraine. This includes Buk 332, later sighted in Ukraine on July 17 and 18 2014.
On July 17 2014 Buk 332 left Donetsk in the morning loaded onto a low-loader, travelling eastwards through separatist held territory, until it reached the town of Snizhe in the early afternoon.
After arriving in Snizhne Buk 332 unloaded and drove under its own town south out of the town.
Buk 332 arrived at a field south of Snizhne and fired a missile that resulted in the destruction of Flight MH17.
Buk 332 was next filmed travelling east through the separatist controlled city of Luhansk on the morning of July 18 2014.
On July 21 2014 the Russian Defence Ministry presented a series of false and fake information. This included lying about the flight path of MH17, lying about radar data, lying about the location of the July 18 2014 Luhansk video, and misdating and heavily manipulating satellite imagery,
Almaz-Antey presented data that was not reflected by witness statements on the ground, or any open source information.
The Russian Ministry of Foreign Affairs was only able present plagiarized blog posts when asked to present their evidence on the fate of MH17.
The full version of the report in English is available here, and available in Russian here.
The Bellingcat Investigation Team is an award winning group of volunteers and full time investigators who make up the core of the Bellingcat's investigative efforts.
Join the Bellingcat Mailing List:
Enter your email address to receive a weekly digest of Bellingcat posts, links to open source research articles, and more.
Support Bellingcat
You can support the work of Bellingcat by donating through the below link:
Donate to Bellingcat!
Sergey - September 28, 2016
Did Bellingcat ever published how many different Buks they detected around the date? It seems they only published photos and info related to movement of one specific Buk, and did not to publish anything else, which by itself is strange. Didn't Bellingcat found photos of other Buks travelling at around the same time in Russia or Ukraine? How many did they found? Where those Buks were located? Ukraine has around 60 Buks with at least 12 of them being near war zone at one time. Similarly I still don't understand claim that MH17 was shot down in error, believing it to be a Ukrainian army transport plane. At some point there were 12 Ukrainian Buks in the area, and there are around 100 flights going through this area every day, how they didn't shot down anything? Shouldn't there be some kind of transponder system on the plane to show it is civilian? Considering there is >500 Buks in different armies seems like it should be able to distinguish civilian from military plane.
Ivar - September 28, 2016
Of course the B777 had a civilian IFF transponder (standard fit) the problem appears that the BUK launcher was on its own without the presence of a command vehicle that would have had the tactical equipment (Radar, Coms & IFF Receiver/Tracker Display) that would have clearly shown it was a civilian commercial flight.
Rols - September 30, 2016
The Ukrainian forces would have no need to launch a SAM as the separatist forces had no aircraft. I'd imagine any Ukrainian SAM sites in the area would have been in case of Russia launching air strikes in support of separatists. BUK 332 is the launcher photographed with one missile missing from the launcher after MH17 was shot down. If you read the report, l can't see how you cannot draw the same conclusion as the investigation concluded.
Mary - October 2, 2016
They able good noodles on ears hang up others! On their photos the witness took the smoke from the rocket, but forgot to shoot the rocket itself. But for me – these photos rough work on photoshop. What they (Bellingcat) do it? The answer is obvious – to stop to find the true culprit. Those people who created this site, they are very interested in promoting the fake version. And they do it persistently and actively.
They show to people one station BUK. But to run a rocket at the goal, need 4 modules BUK. Missile launchers and two radars. Where are these 3 modules?
Oz - October 24, 2016
Its a BUK TELAR – Transporter, Erector, Launcher and Radar that is shown. It can operate by itself quite easily.
Subscribe to our email list to receive a weekly selection of stories published by Bellingcat during the previous week, along with links to our favorite examples of open source research around the web.
Along with our published content, we will update our readers on events that our staff and contributors are involved with, such as noteworthy interviews and training workshops.
© 2019 Bellingcat.
Office 6th,
37 New Walk,
LE1 6TA