LAX97FA123 · Ercoupe (Eng & Research Corp.) 415-D
Ercoupe (Eng & Research Corp.) 415-D · Accident: airframe, component or system failure during initial climb
From Whiteman Airport (WHP) to Oakland San Francisco Bay Airport (OAK)
Event
- NTSB case
- LAX97FA123
- 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.) 415-D
- Aircraft type
- Ercoupe (eng Research 415
- 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
- N3030H
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Whiteman Airport (WHP), CATo Oakland San Francisco Bay Airport (OAK), Oakland, CA
- 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
- Initial climb
- 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
- Electrical system › Improper
- Electrical system, circuit breaker › Not installed
- Other maintenance personnel › Maintenance, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
While on a downwind departure, the pilot declared an emergency and requested an immediate landing. He was cleared to land on any runway. The pilot turned a close base entry to his departure runway, and the turn continued into a descending spiral to impact. Tower personnel observed smoke trailing from the aircraft at the time of the emergency. Postaccident examination revealed an improperly installed electrical system, which lacked circuit protection and proper use of aviation type wire.
Probable cause
improper maintenance/installation of electrical wiring, the lack of circuit protection, and subsequent in-flight electrical fire.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX97FA123
- Event ID
- 20001208X07566
- Case number
- LAX97FA123
- 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: 2c898d86d69d6bc9b5fbb2a70278090c502d2392bc243fb05fb0b27ec0bec0c9; retrieved 2026-09-20T23:01:42.114Z.