FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX04FA167 · Piper PA-38-112

18 Mar 2004 · Jean, NV, United States

Piper PA-38-112 · Accident: loss of control in flight while maneuvering

From Henderson Executive Airport (HND) to an unrecorded destination

Report a problem

Event

NTSB case
LAX04FA167
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
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-38-112

Aircraft type
Piper PA-38
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
N2421D
Operator
Unknown
Onboard fatalities
Unknown
Route
From Henderson Executive Airport (HND), Henderson, NVTo not recorded
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
Maneuvering
First occurrenceThe 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
Destroyed

Cause areas

  • Company maintenance personnel › Maintenance, inspection, inadequate
  • Flt control syst, aileron control cable/rod › Disconnected
  • Flt control syst, aileron control cable/rod › Not safetied
  • Pilot in command › Aircraft control, not attained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane impacted flat desert terrain following an in-flight loss of control. There were no witnesses to the accident. The local solo instructional flight departed about 45 minutes prior to the accident. Recorded radar data indicated that the airplane flew on a southerly course and conducted numerous aerial maneuvers consistent with the type normally practiced during primary flight training. Following the maneuvers, the airplane landed at a nearby uncontrolled airport, then departed again in a northeast direction for 3.8 nm until radar contact was lost. The last radar contact was about 800 feet laterally west of initial impact point, at an above ground altitude of 2,400 feet. The airplane impacted the ground in a steep left bank with a nose low attitude around 30 degrees. The debris field was approximately 100 feet in length, with an energy path opposite in direction to the flight track shown by the recorded radar data. All flight control surfaces were located within the immediate area of the accident site. The right wing separated from the fuselage and was located 30 feet from the fuselage. The right wing aileron balance cable exhibited a tension overload failure inside the right wing. The right wing primary aileron cable was found disconnected at the turnbuckle where it attaches to its corresponding rod end clevis fitting located in the fuselage. The turnbuckle barrel remained attached to the primary cable assembly and the clevis fitting remained attached to the link assembly. The turnbuckle barrel was safety wired on the outboard half that attaches to the primary cable and the safety wire looped back onto itself locking the turnbuckle barrel to the cable. No safety wire or locking device was found on the inboard half of the turnbuckle barrel or clevis fitting. Visual inspection of the threads of both the turnbuckle barrel and the clevis end disclosed that they were undamaged. According to the Piper PA-38-112 parts catalog, the primary cable turnbuckle barrel is to be secured with NAS651-16S locking clips on both sides; however, no clips were found at the accident site or during the subsequent detailed inspection of the wreckage. With the particular configuration of the turnbuckle assembly, it could not be properly secured by the use of safety wire alone. Measurement of the primary right wing aileron cable found that it was not stretched and there was no evidence to indicate that it was connected during the impact sequence. Aircraft records indicated the aileron flight control cable system, including the primary right wing aileron turnbuckle area, were visually inspected at the last 100-hour inspection. The aircraft maintenance records did not have any entries involving the adjustment, removal, or replacement of the aileron flight control cables or components, and the investigation was unable to establish when the safety wire was substituted for the NAS651-16S clips. The three pilots who had flown the airplane on the day before the accident (including one instructional flight and a private pilot practical flight test) reported that there were no discrepancies with the airplane during the flights. The physical evidence is wholly consistent with the primary aileron cable turnbuckle not being connected at ground impact. It is unlikely that the departure from controlled flight that resulted in the ground collision was due to the disconnected aileron cable; however, such a disconnect clearly could hinder any upset recovery effort. Visual meteorological conditions prevailed with no evidence of unusual, hazardous, or violent weather in the area. Evidence clearly shows the engine was producing significant power at ground impact.

Probable cause

The student pilot's failure to regain control of the aircraft following an upset due to the disconnected primary right aileron control cable. The failure of the company maintenance personnel to detect and correct the improperly secured turnbuckle fitting at the last 100-hour inspection is also causal.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX04FA167
Event ID
20040325X00371
Case number
LAX04FA167
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2004-03-19.
  • API snapshot SHA-256: 6474e8866c113e173eb6c9d47ab372fbf42f9a01f56b2bab63d70351fd9dc3f3; retrieved 2026-09-20T18:31:18.334Z.