NTSB investigations: Mitsubishi MU-2B-60
4 cases on aircraft the registry lists as Mitsubishi MU-2B-60, where the first occurrence was “Loss of engine power”. Aircraft are matched to the registry by N-number and event date, checked against the reported serial number, make and model, so older matches can be wrong.
Cases per year
| 1996 | 1 |
|---|---|
| 2000 | 1 |
| 2002 | 1 |
| 2004 | 1 |
Where
Open the mapLatest cases
Query with SQL
duckdb -csv -c "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"Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.
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" DESCRun it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
NTSB DEN05FA034Accident · 2 fatalField investigationFinal reportMitsubishi MU-2B-60 · Englewood, COthe 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 FTW03IA073Incident · No injuriesIncident investigationFinal reportMitsubishi MU-2B-60 · Memphis, TNthe loss of right engine power as a result of a fatigue failure of the propeller shaft coupling.NTSB CHI00FA070Accident · 1 fatalField investigationFinal reportMitsubishi MU-2B-60 · Lewiston, IDthe 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 MIA96FA067Accident · Serious injuriesField investigationFinal reportMitsubishi MU-2B-60 · West Columbia, SCa 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.