Skip to content

NTSB investigations: Mitsubishi MU-2B-20

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

19702026

Where

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 ('5780407')) 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 ('5780407'))
  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 ('5780407'))
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 ERA12CA128Accident · No injuriesData collectionFinal reportMitsubishi MU-2B-20 · Picayune, MSThe pilot's excessive rate of descent during the landing flare/touchdown, which resulted in a hard landing.Dec 29, 2011 · N800BY · Substantial damage NTSB ERA11IA172Incident · No injuriesIncident investigationFinal reportMitsubishi MU-2B-20 · Walterboro, SCThe inadequate inspection and rigging of the nose landing gear downlock mechanism by maintenance personnel, which resulted in the failure of a bolt and the subsequent collapse of the nose gear during the landing roll.Jan 16, 2011 · N52CD · Minor damage NTSB CHI02LA144Accident · No injuriesLimited investigationFinal reportMitsubishi MU2B-20 · Belleville, MIThe pilot's failure to verify the extension of the landing gear prior to landing, and his failure to perform the emergency landing gear extension procedure. The popped circuit breaker was a factor.May 28, 2002 · N54CK · Substantial damage NTSB DEN01FA113Accident · 2 fatalField investigationFinal reportMitsubishi MU-2B-20 · Cerrillos, NMthe pilot's loss of aircraft control inflight for reasons undetermined. Contributing factors were the pilot's inadequate transition/upgrade training and his total lack of experience in aircraft make/model.Jun 10, 2001 · N187AF · Destroyed NTSB ATL99LA054Accident · No injuriesLimited investigationFinal reportMitsubishi MU-2B-20 · Knoxville, TNA loss of engine power for undetermined reasons. Contributing to the accident was the failure of the landing gear to extend for undetermined reasons.Mar 12, 1999 · N176BJ · Substantial damage NTSB ATL96LA078Accident · No injuriesLimited investigationFinal reportMitsubishi MU-2B · Batesville, MSan anomaly in the fuel system that allowed a pressure differential to occur between the center and outer portions of the main integral fuel tank, which in turn resulted in fuel starvation of both engines. A factor relating to the accident was: failure of…Apr 7, 1996 · N310MA · Substantial damage NTSB FTW91FA074Accident · 1 fatalField investigationFinal reportMitsubishi MU-2B-20 · Kenefic, OKImproper planning/decision by the pilots of both aircraft, and the Mitsubishi pilot's misjudgment of his position, while attempting to fly formation at night with an aircraft that did not have all navigation lights operative. Factors related to the accident…May 7, 1991 · N106MA · 2 aircraft · Destroyed NTSB BFO89LA023Accident · 1 fatalLimited investigationFinal reportMitsubishi MU-2B-20F · San Diego, CAPilot incapacitation for an unknown reason.Feb 28, 1989 · N701DM · Destroyed NTSB NYC88LA055Accident · No injuriesLimited investigationFinal reportMitsubishi MU-2B-20 · White Plains, NYThe cross country business flight was uneventful from concord, new hampshire to White Plains, new york under clear sky. During final approach, the pilot extended the gear but did not notice that the circuit breaker had opened and the gear was not lowered. The…Dec 7, 1987 · N866Q · Substantial damage NTSB ATL87FA173Accident · 1 fatalField investigationFinal reportMitsubishi MU-2B · Coral Springs, FLThe pilot reported to ground personnel at fort lauderdale that he was experiencing an avionics problem and the passengerentry door was sprung the day before when it was slammed; however, the pilot elected to depart. The aircraft wreckage was located on June…Jun 18, 1987 · N184MA · Destroyed NTSB DEN87FA003Accident · No injuriesField investigationFinal reportMitsubishi MU-2B-20 · Denver, COAcft had been repossessed and was being ferried from grand junction, CO, to chicago, IL, with en route stop at Denver, CO. After takeoff from Denver, landing gear would not retract. Plt made several attempts without success. He elected to return to Denver.…Oct 12, 1986 · N3MU · Substantial damage NTSB FTW86FA015Accident · 1 fatalField investigationFinal reportMitsubishi MU-2B-2D · El Paso, TXThe plt canceled his IFR flt plan and attempted to fly VFR at a relatively low alt over mountainous terrain with low scattered clouds on a dark night. He reported a large lighted area as being downtown El Paso when in reality it was most likely coronado…Oct 17, 1985 · N23CD · Destroyed NTSB FTW85LA229Accident · No injuriesLimited investigationFinal reportMitsubishi MU-2B-20 · San Angelo, TXA piece of unidentified equipment reportedly was not properly secured during previous maintenance. The equipment reportedly was mounted immediately above the nose wheel extension/retraction mechanism and moved due to acft vibration preventing the nose gear…May 21, 1985 · N711LL · Substantial damage NTSB CHI83LA051Accident · Minor injuriesLimited investigationFinal reportMitsubishi MU-2B-20 · Muskegon, MIThe pilot descended below his altitude and struck trees approximately 4.7 miles south of his destination. The aircraft continued to fly and the pilot elected to make an emergency landing. After touchdown the aircraft skidded down the runway for approximately…Dec 15, 1982 · N45EV · Substantial damage NTSB ATL83FA063Accident · Serious injuriesField investigationFinal reportMitsubishi MU-2B · Louisville, KYA takeoff was initiated from a 3539 ft wet/upsloping rwy. The gross wt of the acft was about 9300 lbs (300 lbs under themax gross wt). The plt stated the acft accelerated, but never reach '107.' After using about 2700 ft, the plt decided to abort the takeoff,…Dec 15, 1982 · N5589S · Substantial damage NTSB MKC82DA146Accident · No injuriesFinal reportMitsubishi MU-2B-20 · Camdenton, MOThe pilot landed hard damaging the landing gear on a paved area short of the displaced threshold. Flaps were set at 20 degrees instead of 40 degrees. After initial landing, the aircraft swerved right and went off the runway.Aug 18, 1982 · N550MA · Substantial damage NTSB ATL81IA033Incident · No injuriesClosedMitsubishi MU-2B · Norfolk, VAJan 6, 1981 · N755Q · Minor damage NTSB DEN80FA012Accident · 2 fatalClosedMitsubishi MU-2B · Provo, UTDec 21, 1979 · N200BR · Destroyed NTSB IAD80FA007Accident · 5 fatalClosedMitsubishi MU-2F · Nashville, TNNov 1, 1979 · N873Q · Destroyed NTSB MIA77FKJ08Accident · No injuriesClosedMitsubishi MU-2B · Gadsden, ALDec 3, 1976 · N304L · Substantial damage NTSB CHI74AC059Accident · No injuriesClosedMitsubishi MU-2B · Elyria, OHJan 11, 1974 · N106MA · Substantial damage NTSB FTW73DQG43Accident · 2 fatalClosedMitsubishi MU-2B · Cedillos C, MexicoJun 13, 1973 · N882Q · Destroyed NTSB CHI73AC067Accident · No injuriesClosedMitsubishi MU-2 · Detroit, MIJan 31, 1973 · N866Q · Substantial damage NTSB CHI73FEA25Accident · No injuriesClosedMitsubishi MU-2B · Noblesville, INJan 12, 1973 · N555C · Substantial damage NTSB MIA73AM054Accident · 1 fatalClosedMitsubishi MU-2B · Alcolu, SCNov 20, 1972 · N757Q · Destroyed NTSB CHI72FEP24Accident · No injuriesClosedMitsubishi MU2B20 · East Troy, WIDec 11, 1971 · N304L · Substantial damage NTSB IAD70AI039Accident · Serious injuriesClosedMitsubishi MU-2B · Salisbury, MDJan 16, 1970 · N764Q · Destroyed