USS Porter Case Study

Overview of the USS Porter DDG 78 Case Study

  • The lecture focuses on the case study of USS Porter (DDG 78), covering an incident that occurred on August 12, 2012.
  • The objective is to understand how violations of maritime rules, poor situational awareness, and inadequate bridge resource management led to a collision between two vessels.
  • Students are tasked with creating a case study presentation next week.

Incident Details

  • Date and Time: The collision occurred on August 12, 2012, at 0053 local time (12:53 AM).
  • Location: The incident happened in the Strait of Hormuz, known for its high traffic density.
  • Vessels Involved:
    • USS Porter (DDG 78):
    • Classification: Arleigh Burke-class destroyer, highly maneuverable with speeds exceeding 30 knots.
    • Characteristics: Smaller vessel compared to commercial tankers, which allows for better maneuverability.
    • VLCC Otowa-san:
    • Classification: Very Large Crude Carrier (VLCC), a Panamanian-flagged Japanese oil tanker.
    • Length: Over 1,000 feet, making it significantly less maneuverable than USS Porter.

Collision Background

  • Traffic Separation Scheme (TSS): The Strait of Hormuz features a TSS that functions like a highway for maritime traffic, allowing vessels to navigate safely through the area.
  • A mix of various types of vessels, including oil tankers and other naval ships, creates a highly congested environment.

Sequence of Events Leading to Collision

  • Pre-collision Preparations:

    • On August 11, 2012, prior to the collision, USS Porter conducted a navigation brief to ensure proper planning and awareness ahead of major evolutions.
    • Specific details of the navigation brief include:
    • Conducting ops intel brief at 1600, where major threats in the area were discussed.
    • Completing a navigation brief as required 24 hours prior to operations.
    • By 2100, USS Porter was in preparations for a transit through the Strait of Hormuz, an operation that required heightened focus due to darkness and reduced visibility.
  • Watch Changes and Fatigue:

    • At 2300, surface watch coordinator relief due to fatigue, which may have impacted situational awareness.
    • Excessive fatigue can lead to a decrease in vigilance and poor decision-making on the bridge.
  • Timeline of Key Events:

    • 0042: Tactical Action Officer (TAO) assumed charge in Combat Information Center (CIC) but failed to note that three key watch standards were not present.
    • 0043: First contact reported at 6 nautical miles off the port bow. This was a vital moment, as the non-under command vessel was visible but not adequately monitored.
    • 0046: CO (Commanding Officer) arrived on the bridge; critical navigational decisions were made but were not based on the previous recommendations from the navigator and the bridge team.
    • 0047: Confusion regarding navigation orders; multiple conflicting instructions created an inability to respond appropriately to changing conditions.
    • 0049: Communication was chaotic; the bridge team reported crossing in front of key vessels but were met with countermanded orders from the CO.
    • 0052: Final moments before collision; the CO dictated a course that directly led into the path of the VLCC Otowa-san, exacerbated by poor visibility and miscommunication on the bridge.

Collision Details

  • Nature of Collision:
    • Occurred at 0053 when USS Porter crossed the bow of the VLCC Otowa-san despite recommendations against this maneuver.
    • Resulted in substantial damage to USS Porter, while the oil tanker sustained no damage.
  • Damage Assessment:
    • Initial repair costs estimated at $700,000, with total repairs reaching approximately $50 million.
    • Fortunately, there were no injuries reported on either side.

Analysis Using Swiss Cheese Model

  • Swiss Cheese Model Explained:

    • A metaphorical representation of how accidents occur due to multiple safety holes aligning.
    • In the case of USS Porter, various systematic failures allowed the incident to happen, including violations of protocols and miscommunications.
  • Identified Failures:

    • CO’s decision-making lacked situational awareness, primarily since he remained in his stateroom prior to the incident.
    • Lack of proper communication between the bridge and CIC contributed to the chaos and poor decision outcomes.
    • Violations of the Rules of the Road, notably failing to take appropriate action to avoid collision, compounded the risk.
    • Inadequate monitoring and absence of essential personnel in CIC indicated poor bridge resource management.

Ethical and Practical Implications

  • Lessons on Leadership Culture:
    • A toxic leadership environment could lead to lower reporting standards and a reluctance to challenge orders from senior officers.
  • Navigational Responsibility:
    • Importance of accountability and responsibility among all ranks in maritime operations; everyone plays a role in ensuring safety at sea.

Conclusion and Class Assignment

  • Upcoming Case Study Assignment: Presentations scheduled for March 2 and March 4 in pairs, requiring detailed analysis of assigned incidents similar to USS Porter’s.
  • Expectations:
    • Include detailed vessel characteristics, sequence of events, analysis of organizational failures, and adherence to maritime rules and protocols.
    • Encourage engagement with resources provided on the Navy casualty reports for deeper insights into assigned incidents.