Article

NTSB investigation: Collision of LNG carrier with tank barge linked to pilot’s actions


published on 2 April 2021 1190

Text and photox by safety4sea

The LNG carrier ‘Genesis River’ collided with a 297-foot-long tank barge being pushed ahead by the 69-foot-long towing vessel ‘Voyager’, spilling petrochemical cargo into the waterway and capsizing a barge. NTSB issued an investigation report, identifying the Genesis River pilot’s decision to transit at sea speed, out of maneuvering mode, as key cause of the incident.

The incident

On May 10, 2019, the 754-foot-long, 122-foot-wide LNG carrier Genesis River had been outbound on the Houston Ship Channel when it met the inbound 740-foot-long, 120-foot-wide liquefied gas carrier BW Oak in the intersection of the Houston Ship Channel and the Bayport Ship Channel, known as the Bayport Flare.

After the Genesis River and the BW Oak passed each other port side to port side, the Genesis River approached the southern terminus of the flare and a 16-degree port turn in the channel. As the Genesis River exited the flare and entered the turn, it crossed over to the opposite side of the Houston Ship Channel and subsequently struck the starboard barge in the Voyager’s two-barge tow.

The Genesis River’s bow penetrated through the barge’s double hull and breached its center cargo tanks. The force of the collision capsized the port barge in the tow, and the Voyager heeled considerably before its face wires parted and the vessel righted itself. Over 11,000 barrels of reformate, a gasoline blending stock, spilled into the waterway from the starboard barge’s breached cargo tanks.

As a result, the Houston Ship Channel was closed to navigation for two days during response operations and did not fully open for navigation until May 15. The total cost of damages to the Genesis River and the barges was estimated at $3.2 million. The cost of reformate containment and cleanup operations totaled $12.3 million. There were no injuries reported.

Probable causes

NTSB determines that the probable cause of the collision between the Genesis River and the Voyager tow was the Genesis River pilot’s decision to transit at sea speed, out of maneuvering mode, which:


  • increased the hydrodynamic effects of the Bayport Flare’s channel banks,
  • reduced his ability to maintain control of the vessel after meeting another deep-draft vessel, and
  • resulted in the Genesis River sheering across the channel toward the tow.

 

Key findings

  1. Pilot and crew credentialing and experience, use of alcohol or other tested-for drugs, fatigue, and environmental conditions were not factors in the accident.
  2. Mechanical and electrical systems on the Genesis River and Voyager operated as designed, and their functionality was not a factor in the accident.
  3. Although the Genesis River master’s decision to place the vessel’s automated radar plotting aid (ARPA) in standby and turn off the ECDIS deprived the bridge team of critical tools with which to monitor the pilots’ actions and ensure that the vessel transited safely, the status of this equipment was not a factor in the accident.
  4. The Genesis River helmsman properly executed the rudder orders of the pilot and his performance was not a factor in the accident.
  5. Although the helmsman in training properly executed the orders of the pilot, placing him at the helm without informing the pilot was contrary to good bridge resource management practice.
  6. Maintaining stern trim while underway would have improved the handling characteristics of the Genesis River.
  7. The combined effect of the speed of the Genesis River and the passing of another large vessel in the asymmetrically shaped channel at the southern terminus of the Bayport Flare resulted in an uncontrollable sheer to port by Genesis River, initiating a chain of events that led to the collision.
  8. The BW Oak pilot’s maneuvering of his vessel to prepare for the meeting with the Genesis River was routine and did not impede the Genesis River’s ability to pass.
  9. Wide-beam, deep-draft vessels meeting in the Houston Ship Channel in the vicinity of the northern and southern terminuses of the Bayport Flare have a higher risk of loss of control due to complex and varying hydrodynamic forces.
  10. Once the Voyager and its tow began the turn to port, the collision was unavoidable.
  11. An increase in engine rpm to arrest the Genesis River’s initial sheer, even if promptly executed after it was ordered by the pilot, would not have prevented the collision.
  12. The pilot transiting the wide-beam, deep-draft Genesis River at sea speed through the shallow and narrow lower Houston Ship Channel left little margin for error and introduced unnecessary risk.
  13. The Genesis River pilot’s decision not to use emergency full astern or the anchors to avoid the collision was reasonable.
  14. The actions of the Voyager relief captain to attempt to avoid the collision by crossing the channel were reasonable, given the information available to him at the time he had to make the decision to maneuver.
  15. The Genesis River pilot’s early and frequent communications with the Voyager mitigated the impacts of the accident and likely prevented loss of the towing vessel and injuries to its crew.
  16. Coast Guard Vessel Traffic Service Houston–Galveston’s response to the collision was timely and appropriate.
  17. The Bayport Flare, as well as other intersections within the Houston–Galveston Vessel Traffic Service area, would benefit from regular risk assessments and the consideration of additional vessel routing measures.

 

Recommendations

As a result of its investigation of this accident, the National Transportation Safety Board makes the following four new safety recommendations:

-To K-Line Energy Ship Management:

  • Review your safety management system and develop formalized procedures for watch team reliefs to ensure embarked pilots are informed of a change in personnel, particularly a change in helmsmen.

-To the Houston Pilots:

  • Revise guidance to operators of the Genesis River and similar vessels to require vessels be sufficiently trimmed by the stern prior to transiting the Houston Ship Channel.
  • Advise your members to avoid conducting any passing arrangements between widebeam, deep-draft vessels in the northern and southern terminuses of the Bayport Flare.
  • Advise your members to avoid transiting wide-beam, deep-draft vessels at sea speed in the lower Houston Ship Channel.
What's your opinion on this?
Login or register to write comments and join the discussion!
Read more...

Article Marine Accident Brief - Collision of Dixie Vandal Tow with Moored Trinity and Tow

by Marine-Pilots.com - published on 8 April 2020

The U.S. National Transportation Safety Board (NTSB) has released a Marine Accident Brief about an accident that occurred in March 2019, involving the towing vessel Dixie Vandal, noting that the BNWAS alarm didn't prevent the fatigued pilot from falling asleep.

0

Article Docking Pilot’s Actions Cited in Probable Cause of Allision

published on 26 November 2020

The National Transportation Safety Board issued Marine Accident Brief 20/37 Tuesday for its investigation of the Sept. 23, 2019, accident involving the tugboat G.M. McAllister and the NGL Energy Partners wharf on the Southern Branch of the Elizabeth River, near Chesapeake, Virginia.

0

Article NTSB investigation: Higher speed contributes to contact of tow with bridge

published on 14 December 2020

NTSB issued an investigation report on the contact of tow William C with a Rock Island railroad bridge protection cell, on Des Plaines River, in January 2020. The investigation established that high speed prevented the pilot to correct the tow’s position after completing the transit through the previous bridge.

0

Video CMA CGM MISSOURI 300m Container Ship grounded in Suez Canal

Container ship CMA CGM MISSOURI ran aground in Suez Canal while transiting in southern direction, at around 0930 UTC Oct 14. As of 1745 UTC, probably refloated or moved, several Suez Canal tugs attending. Traffic probably suspended, but it’s not confirmed. No information on what caused grounding.
Container ship CMA CGM MISSOURI, IMO 9679919, dwt 115600, capacity 9448 TEU, built 2016, flag Liberia.

0

Video Near miss: VALDIVIA dangerously approached beach in Vlissingen, NL

Container vessel ALDIVIA (IMO 9333395) was dangerously close to public beach at Vlissingen Netherlands, on May 21, while heading out to sea, en route from Antwerp to Helsinki Finland.
The cause of dangerous approach is unknown, but the ship wasn’t detained, she continued her voyage.

0

Video Singapore strait accident: Iranian Container Ship MV SHAHRAZ broke into two

Container ship SHAHRAZ and bulk carrier SAMUDRA SAKTI I are reported to run aground in Singapore Strait south of St John Island at around 1900 UTC May 10, close to each other, while proceeding in the same direction, probably trying to avoid collision. As of 0700 UTC May 11, both ships remain in the same positions, coordinates don’t change. SHAHRAZ is en route from Port Klang to Yangshan China, SAMUDRA SAKTI I is en route from Belawan to Bayah, southwest Java.

0

Article Cargo ship RIMINI collided with lock gate, Kiel Canal

by Marine-Pilots.com - published on 19 May 2020

The ship could not slow down and sailed against the Old North Lock - “Alte Schleuse Nord”.

0

Video Marine Pilot falls in Water During Embarkation

We do not put videos of accidents on our website out of voyeurism. We would like to point out that the work of a pilot is always dangerous, especially when embarking and disembarking!
These incidents should be a warning. It can hit anyone out of carelessness.
Dear pilots, please always be mindful and always think of your safety!

0

Article Scary 30m (98.4ft) Wave Off Irelands West Coast Yesterday

by Marine-Pilots.com - published on 29 October 2020

A monster wave of 30m was measured at 03:00 am by the Marine Institute M6 buoy located 200nm West of Ireland.

1

Video Presenting OpenBridge Design System at DSD2020 in Oslo

I recently presented the OpenBridge design system at the Design System Day 2020 in Oslo. I talked about what OpenBridge is, how it differs from other design systems and where we are heading.
The conference was moved online due to the Corona virus, so I had to record the presentation using my mobile phone, and get Jon Olav from the lab to add the slides. So - apologize for the home quality of the presentation, but I hope you enjoy learning more about our work!
Since we launched the free...

0