ERA21LA183 · Piper PA-28-140
Piper PA-28-140 · Accident: system/component malfunction/failure (non-power) on approach
From Front Royal Warren County Airport (FRR) to Shenandoah Valley Regional Airport (SHD)
Event
- NTSB case
- ERA21LA183
- 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
- Event fatalities
- Unknown
- 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-28-140
- Aircraft type
- Piper PA-28
- 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
- N7242F
- Operator
- Djair
- Onboard fatalities
- Unknown
- Route
- From Front Royal Warren County Airport (FRR), Front Royal, VATo Shenandoah Valley Regional Airport (SHD), Weyers Cave, VA
- Aircraft age
- About 53 years (built 1968)
- 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 go-around
- 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
- 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 reported that, while landing, less than 100 ft above ground level, he felt that the approach was unstable and decided to go around. He smoothly applied full engine power, but the airplane did not gain any altitude and started banking hard to the left. He stated that the airplane was to the left of the runway and that he was applying right aileron and right rudder to level the wings with no effect. The airplane subsequently impacted a fence and trees. The pilot was seriously injured, his passenger received minor injuries, and the airplane was substantially damaged. Examination of the airplane revealed that the rudder bar arm and rudder pedal tube, which were part of the rudder control assembly, had separated near a weld, which displayed a crack where extensive corrosion was visible on the fracture surface. Examination under magnification revealed that the fracture of the rudder arm began with an unknown overload event, and crack growth had occurred slowly. As the crack developed, the fracture surfaces fretted against each other until the crack grew enough to cause the left and right fracture surfaces at the base of the weld to the rudder tube to fail as a hinge point, causing a cup-and-cone failure with fresh substrate at the base of the fracture surface. The airplane had accrued about 11,406 hours as of its most recent 100-hour inspection, which was completed about 3 months before the accident. A review of manufacturer’s published guidance revealed multiple documents that included inspection requirements for the rudder pedals, rudder bar, and rudder bar support assembly, which were readily accessible by maintenance personnel for visual inspection. Review of the airplane maintenance records did not reveal any entries that referenced any of the published inspection requirements for the rudder pedals, rudder bar, and rudder bar support assembly. Even without rudder control, the airplane likely remained controllable; however, given the 6-knot right crosswind that existed at the time of the accident, and the airplane’s proximity to the ground when the failure occurred, it is likely that the failure of the rudder control assembly resulted in the pilot’s loss of control.
Probable cause
Maintenance personnel’s inadequate inspection of the rudder control system, which resulted in failure of the rudder control assembly and the pilot’s loss of control during a go-around.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA21LA183
- Event ID
- 20210413102905
- Case number
- ERA21LA183
- 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: d8232c69db6d705ac44516a16fa303187f0cafcfa9ebeb3da9b4543b2c2fc253; retrieved 2026-09-16T13:56:41.634Z.