NTSB investigations: Mitsubishi MU-2B-30

14 cases on aircraft the registry lists as Mitsubishi MU-2B-30. 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.

Defining event

Finding

Phase of flight

Aircraft model

Cases per year

19722026

NTSB investigations: Mitsubishi MU-2B-30 per year, 1972–2026: 14 cases
1972	1
1974	1
1975	1
1977	2
1978	1
1980	1
1982	1
1983	1
1987	1
1992	1
1996	2
1997	1

Where

Open the map

Latest cases

Query with SQL

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 ('5780410')) ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC

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 ('5780410'))
  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 ('5780410'))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC

Run 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 CHI98FA074Accident · 2 fatalField investigationFinal reportMitsubishi MU-2B-30 · Wayne, ILthe pilot in command failed to maintain control of the aircraft. A factor was the lack of experience of the pilot and copilot in the type and model of aircraft. An additional factor was the pilot did not follow the proper procedure when the flaps were raised…Dec 30, 1997 · N999WB · Destroyed NTSB NYC96LA188Accident · No injuriesLimited investigationFinal reportMitsubishi MU-2B-30 · Chillicothe, OHfailure of the pilot to follow the published emergency procedures after loss of power in the left engine. Factors relating to the accident were: fatigue failure of the left torque sensor and gear assembly, which resulted in the loss of engine power, failure…Sep 28, 1996 · N618BB · Substantial damage NTSB MIA96IA114Incident · No injuriesIncident investigationFinal reportMitsubishi MU-2G-30 · Columbia, SCfailure of the nose landing gear bearing due to improper assembly and staking (inadequate quality control) by the manufacturer; which prevented the nose gear from retracting and the main gear from extending, and resulted in a subsequent landing on the nose…Apr 12, 1996 · N920S · Minor damage NTSB DEN92FA064Accident · 6 fatalField investigationFinal reportMitsubishi MU-2B-30 · Alamagordo, NMThe failure of the pilot to exercise adequate VFR departure terrain avoidance procedures, and the failure of the controller to issue a safety alert to the pilot. Factors which contributed to the accident were: the pilot's lack of familiarity with the…Jun 25, 1992 · N108SC · Destroyed NTSB MIA88WA074Accident · No injuriesForeign investigationMitsubishi MU-2B-30 · San Salvador, El SalvadorDec 23, 1987 · N255C · Substantial damage NTSB FTW83LA096Accident · No injuriesLimited investigationFinal reportMitsubishi MU-2B-30 · Lubbock, TXThe plt stated that after a normal approach, touchdown & initial roll-out, the acft veer right & struck a 3 to 4 ft snowbank. An investigation revealed that snow had been falling for over 12 hrs & an 80 ft wide path had been plowed down the center of the…Jan 21, 1983 · N555CH · Substantial damage NTSB ATL82FA110Accident · 6 fatalField investigationFinal reportMitsubishi MU-2B-30 · Lafayette, GADrg the wx briefing the plt was advised that VFR flt was not recommended due to low ceilings & poor visibility. The plt responded he had to go to ft. payne VFR because they have no instrument approach. A jeppesen us (lo)29 low alt enroute chart was found at…Apr 20, 1982 · N165MA · Destroyed NTSB CHI81FEG03Accident · Minor injuriesClosedMitsubishi MU-2B · Cambellstown, OHDec 15, 1980 · N93UM · Substantial damage NTSB IAD78DLQ08Accident · No injuriesClosedMitsubishi MU-2 · Hawesville, KYJan 19, 1978 · N115S · Destroyed NTSB NYC77FA046Accident · 7 fatalClosedMitsubishi MU-2 · Bronx, NYApr 5, 1977 · N888RJ · Destroyed NTSB MIA77FA049Accident · Serious injuriesClosedMitsubishi MU-2B · Augusta, GAApr 1, 1977 · N100SW · Destroyed NTSB HAY76AL042Accident · 9 fatalClosedMitsubishi MU-2B · Rollinsville, CODec 26, 1975 · N133MA · Destroyed NTSB DEN74AD041Accident · 5 fatalClosedMitsubishi MU-2B · Glenwood Spg, COMar 2, 1974 · N711AH · Destroyed NTSB NYC72AN129Accident · 3 fatalClosedMitsubishi MU-2G · Atlantic City, NJApr 16, 1972 · N132MA · Destroyed