NTSB investigations: Beech F33A

7 cases on aircraft the registry lists as Beech F33A, where the probable cause includes Not determined, general. 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

20102026
NTSB investigations: Beech F33A per year, 2010–2026: 7 cases
20103
20121
20131
20151
20191

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 c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1151425')
      AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_findings.parquet' f WHERE f.case_mkey = x.case_mkey AND f.aircrafts_position = x.position AND f.\"inProbableCause\" AND starts_with(f.\"findingCode\", '05000000')))
  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.

NTSB WPR19LA200Accident · No injuriesClass 3 · LimitedFinal reportBeech 33 · Battleground, WAA failure of the throttle control assembly for reasons that could not be determined based on available evidence, which resulted in a runway overrun and impact with an obstacle.Jul 20, 2019 · N873BC · Substantial damageNTSB ERA16FA044Accident · 2 fatalField investigationFinal reportBeech F33A · North Salem, NYA loss of airplane control for reasons that could not be determined because examination of the wreckage revealed no mechanical deficiencies.Nov 19, 2015 · N9318Q · DestroyedNTSB CEN13FA476Accident · 2 fatalField investigationFinal reportBeechcraft F33A · Ennis, TXThe loss of engine power for reasons that could not be determined during postaccident examinations due to postcrash fire damage.Aug 11, 2013 · N4514S · Substantial damageNTSB ANC12FA079Accident · Minor injuriesField investigationFinal reportBeechcraft F33A · Fairbanks, AKThe total loss of engine power reason that could not be determined because postaccident examination and test run did not reveal any anomalies that would have precluded normal operation.Jul 26, 2012 · N334DH · Substantial damageNTSB WPR10FA473Accident · 1 fatalField investigationFinal reportHawker Beechcraft F33 · Phoenix, AZA partial loss of engine power during approach for reasons that could not be determined because postaccident examination did not reveal any anomalies that would have precluded normal operation.Sep 27, 2010 · N1600W · Substantial damageNTSB ERA10LA349Accident · No injuriesLimited investigationFinal reportBeech F33A · Mooresville, NCA loss of engine power for undetermined reasons.Jul 6, 2010 · N350NW · Substantial damageNTSB WPR10LA280Accident · No injuriesLimited investigationFinal reportBeech F33 · Marana, AZThe loss of engine power while maneuvering to land for undetermined reasons.Jun 5, 2010 · N1565A · Substantial damage