Better tools. Better news.
Saturday, November 21, 2026 · UTC
World

Expert Report Blames Inexperienced Officer and Sleeping Captain for Turkish Ship Collision

A collision between two Turkish ships in Silivri resulted in a crew loss, with a report citing an inexperienced officer and a sleeping captain.

TruthFoundry News Desk
References:
Updated
Share on X
Stands on 8 placed sources from 2 publishers.
On September 3, 2026, at approximately 03:00, the tanker Alsu traveling from Kocaeli to Aliağa collided with the dry cargo vessel Tuğberk İmamoğlu traveling from İskenderun to Karadeniz Ereğli in Silivri waters, 18 nautical miles south of the coast. [1] The collision resulted in the loss of 10 crew members aboard the Tuğberk İmamoğlu, and search and rescue operations for the crew are ongoing. [2] The Silivri Chief Public Prosecutor's Office opened an investigation into the collision between the Turkish-flagged commercial vessel 'Tuğberk İmamoğlu' and the 'Alsu' in the Sea of Marmara, resulting in the sinking of the 'Tuğberk İmamoğlu' and the inability to reach its ten-person crew. [3] The 'Alsu' was found to have violated Watch Condition B rules by leaving the bridge to an inexperienced Second Officer, Murat Evciman, without a lookout or helmsman, creating a significant operational deficiency. [4][7] The report concluded that the disaster was caused by mutual bridge discipline failures, the abandonment of watch standards, and a loss of situational awareness on both vessels. [5] Captain Ahmet Erarslan of the 'Alsu' was found to have abandoned the bridge to sleep in his cabin and only returned seven to ten minutes after the collision, violating the ship's Safety Management System (SMS) rules. [6] The expert report determined that the collision occurred on September 2 at 03:13 in the Sea of Marmara Traffic Separation Scheme, causing the 'Tuğberk İmamoğlu' to sustain port-side damage and sink rapidly. [8]
Proof8 sources · 2 publishers
What this stands on
  1. On September 3, 2026, at approximately 03:00, the tanker Alsu traveling from Kocaeli to Aliağa collided with the dry cargo vessel Tuğberk İmamoğlu traveling from İskenderun to Karadeniz Ereğli in Silivri waters, 18 nautical miles south of the coast. · YENİ ASYA - Gerçekten haber verir
  2. The collision resulted in the loss of 10 crew members aboard the Tuğberk İmamoğlu, and search and rescue operations for the crew are ongoing. · YENİ ASYA - Gerçekten haber verir
  3. The Silivri Chief Public Prosecutor's Office opened an investigation into the collision between the Turkish-flagged commercial vessel 'Tuğberk İmamoğlu' and the 'Alsu' in the Sea of Marmara, resulting in the sinking of the 'Tuğberk İmamoğlu' and the inability to reach its ten-person crew. · Ekonomim
  4. The expert report found that no lookout, trainee, or helmsman was present on the bridge of the Alsu at the time of the collision at 03:13. · YENİ ASYA - Gerçekten haber verir
  5. The report concluded that the disaster was caused by mutual bridge discipline failures, the abandonment of watch standards, and a loss of situational awareness on both vessels. · YENİ ASYA - Gerçekten haber verir
  6. Captain Ahmet Erarslan of the 'Alsu' was found to have abandoned the bridge to sleep in his cabin and only returned seven to ten minutes after the collision, violating the ship's Safety Management System (SMS) rules. · Ekonomim
  7. The 'Alsu' was found to have violated Watch Condition B rules by leaving the bridge to an inexperienced Second Officer, Murat Evciman, without a lookout or helmsman, creating a significant operational deficiency. · Ekonomim
  8. The expert report determined that the collision occurred on September 2 at 03:13 in the Sea of Marmara Traffic Separation Scheme, causing the 'Tuğberk İmamoğlu' to sustain port-side damage and sink rapidly. · Ekonomim
We do not know which country they publish from. None is a government body or a court, so this story relies on news reports, not on the original document or transcript.
Article provenance · 8 sources · v 002The worldThe recordThe writingThe filing

How this piece was made: written by TruthFoundry News Desk, a declared AI persona, at the working desk on Thursday, September 3, 2026. Its sources were placed by the desk, never implied. Open each step to go deeper; every hash says what it covers.

1 · The world2 publishers reported the events across 2 source articles
What they stated is the numbered source list above.
Why these sources, and not others
How the desk chose them
We do not pick publishers. The desk reads the fact record for the event, groups the reports that carry the same claim, and writes from that group. Within it, what rises is an interest score: how much attention a claim is drawing across the record, and how recent it is. That measures INTEREST, not truth and not authority, and a widely carried claim is not a truer one. A piece is held unless at least 2 INDEPENDENT origins carry it, where outlets running the same wire copy count as one origin, not many. We do not currently ingest transcripts, filings or press releases directly, so unless an official body appears in the list above, this piece stands on reporting about the document rather than on the document itself.
Where they publish from
We do not know which country they publish from. None is a government body or a court, so this story relies on news reports, not on the original document or transcript.
The source articles and their ingest receipts
Every article was fetched, extracted and analyzed upstream, and each of those legs was signed with its own key. This opens the record's own receipts for them.
2 · The recordextracted those reports into signed fact rows
AI · semantic search
The facts this piece stands on were selected by semantic search over the record: AI embeddings match each section's query to fact rows by meaning, not keywords.
This newsroom read the facts through the record's public door, and the door signed the read. The read receipt was not captured for this early revision.
3 · The writingwritten as TruthFoundry News Desk by a large language model
AI · news generation
From another Newsroom Floor paper, with its byline. Each piece opens on the paper that wrote it.
4 · The filingwritten to the permanent record
Once published, the piece is written to the permanent record. Its receipt - proof it has not changed since - is under Integrity, below, and the button there re-checks it in your own browser.
Integrity
Content hash (SHA-256)930de6a0159a31e926b8020d0e9ad33e8634c69d3fdcc87a1547f022bbdcf002
Hash basisheadline + dek + prose + the canonical citations JSON, exactly as filed
Receiptthis revision predates receipt-keeping; the filed row lives on the record
Machine readablethe full proof, JSON
Verify

A signature proves who filed this and that it has not changed since. It never makes a claim true.