LAX89FA030 · Cessna 421A
Cessna 421A · Accident: total loss of engine power (non-mechanical) en route
From Zamperini Field (TOA) to Tucson International Airport (TUS)
Event
- NTSB case
- LAX89FA030
- 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
- 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
- Instrument Meteorological Cond
Cessna 421A
- Aircraft type
- Cessna 421
- 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
- N3385Q
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Zamperini Field (TOA), Torrance, CATo Tucson International Airport (TUS), Tucson, AZ
- 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
- En route · cruise
- 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 (non-mechanical)
- 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
- Destroyed
Cause areas
- Engine assembly, cylinder › Fatigue
- Engine assembly, cylinder › Separation
- Pilot in command › In-flight planning/decision, poor
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PLT CONTACTED THE ARSA CONTROLLER FOR ADVISORIES AFTER LOSING PWR ON THE RIGHT ENG OVER AN AIR FORCE BASE. THE CONTROLLER ADVISED THE PLT THAT HIS POSITION WAS NEAR A CIVILIAN ARPT WITH LIMITED MAINTENANCE FACILITIES AND AN AIR FORCE BASE. THE PLT ADVISED THAT HE DESIRED TO CONTINUE TO A LARGER CIVILIAN ARPT ALONG HIS ROUTE WHERE HE COULD OBTAIN SERVICE. THE PLT THEN INFORMED THE CONTROLLER THAT HE COULD BARLEY SEE THE GROUND AND THAT HE WAS UNABLE TO MAINTAIN ALT DUE TO THE PROPELLER NOT FEATHERING. THE ACFT OVERFLEW A SMALL CIVILIAN ARPT AND THE PLT TOLD THE UNICOM OPERATOR THAT HE WOULD ATTEMPT TO LAND ON AN INTERSTATE HWY. THE ACFT OVERFLEW THE HWY AND IMPACTED AN ELECTRICAL TRANSMISSION LINE AND COLLIDED WITH A RESIDENCE. POST ACCIDENT INSPECTION REVEALED THE RIGHT ENG #3 CYLINDER HEAD FRACTURED ALLOWING THE HEAD TO DISPLACE OUTWARD 3/8 INCH. FRACTURE RESULTED FROM FATIGUE AT THREADED AREA BTW HEAD AND CYLINDER. THE PROPELLER GOVERNOR OPERATED NORMALLY DURING FUNCTIONAL TESTING AFTER THE ACCIDENT.
Probable cause
THE PILOT'S POOR DECISION AND MISJUDGEMENT OF DISTANCE. THE SEPARATION OF THE CYLINDER, FAILURE OF THE PROPELLER TO FEATHER, AND IMPACT WITH WIRES AND A RESIDENCE WERE FACTORS IN THE ACCIDENT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX89FA030
- Event ID
- 20001213X27261
- Case number
- LAX89FA030
- 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. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1988-11-02.
- API snapshot SHA-256: b7edfeea436ec26c31461116d7ed56d72a3dbb3f88acb3bfafe5e8a08ca97d9d; retrieved 2026-09-21T03:30:03.979Z.