PIPER PA-31-350 near Richmond, VA — 2011-04-12
- Date
- 2011-04-12
- Location
- Richmond, VA, USA
- Airport
- RIC
- Aircraft
- PIPER PA-31-350
- Registration
- N3547C
- Category
- Airplane
- Highest injury
- Serious
- Fatalities
- 0
- Phase of flight
- Takeoff roll
Probable cause
The pilot’s failure to maintain adequate airspeed during the initial climb, which resulted in an aerodynamic stall and subsequent impact with the ground.
NTSB narrative
The twin-engine airplane was scheduled for a routine night cargo flight. Witnesses and radar data described the airplane accelerating down the runway to a maximum ground speed of 97 knots, then entering an aggressive climb before leveling and pitching down. The airplane subsequently impacted a parallel taxiway with its landing gear retracted. Slash marks observed on the taxiway pavement, as well as rotation signatures observed on the remaining propeller blades, indicated that both engines were operating at impact. Additionally, postaccident examination of the wreckage revealed no evidence of any preimpact mechanical failures or malfunctions of the airframe or either engine. The as-found position of the cargo placed the airplane within the normal weight and balance envelope, with no evidence of a cargo-shift having occurred, and the as-found position of the elevator trim jackscrew was consistent with a neutral pitch trim setting. According to the airframe manufacturer's prescribed takeoff procedure, the pilot was to accelerate the airplane to an airspeed of 85 knots, increase the pitch to a climb angle that would allow the airplane to accelerate past 96 knots, and retract the landing gear before accelerating past 128 knots. Given the loading and environmental conditions that existed on the night of the accident, the airplane's calculated climb performance should have been 1,800 feet per minute. Applying the prevailing wind conditions about time of the accident to the airplane's radar-observed ground speed during the takeoff revealed a maximum estimated airspeed of 111 knots, and the airplane's maximum calculated climb rate briefly exceeded 3,000 feet per minute. The airplane then leveled for a brief time, decelerated, and began descending, a profile that suggested that the airplane likely entered an aerodynamic stall during the initial climb.
Analysis
- Primary failure mode
- Engine power loss
- First missed decision gate
- Pilot could have aborted takeoff after detecting left engine power loss.
NTSB coding
Evidence available
- ADS-B / radar
- Photos
- 20 docket documents
Docket documents20
- Air Traffic Controller Statementsatc
- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1form
- Release of Aircraft Wreckage, NTSB Form 6120.15form
- Memorandum for Record - Telephone Interview, Pilotinterview
- Memorandum for Record - Telephone Interview, Witnessesinterview
- Pilot Interview Summary (Courtesy of FAA)interview
- Statement of Party Representatives to NTSB Investigationinterview
- Airframe Manufacturer's Field Notesother
- Airport Diagramother
- Memorandum for Record - FAA Examination of Cargoother
- Materials Laboratory 15 - Factual Report 11-101 (with 4 embedded images)photos
- Photo 1 - Wreckage from Front Right (Photo Courtesy of FAA)photos
- Photo 2 - Taxiway After Wreckage Recovery (Courtesy of Richmond ARFF)photos
- Photo 3 - Abrasions and Slash Marks on Taxiway (Courtesy of Richmond ARFF)photos
- Photo 4 - Slash Marks Oriented Perpendicular to Taxiway, 1 of 2 (Courtesy of Richmond ARFF)photos
- Photo 5 - Slash Marks Oriented Perpendicular to Taxiway, 2 of 2 (Courtesy of Richmond ARFF)photos
- Photo 6 - Right Propellerphotos
- Photo 7 - Left Propellerphotos
- Radar Data Plotradar
- Wreckage Examination Summary (Courtesy of FAA)wreckage
Related mishaps
- BEECH B35
2026-01-02 · La Casa, TX
- CESSNA 172
2025-12-07 · Pensacola, FL
- CHAMPION 7ECA
2025-10-07 · East Rockingham, NC
- BEECH C23
2025-09-10 · South Bend, IN
- SCHWEIZER AIRCRAFT CORP G-164B
2025-09-09 · Dover, DE
- BEECH 35
2025-07-13 · Cedarcreek, MO