During pilotage, incorrect helm application or incorrect helm order are two errors that are easily made. In a recent Mars Report, a bulk carrier suffered water ingress after such an error.
A transcript of what happened:
A loaded bulk carrier was outbound under pilotage with an OOW and helmsman on the bridge. The master was present on the bridge from time to time but was not integrated with the navigation team. At one point, the pilot reduced the ship’s speed so the wake would not affect some nearby berthed wood-chip barges. He did not inform the OOW of the reason for the reduction. He then contacted the pilot of an inbound vessel by mobile phone to arrange a starboard-to-starboard meeting as this was more appropriate for their loaded condition and the depths available in the narrow ship channel. He did not inform the bridge team about this arrangement, nor did the team ask any questions.
Because the speed reduction had reduced the rudder’s effectiveness, at one point the pilot ordered hard port rudder and full ahead. The master had just returned to the bridge and the pilot informed him of the starboard-to-starboard meeting. Some 26 seconds later the pilot ordered midship and then starboard 20. The helmsman confirmed this verbally, but unintentionally put the helm to port 20 instead of starboard 20. This error went unnoticed by the rest of the bridge team.
The pilot ordered hard to starboard. The helmsman started to put on more port helm before realising his error. He then put on full starboard helm.
Both the pilot and the master went to the port bridge wing to view the port aft section. The vessel passed within one metre of the docked barges, but did not strike them. However, the vessel scraped the rocky bottom near the wood-chip dock. There was water ingress in two tanks.
Preventing Such Accidents
Bridge teams should always employ closed-loop communications, but also visually counter-verify orders and executions as a matter of course. Good bridge resource management (BRM) means keeping the team in the loop. Doing so, may help notice these errors.
Mars Reports
This accident was covered in the August Mars Reports, originally published as Mars 201950, that are part of Report Number 322. A selection of this Report has also been published in SWZ|Maritime’s September issue. The Mars Reports are also published on SWZ|Maritime’s website to help prevent maritime accidents.
More reports are needed to keep the scheme interesting and informative. All reports are read only by the Mars coordinator and are treated in the strictest confidence. To submit a report, please use the Mars report form.
Picture: Rocks found in penetrated ballast tank.
