It's July 14, 2012. Global media circulate photos of a burning container ship en route from New Orleans to Antwerp. Reports of casualties emerge. It's the MSC Flaminia, two weeks into its voyage. It will be one of the most tragic sea journeys in recent years.
At 5:42 AM, smoke alarms blare on the MSC Flaminia. The crew immediately initiates emergency procedures, suspecting a conventional fire. The chief officer activates the fire suppression system three times, releasing carbon dioxide into the cargo hold, as per procedure.
However, the system fails to stop the fire. Thick, white smoke begins to pour from the cargo hold. Seeing that the system is ineffective, the crew attempts to directly combat the threat. It is likely that while opening a hatch or introducing water hoses, the sailors' actions generate a spark. An explosion occurs.
In a split second, Cargo Hold No. 4 erupts in flames. There are casualties. The crew is evacuated. As the court would later determine, the crew's conduct was flawless — all procedures were followed and appropriate given their knowledge of the situation.
THE CARGO THAT SHOULD NOT HAVE WAITED
June 2012, New Orleans terminal. Three tank containers (ISO tanks) filled with 80% divinylbenzene — DVB80 for short — arrive at the quay. It's a monomer used in resin production. It has one dangerous characteristic: above approximately 29 degrees Celsius, it begins to spontaneously polymerize and generate heat. The warmer it gets, the faster it reacts. The faster it reacts, the hotter it gets. This process ultimately leads to an explosion.
The tanks sat at the terminal, in the open air, for ten days. In July in New Orleans, temperatures reach well over thirty degrees Celsius. They were loaded onto the ship on July 1st and placed in the cargo hold next to a heated cargo of other chemicals, close to heated fuel tanks.
The DVB manufacturer, American company Deltech, has safety procedures developed after previous auto-polymerization incidents. Among them: avoid shipping DVB from New Orleans during warm months.
The following reconstruction is based entirely on official court records from the United States Court of Appeals.
DANGEROUS CARGO AND SAFETY PROCEDURES
It all began at the chemical plants of Deltech Corporation in Baton Rouge, Louisiana. The company was preparing three large transport tanks filled with 80% divinylbenzene (DVB-80) for shipment to Europe.
DVB-80 is a chemical compound with specific and dangerous properties. It is extremely sensitive to heat. Under high temperatures, DVB-80 molecules become unstable and begin to rapidly combine in a polymerization process. The reaction is exothermic — it generates immense amounts of heat on its own.
If the ambient temperature is too high, a phenomenon known as "thermal runaway" occurs. Inside the sealed tank, pressure drastically increases, and white vapors released through safety valves form a flammable and explosive cloud.
To prevent this, Deltech used a special inhibitor (TBC additive) and ensured proper oxygenation of the liquid. Under normal transport conditions, these safeguards were entirely sufficient.
Deltech also had a rigorous safety protocol: during the summer months, DVB-80 shipments from the nearby, hot port of New Orleans were strictly forbidden. The goods were to be transported exclusively through the cooler port of Newark, New Jersey, which shortened transit time and protected against heat.
However, in June 2012, Deltech's safety system completely failed for two reasons.
Communication error. Due to an internal misunderstanding within Deltech's logistics department, the company — contrary to its own procedures — approved a summer shipment to Antwerp via the New Orleans Terminal (NOT).
Medical emergency. At a critical point in the preparations, a Deltech employee responsible for logistics and tank filling experienced a sudden health emergency.
This led to an organizational rush. To complete the task before the key logistics person's absence, the tanks were filled earlier and dispatched to the port on the same day.
The tankers arrived at the New Orleans terminal and — due to their premature departure from the factory — were left on the dock for 10 days. They stood in full sun, with temperatures reaching approximately 36°C. During this time, the liquid DVB-80 began to absorb heat, consuming oxygen and the protective inhibitor. Inside the containers, a slow, invisible autopolymerization process began.
INFORMATION THAT DID NOT REACH THE SHIP
Several entities were involved in the logistics process before the sea voyage:
Deltech — manufacturer;
Stolt — freight forwarder/NVOCC;
BDP International — documentation agent.
The information that the cargo had been exposed to the sun for 10 days and that this affected its parameters did not reach the shipowner. Four factors contributed to this.
1. The freight forwarder was aware of the tanks being filled earlier and received a Material Safety Data Sheet (MSDS) from Deltech with warnings about DVB-80's explosiveness when exposed to heat — but a system error prevented employees from entering this data into their database.
2. As a result, in the official Dangerous Goods Declarations (DGDs) — the most crucial shipping documents — the freight forwarder classified DVB-80 as a regular Class 9 material, and all warnings about heat were completely omitted.
3. The documentation company BDP overlooked the absence of an annotation prohibiting stowage near heat sources in the working versions of the bills of lading.
4. New Orleans Terminal filed the paper warnings from drivers into the archive, acting in accordance with a procedure that mandated relying solely on electronic instructions from the shipping line.
Consequently, on July 1, 2012, three heated ISO containers, which had been sitting in port for ten days prior, were loaded below deck on the MSC Flaminia into Cargo Hold No. 4 — right next to the ship's heated fuel tanks and heat-generating containers with other chemicals. The carrier and crew believed they were transporting routine, safe cargo.
WHERE THE CHAIN BROKE
The court identified three critical factors.
1. Premature loading into tanks. Stolt filled the DVB tanks earlier than necessary and sent them to the terminal, even though — as the court determined — it had reason to foresee that they would sit idle there for many days. For a substance sensitive to time and temperature, every day of delay poses a real risk.
2. Lack of effective warning about the condition of the specific shipment. The freight forwarder did not effectively convey information to the shipowner about the risk posed by this specific cargo in the tanks. It wasn't about the substance being generally dangerous. It was about these specific tanks already being heated.
3. Discrepancy between documents. Warnings and stowage instructions from the bill of lading were not consistently transferred to the carrier's bills of lading. The information was lost along the way.
The freight forwarder argued that since the shipowner, by the nature of its business, had general knowledge of DVB's sensitivity to heat, this absolved them of the obligation to issue a separate warning about these specific tanks. The court unequivocally rejected this, stating:
a carrier's general knowledge does not supersede the obligation to provide critical information about the condition of a specific shipment.
EXPLOSION
July 14, 2012. The MSC Flaminia sails across the Atlantic from New Orleans to Antwerp. On board are 2,876 containers, including 149 with hazardous cargo, along with a 23-person crew and two passengers. Early in the morning, alarms sound. Smoke rises from cargo hold number 4. The crew rushes to extinguish it.
The crew was international — Germans, Poles, and Filipinos. One of the three fatalities was a Polish officer.
The others were rescued by the tanker DS Crown, which was the first to arrive on the scene; the injured were taken by helicopter to the Azores.
The explosion occurred in cargo hold number 4, in one or more of the three DVB tanks. The fire spread throughout the ship. After the explosion and fire, the crew abandoned the vessel.
THE SHIP NO ONE WANTED TO ACCEPT
After being abandoned by the crew, the Flaminia did not sink. It drifted. The fire continued. Four days later, on July 18, another explosion occurred. The 300-meter container ship became a burning wreck in the middle of the Atlantic, with a plume of smoke visible to passing vessels.
On July 20, a salvage team boarded the ship and began towing it towards Europe. The fire was extinguished with seawater — approximately 30,000 tons of contaminated firefighting water accumulated in the holds. Putting out the fire turned out to be only half the problem. No European port wanted to accept the burning ship with chemicals on board.
For weeks, the Flaminia remained in a holding pattern, hundreds of miles offshore. Information about its exact cargo was fragmented — the full cargo manifest was only revealed by a journalist who published it. It was only five weeks after the crew abandoned the ship that Germany, the flag state, agreed to allow it into its waters.
A flotilla of tugboats from several countries towed the ship through the English Channel. On September 9, 2012, eight weeks after the fire broke out, the MSC Flaminia docked in Wilhelmshaven, Germany. Unloading and clearing debris, contaminated water, and damaged cargo took many months. The repaired ship returned to service in 2014, under a different name.
WHO'S WHO (BEFORE WE GO TO COURT)
To understand what happened next, we need to know the four key players. This is important because the name "MSC Flaminia" is misleading — it suggests the ship was owned by MSC.
Conti — a German company, the ship's owner.
MSC (MSC Mediterranean Shipping Company S.A.) — a Swiss container shipping line based in Geneva. It was not the owner. It chartered the vessel from Conti for many years, giving it its name and livery.
Deltech — an American DVB manufacturer. It produced the chemical, decided on its shipment from New Orleans, and arranged for its transport. In this story, it is the cargo shipper.
Stolt (Stolt Tank Containers / Stolt-Nielsen) — a container operator (NVOCC) who organized the transport of DVB: booked space on the vessel and was responsible for delivering the tanks to the port.
THREE COURTS, THREE QUESTIONS, THIRTEEN YEARS
After the disaster, the legal machinery was set in motion, operating for over a decade on three fronts simultaneously. Each front addressed a different question. This is key to understanding the complexity.
Front 1 — USA: who was at fault?
The owners of the damaged cargo sued everyone in New York. The court in 2018, and on appeal in 2023, ruled clearly: only Deltech (55%) and Stolt (45%) were at fault. Reason: they had full knowledge that DVB is heat-sensitive — yet they prepared it improperly and, crucially, failed to effectively warn the carrier. The vessel owner Conti, the vessel operator, and the carrier MSC were cleared of blame.
The most important sentence of this ruling: MSC is not liable because, although it had general knowledge that DVB can be heat-sensitive, it did not know that these specific tanks were already heated — that they were 'ticking time bombs'. General knowledge is not enough. What matters is the communication of specific, critical information at the right moment.
Front 2 — London: who pays whom for the vessel?
Conti, the owner of the damaged vessel, had no contract with Deltech or Stolt. It had a charter agreement with MSC. So it sued MSC — in arbitration in London, as stipulated by the charter. The tribunal in 2021 awarded Conti approximately 200 million dollars: for MSC having breached the charter by allowing dangerous cargo onto the vessel. In addition, there were specific costs: vessel repair amounted to an additional 21 million dollars, and Conti also incurred millions of euros in cleanup costs and fees to authorities in four countries for pollution prevention.
Front 3 — UK Supreme Court: can MSC limit the bill?
Burdened with 200 million, MSC resorted to an old instrument of maritime law: the 1976 Convention, which allows for limiting liability to an amount dependent on the vessel's tonnage. MSC sought to reduce this to approximately 28 million pounds. The case dragged on for years and in April 2025 reached the Supreme Court, which heard it despite the parties having already settled — because it deemed the matter too important for the entire market. Outcome: MSC could, in principle, limit its liability towards the shipowner, but not against most of Conti's claims.
HOW THE MONEY RETURNED TO ITS SOURCE
The chain of responsibility, though slow, worked its way through to the end.
A US court granted MSC and Conti full recourse against those found liable. Since Conti recovered its losses from MSC, MSC sued the freight forwarder and the manufacturer. In March 2024, after nearly twelve years, all parties — MSC, Conti, Stolt, and Deltech — entered into a single, multilateral, confidential settlement agreement concluding the entire case. According to industry reports, Stolt-Nielsen was to pay MSC up to approximately $290 million. The claims of the cargo owners themselves had been settled earlier by their insurers.
The Moral
In this text, we are not judging anyone – we are relying on court findings. However, this is an excellent case study of what modern logistics entails and the immense importance of planning, analysis, and prediction. Because the lack of one crucial piece of information led to one of the most tragic maritime disasters in recent years.
Dark Stories is a series based on real cases, judgments, and reports. The described event: fire and explosion on the MSC Flaminia, July 14, 2012, during a voyage from New Orleans to Antwerp. The crew was international (German, Polish, Filipino); one of the three fatalities was a Polish officer. We deliberately do not provide the names of the victims — families requested that crew members' data not be disclosed. Court cases: In re M/V MSC Flaminia (US District Court SDNY 2018; US Court of Appeals, 2nd Circuit, no. 18-2974, June 30, 2023) and MSC v Conti [2025] UKSC 14. Settlement amounts are cited from industry reports; some financial terms were covered by a confidential settlement from March 2024.
Our previous publications in the "Dark Stories" series:
1. https://insphera.webflow.io/blog/po-co-nam-fob-mroczne-historie
2. https://insphera.webflow.io/blog/naprawde-cif-mroczne-historie-2
SOURCES AND LINKS
Court and official documents
▪ UK Supreme Court Judgment [2025] UKSC 14 — full text — https://supremecourt.uk/cases/judgments/uksc-2023-0131
▪ England and Wales Court of Appeal Judgment [2023] EWCA Civ 1007 — https://www.bailii.org/ew/cases/EWCA/Civ/2023/1007.html
▪ US Court of Appeals Ruling, 2nd Circuit, In re M/V MSC Flaminia, No. 18-2974 (Justia) — https://law.justia.com/cases/federal/appellate-courts/ca2/18-2974/18-2974-2023-06-30.html
▪ German Accident Report (BSU), Investigation Report 255/12 — https://www.bsu-bund.de/SharedDocs/pdf/EN/Investigation_Report/2014/Investigation_Report_255_12.pdf?__blob=publicationFile
Industry Coverage — liability, US ruling, settlement
▪ The Maritime Executive — Petchem Company, NVOCC Found Liable — https://maritime-executive.com/article/petchem-company-nvocc-found-liable-for-msc-flaminia-fire
▪ FreightWaves — Taking the heat for MSC Flaminia fire — https://www.freightwaves.com/news/shippers-law-taking-the-heat-for-msc-flaminia-fire
▪ SAFETY4SEA — Court found MSC not liable for Flaminia fire — https://safety4sea.com/court-found-msc-not-liable-for-flaminia-fire/
▪ Ship Technology — Fire court ruling upheld in appeal — https://www.ship-technology.com/news/msc-flaminia-fire-court-ruling-upheld-in-appeal/
▪ Container News — Stolt-Nielsen to pay MSC US$290 million — https://container-news.com/stolt-nielsen-to-pay-msc-us290-million-to-settle-msc-flaminia-claim/
▪ SAFETY4SEA — Stolt-Nielsen to pay almost $300 million — https://safety4sea.com/stolt-nielsen-to-pay-almost-300-million-over-msc-flaminia-case/
The liability limitation saga (Conti–MSC, Supreme Court)
▪ The Maritime Executive — MSC Losses Appeal to Limit $200M Liability — https://maritime-executive.com/article/msc-losses-appeal-to-limit-200m-liability-from-2012-msc-flaminia-casualty
▪ Essex Court Chambers — The MSC Flaminia, Supreme Court Judgment — https://essexcourt.com/the-msc-flaminia-supreme-court-judgment/
▪ ICLG — UK Supreme Court rules on long-running maritime accident claim — https://iclg.com/news/22498-uk-supreme-court-rules-on-long-running-maritime-accident-claim
The drama of towing and port refusals
▪ Officer of the Watch — MSC Flaminia Fire Timeline — https://officerofthewatch.com/2012/10/11/msc-flaminia-fire-timeline/
▪ Greens/EFA — Odyssey of the 'MSC Flaminia' — https://www.greens-efa.eu/en/article/news/odyssey-of-the-msc-flaminia
▪ Cedre.fr — MSC Flaminia (towing through the English Channel) — https://wwz.cedre.fr/en/Resources/Spills/Spills/MSC-Flaminia
▪ Wikipedia — MSC Flaminia (technical specifications, timeline) — https://en.wikipedia.org/wiki/MSC_Flaminia
Mechanism of negligence, DGD declaration, and IMDG Code
▪ Handy Shipping Guide — judgment on DGD and lack of effective warning — https://www.handyshippingguide.com/shipping-news/us-court-judges-freight-forwarder-and-chemical-maker-responsible-for-msc-flaminia-deaths_9380
▪ Offshore Energy — Court: MSC Not Liable (Stolt's role as shipper of record) — https://www.offshore-energy.biz/court-msc-not-liable-for-losses-from-msc-flaminia-fatal-fire/
▪ World Maritime News — Stolt Disappointed with Ruling (Stolt's defense argument) — https://worldmaritimenews.com/archives/260671/stolt-disappointed-with-msc-flaminia-ruling/
▪ Wikipedia — International Maritime Dangerous Goods (IMDG) Code — https://en.wikipedia.org/wiki/International_Maritime_Dangerous_Goods_Code
Crew, nationalities, victims
▪ Cedre.fr — crew composition (Germans, Poles, Filipinos), rescue operation details — https://wwz.cedre.fr/en/Resources/Spills/Spills/MSC-Flaminia
▪ FreightWaves — MCA: German-Polish-Filipino crew — https://www.freightwaves.com/news/explosion-aboard-msc-vessel-kills-crewman
▪ Lexology — claims of the chief officer's family (Polish citizen) — https://www.lexology.com/library/detail.aspx?g=8b650cf2-f7b8-4423-8be7-0b7e3aca42e8
Chemical and logistical mechanism
▪ Shipping and Freight Resource — Shipper and Container Operator liable — https://www.shippingandfreightresource.com/shipper-and-container-operator-liable-for-explosion-on-msc-flaminia/
▪ Shipping and Freight Resource — Lack of data and information sharing — https://www.shippingandfreightresource.com/stolt-incident-highlights-consequences-of-lack-of-data-and-information-sharing/
▪ FindLaw — Conti 11 v MSC (booking and terminal details) — https://caselaw.findlaw.com/court/us-5th-circuit/115757486.html
.png)