NTSB investigations: Beech F33A, 1990
6 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
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 year(c.\"eventDate\") = 1990
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") = 1990
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 LAX91LA017Accident · Minor injuriesLimited investigationFinal reportBeech F33A · Mobile, AZA fuel flow interruption due to a fuel system seal fragment becoming lodged in the fuel control unit and the manufacturer's inadequate quality control procedures.NTSB CHI90LA270Accident · Serious injuriesLimited investigationFinal reportBeech F-33A · Osage Beach, MOThe pilot's failure to establish a proper glide path, resulting in contact with trees short of the intended runway.NTSB CHI90LA115Accident · Minor injuriesLimited investigationFinal reportBeech F33A · Milwaukee, WIThe utilization of improper procedures on the part of the pilot in command by attempting to execute a coupled approach outside the parameters of the autopilot.NTSB LAX90LA147Accident · No injuriesLimited investigationFinal reportBeech F-33A · Goodyear, AZThe pilot's failure to follow directives and his misjudgement of distance. Contributing to the accident was the airport management's failure to ensure that the building did not pose a hazard.NTSB LAX90LA146Accident · No injuriesLimited investigationFinal reportBeech F33A · Yuba City, CAA dog suddenly running onto the active runway in front of the aircraft resulted in a collision and substantial airframe damage.NTSB LAX90FA088Accident · 1 fatalField investigationFinal reportBeech F-33A · Oro Valley, AZThe pilot's poor judgement in performing low level aerobatic maneuvers.