Piper PA-34-220T accident near Ankeny, Iowa, June 9, 2010
On June 9, 2010 at about 11:20 pm local time, a Piper PA-34-220T, registered N104NW, was substantially damaged in an accident during landing (flare/touchdown) near Ankeny, Iowa (Ankeny Regional Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 3 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The failure of the stabilator control cable due to wear. Contributing to the accident was the inadequate maintenance inspection of the stabilator control cable.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- June 9, 2010 · about 11:20 pm local time · cases in 2010
- Place
- Ankeny, Iowa · Ankeny Regional Airport · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 3 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-34-220T · all PA-34-220Ts on the register
- Registration
- N104NW · registry record · serial 34-8133059
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Hard landing during landing (flare/touchdown) defining event
The NTSB's findings
- cause Aircraft › Aircraft systems › Flight control system › Stabilizer control system › Failure other cases naming the flight controls
- cause Aircraft › Aircraft systems › Flight control system › Stabilizer control system › Fatigue/wear/corrosion other cases naming the flight controls
- factor Personnel issues › Task performance › Maintenance › Scheduled/routine maintenance › Maintenance personnel
Pilot
- Certificate: commercial pilot, private
- Ratings: multi-engine land; single-engine land; single-engine sea; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane; rotorcraft: helicopter
- Flight time: 4,168 hours in all; 1,460 in this make and model
- Medical certificate: Class 2 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 7,240 hours
- Last inspection: annual inspection, March 19, 2010; 17 hours since
- Maximum gross weight: 4,773 lb
- Seats: 6
- Landing gear: retractable
- Engine 1: Cont Motor TSIO-360 SER (piston); 0 hours total
- Engine 2: Cont Motor TSIO-360 SER (piston); 0 hours total
The flight
- Departed from: DTL Detroit Lakes MN at 9:22 pm
- Destination: IKV Ankeny IA
- Flight plan: IFR
- Runway 36, 5,500 ft by 100 ft
Weather at the time
- Light: daylight
- Wind: from 330° at 12 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 82°F (28°C), dew point 50°F (10°C)
- Altimeter: 29.93 inHg
- Observation at 11:00 pm from IKV, 1 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 2 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
17 documents, released by the NTSB on November 18, 2010. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N104NW on the register today · the tail number may have moved to another aircraft since
- Piper PA-34 Seneca 997 registered today · the model family and its accident history
- Piper 44,843 aircraft on the register
- Engine: Cont Motor TSIO-360 SER 1,907 aircraft carry this series today · as the NTSB recorded it
- Engine: Cont Motor TSIO-360 SER 1,907 aircraft carry this series today · as the NTSB recorded it
- Ankeny Regional · nearest airport
- Detroit Lakes/Wething Field · departed from
- Accidents and incidents in Iowa 871 since 1982 · 131 in the last ten years
- Iowa 4,514 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/CEN10LA312.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
