Busted: What Forced Iran to Change Plane Crash Story

Boeing 737s do not go down for no reason. And for Ukrainian International Airlines Flight 752, that reason is still being determined. However, it is looking more and more plausible that it was mistakenly shot down by Iran’s Islamic Republic’s air defense systems.

The flight is recorded to have taken off in Tehran on Wednesday, only to suddenly catch on fire and plummet to earth shortly afterward, killing 176 passengers. Initially, Iranian officials blamed the explosion and subsequent crash on a technical issue with the plane itself. And that is entirely possible. Aircraft like the Being 737 do malfunction and have problems that can be blamed on nothing but technology.

But we aren’t sure that is what really happened here.

Images have begun to surface of what appears to missile remains or debris found directly in the path of the downed plane. And as a result, Iran has suddenly changed its story.

Coincidence? I think not.

They now claim that the flight tried to turn back shortly after taking off, according to a report taken by Bloomberg on Thursday. However, this new information seems to contradict what was actually found in and around the wreckage.

And the images look pretty damning for Iran.

Images all over Iranian social media show what appears to be the remains of a Russian built Tor M-1 anti-aircraft missile, mainly the “tip.” This part contains guidance instruments and is located at the very front of the warhead. This one looks relatively intact, which is not uncommon for this type of missile.

The image below shows a complete and intact Tor surface-to-air missile system. See any similarities?

But even more evidence of possible Iranian interference was found at the crash site itself.

Large portions of the 737 appear to have sustained a significant amount of shrapnel damage, something that is consistent with a fragmenting missile or warhead. If a weapon was indeed shot at the plane, these incoming shrapnel pieces could have easily shredded the flight and caused it to set fire.

Pictures of the damage to the outside of the aircraft can be seen in the social media post below.

However, it is possible it was unintentionally shot down. Reports that Flight 752 being crashed came in just mere hours after Iran implemented missile strikes against US forces in Iraq. Therefore, their air defense crew would have been on high alert, waiting and watching for some type of retaliatory airstrike from the US.

It’s entirely possible that the trigger-happy anti-aircraft crew saw the Ukrainian flight, not nervous, and simply made a bad call to shoot it down, thinking it was a bomber or other American military plane.

Instead, it turned out to be a commercial jet carrying innocent lives.

Oops. I’d be willing to bet someone got fired for this rather costly mistake.

Naturally, Iran has not taken responsibility for the crash and devastating loss of life. They still maintain that the plane crashed due to no fault of theirs. And whether or not we believe that, there is no surefire way to prove it at this moment. Iran has refused to release or turn over the black box and the plane’s flight recorders to either America, Ukraine, or Boeing officials.

Furthermore, while the missile remains do look suspicious to be sure, there is no way of confirming that these pieces were actually found near or in the path of the wreckage. The images don’t give much detail as to where, when, or how the debris got there. The only thing the photos can actually prove is that it is, in fact, part of a Tor warhead.

However, the images have obviously hit close enough to home that Iranian officials have decided to change their story. And that alone creates plenty of suspicions. The refusal to release the black box only adds more. If, in fact, it was an entirely accidental crash caused by a technical issue, why wouldn’t they just release the flight recorders? Boeing, at the very least, has a rightful claim to know what went wrong with their plane, right?

Now, it just looks as though they are hiding something.