Question 1

Tokyo MoU groups MARPOL deficiencies into separate sub-codes for Annex I (Oil), Annex II (NLS/Chemicals), Annex III (Dangerous Goods), Annex IV (Sewage), Annex V (Garbage), and Annex VI (Air Pollution), rather than one single "pollution" category. What is the practical reason for this granularity?

Accepted Answer

Each Annex has its own distinct equipment, record-keeping, and operational requirements (e.g. Annex V garbage record book and segregation rules are entirely different from Annex VI engine/fuel emissions compliance), so lumping them together would obscure which specific system or competency is actually failing and make trend analysis across the fleet meaningless Granular categorisation lets the data actually drive useful action — a fleet with a pattern of Annex V garbage deficiencies needs different intervention (crew training, segregation bins, record-keeping discipline) than one with Annex VI emissions/fuel-quality issues (engineering/bunker management). This same logic applies directly to how a crew should prepare for inspection: knowing which Annex's record book and procedures apply to which physical system is part of genuine competency, not just terminology.

Question 2

Paris MoU explicitly treats ISM (Document of Compliance / Safety Management Certificate) deficiencies as "clear grounds" for a more detailed PSC inspection. Why does an ISM finding trigger this escalation rather than being treated as an isolated paperwork issue?

Accepted Answer

ISM failures suggest a systemic management weakness rather than a single defective item — if the safety management system itself is not functioning, the inspector cannot trust that any other area of the ship is being properly controlled either, so the scope of inspection is widened to verify the rest of the vessel independently This reflects the same logic as the vetting fundamentals module: a document or certificate proves nothing on its own if the underlying management system is not genuinely functioning. An ISM red flag tells the inspector that other findings on the ship may not be isolated incidents but symptoms of a broader management gap, justifying a wider, deeper inspection scope under Paris MoU's "clear grounds" provisions.

Question 3

SIRE 2.0 Ch.2.4 (Defect Management) and Tokyo MoU code 01106/01107 (DoC/SMC) both probe how a vessel handles known deficiencies. What is the key distinguishing feature of a genuinely functioning defect management process, as opposed to one that merely looks compliant on paper?

Accepted Answer

Defects are formally logged with a realistic timeline and resourcing for correction, tracked to closure, and escalated to the company/DPA if not resolved within the planned period — rather than being logged once and then left open indefinitely or quietly removed from the list without genuine rectification Inspectors specifically look for evidence of a live, working defect-management cycle, not just the existence of a log. A defect list with items that have sat open for months with no escalation, or items closed without evidence of actual repair, tells an inspector the SMS's defect process is a formality rather than a real control — the same "normalisation of deviance" pattern flagged elsewhere across this content library.