NTSB investigations: Mitsubishi MU-2B-60
5 cases on aircraft the registry lists as Mitsubishi MU-2B-60, where the first occurrence was “Loss of control - in flight”. 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
| 1986 | 1 |
|---|---|
| 1988 | 1 |
| 1992 | 1 |
| 1998 | 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\" = 250))
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" = 250))
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 IAD04FA021Accident · 1 fatalField investigationFinal reportMitsubishi MU-2B-60 · Ferndale, MDThe pilot's failure to maintain airspeed during a sharp turn, which resulted in an inadvertent stall and subsequent impact with terrain. Factors included the pilot's failure to fly to the intended point of landing, and his abrupt course reversal back towards…NTSB CHI99FA023Accident · 2 fatalField investigationFinal reportMitsubishi MU-2B-60 · Rock, KSthe pilot failed to maintain control of the aircraft and made an improper evaluation of the weather. Additional factors were flying a test flight at night with the icing conditions in the clouds.NTSB DEN92FA040Accident · 6 fatalField investigationFinal reportMitsubishi MU-2B-60 · New Castle, COAn inadvertent stall during an instrument approach with the autopilot engaged. A factor was: the pilot's physical impairment from a prescription drug.NTSB CHI89FA026Accident · 1 fatalField investigationFinal reportMitsubishi MU-2B-60 · Chicago, ILThe first takeoff was aborted due to a perceived engine problem. Six minutes later on second takeoff, the aircraft climbed to 50 feet, drifted to the right, rolled right and impacted in the infield. This was a single pilot operation in a complex aircraft.…NTSB CHI86FA098Accident · 5 fatalField investigationFinal reportMitsubishi MU-2B-60 · Eola, ILEvidence shows co-pilot called, 'mayday, uncontrolled spin' after acft radar track showed decel from 180 to 120 KTS over 2 min period while maintaining constant 4000 ft crz alt. Constant alt consistent with autopilot/autotrim use, particularly in view of…