NTSB investigations: Beech F33A
10 cases on aircraft the registry lists as Beech F33A, where the first occurrence was “In flight encounter with weather”. 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 |
|---|---|
| 1989 | 1 |
| 1991 | 2 |
| 1996 | 1 |
| 1997 | 1 |
| 1998 | 1 |
| 2002 | 1 |
| 2004 | 1 |
| 2006 | 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\" = 240))
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" = 240))
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 LAX06FA130Accident · 2 fatalField investigationFinal reportBeech F33A · Kingman, AZThe noninstrument rated pilot's cruise flight into instrument meteorological conditions, and his failure to maintain control of the airplane, which resulted in an uncontrolled descent, and an in-flight collision with terrain. Factors associated with the…NTSB ATL05FA008Accident · 1 fatalField investigationFinal reportBeech F33A · Flat Rock, NCThe pilot experienced spatial disorientation, which resulted in a loss of control and the subsequent collision with the ground. Factors were low ceilings and fog.NTSB MIA02FA102Accident · 1 fatalField investigationFinal reportBeech F33A · Conway, SCThe failure of the pilot to request in-flight weather avoidance assistance and his poor in-flight planning/decision for flying into a Level 5 thunderstorm resulting in an in-flight loss of control, uncontrolled descent, and subsequent in-flight collision with…NTSB IAD98FA068Accident · 2 fatalField investigationFinal reportBeech F33A · Delaplane, VAThe pilot's inadequate in-flight decision which led to VFR flight into instrument meteorological conditions. Also causal was the pilot's failure to maintain adequate terrain clearance resulting in collision with mountainous terrain. Contributing factors were…NTSB LAX97FA089Accident · 2 fatalField investigationFinal reportBeech F33A · Mt San Jacinto, CAcontinued VFR flight by the pilot into instrument meteorological conditions (IMC), and his failure to maintain proper altitude or clearance from mountainous terrain. Factors relating to the accident were: the high/mountainous terrain, and the adverse weather…NTSB NYC97FA004Accident · 2 fatalField investigationFinal reportBeech F33A · Doylesburg, PAcontinued VFR flight by the pilot into instrument meteorological conditions, and his failure to maintain altitude and/or clearance from high terrain. Factors relating to the accident were: darkness, low ceiling, fog, and high (mountainous) terrain along the…NTSB CHI91FA126Accident · 2 fatalField investigationFinal reportBeech F.33A · Chippewa Falls, WIThe first pilot's continued flight in known adverse weather. Factors in the accident were the first pilot's poor weather evaluation, the second pilot's complacency and the first pilot's self induced pressure to complete a checkout in model.NTSB SEA91LA050Accident · 4 fatalLimited investigationFinal reportBeech F33A · Ogden, UTThe pilot elected to fly into known adverse weather and encountered icing conditions. Contributing to the accident was the pilot's inadequate evaluation of the weather and a loss of engine power for undetermined reasons.NTSB ATL89FA113Accident · 1 fatalField investigationFinal reportBeech F33A · Ashland, ALThe pilot continued VFR flight into instrument meteorological conditions (IMC). Factors related to the accident were: high terrain, the adverse weather conditions, and trees.NTSB LAX87FA121Accident · 4 fatalField investigationFinal reportBeech F33A · Anza, CAThe non-instrument rated plt & 3 pax planned a pleasure flt to mx. The weather was below VFR minimums however the plt elected to attempt the flt. Several minutes after departure the acft was observed to enter an area where it was snowing, the cloud base was…