CEN12LA146 · Piper PA-22-135
Piper PA-22-135 · Accident: loss of control in flight during initial climb
From Sheridan Municipal Airport (9M8) to Sheridan Municipal Airport (9M8)
Event
- NTSB case
- CEN12LA146
- 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 PA-22-135
- Aircraft type
- Piper PA-22
- 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
- N2677A
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Sheridan Municipal Airport (9M8), Sheridan, ARTo Sheridan Municipal Airport (9M8), Sheridan, AR
- Aircraft age
- Not recorded
- 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
- Initial climb
- 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
- Loss of control in flight
- 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 oper/perf/capability
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that the takeoff was normal until the airplane was climbing through about 200 feet above the ground, at which time he observed that the passenger suddenly tensed up. The pilot said he was then unable to move the rudder pedals because the passenger was stepping on the passenger-side rudder controls. The airplane skewed to the left, descended, and impacted terrain on the left side of the runway. A postaccident examination confirmed flight control continuity and revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation.
The passenger reported this was his first flight ever in any aircraft. He also reported that he was not pressing on the rudder pedals. However, given the pilot’s experience in the accident airplane and the lack of evidence of a preimpact anomaly, it is likely that the passenger did inadvertently interfere with the rudder pedals.
Probable cause
The passenger’s interference with the flight controls during the initial climb, which resulted in a loss of control and impact with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN12LA146
- Event ID
- 20120131X20200
- Case number
- CEN12LA146
- 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, coordinates. 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: 03063e84d9cfb0d9f1cfbbdecec9a4eca7df5781af485fd9bbcacc35e417d51a; retrieved 2026-09-15T17:08:18.536Z.