Technical domain
Incident Investigations
Timelines, near misses, evidence packs, and public reports.
Categories
Category
Blackouts & Power Loss
Investigations involving loss of power, blackout recovery, generators, switchboards, shore power, UPS systems, and cascading electrical failures.
Category
Bridge, Navigation & Positioning Incidents
Cases involving GNSS, AIS, radar, ECDIS, bridge integration, position integrity, watchkeeping, and navigational decision-making.
Category
Communications & Connectivity Failures
Incidents involving satellite links, radio systems, emergency communications, internet failover, and operational connectivity.
Category
Cyber, IT & OT Security Incidents
Investigations involving cyber risk, vendor access, OT exposure, network segmentation, identity compromise, and IT/OT failure chains.
Category
Fire, Flooding & Environmental Events
Cases where electrical, control, monitoring, detection, alarm, or communications systems contributed to fire, flooding, smoke, or environmental events.
Category
Investigation Methods & Evidence Handling
Methods for building timelines, preserving logs, gathering screenshots, interviewing crew, handling technical evidence, and referencing source material.
Category
Machinery, Automation & Control Failures
Events linked to PLCs, alarms, monitoring, propulsion control, thrusters, tank systems, engineering displays, and integrated automation.
Category
Near Misses & Lessons Learned
Near-miss reviews, operational lessons, weak signals, corrective actions, and repeat-failure prevention.
Category
Regulatory Reports & Case References
Flag, class, accident investigation, insurer, manufacturer, and authority reports used as references for technical learning.
Articles in this domain
Filter this domain-
Machinery, Automation & Control Failures · Incident investigation
Alarm Fatigue and the Missed Engineering Alarm
A full case study of the MPV Everest engine-room fire, focused on fuel-transfer alarms, watchkeeping, fatigue, automation design, emergency response, and yacht mitigations.
-
Regulatory Reports & Case References · Reference note
Cheeki Rafiki: How To Use Public Incident Reports Without Overstating The Lesson
A case-based guide to using public maritime investigation reports responsibly, built around the MAIB Cheeki Rafiki report and its yacht-specific safety lessons.
-
Cyber, IT & OT Security Incidents · Incident investigation
Commercial Vessel Malware: Why Remote Access Cannot Be Left To Trust
A case-led cyber incident lesson from the USCG 2019 commercial-vessel malware alert, translated into yacht controls for vendor access, segmentation, logging, and emergency disablement.
-
Machinery, Automation & Control Failures · Incident investigation
Commodore Control-System Failure: Why Backup Controls Must Be Usable
A full case study of the passenger ferry Commodore grounding, focused on control-system software, failed display media, backup controls, emergency response, and yacht automation lessons.
-
Investigation Methods & Evidence Handling · Incident investigation
Dali Blackout Timeline: Building A Technical Incident Sequence
A Dali case study showing how yacht teams should build a technical timeline from alarms, VDR data, PMS events, bridge actions, communications, and evidence gaps.
-
Communications & Connectivity Failures · Incident investigation
El Faro Weather Data Lesson: When Connectivity Becomes Operational
A full case study of El Faro focused on weather data flow, communications architecture, information latency, bridge decision-making, and yacht connectivity lessons.