Fatal NTSB investigations: Mitsubishi MU-2B-25
5 cases on aircraft the registry lists as Mitsubishi MU-2B-25. 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
| 1975 | 1 |
|---|---|
| 1979 | 1 |
| 1981 | 1 |
| 2005 | 1 |
| 2013 | 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.\"highestInjuryLevel\" = 'Fatal'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('5780409'))
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."highestInjuryLevel" = 'Fatal'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('5780409'))
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 CEN14FA046Accident · 1 fatalField investigationFinal reportMitsubishi MU 2B-25 · Owasso, OKThe pilot's loss of airplane control during a known one-engine-inoperative condition. The reasons for the loss of control and engine shutdown could not be determined because the airplane was not equipped with a crash-resistant recorder and postaccident…NTSB SEA05FA105Accident · 4 fatalField investigationFinal reportMitsubishi MU-2B-25 · Hillsboro, ORThe pilot's failure to obtain minimum controllable airspeed during the takeoff climb, which resulted in a loss of aircraft control when the left engine lost partial power. A fatigue failure to an oil tube, which resulted in the partial power loss to the left…NTSB FTW81FA139Accident · 5 fatalClosedMitsubishi MU-2B · Mcleod, TXNTSB FTW80FA019Accident · 1 fatalClosedMitsubishi MU-2B · Post Oak, TXNTSB IAD76AI033Accident · 5 fatalClosedMitsubishi MU-2K · Jefferson City, TN