The U.S. aircraft register, updated daily
Accidents · NTSB ERA14LA015 · Final report

Piper PA-22-135 accident near Selinsgrove, Pennsylvania, October 4, 2013

On October 4, 2013 at about 6:20 pm local time, a 1953 Piper PA-22-135, registered N170JH, was substantially damaged in an accident during takeoff near Selinsgrove, Pennsylvania (Penn Valley Airport). It was a personal flight under general aviation rules (Part 91). 2 people were seriously injured. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
October 4, 2013 · about 6:20 pm local time · cases in 2013
Place
Selinsgrove, Pennsylvania · Penn Valley Airport · cases near this airport · map
Type
Accident
Injuries
2 people were seriously injured.
Weather
visual conditions (good weather)
Aircraft
Piper PA-22-135, built 1953 · all PA-22-135s on the register
Registration
N170JH · no longer on the register · serial 22-1645
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Aircraft maintenance event during prior to flight
  2. Aircraft inspection event during prior to flight
  3. Sys/Comp malf/fail (non-power) during takeoff defining event
  4. Loss of control in flight during takeoff
  5. Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent

The NTSB's findings

  • cause Aircraft › Aircraft systems › Flight control system › Elevator control system › Incorrect service/maintenance other cases naming the flight controls
  • cause Personnel issues › Task performance › Maintenance › Replacement › Maintenance personnel
  • cause Personnel issues › Task performance › Inspection › Post maintenance inspection › Maintenance personnel
  • cause Personnel issues › Action/decision › Action › Lack of action › Pilot
  • cause Aircraft › Aircraft systems › Flight control system › Elevator control system › Inadequate inspection other cases naming the flight controls
  • cause Personnel issues › Task performance › Inspection › Post maintenance inspection › Pilot

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 9,999 hours in all; 9,999 in this make and model
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: left
  • Injury: serious injuries

The aircraft

  • Airframe total time: 3,426 hours
  • Last inspection: annual inspection, August 22, 2013
  • Maximum gross weight: 2,000 lb
  • Landing gear: fixed
  • Engine: Lycoming O-290 SERIES (piston); 0 hours total

The flight

  • Departed from: SEG Selinsgrove PA at 6:20 pm
  • Destination: SEG Selinsgrove PA
  • Flight plan: none
  • Runway 17, 4,760 ft by 75 ft

Weather at the time

  • Light: daylight
  • Wind: at 5 knots
  • Visibility: 10 statute miles
  • Sky: scat at 3,800 ft
  • Temperature: 81°F (27°C), dew point 66°F (19°C)
  • Altimeter: 30.02 inHg
  • Observation at 6:53 pm from SEG

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

12 documents, released by the NTSB on September 16, 2014. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Other NTSB records under N170JH the same tail number, which may have belonged to a different aircraft at the time

2010-04-24ERA10CA245 · accident near Hoensdale, PA · substantial damage · no injuries

Connections how this case links to the rest of the register

Aircraft
Place
Record

The whole map of how records connect · these connections as data: /graph/accident/ERA14LA015.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.