NTSB investigations: Beech F33A, 1989
5 cases on aircraft the registry lists as Beech F33A. 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
| 1971 | 1 |
|---|---|
| 1972 | 1 |
| 1973 | 2 |
| 1974 | 1 |
| 1975 | 2 |
| 1977 | 1 |
| 1978 | 4 |
| 1979 | 3 |
| 1980 | 3 |
| 1981 | 7 |
| 1982 | 3 |
| 1983 | 2 |
| 1984 | 3 |
| 1985 | 3 |
| 1987 | 3 |
| 1988 | 1 |
| 1989 | 5 |
| 1990 | 6 |
| 1991 | 9 |
| 1992 | 5 |
| 1993 | 4 |
| 1994 | 1 |
| 1995 | 6 |
| 1996 | 4 |
| 1997 | 4 |
| 1998 | 5 |
| 1999 | 4 |
| 2000 | 4 |
| 2001 | 2 |
| 2002 | 5 |
| 2003 | 1 |
| 2004 | 4 |
| 2005 | 5 |
| 2006 | 5 |
| 2007 | 2 |
| 2008 | 2 |
| 2009 | 2 |
| 2010 | 4 |
| 2011 | 5 |
| 2012 | 1 |
| 2013 | 1 |
| 2014 | 2 |
| 2015 | 2 |
| 2016 | 4 |
| 2017 | 1 |
| 2018 | 4 |
| 2019 | 3 |
| 2020 | 4 |
| 2021 | 3 |
| 2022 | 4 |
| 2023 | 2 |
| 2024 | 2 |
| 2025 | 1 |
| 2026 | 3 |
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 ('1151425'))
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 ('1151425'))
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 LAX90FA008Accident · 3 fatalField investigationFinal reportBeech F33A · Goodyear, AZThe inflight separation of one propeller blade due to a fatigue fracture of undetermined origin, and failure of the pilot to maintain control of the aircraft during an attempt to return to the runway. A factor in the accident was the oil covered windsheild,…NTSB NYC89LA162Accident · No injuriesLimited investigationFinal reportBeech F33A · Waterville, METhe pilot's disregard of NOTAMS and the excessive landing speed which resulted in a long landing roll.NTSB MIA89LA126Accident · No injuriesLimited investigationFinal reportBeech F-33A · Reddington Bch., FLLoss of engine power for undetermined reasons.NTSB DEN89LA095Accident · No injuriesLimited investigationFinal reportBeech F33A · Lamar, COFailure of an alternator bearing which resulted in total loss of electrical power after the battery became discharged, and failure of the pilot to insure the gear was fully extended during a precautionary landing. The pilot's lack of familiarity with the gear…NTSB ATL89FA113Accident · 1 fatalField investigationFinal reportBeech F33A · Ashland, ALThe pilot continued VFR flight into instrument meteorological conditions (IMC). Factors related to the accident were: high terrain, the adverse weather conditions, and trees.