Murmester study materials
Murmester study resources

Detention for a seized damper and a weak fire pump: certificate, release and follow-up

Murmester · Put your knowledge to work in context.

All case studies

Detention for a seized damper and a weak fire pump: certificate, release and follow-up

An 18,500 GT Panamax bulk carrier has an ISSC valid to 12 May. On 3 April, port State control officers board her in a Paris MoU port on clear grounds following an ISM interview with a crew member. They find that the No. 3 hold fire damper will not close because the spindle is seized, and that the emergency fire pump delivers only 0.22 MPa at the furthest hydrant. The detention order is issued at 17:40. The class surveyor attends the next morning and marks the ship unfit to sail until the damper is repaired; the flag is informed at 09:00 the following day. The owner now asks class to issue a "sailing certificate" so the ship can move, with her cargo, to a repair yard 180 nm away, arguing that the ISSC is still valid until 12 May and that the charter is already on demurrage.

1. Was the detention lawful, and does it invalidate the ISSC?

Read the worked answer

The detention is lawful. SOLAS regulation I/19 permits a port State to control a ship where there are clear grounds for believing that she does not substantially comply with the Convention, and a seized fire damper plus a fire pump at 0.22 MPa are objective evidence that she cannot proceed to sea without danger to the ship or persons on board. What the detention does not do is cancel the ISSC: a statutory certificate is prima facie evidence of compliance, and the port State's action restricts the ship's movement rather than withdrawing the flag's certificate. The consequences are different and still serious: the flag must be notified, class must record the deficiency, and a detention is evidence that the safety management system is not delivering, which can trigger an additional ISM verification. The owner's argument that the ISSC is valid until 12 May is true and irrelevant, because certificate validity is not a defence to a clear ground.

2. Can the ship sail to the repair yard, and on what document?

Read the worked answer

Not on a class "sailing certificate" and not as a normal voyage. Class cannot extend the ISSC; only the flag can, and SOLAS I/14 allows extension only in defined circumstances: up to 5 months where the ship is not in a port of the flag when the certificate expires (I/14(c)), or up to 1 month for a ship on short voyages (I/14(d)). Neither fits a 180 nm movement with cargo from a port where the detention was issued. What fits is a single-voyage dispensation: the port State releases the ship from detention subject to conditions such as a fixed route, weather limits, no cargo operations, class attendance and acceptance by the repair yard, and the flag issues a written authorisation for that one voyage. Class would record a condition of class. The demurrage is commercially painful but legally irrelevant; the movement depends on the port State's release and the flag's documented authorisation, both obtained before departure.

3. What certification and survey consequences must the technical manager plan for?

Read the worked answer

The annual survey clock does not stop. The ISSC anniversary is 12 May, the annual survey must be completed within plus or minus 3 months of that date and the certificate endorsed; missing the window invalidates the certificate and turns a deficiency detention into an expired-certificate detention, which is far worse. Corrective action on the damper and the fire pump must be verified, normally within 3 months for ISM purposes, and the class surveyor's attendance is the verification. The low pump pressure is unlikely to be a one-off: 0.22 MPa at the furthest hydrant suggests a worn pump, a mis-set relief valve or a leaking isolation, so the repair should include a flow test at the two hydrants furthest from the pump, not just an adjustment at the pump. Finally, expect the flag to ask for a root-cause analysis, because the same ISM element has now failed twice.