# NTSB CEN11LA275: Piper PA-32-300, N31407, Oklahoma City, OK, April 7, 2011 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: April 7, 2011, 11:45 local (16:45 UTC) - Place: Oklahoma City, OK - Coordinates: 35.601943, -97.706108 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=35.6019&lon=-97.7061&mi=10 - Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping) - Defining event: [Takeoff: Flight control sys malf/fail](https://openairdocs.org/ntsb-events/333) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report December 27, 2011 - Report: Approved by Office Director - NTSB office: Central Region - Parties: FAA-Oklahoma City FSDO - NTSB case key (mKey): 78810 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN11LA275 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/78810/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=78810 - Page: https://openairdocs.org/ntsb/CEN11LA275 ## Probable cause The loss of aircraft control due to the failure of the stabilator control cable turnbuckle. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Flight control system: elevator control system](https://openairdocs.org/ntsb-findings/01022730): Aircraft › Aircraft systems · Fatigue/wear/corrosion (probable cause); cases with it: [Piper PA-32-300, 1 case](https://openairdocs.org/ntsb-findings/01022730/cases.md?model=7103212), [All aircraft, 74 cases](https://openairdocs.org/ntsb-findings/01022730/cases.md) - [Flight control system: elevator control system](https://openairdocs.org/ntsb-findings/01022730): Aircraft › Aircraft systems · Failure (probable cause); cases with it: [Piper PA-32-300, 1 case](https://openairdocs.org/ntsb-findings/01022730/cases.md?model=7103212), [All aircraft, 74 cases](https://openairdocs.org/ntsb-findings/01022730/cases.md) - [Performance/control parameters: pitch control](https://openairdocs.org/ntsb-findings/01062022): Aircraft › Aircraft oper/perf/capability · Attain/maintain not possible (probable cause); cases with it: [Piper PA-32-300, 1 case](https://openairdocs.org/ntsb-findings/01062022/cases.md?model=7103212), [All aircraft, 526 cases](https://openairdocs.org/ntsb-findings/01062022/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Takeoff: Flight control sys malf/fail](https://openairdocs.org/ntsb-events/333) (defining event); cases with it: [Piper PA-32-300, 1 case](https://openairdocs.org/ntsb-events/333/sequence.md?model=7103212), [All aircraft, 410 cases](https://openairdocs.org/ntsb-events/333/sequence.md) - [Takeoff: Loss of control in flight](https://openairdocs.org/ntsb-events/240); cases with it: [Piper PA-32-300, 12 cases](https://openairdocs.org/ntsb-events/240/sequence.md?model=7103212), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md) - [Takeoff: Nose over/nose down](https://openairdocs.org/ntsb-events/096); cases with it: [Piper PA-32-300, 2 cases](https://openairdocs.org/ntsb-events/096/sequence.md?model=7103212), [All aircraft, 2,287 cases](https://openairdocs.org/ntsb-events/096/sequence.md) - [Takeoff: Abnormal runway contact](https://openairdocs.org/ntsb-events/090); cases with it: [Piper PA-32-300, 4 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=7103212), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md) - [Takeoff: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Piper PA-32-300, 11 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=7103212), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) - [Post-impact: Landing gear collapse](https://openairdocs.org/ntsb-events/094); cases with it: [Piper PA-32-300, 6 cases](https://openairdocs.org/ntsb-events/094/sequence.md?model=7103212), [All aircraft, 1,787 cases](https://openairdocs.org/ntsb-events/094/sequence.md) ## 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](https://openairdocs.org/aircraft/N31407), registered now, S/N 32-7840130 (OpenAirDocs) - Reported make and model: PIPER PA-32-300 - Registry model: [Piper PA-32-300](https://openairdocs.org/model/piper-pa-32-300) (registry code 7103212) (OpenAirDocs) - Registry engine: [Lycoming IO-540 series](https://openairdocs.org/engine/lycoming-io-540-series) (registry code 41530, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 32-7840130 - Airframe hours: 3051 - Engines: 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 ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 59; injuries: none; 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 ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20110407005179A](https://openairdocs.org/incident/20110407005179A), Apr 7, 2011: Piper PA-32-300, Oklahoma City, OK, Substantial damage. Aircraft performing touch and go's at Sundance Airpark. Upon completion of the second touch and go, with full power in a climb at an altitude of approximately… ## Other investigations on N31407 (1) 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. - [NTSB CEN24LA378](https://openairdocs.org/ntsb/CEN24LA378), Sep 30, 2024: Piper PA32 (N31407), Caro, MI, substantial damage. Probable cause: A total loss of engine power due to maintenance personnel’s failure to properly tighten the fuel supply line B-nut at the fuel servo. ## Docket (9 files) The files NTSB released with the investigation on November 14, 2011, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=78810. 2.1 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 706 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40350697&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Materials Laboratory 15 - Factual Report 11-047 (with 3 embedded images) (item 2, .PDF, 347 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40347186&FileExtension=.PDF&FileName=Materials%20Laboratory%2015%20-%20Factual%20Report%2011-047%20(with%203%20embedded%20images)-Master.PDF - Airplane Maintenance Logbook -- Excerpts (item 3, .PDF, 207 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40357059&FileExtension=.PDF&FileName=Airplane%20Maintenance%20Logbook%20--%20Excerpts-Redacted.PDF - Airplane Service Manual -- Excerpts (item 4, .PDF, 573 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40350698&FileExtension=.PDF&FileName=Airplane%20Service%20Manual%20--%20Excerpts-Master.PDF - Piper Service Letter No. 1069 (item 5, .PDF, 58 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40350703&FileExtension=.PDF&FileName=Piper%20Service%20Letter%20No.%201069-Master.PDF - FAA Information Bulletins CE-02-05/CE-02-05R1 (item 6, .PDF, 53 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40357029&FileExtension=.PDF&FileName=FAA%20Information%20Bulletins%20CE-02-05%2FCE-02-05R1-Master.PDF - FAA Information Bulletin CE-11-01 (item 7, .PDF, 40 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40350701&FileExtension=.PDF&FileName=FAA%20Information%20Bulletin%20CE-11-01-Master.PDF - NTSB Safety Recommendation A-01-06~08 (item 8, .PDF, 36 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40350704&FileExtension=.PDF&FileName=NTSB%20Safety%20Recommendation%20A-01-06~08-Master.PDF - Safety Recommendation History A-01-06~08 (item 9, .PDF, 67 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40357062&FileExtension=.PDF&FileName=Safety%20Recommendation%20History%20A-01-06~08-Master.PDF 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.