Stay up to date with notifications from The Independent

Notifications can be managed in browser preferences.

Iran plane crash may have been ‘shootdown event’, aviation experts say

Ukraine initially said plane crash was result of technical failure, before retracting statement

Olivia Alabaster,Simon Calder,Oliver Carroll
Wednesday 08 January 2020 14:14 GMT
Comments
Iran plane crash: Footage shows Boeing 737 crashing just after take off in Tehran

Your support helps us to tell the story

From reproductive rights to climate change to Big Tech, The Independent is on the ground when the story is developing. Whether it's investigating the financials of Elon Musk's pro-Trump PAC or producing our latest documentary, 'The A Word', which shines a light on the American women fighting for reproductive rights, we know how important it is to parse out the facts from the messaging.

At such a critical moment in US history, we need reporters on the ground. Your donation allows us to keep sending journalists to speak to both sides of the story.

The Independent is trusted by Americans across the entire political spectrum. And unlike many other quality news outlets, we choose not to lock Americans out of our reporting and analysis with paywalls. We believe quality journalism should be available to everyone, paid for by those who can afford it.

Your support makes all the difference.

Doubts have been cast over Iranian assertions that a deadly Ukrainian plane crash near Tehran was the result of technical failures, with independent aviation operations experts saying a “shootdown” was the most likely explanation.

Iranian officials said technical issues were behind the Ukrainian International Airlines (UIA) crash, which happened shortly after take-off from Imam Khomeini International airport on Wednesday morning, killing all 176 people on board.

The Ukrainian embassy in Tehran initially echoed this stance, but later retracted its statement, and instead said it was for an official commission to determine the cause of the accident.

While some aviation experts said it was too early to speculate, the OPS group, an aviation risk-monitoring group, said: “We would recommend the starting assumption to be that this was a shootdown event, similar to MH17 – until there is clear evidence to the contrary,” highlighting photos of the crash site which they said “show obvious projectile holes in the fuselage and a wing section.”

UIA has also discounted the possibility of technical problems, insisting there was “nothing wrong” with the three-year-old Boeing 737-800, which had undergone a scheduled technical check only two days earlier.

“We guarantee the safety of our aircraft and the high qualification of our crews,” a spokesperson said.

Vadim Lukashevich, an independent Russian aviation expert, told The Independent that from evidence in the public domain, it was clear that there was some sort of fire on board, and that the plane broke up upon impact. The rest, he said, was “conjecture”.

“In any air accident, there are usually three factors: human, weather and mechanical. Here you can add a fourth – the political. We know that a few hours before the crash, Iran sent missiles over to US targets in Iraq. They were expecting a response by air. We know they were on full alert.”

It is too early to rule out an external strike, he said – even if Iranian claims that one of the engines caught fire turned out to be true.

“An engine fire does not exclude the possibility that it was caused by a missile strike,” he said. “The fact that Iran immediately discounted all explanations bar mechanical is suspicious.”

In light of the obvious political tensions in the area, it was a criminal error not to close off airspace to civil aviation, Mr Lukashevich added. “At a minimum, the Iranians tugged a tiger by his ear and didn’t run away.”

Iran has said it will not be handing over the plane’s black box recorder to US plane manufacturer Boeing.

Philip Baum, the editor of Aviation Security International magazine, said it was too early to speculate.

He told The Independent the incident was notable “given the fact it was in Iran and the timing, and if you associate two states with shootdowns, as victims, then Ukraine springs to mind purely because of MH17,” and Iran, given the 1988 US shooting down of an Iranian civilian plane.

But, he added, it could just be “a bizarre coincidence that it should happen at this moment of time”.

“I just think there is nothing to indicate that it was a shootdown, and if it was shot down then by whom?”

Zeev Sarig, the former head of Ben Gurion airport in Israel, said a technical failure could be behind the plane crash, or an explosive device on board.

Speaking to Russian news agency RIA, he said that while a full investigation was necessary, the two main possibilities were, “a bomb on board that runs on a timer or altitude monitor, exploding when the plane reaches a certain height” or “a technical malfunction about which we don’t know anything yet. Unfortunately from what I see that looks less likely.”

Qassem Biniaz, a spokesperson for Iran’s road and transportation ministry, said the pilot “lost control of the plane” after a fire broke out in one of its engines.

The aircraft is a predecessor to the Boeing 737 Max 8, which has been grounded for 10 months following the Lion Air crash in 2018 and the Ethiopian Airlines crash in 2019.

Faulty flight-control software on board those two Boeing 737 Max 8 airliners resulted in the planes nose-diving, leading to the deaths of 346 people.

Airline officials said most of the passengers were en route to the Ukrainian capital, Kiev, transiting through there to other destinations.

Three Britons were among those who died.

On Wednesday morning, Iranian missiles hit US military bases in Iraq, in response to last week’s targeted US killing of top Iranian general, Qassem Soleimani.

Join our commenting forum

Join thought-provoking conversations, follow other Independent readers and see their replies

Comments

Thank you for registering

Please refresh the page or navigate to another page on the site to be automatically logged inPlease refresh your browser to be logged in