NTSB investigations: Beech C23, 1991
12 cases on aircraft the registry lists as Beech C23. 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
| 1970 | 1 |
|---|---|
| 1971 | 1 |
| 1972 | 6 |
| 1973 | 3 |
| 1974 | 4 |
| 1975 | 10 |
| 1976 | 15 |
| 1977 | 17 |
| 1978 | 19 |
| 1979 | 21 |
| 1980 | 24 |
| 1981 | 9 |
| 1982 | 24 |
| 1983 | 13 |
| 1984 | 8 |
| 1985 | 5 |
| 1986 | 8 |
| 1987 | 10 |
| 1988 | 11 |
| 1989 | 6 |
| 1990 | 4 |
| 1991 | 12 |
| 1992 | 7 |
| 1993 | 8 |
| 1994 | 9 |
| 1995 | 8 |
| 1996 | 6 |
| 1997 | 9 |
| 1998 | 4 |
| 1999 | 11 |
| 2000 | 2 |
| 2001 | 2 |
| 2002 | 8 |
| 2003 | 4 |
| 2004 | 3 |
| 2005 | 6 |
| 2006 | 3 |
| 2007 | 4 |
| 2008 | 10 |
| 2009 | 1 |
| 2010 | 3 |
| 2011 | 3 |
| 2012 | 1 |
| 2013 | 3 |
| 2015 | 1 |
| 2016 | 8 |
| 2017 | 5 |
| 2018 | 1 |
| 2019 | 2 |
| 2020 | 2 |
| 2021 | 4 |
| 2022 | 3 |
| 2023 | 4 |
| 2024 | 3 |
| 2025 | 2 |
| 2026 | 2 |
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\") = 1991
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1151242'))
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") = 1991
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1151242'))
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 ATL92FA033Accident · 2 fatalField investigationFinal reportBeech C23 · Lineville, ALThe pilot continued VFR into IMC conditions where he collided with trees and terrain. Factors in this accident were: low clouds, obscured terrain, and the pilot's inadequate prelflight planning.NTSB FTW92FA045Accident · 4 fatalField investigationFinal reportBeech C23 · Dewitt, ARThe pilot's attempt to land in IMC conditions and her subsequent loss of control during climb out due to spatial disorientation. A factor was the pilot's disregard of the pre-flight weather briefing.NTSB FTW92FA023Accident · 1 fatalField investigationFinal reportBeech C23 · Angleton, TXThe pilot's failure to maintain aircraft control. Factors were his lack of total instrument time, his VFR flight into instrument conditions and spatial disorientation.NTSB CHI92LA024Accident · Minor injuriesLimited investigationFinal reportBeech C-23 · Burlington, IAThe pilot having an improper fuel tank selector position.NTSB NYC91FA199Accident · 3 fatalField investigationFinal reportBeech C23 · Pleasantville, NJA power loss due to a failed crankshaft, while operating over unsuitable terrain. Factors related to the accident were, the night conditions, the failure of maintenance personnel to detect the cracks using magnaflux inspections, the lack of adequate…NTSB NYC91LA191Accident · No injuriesLimited investigationFinal reportBeech C-23 · Williamstown, MAEngine failure as a result of improper engine overhaul performed by other maintenance personnel. A factor was the lack of suitable terrain.NTSB NYC91LA137Accident · No injuriesLimited investigationFinal reportBeech C-23 · Chesapeake, OHThe pilot's failure to maintain an adequate airspeed that would preclude a stall. Contributing to the accident was the opened door.NTSB CHI91LA167Accident · Minor injuriesLimited investigationFinal reportBeech C-23 · Cottage Grove, MNThe pilot in command's improper pre flight planning and preparation. Factors contributing to this accident were the pilot in command's lack of familiarity with the airplane and improper fuel consumption calculations.NTSB LAX91FA219Accident · Serious injuriesField investigationFinal reportBeech C23 · Cibola, AZThe pilot's failure to maintain adequate clearance between the aircraft and ground vehicle during a low pass resulting in an in flight collision with the vehicle, loss of control, and in flight collision with terrain. Factors related to the accident was the…NTSB DEN91FA072Accident · Serious injuriesField investigationFinal reportBeech C23 · Boulder, COInadvertent stall/mush due to the passengers's delay in relinquishing aircraft control, and inadequate supervision of the flight by the pilot in command. Factors were: mixture not leaned, and a high density altitude takeoff with a slight quartering tailwind.NTSB MIA91WA088Accident · No injuriesForeign investigationBeech C23 · Alice Town, BahamasNTSB ATL91LA055Accident · No injuriesLimited investigationFinal reportBeech C23 · Concord, NCThe pilot's inadequate preflight planning in that he disregarded the crosswind limit in the pilot's operating handbook. Factors were the wet runway and the ravine at the end of the runway.