Every PSC deficiency on Form B carries two codes: what is wrong, and what must happen next. The action code sets the deadline and who checks the fix; the rectification record decides whether the finding actually closes. This guide decodes the action codes, sets the deadline for each, and shows how to document rectification so the next inspector sees it closed. Book a demo to track PSC findings to close-out.

Form B · action taken · for masters and DPAs

PSC deficiency codes and action taken: read the code, meet the deadline, prove the fix

A Form B line, decoded. The action code is what drives your next 14 days.

Deficiency code07 groupFire safety
DescriptionSmoke detector in engine room not workingAs written by the PSCO
Action taken17Rectify before departure
Grounds for detentionNoTick box, or code 30 in some regimes

Illustrative line. Full deficiency code numbers follow the code list used by each regime.

PSC action taken codes and what each one requires

Action codes are broadly shared across regional MoUs, though each publishes its own list. Code 17 means rectify before departure without detention; code 30, where used, means grounds for detention. The Paris MoU now marks detention with a “grounds for detention” tick box. For how detainable and non-detainable findings differ, see our detainable vs non-detainable guide. Try the platform free.

CodeMeaningDeadlineWho confirms the fix
10Deficiency rectifiedAlready doneVerified by the PSCO at the inspection
15Rectify at the next portNext port of callNext port may check
16Rectify within 14 days14 days maximumMaster; next inspection may check
17Rectify before departureBefore sailingMaster; PSCO may verify
18Rectify non-conformity within 3 months (older code lists)3 monthsCompany and flag or RO
19ISM: audit by the Administration before departureBefore sailingFlag or RO auditor
21ISM: company corrective action within 3 months (Paris MoU)3 monthsCompany; ship eligible for re-inspection after
30Grounds for detention (Paris MoU uses a tick box)Before releasePSCO verifies before release
46Sail to an agreed repair port to rectifyAt the repair portRepair port authorities
47 / 48Class or flag condition accepted in place of full fixAs set in the conditionClass society or flag
81Temporary repair; full fix within a set timeAs specified, up to 14 daysMaster; next inspection may check
99Other: instruction written in clear textAs writtenAs written

Meanings summarised from Paris MoU guidelines and a published MoU Form B legend. Always read the code list printed with your own inspection report.

Code 17 vs code 30: why one closes on board and one needs the inspector

Both must be fixed before the ship sails. The difference is who has to see it, and what goes on the ship’s record.

Code 17

Rectify before departure

Who verifiesThe master; the PSCO may choose to check
Ship can sailOnce the master is satisfied it is fixed
On the recordA deficiency, not a detention
EvidenceKeep it on board for the next inspector
Code 30 / grounds for detention

Ship detained

Who verifiesThe PSCO, before release
Ship can sailOnly after release, or to an agreed repair port
On the recordA detention against ship, flag and company
EvidencePresented to the PSCO for re-inspection

Deficiency rectification deadlines: build the tracker on day one

Turn every Form B line into a dated task before the inspector leaves. The example below shows one inspection on 12 October with four findings.

FindingCodeDueOwner
Fire door self-closer, A deck17Before sailing, 12 OctChief officer
Emergency lighting, steering gear room16By 26 OctElectrician
Garbage placard missing in galley10Closed at inspectionChief cook
Lifeboat on-load release, maintenance record15Next portSecond officer and company

Close every PSC finding with proof

Turn each Form B line into a task with a deadline, attach the evidence, and see every open finding across the fleet.

Rectification record: what each closure needs

The next inspector reads the database and may ask how an earlier finding was closed. A good rectification record answers every question without a phone call.

Rectification record, example

InspectionPort X, 12-OCT-2026, Form B item 2
DeficiencyEmergency lighting, steering gear room, code 16
Root causeFailed battery pack, not on the PMS list
ActionBattery pack replaced, unit added to monthly PMS test
EvidenceBefore and after photos, test result, spare part receipt
Closed18-OCT-2026, master, signed

Extra evidence by code

17Master’s confirmation before sailing, with photo or test
15 / 16Dated work record and test result, kept for the next port
18 / 21Company corrective action and audit record addressing root cause
30Class or service reports and a request for re-inspection
47 / 48The class or flag condition and its due date

Why rectification records get rejected

Most rejected closures fail on evidence, not on the repair itself.

No datePhotos with no date or link to the finding.
Fixed, not testedEquipment repaired but never function-tested.
Symptom onlyThe item fixed but the system that missed it left unchanged.
Wrong signatoryA class or flag item closed by the ship alone.
Deadline missedA code 16 closed on day 20 with no explanation.
Lost evidenceRecords left on one ship’s laptop and gone after a crew change.

Close the loop in the safety management system

A PSC finding is also a non-conformity under the company’s SMS. Closing it on board is only half the job. Our guide to the top detention codes shows which findings repeat across fleets.

1ReportForm B sent to the office the same day
2FixEach line rectified by its deadline, with evidence
3InvestigateRoot cause for repeat or serious findings
4Fleet checkSister ships checked for the same issue
5ReviewTrends fed into internal audit and management review

PSC deficiency rectification checklist

Use this from the moment Form B is handed over. If a detention seems unjustified, our guide on challenging a detention covers the appeal route.

How Marine Inspection tracks PSC findings to close-out

Marine Inspection turns a Form B into tracked findings: each line gets its action code, due date and owner, and closes only with evidence attached. The board below is an illustrative inspection.

PSC findings · MV example · Port X, 12 Oct2 of 4 closed

Open

15Lifeboat release recordDue next port · 2 photos

Evidence attached

16Emergency lightingTest result and photos · awaiting sign-off

Closed

17Fire door self-closerClosed before sailing
10Garbage placardClosed at inspection
Code-aware deadlinesDue dates set from each action code
Evidence requiredPhotos and test results before closure
Fleet checkPush a finding to sister ships as a check
HistoryEvery closure kept for the next inspection

PSC deficiency and action code FAQs

What does PSC action code 17 mean?

Rectify before departure. The deficiency must be fixed before the ship sails, but it is not a detention, and the master confirms the fix unless the PSCO chooses to verify it.

What does PSC action code 30 mean?

Grounds for detention, in regimes that use the code. The ship cannot sail until the PSCO verifies rectification. The Paris MoU records this with a grounds-for-detention tick box.

How long do I have for a code 16 deficiency?

Up to 14 days. The master should fix it as soon as reasonably possible within that period.

What is the difference between code 15 and code 16?

Code 15 requires rectification at the next port; code 16 allows up to 14 days. Both can be checked by a later inspection.

What evidence closes a PSC deficiency?

A dated record linking the finding to the action taken, with photos, test results, the root cause where relevant, and the right signature, such as class or flag for their items.

Can Marine Inspection track PSC deficiencies?

Yes. Book a demo to see Form B findings tracked by code to close-out.

Read the code, meet the date, keep the proof

Findings closed on time with evidence keep a ship’s PSC history clean, and the next inspection shorter.