# NTSB ATL04IA028: Piper PA-32RT-300T, N39541, Fayetteville, NC, October 25, 2003

- Type: NTSB incident investigation
- Classification: Incident · No injuries · Incident investigation · Final report
- Date: October 25, 2003, 11:15 local (15:15 UTC)
- Place: Fayetteville, NC
- Coordinates: 34.984165, -78.866668
- Nearby events: https://openairdocs.org/map.md?lat=34.9842&lon=-78.8667&mi=10
- Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping)
- Highest injury: No injuries
- Injuries: 1 uninjured
- Status: Completed, report July 7, 2005
- Report: Approved by Office Director
- Parties: Greensboro FSDO
- NTSB case key (mKey): 58289
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ATL04IA028
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/58289/pdf
- Page: https://openairdocs.org/ntsb/ATL04IA028

## Probable cause

Flight control elevator attachment turnbuckle corrosion and fracture resulting in the loss of aircraft control in flight.

## Sequence of events

In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf).

- Airframe/component/system failure/malfunction, takeoff
  - flt control syst,elevator control cable/rod - corroded (cause)
- Forced landing, descent - emergency
- Loss of control - in flight, landing
  - elevator - unavailable
  - aircraft control - restricted
- Nose gear collapsed, landing - flare/touchdown
  - landing gear,nose gear - overload

## Analysis

According to the pilot after liftoff the elevator flight control became unresponsive and he could only control pitch with the elevator trim. The pilot flew to Fayetteville Regional Airport where he requested the longest runway for an emergency landing. During the landing flare, the nose dropped when the pilot reduced engine power, and the nose wheel collided with the runway and collapsed. Examination of the airframe revealed that the left elevator cable assembly turnbuckle was corroded and fractured.  A review of maintenance records showed that the failed assembly had a total time of 2,633 hours and had been in service for 25 years

## Factual narrative

On October 25, 2003, at 1115 eastern daylight time, a Piper PA-32RT-300T, N39541, registered to and operated by a private pilot, nose wheel collapsed during emergency landing on runway 4 at Fayetteville Regional Airport, Fayetteville, North Carolina. The personal flight operated under the provisions of Title 14 CFR Part 91 with no flight plan filed. Visual weather conditions prevailed at the time of the incident. The airplane sustained minor damage, and the pilot was not injured. The flight departed Graves Creek Airport, Fayetteville, North Carolina, at 1110, on October 25, 2003.

According to the pilot after liftoff the elevator flight control became unresponsive and he could only control pitch with the elevator trim. The pilot flew to Fayetteville Regional Airport where he requested the longest runway for an emergency landing. During landing flare, the nose dropped when the pilot reduced engine power, and the nose wheel collided with the runway and collapsed.

Examination of the airplane revealed that the wreckage debris was scattered in the immediate vicinity of the wreckage. The airplane came to rest on a 040 degree magnetic heading approximately one third from the runway threshold. Examination of the airframe revealed that the left elevator cable assembly turnbuckle was broken at the MS21260S4LH cable terminal end. The terminal failed in the shank portion beneath the 0.040 safety wire wraps with only the safety wire maintaining the integrity between the turnbuckle assembly and the cable terminal end. The MS21260 flight control cable terminal on the opposite end of the turnbuckle also revealed evidence of corrosion.

The Piper Lance II Service Manual states "Check aileron, rudder, stabilator trim cables, turnbuckles, guides and pulleys for safety, damage and operation". The Piper recommended inspection times are every 100, 500, and 1000 hours of flight time.  A review of maintenance records showed that the failed assembly had a total time of 2,633 hours but had been in service for 25 years.

## Aircraft

- Registration: [N39541](https://openairdocs.org/aircraft/N39541), registered now, S/N 32R-7887104, built 1978 (OpenAirDocs)
- Reported make and model: Piper PA-32RT-300T
- Registry model: [Piper PA-32RT-300T](https://openairdocs.org/model/piper-pa-32rt-300t) (registry code 7103216) (OpenAirDocs)
- Registry engine: [Lycoming TI0-540 series](https://openairdocs.org/engine/lycoming-ti0-540-series) (registry code 41533, turbo-prop) (OpenAirDocs)
- Category: Airplane
- Serial number: 32R7887104
- Airframe hours: 2630
- Engines: Lycoming TIO-540-51AO 300 horsepower reciprocating
- Damage: Minor damage
- Flight: Personal, Part 91
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, June 12, 2003, 15 hours before
- Departed: 26C, Fayetteville, NC
- Destination: FAY, Fayetteville, NC
- Airport: FAY, Fayetteville Regional, runway 4, 7,204 × 150 ft, asphalt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 59; injuries: none; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; last flight review June 15, 2002; seat: left; flight hours: 5,100 total, 4,800 in this make and model, 5,100 as pilot in command, 5 in the last 90 days, 3 in the last 30 days, 1 in the last 24 hours

## Weather

- Conditions: Visual (VMC), Day
- Wind: 80° at 7 knots
- Visibility: 10 statute miles
- Lowest ceiling: 1,400 ft broken
- Temperature: 63 °F, dew point 54 °F
- Altimeter: 30.35 inHg
- Observed at: FAY

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Incident 20031025031429I](https://openairdocs.org/incident/20031025031429I), Oct 25, 2003: Piper PA32RT300T, Fayetteville, NC, Minor damage. (-23) The pilot departed grays creek airport (2GC) for a short flight to a nearby airport. Upon rotation he noticed that the aircraft seemed to "jump" off of…

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.
