NTSB investigations: Beech F33A
6 cases on aircraft the registry lists as Beech F33A, where the first occurrence was “Loss of control - on ground/water”. 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
| 1984 | 1 |
|---|---|
| 1998 | 1 |
| 1999 | 2 |
| 2000 | 1 |
| 2002 | 1 |
Where
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_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 260))
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" = 260))
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 NYC02LA054Accident · No injuriesLimited investigationFinal reportBeech F33A · Lynchburg, VAThe pilot's failure to maintain directional control and delay in aborting the takeoff.NTSB CHI01LA059Accident · No injuriesLimited investigationFinal reportBeech F33A · Winona, MNThe pilot not maintaining directional control during the landing roll. A factor was the snowbank.NTSB SEA00LA002Accident · No injuriesLimited investigationFinal reportBeech F33A · Idaho Falls, IDThe pilot's failure to adequately compensate for wind conditions. Factors include gusty, turbulent, variable crosswinds, and a fence in the vicinity of the runway.NTSB NYC99LA238Accident · No injuriesLimited investigationFinal reportBeech F33A · Wildwood, NJThe pilot's improper recover from a bounced landing. A factor related to the accident was the pilot's diverted attention due to the loss of a spouse.NTSB CHI98LA276Accident · Minor injuriesLimited investigationFinal reportBeech F33A · Delavan, WIthe pilot's failure to maintain aircraft control during the takeoff roll. Factors contributing to this accident were the pilot's inadequate preflight, his operation of an airplane with a known deficiency, low air pressure on both main tires, the snow fence,…NTSB DEN84LA220Accident · No injuriesLimited investigationFinal reportBeech F33A · Glen Canyon, UTAccording to the plt, a slightly higher than normal apch speed with partial flap extension was used for the apch due to the turbulance and wind gusts to 25 KTS. After crossing the threshold at 20 to 30 ft AGL the flare resulted in what the pilot described as…