Accident Piper PA-32R-300 N8362C,
ASN logo
ASN Wikibase Occurrence # 289741
 
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:Sunday 8 September 2013
Time:15:56 LT
Type:Silhouette image of generic P32R model; specific model in this crash may look slightly different    
Piper PA-32R-300
Owner/operator:Private
Registration: N8362C
MSN: 32R-7680099
Year of manufacture:1976
Total airframe hrs:5156 hours
Engine model:Lycoming TIO-540-K1A5D
Fatalities:Fatalities: 0 / Occupants: 2
Aircraft damage: Substantial
Category:Accident
Location:Guntersville, Alabama -   United States of America
Phase: Standing
Nature:Private
Departure airport:Gadsden-Northeast Alabama Regional Airport, AL (GAD/KGAD)
Destination airport:Gadsden-Northeast Alabama Regional Airport, AL (GAD/KGAD)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The pilot reported that, about 3 to 4 nautical miles east-northeast of the nearest airport, the engine suddenly quit. GPS data indicate that the airplane was about 4,300 ft about that time. The pilot's attempts to restore power were unsuccessful. The pilot stated that he turned the airplane right toward the airport, and that, as he neared it, he announced his intention to land. While on approach, about 1/2 to 3/4 mile from the intended runway and with the flaps retracted, he allowed the airplane to slow to the point that the landing gear autoextend system caused the landing gear to extend, which he had not planned to do. He continued toward the runway, and the airplane touched down in water about 100 yards from the approach end of the intended runway. The pilot stated that, if the landing gear had not extended automatically, he believed that he could have reached land. Although the pilot reported that he turned toward the airport after the power loss, GPS data indicated that he actually flew west of the extended runway centerline and then maneuvered toward the airport. Based on data from the best glide chart in the Pilot's Operating Handbook, if the pilot had proceeded on a more direct course to the airport after the engine power loss or had not allowed the landing gear to automatically extend while on short final, the airplane likely would have been able to reach the intended runway.

Postrecovery examination of the engine revealed that the single-drive dual magneto was separated from the accessory case because the lower attachment hardware had lost its clamping force and that the upper flange of the magneto had fractured due to fatigue cracking. Examination also revealed that the magneto was not installed in accordance with an engine manufacturer's service instruction—an incorrect gasket, washer, and clamp were used—all of which contributed to the separation of the magneto. Although compliance with service instructions is not mandatory for Part 91 operators, if the instructions had been complied with the last time the magneto was serviced, it is likely that it would not have separated despite the fact that the airplane had not undergone an annual inspection in over 2 1/2 years and, therefore, was unairworthy at the time of the accident.

Probable Cause: The improper installation of the engine magneto by unknown maintenance personnel, which resulted in the magneto separating from the engine and a subsequent total loss of engine power. Contributing to the accident was the pilot's delay in proceeding directly to the nearest airport and his failure to prevent the automatic extension of the landing gear following the total loss of engine power, which resulted in a landing undershoot.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: ERA13LA407
Status: Investigation completed
Duration: 1 year and 9 months
Download report: Final report

Sources:

NTSB ERA13LA407

Location

Revision history:

Date/timeContributorUpdates
05-Oct-2022 17:43 ASN Update Bot Added

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