NTSB investigations: Mitsubishi MU-2B-40
17 cases on aircraft the registry lists as Mitsubishi MU-2B-40. 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
| 1980 | 1 |
|---|---|
| 1981 | 3 |
| 1982 | 1 |
| 1992 | 1 |
| 1993 | 1 |
| 1996 | 1 |
| 1999 | 1 |
| 2001 | 1 |
| 2004 | 1 |
| 2006 | 1 |
| 2017 | 2 |
| 2020 | 1 |
| 2025 | 1 |
| 2026 | 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 ('5780440'))
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 ('5780440'))
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 WPR26LA308Accident · No injuriesClass 4 · LimitedFinal reportMitsubishi MU-2B-40 · Norton Shores, MIThe pilot’s failure to extend the landing gear before landing.NTSB WPR25MA128Accident · 6 fatalClass 3 · MajorPreliminary reportMitsubishi MU-2B-40 · Copake, NYOn April 12, 2025, about 1203 eastern daylight time, a Mitsubishi MU-2B-40, N635TA, was destroyed when it was involved in an accident near Copake, New York. The pilot and five passengers were fatally injured. The airplane was operated as a Title 14 Code of…NTSB CEN20LA125Accident · No injuriesClass 3 · LimitedFinal reportMitsubishi MU 2B-40 · Chilton, WIThe pilot's decision to land on the turf runway with insufficient landing performance and his subsequent loss of control during the landing roll.NTSB CEN17FA362Accident · 1 fatalField investigationFinal reportMitsubishi MU 2B-40 · Ainsworth, NEThe pilot's loss of airplane control due to spatial disorientation.NTSB ERA17FA181Accident · 4 fatalField investigationFinal reportMitsubishi MU2B · Eleuthera, BahamasThe pilot's intentional flight into an area of known icing and convective thunderstorm activity, which resulted in a loss of control of the airplane.NTSB NYC06MA208Accident · 2 fatalMajor investigationFinal reportMitsubishi MU-2B-40 · Bunnell, FLThe pilot's inadvertent encounter with thunderstorms.NTSB LAX04FA165Accident · 2 fatalField investigationFinal reportMitsubishi MU-2B-40 · Napa, CAThe pilot's failure to maintain control of the airplane following a shutdown of the left engine during a night visual approach. A factor contributing to the accident was the dark night.NTSB FTW01FA111Accident · 2 fatalField investigationFinal reportMitsubishi MU-2B-40 · The Woodlands, TXThe pilot's failure to maintain airplane control following a loss of right engine power, which resulted in impact with terrain in an uncontrolled descent. A contributing factor was the loss of right engine power as a result of the fatigue failure of the…NTSB NYC99WA121Accident · 2 fatalForeign investigationMitsubishi MU-2B-40 · Perry Sound, CanadaNTSB FTW96LA215Accident · Minor injuriesLimited investigationFinal reportMitsubishi MU-2B-40 · Houston, TXfailure of the pilot to obtain/maintain proper airspeed and flap setting for single engine flight. A factor relating to the accident was: Loss of power in the left engine for an undetermined reason.NTSB NYC93FA177Accident · Minor injuriesField investigationFinal reportMitsubishi MU-2B-40 · S. Charleston, WVwas improper emergency procedures by the pilot which resulted in the shutdown of an operative engine, following a power loss due to a failed torque sensor in the other engine, which resulted in a total power loss approach, landing, and overrun.NTSB BFO92FA094Accident · 2 fatalField investigationFinal reportMitsubishi MU-2B-40 · Concord, NHLoss of control during flight for undetermined reason(s).NTSB DEN82DA029Accident · Minor injuriesFinal reportMitsubishi MU2B-40 · Hayden, COThe aircraft was 20 feet AGL during landing when the crew heard a propeller go into beta mode and the aircraft yawed to the right. The pilot lost control of the aircraft and it collided with a snow bank which separated the wings from the fuselage. Impact…NTSB DEN82FTG02Accident · No injuriesClosedMitsubishi MU-2B · Williston, NDNTSB MIA82FA112Accident · 2 fatalClosedMitsubishi MU-2B · Jacksonville, FLNTSB DEN81FA067Accident · No injuriesClosedSwearingen SA266 · Flagstaff, AZNTSB FTW80FA048Accident · 7 fatalClosedMitsubishi MU-2B · New Orleans, LA