FirstAlerts
Plane CrashesVersion 2

NTSB Investigating DHC-6-300 Accident Near San Clemente, California

The accident record lists substantial damage to a Rampart Aviation Twin Otter on August 11, 2025; the cause has not been determined.

By AI ReporterUpdated Aug 7, 2026, 10:48 a.m. ET
A was substantially damaged in an accident on August 11, 2025, at about 6:30 p.m. local time, according to the accident record, which lists the nearest city as "" in the United States. The record remains a preliminary filing and the matter is developing. The accident record identifies the aircraft as registration and the operator as , and classifies the flight as a Part 135 commuter or on-demand operation. The record does not list injury counts, which is usual for a preliminary filing. No casualty figures are available in the material reviewed. The National Transportation Safety Board is listed in the accident record as the investigating body, and the investigation is open. The cause has not been determined. Aircraft registry records describe as a Dehavilland DHC-6-300, a twin-engine turboprop landplane with Pratt & Whitney PT6A-34 engines, serial number 334, registered in the United States. The registry lists the registered owner as Transport Company LLC; the owner of record is not necessarily the operator, the pilot, or otherwise connected to the flight. Searches of registry, ownership and business sources returned no entity matching that exact name, and no factual description of the organisation could be established. As a matter of record, the NTSB database, which begins in 2008, contains three other cases involving the Dehavilland DHC-6-300, none of them fatal. That count is a record of past cases only and says nothing about the cause of this accident.

Was this report accurate and useful?

Reference data

From aircraft and geographic registries, not from the news sources. Registry records can be out of date, and describe the aircraft and the place only — they say nothing about what happened.

Registration
N344CS
Type
Dehavilland DHC-6-300 — twin-engine turboprop landplane
Engines
P & W PT6A-34
Registered owner
Transport Company LlcThe owner of record is not necessarily the operator, the pilot, or otherwise connected to the flight.

Sources

No sources recorded.

Revision history

  1. Version 27 Aug 2026, 14:48current

    Location now given as the accident record words it ("San Celmente, CA") rather than corrected, and investigating-body attribution tied explicitly to the accident record.

  2. Version 15 Aug 2026, 22:00

    First published.

How we work

This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.

Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.

Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.

None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.