⚓ Real Maritime Incidents. Decoded Into Lessons. Always Free

About MaydayLog — Real Maritime Incidents. Decoded.
About MaydayLog

Every Maritime Accident
Has a Story. We Decode It.

MaydayLog is a maritime incident learning platform — turning dense investigation reports into plain English lessons for engineers, cadets, and everyone who keeps ships running.

50+
Incidents decoded
1.9M
Seafarers worldwide
100%
Free — always
4+
Investigation bodies sourced
Our Mission

Turning Maritime Tragedies Into Knowledge That Travels the World

Every year, thousands of maritime incidents occur at sea. Engines fail. Ships ground. Bridges collapse. Workers die. Investigation bodies spend months producing detailed reports — identifying exactly what went wrong, why it went wrong, and how to prevent it happening again.

Those reports sit unread in dense PDF format. Written in legal language. Buried on government websites. Inaccessible to the engineers and cadets who need them most.

MaydayLog exists to fix that. Every case study we publish takes one of those reports and transforms it — into a clear timeline, a plain English root cause analysis, and practical lessons every watchkeeper can actually use.

"The most important safety reports in the world sit unread. MaydayLog exists to change that."
Sohel Sekh — Founder
Engine Cadet · MEIN SCHIFF RELAX · TUI Cruises
The Problem

Maritime Safety Knowledge Is Being Lost After Every Incident

The maritime industry loses knowledge after every accident. Investigation authorities publish their findings. Companies issue internal bulletins. And then — the lessons fade. The same failures repeat. The same patterns emerge in the next incident report. And the next.

80% of maritime accidents involve human factors. Not because seafarers are careless — but because the systems designed to spread safety knowledge are not reaching the people who need it most.

📄
Reports nobody reads
MAIB, NTSB, ATSB, and IMO publish hundreds of investigation reports every year. Most are never read by the engineers and cadets who could learn the most from them.
🔒
Language that excludes
Investigation reports are written in legal and technical language — essential for legal purposes, but inaccessible for practical learning at sea.
🔄
Patterns that repeat
The same root causes — low lubricating oil, inadequate maintenance, poor alarm management — appear incident after incident. The lessons exist. They just aren't spreading.
What We Do

How MaydayLog Decodes Every Incident

Every case study on MaydayLog follows the same structured format — designed for maximum clarity and practical value for working engineers and cadets.

01
Find the official report
Every case study starts with an official investigation report from MAIB, NTSB, ATSB, AIBN, or IMO — public domain, government-issued, and credible. No speculation. No guesswork.
02
Build the timeline
Every incident is rebuilt event by event — from the first warning sign to the final consequence. Colour-coded by severity so you can see exactly how the situation developed.
03
Decode the root cause
Dense legal findings are translated into plain English root cause analysis — what actually caused the incident, why it wasn't caught, and what systemic failures allowed it to happen.
04
Extract the lessons
Every case study ends with 5 concrete, practical lessons — things you can apply on your next watch, in your next drill, or in your next oral examination. Not theory. Real knowledge.
05
Always credit the source
Every article links directly to the original investigation report. MaydayLog amplifies the work of investigation authorities — not replaces it. Full attribution on every case study.
06
Keep it free — forever
Safety knowledge should have no paywall. Every case study on MaydayLog is free to read — no account required, no subscription needed, no barriers between engineers and the lessons they need.
Our Sources

Built on Official Investigation Reports

MaydayLog sources every case study from official government investigation bodies. All reports are public domain — published specifically to improve maritime safety worldwide.

MAIB
Marine Accident Investigation Branch — United Kingdom
NTSB
National Transportation Safety Board — United States
ATSB
Australian Transport Safety Bureau — Australia
AIBN
Accident Investigation Board — Norway
IMO
International Maritime Organization — Global
JTSB
Japan Transport Safety Board — Japan
Created By

Written From Inside the Engine Room

SS
Founder
Sohel Sekh
Engine Cadet · MEIN SCHIFF RELAX · TUI Cruises

MaydayLog was created by Sohel Sekh — an engine cadet currently working aboard MEIN SCHIFF RELAX, a TUI Cruises vessel. Sohel works daily inside a real cruise ship engine room — maintaining machinery, standing watches, and learning first-hand what it means to keep a modern vessel running safely.

The idea for MaydayLog came from a simple observation: the most important maritime safety reports in the world were sitting unread in government PDF archives — while the same accidents kept happening at sea. As someone who understood both the engineering systems and the learning culture of the maritime industry, Sohel built MaydayLog to bridge that gap.

MaydayLog is not written by journalists or consultants. It is written by someone who goes to work in an engine room — and understands exactly what working engineers and cadets need to know.

Engine Cadet Cruise Ship Engineer MEIN SCHIFF RELAX TUI Cruises Maritime Safety Incident Analysis
Our Principles

What MaydayLog Stands For

🎯
Accuracy above all
Every finding we publish is sourced from official investigation reports. We never speculate, never sensationalise, and never publish without credible sourcing.
⚖️
No blame — only learning
Incidents happen in complex systems. MaydayLog never assigns personal blame. Every analysis focuses on systemic failures and what the industry can learn — not who to point at.
🌍
Free for every seafarer
The 1.9 million seafarers worldwide include engineers in the Philippines, cadets in India, and officers in Eastern Europe. Safety knowledge belongs to all of them — not behind a paywall.
📋
Plain English always
If a junior cadet can't understand it, we haven't done our job. Every case study is written to be clear and readable — without losing technical accuracy.
🔗
Always credit the source
Investigation authorities do the hard work of producing these reports. MaydayLog amplifies their findings — and always links to the original official source.
🚢
Built by someone at sea
MaydayLog is not a media company or consultancy. It is maintained by a working seafarer — which means the content is grounded in the reality of what happens aboard a real vessel.

Start Learning From Real Incidents

Every week a new case study is published — free, detailed, and written for the people who keep ships running. No signup required.