WPR16LA150 · Beech 65 A90 UNDESIGNAT
Beech 65 A90 UNDESIGNAT · Accident: aircraft structural failure en route
From Byron Airport (C83) to Byron Airport (C83)
Event
- NTSB case
- WPR16LA150
- 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
- 0 · 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
- Visual Meteorological Cond
Beech 65 A90 UNDESIGNAT
- Aircraft type
- Beechcraft 65
- 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
- N256TA
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Byron Airport (C83), Byron, CATo Byron Airport (C83), Byron, CA
- Aircraft age
- About 49 years (built 1967)
- 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 · descent
- 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
- Aircraft structural failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The commercial pilot reported that, while setting up for a skydiving jump run, the airspeed was a little slow, and the airplane abruptly stalled, rolled left, and began rotating downward. A jumper, seated in the copilot's seat, stated that the pilot did not retard the throttles during the recovery attempt and that the airplane's airspeed increased rapidly. The jumper also reported that he heard a "loud bang" during the recovery sequence. The pilot briefly recovered the airplane to a wings-level attitude, but it then subsequently stalled and entered another spin. During the second spin event, all the jumpers successfully egressed. After about nine rotations, the pilot recovered the airplane to a wings- and pitch-level attitude, and shortly thereafter, it broke off to the left and stalled and rotated downward again. The pilot recovered the airplane again and flew back to the airport because the airplane was handling abnormally, and he landed it without further incident.
After landing, a witness noted that the airplane's right horizontal stabilizer and elevator were missing; they were subsequently recovered in a field a few miles south of the airport. Magnified optical examination revealed that all the fracture surfaces on the right horizontal stabilizer, elevator, and attachment bracket were consistent with overstress separations, which was likely the source of the loud bang heard by the jumper during the recovery sequence. No indications of fatigue or corrosion were observed. Therefore, it is likely that the right horizontal stabilizer and the attached elevator were overstressed during the airplane's left spin recovery, which led to their in-flight separation. Due to the dynamics during a spin recovery, only the right horizontal stabilizer experienced g forces and air flow beyond its limit.
The Airplane Flight Manual contained a spin recovery procedure, which stated to "immediately move the control column full forward, apply full rudder opposite to the direction of the spin, and reduce power on both engines to idle. These three actions should be done as near simultaneously as possible." It is likely that the pilot's failure to follow these procedures led to the airplane's airspeed rapidly increasing and caused increased air flow, which required additional g forces to recover.
Postaccident, the airplane's weight and balance were calculated for the accident flight, and the center of gravity (CG) was determined to be about 6 to 7 units aft of the limit. An aft CG results in the airplane being in a less stable flight condition, which decreases the ability of the airplane to right itself after maneuvering and likely contributed to the pilot's inability to maintain level flight.
Probable cause
The pilot’s failure to maintain an adequate airspeed and his exceedance of the airplane’s critical angle of attack, which resulted in an aerodynamic stall and subsequent spin. Also causal to the accident was the pilot’s failure to follow prescribed spin recovery procedures, which resulted in increased airspeed and airflow and the subsequent overstress separation of the right horizontal stabilizer. Contributing to the accident was the pilot’s inadequate preflight weight and balance calculations, which resulted in the center of gravity being aft of the limit.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR16LA150
- Event ID
- 20160724X01920
- Case number
- WPR16LA150
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2016-07-24.
- API snapshot SHA-256: 768ab078caff53a4a4c90cd897984522557c662b06bdb0475ea9ea511a6812e1; retrieved 2026-09-16T03:41:29.490Z.