The Hidden Fault That Turned a Container Ship Into a Runaway Threat
On 5 June 2024, the containership MSC Michigan VII left Charleston bound for open sea via the Cooper River and the Arthur Ravenel Jr. Bridge. Mid‑transit, the linkage rod that connected the engine’s governor to its fuel rack disconnected after the engineering crew had been manually adjusting it—a practice the crew was neither trained nor authorised to perform. The result was a runaway engine that pushed the vessel to 16‑17 knots, forcing an emergency evacuation of the eight‑lane bridge and nearby beaches. Although the ship passed safely under the bridge, its powerful wake injured two people on shore and damaged ships and piers.
An investigation by the U.S. Coast Guard and the National Transportation Safety Board (NTSB) soon uncovered that the engine department had for some time been loosening the linkage rod’s locking nuts and removing its safety washers so they could manually tweak engine revolutions to match bridge telegraph orders. MSC Shipmanagement Limited and its chief engineer, Fernando San Diego San Juan, knew this hazardous condition existed but never reported it to the Coast Guard. Worse, when questioned, San Diego San Juan repeatedly lied to investigators about the adjustments and coached other crew members to stick to the same story.
On 10 August 2026, MSC was sentenced to pay a $6 million criminal fine and serve four years’ probation, during which it must conduct a root‑cause analysis of the hazard. San Diego San Juan received a $2,000 fine after pleading guilty to failing to report the condition and obstructing the investigation. The U.S. Department of Justice stressed that the near‑miss echoed the fatal Baltimore bridge strike earlier in 2024, warning that the outcome could have been catastrophic had the ship been inbound instead of outbound.
Behind the Guilty Plea: The Cost of Silencing a Hazard
Unsafe Practice Hidden from Regulators
The core of the case is not just a mechanical failure but a systemic silence. The MSC Michigan VII’s bridge and engine crews lived with a known mismatch between ordered and actual engine revolutions, and the makeshift fix—manually adjusting the linkage rod—was executed with both locking washers removed. That deliberate bypass of a design‑critical safety feature turned a routine maintenance issue into a life‑threatening hazard. MSC and its chief engineer not only allowed the practice but actively concealed it, lying to NTSB and Coast Guard investigators. The obstruction charge adds weight beyond a simple violation: it signals that the company and its officer placed avoidance of regulatory trouble above the safety of a major port and the public.
A Warning Shot After the Baltimore Tragedy
The 2024 Baltimore bridge collapse, caused by a container ship losing power, set a grim precedent. The Charleston incident—occurring months later—shows that similar engineering neglect and cover‑up nearly produced a repeat disaster. The DOJ’s charging documents and the $6 million fine make clear that the U.S. government will treat failure to report hazardous conditions and lying to federal investigators as criminal offenses, not administrative oversights. For MSC, the probation period means its operations are under a microscope; any further safety lapses could trigger far harsher sanctions. The case also raises questions for the industry: how many other vessels have crews quietly performing prohibited adjustments because proper repairs are costly or inconvenient?
What Shipping Operators Must Learn from the MSC Michigan VII Case
The sentencing provides a roadmap of what shipping operators must embed in their safety management systems to avoid criminal liability:
- Mandate immediate reporting of any governor‑linkage anomalies. The MSC Michigan VII crew knew for some time that engine rpm did not match telegraph orders; every such mismatch must trigger a formal report to the master and port‑state authorities.
- Prohibit crew from manually adjusting governor linkages. Only qualified shore‑side technicians should handle these components. Shipboard procedures must explicitly forbid tampering, and logging of all governor‑room access should be maintained.
- Reinstate and inspect all designed safety features. The locking washers that were removed are there to prevent precisely this kind of failure. Regular audits must confirm that every safety device is in place and unmodified.
- Embed a non‑retaliation culture for hazard reporting. The obstruction in this case began with fear of consequences. Companies must ensure that any crew member who flags a dangerous practice is protected and rewarded, not silenced.
- Conduct periodic “near‑miss” root‑cause analyses. The probation sentence requires MSC to dissect this incident. Proactive operators should do the same for their fleets, using data from engine logs and bridge recordings to uncover unreported risks.
Risk & Opportunity Assessment
| Commercial Risk | Medium | The $6 million fine is manageable for a major ship manager, but four years of probation with mandatory root‑cause analysis could restrict operational flexibility and increase scrutiny from insurers and charterers. |
| Competitive Risk | Low | The incident does not directly alter MSC’s market position, though rivals may leverage the reputational stain in commercial negotiations. |
| Regulatory Risk | High | The criminal prosecution signals a DOJ and USCG posture that treats failure to report and obstruction as felony‑level offenses. Any similar future breach will likely bring harsher penalties, and the probation term exposes MSC to immediate sanctions for non‑compliance. |
| Reputation Risk | Medium | The public evacuation of a major bridge and echoes of the Baltimore collapse generate lasting negative visibility. Industry stakeholders—ports, pilots, and insurers—will remember MSC’s active concealment of a safety hazard. |
| Technology Disruption | Low | The failure stemmed from human bypass of existing safety guards, not from an obsolete system. No transformative technology gap is implicated. |
| Commercial Opportunity | Low | The case may encourage adoption of digital engine monitoring and tamper‑proof logging, but that opportunity is generic and not directly tied to MSC’s own business model. |
Comments 0