NTSB investigations: Mitsubishi MU-2B-35
26 cases on aircraft the registry lists as Mitsubishi MU-2B-35. 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
| 1976 | 1 |
|---|---|
| 1977 | 2 |
| 1978 | 3 |
| 1979 | 1 |
| 1980 | 1 |
| 1981 | 3 |
| 1984 | 1 |
| 1985 | 1 |
| 1986 | 1 |
| 1988 | 2 |
| 1989 | 1 |
| 1990 | 1 |
| 1993 | 2 |
| 1995 | 1 |
| 2000 | 1 |
| 2001 | 1 |
| 2002 | 1 |
| 2003 | 1 |
| 2006 | 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 ('5780411'))
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 ('5780411'))
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 DEN06MA119Accident · 1 fatalMajor investigationFinal reportMitsubishi MU-2B-35 · Argyle, FLthe pilot's inadvertent flight into thunderstorm activity that resulted in the loss of control, design limits of the airplane being exceeded and subsequent in-flight breakup. A contributing factor was the failure of air traffic control to use available radar…NTSB MIA04WA027Accident · Serious injuriesForeign investigationMitsubishi MU-2B-35 · Bonaire, NTNTSB MIA02FA084Accident · 2 fatalField investigationFinal reportMitsubishi MU-2B-35 · Carolina, PRThe failure of the pilot to maintain airspeed (Vs) while maneuvering following inadvertent encounter with clouds resulting in an inadvertent stall and uncontrolled descent and subsequent in-flight collision with trees, a wall, and a building.NTSB MIA01FA206Accident · 1 fatalField investigationFinal reportMitsubishi MU-2B-35 · Hilton Head, SCImproper maintenance/installation and and inadequate inspection of the airplane's flap torque tube joints during routine maintenance by company maintenance personnel, which resulted in the right flap torque tube assembly coupler becoming detached and the…NTSB FTW00LA242Accident · No injuriesLimited investigationFinal reportMitsubishi MU-2B-35 · Corsicana, TXthe in-flight separation of the propeller blade, which resulted from intergranular corrosion and fatigue cracking.NTSB MIA95FA226Accident · Serious injuriesField investigationFinal reportMitsubishi MU-2B-35 · Smyrna, TNFailure of the pilot to maintain a proper climb rate after takeoff, and his inadvertent entry in a descending spiral, which he failed to correct. Factors relating to the accident were: darkness, and the pilot becoming spatially disoriented during the initial…NTSB SEA93FA088Accident · 4 fatalField investigationFinal reportMitsubishi MU-2B-35 · Casper, WYFailure of the pilot to maintain proper altitude during the night IFR approach in instrument meteorological conditions (IMC).NTSB ANC93LA025Accident · No injuriesLimited investigationFinal reportMitsubishi MU-2B-35 · Nome, AKFuel starvation due to improper refueling procedures by the FBO personnel, inadequate preflight by the pilot, and resultant ice in the fuel, which blocked fuel flow to the engines. A factor was the lack of suitable terrain for a forced landing.NTSB NYC90LA066Accident · No injuriesLimited investigationFinal reportMitsubishi MU-2B-35 · Teterboro, NJThe pilot of N349MA failed to see and avoid another airplane taxiing in the same direction.NTSB NYC89FA111Accident · Minor injuriesField investigationFinal reportMitsubishi MU-2B-35 · Syracuse, NYFailure of the crew of brockway flight 993 to see-and-avoid the other aircraft due to the first officer's inadequate visual lookout & the captain's inadequate supervision. Factors related to the accident were: the weather condition, and the ground…NTSB DCA89LA012Accident · 1 fatalLimited investigationFinal reportMitsubishi MU-2J · Missing (Pacific Ocean)During a flt at night from majuro, marshall islands to cairns, australia, the plt requested a dscnt from FL 190 to 12,000 to remove ice from the airframe. Later, he requested a climb to FL 200. After starting the climb, he made a mayday call to sidney flt…NTSB NYC88LA085Accident · No injuriesLimited investigationFinal reportMitsubishi MU-2B-35 · Philadelphia, PAThe Mitsubishi MU-2B-35 landed and damage was observed on the underside of the left wing midway between the engine and tip tank and outboard to the tip tank. Further examination of the wing showed a broken lower front wing spar and a bent rear lower wing…NTSB FTW86MA097Accident · 1 fatalMajor investigationFinal reportMitsubishi MU-2B-35 · Bartlett, TXAbout 6 min after takeoff, at 2138:31 CDT, the plt rprtd level at 9000 ft MSL. At 2140:17, he transmitted that he had trouble & said he could not control or disconnect the autopilot (a/p) which was causing the acft to descend. At 2141:14,he stated he was…NTSB FTW85LA183Accident · No injuriesLimited investigationFinal reportMitsubishi MU2J · Patterson, LAOn visual final apch to the arpt at night the acft entered ground fog. Reflection of the landing lights in the fog was distracting. The acft landed in the adjacent seaplane landing area instead of on the hard surface rwy. A subsequent inspection of the aprt…NTSB FTW85LA067Accident · No injuriesLimited investigationFinal reportMitsubishi MU-2B-35 · Robert Lee, TXThe acft was on ferry flt with a planned stop at Robert Lee arpt. Prior to touchdown, during the flare, the plt saw 3 OR4 deer in the middle of the runway. He banked to the left and prior to adding power to go-around, the acft settled to the ground next to…NTSB DEN82FA008Accident · 7 fatalClosedMitsubishi MU-2B · Eagle, CONTSB FTW81FA075Accident · 2 fatalClosedMitsubishi MU-2B · Lajitas, TXNTSB CHI81FET04Accident · No injuriesClosedMitsubishi MU-2B · Wabash, INNTSB FTW80FA042Accident · 4 fatalClosedMitsubishi MU-2B · Houston, TXNTSB FTW79FPG15Accident · Minor injuriesClosedMitsubishi MU-2B · Searcy, ARNTSB DEN78FA065Accident · 6 fatalClosedMitsubishi MU-2J · Raton, NMNTSB UNK78X0128Accident · Serious injuriesClosedMitsubishi MU-2 · Savnt Lake, CanadaNTSB UNK78X0106Accident · 5 fatalClosedMitsubishi MU2 · Neiva, ColombiaNTSB FTW78FPA10Accident · Serious injuriesClosedMitsubishi MU-2J · Addison, TXNTSB FTW77FA045Accident · 1 fatalClosedMitsubishi MU-2B · Austin, TXNTSB IAD76AI054Accident · 3 fatalClosedMitsubishi MU-2B · Easton, MD