MH-17 Shoot-Down “Staged” – Stunning New Evidence Concludes “False Flag” 2

MH-17 False Flag

Radar Reveals Flight MH-17 Successfully Flies Away From Crash Scene.  Aluminum chaff designed to cloak the event was unsuccessful.


Forensics and Eye-Witness Accounts Confirm Alleged MH-17 Crash Victims Were Already Dead Prior to the Day of Attempted False Flag.


OVERVIEW:  Malaysia Airlines Flight 17 (MH17/MAS17) was a scheduled international passenger flight from Amsterdam to Kuala Lumpur that crashed on 17 July 2014 after being allegedly shot down with 283 passengers and 15 crew on board.

The Boeing 777-200ER airliner reportedly lost contact about 50 km (31 mi) from the Ukraine–Russia border and allegedly crashed near Torez in Donetsk Oblast, Ukraine, 40 km (25 mi) from the border.

The incident occurred during the so-called Battle in Shakhtarsk Raion, part of the ongoing manufactured conflict in Donbass, in an area where the Donbass People’s Militia were resisting unlawful aggression from Ukraine’s state-sponsored militia.

According to American and German intelligence sources, the plane was allegedly shot down by pro-Russian insurgents using a sophisticated Buk surface-to-air missile system fired from the territory which they were defending.  Open source investigation has now revealed the bulk of these reported events  to be untrue.  

The Dutch Safety Board issued a fabricated preliminary report on 9 September 2014 and promised a final (fabricated) report one year from the event which would fall on July 17, 2015.

On March 26, 2015, Ukraine’s Oligarchs were reported in dispute and communicating with the perpetrators of the MH-17 False Flag. (Source)

“We know that members of the Israeli military led the violent overthrow of the elected government of Ukraine in February 2014, and we know that Malaysia Airlines Flight MH17 was shot down while flying through the air traffic control region of Dnepropetrovsk, where the governor, Igor Kolomoisky, happens to be an Israeli billionaire involved in aviation companies.”

On July 2, 2015 it was reported that Russia rejected the report contained in the Dutch Safety Board final draft copy claiming the report:

“raises more questions than it gives answers.”  (source)

SRNNEWS.COM July 2, 2015

MOSCOW (AP) — A Russian aviation official says a draft Dutch report into last year’s crash of Malaysian Airlines flight 17 in eastern Ukraine “raises more questions than it gives answers.”

The Dutch Safety Board has made the draft available to representatives of Malaysia, Ukraine, the U.S., Russia, Britain, Australia and the Netherlands.

Oleg Storchevoi, a deputy chief of Rosaviatsiya, said Thursday the agency has complaints regarding both the technical data and the arguments in the report, according to Russian news agencies. He did not give details.

Controversy continues over who downed the plane last July over eastern Ukraine, killing all 298 people aboard. Ukraine and the West suspect it was destroyed by a Russian surface-to-air missile fired by Russian soldiers or Russia-backed separatist rebels fighting in the area. Russia denies that.

# # #

Malaysia MH-17 Update – July 20th 2

What Really Happened to MH17? An Open Source Investigation

by James Corbett
July 20, 2014

This post is intended as a round-up of available information on MH17 from various sources around the web. Corbett Report members are encouraged to debate and discuss the situation in the commments thread below, ask questions, suggest links, and otherwise contribute to this investigation. The article will be updated with information as the investigation continues. [Not a Corbett Report member? Sign up today.]



“A Boeing 777-200 passenger plane, operating Malaysia Airlines Flight 17, crashed in the Ukraine, east of Donetsk. All 298 on board were killed. Flight MH17 departed the gate at Amsterdam-Schiphol Airport, the Netherlands at 12:14 hours local time, bound for Kuala Lumpur, Malaysia. It was airborne at 12:30 (10:30 UTC) from runway 36C and reached a cruising altitude of FL310 at 12:53 (10:53 UTC). Ninety minutes into the flight, at 12:01 UTC and just prior to entering Ukrainian airspace, the flight climbed to FL330. This altitude was maintained until last contact by ADS-B receivers of flight tracking websites, about 13:21 UTC.

“At the point of last contact it was flying 1000 feet above airspace that had been restricted as a result of ongoing fighting in the area. Malaysia Airlines reported that MH17 filed a flight plan requesting FL350 throughout Ukrainian airspace. However, the flight was instructed by Ukrainian air traffic control to fly at FL330.”  *** Continue

Government Story of Malaysia MH-17 Missile Attack In Tail-Spin 3

MH-17 Missile Attack QuestionsA previous post exposed the issue of foreknowledge when videos dealing with the aftermath of the alleged missile attack, were revealed to be produced prior to the crash of Flt MH-17. (More)

On July 20th, the Corbett Report published a useful summary that discloses many irregularities in corporate media coverage and international governmental propaganda sources. (More)

Now we look at more media propaganda published as perception management to global audiences.

EXHIBIT A: The aircraft allegedly shot down over Shaktarsk is a Boeing 777-200, (Tail number,  9M-MRD) – the identical model aircraft (Boeing 777-200) that remains missing in the mysterious disappearance on Flt. MH-370 – tail number, 9M-MRO).

Recent, “near conclusive” evidence reports that MH-370 (9M-MRO) was actually hijacked raising the possibility that aircraft parts from 9M-MRO could have been salvaged, altered, re-painted and used to create the crash scene for MH-17 (9M-MRD).

Malaysia MH-17 and MH-370 as 9M-MRD- 9M-MRO-B


EXHIBIT B:   Mail Online Reported the allegedly doomed Flight MH-17 carrying the tail number 9M-MRD was allegedly photographed by a passenger before boarding.  Closer inspection of the nose gear (See EXHIBIT A) reveals the aircraft carries the tail number 9M-MRC.  This finding makes it impossible that the “doomed flight” photo was taken on the day of departure.  Records available in EXHIBIT G show that the previous departure of 9M-MRC  from Amsterdam occurred on 7/11/2014 as flight MH-17.

MH17 Wrong Aircraft at Gate 9M-MRC-b


EXHIBIT C:  Photos of the crash scene reveal key sections of aircraft wreckage that appear like landscape at “stone henge”.  Of interest is the section of aircraft containing the tail number or “N” number (9M-MRO or 9M-MRD) that serves as a registration number to identify a particular aircraft in the Malaysia Airlines fleet.

The Tail Number for the allegedly doomed flight is 9M-MRD.  The tail section apparently fell from the sky in a vertical position as a convenient opportunity for photographers to easily show the world this plane is not to be confused with tail number 9M-MRO from the flight MH-370 – the Malaysia airliner that is now revealed to have been  hijacked.

MH-17 Crash Scene Tail Number-both photos


EXHIBIT D:  Prominent photo of tail section with Malaysia Airlines logo (livery) provides observers with hollow assurance that the aircraft was positively identified as 9M-MRD.

With the example of  this “agent” walking all over the crash scene evidence, the media has already promoted the idea that the NTSB or designated crash scene investigators will not likely be able to carry out a competent investigation. After all, what would a thorough forensic analysis of the crash scene be obligated to report if it were allowed to take place?

Armed pro-Russian separatist stands on part of the wreckage of the Malaysia Airlines Boeing 777 plane after it crashed near the settlement of Grabovo in the Donetsk region


EXHIBT E:  Alleged crash scene baggage seems too clean to be true.  How likely is it that not one ripped, burnt, charred, shredded or blood-stained item can be detected in this photo?

MH-17 Baggage on ground


EXHIBIT F:   Flight Radar-24 screen capture on the day following the crash (7/18) shows  MH-17, (9M-MRD) as “canceled” on the date of the crash (7/17).  Why is it reported that the “doomed” flight was “canceled” before it was struck by a missile?

As horrific as the crash was reported to be, why did Malaysia Airlines boldly resume normal scheduling of the MH-17 flight for the following day (7/18) and before the risk of a repeated missile attack could be determined.?  The screen-shot was taken after takeoff and while the aircraft (9M-MRL) was still in the air and presumably “safely” en route.  When did Malaysia Airlines determine “business as usual” was more important than air safety?

Flight Radar - MH-17 Cancelled on 7-17-2014-a


EXHIBIT G:  The record shows that from June 12 through July 17, thirteen (13) different B-777 aircraft were assigned to fly the MH-17 flight schedule for a total of 36 trips from Amsterdam to Kuala Lumpur. 

Of special interest is the last flight for 9M-MRD on this route prior to the alleged crash occurred on June 18, 2014 . During this interval only 3 other aircraft flew the route only one time:

(1) 9M-MRM on 6/16,  (2) 9M-MRF on 7/5 and (3) 9M-MRC on 7/11.

Two of the aircraft flew the route within 12 and 6 days, respectively with the probability both aircraft could fly again before exceeding a 30 day hiatus.  This  distinguishes 9M-MRD and 9M-MRM as the only two – out of 13 aircraft – to exceed a 3 week hiatus between scheduled service as Flight MH-17.

MH-17 Schedule Complete


EXHIBIT H: The starboard section of the fuselage contains important evidence about the configuration of the windows beneath the flag.  Archive photos from 2014 show both aircraft were fitted with the metal “plug” aft of the flag rather than a transparent window. To be clear, this finding, alone does not serve as significant evidence that the aircraft in the photo is actually the hijacked MH-370/9M-MRO but is worth filing for future reference.  Photos of each aircraft showing the metal plug configuration from are available: 9M-MRD  Feb 8, 2014  and 9M-MRO Jan 4, 2014

Coconuts TV Reorts:

“Michael Holmes of CNN shared an image on Twitter via his account @holmescnn of a section of what appears to be a Malaysia Airlines jetliner on a grassy field. The Malaysian flag is clearly depicted and the red and blue livery colours used by MAS are also shown.”

The source of the images, a man identifying himself as a tourist guide / traveller / photographer / former soldier from Slovenia, @MatevzNovak, has since posted more photos – taken by a Nadezhda Chernetskaya – of what he claims to be the crash site of Flight MH17 in Grabovo, Ukraine.  (TRNS)

MH17-starboard-Crash Scene- 2 panels


There is much more to discover about this story that bankster controlled media will never report.  If you are paying for cable TV you are most likely financing the largest source of disinformation on earth.

Evidence of Foreknowledge Reported in Alleged MH-17 Missile Attack 31

NOTE:  This preliminary post is waiting for a response from the author on the method used to determine the creation date of the video files alleged as evidence of foreknowledge
Blue Shift Header MH 17 False Flag(Google Translation from Swedish) Now confirmed: MH17 a false-flag attack – Israel & Kiev junta prime suspects (Source)

A look at the time stamps for the nine versions of the video that allegedly shows a conversation between Ukrainian anti-fascists and the Russian military and uploaded to what is said to be the Ukrainian Security Service (SSU) youtube account, indicating that all the videos were created before MH17 wrecked in the afternoon 2014-07-1

Remarkable unit with timestamps confirmed by the date stamp for when the videos were uploaded to a local server contained herein.

MH-17 False Flag-aUkrainian Security Service (SSU) Youtube Account Link

Another screen-shot from 7/19/2014

Note 7/19: Method used to gather data unknown at this time

Below is the screenshot for the time stamps for the nine videos on SSU’s youtube account, as shown in a forensic program .

MH-17 False Flag-Youtube Times

2014-07-16 20:32 UTC  is the time-stamp for the English version, then half past ten in the evening Kiev time, the day before MH17 crashed.

The time stamps of the two files in the screenshot above, without such confirmed by other video software to be:

2014-07-16 19:11:19 UTC
2014-07-17 09:31:06 UTC

 More Info


 Related Events: