Loss of control Accident Aero Commander 680E N222JS,
ASN logo
ASN Wikibase Occurrence # 179770
 
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Monday 21 September 2015
Time:16:20
Type:Silhouette image of generic AC68 model; specific model in this crash may look slightly different    
Aero Commander 680E
Owner/operator:Private
Registration: N222JS
MSN: 680E-721-28
Year of manufacture:1959
Total airframe hrs:7500 hours
Engine model:Lycoming GSO-480-B1A6
Fatalities:Fatalities: 0 / Occupants: 1
Aircraft damage: Substantial
Category:Accident
Location:Boise Air Terminal/Gowen Field (KBOI), Boise, ID -   United States of America
Phase: Landing
Nature:Private
Departure airport:Weiser, ID (S78)
Destination airport:Boise, ID (BOI)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The commercial pilot was conducting a personal flight. He reported that he did not recall what happened the day of the accident. One witness, who was former pilot, reported that he saw the airplane fly over his house and that the engines sounded as if they were “out of sync.” A second witness, who lived about 5 miles away from the airport, reported that she saw the airplane flying unusually low. She added that the engines sounded terrible and that they were “popping and banging.” A third witness, who was holding short of the runway waiting to take off, reported that he saw the airplane approaching the runway about 75 ft above ground level (agl). He then saw the airplane descend to about 50 ft agl and then climb back to about 75 ft agl, at which point the airplane made a hard, right turn and then impacted terrain.
Although a postaccident examination of both engines revealed no evidence of a mechanical failure or malfunction that would have precluded normal operation, the witnesses’ described what appeared to be an engine problem. It is likely that one or both of the engines was experiencing some kind of problem and that the pilot subsequently lost airplane control. The pilot reported in a written statement several months after the accident that, when he moved the left rudder pedal back and forth multiple times after the accident, neither the torque tubes nor the rudder would move, that he found several of the rivets sheared from the left pedal, and that he believed the rudder had failed. However, postaccident examination of the fractured rivets showed that they exhibited deformation patterns consistent with overstress shearing that occurred during the accident sequence. No preimpact anomalies with the rudder were found.
Probable Cause: The pilot's failure to maintain airplane control following an engine problem for reasons that could not be determined because postaccident examination of both engines and the rudder revealed no malfunctions or anomalies that would have precluded normal operation.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: WPR15LA265
Status: Investigation completed
Duration:
Download report: Final report

Sources:

NTSB

Location

Revision history:

Date/timeContributorUpdates
22-Sep-2015 04:52 Geno Added
30-Sep-2015 04:13 Geno Updated [Nature, Departure airport, Source, Narrative]
21-Dec-2016 19:30 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
08-Sep-2017 19:47 ASN Update Bot Updated [Operator, Other fatalities, Departure airport, Destination airport, Source, Narrative]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org