8.3 Thruster Interaction & Faulty Thruster Response

When thrusters fight the water (and each other)

Even a healthy thruster does not always deliver its nameplate force into useful ship motion. Interaction effects redirect or cancel thrust. Separately, faults make a thruster behave unlike its command. Both topics appear in NI assessments because they explain unexpected footprint growth, unexplained power draw, and the need to deselect a unit before it becomes a drive-off engine.

Thruster–hull interaction and the Coanda effect

When thruster wash flows along or against the hull instead of freely into open water, part of the momentum never becomes free-stream force on the vessel. A common teaching label is the Coanda effect: a jet tends to attach to a nearby surface. On ships this appears as thruster race hugging the hull plating, reducing the effective force vector TAL assumed.

Designers place thrusters and define forbidden zones partly to avoid the worst interaction sectors. Allocation algorithms may also derate expected force for known bad angles. As DPO you should not redesign the hull mid-watch, but you should recognise: thrusters at high load with disappointing motion may mean interaction or power limit, not only “weather heavier than forecast.”

Thruster–thruster interference

Two azimuth thrusters aimed so their races cross, or a tunnel thruster blasting into a nearby azimuth disc, create interference. Net force is less than the vector sum of ideal individual thrusts. In extreme cases one thruster “starves” or overloads. Symptoms can include:

• high power for modest position correction,
• oscillation as TAL and thrusters chase a poor efficiency region,
• local alarms on thruster load or temperature,
• footprint larger than capability plots predicted for that thruster set.

Mitigation is mostly configuration and procedure: forbidden zones, preferred azimuth policies, minimum separation of commanded angles, and not forcing manual thruster angles into known bad sectors during critical work.

Faulty thruster responses you must recognise

Interaction is hydrodynamics. Faults are control or machinery failures. High-yield exam and simulator modes include:

Locked azimuth: the unit cannot slew to the angle TAL wants. If the system correctly detects the lock, it should alarm and the thruster should be treated as direction-constrained or taken out. If detection is late, TAL may command an angle the thruster cannot achieve while still counting partial force — residual errors grow.

Runaway: the most dangerous thruster fault for nearby assets. A thruster producing large uncommanded force drives the vessel off position (drive-off). Immediate priorities: recognise the thruster, emergency stop / deselect / isolate per vessel procedure, and use remaining thrusters or independent joystick/manual modes as trained — not endless menu browsing while the vessel walks toward the platform.

Loss of feedback: without reliable RPM/pitch/azimuth feedback, closed-loop confidence collapses. Many systems alarm “feedback failure” and may auto-deselect. Operator action if not auto-cleared: deselect the thruster, confirm TAL redistributes, and treat capability as reduced until the unit is proven healthy.

Deselect and isolate: the DPO’s protective action

Deselecting a thruster tells the DP system: do not allocate demand to this unit; do not count it in the force solution. Isolation (local emergency stop, pitch to zero, breaker open — vessel-specific) ensures the thruster cannot physically produce force even if electronics glitch.

Deselecting a healthy thruster “to see what happens” during critical work is poor practice. Deselecting a faulty thruster is required good practice. Leaving a runaway selected while hoping auto-modes fix it is how drive-offs escalate.

[!IMPORTANT] A thruster that will not follow command, will not report feedback, or produces uncommanded thrust is a liability in the thruster set. Deselect/isolate first; troubleshoot second once the vessel is safe.

Consequence for the capability plot

A DP capability plot (polar diagram) shows theoretical limiting weather for each relative heading — usually for intact thrusters and for post worst-case single failure. When you deselect a thruster or lose one to fault:

1. You are no longer on the intact curve you may have briefed.
2. Depending which thruster failed, you may be at or beyond the designed worst-case envelope — or in a worse non-design case if multiple thrusters are out.
3. Consequence analysis online should reflect the new thruster set; if it alarms, treat it as real.
4. Operational response: reduce concurrent risk, improve heading if a better sector remains, restore thrusters/power, or leave the location per ASOG.

Capability plots are theoretical and assume thrusters deliver expected force. Interaction losses and partial faults mean real footprint can be worse than the plot — another reason footprint monitoring and residual awareness matter live.

Worked fault scenario

During Auto DP beside a platform, the starboard stern azimuth azimuth feedback freezes at 180° while TAL commands 90°. Command–feedback error alarms. Position starts to walk as force is not where the model expects. The DPO deselects the thruster, confirms remaining units take load, checks consequence analysis and thruster page, notifies the engineer, and pauses the critical external operation per ASOG amber/red criteria. Had the thruster instead run away to full thrust, the same deselect/e-stop discipline would be even more urgent to stop a drive-off.

Exam traps for interaction and faults

Bottom line: expect interaction to steal force; configure zones and watch efficiency. Treat locked azimuth, runaway, and lost feedback as faults that demand deselect/isolation, then reassess capability and operational status before continuing critical work.