FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX99FA128 · Ercoupe (Eng & Research Corp.) 415E

20 Mar 1999 · Kingman, AZ, United States

Ercoupe (Eng & Research Corp.) 415E · Accident: airframe, component or system failure on approach

From Lake Havasu City Airport (HII) to Kingman Airport (IGM)

Report a problem

Event

NTSB case
LAX99FA128
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
2 · 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

Ercoupe (Eng & Research Corp.) 415E

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
N94818
Operator
Unknown
Onboard fatalities
Unknown
Route
From Lake Havasu City Airport (HII), LAKE HAVASU CTY, AZTo Kingman Airport (IGM)
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
Approach · VFR pattern base
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
Airframe, component or system failure
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

  • Faa(other/organization) › Procedure inadequate
  • Wing, spar › Corroded
  • Wing, spar › Failure, partial

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

A ground-based witness, located north of the airport, reported observing the accident airplane's wings rolling right and left to nearly a vertical bank. Thereafter, the airplane entered a spin and impacted the ground while in a 30- to 45-degree nose low pitch attitude. The impact site was 0.6 miles from the approach end of the runway. Pilots ahead and behind the airplane reported experiencing moderate to extreme turbulence in the traffic pattern. The surface wind was reported at 14 knots with gusts to 22 knots. At the time of the accident the airplane was calculated to be between 94 and 127 pounds over its maximum certificated 1,400 pounds gross weight. During the on scene wreckage examination, the left wing's rear spar attachment fitting was found severely corroded, with missing rivet heads and was separated. Metallurgical examination of the severely corroded spar attachment fitting revealed the presence of rivet heads that had failed and popped off in flight and an associated corrosion-related crack that had compromised the structural integrity of the fitting assembly. Unable to sustain the imposed wing loading, the fitting failed in flight. The failed rivet heads and evidence of the corrosion was on the backside of the spar in an area not visible during inspections. In 1995, a one-time visual inspection of the wings' internal structure for corrosion was mandated by the Federal Aviation Administration through issuance of Airworthiness Directive 94-18-04. This 'one time' visual inspection requirement was complied with according to a logbook entry dated 1997, and thereafter the wings were recovered with fabric. In May 1998, the pilot purchased the airplane, which had been manufactured in 1948. In September 1998, the airplane received another annual inspection during which no logbook entry was made indicating that the wing's internal structure had been reexamined for evidence of corrosion. The corrosion developed due to the presence of moisture and the dissimilar metals (steel bracket riveted to an aluminum spar) being in contact with each other. The severity of the ongoing corrosion process between the metal components would not have been evident during an external visual inspection, despite the fact that a required access panel had not been installed pursuant to the AD. The AD inadequately addressed the aging aircraft issue by indicating compliance could be achieved through performance of a one-time visual inspection to ferret out nonviewable evidence of internal corrosion.

Probable cause

The in-flight loss of airplane control due to rear wing spar attachment fitting failure. The failure resulted from severe corrosion that was undetected during performance of an inspection specified by an airworthiness directive. The airworthiness directive developed by the FAA was deficient in its specificity relating to recurrence. The directive was also deficient in its procedure requiring external inspection, which would not reveal development of internal corrosion. Contributing factors to the accident were the turbulent atmospheric condition that exacerbated the wing loading and the pilot's operation of the airplane in excess of maximum authorized gross weight.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX99FA128
Event ID
20001205X00336
Case number
LAX99FA128
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: investigation status. 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: fee404684ddc8f4bffab617881fcf064028e4199dc81e5c1f55419ad4eaee40c; retrieved 2026-09-20T22:12:34.491Z.