Question 1

Your crew starts using a new, longer, more pointed creel toggle design because it's easier to thread. Does this need any formal review?

Accepted Answer

Yes — any change to deck equipment, however small, can change the risk profile of a task and should trigger a risk assessment review before routine use In the real incident, the newly introduced blue toggle's longer, more pointed design made it easier to inadvertently thread through a loop like a loose PFD becket — a change in entanglement risk that was never assessed because the toggle swap wasn't treated as significant enough to review.

Question 2

Under the ISM Code and as reinforced in Gard's guidance to Members, the Master's overriding authority to make decisions for the safety of the ship and protection of the environment can be overruled by a commercial instruction from the company, such as a charterer's order to sail on schedule.

Accepted Answer

False False. Gard's guidance to Members consistently stresses that the ISM Code (element 5) gives the Master overriding authority and responsibility for safety and pollution prevention decisions — and that companies must ensure this authority is not undermined by commercial pressure. A charterer's or owner's commercial instruction never overrides the Master's safety judgement; Masters who feel pressured are advised to record their decision and reasoning and report it to the company and, where relevant, to their P&I correspondent.

Question 3

A crew member identifies that a piece of safety equipment does not match what is listed on the safety equipment plan. What is the correct way to handle this under the SMS?

Accepted Answer

Raise it as a non-conformity/observation through the SMS reporting process so it is recorded, investigated, corrected, and — if it reflects a wider issue — used to improve procedures or the safety equipment plan itself The ISM Code requires a system for reporting non-conformities, accidents and hazardous occurrences so they can be analysed and corrective/preventive action taken — quietly fixing an issue without recording it loses this opportunity for systemic improvement.