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

Piper PA22 accident near Cortland, New York, July 13, 2020

On July 13, 2020 at about 1:45 pm local time, a 1957 Piper PA22, registered N2716P, was substantially damaged in an accident during takeoff near Cortland, New York (Cortland County-Chase Field). It was a personal flight under general aviation rules (Part 91). 1 person had minor injuries; 1 other was unhurt. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The mechanic’s incorrect rigging of the aileron control cables, which resulted in a reversal of aileron control inputs applied by the pilot during the takeoff. Also causal was the mechanic’s inadequate post-maintenance inspection and the pilot's inadequate preflight inspection and before takeoff check, which failed to detect the misrigging.

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

What the record shows

Date
July 13, 2020 · about 1:45 pm local time · cases in 2020
Place
Cortland, New York · Cortland County-Chase Field · cases near this airport · map
Type
Accident
Injuries
1 person had minor injuries; 1 other was unhurt.
Weather
visual conditions (good weather)
Aircraft
Piper PA22 150, built 1957 · all PA22s on the register
Registration
N2716P · registry record · serial 22-5280
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot was performing a post-maintenance test flight after a "lengthy restoration" of the airplane had been completed by a mechanic, who accompanied him on the flight. After takeoff, the airplane did not respond in accordance with the pilot’s control inputs, so he elected to immediately land the airplane. The airplane impacted the ground off the departure end of the runway, which resulted in substantial damage to the wings and fuselage. Post-accident examination of the airplane revealed that the aileron control cables had been rigged opposite of the proper orientation prescribed in the airplane’s illustrated parts catalog. Both the pilot and the mechanic stated that when they conducted flight control checks prior to the flight, they confirmed deflection of the ailerons, but that they each failed to confirm that the aileron deflection corresponded correctly to the input at the control yoke.

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. Preflight or dispatch event during prior to flight
  3. Flight control sys malf/fail during takeoff defining event
  4. Collision with terrain or object (not controlled flight into terrain) during emergency descent

The NTSB's findings

  • cause Aircraft › Aircraft systems › Flight control system › Aileron control system › Incorrect service/maintenance other cases naming the flight controls
  • cause Personnel issues › Task performance › Maintenance › Installation › Maintenance personnel
  • cause Personnel issues › Task performance › Inspection › Preflight inspection › Pilot
  • Personnel issues › Task performance › Inspection › Post maintenance inspection › Maintenance personnel

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 787 hours in all; 188 in this make and model; 18 in the last 90 days; 7 in the last 30 days; 733 as pilot in command
  • Last flight review: April 25, 2020
  • Medical certificate: None
  • Seat: left
  • Injury: minor injuries

Pilot-Rated Passenger

  • Certificate: private
  • Ratings: single-engine sea
  • Medical certificate: Class 3
  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 4,065.8 hours
  • Last inspection: annual inspection, July 13, 2020
  • Maximum gross weight: 1,950 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-320-A2B (piston); 4,066 hours total

The flight

  • Departed from: N03 Cortland NY at 1:35 pm
  • Destination: N03 Cortland NY
  • Flight plan: none
  • Runway 24, 3,400 ft by 75 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 310° at 8 knots
  • Visibility: 10 statute miles
  • Sky: scat at 2,500 ft
  • Temperature: 72°F (22°C), dew point 64°F (18°C)
  • Altimeter: 29.87 inHg
  • Observation at 1:45 pm from KITH, 13 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

Photographs from the investigation 4 pictures from the NTSB's docket, as the NTSB released them

The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.

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

6 documents, released by the NTSB on February 11, 2021. 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 N2716P the same tail number, which may have belonged to a different aircraft at the time

1999-05-03NYC99LA105 · accident near Oswego, NY · substantial damage · serious 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/ERA20CA246.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.