Maritime analysis. Real-time insight.

The MSC Michigan Chief Engineer Case: Beyond Blame, Toward Systemic Accountability

Share this article


The Ghost of Dali: A Wake-Up Call

The maritime fraternity has never fully exorcised the ghost of MV Dali. In March 2024, the containership, while transiting the Patapsco River near Baltimore, suffered a cascading electrical blackout that left its propulsion and steering systems inoperable. Without control, the vessel struck the Francis Scott Key Bridge, collapsing several spans and tragically killing six maintenance workers.

The NTSB has since completed its investigation. It found that a loose signal-wire connection caused the blackout that led to the loss of propulsion and steering close to the bridge. For mariners, Dali remains a reminder of how a small technical failure can rapidly become catastrophic. That same question of how abnormal conditions are managed before control is lost leads directly to MSC Michigan VII.

MV Dali – A reminder that systemic failures can turn routine operations into catastrophe.

A Short Story of What Happened: MSC Michigan VII

On June 5, 2024, while departing Charleston Harbor, the vessel’s main engine governor linkage detached. The ship became momentarily unresponsive to bridge orders and surged ahead at 15–17 knots, more than double the legal harbor limit. The pilots informed the authorities immediately who closed the Arthur Ravenel Jr. Bridge and cleared nearby beaches as a precaution. The U.S. Coast Guard detained the vessel for inspection before later lifting the detention order.

At the center of the public story was Fernando San Juan, 61 years old, the Chief Engineer aboard MSC Michigan VII. Federal prosecutors alleged that he failed to report hazardous conditions and obstructed investigators by providing misleading statements and encouraging crew to do the same. San Juan ultimately entered a plea agreement, admitting to failing to report a hazardous condition and to obstructing an agency proceeding.

Court filings describe repeated machinery problems and a main engine that did not always achieve the RPM ordered from the bridge. Problems in the fuel-injection system, including when operating on lower-viscosity low-sulfur fuel, contributed to the condition. Engineers compensated by manually adjusting the governor linkage. What began as a workaround became routine.

On June 5, that workaround failed. The linkage disconnected and engine speed could no longer be controlled.

Those are the immediate facts and technical realities combined. What is less obvious and where the hard lessons lie is how organizational pressures, deferred maintenance, and systemic operational compromises transformed a temporary, emergency workaround into a potentially catastrophic failure.

Schematic of a marine diesel engine governor and linkage system, illustrating how speed control is mechanically managed.

When “Human Error” Becomes System Collapse

Modern maritime investigations often default to a shorthand explanation – human error. It’s tidy, easily digestible for headlines, and satisfies public expectations for accountability. Yet human error rarely exists in isolation. It is almost always the final link in a chain of systemic factors, including:

  • Fatigue and compressed work cycles, leaving crew less alert during critical maneuvers.
  • Reduced spare-part inventories, forcing operators to improvise repairs.
  • Deferred maintenance and prolonged operational compromises, which gradually weaken machinery.
  • Compressed handovers, limiting the incoming officer’s understanding of ongoing issues.
  • Managerial messages, both explicit and implicit, prioritizing schedule and cargo delivery over safe downtime.

In the MSC Michigan VII case, court filings highlighted an abbreviated handover window and chronic mechanical deficiencies. The temporary manual workaround for the governor linkage exemplifies how systemic pressures transform minor technical issues into high-risk situations.

These improvisations shift risk from visible machinery defects into crew practice, where organizational failures can later appear as individual error.

Barring a few standard and reputable companies, this scenario is common across the shipping industry, crews innovate to keep vessels operational, managers approve departures for commercial reasons, insurers protect some operational risks but not systemic failures, and auditors or regulators often remain unaware until an incident occurs. When failure strikes, the person on watch becomes the face of accountability, the name on a charge sheet, while the systemic pressures that created the vulnerability remain largely invisible.

Critical systems require constant vigilance; minor compromises can escalate rapidly.

Reading this as a maritime insider, seafarer, or enthusiast?

Subscribe to The DeepDraft for maritime analysis, daily SITREP updates, weekly briefings, and operational signals worth watching.


Technical Management: Shore Control, Superintendents, and the Competence Gap

Modern shipping relies increasingly on centralized shore-side technical management, creating a structural distance between decision-makers and the engineers managing machinery onboard. In many companies, the heads of fleet technical departments are not always former Chief Engineers. The HODs may appoint junior engineers, dual-certified officers, or even deck officers to technical management roles, individuals who are often less likely to challenge directives. While intended to streamline operations, this structure can weaken technical oversight and operational judgment, leaving crews to manage systemic and mechanical challenges largely on their own.

Senior Chief Engineers onboard are not always convinced by directives from comparatively junior superintendents ashore. The result can be resentment rather than compliance, exposing the growing experiential gap between those making technical decisions ashore and those carrying them out at sea.

Evolution of Superintendent Role

Some superintendents have never carried the full responsibility of a Chief Engineer, or have served only briefly in that role. They increasingly coordinate with sailing Chief Engineers, manufacturers or shore specialists rather than troubleshooting machinery directly. While this approach can improve standardization and information flow, it reduces hands-on engagement and shifts operational risk onto the vessel. Temporary fixes, deferred maintenance, and procedural shortcuts become normalized, especially under commercial pressure or when spare-part inventories are limited.

The MSC Michigan VII incident illustrates the consequences, chronic mechanical issues, constrained spares, and reliance on manual workarounds combined with dispersed shore-side directives left the Chief Engineer, despite decades of experience, as the primary face of accountability, even though the root causes were systemic.

That ship-shore disconnect increasingly extends into how decisions are communicated and recorded, a problem examined further in The WhatsAppisation of Ship Operations.


Cost Cutting, Spares, and Deferred Maintenance

Spare parts are costly, and logistics for critical engine components can be slow and complicated. Under commercial pressure, ships often operate with reduced spare inventories, deferred maintenance, and postponed overhauls.

In MSC Michigan VII, persistent leaks and faults in the fuel injection pumps, fuel lines, and auxiliary fuel pumps affected the delivery of fuel to the main engine cylinders. To maintain engine performance and achieve commanded RPMs during maneuvers, the crew was forced to manually adjust the governor linkage as a workaround. Limited spare availability forced the crew to rely on temporary workarounds. Every decision to postpone maintenance or reduce spare inventories magnified latent risk, turning routine cost-cutting into a safety hazard with legal consequences for onboard personnel.

The wider point remains that vessel condition is ultimately shaped by management decisions, an argument developed further in Flag of Convenience vs Safety: What 2026 PSC Data Really Reveals.

Deferred maintenance and limited spares can transform minor defects into critical failures.

Defect Reporting and Near-Miss Management

Defect reports and near-miss reports are intended to be the cornerstone of organizational learning and operations in shipping. Properly handled, they allow crews and management to identify latent hazards, trigger risk assessments, allocate or procure critical spare parts, and notify classification societies, flag administrations, and port authorities when necessary. This structured approach ensures preventive action before minor technical issues escalate into major incidents.

In reality, however, the reporting system is often subverted by commercial and bureaucratic pressures. Many companies set KPIs for near-miss reporting, requiring a minimum number of events per month. To meet these targets, vessels may submit minor or irrelevant reports, while truly critical hazards go unreported to avoid investigations, follow-up questioning, or operational delays. Similarly, defect reports for critical equipment are often logged only after the defect is rectified, to avoid triggering regulatory scrutiny, short-term certification, additional inspections, or unplanned costs. Outcomes that operators are incentivized to minimize.

This flawed approach undermines the purpose of both systems. Important lessons are lost, latent risks persist, and hazards remain hidden until they manifest in incidents, leaving crews and management exposed. In the case of MSC Michigan VII, issues with fuel supply system components led to manual governor adjustments, a workaround that could have been prevented with timely and transparent defect reporting.

Ultimately, near-miss and defect reporting systems are only effective if reporting is meaningful, timely, and followed by concrete action. Without this, safety systems exist largely on paper, and systemic risks continue to accumulate, waiting for the next preventable accident.

Transparent reporting is essential to prevent small issues from escalating.

Handover Failure: The 5-Hour Gap That Mattered

Handover is deceptively simple but crucial. IMO guidance stresses face-to-face exchange and adequate review of logs, defects, and ongoing repairs. In MSC Michigan VII, the incoming Chief Engineer had only a five-hour handover, far shorter than recommended. As a result, latent defects and established workarounds became his immediate responsibility, setting the stage for cascading failure.

The problem is compounded by crew travel and fatigue. Senior officers often arrive at their vessels after 24–36 hours of continuous travel involving paperwork, medical checks, flights, layovers, and multiple time zone changes. In many cases, they step on board immediately upon arrival and are expected to take charge of safety-critical systems without meaningful rest. This creates a dangerous situation where handover is rushed, fatigue & jet lag is at its peak, and critical details are missed.

The risk can begin before the officer even reaches the gangway, an operational gap examined separately in Crew Transfer: Shipping’s Unregulated Risk Zone.

Travel time should not automatically be treated as meaningful rest. For senior officers joining after prolonged transit, recovery time must form part of the joining arrangement, while regulatory fatigue frameworks need to recognise transit fatigue more clearly.

Officers engage in a comprehensive handover meeting, ensuring continuity and safety in operations.

Legal Exposure: Why the Seafarer Becomes the Face of Accountability

When this article was first published, the MSC Michigan case appeared to follow a familiar pattern in maritime law enforcement. When something goes wrong, it is usually the seafarer, not the company, not the shore office, not the procurement system who ends up in the courtroom. Prosecutors focused on Fernando San Juan’s failure to report hazardous conditions and his misleading statements, because he was physically present and held formal authority.

This focus on the individual makes legal sense, but it raises an uncomfortable imbalance. Onboard personnel can face prison time, fines, loss of certification, and permanent reputational harm in a tight-knit industry. Meanwhile, the systemic factors that shaped their decisions like commercial schedules, cost-cutting on spares, managerial pressure, or inadequate handovers rarely face the same level of scrutiny or accountability.

Until legal frameworks distribute responsibility more evenly between ship and shore, the Chief Engineer or Master often remain the easiest target of accountability, even when they are simply the last visible link in a much longer chain of decisions and pressures.

Since this article was first published, the MSC Michigan VII case has moved further. In August 2026, MSC Shipmanagement also pleaded guilty and was sentenced to a $6 million criminal fine and four years of probation for failing to report the hazardous condition and obstructing the investigation. San Juan was fined $2,000. The company was also ordered to conduct a root-cause analysis.

Safety Culture vs. Commercial Reality
Every vessel displays the company’s Safety and Environmental Policy, which may have limited impact on day-to-day operations. Crews sail with deferred defects, improvised fixes, and commercial pressure that overrides the slogans. A genuine safety culture needs investment in spares, accountability ashore, and protection for those who report concerns otherwise, it remains a poster on the wall, not a practice on board.


Toward Systemic Accountability

For the maritime sector to achieve lasting safety improvements, reforms must go beyond compliance documents and marketing slogans:

  1. Hardened handover and watchkeeping standards
    • Minimum-duration handovers with face-to-face briefings and auditable documentation to ensure incoming officers fully understand ongoing defects, workarounds, and operational nuances.
  2. Spare-part resilience and planned maintenance
    • Verified inventories of critical engine and propulsion components, with penalties for chronic deferrals. Ensure procurement timelines account for obsolete or hard-to-source parts to prevent operational improvisation.
  3. Shared shore-vessel accountability
    • Legal and operational frameworks that hold shore managers responsible for decisions that shift risk onto the crew. Onboard personnel should not be the sole bearers of consequences when systemic pressures compromise safety.
  4. Robust near-miss reporting and a just culture
    • Anonymous, third-party reporting systems protecting whistleblowers from retaliation. Encourage meaningful reporting rather than “KPI-filling” superficial entries.
  5. Transparent investigations that publish lessons
    • Redacted, publicly available root-cause analyses so the industry can learn from incidents without placing undue blame solely on the seafarer.

Change the Question, Not Just the Defendant

Fernando San Juan’s case remains both personal and structural. He pleaded guilty and was fined. MSC Shipmanagement subsequently pleaded guilty and received the larger corporate penalty.

  • What cost pressures, managerial decisions, and regulatory gaps allowed manual linkages to become standard practice?
  • What organizational conditions allowed a hazardous practice to persist before accountability finally reached both ship and shore?

Until the industry answers these questions, every Chief Engineer knows the script, when failure occurs, the blame will be theirs, and the system will have learned only how to hide the same vulnerabilities, rather than prevent them.


Sources

  • US Coast Guard, “MSC Michigan VII released from detention in Charleston.” USCG News
  • Maritime Executive, “Chief Engineer Pleads Guilty in 2024 MSC Runaway Incident.”
  • gCaptain, “Runaway Ship: Chief Engineer Pleads Guilty After Charleston Bridge Scare.”
  • IMO resources on Safety Management and the ISM Code
  • OCIMF, “Engineering Watch, Duty Periods, and Inspection Routines”
  • Legal and academic critiques of flags of convenience and regulatory implications
  • Industry discussions on spares, deferred maintenance, and operational impacts of cost-cutting

This article is an opinion piece by the author and does not reflect the official position of any company, organization, or regulatory body. All factual references are drawn from publicly available sources and news reports.

Updated September 2026: Originally published on 7 October 2025. This article has been updated to reflect subsequent legal developments in the MSC Michigan VII case. The original analysis and central argument have been retained.

Discover more from The DeepDraft

Subscribe now to keep reading and get access to the full archive.

Continue reading