Stay up to date with notifications from The Independent

Notifications can be managed in browser preferences.

Navy aircraft carrier HMS Prince of Wales suffers new technical problem

The Nato flagship had been due to set sail for Rosyth for repairs.

Ben Mitchell
Friday 07 October 2022 17:13 BST
HMS Prince Of Wales (Andrew Matthews/PA)
HMS Prince Of Wales (Andrew Matthews/PA) (PA Wire)

Your support helps us to tell the story

From reproductive rights to climate change to Big Tech, The Independent is on the ground when the story is developing. Whether it's investigating the financials of Elon Musk's pro-Trump PAC or producing our latest documentary, 'The A Word', which shines a light on the American women fighting for reproductive rights, we know how important it is to parse out the facts from the messaging.

At such a critical moment in US history, we need reporters on the ground. Your donation allows us to keep sending journalists to speak to both sides of the story.

The Independent is trusted by Americans across the entire political spectrum. And unlike many other quality news outlets, we choose not to lock Americans out of our reporting and analysis with paywalls. We believe quality journalism should be available to everyone, paid for by those who can afford it.

Your support makes all the difference.

The departure of beleaguered Royal Navy aircraft carrier HMS Prince of Wales to head for repairs has been delayed again after the £3 billion warship suffered a further technical problem.

The Nato flagship broke down off the Isle of Wight in August after sailing from Portsmouth Naval Base to take part in flight trials and diplomatic visits in the US.

Inspections by divers and engineers found that the 33-ton starboard propeller, the same weight as 30 Ford Fiesta cars, had malfunctioned with a coupling holding it in place breaking.

The carrier was taken back to Portsmouth for further examination by engineers from Babcock before the decision was taken for it to travel to Rosyth, Fife, where it was built, to undergo repairs in dry dock.

It had been expected to sail on Monday but work was not completed in time to remove the giant propeller and the sailing was delayed until 11am on Friday.

It is understood that an unconnected technical problem has now occurred onboard, meaning the departure has been put back again until at least 11pm.

The sailing is dependent on the issue being resolved as well as high tides to enable the giant warship to leave Portsmouth Harbour.

The Navy has not commented on how long the repairs at Rosyth are expected to take and how long HMS Prince of Wales will be absent from its role as Nato flagship, but it is understood it will be months rather than weeks.

Its sister ship HMS Queen Elizabeth changed its autumn plans to travel to the US to take over some of the planned engagements including hosting the Atlantic Future Forum in New York – a defence conference aimed at strengthening UK and US bonds.

Rear Admiral Steve Moorhouse, director of Force Generation, who is responsible for making sure Royal Navy ships are ready to deploy, previously explained the fault suffered by HMS Prince of Wales.

He said: “Royal Navy divers have inspected the starboard shaft of the ship and the adjacent areas and they have confirmed there is significant damage to the shaft on the propeller and some superficial damage to the rudder but no damage to the rest of the ship.

“Our initial assessment has shown that coupling that joins the final two sections of the shaft has failed.

“This is an extremely unusual fault and we continue to pursue all repair options.”

A Royal Navy spokesman said: “HMS Prince of Wales is preparing to sail to Rosyth to undergo repairs to her right propeller shaft.

“The full extent of the repairs will be known once the ship has entered dry dock.

“We are committed to getting HMS Prince of Wales back on operations, protecting the nation and our allies, as soon as possible.”

Thank you for registering

Please refresh the page or navigate to another page on the site to be automatically logged inPlease refresh your browser to be logged in