NTSB investigations: Beech F33A
7 cases on aircraft the registry lists as Beech F33A, where the first occurrence was “Loss of engine power”. 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
| 1992 | 1 |
|---|---|
| 1993 | 2 |
| 1999 | 1 |
| 2005 | 1 |
| 2006 | 1 |
| 2007 | 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\" = 350))
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" = 350))
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 NYC07LA244Accident · Minor injuriesLimited investigationFinal reportBeech F33A · Franklin, VAA loss of engine power during approach for undetermined reasons. Contributing to the accident was the unsuitable terrain.NTSB DFW07LA016Accident · No injuriesLimited investigationFinal reportBeech F33 · Houston, TXThe loss of engine power due to fuel starvation as a result of the pilot's improper fuel management.NTSB ATL06CA004Accident · No injuriesData collectionFinal reportBeech F33A · Millington, TNThe pilot's improper fuel management resulting in a total loss of engine power due to fuel starvation. A factor in the accident was the pilot's failure to maintain airspeed and misjudged distance to the forced landing area resulting in a stall and collision…NTSB LAX99LA094Accident · No injuriesLimited investigationFinal reportBeech F33 · Prescott, AZA total loss of engine power for undetermined reasons.NTSB CHI94LA026Accident · Minor injuriesLimited investigationFinal reportBeech F33A · Saint Paul, MNother maintenance personnel's improper maintenance installation and fuel system line fitting undertorqued. Factors related to the accident were the dark night, along with the fence and posts which were contacted.NTSB MIA93FA129Accident · Serious injuriesField investigationFinal reportBeech F33A · Oxford, MSLoss of engine power for undetermined reasons. The lack of suitable terrain for a forced landing was a factor.NTSB DEN93LA001Accident · Minor injuriesLimited investigationFinal reportBeech F33A · Steamboat Sprgs, COThe pilot's selection of an unsuitable landing area when a suitable forced landing area was available. A factor was: fuel starvation for unknown reasons.