ERA21FA224 · Piper PA-31P
Piper PA-31P · Accident: system/component malfunction/failure (non-power) on approach
From Myrtle Beach International Airport (MYR) to Grand Strand Airport (CRE)
Event
- NTSB case
- ERA21FA224
- 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
- 1 · all aircraft and ground
- Ground fatalities
- 0
- 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-31P
- Aircraft type
- Piper PA-31
- 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
- N575BC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Myrtle Beach International Airport (MYR), Myrtle Beach, SCTo Grand Strand Airport (CRE), North Myrtle Beach, SC
- Aircraft age
- About 44 years (built 1977)
- 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
- Approach · VFR pattern downwind
- 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
- System/component malfunction/failure (non-power)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Aircraft › Aircraft systems
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The accident flight was the first flight after an annual inspection during which all flight control surfaces were removed, repainted, and reinstalled. After departure, the pilot reported that he needed to return to the runway. The airplane’s altitude fluctuated between 1,000 ft and 450 ft mean sea level before radar contact was lost. Examination of the engines and propellers revealed no mechanical failures or anomalies that would have precluded normal operation. Examination of the airframe revealed that the elevator trim tabs were installed upside-down and reversed, which would have resulted in the tabs moving opposite of the intended direction. A command from the cockpit controls for nose-up trim would result in the tabs moving in the airplane nose-down direction and vice versa. As found, both trim tabs were deflected trailing edge up, which corresponded to a nose-down trim setting. The mechanic who approved the airplane to be returned to service stated that, after the control surfaces were reinstalled, he examined the primary flight controls for proper movement but did not verify proper movement of the elevator trim tab. Although the control surfaces were tagged with labels as they were removed, those labels likely did not remain attached throughout the painting process, which contributed to their improper reinstallation. The maintenance facility also maintained a different version of the accident airplane, which was designed with the elevator trim tab control rod and control horn positioned on the bottom of the trim tab. It is possible that the mechanic may have thought the trim tab installation on the accident airplane was the same, which could explain why the mechanic inadvertently installed the elevator trim tabs in reverse. Although the illustrated parts catalog (IPC) warned in the introduction section that the IPC should not be used for rigging and installation purposes, a figure on a subsequent page of the IPC incorrectly depicted the elevator trim tab control horn positioned on the bottom side of the elevator trim tab. Had the mechanic referred to this figure, it may have contributed to the incorrect installation of the trim tabs.
It is likely that the pilot applied nose-up trim during takeoff, and subsequently experienced nose-down trim forces due to the improper installation of the trim tab. After 2 minutes of flight, the pilot was unable to maintain control of the airplane, possibly due to the unexpected control forces, which resulted in a rapid descent and collision with terrain. Toxicology testing detected ethanol in the pilot’s liver (0.225 and 0.078 gm/hg) and muscle tissue (0.144 gm/hg). Another postmortem microbial product, propanol, was detected in his liver tissue by one laboratory and in muscle tissue by a second laboratory. When consumed, ethanol distributes quickly and uniformly to body tissues based on water content. One would expect the concentrations in the two liver tissue samples to be similar and the concentrations in liver and muscle tissue to be similar as well. Given the different ethanol tissue concentrations, the state in which the body was recovered, and the presence of n-propanol in liver and muscle tissue, it is likely that the identified ethanol was from sources other than ingestion. Thus, the identified ethanol did not contribute to this accident.
Probable cause
The mechanic’s inadvertent installation of the elevator trim tabs in reverse, which resulted in the pitch trim system operating opposite of the pilot’s input and the pilot’s subsequent loss of control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA21FA224
- Event ID
- 20210522103126
- Case number
- ERA21FA224
- 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, 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: 5bb045d21352302415ae2d92527f60a4dd85cace4c9c29aa7d12d8754a4637f8; retrieved 2026-09-15T07:28:37.409Z.