# NTSB ERA14LA015: Piper PA-22-135, N170JH, Selinsgrove, PA, October 4, 2013 - Type: NTSB accident investigation - Classification: Accident · Serious injuries · Limited investigation · Final report - Date: October 4, 2013, 14:20 local (18:20 UTC) - Place: Selinsgrove, PA - Coordinates: 40.820835, -76.863891 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=40.8208&lon=-76.8639&mi=10 - Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping) - Defining event: [Takeoff: Sys/Comp malf/fail (non-power)](https://openairdocs.org/ntsb-events/330) - Highest injury: Serious injuries - Injuries: 2 serious - Status: Completed, report October 27, 2014 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 88271 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA14LA015 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/88271/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=88271 - Page: https://openairdocs.org/ntsb/ERA14LA015 ## Probable cause The incorrect (reverse) rigging of the elevator cables by maintenance personnel and their subsequent failure to verify that the rigging was correct during postmaintenance checks and the pilot's inadequate preflight check. ## 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 · Incorrect service/maintenance (probable cause); cases with it: [Piper PA-22-135, 1 case](https://openairdocs.org/ntsb-findings/01022730/cases.md?model=7102206), [All aircraft, 74 cases](https://openairdocs.org/ntsb-findings/01022730/cases.md) - [Maintenance: replacement](https://openairdocs.org/ntsb-findings/02062020): Personnel issues › Task performance · Maintenance personnel (probable cause); cases with it: [Piper PA-22-135, 1 case](https://openairdocs.org/ntsb-findings/02062020/cases.md?model=7102206), [All aircraft, 70 cases](https://openairdocs.org/ntsb-findings/02062020/cases.md) - [Inspection: post maintenance inspection](https://openairdocs.org/ntsb-findings/02061515): Personnel issues › Task performance · Maintenance personnel (probable cause); cases with it: [Piper PA-22-135, 1 case](https://openairdocs.org/ntsb-findings/02061515/cases.md?model=7102206), [All aircraft, 57 cases](https://openairdocs.org/ntsb-findings/02061515/cases.md) - [Action: lack of action](https://openairdocs.org/ntsb-findings/02041030): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Piper PA-22-135, 1 case](https://openairdocs.org/ntsb-findings/02041030/cases.md?model=7102206), [All aircraft, 792 cases](https://openairdocs.org/ntsb-findings/02041030/cases.md) - [Flight control system: elevator control system](https://openairdocs.org/ntsb-findings/01022730): Aircraft › Aircraft systems · Inadequate inspection (probable cause); cases with it: [Piper PA-22-135, 1 case](https://openairdocs.org/ntsb-findings/01022730/cases.md?model=7102206), [All aircraft, 74 cases](https://openairdocs.org/ntsb-findings/01022730/cases.md) - [Inspection: post maintenance inspection](https://openairdocs.org/ntsb-findings/02061515): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Piper PA-22-135, 1 case](https://openairdocs.org/ntsb-findings/02061515/cases.md?model=7102206), [All aircraft, 57 cases](https://openairdocs.org/ntsb-findings/02061515/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Prior to flight: Aircraft maintenance event](https://openairdocs.org/ntsb-events/040); cases with it: [Piper PA-22-135, 2 cases](https://openairdocs.org/ntsb-events/040/sequence.md?model=7102206), [All aircraft, 484 cases](https://openairdocs.org/ntsb-events/040/sequence.md) - [Prior to flight: Aircraft inspection event](https://openairdocs.org/ntsb-events/050); cases with it: [Piper PA-22-135, 1 case](https://openairdocs.org/ntsb-events/050/sequence.md?model=7102206), [All aircraft, 229 cases](https://openairdocs.org/ntsb-events/050/sequence.md) - [Takeoff: Sys/Comp malf/fail (non-power)](https://openairdocs.org/ntsb-events/330) (defining event); cases with it: [Piper PA-22-135, 1 case](https://openairdocs.org/ntsb-events/330/sequence.md?model=7102206), [All aircraft, 994 cases](https://openairdocs.org/ntsb-events/330/sequence.md) - [Takeoff: Loss of control in flight](https://openairdocs.org/ntsb-events/240); cases with it: [Piper PA-22-135, 9 cases](https://openairdocs.org/ntsb-events/240/sequence.md?model=7102206), [All aircraft, 5,002 cases](https://openairdocs.org/ntsb-events/240/sequence.md) - [Uncontrolled descent: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Piper PA-22-135, 17 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=7102206), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The pilot reported that, during takeoff, he applied full throttle and that, when the airplane began to gain airspeed, he pushed the yoke forward to bring the tailwheel off the runway. The tail did not rise, and the airplane subsequently "jumped" off the runway; the pilot pushed the yoke forward again, but the airplane continued to climb. The pilot then decreased the engine power, the airplane's nose lowered, and the pilot pulled back on the yoke to arrest the descent, but the nose did not rise. The airplane continued to descend at a higher rate, and the pilot applied nose-up trim; however, the airplane subsequently impacted the runway. Examination of the airplane maintenance logbooks revealed that the accident flight was the first flight after an annual inspection had been completed and that the elevator control cables were replaced during the inspection. Examination revealed that the elevator control cables were installed incorrectly and moved the elevators in the direction opposite to that commanded: when the pilot pushed the yoke forward, the airplane climbed, and, when the pilot pulled the yoke aft, the airplane descended. It is likely that the maintenance personnel installed the flight control cables incorrectly and failed to verify that the routing from the elevator cables to the control yoke was correct during the recent annual inspection and postmaintenance check. It is also likely that the pilot failed to perform an adequate preflight check, which required the pilot to verify that all controls were in the proper position. ## Factual narrative On October 4, 2013, about 1420 eastern daylight time, a Piper PA-22, N170JH, impacted the runway immediately after takeoff from Penn Valley Airport (SEG), Selinsgrove, Pennsylvania. The private pilot and passenger sustained serious injuries. The airplane was operated under the provisions of Title 14 Code of Federal Regulations Part 91 and no flight plan had been filed. Visual meteorological conditions prevailed for the personal local flight, which was originating at the time of the accident. According to the pilot, he completed the before takeoff checklist, which included a flight control check of the tailwheel equipped airplane; however, he could not see the elevator from the pilot seat. He taxied the airplane onto the runway, applied full throttle, and when the airplane began to gain airspeed, he pushed the yoke forward in order to bring the tailwheel off the runway. The airplane departed the runway, the pilot pushed the yoke forward again, but the airplane continued to climb at a "low airspeed." The pilot decreased the engine power, the nose of the airplane lowered, and the pilot pulled back on the yoke to arrest the descent. The airplane responded by descending at a higher rate, the pilot applied nose-up trim; however, the airplane impacted the runway. The pilot did not recall any events after the airplane impacted the runway. According to a witness, he saw the airplane taxiing on the parallel taxiway, then enter the runway without stopping, and begin the takeoff roll. Immediately after the main landing gear departed the runway, the airplane "went into a vertical climb." Then, above the runway, the nose of the airplane dropped, and it descended vertically in a slight left turn. The airplane impacted the runway, which resulted in substantial damage to the wings and fuselage. According to the airplane maintenance logbooks, the annual inspection was recorded on August 22, 2013, at a total time of 3425.6 hours. The airframe maintenance records indicated that the left hand and right hand elevator cables were replaced at that time. A postaccident examination of the airplane revealed that the tachometer in the airplane indicated a total time of 3425.9 hours. In an interview with the mechanics that performed the annual maintenance, they stated that during the annual inspection the mechanics decided to replace the elevator cables since they were frayed. The mechanics routed the new cables in with the part tags attached and a second mechanic confirmed the cable installation. Then, they performed a flight control check utilizing the control column to confirm the correct installation of the elevator cables. Once checking the airplane, one of the mechanics noticed that a bolt was too short, removed, one cable, replaced the bolt with a longer bolt, and reattached the elevator cable. When asked if they verified the cable rigging, both mechanics stated that they confirmed the correct routing from the elevator cables to the control yoke. In addition, theystated there was no maintenance manual for the airplane and they used the illustrated parts catalog in order to install the cables. Examination of the airplane by a Federal Aviation Administration inspector revealed that the elevator control cables moved the opposite direction as commanded. When the elevator control cable was operated that corresponded to the yoke being pushed forward, the elevator control surface moved in the upward direction or positioned the airplane in a nose up attitude. When the elevator control cable was operated that corresponded to the yoke being pull aft, the elevator control surface moved downward or positioned the airplane in a nose down attitude. In the operating instructions for the airplane, under the section labeled "Preflight," it stated that "upon entering the plane, the pilot should ascertain that all controls operate normally and are in proper position and that the door is closed and latched." In the "Maintenance" section of the PA-22 Owners' Handbook, it stated in the "Leveling and Rigging" section that "In rigging the control system of the Tri-Pacer, this procedure should be followed: (1) Center the nose wheel, rudder pedals, rudder and ailerons with the interconnecting cables slack at turnbuckles, located behind the baggage compartment. (2) Check the airplane in flight for proper trim with the interconnecting cables slack. (3) During the flight check, if ailerons do not line up with the flap trailing edges equally, adjust the aileron tab to obtain proper aileron position." In addition, the Piper Tri-Pacer Inspection Report, section "D. Fuselage and Empennage Group" task No. 9 of stated to "inspect rudder, elevator and stabilizer trim cables, turnbuckles, guides and pulleys for safety, damage, corrosion and operation." ## Aircraft - Registration: [N170JH](https://openairdocs.org/deregistered/N170JH-2018-05-30), registration cancelled 2018-05-30, S/N 22-1645, built 1953 (OpenAirDocs) - Reported make and model: PIPER PA-22-135 - Registry model: [Piper PA-22-135](https://openairdocs.org/model/piper-pa-22-135) (registry code 7102206) (OpenAirDocs) - Registry engine: [Lycoming 0-290 series](https://openairdocs.org/engine/lycoming-0-290-series) (registry code 41506, 4 cycle) (OpenAirDocs) - Category: Airplane - Serial number: 22-1645 - Year built: 1953 - Airframe hours: 3426 - Engines: LYCOMING O-290 SERIES reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, August 22, 2013 - Departed: SEG, Selinsgrove, PA - Destination: SEG, Selinsgrove, PA - Airport: SEG, Penn Valley Airport, runway 17, 4,760 × 75 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 34; injuries: serious; private; airplane ratings: single-engine land; medical: class 3, without waivers/limitations; seat: left; flight hours: 9,999 total, 9,999 in this make and model ## Weather - Conditions: Visual (VMC), Day - Wind: variable at 5 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 81 °F, dew point 66 °F - Altimeter: 30.02 inHg - Observed at: SEG ## 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 20131004019599A](https://openairdocs.org/incident/20131004019599A), Oct 4, 2013: Piper PA-22-135, Selinsgrove, PA, Substantial damage. As stated by witness: the aircraft departed runway 17, full-length, and initiated a takeoff roll without stopping on the runway. Immediately after lift-off,… ## Other investigations on N170JH (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 ERA10CA245](https://openairdocs.org/ntsb/ERA10CA245), Apr 24, 2010: Piper PA-22-135 (N170JH), Hoensdale, PA, substantial damage. Probable cause: The pilot's improper final approach, resulting in a bounced landing and ground loop. Contributing to the accident was the pilot's lack of experience in tailwheel airplanes. ## Docket (12 files) The files NTSB released with the investigation on September 16, 2014, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=88271. 7.6 MB in all. - Pilot Statements (item 1, .PDF, 291 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40416209&FileExtension=.PDF&FileName=Pilot%20Statements-Redacted.PDF - Witness Statements (item 2, .PDF, 592 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40416210&FileExtension=.PDF&FileName=Witness%20Statements-Redacted.PDF - FAA Examination Video (item 3, .PDF, 97 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40416611&FileExtension=.PDF&FileName=FAA%20Examination%20Video-Master.PDF - Maintenance Records - Excerpts (item 4, .PDF, 911 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40416211&FileExtension=.PDF&FileName=Maintenance%20Records%20-%20Excerpts-Redacted.PDF - Interview with Mechanics - Audio (item 5, .PDF, 97 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40416612&FileExtension=.PDF&FileName=Interview%20with%20Mechanics%20-%20Audio-Master.PDF - Weather Observations SEG (item 6, .PDF, 153 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40416212&FileExtension=.PDF&FileName=Weather%20Observations%20SEG-Master.PDF - PA22 Owners Handbook - Maintenance Excerpt (item 7, .PDF, 418 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40416213&FileExtension=.PDF&FileName=PA22%20Owners%20Handbook%20-%20Maintenance%20Excerpt-Master.PDF - PA22 Service Memo (item 8, .PDF, 920 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40416214&FileExtension=.PDF&FileName=PA22%20Service%20Memo-Master.PDF - PA22 Owners Handbook - Preflight Excerpt (item 9, .PDF, 141 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40416215&FileExtension=.PDF&FileName=PA22%20Owners%20Handbook%20-%20Preflight%20Excerpt-Master.PDF - Google Earth Overview Map of Accident Site (item 10, .PDF, 142 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40416216&FileExtension=.PDF&FileName=Google%20Earth%20Overview%20Map%20of%20Accident%20Site-Master.PDF - Photo 1 - Left Side of Wreckage (Photo Courtesy of FAA) (item 11, .PDF, 1.8 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40416217&FileExtension=.PDF&FileName=Photo%201%20-%20Left%20Side%20of%20Wreckage%20(Photo%20Courtesy%20of%20FAA)-Master.PDF - Photo 2 - Front View of Wreckage (Photo Courtesy of FAA) (item 12, .PDF, 2.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40416218&FileExtension=.PDF&FileName=Photo%202%20-%20Front%20View%20of%20Wreckage%20(Photo%20Courtesy%20of%20FAA)-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.