NTSB investigations: Mitsubishi MU-300

7 cases on aircraft the registry lists as Mitsubishi MU-300. 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

19862026
NTSB investigations: Mitsubishi MU-300 per year, 1986–2026: 7 cases
19861
19931
19991
20001
20022
20161

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 ('5780602'))
  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.

NTSB CEN16IA091Incident · No injuriesIncident investigationFinal reportMitsubishi MU 300 · Little Rock, ARThe flight crew's inadequate preflight inspection of the airplane, during which they failed to see a fueling mat that had been placed on the inboard trailing edge of the right wing, which the right engine subsequently ingested during the takeoff roll.…Jan 12, 2016 · N200LP · Minor damageNTSB CHI02FA097Accident · No injuriesField investigationFinal reportMitsubishi MU-300 · Anderson, INMissed approach not executed and flight to a destination alternate not performed by the flight crew. The tail wind and snow/ice covered runway were contributing factors.Mar 25, 2002 · N617BG · Substantial damageNTSB NYC02FA059Accident · No injuriesField investigationFinal reportMitsubishi MU-300 · Cleveland, OHThe pilot's failure to obtain the proper touch down point on the runway, and the pilot-in-commands failure to initiate a go-round. Factors in the accident were the tailwind condition, the snow-covered runway.Feb 11, 2002 · N541CW · Substantial damageNTSB FTW00LA084Accident · No injuriesLimited investigationFinal reportMitsubishi MU-300 · Dallas, TXThe diminished effectiveness of the anti-skid brake system due to the slush contaminated runway. Factors were the freezing rain encountered during the approach, coupled with a failure of the horizontal stabilizer heat.Jan 27, 2000 · N900WJ · Substantial damageNTSB CHI99LA093Accident · No injuriesLimited investigationFinal reportMitsubishi 300 · Columbus, NEthe pilot-in-command failed to attain the proper touchdown point during the landing. Factors associated with the accident were the rough, snow covered terrain encountered off the end of the runway, and the low ceiling at the time of the landing.Feb 18, 1999 · N110DS · Substantial damageNTSB CHI94FA050Accident · 3 fatalField investigationFinal reportMitsubishi MU-300 · Goodland, KSThe pilot-in-command's inadvertent stall of the airplane. A factor associated with the accident is the pilot-in-command's poor IFR procedures.Dec 15, 1993 · N710MB · DestroyedNTSB CHI86IA231Incident · No injuriesIncident investigationFinal reportMitsubishi MU-300IA · Chicago, ILAfter landing the corporate jet was cleared to taxi to the general aviation ops to deplane pax. A food service truck crossing the taxiway failed to yield the right of way. The acft was unable to stop before the left wing struck the rear of the vehicle.Sep 25, 1986 · N19R · Minor damage