Classification
- Incident Type: Grounded
- Severity: Low
Vessel Details
| Field | Value |
|---|---|
| Vessel Name | MSC Clorinda |
| Vessel Type | Container |
| Flag State | |
| IMO Number | 9484429 |
| Gross Tonnage | |
| LOA (m) | |
| Capacity | 13,050 TEU |
Incident Details
| Field | Value |
|---|---|
| Date | 2017-01-04 |
| Location | Suez Canal, kilometer 145 |
| Coordinates | 30.6053, 32.3331 |
| Region | Egypt |
| Fatalities | |
| Injuries | |
| Missing | |
| Direct Damage | |
| Economic Damage |
Key facts
- MSC Clorinda grounded at kilometer 145 in the Suez Canal on 4 January 2017.
- The vessel was fourth in a northbound convoy of 27 vessels.
- The grounding detained the northbound convoy and 31 vessels in a southbound convoy.
- Canal tugs refloated MSC Clorinda at about 10:35 local time.
- Both convoys resumed transit after the vessel was refloated.
Narrative
On 4 January 2017, the containership MSC Clorinda grounded at kilometer 145 in the Suez Canal. gCaptain, citing the GAC shipping agency, reported that the vessel was fourth in a northbound convoy of 27 vessels. The report identified MSC Clorinda as a 13,050 TEU containership.
The grounding detained the northbound convoy and 31 vessels in a southbound convoy. Suez Canal tugs were deployed to refloat the vessel. GAC later reported that MSC Clorinda was successfully refloated at approximately 10:35 local time and that both convoys resumed transit.
The available reporting does not state the navigational cause of the grounding or identify any casualty, pollution, vessel damage, or financial loss. It also does not identify an investigating body or publish official findings.
Sequence of events
| Date/time | Event |
|---|---|
| 2017-01-04 | MSC Clorinda grounded at kilometer 145 while fourth in a northbound convoy. |
| 2017-01-04 | Canal traffic in both directions was detained while tugs attempted to refloat the vessel. |
| 2017-01-04 10:35 local | GAC reported that MSC Clorinda had been refloated and that both convoys resumed transit. |
Investigation
The available gCaptain report does not identify an investigating body or publish official findings. The navigational cause and any damage assessment remain unresolved.