CEN15FA342 · Piper PA 32R-300
Piper PA 32R-300 · Accident: controlled flight into terrain/object (CFIT) on approach
From Coleman A. Young Municipal Airport (DET) to Harbor Springs Airport (MGN)
Event
- NTSB case
- CEN15FA342
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 1 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Piper PA 32R-300
- Aircraft type
- Piper PA-32
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N43829
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Coleman A. Young Municipal Airport (DET), Detroit, MITo Harbor Springs Airport (MGN), Harbor Springs, MI
- Aircraft age
- About 38 years (built 1977)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Approach · VFR pattern final
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Controlled flight into terrain/object (CFIT)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Psychological
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB 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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN15FA342
- Event ID
- 20150810X05447
- Case number
- CEN15FA342
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2015-08-10.
- API snapshot SHA-256: 1dc838a6d495d740f13a3ec4ded8642eba3e705e3c7fcdd16fc723ed3627f7e2; retrieved 2026-09-14T19:49:13.659Z.