Maritime Insights
Industry knowledge, career guidance, and maritime intelligence for the global shipping community.
Mastering the Ship-Shore Safety Checklist
The ISGOTT ship-shore safety checklist is not a form. It is a negotiation between two organisations that do not work for each other, conducted in about an hour, with the shared goal of not blowing something up. Every senior tanker officer has watched it degrade into box-ticking: the terminal representative reads questions at speed, the chief officer initials without walking the manifold, and both parties sign a joint declaration neither has truly verified. That is precisely when accidents happen — during the routine transfers where everyone is confident. This article is written for masters, chief officers, and cargo officers who run the pre-transfer conference. It explains what the checklist sections are actually trying to protect — mooring integrity, emergency shutdown readiness, communication channels, cargo containment, and fire-fighting readiness — and how the coded questions (re-check items, agreement items, permission items) are supposed to drive behaviour after signing, not just before. It covers the practical discipline that separates a living checklist from a dead one: physically walking the interface together, agreeing the re-check interval and sticking to it, handling disagreements over items like emergency towing-off wires, and knowing when an answer of "no" means stop, not negotiate. It also addresses the repetitive checks that happen during the transfer itself, when the cargo officer on watch is tired, the terminal wants rate, and the temptation to pencil-whip the hourly verification is strongest. If you run tanker transfers, this is the meeting where you earn your salary.
Preparing Junior Officers for Vetting
Every junior officer remembers their first SIRE or CDI inspection. The inspector appears at your station with a notebook, asks you to explain the lifeboat on-load release mechanism or demonstrate LEL testing with the ship's gas meter, and suddenly the procedures you signed off as familiar with feel very far away. Vetting outcomes increasingly turn on how junior officers answer, because inspectors deliberately seek out the least senior person at the equipment — a well-drilled crew's weakest member should still be competent, and that is what they are testing. This article is written for junior deck and engineer officers on tankers. It sets out the questions inspectors actually ask: launching and release arrangements for survival craft, fire damper locations and operation, fixed fire-fighting system operation, SCBA donning time, gas detector calibration and use, inert gas system alarms and trip settings, ODME operation, cargo valve and emergency shutdown locations, and the contents of the oil record book entries they have signed. It explains how to build genuine confidence rather than rehearsed answers — hands-on time with the equipment every week, knowing where things are before being asked, and being honest when you do not know, because an inspector respects "I will find out" and destroys people who bluff. It also covers the paperwork inspectors check against people: training records, familiarisation entries, drill participation, and rest hours. The goal is not to perform for one day. It is to be the officer whose daily standard survives a stranger with a clipboard.
Root Cause Analysis for DPAs
The ISM Code requires the company to analyse non-conformities and hazardous occurrences and to implement corrective action. What it does not specify is how — and the gap between a genuine analysis and a form completed to close the SMS loop is where repeat incidents live. Every DPA has seen the corrective action that corrects nothing: "crew to be reminded of procedure" for an incident whose procedure was unworkable, or "additional training" for a failure caused by manning, fatigue, or a maintenance backlog nobody would fund. Six months later the same event recurs, and the auditor asks what happened to the previous corrective action. This article is a practical RCA guide for the Designated Person Ashore. It covers evidence collection from shipboard before memories fade and the crew rotates — timelines, logs, alarm printouts, photographs, and structured interviews that separate what people did from what they now wish they had done. It explains when 5-Why is enough and when you need a wider method such as a fishbone or barrier analysis, because some incidents have linear causes and some have a web of failed defences. It addresses the near-miss reporting culture that feeds real analysis — a reporting system that punishes reporters produces silence, and silence looks like safety until it does not. Finally, it sets out how to write corrective actions that survive audit: specific, owned, resourced, time-bound, and verified for effectiveness after implementation. The goal is a management system that learns, not one that files.
Enclosed Space Entry Fatal Errors
Enclosed space entries keep killing seafarers in the same handful of ways, and the pattern is so consistent it should shame the industry. A ballast tank or cargo hold is opened without testing. Someone collapses at the bottom of a ladder. A shipmate sees them fall, goes in after them with no breathing apparatus and no attendant, and collapses beside them. Sometimes a third person follows. The majority of enclosed space fatalities include would-be rescuers who died attempting to save a colleague with no equipment and no plan — the single most predictable, preventable feature of these accidents. This article walks through the fatal errors one by one: skipping or faking atmosphere testing, testing at one level only, no ventilation before entry, no trained attendant standing at the entrance, no rescue plan beyond "we will pull him out", and a permit signed by an officer who never saw the space. It then sets out the correct entry procedure in operational order — risk assessment, isolation, ventilation, calibrated multi-point gas testing (oxygen around 20.9 percent as the reference, flammable and toxic gases checked against your SMS limits), entry permit with a time limit, continuous attendant, communication checks, and rehearsed rescue with the right equipment staged at the entrance. It closes with what officers must actually enforce when the entry is inconvenient, the ship is short-handed, and the tank "only needs a quick look". There are no quick looks. Every level of the crew needs to read this one.
ECDIS Safety Parameters
Most ECDIS-assisted groundings share an uncomfortable feature: the equipment worked exactly as configured. The alarm did not sound because the safety contour was set to a value that made the hazard invisible, or because the check scale was wrong, or because the officer had muted the look-ahead alarm after hundreds of nuisance activations in confined water. ECDIS does not run ships aground; parameters chosen by people do. Accident investigation reports — the Ovit grounding on the Varne Bank among the better-known — repeatedly find safety settings that were never adjusted from defaults, never understood, or set once at handover and inherited blindly by every subsequent watchkeeper. This article explains the parameters that actually control what the ECDIS warns you about: the safety contour and how it differs from safety depth, the shallow and deep contours that frame the picture, and the cross-track distance and look-ahead settings that define the safety frame around your planned route. It covers the alarm fatigue problem honestly — an ECDIS that cries wolf on every leg teaches watchkeepers to silence it, and the fix is better settings and better route checking. It lists the setup errors found in audits: default values never changed, safety contour shallower than the ship's draft logic requires, unchecked route legs, and scale mismatches between planning and monitoring views. Written for second officers who plan routes and senior officers who verify them, this is the configuration conversation your bridge team needs before the next pilotage, not after the next investigation.