ERA16FA169 · Piper PA32 300
Piper PA32 300 · Accident: loss of control in flight during initial climb
From Boone Inc Airport (NC14) to Boone Inc Airport (NC14)
Event
- NTSB case
- ERA16FA169
- 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 PA32 300
- Aircraft type
- Piper PA32
- 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
- N43576
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Boone Inc Airport (NC14), Boone, NCTo Boone Inc Airport (NC14), Boone, NC
- Aircraft age
- About 42 years (built 1974)
- 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
- Initial climb
- 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
- Loss of control in flight
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The private pilot and two passengers were conducting a local flight from the pilot's home airport. One witness stated that his attention was drawn to the airplane due to its "very fast" landing approach. The airplane then disappeared from his view; shortly thereafter, he saw a plume of smoke in the area of a golf course on the northwest side of the airport. Several witnesses on the golf course stated that the airplane appeared to be taking off, and noted that it was "struggling," that it was "too low," and was "bobbing up and down." The airplane impacted a stand of 75-ft-tall pine trees and came to rest on the golf course, where it was consumed by a post-crash fire. The rear seat passenger was fatally injured; the pilot and front seat passenger received serious injuries. Neither the pilot nor the passenger could recall the events of the accident flight.
Postaccident examination of the airframe and engine revealed no anomalies that would have precluded normal operation. The landing runway measured 2,700 ft long by 40 ft wide. Given the witness observation of the airplane's fast approach speed, it is likely that the pilot initiated a go-around due to excessive airspeed and/or a lack of runway remaining on which to stop; however, it could not be determined when the pilot began the go-around maneuver. The airplane's low altitude as it climbed away from the runway suggests that the pilot may have initiated the go-around near touchdown or possibly even after touching down. Had the pilot started the go-around earlier, after recognizing the airplane's unstabilized approach due to excessive airspeed, he would have allowed more time to re-configure the airplane, establish a positive rate of climb, and clear the trees near the end of the runway. However, the late go-around placed the airplane in close proximity to the trees, from which the pilot subsequently failed to maintain lateral clearance.
Probable cause
The pilot's delayed decision to conduct a go-around following an unstabilized landing approach and his subsequent failure to maintain clearance from trees near the end of the runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA16FA169
- Event ID
- 20160425X45203
- Case number
- ERA16FA169
- 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: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: ff2c138f2bef646c3f697e5f4daec7c45a9b597f64572d333d24b31fe75af62f; retrieved 2026-09-14T21:44:57.377Z.