CEN21FA300 · Beech 35-33
Beech 35-33 · Accident: loss of control in flight en route
From Ardmore Municipal Airport (ADM) to an unrecorded destination
Event
- NTSB case
- CEN21FA300
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 2 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Instrument Meteorological Cond
Beech 35-33
- Aircraft type
- Beechcraft 35
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N302Z
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Ardmore Municipal Airport (ADM), Ardmore, OKTo not recorded
- Aircraft age
- About 61 years (built 1960)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route · climb to cruise
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of control in flight
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Psychological
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot was conducting a personal flight at night in low-visibility conditions. According to automatic dependent surveillance-broadcast (ADS-B) data, during the initial portion of the flight, the airplane’s altitude was generally between 1,000 and 2,000 ft before the airplane climbed to 3,000 ft. About 4.5 minutes before the accident, the airplane entered a gradual descent to an altitude between about 1,400 and 1,500 ft and continued to fly at that altitude (200 to 300 ft above ground level) for about the next 2 minutes. The airplane then entered a left turn that became increasingly tighter. During this turn, the airplane climbed to about 1,600 ft before descending. The last ADS-B return showed that the airplane was about 0.2 miles west of the last radar return, about 280 ft above ground level, and along a track of about 190°. Postaccident examination revealed no evidence of a pre-existing mechanical malfunction or failure that would have precluded normal operation of the airplane. The pilot was not instrument rated. The available evidence for this accident did not indicate whether the pilot received weather information for the route of flight. The pilot likely anticipated visual meteorological conditions given that, shortly before takeoff, he informed his wife that the airplane would be in those conditions along the entire route. The low-visibility night conditions were conducive to the development of spatial disorientation. Although ADS-B data showed that the airplane was flying close to terrain during the final portion of the flight, the airplane was maneuvering over an area without much cultural lighting (such as the illumination from the reflection of lighting in a metropolitan area). Without such lighting, the pilot would not have had reliable visual references for maintaining attitude control. The spiral flightpath was consistent with the pilot experiencing the known effects of spatial disorientation. Also, the wreckage distribution and extensive airplane fragmentation were consistent with a highenergy impact resulting from the effects of spatial disorientation.
Probable cause
The pilot’s loss of airplane control due to spatial disorientation during low-level nighttime flight.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN21FA300
- Event ID
- 20210702103400
- Case number
- CEN21FA300
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates, cause areas. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: b42dc49c43f11bb22c13237ded99804c647591891114c56433bb5b909be36695; retrieved 2026-09-15T07:30:51.899Z.