NTSB investigations: Beech F33A
13 cases on aircraft the registry lists as Beech F33A, where the first occurrence was “Loss of control - in flight”. 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
| 1987 | 1 |
|---|---|
| 1991 | 1 |
| 1993 | 1 |
| 1995 | 4 |
| 1996 | 2 |
| 1997 | 1 |
| 2000 | 1 |
| 2001 | 1 |
| 2004 | 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.\"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\" = 250))
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" = 250))
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 LAX04CA104Accident · Serious injuriesData collectionFinal reportBeech F33A · Shoshone, CAthe CFI's failure to verify the wind direction prior to takeoff, which resulted in his failure to attain an adequate airspeed and led to an inadvertent stall-mush. The short runway and variable winds were factors.NTSB LAX01LA139Accident · Minor injuriesLimited investigationFinal reportBeech F-33A · Mobile, AZThe certified flight instructor's inadequate supervision of the dual student who failed to recognize the extent of the crosswind and lost directional control. A factor in the accident was the variable wind condition.NTSB NYC00LA258Accident · Serious injuriesLimited investigationFinal reportBeech 33-F33A · Warwick, NYThe pilot's improper decision to fully retract flaps during a go-around.NTSB NYC98LA052Accident · Minor injuriesLimited investigationFinal reportBeech BE-33A · Lancaster, PAPassenger control interference which resulted in pilot's failure to maintain control of the airplane during landing.NTSB CHI96FA169Accident · 1 fatalField investigationFinal reportBeech F33A · Saint Clair, MOfailure of the pilot to maintain adequate airspeed, while maneuvering at low altitude, which resulted in a stall and collision with the terrain.NTSB CHI96FA133Accident · 1 fatalField investigationFinal reportBeech F-33A · Prairie City, SDthe pilot's failure to maintain control of the airplane. A factor was pilot fatigue.NTSB BFO95FA097Accident · 1 fatalField investigationFinal reportBeech F33A · Farmingdale, NYfailure of the pilot to maintain pitch control of the airplane during the initial climb after lift-off, which resulted in a steep climb, loss of airspeed, and a resultant stall/spin and subsequent crash. A factor relating to the accident was: failure of the…NTSB SEA95FA175Accident · 2 fatalField investigationFinal reportBeech F33A · Swan Lake, MTthe pilot's incapacitation due to a heart attack.NTSB FTW95LA193Accident · No injuriesLimited investigationFinal reportBeech F33A · Houston, TXThe pilot's inadequate compensation for the wind conditions. A factor was the crosswind.NTSB LAX95LA090Accident · No injuriesLimited investigationFinal reportBeech F33A · Tucson, AZthe student pilot's poor short field takeoff procedure and excessive nose rotation resulted in an inadvertent stall. A factor is the student pilot's lack of total experience.NTSB LAX93FA377Accident · 3 fatalField investigationFinal reportBeech F33A · Baker, CAA loss of control for undetermined reason(s).NTSB LAX91FA329Accident · 4 fatalField investigationFinal reportBeech F33A · Earp, CAThe pilot's failure to maintain adequate airspeed, while maneuvering during a low pass, which resulted in a stall. A factor related to the accident was: lack of altitude to recover from the stall.NTSB NYC88LA008Accident · 1 fatalLimited investigationFinal reportBeech F-33A · Concord, NHThe plt obtained a telephone wx briefing then filed an IFR flt plan for a 1030 EDT departure fm Concord municipal airport. The plt rptd off Concord at 800 ft and climbing at 1047. Manchester departure control acknowledged, assigned a transponder code, and…