Deficiencies
Record and track deficiencies from inspections with corrective action workflows.
Accidents
Every feature in Accidents is built for daily maritime work — simple to use, fast to navigate, and fully integrated with the rest of Navatom.
01
The investigation is recorded on the accident itself from the moment it is reported, on the ship app and the office app: the date of the investigation, the weather on the Beaufort scale and the visibility, the incident types in the order they happened, the witnesses, and the soft and hard evidence. Where it happened is recorded as a port, a position or an address, with the part of the vessel. The investigation report sits on the same record, and Navatom AI can draft it for you to edit and confirm.
02
Record each injured crew member with the severity of the injury, from minor to critical, and its recordability: lost time with the workdays lost, restricted work, medical treatment or first aid. These are the classes lost-time and recordable injury statistics are built from. The crew list offered is the crew on board that vessel on the day of the accident, each with their rank.
03
An accident can be reported on board straight after the event with no connection, and worked on in the ship app or the office app, photos included. Changes wait on the device and are sent when the connection returns, and any conflict with a change made elsewhere is shown to you. Accidents can also be reported and worked on in the Navatom mobile app for iPhone and Android, offline too.
04
Record what could have happened, not only what did. An accident is marked high potential when, under slightly different circumstances, it could realistically have caused a fatality or permanent disability, and its potential severity sits beside its actual severity on the same scale.
05
Record each effect of an accident beyond harm to people: sea or air pollution, a conservation breach, a commercial effect or another, with a severity from reversible to irreversible damage. A sea pollution records the quantity, whether it went overboard or stayed on board, the environmental rules it falls under, from oil to ballast water, its source and the substance; a cargo incident records what happened and what caused it.
Environmental impact records link directly to the incident investigation and corrective actions. When regulatory authorities or P&I clubs require environmental damage documentation, the complete record is immediately available with supporting evidence.
06
Write the investigation report on the accident's Report tab, in a rich-text editor. Navatom AI can draft it from the accident's record, and the draft opens for you to edit before anything is saved.
Investigation reports serve multiple audiences: internal management review, flag state reporting, P&I club notifications, and classification society communication. The structured format ensures that every audience receives the complete, consistent information they need.
07
Each accident records the broad areas its causes came from, people, procedures, equipment, environment or organization, and its root causes, chosen from your company's root-cause systems or from standard systems such as the Marine Systematic Cause Analysis Technique (MSCAT). The office links repeats of the same accident on a vessel, so causes that come back show across the fleet.
08
Address incident findings at three levels: interim actions secure the scene and contain immediate risks, corrective actions resolve the specific conditions that contributed to the incident, and preventive actions update your safety management system to prevent recurrence.
Each action has its own due date, and the office verifies it once it is done or sends it back. Later the office reviews verified actions for effect, and an action found not effective opens again. For serious incidents, all three action types work in parallel — the scene is secured while the investigation proceeds and systemic changes are planned.
09
Hard evidence is a file that supports the investigation, such as a photo of the damage or a copy of a log page; soft evidence is a written statement, such as what a witness saw. Both are kept on the accident, separate from its general attachments and comments, and are available for investigation review.
10
List the people who saw the accident: crew members on board that day, your company's employees, or third parties such as a pilot or a stevedore. What each witness said is recorded as soft evidence on the same investigation. All witness records are preserved as part of the permanent investigation file.
11
Record the weather at the time of every incident as a force on the Beaufort scale, from 0 to 12, and the visibility as very poor, poor, moderate or good. These conditions often play a critical role in incident causation.
Standardized weather recording using the Beaufort scale ensures consistent, comparable data across all incidents and vessels. Fleet-wide analysis can reveal whether certain weather conditions correlate with increased incident frequency.
12
When the worst happens, a fatality records the crew member and what happened, on the same record as the investigation, the witnesses and the evidence.
Fatality records link to the complete incident investigation, including witness statements, environmental conditions, and evidence. This comprehensive documentation supports your obligations to flag state authorities, P&I clubs, and maritime investigation bodies.
13
Every accident follows a six-stage lifecycle from initial reporting through investigation, corrective action, verification, and closure. The lifecycle ensures that no incident is closed without completing the required investigation, evidence collection, and corrective action steps.
The office accepts an accident and sets its due date, and resolves and closes it once the work is done. It can be resolved as fixed only when at least one corrective action is done and none is still open, and it can be reopened if needed.
14
Classify every incident by both priority and severity to ensure that the most serious events receive immediate investigation resources. Severity captures the actual harm — injuries, fatalities, environmental damage, property loss. Priority determines the investigation urgency.
The dual classification ensures that a near-fatal injury receives more investigation resources than a minor first-aid case, while both remain in the system for trend analysis and regulatory compliance.
15
Report and investigate incidents from both ship and office environments. Shipboard incidents are documented by the vessel crew and immediately visible to shore-based investigation coordinators. Office-initiated investigations are communicated to vessels.
The dual-context approach ensures that your designated person ashore sees the same incident data as the vessel master. Investigation coordination between ship and shore happens in real time through the shared system.
16
Assign each accident to the officer ranks who work on it on board and to the people who follow it in the office. Several officers and office staff can be assigned to one accident, and each sees it on their own dashboard.
17
Five dashboard widgets show your accidents and the fleet's that are overdue or in progress, new ones waiting to be accepted, and unassigned ones. Each shows as a count or as a table you can open, for the vessels you choose.
18
Two pages of accident analytics. Flow shows how accidents move through their statuses and where they wait; Root Causes shows which causes come back across the fleet.
19
Document every incident with detailed narrative descriptions and supporting files. Attach photographs of the scene, equipment damage reports, medical records, authority correspondence, and any other evidence that supports the investigation.
Rich documentation is critical for serious incident investigations. When flag State authorities, P&I clubs or maritime investigation bodies request information, the accident prints or saves as a PDF with your company's header.
20
Coordinate investigation activities with threaded comments attached to each incident record. Ship and shore personnel can exchange updates, share analysis, request additional evidence, and discuss findings in context.
The comment thread preserves the investigation narrative — questions asked, evidence requested, hypotheses explored, and conclusions reached. This collaborative record demonstrates the thoroughness of your investigation process.
21
Every action on an accident is recorded in its event history, with who did it and when. From initial reporting through witness additions, evidence uploads, injury documentation, severity changes, and investigation closure — every step is captured with full attribution.
The audit trail serves both internal and external purposes. Internally, it ensures investigation accountability.
Externally, it provides the documented evidence that maritime authorities, insurers, and investigation bodies require.
Technical
Architecture and engineering behind Accidents — data handling, real-time sync, and interface design.
All incident views use high-performance data grids with advanced filtering by severity, incident type, vessel, injury status, and date range. Browse extensive incident records without performance degradation.
The investigation data model captures six dimensions of every incident: the event, the people (injuries/fatalities), the environment (weather/sea state), the evidence (hard/soft), witness accounts, and investigation findings — all linked in a single coherent record.
Five injury severity levels and four recordability classes, with lost workdays for lost-time injuries. The framework covers everything from first-aid cases to fatalities, each recorded against the crew member on board that day.
Hard and soft evidence are managed in separate categories: hard evidence holds the files that support the investigation, soft evidence the written statements. Both stay apart from the record's general attachments and comments.
The six-stage lifecycle enforces its rules at each step: an accident is resolved as fixed only once a corrective action is done and none is open, and the office accepts, resolves and closes it.
Every action on an accident is recorded as it happens, with who did it and when. The same record feeds the audit trail, notifications and dashboards.
Accidents are kept on the device, so you can keep working on them in the ship app and the office app with no connection. Changes and photos wait in an outbox and are sent when the connection returns, and any conflict is shown to the user rather than resolved silently.
Standardized weather recording using the Beaufort scale (force 0 to 12), visibility categories, and structured environmental condition fields enable fleet-wide correlation analysis between conditions and incident frequency.
Same Category
Other Issues modules that integrate with Accidents.
Record and track deficiencies from inspections with corrective action workflows.
Manage non-conformity reports, root cause analysis, and corrective actions.
Capture near-miss reports to promote proactive safety culture across the fleet.
Document technical findings from surveys, inspections, and maintenance activities.
Start your free trial today and see how Accidents fits into your fleet operations.