Article

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


published on 2 April 2021 1986 -

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.

Join the conversation...

Login or register to write comments and join the discussion!
LV
Louis Vest Houston Pilots, USA
on 15 August 2021, 15:04 UTC

Once again the NTSB misses an opportunity to go a little deeper into an investigation. Over the years they have conducted many investigations where a ship loses control in situations that are routine for other ships in the same circumstances. The case of the Eagle Otome in Sabine Pass was one. The Orange Sun in NY harbor was another. Probably the Evergiven as well. There have been many more.
Thousands of ships transit the Houston Ship every year and sea speed across Galveston Bay is routine. This collision was most likely because the ship was built with the bare minimum size rudder designed to keep course in open deep water. It was obviously inadequate for maneuvering of any kind and particularly not for shallow water narrow channels. The full NTSB report actually says the rudder was designed for fuel efficiency which probably means she was also designed to be directionally unstable so as to minimize the amount of rudder necessary to course correct but not helpful when making bigger course changes in a channel.
The report said the Genesis River met the IMO maneuvering standards but they should have looked deeper into its zig-zag test. I would guess it was not performed on the actual ship but on a simulation.
In fact, the pilot who maneuvered the ship through the upper channel made a point of telling the NTSB that the ship was a poor handling one. The voice data recorder recorded the two pilots discussing her bad maneuverability and that of other ships in their experience. Why not look into why she was so bad? Easier to blame the pilot.
The report outlines a scenario in which the intersection of the Bayport channel with the main ship channel played a major role because of the variations in channel width.
I have transited that area many times as a pilot before retirement. There is an effect, but not really significant.
I’d propose an alternate explanation. The previous meetings were in the straight parts of the channel. These meetings only require the ship to turn 4-6 degrees. The collision occurred after the ship made a turn in the channel of 15 degrees. That is enough of a turn to make a loaded ship that is directionally unstable very difficult to check up and steady on the new course. You can start the turn with 10 degrees of rudder, but once she begins swinging full rudder in the opposite direction is barely adequate.
This might not be what happened - I didn’t talk to the pilots - but it is more likely than the haunted Bayport channel scenario.
[show more]
0

Read more...

Video Pilot Transfer - New Zealand (Auckland) & Australia (Melbourne/Fremantle)

published on 21 October 2021

Spotted some Pilot Boats in the Port of Auckland, New Zealand and Melbourne & Fremantle Australia (Port codes: Auckland:NZ AKL ; Melbourne:AU MEL ; Fremantle:AU FRE).

0

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

Video What happens during a snapback event?

published on 18 February 2022

Case Study Video:
BHP - a global mining company and port owner – asked us to develop a test set-up to see what happens during a snapback event and evaluate their safety protection fence. The test data helped in the development of a safer protection fence and gave real insight into snapback behaviour.
Collaboration with BHP, Geobrugg and Wilhelmsen.

0

Article Updated Marine Safety Information by U.S. Coast Guard

published on 6 November 2020

U.S. Coastgard has published an update of their Recommendation for Pilot Transfer Arrangements in latest Marine Safety Information Bulletins (MSIB).

"Recent deaths of maritime pilots while embarking commercial vessels highlight the risks of operating in an
unforgiving maritime environment. To ensure the safety of all personnel boarding a vessel at sea, the Coast
Guard reminds vessel owners and operators of the requirements contained in the Safety of Life at Sea (SOLAS) Chapter V, Regulation 23 and strongly recommends that owners and operators follow the recommendations within IMO Resolution A.1045(27) – Pilot Transfer Arrangements. "

0

Article Man dies after falling from pilot boat (Canada)

published on 28 September 2022

The RCMP are investigating the death of a man who went overboard outside St. John's harbour from a pilot boat early Tuesday morning.

1

Article NTSB Reports on Collision between Baxter Southern Tow and BNSF Coal Train

published on 19 September 2022

The National Transportation Board said Thursday that a Mississippi River towing vessel’s pilot and its captain pushed its tow up against a riverbank too close to a railroad track, leading to a collision and train derailment near Galland, Iowa.

0

Video Hamburg-Süd 10.000-TEU container ship breached hull in ferry pontoon contact in Brazil

published on 27 June 2021

Container ship CAP SAN ANTONIO contacted landing pontoon of Santos – Guaruja commute ferry in the afternoon Jun 20, while leaving Santos, Brazil. The ship dragged pontoon for some time, and sustained portside hull breach above waterline, probably in ballast tank area. CAP SAN ANTONIO was taken to outer anchorage and anchored, for investigation, survey, probably for some temporary repairs. She’s bound for Paranagua.

2

Video New Burnham-On-Sea pilot boat arrives

published on 23 July 2020

Full story at https://www.Burnham-On-Sea.com

1