{"id":19585,"date":"2025-11-03T19:02:22","date_gmt":"2025-11-03T19:02:22","guid":{"rendered":"https:\/\/krogragg.com\/?p=19585"},"modified":"2025-11-03T19:02:22","modified_gmt":"2025-11-03T19:02:22","slug":"lack-of-coordination-between-crew-pilots-caused-fremantle-ship-collision-atsb","status":"publish","type":"post","link":"https:\/\/krogragg.com\/?p=19585","title":{"rendered":"Lack Of Coordination Between Crew & Pilots Caused Fremantle Ship Collision: ATSB"},"content":{"rendered":"\n
Lack Of Coordination Between Crew & Pilots Caused Fremantle Ship Collision: ATSB<\/div>\n

\t

\n
<\/BR>
\n
\n \t

\n
<\/BR><\/p>\n

\n
\"Lack<\/div>\n
\"ATSB\"
Image Credits: ATSB<\/figcaption><\/figure>\n

Ineffective coordination and monitoring by the crew and harbour pilots on board the container ship Maersk Shekou contributed to its collision with the tall ship Leeuwin II in the Port of Fremantle, the Australian Transport Safety Bureau has found.<\/p>\n

The 333-metre, Singapore-flagged Maersk Shekou was being navigated into Fremantle under the direction of two harbour pilots in heavy squall conditions before dawn on 30 August 2024, an ATSB investigation final report details.<\/p>\n

The investigation\u2019s review of audio from the ship\u2019s bridge, taken from the vessel data recorder, found the primary pilot did not provide the helmsman with a planned port 10\u00b0 helm order to turn into the inner harbour, which went undetected by the rest of the bridge team.<\/p>\n

This meant that as the pilot attempted to use the main engine and four attached tugs to turn the ship, the helmsman attempted to maintain the ship on the previously instructed heading of 083\u00b0, rigorously opposing the ship\u2019s planned turn.<\/p>\n

As a result, the Maersk Shekou continued towards Victoria Quay and collided with the Leeuwin II, which was berthed at the quay, before the stern contacted the wharf edge and containers struck the roof of the WA Maritime Museum.<\/p>\n

The Leeuwin II was dismasted and two crew, who had been on board and were escaping via its gangway just as the collision occurred, sustained minor injuries. The container ship sustained minor damage, including a hull breach, but its crew and the pilots were uninjured.<\/p>\n

Chief Commissioner Angus Mitchell said the ATSB found the ship\u2019s bridge team \u2013 comprising the two pilots and the ship\u2019s crew \u2013 ineffectively implemented bridge resource management practices.<\/p>\n

Specifically, there was not a shared mental model of the actions needed during the passage across members of the bridge team, and they failed to adequately monitor, or challenge, the ship\u2019s turn and position in the channel.<\/p>\n

\u201cA properly functioning bridge team requires that all its members maintain a shared mental model to actively monitor a ship\u2019s progress,\u201d Mr Mitchell said.<\/p>\n

\u201cThis relies on relevant information being conveyed to all members of the team, and actions that are incorrect being identified, communicated and rectified immediately.\u201d<\/p>\n

The ATSB\u2019s investigation also found the secondary pilot was distracted from their monitoring responsibilities as they were engaged in a non-essential mobile phone call as the ship was transiting a critical area in the entrance channel.<\/p>\n

\u201cThis meant they were distracted from their monitoring role and did not identify that the lead pilot had not ordered a course alteration, and that the helmsman\u2019s actions were opposing the ship\u2019s planned turn,\u201d Mr Mitchell said.<\/p>\n

\u201cThis highlights the importance of minimising distractions on the bridge, especially during critical stages of a passage.\u201d<\/p>\n

The investigation also identified that making fast the supporting tugs was delayed, resulting in the bridge team, including the pilot, being engaged with the final tug\u2019s attachment just as the ship approached the wheel over point for the inner harbour entrance channel.<\/p>\n

\u201cThis increased bridge team workload at the most critical stage of the passage.\u201d<\/p>\n

Mr Mitchell noted the ATSB also identified several risk controls established by Fremantle Ports to ensure the safe entry of large container vessels had not been adequately implemented, although these did not all directly contribute to the collision.<\/p>\n

\u201cThese included entering the inner harbour channel without all tugs being secured, prior to sunrise, and well in-excess of the operational wind limits \u2013 all of which contravened documented procedures.\u201d<\/p>\n

Mr Mitchell said these factors collectively reduced the effectiveness of the port\u2019s risk control measures and increased the risk of future safety occurrences.<\/p>\n

Both the port and the pilotage provider, Fremantle Pilots, have committed to implement a range of safety actions in response to the investigation.<\/p>\n

Concluded Mr Mitchell: \u201cThe dynamic nature of marine operations often results in conditions varying from those expected, and it is essential any associated risks and consequences \u2013 particularly those affecting pre-defined and documented limits \u2013 are carefully reassessed when required, and any changes to the plan are effectively communicated between all concerned parties.\u201d<\/p>\n

Read the final report: Collision between container ship Maersk Shekou and tall ship STS Leeuwin II, Fremantle, Western Australia, on 30 August 2024<\/a><\/p>\n

Press Release<\/em><\/p>\n<\/div>\n

\t

\n
<\/BR>
\n MI News Network
\n \t

\n
<\/BR>
\nGo to marine insight<\/a>
\n \t

\n
<\/BR><\/p>\n","protected":false},"excerpt":{"rendered":"

Lack Of Coordination Between Crew & Pilots Caused Fremantle Ship Collision: ATSB Image Credits: ATSB Ineffective coordination and monitoring by the crew and harbour pilots on board the container ship Maersk Shekou contributed to its collision with the tall ship Leeuwin II in the Port of Fremantle, the Australian Transport Safety Bureau has found. The […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[194,196],"tags":[197],"class_list":["post-19585","post","type-post","status-publish","format-standard","hentry","category-marine-insight","category-shipping-news","tag-marine-insight"],"_links":{"self":[{"href":"https:\/\/krogragg.com\/index.php?rest_route=\/wp\/v2\/posts\/19585"}],"collection":[{"href":"https:\/\/krogragg.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/krogragg.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/krogragg.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/krogragg.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=19585"}],"version-history":[{"count":0,"href":"https:\/\/krogragg.com\/index.php?rest_route=\/wp\/v2\/posts\/19585\/revisions"}],"wp:attachment":[{"href":"https:\/\/krogragg.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=19585"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/krogragg.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=19585"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/krogragg.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=19585"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}