Passenger Accounting: The Accuracy of the Roll-Call after Costa Concordia
SOLAS III/27 governs counts and information before departure; during an emergency, the accountability method comes from the ship's approved procedure and SMS.
Operational Explanation
Separate the pre-departure passenger information system from emergency accountability. SOLAS III/27 requires the count, information on persons needing assistance and prescribed data before departure; it does not mandate a universal name-by-name roll-call at assembly stations.
Regulatory Reference
SOLAS Regulation III/8 (Muster list and emergency instructions) as the procedural basis; Cruise Vessel Security and Safety Act (CVSSA), United States: obligation to report every disappearance to the competent authorities (Coast Guard, FBI for US citizens), regardless of the status of investigations, with public quarterly reports from the Department of Transportation, a series still being published.
The duty to count, however, is not in III/8. It is in SOLAS Regulation III/27, Information on passengers, worth reading in full because it is short and is invariably quoted from memory. Paragraph 1: “All persons on board all passenger ships shall be counted prior to departure”. Paragraph 2: details of persons who have declared a need for special care or assistance in emergency situations are recorded and communicated to the master prior to departure. Paragraph 3: “Not later than 1 January 1999, the names and gender of all persons on board, distinguishing between adults, children and infants shall be recorded for search and rescue purposes”. Paragraph 4: that information “shall be kept ashore and made readily available to search and rescue services when needed”. Paragraph 5: Administrations may exempt ships from paragraph 3 where their scheduled voyages make keeping such records impracticable.
Three observations that head off three errors. The date “Not later than 1 January 1999” in paragraph 3 is not a leftover from an old edition: it is in the text in force, a spent transitional date never tidied out. Readers sometimes conclude they are holding a superseded version of the Convention, and need reassuring.
Second: III/27 requires neither nationality nor date of birth. It asks for name, gender and the adult/child/infant distinction. Nationality is a European requirement, not an IMO one: it comes from Directive 98/41/EC as amended by Directive (EU) 2017/2109, which for voyages exceeding 20 miles to the next port of call requires family names, forenames, gender, nationality and dates of birth, and prescribes their electronic transmission to the National Single Window within fifteen minutes of departure. III/27.4, by contrast, is content that the information be «kept ashore and made readily available».
Third: III/27 binds passenger ships on international voyages; 98/41/EC applies to ships operating to or from ports of Member States, including the domestic voyages SOLAS does not reach. For a ship trading in Europe the two regimes stack, and the more demanding one is the European.
The articles of Directive 98/41/EC that impose concrete duties on board are worth reading. Article 4(1): “All persons on board any passenger ship which departs from a port located in a Member State shall be counted before that passenger ship departs”. Article 4(2) adds that the number is communicated to the master and reported in the single window. Article 5(1) sets the threshold — voyages where the distance from the point of departure to the next port of call exceeds 20 miles — and the data list: “the family names of the persons on board, their forenames, their gender, their nationality, their dates of birth”, plus volunteered information on special care or assistance in an emergency and, if the Member State so chooses, an emergency contact number. Article 5(2) requires those data to be reported in the single window on departure and “in no case later than 15 minutes after its departure”: fifteen minutes, not «as soon as practicable».
Article 8 assigns responsibility: each company appoints a passenger registrar, responsible for reporting the information in the single window, and ensures that information on persons who have declared a need for assistance is “properly recorded and communicated to the master before the passenger ship departs”. Data are kept only until the voyage has been safely completed and reported, then erased “automatically and without undue delay”: an obligation to delete, not an option.
Two dates that make many procedures still in use obsolete. Directive (EU) 2017/2109 allowed a six-year transitional period from 20 December 2017 during which data could be communicated to the company's passenger registrar or shore-based system instead of the single window. That period expired on 20 December 2023: the alternative route no longer exists. And the Directive's reference to «Directive 2010/65/EU» is now a reference to a repealed act: the single window today is that of Regulation (EU) 2019/1239, establishing the European Maritime Single Window environment (EMSWe).
Scope of Application
Before departure apply SOLAS III/27 and, where relevant, EU and National Single Window requirements. In an emergency apply the approved procedure/SMS method, which may combine roll-call, electronic scanning and search teams.
Procedure / How to Complete It
- Complete count and passenger information before departure.
- Record and transmit special-assistance information under the applicable regime.
- In an emergency use the accountability method set by the approved procedure/SMS.
- Reconcile results and searches without attributing the method directly to III/27.
Practical Example
Example: during an abandon-ship drill, the person in charge of an assembly station carries out the name-by-name roll-call against the assigned list, immediately reports to the bridge two names found absent, and waits for confirmation before declaring the station complete, following the Company's documented procedure.
What Typically Goes Wrong
Common Mistakes Mistake Library
| Mistake | Consequence | How to avoid it |
|---|---|---|
| Counting of those present at assembly stations left to individual initiative, without a written and assigned procedure | As in the Costa Concordia case, inability to establish with certainty who is actually present or missing | Define and exercise a written, assigned counting procedure for every assembly station |
| Discrepancies between attendance recorded and the muster list not reported immediately to the bridge | Delay in searching for people actually missing during the emergency | Report every discrepancy found immediately, without waiting for the count of the entire ship to be completed |
| Disappearance reporting procedures to the Coast Guard/FBI not kept up to date for ships subject to CVSSA | Regulatory non-compliance and delayed notification to the competent authorities | Always keep the reporting procedures required by CVSSA up to date for ships operating to/from US ports |
What the PSCO Checks
Operational Tips
- Do not leave the counting method implicit: write it explicitly into the emergency procedure and exercise it regularly.
- Report every discrepancy found immediately to the bridge, however minor: the Costa Concordia case teaches that delays accumulate.
- For ships subject to CVSSA, always keep the procedures for reporting disappearances to the competent US authorities up to date.
Preparation checklist
- Pre-departure count complete
- Data and special-assistance information available
- EU/NSW requirements checked
- Emergency-accountability method defined in SMS
FAQ
Related Topics
Last substantive revision of this page: 13 August 2026 · page fingerprint d02d3c15caa8