8.1 Tunnel, Azimuth & Retractable Thrusters
Key Takeaways
- Tunnel (transverse) thrusters sit in a fixed athwartships tunnel and produce port/starboard thrust only — useful for sway and yaw, never for surge
- Azimuth thrusters rotate through 360° so one unit can contribute surge, sway and yaw depending on azimuth angle and load
- Retractable azimuth thrusters lower for DP/manoeuvring and retract into the hull for transit, docking clearance, or to reduce interaction
- Main propellers and rudders may be included in the DP thruster set when they can deliver commanded force/moment under closed-loop control
- Command signals tell the thruster what to do; feedback signals report RPM, pitch, azimuth and status so the controller can close the loop and detect faults
Why thruster types matter on the DPO exam
Thrusters are the actuators of dynamic positioning: they turn controller force demand into real surge, sway and yaw. The Nautical Institute seven-component model lists thrusters as a core component because no thrusters means no station-keeping, regardless of how good the references and computers are. Induction and Simulator assessments test whether you can distinguish thruster types, what each can and cannot do, and how command versus feedback keeps the control loop honest.
You are not expected to design a thruster layout, but you must reason operationally: Can this unit produce fore-and-aft force? What happens if it is offline? Why is that azimuth thruster better placed for yaw? What does a frozen feedback signal mean? This section builds the hardware vocabulary used by thrust allocation (next section) and thruster-fault response (section 8.3).
Tunnel (transverse) thrusters
A tunnel thruster is mounted in a transverse tunnel through the hull — typically at the bow (bow thruster) and sometimes at the stern (stern thruster). The propeller axis is fixed athwartships. Reversing pitch or reversing propeller rotation reverses thrust direction (port ↔ starboard). There is no rotation of the thruster body to aim thrust forward or aft.
| Feature | Tunnel thruster |
|---|---|
| Axis | Fixed transverse (port–starboard) |
| Force | Lateral (sway); yaw if offset from centre of rotation |
| Surge | None — cannot push the vessel ahead or astern |
| Typical locations | Bow (common); stern (when fitted) |
| DP role | Side-force and heading assist; cannot replace main propulsion for surge |
Because tunnels only push sideways, TAL uses them for sway and yaw demand. If weather requires large surge force, tunnels contribute nothing along the ship’s centreline. Multiple bow tunnels improve redundancy for lateral force but still share the same fixed-axis limitation.
Tunnel thrusters can lose effectiveness when the vessel has significant forward speed (air drawn into the tunnel, reduced immersion, or cavitation), and they may be depth/draft sensitive. On DP at near-zero speed these issues are smaller, but shallow draft, heavy roll, or ice/debris ingestion still matter operationally.
Azimuth thrusters
An azimuth thruster (azimuthing thruster, azipod-style unit, or steerable thruster) mounts a propeller on a unit that can rotate in azimuth through a full circle (or nearly so). By changing azimuth angle and thrust magnitude (RPM and/or pitch), one thruster can produce force in any horizontal direction. That force, acting at a lever arm from the vessel’s centre of rotation, also creates yaw moment.
| Feature | Azimuth thruster |
|---|---|
| Axis | Steerable 360° (azimuth angle commanded by DP/TAL) |
| Force | Surge, sway, or any combination in the horizontal plane |
| Yaw | Strong when thrust is directed off the centreline |
| Typical locations | Stern main propulsors; bow/midship auxiliary azis |
| DP role | Highly flexible — often the backbone of station-keeping |
Many DP vessels use stern azimuths as main propulsion for transit as well as DP. That dual role is a strength: the same units that drive the vessel to the field hold it on location. Exam trap: do not say azimuth thrusters “only push sideways” or “have no effect on heading.” They are the opposite — omni-directional and highly effective for heading control.
Azimuth units need time to slew (rotate) when the optimal angle changes. Rate limits, mechanical stops, and forbidden zones (next section) constrain how freely TAL may aim them. Feedback of actual azimuth angle is critical so the controller knows where thrust is really pointing.
Retractable azimuth thrusters
A retractable azimuth thruster is an azimuth unit that can be lowered into the water for DP and manoeuvring and retracted into a hull trunk when not required. When lowered and online for DP, it behaves like other azimuth thrusters: 360° steering and full horizontal force contribution. When retracted, it is usually deselected from the thruster set and contributes no force.
| Advantage | Why it matters |
|---|---|
| Transit efficiency / clearance | Unit stowed out of the flow or for shallow approaches |
| Layout flexibility | Extra DP thruster without permanent underwater appendage drag |
| Dry-dock / ice / damage protection | Can be raised when risk of grounding or ice is high |
| Interaction management | Sometimes raised if wash conflicts with other work (vessel-specific) |
Retractables add deployment status to your mental checklist: is the unit fully lowered, locked, ready, and enabled in DP? A thruster that is mechanically down but not enabled, or enabled but not fully deployed, is a classic capability surprise. Always confirm thruster status pages after configuration changes.
Main propellers and rudders in the thruster set
DP systems do not always ignore conventional main shaft propellers and rudders. Where the vessel has controllable-pitch or RPM-controlled main screws and rudders that can be driven by the DP controller, they may be included as force producers:
- Main propellers primarily contribute surge (ahead/astern). Twin screws offset from centreline also produce yaw when differentially loaded.
- Rudders deflect the propeller race to create lateral force and yaw moment when there is wash over the rudder; at zero speed their effectiveness collapses, so pure rudder “thrust” is limited on DP compared with dedicated thrusters.
On many diesel-electric DP designs, azimuth main propulsors replace traditional shaft + rudder pairs. On hybrid layouts, TAL may allocate among tunnels, azis, and shaft lines together. Exam principle: any actuator the DP system can command and receive feedback from may be part of the thruster set — inclusion is configuration- and vessel-specific, not a universal rule that “mains never count.”
Strengths and limits comparison
| Type | Strengths | Limits |
|---|---|---|
| Tunnel | Simple fixed axis; strong side force; common bow redundancy | No surge; less effective at speed; draft/immersion sensitive |
| Azimuth (fixed hull) | 360° force; surge + sway + yaw; often main propulsion | Slew time; forbidden-zone constraints; wash interaction risk |
| Retractable azimuth | Omni-directional when down; stow for transit/clearance | Deployment dependency; trunk complexity; must be down and enabled |
| Main prop + rudder | Efficient surge; familiar machinery | Rudder weak at low speed; less free force direction than azis |
Command signals versus feedback signals
Every thruster control loop has two directions of information:
| Signal direction | Meaning | Examples |
|---|---|---|
| Command | What DP/TAL tells the thruster to do | RPM demand, pitch demand, azimuth angle demand, enable/start |
| Feedback | What the thruster actually reports | Measured RPM, pitch, azimuth angle, motor load, ready/running/fault |
The controller compares command and feedback. When they match within tolerance, allocation trusts the force model. When they diverge — e.g. azimuth commanded 90° but feedback stuck at 0°, or RPM commanded high but feedback near zero — the system should alarm and may treat the thruster as faulty or ineffective. Operators must also watch this mismatch: a thruster that “looks online” but produces no feedback motion is a drive-off or drift-off hazard if left selected.
[!IMPORTANT] Command is intention; feedback is reality. TAL allocates on the assumption that enabled thrusters deliver approximately what is commanded. Frozen, lost, or wildly wrong feedback is a fault condition, not a display curiosity.
Worked orientation scenario
A DP vessel holds with two stern azimuths, two bow tunnels, and one retractable midships azimuth. Weather is on the beam. TAL aims stern azis partly athwartships, loads bow tunnels for sway, and uses the midships unit for extra lateral force. The DPO then realises the retractable is still stowed from transit — it shows deselected. Capability is less than the pre-entry briefing assumed. After lowering, enabling, and verifying feedback (azimuth tracking, RPM responding), the footprint tightens. Lesson: thruster type capability only exists when the unit is physically available, enabled, and feeding healthy feedback.
Exam traps for thruster types
| Trap | Correct framing |
|---|---|
| “Tunnel thrusters rotate 360°” | Tunnels are fixed axis; azis rotate |
| “Azimuth thrusters only do sway” | Azis contribute surge, sway and yaw |
| “Retractables cannot be used for DP” | They are commonly used when lowered |
| “Main propellers are never in DP” | They may be included when commanded by DP |
| “Feedback is optional decoration” | Feedback closes the loop and supports fault detection |
Bottom line: match the thruster type to its force envelope — tunnels for fixed lateral force, azimuths (including retractables when deployed) for steerable omni-directional force, and optional main prop/rudder contribution for surge and yaw. Always separate commands (demands) from feedback (actual response) when diagnosing thruster behaviour.
Which statement about a tunnel (transverse) thruster is correct?
Why is an azimuth thruster especially useful in a DP thruster set?
What operational advantage does a retractable azimuth thruster offer?
In thruster control, what is the essential difference between a command signal and a feedback signal?