Skip to main content

Accidents

CSCL Jupiter collision in Vietnam (2019)

On the evening of 22 August 2019, COSCO Shipping Lines reported that CSCL Jupiter 063W had a collision at “CAPMEP TCTT” in Vietnam. The Vietnam Seaports Association identifies TCTT as Tan Cang–Cai Mep Thi Vai Terminal. COSCO's notice does not state the vessels' movements or name another vessel. Contemporary VesselFinder reporting described a collision with another ship but likewise did not identify it. COSCO reported damage to CSCL Jupiter without describing its nature or extent. (COSCO notice, 26 August 2019; VesselFinder, 27 August 2019.)

Classification

  • Incident Type: Collision
  • Severity: Medium
  • Severity basis: COSCO forecast about a one-week schedule delay for temporary repairs; actual delay was not established.

Vessel Details

FieldValue
Vessel NameCSCL Jupiter
Vessel TypeContainer
Flag State
IMO Number9467263
Gross Tonnage
LOA (m)366
Other vesselNot identified in the available account

Incident Details

FieldValue
Date2019-08-22
LocationCai Mep Thi Vai Terminal (TCTT), Vietnam
RegionOther
Fatalities0
Injuries0
Missing
Direct Damage
Economic Damage

Key facts

  • COSCO Shipping Lines reported that CSCL Jupiter had a collision at TCTT in Vietnam on the evening of 22 August 2019; its notice does not state either vessel's motion or identify another vessel.
  • The operator said CSCL Jupiter was damaged but did not describe the damage. Contemporary VesselFinder reporting described another ship but did not identify it.
  • COSCO reported no casualties, marine pollution, or damage to loaded cargo.
  • The operator expected a delay of about one week for temporary repairs; this was a forecast, and the notice did not report actual repair completion or final delay.

Narrative

On the evening of 22 August 2019, COSCO Shipping Lines reported that CSCL Jupiter 063W had a collision at “CAPMEP TCTT” in Vietnam. The Vietnam Seaports Association identifies TCTT as Tan Cang–Cai Mep Thi Vai Terminal. COSCO's notice does not state the vessels' movements or name another vessel. Contemporary VesselFinder reporting described a collision with another ship but likewise did not identify it. COSCO reported damage to CSCL Jupiter without describing its nature or extent. (COSCO notice, 26 August 2019; VesselFinder, 27 August 2019.)

COSCO said there were no casualties, no marine environmental pollution, and no damage to loaded cargo. It expected the vessel's schedule to be delayed by about a week for temporary repairs; this was a forecast, not a report of the final delay or repair completion. A later Cai Mep International Terminal account records that CSCL Jupiter discharged its cargo at CMIT on 7 September after an unspecified problem and departed for Singapore to continue repairs. That account does not explicitly connect the problem to the 22 August collision, so it does not establish the collision's repair timeline. No cause, maneuvering sequence, investigation body, or monetary damage estimate was included in COSCO's notice.

Investigation

COSCO's customer notice reports the collision and immediate operational impact but does not identify an investigation body or provide findings about cause. A 9 September 2019 CMIT report describes a later CSCL Jupiter cargo discharge and repair voyage after an unspecified problem; it does not expressly identify that problem as the collision damage, so the link remains unconfirmed.

References

Similar incidents