MH17 Verdict: Real Evidence Points to US-Kiev Cover-up of Failed False Flag
Until this past Monday, the downing of Malaysian Airlines Flight MH17 on July 17th, 2014, was a potential game changer for global geopolitics and the New Cold War. However, a funny thing happened on the way to the Kremlin…
There are other well-known anomalies surrounding this event which have been covered at 21WIRE, as well as connections to MH370, but for the purposes of this investigation we will focus on both factual and speculative evidence brought forth by the US, Ukraine and Russia.
As we will clearly demonstrate, the only wild conspiracy theories being pushed right now, are those coming out of the US State Department, and the government in Kiev, Ukraine, which are being repeated by CNN, BBC, FOX-NewsCorp, ABC, CBS and NBC…
The Brink of War
Last Monday morning was not a pleasant one for the US State Department. Russian officials surprised Washington and its NATO partners when it released all available satellite imagery and air traffic control data which was recorded in and around the final minutes of Flight MH17 – and presented it to the world media on live television. The data painted a very different picture, drawing contrasting conclusions to what Washington and Kiev officials had been disseminating via western media since July 17th. Following their presentation, Moscow handed its findings – air traffic data and time stamped satellite imagery – to European authorities. We will review those findings in detail later in this report. In stark contrast, US officials have been reluctant to do the same. Is Washington willing to share any object data or evidence to the public, or is it only interested in sharing that which somehow fits into the same predetermined narrative it stood by on July 17th, one which already assigned guilt to both rebel fighters in eastern Ukraine and Russia?
We hope that political leaders and media organizations in the US and Europe will take the time to consider all available information, rather than simply repeat and spin what is bouncing around the media echo chamber. It’s also crucial to understand the geopolitical context in which this incident has occurred in order to discover who really possessed the motive, and the means to destroy this passenger aircraft, and which parties stand to benefit most from such an international incident.
After reviewing the evidence, all indicators points to the downing of MH17 as a highly coordinated, but failed false flag event.
MH17: A Doomed Flight Path
A Malaysian Airlines spokesman has already confirmed that, for some unknown reason, Kiev-based Ukrainian Air Traffic Control (ATC) ordered MH17 off of its original flight path along the international air route, known as L980.
Most likely, this order was given to pilots while MH17 was still in Polish air space. L980 is one of the most popular and most congested air routes in the world, as well as a key link between major international hubs in Europe, like London Heathrow, Amsterdam Schiphol, and Frankfurt, and Asian destinations, like Singapore, Mumbai, Hong Kong and Kuala Lumpur.
As MH17 moved into Ukrainian air space, it was moved by ATC Kiev approximately 200 miles north – putting it on a new course, heading directly into a war zone, a well-known dangerous area by now – one that’s hosted a number of downed military craft over the previous 3 weeks.
Robert Mark, a commercial pilot and editor of Aviation International News Safety magazine, confirmed that most Malaysia Airlines flights from Amsterdam to Kuala Lumpur would normally travel along a route significantly further south than the route MH17 was diverted onto. Data on all airline flight records can be found here.
The BBC reported on July 17th: “Ukraine’s SBU security service has confiscated recordings of conversations between Ukrainian air traffic control officers and the crew of the doomed airliner, a source in Kiev has told Interfax news agency.”
Independent investigators are worried that ATC audio records of the MH17 flight appear to have been confiscated by the Kiev government. No reason has been given for this loss of transparency, but not a word from Washington regarding this cover-up of crucial evidence.
Did this order to change the flight path come from the Ukrainian authorities? Was the pilot instructed to change course? To be sure, the order to change the flight path did not come from Eurocontrol, but rather from ATC in Kiev.
Clue: British media run interference by conjuring a “Storm”
Soon after the incident, British news outlets began floating the story – without evidence, that MH17 was diverted to “avoid thunderstorms in southern Ukraine”. This was also placed on Wikipedia at the same time. Nico Voorbach, who is Dutch, is president of the European Cockpit Association, and was the man used to nudge out this talking point. Voorbach casually slides this crucial fabrication out there, telling The Guardian of all papers, “I heard that MH17 was diverting from some showers as there were thunderclouds”.
The only problem is that Malaysian Airlines immediately refuted this in a report from Malaysia News:
“ MAS operations director Captain Izham Ismail has also refuted claims that heavy weather led to MH17 changing its flight plan (…) There were no reports from the pilot to suggest that this was the case,” Izham said.
What is significant, however, is that the Western media acknowledged that the change in the flight path did occur, indicating that the alleged “heavy weather” narrative is a fabrication designed to distract, and obscure the fact that MH17′s course was indeed divert into the war zone that day.
Global Research clarifies this confusing issue:
“The route over Ukrainian airspace where the incident occurred is commonly used for Europe to Asia flights. A flight from a different carrier was on the same route at the time of the MH17 incident, as were a number of other flights from other carriers in the days and weeks before. Eurocontrol maintains records of all flights across European airspace, including those across Ukraine.”
“What this statement confirms is that the MH17 ‘s “usual flight path” was similar to the flight paths of some 150 international flights which cross Eastern Ukraine on a daily basis. According to Malaysian Airlines “The usual flight route [across the sea of Azov] was earlier declared safe by the International Civil Aviation Organisation. The International Air Transportation Association has stated that the airspace the aircraft was traversing was not subject to restrictions (that approved flight path is indicated in the maps below).”
The regular flight path of MH17 (and other international flights) over a period of ten days prior to July 17th (day of the disaster), crossing Eastern Ukraine in a southeasterly direction is across the Sea of Azov.
The Times of India reported this: “Minutes before the crash caused by a missile strike, the AI pilots had also heard the controller give the Malaysian aircraft MH17 what is called “a direct routing”. This permits an aircraft to fly straight, instead of tracking the regular route which is generally a zig-zag track that goes from one ground-based navigation aid or way point to another. “Direct routing saves fuel and time and is preferred by pilots. In this case, it proved fatal,” said an airline source.”
UPDATE TBC: A number of bloggers have reported that the past flights on FlightRadar and FlightAware were changed between July 24-25th, the new “old flights” were placed over the Donetsk People’s Republic instead of the flights going further south. This does not jibe with what was reported last week by researcher Vagelis Karmiros using data from flight-tracking website Flightaware and published on a number established sites like Zero Hedge. Stay tuned here for updates.
The fatal event occurred somewhere in the interval between 17:21:28 and 17:22:30 Moscow Time. The exact time of the crash is believed to be at 5:23pm. The last available geographic coordinates can be found here on Flight Radar24:
Weather and Visibility Factor
Kiev-based air traffic controllers not only led MH17 right over its alleged ‘target zone’ in Eastern Ukraine’s Donetsk region, but also helped make it visible.
Although weather data online is all but unavailable for the area of Donetsk, Ukraine for July 17th, conditions are evident by numerous videos depicting the crash and crash site in the aftermath – it was cloudy and overcast, with more visibility above the cloud canopy. This factor is important because at its cruising altitude of approximately 33,000 feet (10,000 meters), the airliner would not be visible from the ground in the rebel-held area where Washington is insisting a SAM missile was launched. Why Kiev air traffic controllers order MH17 to suddenly drop its altitude, from 35,000 feet to around 33,000 feet, just before the plane’s demise is unknown for sure, but it would have been near impossible for the alleged rebel gunman occupying this relatively small rebel-held patch of land to make a visual sighting of MH17 and acquire the target during the 1-2 minute window they would have had (assuming they were even in possession of the BUK missile system).
The Los Angeles Times reports:
“Malaysia Airlines Flight 17 was cruising just 1,000 feet above restricted airspace when it was struck by a missile in Ukraine’s Donetsk region, according to aviation and intelligence officials.
“Despite ongoing violence in eastern Ukraine, including the recent downing of two military aircraft, Ukrainian aviation officials had closed the region’s airspace only below 32,000 feet in altitude.
Malaysia Airlines Flight 17 was cruising just 1,000 feet above restricted airspace (33,000 ft) when it was struck by a missile in Ukraine’s Donetsk region, according to aviation and intelligence officials.”
To date, Kiev has refused to acknowledge or explain why the plane was moved into position in this way. Moreover, Interfax news agency reported that Ukraine’s SBU security service confiscated recordings of conversations between Ukrainian air traffic control officers and the crew immediately after the incident.
The probability that this is all an ‘unfortunate coincidence’ reduces to near zero when one considers the air traffic data and Kiev’s denial of the close proximity of its Ukrainian SU-25 fighter jet in pursuit of MH17 minutes before the crash (see ‘Aircraft in the Vicinity’ below).
Small Rebel Target Window
Much has been made by the US and its media of MH17 being shot down and crashing in “the rebel-held area”, but few are aware of just how small the said area actually is. The Ukrainian military had already isolated the rebel area which Kiev and Washington insist a rebel-controlled BUK SAM missile battery had fired on the passenger jet. The actual size of this rebel-held patch is only 50 miles wide, with MH17 approaching on a southeastern route over Horlivka, the frontline of this rebel-held zone, towards Snezhnoye (Snizhne). Cruising at 580 mph (933 kmph), MH17 would have only been visible for a very short time – just over 1 minute (if Kiev had not ordered MH17 to alter its course and altitude then it would not have been visible at all), from the vantage point of the alleged rebel firing position. According the Jane’s Defense, the alleged culprit – an SA-11 (NATO code name) or ‘BUK’ missile system, requires 5 minutes set-up active targeting, followed by an additional 22 seconds ‘reaction time’ for target acquisition and firing. As the MH17 was only visible for 70 seconds above this rebel-held area surrounding Grabovo, unless the alleged rebel firing position was specifically tracking MH17 long before it entered the rebel-held airspace and could distinguish it from other military civilian aircraft also in the general vicinity, Washington’s theory and Kiev’s accusation – that rebels shot down this aircraft becomes even weaker.
Considering these factors, the probability increases greatly that targeting MH17 would have had to be premeditated far in advance of the 70 seconds it was visible above this particular rebel-held area.
Russian Satellite Data and Public Presentation
On Monday, the Russian government, with almost every major global media outlet in attendance, released all of its air traffic data and satellite imaging data (in fact, only part of it) – all verifiable, including time stamps and supporting data. The entire content of the presentation was also handed over to the European authorities. The conclusions to be drawn from this are stunning, to say the least. Despite the public release of this information, US and British media outlets did report back to its people on these findings. They are as follows:
Minutes before the downing of MH17, the plane made a mysterious ‘Left Turn’ as it flew over the Donetsk area at approximately 5:20pm Moscow time, making a sharp 14km deviation, before attempting to regain its previous course before dropping altitude disappearing from radar at 5:23pm. As we previously pointed out, air traffic controllers in Kiev had already diverted MH17 200 miles further north into the target zone, so the question remains: was Kiev ATC also responsible for this final, fatal diversion, or is there another reason for this unusual turn (see ‘Mysterious Left Turn’, below)?
According to clear satellite images provided, on July 16th, the Ukrainian Army positioned 3-4 anti-aircraft BUK M1 SAM missile batteries close to Donetsk. These systems included full launching, loading and radio location units, located in the immediate vicinity of the MH17 crash site. One system was placed approximately 8km northwest of Lugansk. In addition, a radio location system for these Ukrainian Army missile batteries is situated 5km north of Donetsk. On July 17th, the day of the incident, these batteries were moved to a position 8km south of Shahktyorsk. In addition to this, two other radio location units are also identified in the immediate vicinity. These SAM systems had a range of 35km distance, and 25km altitude.
From July 18th, after the downing of MH17, Kiev’s BUK launchers were then moved away from the firing zone.
Unlike rebel fighters, the Ukrainian military is in possession of some 27 BUK missile systems capable of bringing down high-flying jets, and forensic satellite imagery places at least 3 of their launchers in the Donetsk region on the day of this tragedy. Yet, Washington and NATO will not inquire about the possibility that any of these system had targeted MH17.
Watch the official video here:
This is a definitive smoking gun: why did the Ukrainian Army move these short-range anti-aircraft SAM missile batteries into position on July 16-17th – to an interior region of East Ukraine where it’s known that the rebel resistance possess no air crafts whatsoever? Not surprisingly, both the US and Kiev have not answered that difficult question, perhaps for obvious reasons.
In addition, the Ukrainian Army’s radio location traffic near Donetsk peaked on the 16th and 17th, including a total of 9 separate radio location systems active. On the 18th and 19th of July, radio location traffic from these stations dropped sharply, down to 4 stations. If, as Washington/Kiev claims, rebels fired a BUK missile at MH17, then the rebel radar location signals would be clearly noted and verifiable on the day; only, they are not.
Between 5pm-6pm Moscow Time on July 17th, the following aircraft have been identified in the general vicinity of MH17 on its course heading to its fatal destination of Grabovo:
1. Boeing 772 – traveling southeast from Copenhagen to Singapore at 5:17pm
2. Boeing 778 – traveling southeast from Paris to Taipei at 5:24pm
3. Boeing 778 – traveling northwest from Delhi to Birmingham circa 5:20pm
4. Boeing 777 – Malaysia Airlines Flight MH17 at 5:17pm
5. Ukrainian Fighter Jet (confirmation of model TBC) appears on radar, trailing MH17 at same altitude, est. 4km behind it at 5:21pm
Note: the pilots and passengers of Singapore Airlines Flight SIA351were close enough to have visually observed, at high altitude, the demise of MH17.
At 5:20pm MH17 began to abruptly lose speed, eventually slowing to 124mph (200kmph). About this time, possibly an Su-25 Ukrainian fighter jet appears on ATC radar climbing in the direction of MH17, before trailing MH17 on the same flight path approximately 3-5km behind MH17, rapidly approaching the same flight level – only minutes before MH17 disappeared on radar. Note that a Ukrainian fighter would not have been visible on ATC radar before it broke the ATC long-range standby radar tracking ceiling of 5km in altitude. Civilian ATC radar would not be able to identify this Su-25 as military because no secondary detection system is mounted – typical for military aircraft. Over the next four minutes, the Ukrainian fighter remained in the area.
Note also that the Su-25 can be armed with air-to-air R-60 missiles with a range of up to 5km-12km, but as 21WIRE has discovered, the Su-25 is not the only combat aircraft the Ukrainian Air Force has in its possession. On June 4, 2014, Janes Defense reported that Kiev have recently returned to service two other higher performance fighters, including the Su-27 ‘Flanker’ and the MiG-29 ‘Fulcrum’ fighters. The altitude ceiling performance characteristics of all in-service Ukrainian fighters are as follows:
Su-25 ‘Frogfoot’ fighter – Ceiling: 23,000 ft/7,000 m, or up 32,800 ft/10,000 m (depending aircraft modifications)
Su-27 ‘Flanker’ fighter – Ceiling: 64,000 ft/19,000 m
MiG-29 ‘Fulcrum’ jet – Ceiling: 59,000 ft/ 18,000 m
Su-24 ‘Fencer’ fighter – Ceiling: 36,000 ft/ 11,000 m, or 57,400 ft/17,500 m (depending on variations of turbo intake)
Although the exact altitude position of MH17 is not yet know for every given second of its final minutes, it’s clear that a Ukrainian combat jet was in its shadow. Suffice to say, Kiev had a number of combat aircraft capable of engaging MH17 at within a wide range of altitudes, as well as firing air-to-air missile at short range (3-5km)either upwards, or downward angles using laser guided targeting which is standard on many of these models.
Another Smoking Gun: Kiev government officials insisted on July 17th that, “No military aircraft were available in the region”. Based on available data detailed above, this appears to be a lie, indicating that a cover-up was taking place.
Again, it’s important to note here that at the moment when MH17 was allegedly was hit for the first time, at around 5:23pm Moscow time, the passenger jet was also within the range of several Ukrainian BUK batteries deployed close to Donetsk and as well as the Ukrainian Army’s BUK system positioned on the day just 8km south of Shakhterskoye, only a few miles from the eventual crash site at Grabovo.
IMAGE: A Ukrainian military Su-25 fighter jet carries air-to-air missiles, as do the Su-27 ‘Flanker’, and the MIG-29 Folcrum Fighter.
MH17′s Mysterious Left Turn
On passing glance, this seemingly minor, yet unexplained event doesn’t appear to be significant, but as is often the case, the devil is in the detail.
Again, was Kiev ATC also responsible for MH17′s final and fatal diversion from its course, or is there another reason for what appears to be an evasive maneuver?
One very real possibility for MH17 losing being diverted 14km to the left is that its GPS or navigation system was being jammed. US-NATO forces happened to be conducting an electronic warfare exercise in the Black Sea on July 17th (see ‘SEA BREEZE 2014′, below). In addition to this possibility, all Boeing jets (except Germany’s Lufthansa fleet) are equipped with a remote override that can be accessed by authorities in certain foreign countries, one being the United States. Although not publicly acknowledged until recently, Boeing Uninterruptible Autopilot (BUAP) systems have been standard since the late 1990′s, apparently designed to take control of a commercial aircraft away from the pilot or flight crew, chiefly in the event of a terrorist incident.
Another possible explanation for this crucial event in the timeline is that MH17 was hit, or damaged, taking an emergency 180º left turn for 14km, before disappearing completely off of radar. This appears to be the case. On July 23rd, Anna-News published an interview with retired Russian Air Force colonel Aleksand Zhilin (Александр Жилин) a frequent military commentator on Ukraine’s Civil War.
“According to the colonel, at 16:19:45 (local time, and 5:19pm Moscow time), a Ukrainian jet fighter targeted the Boeing with an air-to-air missile R-60. The missile damaged the right engine of the Boeing. The Boeing was hit, but still managed to stay in the air. However, in doing so, the Boeing turned 180 degrees to the left. It was at this moment that the false flag attack started falling apart. According to Zhilin, part of the plan controlled by the US with Ukrainian hands executing it was to have the Boeing crash past the southern frontline by the Ukrainian-Russian border. Had the Boeing fallen there, securing the crash sites with the troops in response to international pressure was on top of all else effectively to allow Kiev to lift the encirclement of its brigades (currently pinned down by rebels) in the southern pocket by the Russian border.”
“When, however, the Boeing started to turn in the opposite direction and was still apparently manageable, the US-Ukrainian headquarters of the special operation panicked and ordered the Buk battery to destroy the plane in the air in order to pre-empt the possibility of the Boeing’s emergency landing. A Buk missile was fired and the plane was then finally destroyed.”
21WIRE spoke to former Czech diplomat and political analyst, Vladimir Suchan, who puts Zhilin’s comments into context of what was happening militarily at the time of the crash. Suchan explains, “If MH17 was hit right over the frontline over Snezhnoye, this would have placed the timing and location of the intended downing and crash site to either the territory controlled by the Ukrainian army, or much closer to the border between Russia and Ukraine where the “securing of the site” would allow lifting the strategic encirclement of the Ukrainian troops in the south and thus, on top of other objectives, saving Kiev’s armed forces from its first major military defeat.” (see ‘Military All-Out Offense’ section below)
If, indeed MH17 was struck by an air-to-air missile at that time, a distress call may have been sent to Kiev ATC, but as yet, Kiev officials may be reluctant to share, or release the entirety of its communications from July 17th.
At the time of this report being filed at 21WIRE, a second source to verify this testimony is not presently available. Zhilin’s account certainly makes sense when placed next to all ATC and satellite data released by Moscow. However, flight recorder information and data from MH17′s black boxes would certainly be able to corroborate this timeline of events, and one hopes that Great Britain’s predetermined political stance against Russia does not prevent Downing Street, or MI5 Intelligence Services from releasing the black box information in its entirety and more importantly, a full and unedited disclosure to the media. More than likely, the BBC will have first access to this release, and how the BBC report their findings will be very telling.
Above, is one possible map of MH17 final minutes, as calculated from one source of available public data, available here: http://nikolay-istomin.livejournal.com/3057934.html.
This account is also consistent with the location of key pieces of wreckage scattered over the wider crash site radius. It shows M17 turning back on itself, after being struck initially. If this was the final path, then it completely disapproves the US (US State Department) conspiracy theory that a rebel-controlled BUK missile hit the plane head-on from Snezhnoye (Snizhne). This U-turn then also helps explain why Kiev’s first “leaked conversation of the rebels” (see ‘Kiev’s Botch Social Media Audio’ below) tried to place the rebel’s BUK battery at a completely different location in Debaltzevo, a few kilometers northwest of the main crash site at Grabovo. However, that would not explain the U-turn, which they tried so much to conceal – for it points to the Ukrainian jet fighter.
As part of their PR damage-control exercise, Washington released this Google Map-style graphic on Tuesday July 22nd, illustrating its theory that the rebel missile battery was now located in Snezhnoye:
Incredibly, Washington’s latest evidence/theory, depicted above, put their alleged rebel firing position in an entirely new spot – at Snezhnoye, and this now contradicts other ‘social media’ items being held-up by John Kerry and President Obama in their “mountain of evidence” (see ‘More Falsified and Sloppy ‘Evidence’ Supplied by SBU’, below).
The irony of this somehow escaped US State Dept. Deputy Spokesperson, Marie Harf during her globally televised ‘intelligence’ briefing on Tuesday (see ‘US Now in Full Retreat and Damage-Control Mode’, below).
Almost certainly, the US government already has a comprehensive communications, satellite and radar data set which could either corroborate, or disprove what Russia has released. The fact that Washington only has this Google graphic to offer to the public indicates that what it has… may not be what it wants.
Whistleblower: A Spanish Air Traffic Controller in Kiev
All evidence pointing to a Ukrainian Su-25 fighter jet in the same frame as MH17, also validates the testimony of ‘Carlos’, an ATC contractor in Kiev. ETNreceived information from an air traffic controller (Borispol Airport) in Kiev on Malaysia Airlines flight MH17:
“This Kiev air traffic controller is a citizen of Spain and was working in the Ukraine. He was taken off duty as a civil air-traffic controller along with other foreigners immediately after a Malaysia Airlines passenger aircraft was shot down over the Eastern Ukraine killing 295 passengers and crew on board. The air traffic controller suggested in a private evaluation and basing it on military sources in Kiev, that the Ukrainian military was behind this shoot down. Radar records were immediately confiscated after it became clear a passenger jet was shot down. Military air traffic controllers in internal communication acknowledged the military was involved, and some military chatter said they did not know where the order to shoot down the plane originated from. Obviously it happened after a series of errors, since the very same plane was escorted by two Ukrainian fighter jets until 3 minutes before it disappeared from radar.”
‘Carlos’ was reporting from the Kiev airport in real time on Twitter, of the downing of MH17 as the tragedy was taking place — during that very time and in the very next hour – only to disappear immediately, along with his twitter account.
Again, real mounting evidence which points to an obvious cover-up by Kiev and its NATO partners.
CSI: Flight MH17
Crime scene investigation is important, although reports to date from the crash site in Grabovo do not inspire very much confidence that a thorough and independent forensic investigation will be carried out, or that the chain of custody for evidence is being observed. The key evidence would be ballistics, including pieces of shrapnel retrieved from the wreckage. It should be easy to determine if they came from any of the following:
1. A bomb on board (this is still a possibility).
2. An air-to-air missile.
3. A surface-to-air missile.
After that, the autopsy of the bodies would reveal additional evidence about what really took place on July 17th. A present, the majority of the remains are being handled by the Netherlands government, and given their NATO involvement to date in the Ukrainian conflict, it’s debatable whether or not they would present any findings which do not square with Washington and Kiev’s narrow, yet ever-evolving narrative of the incident.
Finally, if MH17 was indeed shot down as a false flag provocation of war by either a Ukrainian SU-25 fighter, or a Ukrainian Army BUK SAM – or both, as much of the hard evidence suggests, then would Malaysia declare war on the Ukraine? Would the UN table a resolution backing sanctions against Ukrainian officials in Kiev for their role in this international war crime?
US-NATO’s Military Drill in the Black Sea Ended on July 17th
Russia’s Satellite Data and Public Presentation on Monday July 21st has put Washington on its back foot. The existence of this intelligence, now made public, along with other data in Russia’s possession, means that the Washington cannot show the real intelligence – which they too have. It’s no coincidence that US and NATO conducted a large-scale military and intelligence drill in the Black Sea just south of Crimea named, SEA BREEZE 2014, which just so happened to end on… July 17th. The drill included hundreds of US military specialists running ‘war simulations’ in electronic warfare, data collection from a spy satellite, and ‘monitoring’ of all passenger aircraft flying in the region. A massive drill – yet another improbable coincidence.
Another smoking gun: Is it a coincidence that the US had its new experimental satellite positioned over Eastern Europe for 1-2 hours, and directly over Donetsk in eastern Ukraine from 5:06pm – 5:21pm. Taking this fact into consideration, alongside the other improbable ‘coincidences’, leads to an almost certain conclusion.
In addition to SEA BREEZE, both US and British armed forces had also scheduled a concurrent military exercise, code named, Rapid Trident 2014, a NATO event which takes place annually in and around the Ukraine, designed to “promote regional stability and security, strengthen partnership capacity and foster trust while improving interoperability between the land forces of Ukraine, and NATO and partner nations,” according to the US Forces in Europe website. Since March, the Pentagon has kept quiet regarding the number of US forces, and hardware assets expected to participate in the maneuvers.
According to US Army spokesman Col. Steven Warren, Rapid Trident is the only Ukraine military exercise the US planned to participate in this year, and it’s main purpose was, “To help the Ukrainian military improve its troops and weapons operability with NATO forces.”
Ukrainian Military All-Out Offensive Timed For July 18th
Three uncomfortable realities in Kiev were prevailing before the downing of MH17 on July 17th.
First, the troops were losing morale, and suffering defections and other serious set-backs in an increasingly unpopular military theater of Eastern Ukraine. Kiev was losing the PR war hearts and minds in the Ukraine and abroad.
After the downing of MH17, Kiev garnered huge public sympathy and support, and just so happened to launch a massive offensive on July 18th, one which military analysts believe would have to have been planned many weeks in advance – and could not just be a knee-jerk reaction to the MH17 tragedy as government spokespersons in Kiev insist.
Secondly, they were losing the war. Behind the lines battle reports from Igor Strelkov’s blog at the time confirms this all-out offensive at Snezhnoye by the Kiev military planners against the People’s Republics of Donetsk and Lugansk – allowing the Ukrainian Army to penetrate deeper and deeper, in effect splitting Donetsk and Lugansk.
Vladimir Suchan adds, “After the loss of MH17 and some talk about “humanitarian ceasefire”, the Kiev regime launched three massive offensives from the north, the west (from Artemovsk, which included a large tank attack) and in the south. Since it always takes some good time to prepare an offensive, this had to be planned sufficiently ahead, though, with a view of the desperate situation for the junta in the south, most likely at a very accelerated pace. http://voicesevas.ru/news/yugo-vostok/2968-voyna-na-yugo-vostoke-onlayn-18072014-hronika-sobytiy-post-obnovlyaetsya.html
“In this regard, it is also very plausible that some hope was put on having the command of Novororrysia paralyzed, busy and distracted over MH17. By all accounts, both the timing and location of the MH17 crash, has enabled a huge ‘game changer’ in terms of how this conflict was previously going.”
If the international community were indeed to connect the prospect of a false flag attack on MH17 with the false flag attack by Maidan snipers back in February, and the attempted false flag attack with the Odessa massacre, perhaps the Ukrainian Civil War could be abated, for the right reasons.
As the US media juggernaut rolls ahead, there is still no sign of either Washington, London or Brussels admitting that their partners in Kiev are massacring civilians in a brutal civil war…
Disturbing reports are also coming in about the Ukrainian Military dropping White Phosphorus on civilian targets this week, as forces continue bombarding areas surrounding of Lugansk. Here are two unconfirmed videos, possible evidence of unconventional chemical weapons being deployed over several locations near Lugansk People’s Republic of Novorossia, from July 20-21, 2014:
Thirdly, Kiev is going broke trying to fund what appears to be an ethnic cleansing campaign in eastern Ukraine. Sources from the Parliamentary budget office in Kiev now confirm that as of August 1st, Kiev can’t pay its military (who are, in fact, waging war against its own people and calling it ‘anti-terror operations’).
“To continue the anti-terrorist operation in eastern Ukraine, it is necessary to amend the state budget and to find additional sources of its content. We do not have money to pay at least a cash security to our military from August”, stated Ukraine’s Finance Minister Oleksandr Shlapak, speaking in Parliament this week. According to Shlapak, funds previously provided by the state budget for these purposes has been calculated for the period prior to July 1st, and continued operations will require additional funds totaling 9 billion UAH ($1 billion). Infighting has already begun, as MP’s are now blaming the Ministry of Defense and army staff for corruption and looting of money.
In the wake of the MH17 disaster, US and its NATO allies are responding with a renewed call for more military aid to Kiev and to fast-track the Ukraine’s membership into Washington’s overseas military surrogate, NATO. As an emergency response to “secure the crash site”, NATO stalwart, The Netherlands, are weighing up deploying NATO troops into the middle of this war zone. Such a move could easily cascade into something much worse should another bizarre “accident” occur, or some tragedy befalls Dutch troops inserted into the hot zone.
Russian President Vladimir Putin has responded with strong words of condemnation, stating, “No matter what our Western counterparts tell us, we can see what’s going on. As it stands, NATO is blatantly building up its forces in Eastern Europe, including the Black Sea and the Baltic Sea areas. Its operational and combat training activities are gaining in scale.”
While the US push Kiev eastwards to fight Washington’s proxy war against Russia, the political and financial situation in Kiev is rapidly falling apart.
On Thursday July 24th, Victoria Nuland’s hand-picked coalition leader following a US-backed violent military coup back in February, Prime Minister of Ukraine Arseniy ‘Yatz’ Yatsenyuk (photo, left) announced his resignation in connection with the collapse of a Washington-designed coalition and parliament blocking government initiatives.
Watch as a fist fight break out this week between Washington’s new Neofascist partners during a Parliament session in Kiev:
His resignation indicates that ‘Yatz’ may be falling out of favor with central planning in Washington, and a sign of chaos still to come in the halls of Kiev’s Parliament.
Made-up ‘Evidence’ From Washington and Kiev
The talking point shift by the US media on Tuesday July 22nd was an obvious reaction to the Russian data dump. US media are now airing Washington DC’s revised conspiracy theories. Theory 1) “The rebels shot MH17 down by mistake”, and Theory 2) “Russia is responsible for creating the conditions for this tragedy”.
In reality, no evidence actually exists to date, other than anecdotal, that the rebels in the east possess any ‘BUK’ surface-to-air missile systems (see Washington and Kiev’s ‘BUK’ Missile Evidence Debunked’, below).
Close observers of Washington DC’s media blitz can only be left with a feeling of embarrassment, as the US State Department still clings to some semblance of continuity in the face of a total PR meltdown. As late as July 22nd, the US State Department was still attempting to pass-off its ‘evidence’ from social media (Twitter and YouTube), and backed-up by what it claims is “common sense”, that “clearly indicates Ukrainian militia shot down MH17″.
Since the incident on July 17th, the Kiev regime and US State Department have built their case against Rebels in eastern Ukraine and Moscow, and even Vladimir Putin himself, on the following items, which have all been thoroughly discredited by now:
1. The audio “tapes” issued by Kiev
2. A video and photos of BUK missile batteries issued by Kiev (of their own BUK missile batteries)
3. Claims by Kiev and supported by the West, that Ukraine had “no military aircraft in the air” at the time of the crash of the MH17 plane.
On July 22nd, the Ukrainian President Petro Poroshenko (photo, left) was forced to change Kiev’s story – a damage-control exercise to the overwhelming evidence against Ukraine. He has since reversed this position.
Suchan explains the western political media machine and its all-out effort to cast Russia and Putin as international pariahs over the incident:
“What has been thus established is that Ukraine, as well as the US, the EU, NATO, and other Western countries, have been systematically and grossly lying about evidence pertaining to the tragedy of MH17, thus willfully – and bluntly, abusing the tragedy and the demise of the victims and the suffering of their families for perverse political goals related to NATO expansionism and anti-Russian hysteria, and ‘Russophobia’, in order to support an openly fascist regime in Kiev, whose objective is the deliberate destruction of civilians and civilian infrastructure in east Ukraine.”
“The smearing campaign has also been used to demonize and criminalize anti-fascism and its resistance to a fascist dictatorship in Kiev, enrolled by Ukraine’s criminal oligarchs.”
Washington and Kiev’s ‘BUK’ Missile Evidence Debunked
Immediately after the MH17 crash event on July 17th, the Ukrainian government in Kiev quickly uploaded a brief YouTube video it purported to be ‘evidence’ of “a ‘BUK’ missile system being moved” out of a rebel-held area near Donetsk. US State Department officials, and every US media outlet, led by CNN, FOX, ABC, NBC and CBS, along with major US talk radio hosts like Sean Hannity, immediately jumped on this 5 second YouTube video claiming it was, “Irrefutable proof that a Russian-made BUK missile system was being moved away after it shot down MH17″. That talking point began to cascade from media, and into public chatter. It seemed their job was all but done.
Rupert Murdoch’s News Corporation newspaper , The Sun, always ready to take any pro-war line to the extreme, led the ‘conflict pornography’ on news stands, intentionally inciting fear and jingoism, doing what it always does: nudge British working class readers in a predetermined direction and fuse public opinion among differing classes on divisive international issues. No surprise then, as The Sun ran, “Putin’s Missile” as its headline the next morning. Similar covers and headlines were cloned across US and British media. Within hours of the news breaking – and despite this blanket coverage, not one of these newspapers or TV broadcasters offered any real evidence outside of anecdotal and wild speculation and conjectural theories.
Once again, we’ve witnessed the world’s most powerful, highly coordinated and synchronized propaganda machine. Once it’s set in motion, most western consumers are helpless to fend off its relentless repeating and universal coverage across hundreds of media outlets owned in most part by 5 US, and 2 British corporations.
A similar attempt was made by Washington and London last September, when US Secretary of State John Kerry, along with then British Foreign Secretary William Hague, presented their now infamous claim of ‘open source evidence’ (YouTube videos) used to assign blame to the Syrian government for a chemical weapons attack against its own people. Many of the photos and videos were later proven to be faked and staged, and ‘the gas’ was made in Britain, and that ‘chemical attack’ was in fact staged by Syrian insurgents still being supported by the US-British-Saudi-Qatari Axis.
Verdict: Active Cover-Up Taking Place
Washington’s initial ‘BUK Missile’ social media evidence seems to be rapidly heading down the same memory hole as its Syria predecessor, and soon, it will not be mentioned again by any US official. The speed at which it was released after the crash, and the fact that falsified audio, video, and photos have been intentionally released by the Kiev government in the wake of such a tragedy, demonstrates a clear motive to deceive the public about who is to blame for the MH17 event – using falsified evidence to build a case against ‘pro-Russian separatists’ and Moscow, and even Russian President Vladimir Putin himself.
What is obvious, but not being discussed in mainstream western circles is that, as with Syria since 2011, Washington and its NATO allies have been openly conducting a proxy war in the Ukraine, and have managed to control media coverage in the west so that what clearly a Civil War in the Ukraine – is being cynically, and very wrongly labeled as an “anti-terror operation”. On a daily basis, the Ukrainian Military are carrying out attacks on civilian targets all over Eastern Ukraine, killing thousands of its own innocent citizens with the full logistical and financial backing of the Washington and NATO. In Syria, the tables are reversed, where the government in Damascus is clearly fighting against known al Qaeda and ISIS-linked foreign terrorists brigades, as Washington and London politicians and media insist on calling it a ‘civil war’. Both are classic proxy wars being waged by the NATO block of nations.
More Falsified and Sloppy ‘Evidence’ Supplied by SBU Defense Ministry in Kiev
Let’s start with the famous 5 second YouTube video released by Kiev and lauded by Washington, CNN, ABC, FOX et all, of a BUK missile battery being moved, we were told, secretly by rebels out of the area after the plane crash.
Not only does signage clearly visible in the video place this truck in Krasnoarmeysk – a town which has been in control of the Ukrainian Army since May 11th. Here is one early news release of the now discredited video.
In the absence of any real evidence or data, it’s worth asking who has paid large sums of money to create a 3-D computer animation sequences, of what the US/Kiev governments claim look place?
In addition to falsified YouTube video, Kiev also published falsified photos of an alleged BUK missile system on July 19th. Kiev’s Security Service (SBU) published photos online it claimed showed ‘Russia’ secretly withdrawing a BUK-M system from the Ukraine civil war zone, but shortly after publishing this article the photos in question were deleted. The photo released by Kiev was actually an image taken of its own military’s BUK missiles – ironically, our readers will find that Kiev showing photos of its own systems is much closer to the real story than we previously thought.
Somewhat haphazardly, Kiev’s SBU, which is overseen by the new CIA station occupying the top floor in the same building in Kiev, released two more videos meant to assign blame