MSC Flaminia
MSC Flaminia
Main page
694847

MSC Flaminia

logo
Community Hub0 subscribers
Read side by side
MSC Flaminia
View on Wikipedia
from Wikipedia

History
NameMSC Flaminia
OwnerConti Reederei
OperatorNSB Niederelbe
Port of registryHamburg, Germany
BuilderDaewoo Shipbuilding & Marine Engineering
Yard number4073[1]
Laid down5 March 2001
Launched26 May 2001
Sponsored byFlaminia Manghina[citation needed]
Completed20 August 2001
In service2001–2012; 2014–
Identification
StatusIn service
Notescurrent ship name: CMA CGM San Francisco
General characteristics
TypeContainer ship
Tonnage
  • 75,590 GT
  • 42,233 NT
  • 85,823 DWT
Length299.99 m (984 ft 3 in)
Beam40 m (131 ft 3 in)
Draft14.5 m (47 ft 7 in)
Depth24.2 m (79 ft 5 in)
Installed powerHyundai-MAN B&W 10K98 MC-C (57,100 kW)
Propulsion
  • Single shaft, fixed-pitch propeller
  • Bow thruster (1,500 kW)
Speed25 knots (46 km/h; 29 mph)
Capacity6,750 TEU
Crew23

MSC Flaminia is a German container ship which caught fire on 14 July 2012, claiming three lives (only two of which could be recovered) and forcing the crew to abandon ship in the middle of the Atlantic Ocean. After the fire had been brought under control, the stricken container ship was towed to Europe and arrived at Wilhelmshaven, Germany, on 9 September 2012. In March 2013, she departed Wilhelmshaven for Mangalia, Romania for repairs which were finished in July 2014. The ship is currently sailing under the name CMA CGM San Francisco.

Description

[edit]

MSC Flaminia is a post-Panamax container ship with a capacity of 6,750 TEUs and deadweight tonnage of 85,823 tons. She is nearly 300 metres (984 ft 3 in) long and 40 metres (131 ft 3 in) wide, and fully laden draws 14.5 metres (47 ft 7 in) of water. Like most large container ships, MSC Flaminia is powered by a single low-speed two-stroke crosshead diesel engine coupled to a fixed-pitch propeller. Her main engine, a 10-cylinder Hyundai-MAN B&W 10K98 MC-C, is rated at 57,100 kW (76,600 hp) and is capable of propelling the ship at 25 knots (46 km/h; 29 mph).[1] She also has a 1,500 kW bow thruster for manoeuvering at ports. Power for onboard consumers and reefer containers is generated by four Wärtsilä 6R32LND auxiliary generators.[2]

History

[edit]

MSC Flaminia was built in 2001 by South Korean shipbuilder Daewoo Shipbuilding & Marine Engineering, commonly abbreviated as DSME. Laid down on 5 March 2001 and launched on 26 May, she was completed and entered service on 20 August 2001 with Hamburg, Germany, as her port of registry.[1][2] The ship, owned by Conti Reederei and managed by NSB Niederelbe, has been chartered to Mediterranean Shipping Company (MSC) for 16 years.[3]

2012 fire

[edit]

On 14 July 2012,[4] a fire in hold 4 caused an explosion aboard MSC Flaminia while the ship was underway from Charleston, South Carolina US to Antwerp, Belgium, forcing the crew to abandon the ship some 1,000 nautical miles (1,900 km; 1,200 mi) from nearest land in the middle of the Atlantic Ocean.[5] Her Majesty's Coastguard received a distress signal at 10:07 (UTC (GMT)) and broadcast an alert to all vessels in the area.[6] DS Crown, a German-owned, Bahamas-flagged oil tanker en route from Halifax, Nova Scotia, Canada to Falmouth, Cornwall, United Kingdom,[5] was the first to arrive at the scene and rescue 22 crew members and two passengers from a lifeboat and a liferaft. One crewman remains missing and is presumed dead. The ship's first officer died on DS Crown shortly after being taken aboard from burns he had sustained while fighting the fire.[3][6][7] On 8 October, another seriously injured crew member of MSC Flaminia died in a specialist hospital for burn wounds in Portugal.[8] A number of containers were also lost overboard.[9]

The damaged MSC Flaminia at JadeWeserPort in Wilhelmshaven, Germany.

After the crew and passengers had abandoned the ship, MSC Flaminia was left drifting in mid-Atlantic. Dutch salvage company Smit International signed a salvage contract for the stricken vessel, but the extent of the fire was not known until the first salvage tug, Fairmount Expedition, arrived at the scene on 17 July. According to the first reports, the fire was still burning in holds 4, 5 and 6, and the ship had developed a list of about 8.5 degrees as a result of the firefighting operations, but the engine room, superstructure and aftship were not seriously damaged. A second explosion occurred on the ship on 18 July, but the salvage efforts soon continued. The ship's own firefighting system was also started and the salvage personnel attempted to find the missing crewman. On 20 July, Fairmount Expedition began to tow MSC Flaminia towards Europe while Anglian Sovereign, another salvage tug with specialized firefighting equipment, continued to cool down the fire. On 24 July, it was announced that the fire on board MSC Flaminia was under control and an aerial high definition video, recorded by a helicopter on 26 July,[10] showed the damage to the ship and its containers. By 29 July, the ship had arrived within 100 nautical miles (190 km; 120 mi) of the British coast. However, the deteriorating weather prevented the salvage crew from entering the ship, then listing at 10 degrees, on 31 July and she was moved away from the coast. Although the fires had been put out in holds 4, 5 and 6, temperatures in hold 7 were still rising. On 13 August, the salvage efforts restarted but, as no European country had given the ship a permission to enter its coastal waters, MSC Flaminia remained at her waiting position approximately 240 nautical miles (440 km; 280 mi) offshore. In addition to extinguishing individual containers, the salvage crew had pumped water from the cargo holds to stabilize the vessel, reducing the list to around 2.5 degrees.[8]

On 20 August 2012, five weeks after the crew abandoned the vessel, MSC Flaminia was given permission to enter German waters. After the ship had been towed to a sheltered anchorage off Land's End, a team of experts entered the vessel and identified the possible hazards on board. After the ship had been deemed safe, she was allowed to pass through the English Channel and proceed to Heligoland and later to JadeWeserPort in Wilhelmshaven, Germany, where she arrived on 9 September 2012.[11][12]

The fire aboard the MSC Flaminia was due to the auto-polymerization and ignition of the chemical DVB80 (Divinylbenzene 80%), which is used in making plastic resins.[13][14] The chemical was stored incorrectly while on shore, and loaded incorrectly on the vessel for the transatlantic crossing. The chemical was incorrectly loaded because the container was labelled as a marine toxin rather than an explosive hazard. Marine toxins are stored in the cargo hold to reduce the risk of spills in the ocean. Explosive hazards are stored on deck to reduce risk of structure damage due to explosions.[13]

In 2018, the United States District Court for the Southern District of New York found MSC was not liable for the loss. MSC was found to be following industry practices given the information they possessed on the cargo. The court said that two parties bear the responsibility for the incident, those being Deltech, and Stolt Tank Containers B.V. The New York court found Deltech 55% strictly liable and Stolt Tank Containers 45% strictly liable for the fire and explosion.[13][14] The vessel owner Conti and its operator NSB were also cleared from responsibility for losses as the vessel was in sound condition when provided and the crew was properly trained.[13]

The fire onboard MSC Flaminia has again raised concerns about misdeclared cargo. Containers containing explosive or flammable materials are normally carried on the decks for safety, but if the cargo manifest is incorrect or falsified, they might be stowed inside the cargo holds where they create a potential hazard. The shipping company has confirmed that, according to the cargo manifest, the ship was not carrying calcium hypochlorite, a chemical compound responsible for several container ship fires in the 1990s, in any of the 2,876 containers on board the ship.[3][5][15] Furthermore, the reluctance of any country to give permission for the ship to enter its coastal areas raised concerns about the vessel sinking or being intentionally scuttled in deep water.[16] A similar situation resulted in a major oil spill in 2002 when the oil tanker Prestige broke in two and sank after French, Portuguese and Spanish governments refused to allow the ship to dock in their ports.[citation needed]

In March 2013, MSC Flaminia departed Wilhelmshave for Mangalia, Romania, where she underwent extensive repairs.[17] The repairs concluded with sea trials in July 2014.[citation needed]

See also

[edit]
  • Hyundai Fortune, a 5,551 TEU container ship that was seriously damaged in a similar fire in 2006.

References

[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

MSC Flaminia

View on Grokipedia
from Grokipedia
MSC Flaminia was a German-registered container ship chartered by Mediterranean Shipping Company (MSC) that suffered a catastrophic explosion and fire on 14 July 2012 while en route from the United States to Europe across the North Atlantic Ocean, resulting in three crew fatalities, two severe injuries, and the abandonment of the vessel.[1][2][3] The 300-meter-long ship, with a capacity of approximately 6,700 twenty-foot equivalent units (TEU), was owned by Conti 11 Container Schiffahrts-GmbH & Co. KG and technically managed by NSB Niederelbe GmbH & Co. KG at the time of the incident.[1][3][4] The disaster originated from a runaway chemical reaction in containers holding divinylbenzene (DVB), a hazardous monomer that underwent auto-polymerization due to excessive heat exposure during pre-loading storage in warm conditions and proximity to heated bunker fuel tanks on board.[2] Smoke was first detected in hold 4 at approximately 05:42 UTC, prompting the crew to activate CO2 suppression systems, but this inadvertently fueled an explosion that ripped open the deck, ignited widespread fires, and forced the 25 surviving crew members to evacuate into lifeboats before being rescued by nearby vessels.[1][2][3][5] The blaze, which burned for days and reached temperatures exceeding 1,000°C in some areas, destroyed most cargo aft of hold 4, caused the ship to list 11° from water ingress and cargo shifts, and led to an unknown number of containers—potentially including 150 with hazardous materials—being lost overboard, though no major oil spill occurred.[1][3] Salvage efforts, coordinated under a Lloyd's Open Form agreement by SMIT Salvage and involving multiple tugs including the Fairmount Expedition, extinguished the fires through boundary cooling and towed the smoldering vessel to Wilhelmshaven, Germany, arriving on 9 September 2012 after a tense passage through the English Channel.[1][3] Subsequent investigations cleared the shipowner, technical operator, and charterer of liability, attributing fault primarily to the cargo shippers—Deltech Europe for improper handling of the DVB and Stolt Tank Containers for inadequate stowage warnings—with court rulings assigning 55% and 45% responsibility, respectively, in a U.S. District Court decision.[2][4] The protracted litigation, involving general average claims and limitation of liability under the 1976 Convention, culminated in a $290 million settlement in 2024 paid by Stolt-Nielsen to resolve outstanding compensation for damages exceeding $250 million; a UK Supreme Court ruling on 9 April 2025 confirmed that charterers could limit liability to shipowners under the Convention.[2][6][7] The vessel was repaired and returned to service under MSC, renamed CMA CGM San Francisco in 2021, and as of 2025 continues operating under CMA CGM, highlighting ongoing challenges in hazardous cargo transport regulations.[8][9]

Design and Construction

Building and Launch

The MSC Flaminia was constructed by Daewoo Shipbuilding & Marine Engineering at their Okpo shipyard in Geoje, South Korea, under yard number 4073.[10][11] The keel was laid down on 5 March 2001, followed by the launch on 26 May 2001, and the vessel was delivered on 20 August 2001.[10] Upon delivery, the ship was owned by Conti 11 Container Schiffahrts-GmbH & Co. KG, a subsidiary of the German shipping company Conti Reederei, and operated by NSB Niederelbe Schiffahrts GmbH & Co. KG.[12][11] She entered service under her original name, MSC Flaminia, and was registered under the German flag in Hamburg.[8][11]

Technical Specifications

The MSC Flaminia is a post-Panamax container ship designed for efficient transoceanic cargo transport.[8] Key physical dimensions include an overall length of 299.99 meters, a beam of 40 meters, a maximum draft of 14.5 meters, and a molded depth of 24.2 meters.[8][5]
SpecificationValue
Gross Tonnage (GT)75,590
Net Tonnage (NT)42,233
Deadweight Tonnage (DWT)85,823
These tonnages reflect the vessel's capacity to handle substantial cargo loads while complying with international maritime standards.[5][8] The ship has a container capacity of 6,732 twenty-foot equivalent units (TEU), enabling it to transport a diverse range of standardized containers across global routes.[5] Propulsion is provided by a single Hyundai-MAN B&W 10K98MC-C low-speed two-stroke diesel engine rated at 57,100 kW, driving a fixed-pitch single propeller to achieve a maximum speed of 25.6 knots.[8][5] Accommodations are designed for a crew of 23 members, supporting operational needs during extended voyages.[13] Additional features include a double-bottom hull with continuous wing tanks for enhanced structural integrity and stability, along with specialized systems for container stacking and lashing to secure cargo against dynamic sea conditions.[5][8]

Service History

Initial Operations

The MSC Flaminia was delivered by Daewoo Shipbuilding & Marine Engineering on August 20, 2001, and entered service shortly thereafter under a time charter to Mediterranean Shipping Company (MSC) for transatlantic and European container routes.[10][14] The vessel, with a capacity of 6,750 TEU, was owned by Conti 11 Container Schiffahrts-GmbH & Co. KG and technically managed by NSB Niederelbe GmbH & Co. KG from the outset.[15][5] This time charter, initially agreed in November 2000 on a New York Produce Exchange form and later extended, placed the ship under MSC's commercial control while NSB Niederelbe handled operations.[16] The charter arrangement continued without significant changes until at least 2009, when it was reaffirmed for ongoing service.[17] During its initial decade, the MSC Flaminia engaged in routine container transport, primarily linking Western European ports such as Antwerp with U.S. East Coast facilities like Charleston, South Carolina, as part of regular liner services; occasional voyages extended to North American and Asian routes to support broader trade demands.[5] No major incidents marred this period of uneventful operations.[18] The ship flew the German flag with Hamburg as its port of registry throughout these early years, ensuring compliance with international maritime standards under German oversight.[5]

2012 Fire and Abandonment

The MSC Flaminia departed from Charleston, South Carolina, on July 8, 2012, carrying 2,876 containers loaded with general cargo, including hazardous materials, on a voyage bound for Antwerp, Belgium, with scheduled calls at Felixstowe, United Kingdom, and Bremerhaven, Germany.[5][13] On July 14, 2012, approximately 1,000 nautical miles west of Brest, France, in the North Atlantic Ocean at position 48°13.8'N 027°57.9'W, smoke was detected emanating from cargo hold No. 4 at around 05:42 UTC.[5] The general alarm was sounded at 05:50 UTC, and the crew initiated firefighting measures, including discharging carbon dioxide into the hold at 06:42 UTC and preparing water hoses for boundary cooling by 07:50 UTC. An explosion occurred in hold No. 4 at 08:04 UTC, severely damaging the vessel's structure, causing it to list, and spreading fire to adjacent holds No. 5 and No. 6; the blaze intensified rapidly due to the combustible nature of the cargo, including plastics and chemicals.[5] The fire was caused by the auto-polymerization of divinylbenzene (DVB80), a self-reactive substance, within three tank containers that had been misdeclared as non-hazardous Class 9 marine pollutants rather than the correct Class 4.1; these containers, loaded with DVB80, originated from Deltech Corporation in the United States and were shipped by Stolt Tank Containers B.V.[5][19] The improper declaration led to stowage under deck in hold No. 4 near potential heat sources, allowing the chemical reaction to build heat and pressure unchecked until it ignited, triggering the explosion.[19] The 25 persons on board, consisting of 23 crew members and 2 passengers, lacking adequate protective equipment and facing ineffective CO₂ suppression due to system limitations and the fire's intensity, battled the blaze for several hours but could not contain it amid the vessel's increasing instability and risk of further explosions.[5] The master ordered abandonment at approximately 10:00 UTC on July 14, with the 22 survivors (20 crew members and 2 passengers) evacuating in the starboard lifeboat and a life raft after the port lifeboat was obstructed by shifted containers and winch malfunctions; rescue was coordinated by the UK Maritime and Coastguard Agency's Falmouth MRCC, with involvement from French and US authorities, and the survivors were transferred to the nearby vessel DS Crown.[5][20] In the immediate aftermath, the MSC Flaminia was left adrift and burning, with fires persisting in the affected holds and a second explosion occurring on July 18; salvage teams from SMIT Salvage boarded on July 20 to resume firefighting using the ship's systems and external support from tugs such as the Fairmount Expedition and Anglian Sovereign.[5][1] The vessel was secured and taken in tow on July 23 after the fire was declared under control, beginning a slow transit toward European ports under salvage supervision.[5]

Repairs and Return to Service

Following the extinguishment of the fire, the MSC Flaminia was towed by salvage tugs to the port of Wilhelmshaven, Germany, where it arrived on 9 September 2012 for initial assessment and cargo discharge.[1] Although the extent of damage initially raised questions about whether the vessel would be declared a constructive total loss or repaired, the owners opted for extensive restoration rather than scrapping.[21] On 15 March 2013, the ship departed Wilhelmshaven under tow for the Daewoo Mangalia Heavy Industries shipyard in Romania, where a comprehensive refit commenced.[5] The repairs, which addressed severe structural damage from the fire and explosions, lasted over 16 months and concluded in July 2014, with costs for the vessel's restoration estimated at $21 million.[22] Key work included reinforcements to the cargo holds to restore integrity and near-original capacity, alongside upgrades to improve overall seaworthiness. Upon completion, the vessel was renamed CMA CGM San Francisco and transferred to the CMA CGM fleet, sailing under the Liberian flag; it re-entered commercial service in July 2014.[23] The vessel was later renamed back to MSC Flaminia and then to CMA CGM San Francisco again in October 2021.[24] The refit also incorporated efficiency enhancements, such as a new bulbous bow and propeller, aimed at reducing fuel consumption and emissions.[25] As of November 2025, CMA CGM San Francisco continues to operate as an active container ship on global trade routes, with recent voyages traversing the South Atlantic Ocean en route to ports in West Africa.[26]

Incident Aftermath

Casualties and Rescue Operations

The explosion and fire aboard the MSC Flaminia on 14 July 2012 resulted in three fatalities among the crew. Chief Officer Cezary Siuta, a Polish national, died from severe burns shortly after rescue, around 1400 UTC on the same day. Able-bodied seaman Ramon S. Parcon, a Filipino national, was reported missing immediately after the initial blast and presumed dead, with his body never recovered. A third crew member, also Filipino, died on 7 October 2012 in a specialist burn treatment hospital in Portugal from injuries sustained during initial firefighting efforts. Of the three deceased, two bodies were recovered.[27][28][29][5] In addition to the fatalities, several crew members suffered injuries, primarily burns of varying degrees, smoke inhalation, and physical trauma from the explosion and attempts to combat the fire. At least four individuals were seriously injured, including the bosun, an ordinary seaman with hand injuries, an oiler, and others whose clothing ignited due to the absence of adequate protective equipment during the response. Two crew members sustained minor injuries, while the remaining injured received prompt medical attention to address their conditions.[5][30] The 25 people on board—23 crew members (five Germans, three Poles, and 15 Filipinos) plus two passengers—abandoned the vessel shortly after the explosion at approximately 1100 UTC on 14 July 2012, launching a starboard lifeboat and a liferaft amid challenges such as blocked access to the port lifeboat and the need to lower the critically injured chief officer via raft. The chemical tanker DS Crown, responding to the ship's mayday calls broadcast via DSC and VHF, arrived on scene and rescued all 25 survivors by 1208 UTC, providing initial medical care including cooling burns with seawater due to limited first aid resources. Survivors were subsequently transferred to the nearby container ship MSC Stella for expedited transport toward land, while Portuguese rescue helicopters airlifted the most severely injured to hospitals in the Azores for advanced treatment; the remainder were conveyed to ports in Europe, including Southampton, UK, for further evaluation and repatriation.[5][31][20] The multinational rescue effort was coordinated through several maritime rescue coordination centers, including the UK's MRCC Falmouth, Portugal's MRCC Delgada and RCC Lajes, and support from the German Central Command for Maritime Emergencies (CCME), with additional involvement from French and other European authorities to ensure seamless handover and medical logistics. The operation highlighted effective international collaboration under the International Convention on Maritime Search and Rescue, facilitating the safe transport of survivors to medical facilities in the Azores and mainland Europe without further casualties post-evacuation.[5]

Legal Proceedings and Liability

Following the 2012 fire aboard the MSC Flaminia, multiple legal actions were initiated by the vessel's owner and operator, Conti 11 Container Schiffahrts-GmbH & Co. KG (Conti), against the time charterer, Mediterranean Shipping Company (MSC), as well as against cargo interests including Deltech Corporation (the cargo owner) and Stolt Tank Containers B.V. (the cargo packer).[32][33] These proceedings centered on claims for vessel repairs, lost income, and cargo damage, with total claims exceeding $280 million.[34] In the United States, consolidated cases under In re M/V MSC Flaminia were filed in the U.S. District Court for the Southern District of New York starting in 2012, involving cargo claimants seeking recovery from Conti, MSC, Deltech, and Stolt.[35] The court bifurcated the proceedings into phases, with Phase II addressing liability for cargo losses. On September 10, 2018, Judge Shira A. Scheindlin ruled that MSC and Conti were not liable, apportioning 55% fault to Deltech for improper cargo declaration and 45% to Stolt for faulty packing of the divinylbenzene containers that initiated the fire.[16][33] Damages were awarded to Conti and cargo interests accordingly, covering repair costs estimated at around $21 million plus additional expenses.[22] Parallel litigation in the UK addressed Conti's claims against MSC for breach of charterparty terms regarding dangerous cargo shipment. An arbitration panel in London awarded Conti approximately $200 million in damages in July 2021, but MSC sought to limit liability under the 1976 Convention on Limitation of Liability for Maritime Claims (LLMC).[36] The High Court and Court of Appeal initially ruled against limitation, but the UK Supreme Court overturned this on April 9, 2025, affirming MSC's right to limit liability to the LLMC tonnage-based fund, even for owner-originated claims.[37] In the US, appeals by Deltech and Stolt were dismissed by the Second Circuit in June 2023, upholding the district court's fault allocation.[38] Insurance coverage played a central role, with multiple providers including Steamship Mutual (Conti's P&I club) handling portions of the claims and settlements.[36] Cargo interests reached a $290 million settlement with Stolt-Nielsen in May 2024, resolving outstanding liabilities.[39] The incident prompted regulatory scrutiny, influencing updates to the International Maritime Dangerous Goods (IMDG) Code by the International Maritime Organization (IMO). Post-2012 amendments, including those in editions 37-14 and subsequent biennial revisions, enhanced requirements for hazardous cargo declaration, temperature control, and stowage to prevent polymerization risks in chemicals like divinylbenzene.[40][41] As of November 2025, no major new lawsuits have emerged, with the core disputes fully resolved through the 2025 Supreme Court decision and prior settlements.[42]

Environmental Impact

The fire aboard the MSC Flaminia resulted in the loss or jettisoning of several containers overboard, including those carrying hazardous materials such as divinylbenzene (DVB) and calcium hypochlorite, as well as general cargo like electronics.[5][43] These substances, classified under UN codes like 3082 for environmentally hazardous and flammable goods, posed risks of chemical release into the mid-Atlantic waters where the incident occurred.[5] Initial concerns focused on potential spills from damaged fuel systems and toxic cargo residues, including minor leaks from the vessel's heavy fuel oil bunkers and fears of widespread pollution if the ship sank with undeclared hazardous materials like DVB.[1][13] However, environmental assessments confirmed no large-scale oil or chemical spills, with aerial and maritime surveillance detecting only trace contamination from firefighting runoff.[44][5] Mitigation efforts included continuous monitoring by European agencies such as the European Maritime Safety Agency (EMSA) and the UK's Maritime and Coastguard Agency (MCA), which conducted risk analyses, surveillance flights, and on-scene coordination during the tow to Wilhelmshaven, Germany.[5] Debris and lost containers were recovered where possible en route and during unloading from September 2012 to March 2013, while approximately 35,000 tonnes of contaminated extinguishing water were pumped out and safely disposed of to prevent marine ecosystem harm.[5] No long-term damage to marine environments was reported following these measures.[44] The incident underscored risks associated with misdeclared hazardous cargo in container shipping, prompting enhanced guidelines on dangerous goods handling under the International Maritime Dangerous Goods (IMDG) Code and influencing EU operational protocols for ships in distress.[5][45] It also contributed to calls for SOLAS amendments on container fire safety, with IMO discussions citing the event as a key example for improved firefighting and stowage standards implemented between 2013 and 2015.[46][47] As of 2025, the repaired MSC Flaminia continues operations under MSC Mediterranean Shipping Company, with no ongoing environmental issues and compliance to current international green shipping standards, including reduced emissions protocols under IMO regulations.[36]

References

  1. MSC Flaminia - Cedre.fr
  2. https://www.maritime-executive.com/article/petchem-company-nvocc-found-liable-for-msc-flaminia-fire
  3. MSC Flaminia - SMIT Salvage
  4. MSC Mediterranean Shipping Company SA (Appellant) v Conti 11 ...
  5. “MSC FLAMINIA”: Supreme Court Clarifies Application of the ... - HFW
  6. MSC Flaminia - IMO 9225615 - scheepvaartwest
  7. Schiffsdaten - Ship-DB
  8. MSC Flaminia - Ships Nostalgia
  9. https://www.marineinsight.com/case-studies/details-on-the-container-ship-msc-flaminia-accident/
  10. [PDF] Fire and explosion on board the MSC FLAMINIA on 14 July 2012 in ...
  11. MSC FLAMINIA 2012 - Fortunes de mer
  12. [PDF] Stolt Tank Containers B.V. and others - Courts and Tribunals Judiciary
  13. Stolt-Nielsen Sets Aside $155M After Losing MSC Flaminia Appeal
  14. [PDF] MSC Mediterranean Shipping Company SA (Appellant) v Conti 11 ...
  15. MSC Mediterranean Shipping Company SA (Appellant) v Conti 11 ...
  16. Details on the Container Ship MSC Flaminia Accident - Marine Insight
  17. Petchem Company, NVOCC Found Liable for MSC Flaminia Fire
  18. Falmouth welcomes container ship blast crew survivors - BBC News
  19. Big box ship casualties pose extreme risks - Riviera Maritime Media
  20. MSC Losses Appeal to Limit $200M Liability from 2012 MSC ...
  21. Stolt-Nielsen to pay MSC US$290 million to settle MSC Flaminia claim
  22. Flaminia back in service as 'eco ship' | News - Motorship
  23. SAN FRANCISCO - Container Ship (IMO: 9225615, MMSI
  24. Sailor Cezary Siuta dies after blast on MSC Flaminia - BBC News
  25. MSC Flaminia Fire Timeline - Officer of the Watch
  26. MSC FLAMINIA Crew Member Passed Away (Germany)
  27. MSC Flaminia Crew Member Dies From Wounds Sustained in Blast
  28. A First-Hand Account of Tragedy and Heroism on Board the MSC ...
  29. “MSC FLAMINIA”: Supreme Court Clarifies Limitation of Liability for ...
  30. IN RE: M/V MSC FLAMINIA (2023) - FindLaw Caselaw
  31. The M/V MSC FLAMINIA – Explosion, Fire, General Average ...
  32. IN RE M/V MSC FLAMINIA, No. 1:2012cv08892 - Justia Law
  33. MSC Flaminia – The Final Word on Limitation - Steamship Mutual
  34. MSC Mediterranean Shipping Company SA (Appellant) v Conti 11 ...
  35. In re: M/V MSC Flaminia, No. 18-2974 (2d Cir. 2023) - Justia Law
  36. MSC FLAMINIA Incident Concludes with $290 Million Compensation ...
  37. TT Talk | Changing dangerous goods regulations - TT Club
  38. Fire-fighting techniques have proven inadequate to stop container ...
  39. MSC Flaminia in the Supreme Court
  40. Tracking Chemical Hazards on the High Seas | Insights & Events
  41. Fire-hit MSC Flaminia 'safe' to be towed - BBC News
  42. Lessons learned from the accident of MSC Flaminia: new guidelines ...
  43. IMO urged to amend fire safety regulations - FreightWaves
  44. Lessons learned from MSC Flaminia - safety4sea
User Avatar
No comments yet.