- Date
- April 7, 2011, 11:45 local (16:45 UTC)
- Place
- Oklahoma City, OK
- Injuries
- 2 uninjured
- Damage
- Substantial damage
- Phase of flight
- Takeoff
- Aircraft
- N31407Piper PA-32-300
- Defining event
- Takeoff: Flight control sys malf/fail
- Weather
- Visual (VMC) · Day
- Status
- Completed · report December 27, 2011
- Report
- Approved by Office Director
- NTSB office
- Central Region
- Parties
- FAA-Oklahoma City FSDO
- FAA report
- 20110407005179A
- Case key
- 78810
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
Probable cause
The loss of aircraft control due to the failure of the stabilator control cable turnbuckle.
Findings · 3
NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.
Sequence of events
The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.
Analysis
The airplane nosed over shortly after takeoff and impacted the runway. The nose landing gear collapsed and the airplane sustained substantial damage to the firewall. A postaccident examination revealed that a stabilator control cable had failed at a turnbuckle as a result of stress corrosion cracking, which compromised the pilot's ability to control the pitch attitude of the airplane. The airplane was within the maintenance inspection requirements at the time of the accident, with the most recent annual inspection being completed about 1 year prior to the accident. The airplane service manual included a special control cable fitting inspection for airplanes in service 15 years or more. Any evidence of corrosion or cracking was cause for replacement according to the service manual. The accident pilot had owned the airplane for about 26 years. During the time he owned the airplane, the control cables had not been replaced. The investigation could not determine when the stress corrosion cracking commenced on the turnbuckle.
Factual narrative
On April 7, 2011, about 1140 central daylight time, a Piper PA-32-300, N31407, nosed over shortly after takeoff and impacted the runway. The airplane had just lifted off from runway 17 (5,001 feet by 100 feet, concrete) at Sundance Airport (HSD), Oklahoma City, Oklahoma. The pilot and passenger were not injured. The nose landing gear collapsed and the airplane sustained substantial damage to the firewall during the accident sequence. The aircraft was registered to and operated by the pilot under the provisions of 14 Code of Federal Regulations Part 91 as a personal flight. Visual meteorological conditions prevailed for the flight, which was operated without a flight plan. The flight originated from HSD about 1130. The pilot informed Federal Aviation Administration inspectors that he was performing takeoffs and landings (touch and goes) at the time of the accident. He stated that upon completion of the second touch and go, about 15 feet above ground level during the initial climb after lifting off, the nose of the airplane pitched down abruptly. The nose landing gear contacted the runway, followed immediately by the main landing gear. The airplane bounced and momentarily became airborne again. When it impacted the runway again, the nose landing gear collapsed. The airplane veered to the left and came to rest in the grass area adjacent to the runway. A postaccident examination revealed that a stabilator control cable had failed at a turnbuckle as a result of stress corrosion cracking. The airplane was within the maintenance inspection requirements at the time of the accident, with the most recent annual inspection being completed approximately 1 year prior to the accident. The airplane service manual included a special control cable fitting inspection for airplanes in service 15 years or more. Any evidence of corrosion or cracking was cause for replacement according to the service manual. The accident pilot had owned the airplane for approximately 26 years. During the time he owned the airplane, the control cables had not been replaced.
Aircraft
- Registration
- N31407
- Reported as
- Piper PA-32-300
- Category
- Airplane
- Serial number
- 32-7840130
- Airframe hours
- 3,051
- Engine
- Lycoming IO-540 SER, 300 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Personal · Part 91
- Airworthiness certificate
- Standard, Normal
- Last inspection
- Annual · April 5, 2010 · 22 hours before
- Departed
- HSD · Oklahoma City, OK
- Destination
- HSD · Oklahoma City, OK
- Airport
- HSD · Sundance, runway 17, 5,001 × 100 ft, concrete
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot
- Age
- 59
- Injuries
- None
- Certificate
- Commercial
- Airplane ratings
- Single-engine land, Multi-engine land
- Instrument ratings
- Airplane
- Medical
- Class 3, With waivers/limitations
- Last flight review
- October 19, 2010
- Seat
- Left
- Flight hours
- 3,620 total · 1,720 in this make and model · 3,518 as pilot in command · 7 in the last 90 days · 3 in the last 30 days · 1 in the last 24 hours
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- 200° at 9 knots
- Visibility
- 6 statute miles
- Lowest ceiling
- None
- Temperature
- 70 °F, dew point 48 °F
- Altimeter
- 29.72 inHg
- Observed at
- PWA, 5 nm away
Docket · 9
The files NTSB released with the investigation on November 14, 2011, on NTSB’s docket system: statements, records, photos and specialists’ reports. 2.1 MB in all.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.
Other investigations on N31407 · 1
Matched to the same aircraft by N-number and date.