Fatal NTSB investigations: Beech A23-24
22 cases on aircraft the registry lists as Beech A23-24. 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
| 1966 | 1 |
|---|---|
| 1967 | 1 |
| 1968 | 2 |
| 1970 | 1 |
| 1972 | 1 |
| 1974 | 1 |
| 1975 | 2 |
| 1977 | 2 |
| 1978 | 2 |
| 1983 | 1 |
| 1984 | 1 |
| 1992 | 1 |
| 1993 | 1 |
| 1995 | 1 |
| 1998 | 1 |
| 2000 | 1 |
| 2001 | 1 |
| 2023 | 1 |
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 c.\"highestInjuryLevel\" = 'Fatal'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1151226'))
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 c."highestInjuryLevel" = 'Fatal'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1151226'))
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 CEN24FA057Accident · 2 fatalClass 3 · FieldFinal reportBeech A23-24 · Oklahoma City, OKA total loss of engine power due to multiple connecting rod failures from oil starvation associated with an extensive before takeoff oil system leak, the source of which could not be identified due to postaccident fire damage.NTSB NYC01FA172Accident · 1 fatalField investigationFinal reportBeech A23-24 · Bridgeville, DEThe pilot's incapacitation, which resulted in a loss of aircraft control while maneuvering. A factor was the FAA Aeromedical Certification Division's inadequate certification/approval of the pilot's medical certificate. Findings were the pilot's inappropriate…NTSB NYC01FA021Accident · 3 fatalField investigationFinal reportBeech BE-23-24 · Kingston, OHThe pilot's failure to check both fuel tanks visually during the preflight inspection. A factor in the accident was the dark night.NTSB NYC98FA180Accident · 5 fatalField investigationFinal reportBeech A23-24 · Shunk, PAThe pilot-in-command's attempted flight into known adverse weather conditions, his failure to maintain control of the aircraft, and his exceeding the airframe design limits resulting in separation of the outboard left wing. Contributing factors were clouds,…NTSB NYC95LA113Accident · 1 fatalLimited investigationFinal reportBeech A23-24 · Atlantic City, NJThe pilot's delayed decision to abort the landing. Factors in the accident were: the downwind landing and the pilot's misjudgment of distance and speed.NTSB ATL93FA046Accident · 2 fatalField investigationFinal reportBeech A23 · Ft. Bragg, NCThe loss of engine power for undetermined reasons and the loss of control during the forced landing.NTSB LAX92FA196Accident · 2 fatalField investigationFinal reportBeech A23-24 · Corona, CA1) The flying pilot's improper landing flare which resulted in a hard landing and significant damage to the aircraft empennage flight controls, 2) the flying pilot's decision to initiate a go around with the obvious serious damage to the aircraft, and 3) the…NTSB LAX84FA259Accident · 1 fatalField investigationFinal reportBeech A23-24 · Bowman, CAOn a flt from fair oaks, CA, to reno, NV, a flt of about 1 hr 15 mins, the acft experienced a total power loss. The plt asked the pax to select the other fuel tank. The selctor handle was not attached to the valve. But the pax located the handle and turned…NTSB FTW83FA150Accident · 2 fatalField investigationFinal reportBeech A23-24 · Shawnee, OKThe plt departed his private, 1200 ft airstrip & flew to the Shawnee muni arpt with 1 passenger. During arrival on the return flt, he elected to land toward the south. According to a witness, there was a thunderstorm at that time aprx 1/2 to 1 mi…NTSB MKC79FA001Accident · 4 fatalClosedBeech A23-24 · Lyndon, KSNTSB MKC78FA031Accident · 1 fatalClosedBeech A23-24 · Wichita, KSNTSB MIA78FA024Accident · 4 fatalClosedBeech A24 · Alachua, FLNTSB LAX78FA002Accident · 2 fatalClosedBeech A23-24 · El Cajon, CANTSB MIA75AM075Accident · 2 fatalClosedBeech A23-24 · Sarasota, FLNTSB CHI75AC071Accident · 1 fatalClosedBeech A23 · Troy, OHNTSB MKC74AK043Accident · 3 fatalClosedBeech A23-24 · Montevideo, MNNTSB NYC72AN160Accident · 4 fatalClosedBeech A23-24 · Sapphire, NCNTSB IAD71AI017Accident · 4 fatalClosedBeech A23-24 · Ocean City, MDNTSB DIA69A0007Accident · 5 fatalClosedBeech A23-24 · Cana, VANTSB NYC69A0005Accident · 4 fatalClosedBeech A23 · Bristol, NYNTSB MKC68A0030Accident · 3 fatalClosedBeech A23 · Stoutland, MONTSB MKC67A0029Accident · 1 fatalClosedBeech A23 · Fergus Falls, MN