Question 1

During your oral exam you are asked: a junior engineer under your supervision repeatedly takes shortcuts during routine watchkeeping rounds — skipping certain checks they consider "unnecessary" — but their work is otherwise competent and they have not yet caused an incident. How do you address this as Chief Engineer?

Accepted Answer

Address the behaviour directly, explaining the purpose of each check being skipped (linking it to specific failure modes it is designed to catch) so the engineer understands the "why" rather than just the "what", and monitor to confirm the behaviour changes, escalating through documented coaching/formal process if it does not Routine checks often exist because of specific historical failure modes that may not be obvious to less experienced personnel, and shortcuts that have not yet caused an incident represent latent risk rather than absence of risk — "nothing has gone wrong yet" is not evidence that the check is unnecessary. Effective supervision addresses the root cause (often a lack of understanding of why a check matters, or time pressure) through explanation and engagement rather than punitive action for a first occurrence, while removing checks based on a junior engineer's unverified judgement that they are "unnecessary" risks normalising the erosion of the safety management system across the whole department.

Question 2

Gard's loss prevention guidance repeatedly highlights that many serious incidents follow a 'normalisation of deviance' — small departures from procedure that become accepted because nothing went wrong before. As Master, what's the most effective way to counter this on board?

Accepted Answer

Actively encourage crew to raise near-misses and procedural drift without fear of blame, and personally follow the same standards you expect of others Gard's guidance on human factors and safety culture identifies normalisation of deviance — where shortcuts that 'worked fine last time' quietly become the new normal — as a precursor to many serious casualties. The most effective defence is an open reporting culture for near-misses and minor deviations, combined with visible leadership from the Master, who sets the tone for what is and isn't acceptable on board.

Question 3

Gard's guidance on near-miss reporting notes that crew sometimes hesitate to report their own minor errors or close calls. As an OOW, why does Gard say this matters for the wider fleet, not just your own ship?

Accepted Answer

Near-miss data, shared and analysed across a fleet (and via schemes like CHIRP Maritime), helps identify recurring risks before they cause a serious incident elsewhere Gard's loss prevention work draws heavily on aggregated near-miss and incident data — including confidential schemes such as CHIRP Maritime — precisely because a near-miss on one vessel is often a warning sign for a hazard that exists across many similar ships. A culture where OOWs report close calls without fear of blame is one of the cheapest and most effective loss-prevention tools available.