CEN17LA062 · Piper PA22 108
Piper PA22 108 · Accident: loss of control in flight on approach
From Poplar Bluff Municipal Airport (KPOF) to Piedmont Municipal Airport (KPYN)
Event
- NTSB case
- CEN17LA062
- 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
- 0 · 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 PA22 108
- Aircraft type
- Piper PA22
- 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
- N5499Z
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Poplar Bluff Municipal Airport (KPOF), Poplar Bluff, MOTo Piedmont Municipal Airport (KPYN), Piedmont, MO
- Aircraft age
- About 54 years (built 1962)
- 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
- 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
- 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
- Wire
- 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
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The private pilot reported that he performed several touch-and-go landings at a nearby airport and then returned to his home airport to perform several more touch-and-go landings. As he approached the runway for the third landing, he added throttle to adjust his glidepath; however, the engine did not respond. The pilot added that the engine continued to run but did not produce enough power to maintain altitude. The airplane continued to descend, and its landing gear caught a power line. The airplane then impacted terrain. Fuel was present on site. Examination of the airframe and engine revealed no evidence of preimpact mechanical malfunctions or failures that would have precluded normal operation. The examination noted that the propeller blade tips were bent forward with gouges and chordwise scoring on the leading edges, consistent with the engine producing high power. The pilot reported that he did not apply carburetor heat on the approach; however, weather conditions in the area were conducive to the formation of serious carburetor icing at cruise power settings. Although the pilot did not apply carburetor heat and reported that the engine did not produce enough power to maintain altitude, the postaccident examination did not reveal any airplane mechanical malfunctions or failures, and propeller signatures indicate the engine was producing high power during the accident sequence. Thus, the reason for the pilot’s descent below glidepath could not be determined based on the available information.
Probable cause
The pilot’s descent below glidepath, which resulted in the airplane’s impact with power lines.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN17LA062
- Event ID
- 20161229X93022
- Case number
- CEN17LA062
- 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, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2016-12-28.
- API snapshot SHA-256: 1ab87077b5e4a4238f43dfcaaace6e9322dbb2c1a222de19033f744223ee2230; retrieved 2026-09-16T04:55:17.889Z.