MIA99LA025 · Ercoupe (Eng & Research Corp.) 415-C
Ercoupe (Eng & Research Corp.) 415-C · Accident: total loss of engine power (mechanical failure) on approach
From 5M0 to an unrecorded destination
Event
- NTSB case
- MIA99LA025
- 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
- 0 · 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-C
- 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
- N99924
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 5M0To 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
- Approach · VFR pattern downwind
- 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
- Total loss of engine power (mechanical failure)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Wire, transmission
- 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
- Other maintenance personnel › Maintenance, modification, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The engine lost power as the pilot turned onto the downwind leg for landing. As the pilot approached a field for landing, the aircraft collided with a power line and then the ground. Postcrash examination of the engine showed it was operating with an excessive rich fuel mixture. The carburetor float was found stuck in the full needle valve open position due to excessive solder on the float fulcrum contacting the bowl wall. The carburetor had been recently modified by installing a new style needle valve, which also required the addition of weight to the float fulcrum with solder.
Probable cause
Improper modification of the carburetor float by maintenance personnel resulting in the float sticking in the full needle valve open position and failure of the engine due to excessive fuel flow.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA99LA025
- Event ID
- 20001211X11318
- Case number
- MIA99LA025
- 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: f3aeab978c5ff33cd75756fb0a842b2da581f1e18edb1ba5512298ecc7ef0898; retrieved 2026-09-21T11:19:18.938Z.