Beirut explosions: Timeline of events

Reports suggest Lebanese authorities were aware of the dangerous stockpile since 2014

Zoe Tidman
Wednesday 05 August 2020 15:38
Comments
Aerial footage shows devastating impact of Beirut explosion

More than 100 people have died and around 4,000 have been injured after a huge explosion rocked Beirut, the capital of Lebanon.

The blast appeared to have been triggered by a fire that set off a cargo of ammonium nitrate, which is used in bombs and fertilisers, that had been stored at the port for years, though it was unclear what sparked the initial blaze.

The Lebanese president has said more than 2,700 tonnes of the highly explosive material was being stored in the city’s port without safety measures.

Initial investigations indicate years of inaction and negligence over the storage of ammonium nitrate, an official source familiar with the findings has said.

Tuesday’s explosion was the most powerful ever suffered by Beirut, a city still scarred by civil war three decades ago and reeling from a deep financial crisis rooted in decades of corruption and economic mismanagement.


Here is what is understood to be the timeline of events leading up to the deadly blast:

September 2013

A ship sailing under a Moldovan flag docked in Beirut after suffering technical problems, according to Shiparrested.com, an industry network dealing with legal cases.

The Rhosus was heading from Georgia to Mozambique carrying 2,750 tonnes of ammonium nitrate, according to the network.

It said that, upon inspection, the vessel was forbidden from sailing and was abandoned by its owners shortly afterwards, leading to various creditors coming forward with legal claims.

“Owing to the risks associated with retaining the ammonium nitrate on board the vessel, the port authorities discharged the cargo onto the port’s warehouses,” it added.

2014

Ammonium nitrate was taken into storage at the port, according to comments made by the interior minister after the explosion to a Lebanese TV station.

The director of Lebanese customs at the time asked what should be done with the cargo, which had been deposited in a warehouse at Beirut’s port, documents shared online have shown, according to Al Jazeera.

Custom officials asked a judge for guidance over the ammonium nitrate several months later, the news channel reported.

(AP

2015

Documents seen by Reuters suggest customs asked for help over the cargo this year - as well as the year before.

2016

Lebanese customs asked the judiciary to ask the “concerned maritime agency” to re-export or approve the sale of the ammonium nitrate removed from the Rhosus, according to a document seen by Reuters.

2017

Another document revealed customs asked the same thing from the judiciary this year.

After the blast happened, Badri Daher, the current director general of Lebanese customs, revealed customs had sent a total of six documents to the judiciary in the past, warning the material posed a danger.

“We requested that it be re-exported but that did not happen. We leave it to the experts and those concerned to determine why,” he told broadcaster LBCI.

Early 2020

A team inspected the ammonium nitrate being held in the warehouse, and warned it would “blow up all of Beirut” if it was not moved, according to a source close to a port employee.

4 August 2020

Two massive blasts at Beirut’s port devastate the capital, killing scores of people and injuring thousands.

It triggered fires, overturned cars and blew out windows and doors across the city.

5 August 2020

Rescue workers searched for survivors under the rubble.

The known death toll rose to 100, according to Lebanon’s Red Cross.

Additional reporting by agencies

Register for free to continue reading

Registration is a free and easy way to support our truly independent journalism

By registering, you will also enjoy limited access to Premium articles, exclusive newsletters, commenting, and virtual events with our leading journalists

Please enter a valid email
Please enter a valid email
Must be at least 6 characters, include an upper and lower case character and a number
Must be at least 6 characters, include an upper and lower case character and a number
Must be at least 6 characters, include an upper and lower case character and a number
Please enter your first name
Special characters aren’t allowed
Please enter a name between 1 and 40 characters
Please enter your last name
Special characters aren’t allowed
Please enter a name between 1 and 40 characters
You must be over 18 years old to register
You must be over 18 years old to register
Opt-out-policy
You can opt-out at any time by signing in to your account to manage your preferences. Each email has a link to unsubscribe.

By clicking ‘Create my account’ you confirm that your data has been entered correctly and you have read and agree to our Terms of use, Cookie policy and Privacy notice.

This site is protected by reCAPTCHA and the Google Privacy policy and Terms of service apply.

Already have an account? sign in

By clicking ‘Register’ you confirm that your data has been entered correctly and you have read and agree to our Terms of use, Cookie policy and Privacy notice.

This site is protected by reCAPTCHA and the Google Privacy policy and Terms of service apply.

Register for free to continue reading

Registration is a free and easy way to support our truly independent journalism

By registering, you will also enjoy limited access to Premium articles, exclusive newsletters, commenting, and virtual events with our leading journalists

Already have an account? sign in

By clicking ‘Register’ you confirm that your data has been entered correctly and you have read and agree to our Terms of use, Cookie policy and Privacy notice.

This site is protected by reCAPTCHA and the Google Privacy policy and Terms of service apply.

Join our new 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