Fatal NTSB investigations: Mitsubishi MU-2B-20
9 cases on aircraft the registry lists as Mitsubishi MU-2B-20. 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 |
|---|---|
| 1973 | 1 |
| 1979 | 2 |
| 1985 | 1 |
| 1987 | 1 |
| 1989 | 1 |
| 1991 | 1 |
| 2001 | 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 ('5780407'))
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 ('5780407'))
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 DEN01FA113Accident · 2 fatalField investigationFinal reportMitsubishi MU-2B-20 · Cerrillos, NMthe pilot's loss of aircraft control inflight for reasons undetermined. Contributing factors were the pilot's inadequate transition/upgrade training and his total lack of experience in aircraft make/model.NTSB FTW91FA074Accident · 1 fatalField investigationFinal reportMitsubishi MU-2B-20 · Kenefic, OKImproper planning/decision by the pilots of both aircraft, and the Mitsubishi pilot's misjudgment of his position, while attempting to fly formation at night with an aircraft that did not have all navigation lights operative. Factors related to the accident…NTSB BFO89LA023Accident · 1 fatalLimited investigationFinal reportMitsubishi MU-2B-20F · San Diego, CAPilot incapacitation for an unknown reason.NTSB ATL87FA173Accident · 1 fatalField investigationFinal reportMitsubishi MU-2B · Coral Springs, FLThe pilot reported to ground personnel at fort lauderdale that he was experiencing an avionics problem and the passengerentry door was sprung the day before when it was slammed; however, the pilot elected to depart. The aircraft wreckage was located on June…NTSB FTW86FA015Accident · 1 fatalField investigationFinal reportMitsubishi MU-2B-2D · El Paso, TXThe plt canceled his IFR flt plan and attempted to fly VFR at a relatively low alt over mountainous terrain with low scattered clouds on a dark night. He reported a large lighted area as being downtown El Paso when in reality it was most likely coronado…NTSB DEN80FA012Accident · 2 fatalClosedMitsubishi MU-2B · Provo, UTNTSB IAD80FA007Accident · 5 fatalClosedMitsubishi MU-2F · Nashville, TNNTSB FTW73DQG43Accident · 2 fatalClosedMitsubishi MU-2B · Cedillos C, MexicoNTSB MIA73AM054Accident · 1 fatalClosedMitsubishi MU-2B · Alcolu, SC