Fatal NTSB investigations: Mitsubishi MU-2B-30
7 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.
Cases per year
| 1972 | 1 |
|---|---|
| 1974 | 1 |
| 1975 | 1 |
| 1977 | 1 |
| 1982 | 1 |
| 1992 | 1 |
| 1997 | 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 ('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."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 ('5780410'))
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 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…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…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…NTSB NYC77FA046Accident · 7 fatalClosedMitsubishi MU-2 · Bronx, NYNTSB HAY76AL042Accident · 9 fatalClosedMitsubishi MU-2B · Rollinsville, CONTSB DEN74AD041Accident · 5 fatalClosedMitsubishi MU-2B · Glenwood Spg, CONTSB NYC72AN129Accident · 3 fatalClosedMitsubishi MU-2G · Atlantic City, NJ