ERA20CA246 · Piper PA22 150
Piper PA22 150 · Accident: flight control system malfunction/failure during takeoff
From Cortland County Chase Field (N03) to Cortland County Chase Field (N03)
Event
- NTSB case
- ERA20CA246
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Piper PA22 150
- Aircraft type
- Piper PA22
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N2716P
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Cortland County Chase Field (N03), Cortland, NYTo Cortland County Chase Field (N03), Cortland, NY
- Aircraft age
- About 63 years (built 1957)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Takeoff
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Flight control system malfunction/failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft systems
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA20CA246
- Event ID
- 20200713X05400
- Case number
- ERA20CA246
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 49aead4c52bf37203df81b13e5a0ded4a347c663db5e7fc9a2a9fd70e5f14a58; retrieved 2026-09-16T12:05:49.710Z.