DISINFO: The team that investigated the MH17 crash should be arrested for falsifying numerous evidences
DISINFORMATION CASE DETAILS
  • Outlet: es.news-front.info (archived)*
  • Date of publication: June 10, 2020
  • Outlet language(s): Spanish
  • Reported in: Issue 201
  • Countries / regions discussed: The Netherlands, Ukraine, Russia
Tags:
MH17

DISINFO: The team that investigated the MH17 crash should be arrested for falsifying numerous evidences

SUMMARY

The prime minister of the Netherlands must immediately order the arrest of the investigative team in the MH17 case due to numerous falsifications in the investigation. It is time to stop the lies of the Dutch investigators that are trying to “adjust” the evidence to the official version. Russian experts refuted 5 years ago that the Malaysian Boeing was taken down with a missile 9M38M1, which leaves characteristic damage that wasn’t found in the fuselage of the Malaysian plane. However, Dutch prosecutors refuse to accept the Russian data. Besides, the main suspect, the Ukrainian Security Service (SBU), which had a clear interest in the Boeing accident, was admitted in the investigation, which is like having the murderer involved in the investigation.

RESPONSE

Recurrent pro-Kremlin disinformation narrative on the downing of the flight MH17 over Ukraine, aiming to discredit the criminal trial and the Joint Investigation Team (JIT). The results of the investigation of the Joint Investigation Team are clear: flight MH17 was shot down by a missile from the 9M38 series, which was launched by the BUK TELAR system. The system was transported from the Russian Federation to an agricultural field near the city of Pervomaiskiy in eastern Ukraine, from where the rocket was launched. After firing, the system with one missing missile returned to the Russian Federation. On May 24 2018, JIT announced in its conclusion that the Buk belongs to the 53rd Anti-Aircraft Missile Brigade, a unit of the Russian armed forces in Kursk, Russian Federation. The public hearing on the incident started on 9 March 2020 in the Netherlands. There is no proof that any of the evidence has been manipulated or falsified by the JIT. In order to find out the cause of the crash, the Joint Investigation Team investigated all human remains, personal belongings and wreckage of the aircraft found in the vicinity of the disaster site. The traces were secured and investigated and compared by experts. In addition, the JIT sought and heard witnesses and experts, analysed radar and satellite images, assessed large amounts of telecom data such as intercepted telephone conversations and analysed big data. Read more about the investigation here. You can see other examples of pro-Kremlin disinformation on the MH17 case in our database, such as claims that JIT tampered with the evidence; that the plane was not downed by a BUK missile, but rather by a Ukrainian fighter; that the plane crash was triggered by an explosion on board; that the trial in The Hague is not justice but information warfare; that the irrefutable evidence of Russia’s innocence is being rejected; or that both the MH17 and the Skripal cases are anti-Russian provocations.

Embed

Related disinfo cases

Disclaimer

Cases in the EUvsDisinfo database focus on messages in the international information space that are identified as providing a partial, distorted, or false depiction of reality and spread key pro-Kremlin messages. This does not necessarily imply, however, that a given outlet is linked to the Kremlin or editorially pro-Kremlin, or that it has intentionally sought to disinform. EUvsDisinfo publications do not represent an official EU position, as the information and opinions expressed are based on media reporting and analysis of the East Stratcom Task Force.

    Your opinion matters!

    Data Protection Information *

      Subscribe to the Disinfo Review

      Your weekly update on pro-Kremlin disinformation

      Data Protection Information *

      The Disinformation Review is sent through Mailchimp.com. See Mailchimp’s privacy policy and find out more on how EEAS protects your personal data.