Question 1

A crew member notices a spanner slipped from their tool belt and fell two decks, narrowly missing someone working below, but no one was hurt and no equipment was damaged. What should the crew member do?

Accepted Answer

Report it as a near-miss, since a tool fell and nearly struck someone — this reveals a tethering or procedural gap worth addressing before it happens again with a different outcome The absence of injury this time was largely down to luck (timing and position), not a functioning control — this is exactly the kind of event near-miss reporting exists to capture before luck runs out.

Question 2

A welding job is required on a bracket on the funnel platform, and a separate crew member needs to be positioned just below on a suspended stage for an unrelated inspection task at the same time. What should the Chief Officer do?

Accepted Answer

Treat this as a combined-hazard situation: the falling sparks/hot material hazard from welding directly threatens the worker below, so the tasks should be sequenced (not run simultaneously) or the lower position relocated outside the hot work exclusion zone Falling sparks and hot slag from welding work directly above another worker is a serious burn and fire risk; sequencing the tasks or repositioning is the appropriate control, not relying on the lower worker's PPE or the welder's aim to compensate.

Question 3

A crew member needs to inspect a davit fall wire and, while doing so, accidentally brushes against the release lever, but nothing happens because the davit had already been isolated and the release mechanism secured beforehand. What does this near-miss demonstrate?

Accepted Answer

That the control measure worked exactly as intended — the isolation and secured release mechanism prevented what could have been a serious incident, and this should still be reported as a near-miss for learning purposes A control measure preventing harm is exactly what it's there for — this is a success story for the control, not evidence it was unnecessary. It should still be logged as a near-miss, since near-miss reporting captures situations where the safety margin was tested, even when nothing went wrong.