Beech 65 A90 accident near Byron, California, July 24, 2016
On July 24, 2016 at about 2:00 am local time, a 1967 Beech 65 A90, registered N256TA, was substantially damaged in an accident during enroute (descent) near Byron, California (Byron airport). It was a skydiving flight under general aviation rules (Part 91). No one was hurt; 15 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
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.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 24, 2016 · about 2:00 am local time · cases in 2016
- Place
- Byron, California · Byron · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 15 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Beech 65 A90 UNDESIGNAT, built 1967 · all 65 A90s on the register
- Registration
- N256TA · no longer on the register · serial LJ-256
- Damage
- Substantial damage
- Flight
- Skydiving flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Aerodynamic stall/spin during enroute (climb to cruise)
- Aircraft structural failure during enroute (descent) defining event
The NTSB's findings
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Not attained/maintained
- cause Personnel issues › Task performance › Use of equip/info › Use of equip/system › Pilot
- cause Personnel issues › Action/decision › Action › Incorrect action performance › Pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Angle of attack › Capability exceeded
- cause Personnel issues › Task performance › Use of equip/info › Use of checklist › Pilot
- factor Personnel issues › Task performance › Planning/preparation › Weight/balance calculations › Pilot
- factor Aircraft › Aircraft oper/perf/capability › Aircraft capability › CG/weight distribution › Capability exceeded
Pilot
- Certificate: commercial pilot
- Ratings: multi-engine land; single-engine land; instrument: airplane
- Flight time: 1,860 hours in all; 20.5 in this make and model; 284.2 in the last 90 days; 1,706.1 as pilot in command
- Last flight review: March 16, 2016
- Medical certificate: Class 1 (without waivers/limitations)
- Seat: left
- Injury: no injuries
Passenger
- Seat: unk
- Injury: no injuries
Passenger
- Seat: unk
- Injury: no injuries
Passenger
- Seat: unk
- Injury: no injuries
Passenger
- Seat: unk
- Injury: no injuries
Passenger
- Seat: unk
- Injury: no injuries
Passenger
- Seat: unk
- Injury: no injuries
Passenger
- Seat: unk
- Injury: no injuries
Passenger
- Seat: unk
- Injury: no injuries
Passenger
- Seat: unk
- Injury: no injuries
Passenger
- Seat: unk
- Injury: no injuries
Passenger
- Seat: unk
- Injury: no injuries
Passenger
- Seat: unk
- Injury: no injuries
Passenger
- Seat: unk
- Injury: no injuries
Passenger
- Seat: unk
- Injury: no injuries
The aircraft
- Airframe total time: 14,543.9 hours
- Last inspection: continuous airworthiness programme, December 5, 2015
- Maximum gross weight: 9,650 lb
- Seats: 15
- Landing gear: retractable
- Engine 1: Pratt and Whitney PT6A-20 (turboprop); 0 hours total
- Engine 2: Pratt and Whitney PT6A-20 (turboprop); 0 hours total
The flight
- Departed from: C83 Byron CA at 1:51 am
- Destination: C83 Byron CA
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: from 280° at 12 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 90°F (32°C), dew point 45°F (7°C)
- Altimeter: 29.81 inHg
- Observation at 1:53 am from LVK, 12 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 14 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
11 documents, released by the NTSB on December 11, 2017. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Materials Laboratory Factual Report 16-076 | PDF, 3 pages | View Download |
| 2 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 12 pages | View Download |
| 3 | Record of Conversation | PDF, 6 pages | View Download |
| 4 | Recorded Air Traffic Control radar Data (Plot) | PDF, 4 pages | View Download |
| 5 | Airplane Flight Manual Spin Warning | PDF, 1 page | View Download |
| 6 | Pilot's Handbook of Aeronautical Knowledge Excerpt | PDF, 2 pages | View Download |
| 7 | Maintenance Record | PDF, 1 page | View Download |
| 8 | Weight and Balance | PDF, 4 pages | View Download |
| 9 | Airframe Examination | PDF, 3 pages | View Download |
| 10 | Statement of Party Representatives to NTSB Investigation | PDF, 1 page | View Download |
| 11 | Accident Airplane Pictures | PDF, 3 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Other NTSB records under N256TA the same tail number, which may have belonged to a different aircraft at the time
Connections how this case links to the rest of the register
- N256TA: not on the register today · the record of its deregistration
- Beechcraft 65 201 registered today · the model family and its accident history
- Beechcraft 6 aircraft on the register
- Engine: Pratt and Whitney PT6A-20 2,217 aircraft carry this series today · as the NTSB recorded it
- Engine: Pratt and Whitney PT6A-20 2,217 aircraft carry this series today · as the NTSB recorded it
- Byron Airport · nearest airport
- Accidents and incidents in California 9,080 since 1982 · 1,094 in the last ten years
- California 28,286 aircraft registered
- Other NTSB records under N256TA 1 records · the number may have belonged to another aircraft at the time
The whole map of how records connect · these connections as data: /graph/accident/WPR16LA150.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
