Suez Canal Blockage: EverGiven: Difference between revisions
Roxana (talk | contribs) m (Roxana moved page Suez Canal obstruction 2021 to Suez Canal Blockage: EverGiven) |
Roxana (talk | contribs) No edit summary |
||
| Line 15: | Line 15: | ||
On 28 March, at least 369 ships were queuing to pass through the canal, stranding an estimated US$9.6 billion worth of trade. On 29 March, Ever Given finally freed by 14 Egyptian, Dutch, and Italian tug boats at high tide to dislodge it. | On 28 March, at least 369 ships were queuing to pass through the canal, stranding an estimated US$9.6 billion worth of trade. On 29 March, Ever Given finally freed by 14 Egyptian, Dutch, and Italian tug boats at high tide to dislodge it. | ||
(Source: Wikipedia) | (Source: Wikipedia) | ||
|Involved Organisations=Hamburg Fire Department, Egyptian Authorities | |||
|SMCS usage problems solving=From the perspective of the Hamburg Fire Department, the consequences for the Port of Hamburg are to be assessed. The aim was to evaluate information in real time from Social Media. | |SMCS usage problems solving=From the perspective of the Hamburg Fire Department, the consequences for the Port of Hamburg are to be assessed. The aim was to evaluate information in real time from Social Media. | ||
|Use cases thematic=Collecting and Analysing Information from SMCS, Making Information Accessible | |Use cases thematic=Collecting and Analysing Information from SMCS, Making Information Accessible | ||
Revision as of 13:50, 23 October 2023
Last edited: 18 November 2023
Hazard:
Interrupted traffic routes, High economic damageYear:
2021Location:
Suez Canal, EgyptInvolved Organisations:
Hamburg Fire Department, Egyptian AuthoritiesPublishing Organisation
unknown
Category
Real-world
Theme
Social Media
Thematic
- Collecting and Analysing Information from SMCS
- Making Information Accessible
Disaster Management Phase
After, Before, During
Description
In March 2021, the Suez Canal was blocked for six days by the Ever Given, a container ship that had run aground in the canal. The 400-metre-long (1,300 ft), 224,000-ton, 20,000 TEU vessel was buffeted by strong winds on the morning of 23 March, and ended up wedged across the waterway with its bow and stern stuck in the canal banks, blocking all traffic until it could be freed. Egyptian authorities said that "technical or human errors" may have also been involved. The obstruction occurred south of the two-channel section of the canal, so there was no way around it for other ships. The blockage of one of the world's busiest trade routes significantly slowed down trade between Europe, Asia and the Middle East. On 28 March, at least 369 ships were queuing to pass through the canal, stranding an estimated US$9.6 billion worth of trade. On 29 March, Ever Given finally freed by 14 Egyptian, Dutch, and Italian tug boats at high tide to dislodge it.
(Source: Wikipedia)What was the overall goal of the Use Case?
From the perspective of the Hamburg Fire Department, the consequences for the Port of Hamburg are to be assessed. The aim was to evaluate information in real time from Social Media.What worked well and could be recommended to others?
Photos and information about the operation were pulled from social media more quickly than was possible using conventional fire service means and improved the situational picture.
The salvage operation provides information for the company's own operational planning in the event of accidents in the port. In particular, the timeline was tracked to estimate when the impact in Hamburg is likely to occur in future events. The use of special maps, estimating which ships will be „delayed“ are useful.