# NTSB investigations: Cessna 340: Loss of engine power(total) - nonmechanical

NTSB aviation accident and incident investigations since 1962: the probable cause, findings, aircraft, crew, weather and docket of each, linked to the FAA registry and the FAA’s own reports.

## Latest cases

- [NTSB DEN02FA034](https://openairdocs.org/ntsb/DEN02FA034.md): Cessna 340 · Englewood, CO · Accident · 4 fatal · Field investigation · Final report · Mar 24, 2002 · N341DM · Destroyed
  > the pilot not following procedures/directives (flying a landing approach with the left fuel selector in the auxiliary position). Contributing factors were the loss of the left engine power due to fuel starvation, the pilot's failure to maintain aircraft…
- [NTSB NYC92FA029](https://openairdocs.org/ntsb/NYC92FA029.md): Cessna 340 · Columbus, OH · Accident · 5 fatal · Field investigation · Final report · Nov 13, 1991 · N7672Q · Destroyed
  > The pilot's improper execution of an emergency procedure, after an engine failure, which resulted in the loss of airplane control. Factors related to the accident were: the pilot's improper management of the fuel system; the pilot's lack of proficiency in…
- [NTSB ATL90FA145](https://openairdocs.org/ntsb/ATL90FA145.md): Cessna 340 · Atlanta, GA · Accident · Serious injuries · Field investigation · Final report · Jul 15, 1990 · N9865F · Substantial damage
  > The pilot-in-command's inadequate fuel management, in that he did not select main fuel tanks prior to this approach. This resulted in fuel starvation to the engines, and the subsequent loss of all engine power.
- [NTSB LAX89LA224](https://openairdocs.org/ntsb/LAX89LA224.md): Cessna 340 · Paso Robles, CA · Accident · No injuries · Limited investigation · Final report · Jun 20, 1989 · N69549 · Substantial damage
  > Improper use (mismanagement) of the fuel system by the pilot, which resulted in fuel starvation. Related factors were: the lack of fuel quantity indicators (not installed) in the aircraft, flight by the pilot with this known deficiency, and trees in the…

## The whole list in SQL

Runs in DuckDB 1.2 or later on the release's Parquet files over HTTPS:

```sql
SELECT c."ntsbNumber", c."eventDate", c."eventType", c."eventCity", c."eventStateOrRegion", a.n_number, a."aircraftMake", a."aircraftModel", c."highestInjuryLevel", c."totalFatal", c."completionStatus", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c."mKey" AND a.position = 1
WHERE c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2076404')
    AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 353))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC
```

This list as a web page: https://openairdocs.org/ntsb?model=2076404&occurrence=353

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.