Fatal NTSB investigations: Beech F33A
55 cases on aircraft the registry lists as Beech F33A. 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
| 1971 | 1 |
|---|---|
| 1973 | 1 |
| 1977 | 1 |
| 1979 | 1 |
| 1981 | 2 |
| 1985 | 2 |
| 1987 | 3 |
| 1989 | 2 |
| 1990 | 1 |
| 1991 | 4 |
| 1992 | 1 |
| 1993 | 1 |
| 1995 | 2 |
| 1996 | 3 |
| 1997 | 1 |
| 1998 | 2 |
| 1999 | 1 |
| 2000 | 1 |
| 2001 | 1 |
| 2002 | 2 |
| 2003 | 1 |
| 2004 | 1 |
| 2005 | 1 |
| 2006 | 3 |
| 2010 | 2 |
| 2011 | 1 |
| 2013 | 1 |
| 2014 | 1 |
| 2015 | 1 |
| 2016 | 1 |
| 2018 | 1 |
| 2019 | 1 |
| 2020 | 3 |
| 2021 | 1 |
| 2022 | 1 |
| 2024 | 1 |
| 2026 | 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.\"highestInjuryLevel\" = 'Fatal'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1151425'))
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."highestInjuryLevel" = 'Fatal'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1151425'))
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 CEN26FA172Accident · 2 fatalClass 3 · FieldPreliminary reportBeechcraft F33A · Minneapolis, MNOn April 25, 2026, about 1151 central daylight time, a Beechcraft F33A airplane, N8032X was destroyed when it was involved in an accident near Minneapolis, Minnesota. The pilot and passenger were fatally injured. The airplane was operated under Title 14 Code…NTSB CEN24FA304Accident · 4 fatalClass 3 · FieldPreliminary reportBeech F33 · Oklahoma City, OKOn August 6, 2024, about 1326 central daylight time, a Beechcraft F33A airplane, N8095U, was destroyed when it was involved in an accident near Oklahoma City, Oklahoma. The private pilot and the three passengers sustained fatal injuries. The airplane was…NTSB CEN23FA060Accident · 3 fatalClass 3 · FieldFinal reportBeech F33A · Yukon, OKThe pilot’s loss of airplane control for reasons that could not be determined.NTSB ERA21LA101Accident · 1 fatalClass 3 · LimitedFinal reportBeech F33 · Columbia, SCThe pilot's in-flight loss of airplane control due to spatial disorientation during a missed approach in instrument meteorological conditions.NTSB ERA20LA262Accident · 2 fatalClass 3 · LimitedFinal reportBeech F33 · Malbis, ALThe noninstrument-rated pilot’s decision to depart in deteriorating weather conditions, which led to restricted visibility and the pilot’s loss of airplane control due to spatial disorientation. Contributing to the pilot’s poor decision-making was…NTSB ERA20LA179Accident · 1 fatalClass 3 · LimitedFinal reportBeech F33 · Land O Lakes, FLThe partial loss of engine power due to a contaminated fuel system and the pilot’s improper decision to attempt a takeoff with a known deficiency in engine power.NTSB CEN20FA076Accident · 1 fatalClass 3 · FieldFinal reportBeech 33 · Granbury, TXThe pilot's exceedance of the airplane's critical angle of attack while maneuvering in the airport traffic pattern, which resulted in an aerodynamic stall and loss of control.NTSB ERA19FA240Accident · 3 fatalClass 3 · FieldFinal reportBeech F33 · Hatboro, PAThe pilot's loss of airplane control due to spatial disorientation during the departure climb after entering instrument meteorological conditions.NTSB WPR18FA266Accident · 1 fatalClass 2 · FieldFinal reportBeech 33 · Cottonwood, AZThe pilot's mismanagement of the available fuel, which resulted in a total loss of engine power due to fuel starvation.NTSB ERA16FA312Accident · 3 fatalField investigationFinal reportBeech F33 · Carrollton, GAThe failure of the Beech pilot to see and avoid the Diamond that was in front of and below his airplane on final approach and his use of an incorrect radio communication frequency for the airport.NTSB ERA16FA044Accident · 2 fatalField investigationFinal reportBeech F33A · North Salem, NYA loss of airplane control for reasons that could not be determined because examination of the wreckage revealed no mechanical deficiencies.NTSB ERA14FA138Accident · 1 fatalField investigationFinal reportBeech F33 · Lumberport, WVA stroke or cardiovascular event, which resulted in the pilot’s acute impairment or incapacitation and his subsequent flight into terrain.NTSB CEN13FA476Accident · 2 fatalField investigationFinal reportBeechcraft F33A · Ennis, TXThe loss of engine power for reasons that could not be determined during postaccident examinations due to postcrash fire damage.NTSB CEN11FA347Accident · 1 fatalField investigationFinal reportBeech F33A · Taos, NMThe pilot’s continued visual flight into instrument meteorological conditions, which resulted in loss of situational awareness, and a possible encounter with icing conditions.NTSB WPR10FA473Accident · 1 fatalField investigationFinal reportHawker Beechcraft F33 · Phoenix, AZA partial loss of engine power during approach for reasons that could not be determined because postaccident examination did not reveal any anomalies that would have precluded normal operation.NTSB CEN10FA364Accident · 2 fatalField investigationFinal reportBeech F33A · Perry, KSThe failure of the engine driven fuel pump causing a loss of engine power and the pilot's failure to maintain aircraft control resulting in an inadvertent stall. Contributing to the accident was the pilot’s failure to follow the emergency procedures checklist…NTSB ATL06FA129Accident · 3 fatalField investigationFinal reportBeech F-33A · Alabaster, ALThe pilot's failure to maintain airspeed while maneuvering toward an emergency landing area following the total loss of engine power shortly after takeoff resulting in an inadvertent stall, uncontrolled descent, and collision with the ground, and a fence. A…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 LAX06FA099Accident · 1 fatalField investigationFinal reportBeechcraft F33A · Buckeye, AZThe student pilot's failure to maintain aircraft control for undetermined reasons.NTSB LAX06FA031Accident · 1 fatalField investigationFinal reportBeech F33A · Geyserville, CAthe pilot's failure to maintain an adequate terrain clearance altitude profile during the descent that resulted in controlled flight into terrain.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 DEN03FAMS1Accident · 2 fatalMissing aircraftFinal reportBeech F33A · Greer, AZThe airplane is missing for unknown reason.NTSB ATL03LA012Accident · 1 fatalLimited investigationFinal reportBeech F33A · Fernandina Bch, FLWater contamination in the fuel system which resulted in the loss of engine power and the subsequent collision with trees.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 LAX01FA279Accident · 2 fatalField investigationFinal reportBeech F-33A · Mobile, AZThe flying pilot's initiation of an intentional maneuver at an altitude inadequate to maintain terrain clearance. Low altitude flight was a contributing factor.NTSB LAX00FA206Accident · 2 fatalField investigationFinal reportBeech F33A · Columbia, CAThe pilot's failure to abort the downwind takeoff and his failure to attain flying speed.NTSB SEA99FA144Accident · 1 fatalField investigationFinal reportBeech F33A · White Swan, WAInadequate preflight planning/preparation and low airspeed. A dirt embankment, soft runway, and an excessive takeoff weight were factors.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 FTW98FA191Accident · 1 fatalField investigationFinal reportBeech F33A · Del Rio, TXthe pilot's loss of control during a go-around after impacting approach light poles on initial approach. A contributing factor was the prevailing dark night light condition.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 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 LAX93FA377Accident · 3 fatalField investigationFinal reportBeech F33A · Baker, CAA loss of control for undetermined reason(s).NTSB LAX92LA153Accident · 2 fatalLimited investigationFinal reportBeech F33A · Payson, AZThe pilot's poor preflight planning/preparation by intentionally flying into known adverse weather and his poor in-flight decision by not flying to an alternate airport when the airplane began to encounter icing. Contributing to this accident was the icing…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 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 DEN91FA049Accident · 2 fatalField investigationFinal reportBeech F33A · Sterling, COPoor judgement of the pilot and his misjudgement of altitude while buzzing over glassy water. His lack of visual ques to judge altitude over glassy water was a related factor.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 LAX90FA088Accident · 1 fatalField investigationFinal reportBeech F-33A · Oro Valley, AZThe pilot's poor judgement in performing low level aerobatic maneuvers.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,…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 NYC88FA032Accident · 2 fatalField investigationFinal reportBeech F-33A · Forked River, NJThe pilot and passenger departed white plains, new york on a VFR flight to kill devil hills, north carolina. Search efforts were initiated when the aircraft failed to arrive at its destination. A witness in a hunting camp near the crashsite saw the aircraft…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…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…NTSB LAX86FA057Accident · 1 fatalField investigationFinal reportBeech F33A · Sacramento, CAOn December 4, 1985 at 2230 PST, a Beech F33A, operated by the owner, collided with trees during a missed approach at Sacramento metropolitan airport, Sacramento, California, while on a business flight. Instrument meteorological conditions prevailed at the…NTSB LAX85FA213Accident · 1 fatalField investigationFinal reportBeech F33A · Goleta, CAWhen the plt was advised the destn arpt (santa ynez) was directly ahead at 12 mi, he requested a freq change & radar svc was terminated. About 9 min later, he reestablished radio contact (with ARTCC) & reported he was not sure of his psn. The controller told…NTSB CHI81FA063Accident · 1 fatalClosedBeech F33A · Spring Valley, IL