ERA20CA251 · Piper PA 22 150
Piper PA 22 150 · Accident: runway excursion during landing
From Fuquay Airport / Angier Field (78NC) to Fuquay Airport / Angier Field (78NC)
Event
- NTSB case
- ERA20CA251
- 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 150
- 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
- N1520P
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Fuquay Airport / Angier Field (78NC), Fuquay Varina, NCTo Fuquay Airport / Angier Field (78NC), Fuquay Varina, NC
- Aircraft age
- About 66 years (built 1954)
- 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
- Landing · landing roll
- 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
- Runway excursion
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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 › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
As the pilot approached the destination airport for landing, he felt that the elevator trim was not working properly. He elected to return to the 2,780-ft-long grass runway at his home airport. While approaching the airport he continued his attempts to adjust the pitch trim, to no avail. He further reported that even after his attempts to adjust the elevator trim, it felt as if there was too much nose down trim, as he had to maintain back pressure on the yoke to keep the wings level. As the approach continued, he felt that he could not slow the airplane down or descend enough and entered a slip. The airplane landed “long and fast,” and the brakes were not effective due to the damp grass. The airplane departed the end of the runway and the right wing was substantially damaged after it impacted a tree. After the accident, the pilot stated that he adjusted the elevator trim and the system seemed to work properly.
Probable cause
The pilot's failure to attain a proper approach speed, which resulted in an overrun of the wet grass runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA20CA251
- Event ID
- 20200716X10938
- Case number
- ERA20CA251
- 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, cause areas. 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: f7547d8c27d0357761d04635a9007f0cea0b43629e9aa7ccf5decb21e0f41b0f; retrieved 2026-09-16T12:09:54.756Z.