Stay up to date with notifications from The Independent

Notifications can be managed in browser preferences.

Iran-UK tensions: Everything we know about the British ships seized in Strait of Hormuz

Stena Impero lost contact with parent company on Friday afternoon

Henry Austin
Friday 19 July 2019 20:49 EDT
Comments
Iranian authorities 'seize British oil tanker in Persian Gulf'

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.

Iran’s Islamic Revolutionary Guard seized two British oil tankers in the Strait of Hormuz over what it claimed were violations of international regulations.

Here is what we know so far.

At around 4pm UK time, the Stena Impero, was “was approached by unidentified small crafts and a helicopter during transit of the Strait, while the vessel was in international waters”, according to the tanker’s owners, Stena Bulk.

At the time of publication, the company said they had not been able to contact the crew, made up of Indian, Russian, Latvian and Filipino nationals.

Trackers showed the ship changing course and heading towards Iran.

There was no official statement from Iran about why the ship was seized but a port authority chief was quoted by the semi-official Tasmin news agency, as saying that it was “causing problems”. Unnamed sources were also quoted as saying that the ship was dumping residue.

The seizure appeared to take the British government by surprise. It said it was investigating.

Around an hour after the first ship was taken, a second tanker MV Mesdar was seized and was seen to veer some distance off-course towards the Iranian coast.

Describing the actions as “unacceptable”, Jeremy Hunt, the foreign secretary, convened a Cobra emergency committee of government ministers at Whitehall.

Speaking to reporters outside the White House, US President Donald Trump said America would be “working with the UK” and referenced reports that a second oil tanker may be involved.

“We will talk to the UK and we have no written agreement but we have an agreement. They’ve been a very great ally of ours.”

Bob Sanguinetti, of the UK Chamber of Shipping, also condemned the Revolutionary Guard’s move.

He said: “This incident represents an escalation. Whilst we call for measured response, it is also clear that further protection for merchant vessels must be forthcoming to ensure enhanced security to guarantee free flow of trade in the region.”

Around five hours after it changed direction, the MV Mesdar was allowed to continue its journey, it’s owner said, adding that it was boarded by armed guards. It did not state their nationality.

Support free-thinking journalism and attend Independent events

“All the crew are safe,” the company said in a statement.

After the Cobra meeting, a government spokeswoman said minsters were “deeply concerned about Iran’s unacceptable actions which represent a clear challenge to international freedom of navigation.”

She added: “We have advised UK shipping to stay out of the area for an interim period.”

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