HMAS Sydney charts course for Australia
HMAS Sydney will return home on October 24 after a busy four months at sea during a regional presence deployment.
CAPTION: HMAS Sydney conducts officer of the watch manoeuvres during Exercise Pacific Dragon 2024. Photo by Leading Seaman Daniel Goodman.
The Hobart-class guided missile destroyer will be welcomed back by families, friends and the Royal Australian Navy Band at Fleet Base East.
During the deployment, Sydney conducted first-of-class missile firings of the Naval Strike Missile and Standard Missile 6.
The ship participated in Exercise RIMPAC, Exercise Pacific Dragon, Indo-Pacific Endeavour and Operation Argos – the ADF’s contribution to international efforts to enforce United Nations Security Council sanctions against North Korea.
Sydney also conducted activities with regional partners, including Japan, South Korea, New Zealand, the Philippines and the United States to improve cooperation and interchangeability.
The crew conducted a number of replenishments at sea with Canada, Japan and New Zealand, as well as an Australian first with German Navy ship FGS Frankfurt Am Main.
Acting Commander Australian Fleet Commodore Ray Leggatt said Sydney’s deployment demonstrated Australia’s commitment to engaging closely with allies and partners as part of maintaining a near-continuous presence in the Indo-Pacific region.
“Sydney has accomplished a lot over their deployment and worked with regional partners contributing to keep the region peaceful, stable and prosperous,” Commodore Leggatt said.
Commanding Officer Sydney Commander Grant Coleman commended his crew for everything they had accomplished during the deployment.
“I am proud of the way Sydney’s crew worked throughout this deployment, with their actions enhancing the lethality of the surface combatant fleet, contributing to regional security and representing Australia in the Indo-Pacific and beyond,” Commander Coleman said.
Sydney steamed 29,833 nautical miles and was away from its home port for 136 days throughout the deployment.
.
.
.
.
