Fatal NTSB investigations: Mitsubishi MU-2B-35
13 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 | 1 |
| 1978 | 2 |
| 1980 | 1 |
| 1981 | 2 |
| 1986 | 1 |
| 1988 | 1 |
| 1993 | 1 |
| 2001 | 1 |
| 2002 | 1 |
| 2006 | 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 ('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."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 ('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 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 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 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 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 DEN82FA008Accident · 7 fatalClosedMitsubishi MU-2B · Eagle, CONTSB FTW81FA075Accident · 2 fatalClosedMitsubishi MU-2B · Lajitas, TXNTSB FTW80FA042Accident · 4 fatalClosedMitsubishi MU-2B · Houston, TXNTSB DEN78FA065Accident · 6 fatalClosedMitsubishi MU-2J · Raton, NMNTSB UNK78X0106Accident · 5 fatalClosedMitsubishi MU2 · Neiva, ColombiaNTSB FTW77FA045Accident · 1 fatalClosedMitsubishi MU-2B · Austin, TXNTSB IAD76AI054Accident · 3 fatalClosedMitsubishi MU-2B · Easton, MD