NTSB investigations: Beech F33A

7 cases on aircraft the registry lists as Beech F33A, where the first occurrence was “Airframe/component/system failure/malfunction”. 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.

Defining event

Finding

Phase of flight

Aircraft model

Cases per year

19882026

NTSB investigations: Beech F33A per year, 1988–2026: 7 cases
1988	1
1989	2
1992	1
1995	1
1998	1
2004	1

Where

Open the map

Latest cases

Query with SQL

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_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 130)) ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC

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_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 130))
  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."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_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 130))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC

Run 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 LAX04LA312Accident · No injuriesLimited investigationFinal reportBeech F33A · Fresno, CAthe pilot's loss of pitch control authority during landing flare due to an autopilot system failure that inhibited control yoke movement. A factor was inadequate autopilot system maintenance.Sep 3, 2004 · N1854N · Substantial damage NTSB ATL99LA024Accident · Serious injuriesLimited investigationFinal reportBeech 33-F33A · Fernandina Bch, FLThe Pilot's failure to maintain flying airspeed that resulted in a loss of control and an inadvertent stall. Factors were several electrical system component malfunction.Nov 28, 1998 · N69FL · Substantial damage NTSB BFO95LA063Accident · Minor injuriesLimited investigationFinal reportBeech F33A · Ft Washington, MDA loss of engine power for an undetermined reason(s).Jun 11, 1995 · N1775B · Destroyed NTSB CHI92LA117Accident · No injuriesLimited investigationFinal reportBeech F33A · Langdon, NDFailure of the pilot to fully extend the landing gear using manual procedures after an electrical system failure. A factor associated with the accident is the pilot misreading a published emergency procedure.Mar 21, 1992 · N2046W · Substantial damage NTSB LAX90FA008Accident · 3 fatalField investigationFinal reportBeech F33A · Goodyear, AZThe inflight separation of one propeller blade due to a fatigue fracture of undetermined origin, and failure of the pilot to maintain control of the aircraft during an attempt to return to the runway. A factor in the accident was the oil covered windsheild,…Oct 11, 1989 · N67536 · Destroyed NTSB DEN89LA095Accident · No injuriesLimited investigationFinal reportBeech F33A · Lamar, COFailure of an alternator bearing which resulted in total loss of electrical power after the battery became discharged, and failure of the pilot to insure the gear was fully extended during a precautionary landing. The pilot's lack of familiarity with the gear…Mar 27, 1989 · N3042Z · Substantial damage NTSB LAX88DUJ03Accident · No injuriesFinal reportBeech F33A · Goodyear, AZDuring an instructional flight, after takeoff, at 300 feet, the pilot and student said they heard a loud bang. The engine experienced a loss of power and the pilot noted that the top of the engine cowling was gone. A forced landing was made off the runway.…Feb 18, 1988 · N6785Y · Substantial damage