Fatal NTSB investigations: Mitsubishi MU-2B-60
23 cases on aircraft the registry lists as Mitsubishi MU-2B-60. 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
| 1981 | 1 |
|---|---|
| 1983 | 2 |
| 1984 | 1 |
| 1986 | 1 |
| 1988 | 1 |
| 1990 | 2 |
| 1991 | 1 |
| 1992 | 2 |
| 1993 | 1 |
| 1998 | 1 |
| 2000 | 1 |
| 2003 | 1 |
| 2004 | 2 |
| 2005 | 1 |
| 2006 | 1 |
| 2010 | 1 |
| 2016 | 1 |
| 2020 | 1 |
| 2021 | 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 ('5780460'))
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 ('5780460'))
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 CEN21FA209Accident · 4 fatalClass 3 · FieldFinal reportMitsubishi MU2B · Hattiesburg, MSThe pilot’s failure to maintain control of the airplane during the night instrument approach which resulted in an inadvertent aerodynamic stall from which the pilot was unable to recover.NTSB CEN20LA215Accident · 1 fatalClass 3 · LimitedFinal reportMitsubishi MU2B · Sioux Falls, SDThe pilot’s failure to maintain control of the airplane during takeoff for reasons that could not be determined.NTSB CEN16RA136Accident · 7 fatalForeign investigationMitsubishi MU 2B · Iles-de-la-Madeleine, CanadaimportNTSB CEN10FA097Accident · 4 fatalField investigationFinal reportMitsubishi MU-2B-60 · Elyria, OHThe pilot's failure to maintain adequate airspeed during the instrument approach, which resulted in an aerodynamic stall and impact with terrain.NTSB MIA06FA120Accident · 1 fatalField investigationFinal reportMitsubishi MU-2B-60 · Fort Pierce, FLthe pilot’s loss of aircraft control during the initial climb which was precipitated by the sudden loss of thrust and increase in drag from the right engine, and the pilot’s failure to adhere to the published emergency procedures regarding the position of the…NTSB DFW05FA202Accident · 1 fatalField investigationFinal reportMitsubishi MU-2B-60 · Parker, COThe pilot’s failure to fly a stabilized instrument approach at night which resulted in controlled flight into terrain. Contributing factors were; the dark night, low clouds, the inadequate design and function of the airport facility’s Minimum Safe Altitude…NTSB DEN05FA034Accident · 2 fatalField investigationFinal reportMitsubishi MU-2B-60 · Englewood, COthe pilot's failure to maintain minimum controllable airspeed during the night visual approach resulting in a loss of control and uncontrolled descent into terrain. A contributing factor was the precautionary shutdown of the left engine for undetermined…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 NYC03LA046Accident · 1 fatalLimited investigationFinal reportMitsubishi MU-2B-60 · Cleveland, OHthe bank couriers inadequate visual lookout, as he approached an airplane with operating engines. A factor was the lack of guidance and training from the bank, for working around airplanes with operating engines.NTSB CHI00FA070Accident · 1 fatalField investigationFinal reportMitsubishi MU-2B-60 · Lewiston, IDthe pilot failed to follow the flight manual procedures and did not engage the Continuous Ignition system resulting in both engines flaming out when the air induction system was blocked with ice. Additional factors to the accident included the hilly terrain,…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 DCA93GA042Accident · 8 fatalClass 1Final reportMitsubishi MU-2B-60 · Zwingle, IAThe fatigue cracking and fracture of the propeller hub arm. The resultant separation of the hub arm and the propeller blade damaged the engine, nacelle, wing, and fuselage, thereby causing significant degradation to aircraft performance and control that made…NTSB DCA92MA049Accident · 6 fatalClass 1 · MajorFinal reportMitsubishi MU-2B-60 · Greenwood, INThe inherent limitations of the see-and-avoid concept of separation of aircraft operating under visual flight rules that precluded the pilots of the MU-2 and the PA-32 from recognizing a collision hazard and taking actions to avoid the midair collision.…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 FTW91FA043Accident · 3 fatalField investigationFinal reportMitsubishi MU-2B-60 · Tulsa, OKThe shutdown of one engine for undetermined reasons, and the pilot's failure to maintain vmca during a critical phase of flight. A factor in the accident was the pilot's improper emergency procedure.NTSB FTW90FA072Accident · 5 fatalField investigationFinal reportMitsubishi MU-2B-60 · Putnam, TXImproper planning/decision by the pilot, which resulted in excessive accummulation of structural icing (on the aircraft's wings, stabilizers, fuselage, and/or engine inlets), and his failure to maintain adequate airspeed and aircraft control. Factors related…NTSB DEN90FA055Accident · 1 fatalField investigationFinal reportMitsubishi MU-2B-60 · Rapid City, SDFailure of the pilot to maintain adequate airspeed (VMC), which resulted in a loss of aircraft control. A factor related to the accident was: fatigue failure of a coupling shaft in the #1 engine, which resulted in loss of power in that engine.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…NTSB DCA84AA022Accident · 1 fatalFinal reportMitsubishi MU-2B-60 · Burlington, CTThe acft was flown earlier in the day for a sales demonstration. On the return flt, when the landing gear were lowered, the plt thought he heard a noise emitting from the gear, although cockpit indications were normal. The acft landed at johnnycake arpt & was…NTSB DCA83AA022Accident · 4 fatalFinal reportMitsubishi MU-2B-60 · Jeffersonville, GAThe acft was on the return portion of a round trip flt, hauling canceled bank checks. When they boarded before takeoff, the plt's wife, who was not a plt, occupied the r front seat & his 2 daughter's, ages 4 & 6, were in the passenger seats. Previous legs of…NTSB LAX83FA083Accident · 6 fatalField investigationFinal reportMitsubishi MU-2B-60 · Scottsdale, AZThe acft diverted from Scottsdale AZ to a flt course to sedona because of thunderstorms & high winds at Scottsdale, but after a radio conversation with Scottsdale twr, the plt decided to reroute to land at Scottsdale. The plt did not read back the weather…NTSB DEN82FA006Accident · 2 fatalClosedMitsubishi MU-2B · Saratoga, WY