NTSB investigations: Mitsubishi MU-2B-25
14 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 |
|---|---|
| 1977 | 1 |
| 1979 | 2 |
| 1981 | 1 |
| 1982 | 1 |
| 1990 | 3 |
| 1992 | 1 |
| 2005 | 1 |
| 2011 | 1 |
| 2013 | 1 |
| 2015 | 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 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."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 GAA15CA303Accident · No injuriesData collectionFinal reportMitsubishi MU 2B-25 · Arvin, CAThe pilot's failure to maintain clearance from trees while taxiing into position for takeoff on a narrow private airstrip, resulting in the left wing striking a tree.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 ERA11LA507Accident · No injuriesLimited investigationFinal reportMitsubishi MU-2B-25 · Atlanta, GAThe improper installation of the nose landing gear strut and subsequent collapse of the nose landing gear during landing.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 DEN93LA013Accident · No injuriesLimited investigationFinal reportMitsubishi MU-2B-25 · Broomfield, COA failure by FBO personnel to properly connect the nose wheel torque link after towing the aircraft.NTSB MIA90IA148Incident · No injuriesIncident investigationFinal reportMitsubishi MU-2B · Tyndall Afb, FLA propeller blade fatigue failure due to improper overhaul by other maintenance personnel not performing overhaul in accordance with factory service bulletins.NTSB DEN90LA047Accident · No injuriesLimited investigationFinal reportMitsubishi MU-2B-25 · Broomfield, COLoss of directional control by the pilot, during takeoff ground run. Contributing to this accident were a loss of power on the left engine due to snow ingestion, heavy snow showers in progress and an icy, snow covered runway.NTSB MIA90LA051Accident · No injuriesLimited investigationFinal reportMitsubishi MU-2B-25 · Jacksonville, FLFailure of the owner/operator to obtain proper maintenance and inspection of the aircraft. Factors related to the accident were: operation of the aircraft by the pilot without a current annual inspection (known deficiency), an oil leak in the left engine…NTSB MKC82IA137Incident · No injuriesIncident investigationFinal reportMitsubishi MU-2B-25 · St. Joseph, MOAfter takeoff, the pilot was cleared to climb to 6000 ft MSL. While climbing through about 5000 ft, he heard a loud noise (bam) as the left engine lost power. The left engine was shut down and feathered and a landing was made with no other problems. An…NTSB FTW81FA139Accident · 5 fatalClosedMitsubishi MU-2B · Mcleod, TXNTSB FTW80FA019Accident · 1 fatalClosedMitsubishi MU-2B · Post Oak, TXNTSB OAK79FVG43Accident · No injuriesClosedMitsubishi MU2 · Sacramento, CANTSB CHI77FEC25Accident · Serious injuriesClosedMitsubishi MU-2B · Ypsilanti, MINTSB IAD76AI033Accident · 5 fatalClosedMitsubishi MU-2K · Jefferson City, TN