Beech G35 accident near Byron, Georgia, July 31, 2011
On July 31, 2011 at about 5:19 pm local time, a Beech G35, registered N156RP, was substantially damaged in an accident during enroute (descent) near Byron, Georgia. It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot’s sustained flight at airspeeds in excess of the airplane's never exceed speed during a steep descent, which resulted in a subsequent in-flight structural failure due to overstress.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 31, 2011 · about 5:19 pm local time · cases in 2011
- Place
- Byron, Georgia · map
- Type
- Accident
- Injuries
- 1 person was killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Beech G35 · all G35s on the register
- Registration
- N156RP · no longer on the register · serial D-4492
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
During a cross-country flight, about 9,200 feet mean sea level, the pilot cancelled his visual flight rules flight following and descended toward the destination airport. Review of the radar data showed the airplane descending from 9,200 feet at a rate of 2,000 feet per minute and a ground speed of 180 knots. At an altitude of about 3,000 feet, the ground speed was 178 knots and radar contact was lost. No radio transmissions were received from the pilot after radar contact was lost. Witnesses who were working in a field said they heard a loud "popping" sound. They looked up and saw an airplane and what looked like a wing separating from it. They continued to watch the airplane as it began to spin before crashing into the ground. Examination of the airplane revealed that the airplane wings had experienced high positive forces when the stabilizers broke in a downward direction. Once the stabilizers broke, the airplane immediately pitched down and changed rapidly from a high positive angle of attack (AOA) to a high negative AOA. The high negative air loads on the wings caused the right wing to break in a downward direction and caused the left wing and fuselage to rotate left wing down. Further breakup analysis indicated that there was no specific evidence of flutter. A review of the airplane flight manual revealed the never-exceed speed (VNE) for calculated and indicated airspeed was 176 knots. During the postaccident examination of the airspeed indicator, the indicator needle was stuck at the 192 mph position. It is likely that as a result of the continued flight beyond the VNE envelope during a steep descent to the destination airport, the airplane broke up in flight due to the airplane exceeding the design limits.
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
- Aircraft structural failure during enroute (descent) defining event
- Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent
The NTSB's findings
- cause Personnel issues › Action/decision › Action › Incorrect action performance › Pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Capability exceeded
- cause Aircraft › Aircraft structures › Fuselage › Fuselage main structure › Failure other cases naming the airframe structure
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 400 hours in all; 140 in this make and model
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: unk
- Injury: fatal
The aircraft
- Airframe total time: 4,172 hours
- Last inspection: annual inspection, June 4, 2011
- Maximum gross weight: 3,650 lb
- Seats: 3
- Landing gear: retractable
- Engine: Cont Motor E225 SERIES (piston); 0 hours total
The flight
- Departed from: DVK Danville KY at 3:19 pm
- Destination: PXE Perry GA
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: from 320° at 9 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 95°F (35°C), dew point 72°F (22°C)
- Altimeter: 30.00 inHg
- Observation at 5:55 pm from WRB, 11 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
39 documents, released by the NTSB on October 17, 2012. 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.
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N156RP: not on the register today · the record of its deregistration
- Beechcraft G35 224 registered today · the model family and its accident history
- Beechcraft 6 aircraft on the register
- Engine: Cont Motor E225 SERIES 980 aircraft carry this series today · as the NTSB recorded it
- Stuart Powell Field · departed from
- Perry-Houston County · bound for
- Accidents and incidents in Georgia 2,138 since 1982 · 361 in the last ten years
- Georgia 8,806 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/ERA11FA431.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.
