FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI02FA292 · Piper PA-24-260

24 Sept 2002 · Ankeny, IA, United States

Piper PA-24-260 · Accident: airframe, component or system failure during initial climb

From Ankeny Regional Airport (IKV) to Lee C Fine Memorial Airport (AIZ)

Report a problem

Event

NTSB case
CHI02FA292
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-24-260

Aircraft type
Piper PA-24
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
N8782P
Operator
Unknown
Onboard fatalities
Unknown
Route
From Ankeny Regional Airport (IKV), Ankeny, IATo Lee C Fine Memorial Airport (AIZ), KAISER/LAKE OZA, MO
Aircraft age
Not recorded
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
First occurrenceThe 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
Airframe, component or system failure
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

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane was destroyed when it impacted the terrain during takeoff climb from runway 18. Witnesses reported seeing the airplane bank left after raising its landing gear about 100-150 feet agl. One witness reported hearing the engine overspeed after the landing gear were raised, but that the overspeed was momentary. Another witness observed the airplane in a very steep bank, approximately 80 degrees. He reported the angle of bank was reduced to about 30 degrees prior to ground impact. The passenger who was in the right rear seat of the accident airplane reported that during take-off the engine started "missing." He reported the pilot stated, "This isn't right," and reached to adjust something and soon after the engine smoothed out. The pilot made a radio call (which the witness could not hear) and banked the airplane to the left. He reported the nose and left wing dropped and the airplane's left wing impacted the ground with about a 30 degree angle of bank. The nose of the airplane hit the ground and the airplane spun around, but did not cartwheel, before it came to a stop. The witness reported that he thought the airplane's engine was no longer missing, but was operating normally when the airplane impacted the ground. The airplane wreckage was located in a harvested cornfield about 600 feet east of runway 18. The approximately 65 foot wreckage path was on a heading of about 030 degrees magnetic. A propeller slash was unearthed about 30 feet from the initial point of impact along the wreckage path. The propeller slash was about 51 inches in length measured at ground level, and it measured about 18 inches deep from ground level to the bottom of the slash mark. The north side of the ground slash had been polished smooth and exhibited a gray color on the slash's surface similar to the paint found on the propeller blades. Inspection of the flight controls revealed continuity between all flight controls and their respective control surfaces. Inspection of the engine revealed it rotated and had thumb compression and suction on all cylinders. The propeller blades had rotational scoring of the paint on camber side of the blades, but no twisting or deformation of the tips. The propeller governor's pressure relief valve spring was found broken as a result of a fatigue fracture. A functional test of the propeller governor revealed that the pressure relief setting and the pump capacity were well below specified minimums. Hartzell Propellers reported, "Such deficiency might cause a propeller to operate at reduced blade angle and higher than normal RPM after take-off." Replacement of the pressure relief valve spring at overhaul was required by Service Bulletin 176 dated November 15, 1991, was not performed. The terrain south of runway 18 at IKV was an open field with few obstacles.

Probable cause

The pilot applied an excessive angle of bank and failed to maintain terrain clearance. An additonal factor was the pilot's attention being diverted.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI02FA292
Event ID
20020927X05237
Case number
CHI02FA292
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. 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: 4e5ab337022fb7f2ee626dd320d7ee5498b6e2323fb237929681c3217781ea90; retrieved 2026-09-20T19:46:04.492Z.