Accident Zenair CH 601 XL Zodiac N601PH,
ASN logo
ASN Wikibase Occurrence # 196777
 
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:Wednesday 19 July 2017
Time:11:30
Type:Silhouette image of generic CH60 model; specific model in this crash may look slightly different    
Zenair CH 601 XL Zodiac
Owner/operator:Private
Registration: N601PH
MSN: 601-040S
Year of manufacture:2007
Total airframe hrs:264 hours
Engine model:Continental O-200
Fatalities:Fatalities: 1 / Occupants: 1
Aircraft damage: Destroyed
Category:Accident
Location:2 miles east of Bradford County Airport (N27), Towanda, PA -   United States of America
Phase: Initial climb
Nature:Private
Departure airport:Towanda, PA (N27)
Destination airport:Towanda, PA (N27)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The student pilot had just completed a 20-minute local flight and had returned to the airport to conduct touch-and-go takeoffs and landings. During the pilot's second touch-and-go landing, witnesses reported that the engine seemed to be producing partial power during the initial climb and the airplane appeared to stall and recover three times during climb out. As the pilot continued to climb, he bypassed several areas off the departure end of the runway and north and west of the extended runway centerline in which to conduct a forced landing in an open field. The airplane made a shallow turn to the right, then, about 1.5 miles southwest of the airport, it made left a turn south. The pilot declared an emergency over the airport's common traffic advisory frequency, stating that he was attempting to return to the runway; the airplane continued to turn left towards rising terrain. During the turn, the left wing dropped and the airplane descended at a steep angle into trees and rising terrain. The airplane's ballistic recovery system was activated; however, it could not be determined if it was deployed before impact or if accident dynamics caused activation of the system. Examination of the wreckage did not reveal any evidence of preimpact mechanical malfunctions or failures that would have precluded normal operation; however, the scope of the examination was limited due to thermal damage.

The weather conditions at the time of the accident were in the area of a carburetor icing probability chart that was conducive to the formation of serious carburetor icing at descent power and light carburetor icing at cruise or descent power. The pilot operating handbook for the airplane required the application of carburetor heat before landing. If the pilot did not apply carburetor heat during the approach and landing, carburetor ice may have formed, and when he added power for the subsequent takeoff, the engine power would have been reduced. However, the carburetor heat lever could not be functionally tested due to impact and thermal damage, so it could not be determined whether the pilot used the carburetor heat or not; thus the reason for the partial loss of engine power could not be determined. Suitable off airport landing locations were available on the extended runway centerline and to the northwest of the extended runway centerline; however, the pilot elected to turn south toward rising terrain. The pilot subsequently exceeded the airplane's critical angle of attack while attempting to return to the airport following the partial loss of engine power, resulting in an aerodynamic stall and loss of control.

The pilot had significant heart disease with an enlarged heart, aortic valve replacement, and some arrhythmia that required treatment with a pacemaker, all of which put him at increased risk for sudden incapacitation. However, his heart disease would not have affected his decision-making nor his ability to respond to an inflight emergency, and there is no evidence that his heart disease contributed to the accident.


Probable Cause: A partial loss of engine power for reasons that could not be determined based on the available information, and the pilot's exceedance of the airplane's critical angle of attack during an attempted return to the airport, which resulted in an aerodynamic stall and loss of control. Contributing to the accident was the pilot's decision to return to the airport following a partial loss of engine power.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: ERA17FA248
Status: Investigation completed
Duration: 2 years and 9 months
Download report: Final report

Sources:

NTSB
FAA register: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?omni=Home-N-Number&nNumberTxt=N601Ph

Location

Media:

Revision history:

Date/timeContributorUpdates
19-Jul-2017 18:11 Iceman 29 Added
19-Jul-2017 18:14 Iceman 29 Updated [Location, Embed code]
19-Jul-2017 18:19 Iceman 29 Updated [Total fatalities, Embed code]
19-Jul-2017 19:46 Iceman 29 Updated [Time, Aircraft type, Location, Source, Embed code, Narrative]
20-Jul-2017 05:26 Iceman 29 Updated [Operator, Total occupants, Other fatalities, Embed code, Narrative]
20-Jul-2017 18:39 PiperOnslaught Updated [Aircraft type, Registration, Cn, Source, Embed code, Damage]
20-Jul-2017 22:11 Geno Updated [Aircraft type]
20-Jul-2017 22:17 Geno Updated [Aircraft type, Location, Source, Narrative]
21-Jul-2017 07:46 Alpine Flight Updated [Time, Aircraft type, Source, Damage]
22-Apr-2020 17:04 ASN Update Bot Updated [Time, Nature, Departure airport, Destination airport, Source, Narrative, Accident report, ]

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