FTW00FA245 · Cessna 421C
Cessna 421C · Accident: total loss of engine power (mechanical failure) en route
From Pecos Municipal Airport (PEQ) to San Antonio International Airport (SAT)
Event
- NTSB case
- FTW00FA245
- 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
- Visual Meteorological Cond
Cessna 421C
- 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
- N421NT
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Pecos Municipal Airport (PEQ), Pecos, TXTo San Antonio International Airport (SAT), San Antonio, TX
- 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 (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
- Tree(s)
- 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, not obtained
- Lubricating system › Contamination
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
Approximately 8 months prior to the accident, during a cross country flight, the owner shutdown the left engine due to low oil pressure and diverted from his intended destination to a nearby airport. During descent, the right alternator failed, and the owner performed the emergency gear extension procedure. Following an emergency gear extension, the landing gear of this model airplane cannot be retracted until the system has been ground serviced. A mechanic reported that about 7 months prior to the accident, with the owner present, he removed the oil filter from the left engine, found it packed with metal shavings and told the owner that the engine needed overhaul. Two other mechanics reported that approximately three weeks before the accident, they installed an oil filter on the left engine, changed the oil, and cleaned the oil pressure regulator. They ground ran both engines with no discrepancies noted. One of the mechanics reported that following the engine run, the left engine oil filter was removed, examined, and no metal was found. The landing gear was not serviced. According to the owner, the pilot was "hired" by one of the two mechanics to ferry the airplane with the gear extended to a location where the gear could be serviced. While en route, the pilot reported a loss of power on the left engine, that he was having trouble feathering the engine, that the airplane would not maintain altitude and he was looking for a place to land. Witnesses observed the airplane flying low, wheels down and losing altitude. They further observed it roll into a steep left bank, hit trees and a fence, catch fire, come to rest inverted on a road and burn. Post accident examination of the left engine revealed a hole in the right crankcase half over the #3 cylinder attach point. Disassembly of the left engine revealed that the #3 connecting rod was separated from the crankshaft, and the rod bolts, rod cap, and top of the rod were deformed. The #5 piston pin had one cap missing. Scoring was noted on the crankshaft journals, and the main bearings exhibited discoloration and deformation consistent with oil starvation. The cylinders exhibited deformation, scoring in the barrels, and deposits on the domes. The camshaft exhibited discoloration and scoring on the camshaft lobes. Disassembly of the left propeller revealed that it was in the vicinity of low pitch/latch position and not rotating at impact. The disassembly of the right engine and propeller did not reveal any discrepancies that would have precluded operation prior to impact. Estimates of the airplane's climb performance indicated that with the landing gear down and the left propeller stopped, it was not capable of sustained flight.
Probable cause
the loss of left engine power as a result of the owner's failure to overhaul the engine before further flight after the lubrication system was found contaminated with metal. Contributing factors were the pilot's decision to fly the aircraft with a non-operating landing gear system, which resulted in a forced landing, and the lack of suitable terrain for the forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW00FA245
- Event ID
- 20001212X21721
- Case number
- FTW00FA245
- 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, coordinates. 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: c4de69b450a741d99a63885b5ca3283536a6fe8f750b5d3bc1cfde5f575b6cd8; retrieved 2026-09-20T20:54:38.297Z.