# NTSB investigations: Mitsubishi MU-2B-60: Loss of engine power

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 DEN05FA034](https://openairdocs.org/ntsb/DEN05FA034.md): Mitsubishi MU-2B-60 · Englewood, CO · Accident · 2 fatal · Field investigation · Final report · Dec 11, 2004 · N538EA · Destroyed
  > the pilot's failure to maintain minimum controllable airspeed during the night visual approach resulting in a loss of control and uncontrolled descent into terrain. A contributing factor was the precautionary shutdown of the left engine for undetermined…
- [NTSB FTW03IA073](https://openairdocs.org/ntsb/FTW03IA073.md): Mitsubishi MU-2B-60 · Memphis, TN · Incident · No injuries · Incident investigation · Final report · Aug 20, 2002 · N610CA · No damage
  > the loss of right engine power as a result of a fatigue failure of the propeller shaft coupling.
- [NTSB CHI00FA070](https://openairdocs.org/ntsb/CHI00FA070.md): Mitsubishi MU-2B-60 · Lewiston, ID · Accident · 1 fatal · Field investigation · Final report · Feb 11, 2000 · N152BK · Destroyed
  > the pilot failed to follow the flight manual procedures and did not engage the Continuous Ignition system resulting in both engines flaming out when the air induction system was blocked with ice. Additional factors to the accident included the hilly terrain,…
- [NTSB MIA96FA067](https://openairdocs.org/ntsb/MIA96FA067.md): Mitsubishi MU-2B-60 · West Columbia, SC · Accident · Serious injuries · Field investigation · Final report · Jan 19, 1996 · N50KW · Destroyed
  > a total loss of power on one engine for undetermined reasons, and the pilot-in-command's failure to maintain airspeed (VMC) resulting in an in-flight loss of control. Contributing to the accident was the wind gusts encountered while on final approach to land.

## 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 ('5780460')
    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" = 350))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC
```

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

---
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.