# NTSB investigations: Beech 65: 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 MIA93FA031](https://openairdocs.org/ntsb/MIA93FA031.md): Beech 65 · Orlando, FL · Accident · 5 fatal · Field investigation · Final report · Dec 19, 1992 · N555GC · Destroyed
  > The pilot's failure to feather the propeller to maintain altitude following a loss of power of the left engine. The power loss was due to an improperly maintained fuel system. In addition, the right engine lost power for an undetermined reason(s).
- [NTSB BFO90LA001](https://openairdocs.org/ntsb/BFO90LA001.md): Beech A65 · Friendly, MD · Accident · Minor injuries · Limited investigation · Final report · Oct 15, 1989 · N186M · Substantial damage
  > The pilot's improper use of his fuel supply, which resulted in fuel starvation and loss of power in the left engine. A factor related to the accident was the pilot's lack of familiarity with the aircraft.
- [NTSB BFO86FID02](https://openairdocs.org/ntsb/BFO86FID02.md): Beech BE65 · Wakefield, VA · Accident · No injuries · Final report · Feb 27, 1986 · N1QV · Substantial damage
  > The acft landed short of the rwy after loss of power on both engines. Contact with a dirt bank sheared the landing gear and the acft slid onto & down the rwy for about 436 ft before stopping. The plt said the fuel gauges were 1/4 on mains and 1/8 on avg…
- [NTSB FTW84LA249](https://openairdocs.org/ntsb/FTW84LA249.md): Beech 65 · Zapata, TX · Accident · No injuries · Limited investigation · Final report · May 25, 1984 · N404C · Destroyed
  > According to law enforcement officers, the acft experienced double eng failure and made a forced landing in unimproved terrain. During the landing rollout the acft struck several trees. An intense post crash fire erupted destroying all but one wing tip of 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 ('1152802')
    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=1152802&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.