LAX90LA247 · Beech A-35
Beech A-35 · Accident: total loss of engine power (mechanical failure) on approach
From an unrecorded airport to Presidente Itamar Franco Airport (IZA)
Event
- NTSB case
- LAX90LA247
- 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
Beech A-35
- Aircraft type
- Beechcraft A-35
- 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
- N8663A
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Presidente Itamar Franco Airport (IZA)
- 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 final
- 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)
- 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/operator management › Maintenance, overhaul, not performed
- Fuel system, carburetor › Leak
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE AIRCRAFT WAS PERFORMING 'S' TURNS ON FINAL TO ALLOW SPACING FOR A GLIDER DEPARTURE. AS THE PILOT ADDED THROTTLE THE ENGINE FAILED TO RESPOND AND THE AIRCRAFT LANDED SHORT OF THE RUNWAY IN A HILLY BRUSH COVERED AREA. THE CARBURETOR WAS FUNCTIONALLY TESTED TO MANUFACTURER'S SPECIFICATIONS, HOWEVER, IT WAS FOUND TO BE ON THE RICH SIDE. FURTHER EXAMINATION OF THE UNIT REVEALED THAT FUEL WAS LEAKING INTO THE INTAKE AIR SECTION OF THE CARBURETOR FROM A CRACKED RUBBER DIAPHRAM. ACCORDING TO BENDIX, THE CARBURETOR SHOULD BE OVERHAULED AT THE SAME TIME THE ENGINE IS OVERHAULED. DETAILED REVIEW OF THE MAINTENANCE RECORDS DISCLOSED NO EVIDENCE THAT THE CARBURETOR WAS OVERHAULED DURING THE LAST ENGINE OVERHAUL.
Probable cause
AN ENGINE FAILURE DUE TO FUEL LEAKAGE FROM A RUPTURED DIAPHRAM IN THE CARBURETOR; FAILURE OF THE AIRCRAFT OWNER TO COMPLY WITH THE MANUFACTURER'S RECOMMENDED COMPONENT OVERHAUL INTERVALS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX90LA247
- Event ID
- 20001212X23738
- Case number
- LAX90LA247
- 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: 32c07f52556b226dee676d10831e6736150b93a921201a3a8ba8eb4323b51278; retrieved 2026-09-23T05:39:27.424Z.