NTSB investigations: Mitsubishi MU-2B-30, 1996
2 cases on aircraft the registry lists as Mitsubishi MU-2B-30. 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
| 1972 | 1 |
|---|---|
| 1974 | 1 |
| 1975 | 1 |
| 1977 | 2 |
| 1978 | 1 |
| 1980 | 1 |
| 1982 | 1 |
| 1983 | 1 |
| 1987 | 1 |
| 1992 | 1 |
| 1996 | 2 |
| 1997 | 1 |
Where
Latest 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 year(c.\"eventDate\") = 1996
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('5780410'))
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 year(c."eventDate") = 1996
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('5780410'))
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 NYC96LA188Accident · No injuriesLimited investigationFinal reportMitsubishi MU-2B-30 · Chillicothe, OHfailure of the pilot to follow the published emergency procedures after loss of power in the left engine. Factors relating to the accident were: fatigue failure of the left torque sensor and gear assembly, which resulted in the loss of engine power, failure…NTSB MIA96IA114Incident · No injuriesIncident investigationFinal reportMitsubishi MU-2G-30 · Columbia, SCfailure of the nose landing gear bearing due to improper assembly and staking (inadequate quality control) by the manufacturer; which prevented the nose gear from retracting and the main gear from extending, and resulted in a subsequent landing on the nose…