Accident Piper PA-32R-300 Cherokee Lance N43829,
ASN logo
ASN Wikibase Occurrence # 178484
 
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 9 August 2015
Time:23:25
Type:Silhouette image of generic P32R model; specific model in this crash may look slightly different    
Piper PA-32R-300 Cherokee Lance
Owner/operator:Private
Registration: N43829
MSN: 32R-7780527
Year of manufacture:1977
Total airframe hrs:4842 hours
Engine model:Lycoming IO-540-K1G5D
Fatalities:Fatalities: 1 / Occupants: 1
Aircraft damage: Substantial
Category:Accident
Location:Near Harbor Springs Airport (KMGN), Harbor Springs, MI -   United States of America
Phase: Approach
Nature:Private
Departure airport:Detroit, MI (DET)
Destination airport:Harbor Springs, MI (MGN)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The private pilot was completing a long cross-country flight during dark, night visual meteorological conditions. While on a visual approach to the runway, the airplane impacted trees and terrain less than a mile from the end of the runway. The pilot had not logged night flight experience in several years and had not logged any night flight experience in the make and model of the accident airplane. Additionally, he had not logged a flight into the airport in his logbook.

The airport's tree obstructions and nonstandard precision approach path indicator with a 4.0-degree glidepath were noted in the airport facility directory. However, it was the pilot's first flight into the airport; thus, it is likely that his unfamiliarity with the airport environment, including the trees close proximity to the airport and nonstandard glidepath, and the dark, night conditions led to his failure to maintain clearance from the trees. The witness marks on the trees and the damage to the airplane were consistent with the airplane being in a relatively wings level descent when it impacted the tops of the trees. The condition of the landing gear and flaps were consistent with the airplane being configured to land. There were no mechanical anomalies with the airplane, engine, or related systems that would have precluded normal operation at the time of the accident.
Probable Cause: The pilot's failure to maintain clearance from the trees during the approach in dark, night conditions, which resulted in controlled flight into trees and terrain.

Sources:

NTSB
FAA register: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=43829

Location

Revision history:

Date/timeContributorUpdates
10-Aug-2015 15:56 Geno Added
21-Dec-2016 19:30 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
01-Dec-2017 15:08 ASN Update Bot Updated [Operator, Other fatalities, Nature, 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