Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

June 9, 2010 · Piper PA-34-220T · N104NW

Ankeny, IA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
June 9, 2010
Injury Outcomes
No injuries (3 uninjured)
Location
Ankeny, IA
Aircraft
Piper PA-34-220T
Tail Number
N104NW
Operator
Mclaughlin John H
Injuries
None
Aircraft Damage
Substantial
NTSB Number
CEN10LA312

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.

NTSB 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.

Full Narrative

On June 9, 2010, at 1820 central daylight time, a Piper PA-34-220T, N104NW, sustained substantial damage during a hard landing on runway 36 (5,500 feet by 100 feet, concrete) at the Ankeny Regional Airport (IKV), Ankeny, Iowa. The pilot and two passengers were not injured. The 14 Code of Federal Regulations Part 91 personal flight departed Detroit Lakes (DTL), Minnesota, about 1622 with IKV as the destination airport. Visual meteorological conditions prevailed and an instrument flight rules(IFR) flight plan was filed. The pilot reported that the flight was normal until the final approach for landing. He reported that when he pulled back on the control yoke during the flare, the nose of the airplane did not pitch up. The airplane landed hard on the nose wheel and bounced several times. The pilot maintained directional control of the airplane before he stopped it on the runway. Once stopped, he taxied the airplane to the ramp. The firewall and fuselage sustained substantial damage. A Federal Aviation Administration (FAA) airworthiness inspector examined the airplane. Maintenance personnel removed the floorboards and tunnel panels for inspection of the control cables. The inspection revealed that the stabilator control cable had fractured in two pieces. The location of the fracture was in the unobstructed space 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 or tail cone. The entire length of the cable was covered with dried black grease. The cable was removed and sent to the National Transportation Safety Board’s (NTSB) Materials Laboratory for examination. The NTSB Materials Laboratory’s inspection revealed that the cable’s composition was consistent with stainless steel. The cable fractured approximately 18 inches from the turnbuckle end and approximately 65 inches from the ball portion of the single-shank ball-end terminal. The entire length of the cable was covered with grease. The individual cable wires in the area of the fracture were found partially unraveled and the exposed surfaces were covered with grease. A majority of the fractured ends of the individual wires exhibited wear damage at a slant plane relative the length of the cable that reduced the ends of the wire to a knife edge. Wear damage reduced the majority of a wire’s cross section. The ends of the remaining fractured wires exhibited elongation deformation and cup and cone fracture features typical of overstress separation. The fractured end of the wires showed micro-void coalescence dimple features typical of overstress separation with no evidence of fatigue cracking. On January 3, 2001, the New Piper Aircraft Company issued Service Bulletin (SB) 1048, “Stainless Steel Control Cables.” It identified Piper manufactured airplanes that had stainless steel cables installed. According to the SB-1048, the accident airplane, N104NW, serial number 34-8133059, had stainless steel control cables installed during its manufacture. The bulletin stated, “Service reports have been received stating that stainless steel cables in the aircraft control system have a considerably shorter service life as compared to galvanized cables for the same application.” The service bulletin stated that it was mandatory to inspect and maintain the control system cables in accordance with the FAA Advisory Circular (AC) 41.13. On July 11, 2001, the FAA issued Special Airworthiness Information Bulletin (SAIB) No. CE-01-30. The SAIB recommended that owners or operators of the affected aircraft perform an inspection and possible replacement of the stainless steel cables as outlined in the Piper SB-1048. The FAA recommended that the inspections be accomplished at each 100-hour or annual inspection. FAA AC-41.13, “Acceptable Methods, Techniques and Practices – Aircraft Inspection and Repair,” stated that the inspection and repair of control cables should be accomplished at annual inspections and during 100-hours inspections. It stated that a cloth should be passed over the cable to snag on broken wires. The aircraft maintenance logbooks indicated that the last annual maintenance inspection was conducted on March 18, 2010. The total time on the airframe at the time of the inspection was 7,240.2 hours. The airplane had flown about 17 hours since the last annual inspection. The logbook entry 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.

Flight

Event TypeAccident
Event Time18:20 CDT
Nearest AirportAnkeny Regional Airport (0nm)
Runway36
Runway Length5500 ft
Runway Width100 ft
Flight Plan FiledIFR
Flight Plan ActivatedYes
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-34-220T
Tail NumberN104NW
Aircraft CategoryAir
DamageSubstantial
OperatorMclaughlin John H
Operating RulePart 91
Engines2
Engine TypeReciprocating
Engine DetailsCont Motor · TSIO-360 SER · Reciprocating · 220 | Cont Motor · TSIO-360 SER · Reciprocating · 225
Seats6

People & Injuries

Injury SummaryNo injuries (3 uninjured)
Fatal0
Serious0
Minor0
Uninjured3
Total3
Crew 1Age 72 · Second Class · None

Conditions

ConditionsVMC
LightDaylight
Wind330° @ 12 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point50
Altimeter29.93 inHg
Observation Time23:00
Weather SourcePILO

Appendix: Source Data