FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN10LA312 · Piper PA-34-220T

9 Jun 2010 · Ankeny, IA, United States

Piper PA-34-220T · Accident: hard landing

From Detroit Lakes Airport (DTL) to Ankeny Regional Airport (IKV)

Report a problem

Event

NTSB case
CEN10LA312
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 PA-34-220T

Aircraft type
Piper PA-34
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
N104NW
Onboard fatalities
Unknown
Route
From Detroit Lakes Airport (DTL), Detroit Lakes, MNTo Ankeny Regional Airport (IKV), Ankeny, IA
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
Landing · flare/touchdown
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
Hard landing
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 systems

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot reported that when he pulled back on the control yoke during the landing flare the nose of the airplane did not pitch up. The airplane landed hard on the nosewheel and bounced several times before stopping on the runway. A postaccident examination of the airplane revealed that the stabilator control cable had fractured in two pieces. The location of the fracture was in the unobstructed area in the tail cone; the location of the fracture was not associated with a pulley, fairlead, or bulkhead, and no rubbing or chaffing was found in the area of the fracture. The entire length of the cable was covered with dried black grease and the majority of the fractured ends of the individual wires exhibited wear damage with the exposed surfaces of the wires covered in grease. The ends of the fractured wires exhibited features typical of overstress separation, with no evidence of fatigue cracking. Federal Aviation Administration guidance states that the inspection and repair of control cables should be accomplished during annual inspections. The aircraft maintenance logbooks indicated that the last annual maintenance inspection was conducted about three months prior to the accident, equating to 17 flight hours. The logbook entry for that inspection indicated that the control cables were checked for correct rigging and cable tensions. The logbook entry stated, “Stabilator OK.” There was no indication of any repair or replacement of the stabilator control cable.

Probable cause

The failure of the stabilator control cable due to wear. Contributing to the accident was the inadequate maintenance inspection of the stabilator control cable.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN10LA312
Event ID
20100610X21734
Case number
CEN10LA312
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: 71fc844b5b540a1d9dc0a753de8aa6e813855e502a80a2306060974db594f65f; retrieved 2026-09-15T14:26:05.296Z.