Question 1

RISQ Q3.6 requires an effective Master/Pilot information exchange (MPX) using a standard checklist, covering the pilotage plan, ship characteristics, local conditions, and contingency abort points. Why does RISQ specifically require "contingency plans... identif[ying] possible abort points in the event of a malfunction or a shipboard emergency" as part of the MPX, rather than leaving this to be addressed only if an emergency actually occurs?

Accepted Answer

Deciding abort points and emergency response in the middle of an actual pilotage emergency, under time pressure and often in confined waters, is far less reliable than having agreed them calmly in advance — the MPX is the one structured opportunity to establish this shared understanding between Master and pilot before any time pressure exists This reflects a well-established human factors principle that appears repeatedly across this content library: decisions made calmly in advance are more reliable than decisions made reactively under pressure. Pilotage is a high-consequence, time-critical phase, which is exactly why the MPX checklist treats contingency/abort planning as a mandatory line item rather than an optional discussion.

Question 2

RISQ Q3.18 asks an inspector to verify ECDIS competency by requesting the Master/watchkeeper to demonstrate live functions (safety settings, voyage plan checks, manual position fixing, CATZOC/SCAMIN knowledge, contingency action for ECDIS failure) rather than simply reviewing a training certificate. Why does the inspection rely on live demonstration over documentary evidence here?

Accepted Answer

A certificate proves training was completed at some point, not that the officer retains functional competence with the specific equipment fitted on this vessel — RightShip's own guidance explicitly lists the functions to be demonstrated in front of the inspector because a paperwork-only check cannot distinguish genuine competence from a forgotten or never-applied skill This mirrors the same Human Factors principle seen in SIRE 2.0: documentary compliance and demonstrable competence are assessed as two separate things. RISQ's own guide to inspection for Q3.18 explicitly lists "basic functionality... in the presence of the inspector" as the verification method — a deliberate design choice, not an inspector preference.

Question 3

RISQ Q3.12 requires the Bridge Navigational Watch Alarm System (BNWAS) to be operational underway AND at anchor, with required tests conducted and recorded. Why does RISQ specifically call out "at anchor" rather than only "underway"?

Accepted Answer

BNWAS exists to detect watchkeeper incapacitation/absence, which is a real risk at anchor as well as underway — anchor watch failures (dragging anchor undetected, drifting into a shipping lane) have caused real casualties, so the alarm's value does not disappear just because the vessel is not making way A common assumption is that watchkeeping risk is purely an underway phenomenon — RISQ's explicit "at anchor" requirement corrects that assumption. An unmonitored anchor watch can fail just as seriously: dragging anchor in worsening weather, traffic encroachment, or a medical incapacitation are all anchor-watch failure modes BNWAS is designed to catch.