Lesson previewControl, State, Gate, Localise1 section shown
Preview lesson
Control, State, Gate, Localise
What you will learn
Use one repeatable troubleshooting loop that controls the boat, states the observable symptom and opens only the adjacent evidence boundary.
Troubleshooting is disciplined uncertainty management. The first job is vessel control, then a precise symptom state, critical-warning gate, system boundary, one safe check and a condition-matched verification—not a favourite part.
Separate navigation from diagnosis. Establish lookout, steerage, traffic and drift control before asking anyone to enter a machinery space or look down at a panel. If propulsion loss can narrow safe options, use sail, anchor, open water or assistance early as the actual boat and conditions permit.
State what the engine did in observable terms: no response, click, slow or normal crank, starts then stops, warning under load, persistent smoke with power loss, new vibration, or runs without transmitting thrust. Add when it occurred, load, temperature, warnings, recent work and what changed immediately before it.
Apply critical stop gates before searching for a cause. Oil-pressure, cooling, smoke, fire, fuel spray, high current, exhaust or carbon-monoxide evidence, severe vibration and uncertain transmission integrity can veto continued running. Then localise the last supported system claim and make one cool, isolated, exact-manual operator check. Record the result before another change.
Choose an observed state, identify the evidence edge and keep later claims open until a safe check and matched retest support them.
Worked example
During a harbour departure the engine responds normally in neutral, but ahead produces new heavy vibration and little thrust.
- 1Control the boat first: disengage or reduce demand, keep lookout and preserve space rather than repeatedly loading the drivetrain.
- 2State the symptom as gear/load dependent. Engine response in neutral does not prove the torque-to-propeller path.
- 3Keep control cable, gearbox, coupling, shaft or saildrive, propeller fouling/damage and mounts open; inspect only isolated visible boundaries and use a contingency before options narrow.
Sense check: 'The propeller is fouled' is plausible, but the evidence currently supports only a propulsion-boundary fault and an unsafe reason to stop loading it.
| Observed state | Last claim supported | Adjacent open boundary |
|---|---|---|
| No response | Start requested | Control state, supply, interlock, high-current path, starter or seized load |
| Normal crank, no fire | Electrical rotation | Run/stop state, fuel continuity, air, compression and exact start procedure |
| Runs, warning under load | Combustion and loaded operation | Named warning channel and its physical system condition |
| Runs, no thrust | Engine torque may exist | Control, gearbox, coupling, shaft or saildrive and propeller |
Make a six-line fault report
A crew member or remote mechanic needs information that preserves evidence and vessel safety.
1. Control
State boat position, traffic, drift, steerage and current fallback.
2. State
Name the exact crank, run, load, smoke, warning, vibration or thrust condition.
3. Gate
Report every critical alarm, leak, heat, smell, fume, noise or electrical cue.
4. Trace
Name the last system stage actually supported and the one safe check already made.
Sense check: A precise report creates better decisions than a parts theory while preventing multiple people from changing different boundaries at once.
Common mistake or limitation
- Diagnosing a component from the first symptom before controlling the vessel and naming the operating state.
- Treating a silent or cleared alarm as permission to ignore heat, leakage, fumes or abnormal sound.
- Changing several plausible items before recording which condition changed the evidence.
Recap
- Control boat → state symptom → gate warnings → localise → check one thing → verify or abort.
- Keep the conclusion no stronger than the last supported stage.
- Safety-critical uncertainty is a reason to stop and escalate, not to force a diagnosis.
Optional quick check
Section 1 of 1