Star azipod propulsion problem

[chengkp75]

I am just curious whether the problem with really with the Azipod or with the diesel engines that generate power to the electric motors of the Azipods, which drive the propellers. The Star is much like a Chevy volt hybrid car - the gas/(diesel) engine runs a generator for the electric motor that drives the wheels, or in the case of a ship, the propellor.

 

The Star has 2 Azipods and 4 diesel engines, according to Wikipedia. Can someone on the Star go to the stern of the ship and see if they think both propellers are turning? (I don't if you really can tell, but it is worth a try). If it is clear both are operating, then the problem is not with the Azipods.

 

I was on the June Baltic cruise with the Star when it departed Stockholm late because of a technical problem. As I recall, the problem was with for one of the diesel engines and I thought they said it was a electronic module that was bad. This is something I think can be fixed or replaced while the ship is still in the water.

 

If the problem is not with the Azipod, then they don't need to drydock. Drydocking will have a profound effect on the itinerary. I don't know how they would accommodate passengers going off and on the ship while drydocked.

 

I will be boarding the NCL Star Dec. 22 in HK. Will bring a lot books to read.

 

Yes, the ship is operating on one azipod, as reported by a poster who is onboard and has seen only one wake. Ships have operated on one azipod for long periods of time, the Star did it for months in 2004 around Hawaii.

 

Even if the problem is with the azipod, I believe from the information given out onboard, and the fact that they have sent for a technician, that the problem is not a mechanical problem in the azipod itself, but in the electrical controls. Unlike your Chevy volt, where DC power is stored in batteries, and sent to DC motors which are easily controlled for speed by varying the voltage to the motor, the ship generates AC power at 60 Hz, so an AC motor, by its design runs at a fixed speed in relation to the frequency of the power. To vary the speed of an AC motor, you need to convert the AC power to DC, then reconvert that DC power back to AC, but with a frequency that is variable. With a variable frequency, the motor, and hence the propeller can turn at various speeds. This "variable frequency drive" appears to be what has failed, and this is inside the hull of the ship, not in the azipod, and can be repaired while underway.

 

The diesel engines are not always all available. While it does require all 4 diesel generators to get the ship to maximum speed, she can do easily 19-20 knots with only 3. Itineraries are typically designed to allow for only having 3 engines available, as routine maintenance needs to be done periodically. Further, the engines are torn completely down for overhaul every 12,000 hours (about every 2 years), and these overhauls take 2-3 weeks to complete, so very often the ships are sailing around with one engine out of service and no one onboard is the wiser.

[echintune]

I received an official email (from NCL corporate) regarding a revised itinerary for the December 22 sailing.

 

Depart Hong Kong as scheduled

Overnight in Da Nang (subject to change)

Overnight in Phu My

One full day in Bangkok

Arrive in Singapore on Jan 4 8pm.

 

Taiwan, Ha Long Bay, Sihanoukville and Ko Samui ports have been cancelled.

 

That's very confusing I've just received an email from NCL for the Dec 22 sailing with the following itinerary:

 

Thu 22/12 Hong Kong China 07:00

Fri 23/12 Hong Kong China 14:00

Sat 24/12 at sea

Sun 25/12 Ha-long bay Vietnam 08:00 17:00

Mon 26/12 Danang Vietnam 08:00 18:00

Tue 27/12 at sea

Wed 28/12 Nha Trang Vietnam 08:00 17:00

Thu 29/12 at sea

Fri 30/12 at sea

Sat 31/12 Sihanookville Cambodia 08:00 18:00

Sun 01/01 at sea

Mon 02/01 Ko Samui Thailand 08:00 17:00

Tue 03/01 at sea

Wed 04/01 at sea

Thu 05/01 Singapore 06:00

[sbsmutoni]

That's very confusing I've just received an email from NCL for the Dec 22 sailing with the following itinerary:

 

Thu 22/12 Hong Kong China 07:00

Fri 23/12 Hong Kong China 14:00

Sat 24/12 at sea

Sun 25/12 Ha-long bay Vietnam 08:00 17:00

Mon 26/12 Danang Vietnam 08:00 18:00

Tue 27/12 at sea

Wed 28/12 Nha Trang Vietnam 08:00 17:00

Thu 29/12 at sea

Fri 30/12 at sea

Sat 31/12 Sihanookville Cambodia 08:00 18:00

Sun 01/01 at sea

Mon 02/01 Ko Samui Thailand 08:00 17:00

Tue 03/01 at sea

Wed 04/01 at sea

Thu 05/01 Singapore 06:00

 

 

That's interesting. I got an email too, and it's for the first of these (quoted by "rowdypfeifer").

[eoehme]

I also received the revised itinerary like echintune...this is very confusing

[marcs1]

I received an official email (from NCL corporate) regarding a revised itinerary for the December 22 sailing.

 

Any mention of being given a discount on the fare paid for this cruise or on a future cruise?

[rowdypfeifer]

Any mention of being given a discount on the fare paid for this cruise or on a future cruise?

 

Yes, it was included in the letter. 50% refund and 50% future cruise credit if sailing and 100% refund and 25% future cruise credit if not.

 

Letter was signed by NCL VP of passenger services.

[Ange66]

I too have received the same itinerary as echintune and eohme, not by email, it was a phone call from NCL

 

 

Sent from my iPad using Forums

[eoehme]

So, it seems that NCL Europe did sent a different revised itinerary than NCL US is sending to their clients.

[Cruisers6165]

We have received a different itinerary from NCL via Vacations To Go.

 

22nd Hong Kong

23rd Hong Kong

24th At Sea

25th Chan May

26th Chan May

27th At Sea

28th Phu My

29th Phu My

30th At Sea

31st At Sea

1st Laem Chabang

2nd At Sea

3rd At Sea

4th Singapore

5th Singapore

 

How can there be so many revisions floating around??

[marcs1]

 

How can there be so many revisions floating around??

 

This is from an E-mail dated December 16, 2016 from NCL:

overnight

Fri Hong Kong, China 2:00 pm

Sat At Sea

Sun Hue/da Nang (Chan May), Viet Nam 8:00 am overnight

Mon Hue/da Nang (Chan May), Viet Nam 5:00 pm

Tue At Sea

Wed Phu My (Ho Chi Minh City), Viet Nam 3:00 pm overnight

Thu Phu My (Ho Chi Minh City), Viet Nam 10:00 pm

Fri At Sea

Sat At Sea

Sun Laem Chabang, Thailand 6:00 am 10:00 pm

Mon At Sea

Tue At Sea

Wed Singapore, Singapore 8:00 pm

Thu Singapore, Singapore

NOTE: The call in Chan May is subject to change.

 

As a gesture of our thanks for our guest's understanding of this unforeseen delay and change in itinerary:

a. Guests who choose not to sail the revised itinerary, we will provide a full refund of this 14-day Asia cruise, and a 25% future cruise credit of current

14-day cruise fare paid.

b. Guest who chose to sail, will receive a 50% refund of this 14-day Asia cruise and 50% future cruise credit of current 14-day cruise fare paid.

Please note that the following nationalities require a Thai visa: Colombia; Costa Rica; Ecuador; Guatemala; Lebanon; Morocco; Mexico and Venezuela. It is extremely important that the visas be secured prior to arrival as guests will be denied boarding without them. We thank you for understanding and for

choosing Norwegian Cruise Line.

Sincerely,

Vivian Ewart

[Circusboy354]

Unfortunately Nha Trang, our first port has now officially been cancelled due to the weather / tendering conditions. Such a shame, I think it was the highlight of our revised itinerary.

[mking8288]

Unfortunately Nha Trang, our first port has now officially been cancelled due to the weather / tendering conditions. Such a shame, I think it was the highlight of our revised itinerary.

Sorry to hear that & thank you for keeping us updated with onboard news ... Was wondering as it's Saturday in VN but Friday evening in the US mainland. Marinetraffic tracking not updating but obviously, ship is still at sea with light chops, cloudy skies, etc. and not appeared to be anywhere near the coastline.

 

Chan May in 2 days - isn't that also going to be a tendering port, hopefully - it will give folks a chance to exercise those sea legs. Hopefully, luck will be on your side.

 

The revised schedule with the conflicting departure time, it seemed, has to do with sailing/leaving HK at 7 AM originally scheduled for 12/23, Friday morning and now pushed back to the afternoon instead ... which, would make sense to give the technicans & specialists more time to stay onboard to do any repairs to the electrical components associated with the azipod, instead of rushing her out to see.

 

It seemed that the Star left late night earlier in the week doing around 10 knots but took her as fast as almost 13 knots, based on posted tracking data ... and, assumption is that until the systems are fully repaired and operationally safe, she isn't and hasn't been able to go any faster than 10 to 12 knots. Is that a fair assumption ?

[opmet]

The revised schedule with the conflicting departure time, it seemed, has to do with sailing/leaving HK at 7 AM originally scheduled for 12/23, Friday morning and now pushed back to the afternoon instead ... which, would make sense to give the technicans & specialists more time to stay onboard to do any repairs to the electrical components associated with the azipod, instead of rushing her out to see.

 

 

 

It seemed that the Star left late night earlier in the week doing around 10 knots but took her as fast as almost 13 knots, based on posted tracking data ... and, assumption is that until the systems are fully repaired and operationally safe, she isn't and hasn't been able to go any faster than 10 to 12 knots. Is that a fair assumption ?

 

 

nothing is changed with the departure time in hong kong.

 

 

 

Sent from my iPhone using Tapatalk

[Circusboy354]

Sorry to hear that & thank you for keeping us updated with onboard news ... Was wondering as it's Saturday in VN but Friday evening in the US mainland. Marinetraffic tracking not updating but obviously, ship is still at sea with light chops, cloudy skies, etc. and not appeared to be anywhere near the coastline.

 

Chan May in 2 days - isn't that also going to be a tendering port, hopefully - it will give folks a chance to exercise those sea legs. Hopefully, luck will be on your side.

 

The revised schedule with the conflicting departure time, it seemed, has to do with sailing/leaving HK at 7 AM originally scheduled for 12/23, Friday morning and now pushed back to the afternoon instead ... which, would make sense to give the technicans & specialists more time to stay onboard to do any repairs to the electrical components associated with the azipod, instead of rushing her out to see.

 

It seemed that the Star left late night earlier in the week doing around 10 knots but took her as fast as almost 13 knots, based on posted tracking data ... and, assumption is that until the systems are fully repaired and operationally safe, she isn't and hasn't been able to go any faster than 10 to 12 knots. Is that a fair assumption ?

 

 

We left Singapore at Midnight Tuesday into Wednesday and have been at sea since, doing an average of 10 knots, from what I've noticed as low as 6 and high as 14 for a short period. Chan May is docked, they're currently trying to see if that's available tomorrow and have another reschedule.

 

I was really surprised and almost amused to see a large number of people around the ship at 7.30 am this morning with backpacks etc thinking they were going ashore.

 

At this stage I think we're just on a surprise adventure now, the only guarantee is that we'll be in Hong Kong on or before the 22nd. Right after they official announcement that Nha Trang was cancelled the internet went down for an hour. Sea conditions last night were 'very rough' and have been downgraded today to 'rough' although it feels rougher now than earlier.

[karoo]

We left Singapore at Midnight Tuesday into Wednesday and have been at sea since, doing an average of 10 knots, from what I've noticed as low as 6 and high as 14 for a short period. Chan May is docked, they're currently trying to see if that's available tomorrow and have another reschedule.

 

I was really surprised and almost amused to see a large number of people around the ship at 7.30 am this morning with backpacks etc thinking they were going ashore.

 

At this stage I think we're just on a surprise adventure now, the only guarantee is that we'll be in Hong Kong on or before the 22nd. Right after they official announcement that Nha Trang was cancelled the internet went down for an hour. Sea conditions last night were 'very rough' and have been downgraded today to 'rough' although it feels rougher now than earlier.

 

 

It certainly has become your mystery cruise. I'm sure you must know every inch of the ship by now. Here's hoping all the people who packed their backpacks get to use them soon!

 

 

Sent from my iPhone using Forums

[Circusboy354]

There is another ship in port at Chan May tomorrow, they leave at 6pm and we're docking at 7pm for an overnight, Sanya and our arrival in Hong Kong remain unchanged. Although it's been challenging I feel that NCL have done all they can to make the best out of our situation.

 

I've seen complaints from those on the 22nd Dec sailing, as far as I can tell they are still putting a plan in place to have three ports, all with overnight stays to allow them to work on the Azipod. It's a shame they will probably miss some of the ports that in my opinion would be the better ports in that itinerary but at the end of the day it's something out of everyones control now.

[karoo]

There is another ship in port at Chan May tomorrow, they leave at 6pm and we're docking at 7pm for an overnight, Sanya and our arrival in Hong Kong remain unchanged. Although it's been challenging I feel that NCL have done all they can to make the best out of our situation.

 

I've seen complaints from those on the 22nd Dec sailing, as far as I can tell they are still putting a plan in place to have three ports, all with overnight stays to allow them to work on the Azipod. It's a shame they will probably miss some of the ports that in my opinion would be the better ports in that itinerary but at the end of the day it's something out of everyones control now.

 

 

[emoji106]

 

 

Sent from my iPhone using Forums

[don't-use-real-name]

It appears that the maintenance work is being done in the safe confines of a

port instead of at sea. Also it appears that the work necessary is not under

water or the hull. In either of these cases the exterior azipod would not be

done with divers - at sea no-way unless NCL is filming the latest Mission

Impossible movie. At port in the murky bottom of the port how could anyone

see what was to be done if at all - the reason for dry-docking.

NCL would not want to be tinkering with only one useable azipod while at sea

avoiding the trauma of the likes of the Carnival Triumph (dead in the water).

 

So it must be related to something electrical or perhaps computer software

not propelling the ship as it should. Being tied up at port minor tweaking of

the non responding azipod could be done until a fixing solution is found.

 

Fortunate that tweaking can be done with adjustments to the port schedules

so something can be salvaged out of the cruise instead of the disappointing

total loss when ferrying from the Pacific Coast to the Bahamas when it came

out of dry-dock.

 

Comments from our readers ?

[chengkp75]

Sorry to hear that & thank you for keeping us updated with onboard news ... Was wondering as it's Saturday in VN but Friday evening in the US mainland. Marinetraffic tracking not updating but obviously, ship is still at sea with light chops, cloudy skies, etc. and not appeared to be anywhere near the coastline.

 

Chan May in 2 days - isn't that also going to be a tendering port, hopefully - it will give folks a chance to exercise those sea legs. Hopefully, luck will be on your side.

 

The revised schedule with the conflicting departure time, it seemed, has to do with sailing/leaving HK at 7 AM originally scheduled for 12/23, Friday morning and now pushed back to the afternoon instead ... which, would make sense to give the technicans & specialists more time to stay onboard to do any repairs to the electrical components associated with the azipod, instead of rushing her out to see.

 

It seemed that the Star left late night earlier in the week doing around 10 knots but took her as fast as almost 13 knots, based on posted tracking data ... and, assumption is that until the systems are fully repaired and operationally safe, she isn't and hasn't been able to go any faster than 10 to 12 knots. Is that a fair assumption ?

 

One pod should give her about 16-18 knots. Horsepower to speed for a ship is exponential, so the last few knots require a whole lot of power.

[chengkp75]

It appears that the maintenance work is being done in the safe confines of a

port instead of at sea. Also it appears that the work necessary is not under

water or the hull. In either of these cases the exterior azipod would not be

done with divers - at sea no-way unless NCL is filming the latest Mission

Impossible movie. At port in the murky bottom of the port how could anyone

see what was to be done if at all - the reason for dry-docking.

NCL would not want to be tinkering with only one useable azipod while at sea

avoiding the trauma of the likes of the Carnival Triumph (dead in the water).

 

So it must be related to something electrical or perhaps computer software

not propelling the ship as it should. Being tied up at port minor tweaking of

the non responding azipod could be done until a fixing solution is found.

 

Fortunate that tweaking can be done with adjustments to the port schedules

so something can be salvaged out of the cruise instead of the disappointing

total loss when ferrying from the Pacific Coast to the Bahamas when it came

out of dry-dock.

 

Comments from our readers ?

 

The controls for each pod are separate, so "tinkering" with the non-operational pod would have no effect on the operational one. As for the Triumph, she was dead in the water because no generators were functioning, not because of propulsion issues.

 

Quite a lot of work can be done in port with divers. We overhauled a stern thruster using divers, over 7 days in 4 ports. In between ports, all the loose items like the thruster propeller blades and such were chained into the tunnel, and then taken out again and hung off the hull to allow the divers to work at each port.

 

Things like the propeller shaft seal on the azipod or bent blades, or even removal of blades if the pod bearings had failed and the shaft needed to be locked from turning, can be done by divers. The only thing that requires a drydock would be bearing replacement in the pod.

 

It is likely the control circuit for the variable frequency drive, or the power rectifiers themselves that handle the 19Mw of power to the pod motor that are being troubleshot and repaired.

[karoo]

The controls for each pod are separate, so "tinkering" with the non-operational pod would have no effect on the operational one. As for the Triumph, she was dead in the water because no generators were functioning, not because of propulsion issues.

 

 

 

Quite a lot of work can be done in port with divers. We overhauled a stern thruster using divers, over 7 days in 4 ports. In between ports, all the loose items like the thruster propeller blades and such were chained into the tunnel, and then taken out again and hung off the hull to allow the divers to work at each port.

 

 

 

Things like the propeller shaft seal on the azipod or bent blades, or even removal of blades if the pod bearings had failed and the shaft needed to be locked from turning, can be done by divers. The only thing that requires a drydock would be bearing replacement in the pod.

 

 

 

It is likely the control circuit for the variable frequency drive, or the power rectifiers themselves that handle the 19Mw of power to the pod motor that are being troubleshot and repaired.

 

 

Love your insightful comments! Why would they only be doing 6 knots at some stages?

 

 

Sent from my iPhone using Forums

[chengkp75]

Love your insightful comments! Why would they only be doing 6 knots at some stages?

 

 

Sent from my iPhone using Forums

 

At higher speeds, the non-operational pod propeller is "freewheeling" or turning like a pinwheel held outside a car's window. This reduces drag. But if they were trying to start the non-op pod at low power, they would need to slow down so they could see whether the pod was responding to power from the variable frequency drive or just getting "jump started" from freewheeling. Tells me their working on it as they proceed.

[anthony604266]

22 HK

23 HK

24 At sea

25 Chan May, Vietnam

26 Chan May, Vietnam

27 At sea

28 Plu My, Vietnam

29 Plu My, Vietnam

30 At Sea

31 At Sea

1 Jan Leam Chabang, Thalland

2 Jan At Sea

3 Jan At Sea

4 Jan Singapore

5 Jan Singapore

 

I have cancelled my cruise for a full refund This is a nightmare no stops days at sea ship not functioning properly sea state south china sea 5-7 the whole cruise.

 

Take the money and run

[mking8288]

There is another ship in port at Chan May tomorrow, they leave at 6pm and we're docking at 7pm for an overnight, Sanya and our arrival in Hong Kong remain unchanged. Although it's been challenging I feel that NCL have done all they can to make the best out of our situation. I've seen complaints from those on the 22nd Dec sailing, as far as I can tell they are still putting a plan in place to have three ports, all with overnight stays to allow them to work on the Azipod ... but at the end of the day it's something out of everyones control now.

Absolutely agreed, NCL in this instances really gone above board with the compensation & arrangements. Read on another site that some felt the 50% off had to be used within a year or lose it and that it's not transferrable as being unfair (translations - cannot be sold or "bartered" with) - :rolleyes: - while one is still sailing, lodging & food onboard, etc. I don't see those doing Atlantic 6 or 7 day crossings making a sting about not going ashore - well, expectations are different - "things" happened and I am sure NCL did not wished for or plan for it to happen.

 

Good thing that majority or almost all the pax are in good spirit and enjoying, making the best of the unfortunate situation. Earlier this week, we looked at the 22nd. sailing and NCL (were) still selling it - could've possibly book it & gotten quite a deal (if we only have unused vacation time for 2016 left) - just relax on the ship, eat, have fun and go ashore ... whenever. Hopefully, folks can make dinner in Chan May - get some fresh Papaya Salad, Cha Gio, Coi Cuon, hot bowl of Pho and icey Cafe Sua Da from the locals.

 

One pod should give her about 16-18 knots. Horsepower to speed for a ship is exponential, so the last few knots require a whole lot of power.

Thanks. We've been on quite a few sailings where it's common for the ship to not run on all the engines / azipods unless top speed is needed ... just like automotive engine, beyond the optimal range - it will burn more fuel & if seas are rough, not a good ride for most.

 

We're on the GEM and she ran almost 25 knots with a strong tail wind, for probably 12+ hours to race away from an incoming Nor-Easter, hugging the East Coast & that was one heck of a roller coaster ride. Until that cruise, we didn't realize that the Jewel/Dawn class ships can go that fast.

[teamflames]

I am not experienced with these matters but the refund and 50% sounded very reasonable to us but wondering why the cruise for 22nd which is similarly affected is not getting the exact same offer?

Also, considering ncl has made it clear that further itinerary changes are possible and the ports they are stopping at are industrial ports a long way from the "attractions" shouldn't excursions or at least shuttles be put on at no charge????

 

 

Sent from my iPod touch using Forums