Cruise Ship Passenger Overboard Incident Report Form

Complete it as soon as the immediate response is stabilized and the key facts can be verified. The form is designed for a passenger overboard event, so it should capture the incident date, reported time, last known location, communications, and search actions while details are still fresh. If the situation is still active, record what is known and update the report as new information is confirmed.

It is typically completed by the officer or manager responsible for incident documentation, often with input from the bridge team, security, medical staff, and witnesses. The reporting source and crew response fields help show who observed the event and who took action. If multiple departments contribute, one person should own the final version to keep the audit trail consistent.

This template is specific to passenger overboard events, so it includes last known location, last seen time, GMDSS activation, coast guard notification, search pattern, and recovery actions. A generic incident form often misses the communication log and search chronology that matter in this scenario. It also helps separate confirmed facts from witness statements and uncertain location details.

It is event-driven, not scheduled, and should be used for each passenger overboard incident or suspected overboard event. If the incident evolves over several hours, the same form can be updated with additional communications, search steps, and follow-up actions. That keeps one record tied to the full response timeline.

Common mistakes include leaving the last known location vague, failing to record exact times, and not documenting who was notified and when. Another issue is mixing witness accounts with confirmed facts without labeling them clearly. The form works best when each field is completed with the most precise verified information available.

Yes. You can add fields for ship name, voyage number, incident severity, internal case number, or additional notification steps if your operating procedure requires them. You can also use conditional logic so medical fields appear only when injury or medical need is reported. Keep the form focused on minimum necessary data and avoid adding fields that do not support the incident record.

Yes. The structure supports a clear audit trail by capturing times, actions, notifications, and evidence preservation in one place. That makes it easier to review the response later, compare crew accounts, and show that the incident was documented promptly. If passenger names or other PII are collected, include a clear disclosure about how the information will be used and stored.

Use it alongside your incident management, safety, and communications process so the bridge, security, and medical teams can contribute the facts they control. If your system supports attachments, link photos, logs, or witness statements to the report rather than copying everything into free text. A shared workflow reduces gaps between the response, notification, and follow-up stages.

An ad hoc note usually misses structure, exact timing, and consistent terminology, which makes later review harder. This template prompts the team to capture the same critical details every time, including communications, search pattern, and evidence preservation. That consistency is especially useful when multiple departments or outside authorities need to review the record.