FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW99LA059 · Cessna 421C

1 Jan 1999 · SHELBYVILLE, TX, United States

Cessna 421C · Accident: airframe, component or system failure en route

From Lakefront Airport (NEW) to Millard Airport (MLE)

Report a problem

Event

NTSB case
FTW99LA059
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

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
N234CG
Operator
Unknown
Onboard fatalities
Unknown
Route
From Lakefront Airport (NEW), New Orleans, LATo Millard Airport (MLE), Omaha, NE
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
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
Substantial

Cause areas

  • Electrical system, alternator › Failure
  • Electrical system, voltage regulator › Failure

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

During a precautionary landing following a loss of electrical power, the pilot turned the airplane to avoid colliding with a pickup truck, and the airplane impacted trees. The pilot reported that while IMC, at 14,000 feet msl, he started preparing for ice penetration and turned on the two propeller anti-ice switches. The right propeller anti-icing circuit breaker popped, and when the circuit breaker was reset, the airplane experienced a total electrical failure. The pilot initiated an emergency descent, and entered into VFR conditions at about 1,500 feet. After about 30 minutes of trying to locate an airport, with it getting dark and thunderstorms in the area, the pilot elected to land on a narrow road with trees on both sides. Testing of the alternator system revealed discrepancies with the left alternator, both voltage regulators, and the right alternator out sensor.

Probable cause

The total failure of the aircraft's electrical system. Factors were the thunderstorms, the dusk light condition, and the lack of suitable terrain for the precautionary landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW99LA059
Event ID
20001204X00054
Case number
FTW99LA059
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: cc28430742c0747d62aed24bbf8aa375af6c173f78a139d468702814cd66f244; retrieved 2026-09-21T20:37:30.802Z.