Study MED2 by converting each engine-room system into a fault tree: a symptom at the top, candidate causes below, and the specific observation that distinguishes them. Work through cooling, lubrication, fuel and fixed safety systems this way, test your trees against vessel walkthroughs and paper scenarios, and finish with explicit readiness checks before booking any assessment.
Why one symptom has several causes: the core MED2 difficulty
MED2 content centres on machinery where identical symptoms, such as rising temperature or falling pressure, arise from unrelated faults. Effective study isolates the single observation that discriminates between causes, then links it to the correct decision.
Consider rising jacket water temperature. On a raw-water-cooled engine it may mean a blocked suction, a failed impeller or a slipping belt; on a heat-exchanger engine the raw-water side and the freshwater circuit fail differently. If you memorise 'overheating: check water', you cannot answer a follow-up about what you would look at first, because the discriminating observation differs between arrangements.
Build the separation into your notes deliberately. For each system, write the symptom, list three or four plausible causes, and beside each cause write the one check that rules it in or out, such as exhaust discharge, dipstick level, filter vacuum or bilge level. When two causes share no discriminating check, you have found a gap in your understanding worth closing. This structure also mirrors how a safe decision is reached: observe, separate, then act.
This approach matters because engine-room competence is judged on decisions under uncertainty. A driver who knows that a symptom has four causes but cannot name the separating observation cannot justify shutting down versus reducing load, and that justification is the substance of the subject.
- Symptom first: start every study note from an observable condition, not from a component list.
- One separating observation per cause: if you cannot name it, flag the topic for a vessel walkthrough.
- Decision last: attach the response, such as reduce load, stop, or isolate, to each cause rather than to the symptom generally.
Cooling systems: separating raw water, heat exchanger and keel cooling
Cooling appears in three common arrangements on domestic commercial vessels. Each rejects heat at a different point, so the observation that identifies a fault, especially exhaust discharge, differs between them.
In a raw-water system, seawater is drawn through a seacock and strainer, pumped through the engine and expelled, often via the exhaust. In a heat-exchanger system, a closed freshwater circuit cools the engine and a separate raw-water circuit cools that freshwater through the heat exchanger. In keel cooling, engine heat is rejected through external or tank-mounted pipes, so there is no seawater circuit through the block at all.
Worked scenario one: an engine's temperature climbs while under way. A plausible mistake is to treat all overheating alike and immediately shut down, losing the observations that identify the cause. The better decision is a quick structured look: is there a solid discharge of seawater at the exhaust outlet? A weak or absent discharge points to the raw-water side, such as a blocked strainer or a damaged impeller, so you would reduce load and close the cooling suction as appropriate. A strong discharge with high temperature points to the closed circuit, such as a stuck thermostat or low coolant, so you would check the header tank. Why it matters: the remedies, the shutdown urgency and the report you log differ completely, and acting on the wrong branch can turn a strainer clean-out into a salvage job. Practise this split on paper until the two branches feel automatic.
| Arrangement | Where heat is rejected | Key observation points | Practical implication |
|---|---|---|---|
| Raw water | Direct to sea via the engine and exhaust | Exhaust outlet discharge, strainer bowl, pump condition | Suction blockage or impeller failure stops flow visibly at the exhaust |
| Heat exchanger | Freshwater circuit transfers to a raw-water circuit | Header tank level, exchanger outlets, exhaust discharge | Raw-water and freshwater faults must be diagnosed on separate branches |
| Keel cooling | Through external piping or a tank | Coolant level, pipe fouling, temperature trend against load | No seawater through the engine, so marine-growth fouling is the watch item |
Lubrication: pressure, flow and the low-oil-pressure decision
Lubrication study must distinguish oil pressure from oil distribution, because a gauge reading alone does not locate the fault. The decision at low pressure is whether to keep running, and the separating observations decide it.
Pressure reflects resistance in the system: a blocked filter or a faulty relief valve can hold pressure while starving a bearing, and a worn pump or diluted oil can drop pressure while flow continues somewhere. On a study note, list the causes of low indicated pressure, then attach the check that separates each: dipstick level and oil condition, filter condition, recent temperature behaviour, and any warning devices fitted to the engine.
Worked scenario two: during a watch, the lubricating oil gauge falls below its usual reading while the engine sounds normal. A plausible mistake is to top up oil and continue at full load, treating the gauge as a level indicator and pressing on toward the destination. The better decision is to reduce load, verify the level and condition on the dipstick, and if the level is correct and the reading stays low, stop the engine and investigate rather than run it further. Why it matters: a bearing running on thin or insufficient oil can fail within minutes, and the cost of stopping to investigate is small compared with a seizure in a shipping channel or a tow home. Rehearse the sequence in words, reduce, verify, decide, because the exam-style question and the real watch both reward the same ordering.
- Dipstick first: level and appearance of the oil separate consumption, dilution and leaks from internal causes.
- Trend beats a snapshot: compare the reading with the same load and temperature as previous watches.
- Report and record: whatever the decision, log the observation, the action and the reason in the engine record.
Fuel and combustion: reading smoke and tracing the fuel path
Exhaust smoke colour is a separating observation for combustion problems, and the fuel supply path from tank to injector is the trace you must be able to walk. Restriction, air and water each leave different evidence.
Black smoke points to incomplete combustion from excess fuel or insufficient air, so the trace runs to the air side, such as a choked filter, as well as to injection quality. White or bluish smoke points to unburnt or burning oil or water entering the cylinders. Sketch the full fuel path: tank, shutoff, water separator, filters, lift or supply pump, injectors, and return line, marking the test point at each stage.
Trace a paper example: an engine loses power under load and smokes heavily. If you jump to 'dirty fuel', you may change filters and gain nothing when the true branch is an air restriction. The structured move is to check the air path first, since it is fast and safe, then check filter condition and water in the separator, then injector behaviour. Note where air can enter a fuel line, because bleeding procedures differ between engines and air after a filter change is a common self-inflicted fault. Add the operational rule that fuel-system work, like any machinery intervention, is reported and recorded so the next watch inherits the history rather than the mystery.
- Air path before fuel path: it is the quickest, safest separating check for black smoke under load.
- Water in the separator: inspect the bowl routinely and treat any water as a tank-level and filling-practice question.
- Bleeding order: know your engine's sequence so a filter change does not become a no-start.
Bilge, fire and steering: fixed systems and the SMS that governs them
Beyond the main engine, MED2 covers bilge pumping, fire detection and suppression, and steering gear, together with the safety management system and records that tie them into daily operation.
For bilge systems, study pump types, check valves, strum boxes and the bilge alarm, and be able to explain why a pump that runs may still fail to pump: a blocked strum box, a leaking suction or an open cross-connection. For fire protection, know the fixed arrangements fitted to small commercial vessels, portable extinguisher selection by fire class, and the routine checks that keep both usable. For steering, understand the drive arrangements, emergency steering provisions and the value of testing them before a passage rather than during one.
Tie these to documentation, because Australian domestic commercial vessels operate under the National Standard for Commercial Vessels framework and under a safety management system that AMSA administers through its marine orders. Practise writing a short entry for each system: bilge alarm tested before departure, extinguisher gauges checked monthly, steering tested and logged. Then reverse it: given an entry that says 'pump ran, level unchanged', decide what you would do next and where you would look. That two-way practice, system to record and record to decision, is the applied form of this part of the syllabus and it is where the knowledge becomes operational rather than list-like.
- Pump runs, level unchanged: work the causes, strum box, suction leak, valve state, before assuming the pump is sound.
- Fire class before extinguisher type: match the agent to the fire, and know where each unit is and whether it is charged.
- Emergency steering: know the vessel's arrangement and rehearse the changeover on paper before you need it.
Self-check exercise: build and stress-test an overheating fault tree
Construct a fault tree for rising jacket temperature on a paper vessel of your choosing, then test it against a walk-through or a set of invented observations until every branch has a separating check.
Choose one arrangement, say a heat-exchanger engine with a raw-water circuit. Draw the symptom at the top and branch to at least four causes: blocked raw-water strainer, failed impeller, low coolant or air lock in the closed circuit, and stuck thermostat. Under each branch, write the observation that separates it, such as exhaust discharge strength, strainer bowl condition, header tank level, and temperature behaviour at different loads. Score yourself against the rubric below and repeat for a raw-water-only engine so the branches stop blending together.
Stress-test the tree with invented evidence. For example, write yourself the case: strong exhaust discharge, header tank an hour after topping up, temperature normal at low load and high at cruising speed, and check that your tree sends you to the thermostat and coolant-branch, not to the raw-water branch. If a branch has no separating observation, close the gap using the vessel itself: open the strainer, find the header tank, trace the keel-cool or exchanger pipework. Expected observations are concrete, a clear discharge, a half-full bowl, a marked level, so record what you actually saw and where, and revise the tree the same day while the walk-through is fresh.
- Rubric, 4 points: four or more distinct causes, each with its own separating observation.
- Rubric, 3 points: causes are distinct but two share an observation; identify which and refine.
- Rubric, 2 points or below: the tree mixes raw-water and closed-circuit branches; redraw with the table above alongside.
- Milestone: you can reproduce the tree from memory on a blank page within ten minutes. This is a learning milestone only, not a prediction of any assessment outcome.
An adaptable preparation sequence and concrete readiness checks
Sequence your preparation from system mapping through fault trees to scenario practice and record-keeping drills. Finish when you meet explicit readiness checks, not when your notes look complete.
A flexible sequence: first, map the syllabus onto a real or paper vessel, listing every system you must know and where it physically sits. Second, build a fault tree for each major system using the method above, one or two systems per session. Third, walk the vessel and verify every separating observation by eye, revising the trees. Fourth, run paper scenarios, invented symptoms and evidence, and practise the decision sequence out loud. Fifth, drill the records: write the log entries an SMS expects for tests, faults and interventions. Sixth, review AMSA's published incident summaries and news to see how system failures appear in real reports, then ask which branch of your trees each report illustrates.
Readiness checks to finish: you can sketch the fuel, cooling and lubrication paths of your reference engine from memory with test points marked; you can state the separating observation and the decision for at least four causes of overheating and of low oil pressure without notes; you can explain what a bilge pump and a fixed fire system each need to actually work, not just what they are called; and you can write a correct log entry for a machinery fault and its response. Where any check fails, return to that system's tree rather than rereading general notes. One short note: administrative details, including eligibility, sea service and assessment arrangements, belong to AMSA and should be confirmed on its website when planning your timeline.
- Check one: blank-page sketches of the three fluid paths with test points marked.
- Check two: spoken decision sequences for overheating and low oil pressure, cause by cause.
- Check three: for bilge, fire and steering, the operating test you would perform and the entry you would write.
- Check four: two paper scenarios answered with reduce, verify, decide, and a log entry for each.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.