NTSB investigations: Beech F33A, 2005
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
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\") = 2005
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") = 2005
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 LAX06LA065Accident · No injuriesLimited investigationFinal reportBeech F33A · La Verne, CAthe failure of the pilot of the other aircraft to comply with his air traffic control clearance and line up for the proper runway, and his failure to maintain an adequate visual lookout, which resulted in his in-flight collision with the Cessna airplane.NTSB NYC06CA031Accident · No injuriesData collectionFinal reportBeech F33A · Montgomery, NYThe pilot's misjudgment of the landing flare, which resulted in a hard landing short of the runway. Factors included the night lighting conditions, the time-out and reestablishment of the high intensity runway lighting, and the pilot's failure to go around.NTSB LAX06FA031Accident · 1 fatalField investigationFinal reportBeech F33A · Geyserville, CAthe pilot's failure to maintain an adequate terrain clearance altitude profile during the descent that resulted in controlled flight into terrain.NTSB ATL06CA004Accident · No injuriesData collectionFinal reportBeech F33A · Millington, TNThe pilot's improper fuel management resulting in a total loss of engine power due to fuel starvation. A factor in the accident was the pilot's failure to maintain airspeed and misjudged distance to the forced landing area resulting in a stall and collision…NTSB MIA05CA114Accident · No injuriesData collectionFinal reportBeech F33A · Cedar key, FLThe pilots improper landing flare/touchdown, which resulted in a hard landing, and damage to the airplane.