NTSB investigations: Beech E33, 1989
3 cases on aircraft the registry lists as Beech E33. 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
| 1968 | 2 |
|---|---|
| 1969 | 4 |
| 1970 | 3 |
| 1975 | 1 |
| 1977 | 1 |
| 1978 | 1 |
| 1982 | 1 |
| 1983 | 1 |
| 1985 | 1 |
| 1989 | 3 |
| 1990 | 1 |
| 1993 | 1 |
| 1999 | 1 |
| 2011 | 1 |
| 2012 | 1 |
| 2025 | 1 |
| 2026 | 1 |
Where
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 year(c.\"eventDate\") = 1989
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1151422'))
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 year(c."eventDate") = 1989
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1151422'))
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 CHI89IA180Incident · No injuriesIncident investigationFinal reportMcdonnell Douglas MD-80 · Chicago, ILThe failure of the controller to clarify the confusing communications, to correct the pilot's misinterpretation of the instructions being given, and the failure of the supervisor to properly monitor the situation. Factors related to the incident were the…NTSB DEN89FA152Accident · 1 fatalField investigationFinal reportBeech E33 · Angel Fire, NMImproper planning/decision by the pilot, his premature rotation for takeoff and subsequent failure to obtain or maintain sufficient speed to climb, and his failure to abort the takeoff (while there was sufficient rwy remaining). Contributing factors were: the…NTSB LAX89LA097Accident · No injuriesLimited investigationFinal reportBeech E33 · Parlier, CAThe pilot's improper in-flight planning/decision to continue to the destination airport after encountering a restrictionof fuel flow from the right tank and subsequent fuel starvation when the left tank emptied. Contributing factors were the blocked fuel vent…