A safety concern raised the wrong way vanishes; raised the right way it triggers legal machinery an owner cannot ignore. Both the mechanisms and the protections already exist — they are simply under-used.
A deckhand notices a davit winch that judders under load and mentions it to the bosun, who is busy; a stewardess feels a rotation of consecutive eighteen-hour days has stopped being safe. Nothing is written down, nothing changes, and the concern quietly dies — until it becomes a near-miss, or worse. On yachts the barrier is rarely the absence of rules; it is a crew that does not know the reporting route exists, and a fear that raising it ends a career.
Onboard safety complaints on a commercially registered or chartering superyacht are not a matter of goodwill; they sit inside two binding instruments. The Maritime Labour Convention 2006 — the seafarer's bill of rights — obliges every ship to carry onboard complaint procedures a crew member can use without fear of victimisation, and gives the seafarer the right to escalate to the flag state and to be accompanied through the process. Its remit covers hours of rest, accommodation, medical care, safety and the working environment.
The International Safety Management (ISM) Code sits alongside it and governs the safety system itself. Any yacht of 500 gross tonnes or more in commercial use must operate a documented Safety Management System (SMS), which requires that hazards, near-misses and non-conformities be reported, analysed and corrected. Where MLC 2006 protects the person raising the concern, the ISM Code compels the company to have a system that receives, records and acts on it. A crew member invoking either is exercising a legal right, not asking a favour.
Under MLC 2006, every yacht within scope must carry a written onboard complaint procedure and give each seafarer a copy. It sets out an escalating path: raise the matter first with the head of department or the officer directly responsible, then with the master, with defined points at which it moves ashore if unresolved. The crew member may be accompanied or represented at every stage, and the procedure must name the flag-state contact and the shore-based route in case the ship-level steps fail.
In practice the procedure is often a laminated page nobody reads until a crisis. Failures cluster in predictable places: crew are never actually handed the document at induction; the person to complain to is the person the complaint is about; concerns are raised verbally so no record exists; and on a small crew the fear of being labelled difficult overrides the paper right. The remedy is procedural discipline — issue the document at sign-on, log every concern in writing with a date, and treat the escalation ladder as a live tool rather than a compliance artefact filed and forgotten.
The ISM Code's safety culture rests on a single unglamorous discipline: reporting the incident that did not quite happen. A parted mooring line that injures no one, a tender that came alongside too fast, a fire door propped open — each is a near-miss the SMS is designed to capture, analyse for root cause, and close out with corrective action. A yacht generating no near-miss reports is not a safe yacht; it is a yacht where nobody is reporting.
The value lies in acting on the small signals. A functioning SMS treats a near-miss report as a gift, not an accusation, because it is the cheapest possible warning of the accident it forestalls.
When a concern is not resolved onboard, MLC 2006 and the ISM Code provide a defined ladder that reaches well beyond the yacht. Knowing the rungs — and that each is a legitimate right — is what turns a private grievance into an obligation the owner and manager must answer.
| Stage | Raise it with | What it triggers |
|---|---|---|
| Onboard, informal | Head of department / bosun | Immediate correction; logged as hazard or near-miss in the SMS |
| Onboard, formal | The master, in writing | Formal complaint recorded; investigation; documented response |
| Shore-side | The DPA (Designated Person Ashore) | Direct line to top management; SMS review; corrective action |
| Flag state | Yacht's flag administration | External oversight; may direct the company or inspect |
| Port State Control | PSC in the port of call | Inspection; deficiencies logged; detention if serious |
| Labour dispute | Flag state / competent authority | MLC 2006 complaint handled by the state, seafarer accompanied |
Each rung exists precisely so a concern need never dead-end onboard. A crew member may go ashore to the DPA or flag state directly where the situation warrants, and Port State Control in the next harbour can inspect on the strength of a credible complaint.
The ISM Code's most under-used safeguard is the Designated Person Ashore. The DPA is a named individual in the management company with a direct line to the highest level of management and a specific duty to monitor safety and provide shore-based support to the vessel. The point of the role is independence from the chain of command onboard: a crew member can bypass a master or captain who is part of the problem and reach someone ashore with the authority to act. Every crew member should know the DPA's name and contact details before leaving the dock.
Retaliation is the fear that silences most concerns, and both frameworks address it head-on. MLC 2006 prohibits the victimisation of a seafarer for filing a complaint, and requires that complaints be handled fairly and, where possible, confidentially. A dismissal, demotion or campaign of pressure following a genuine safety report is itself a breach the flag state can act on. No system eliminates the social cost of speaking up on a small crew, but the legal position is unambiguous: the seafarer who reports in good faith is protected, and the party who retaliates is in the wrong.
Frameworks describe the floor; culture determines whether anyone stands on it. A yacht with a genuine safety culture is one where reporting a near-miss earns thanks rather than a reprimand, where the complaint procedure is walked through at induction, and where the captain visibly closes the loop on concerns so the crew see that raising them changes something. Where that culture is absent, the paperwork exists and the reporting does not — and the first anyone hears of a problem is the injury.
The owner and the management company hold the ultimate duty. They fund the vessel, appoint the DPA and set the tone the captain enforces. A concern that reaches them — through the master, the DPA or the flag state — is not a nuisance to be managed but a legal and moral obligation to act, and the cost of acting is always smaller than the cost of the accident that follows inaction.
Through the Obsidian Helm Marketplace we source and vet independent maritime safety advisers and ISM auditors from an established network, and commission a discreet review of your yacht's SMS, onboard complaint procedure and DPA arrangements against MLC 2006 and the ISM Code. We negotiate one all-in engagement, conducted under NDA, and give you a plain account of where the gaps sit and what it costs to close them before they become an incident.
Enter The Marketplace Request A Vetted IntroductionNo salesperson. We review every request personally and reply in confidence — sourcing, vetting brokers, or solving the problem above.
Under MLC 2006 every yacht within scope must carry a written onboard complaint procedure and give each crew member a copy. It sets an escalating path: raise the concern first with the head of department, then the master in writing, then shore-side. The crew member may be accompanied at every stage and cannot lawfully be victimised for using it.
The Designated Person Ashore is a named individual in the management company, required by the ISM Code, with a direct line to top management and a duty to monitor safety. The role is independent of the onboard chain of command, so a crew member can bypass a captain who is part of the problem and reach someone ashore with authority to act.
Yes. MLC 2006 prohibits the victimisation of a seafarer for filing a complaint and requires that complaints be handled fairly and, where possible, confidentially. A dismissal, demotion or pressure campaign following a good-faith safety report is itself a breach the flag state can act on, so the reporter is legally protected.
A near-miss is an event that could have caused injury, damage or loss but did not, reported because the next occurrence may not be so lucky. A non-conformity is an observed situation where evidence shows a required standard is not being met. The ISM Code's Safety Management System is built to capture, analyse and correct both.
When onboard and DPA steps fail to resolve a genuine concern, a crew member may take an MLC 2006 complaint to the yacht's flag state, which can direct the company or inspect. Port State Control in the port of call can also inspect on the strength of a credible complaint and log deficiencies, or detain the yacht where the risk is serious.
Tell us, in confidence, what keeps you up. We reply privately, under NDA.
Request Your Invitation