FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Prompt Air Cessna T210M accident

21 Feb 1992 · Washington, IN, United States

Cessna T210M · Accident: total loss of engine power (mechanical failure) en route

From Bowman Field (LOU) to Abraham Lincoln Capital Airport (SPI)

Report a problem

Event

NTSB case
CHI92LA094
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
Charter & commuter
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 T210M

Aircraft type
Cessna 210
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
N732TR
Operator
Prompt Air
Onboard fatalities
Unknown
Route
From Bowman Field (LOU), Louisville, KYTo Abraham Lincoln Capital Airport (SPI), Springfield, IL
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 135: Air Taxi & Commuter
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)
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

  • Engine assembly, crankshaft › Fatigue
  • Engine assembly, crankshaft › Fractured

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

NTSB narrative

THE ACCIDENT AIRPLANE SUSTAINED SUBSTANTIAL DAMAGE DURING A FORCED LANDING FOLLOWING A COMPLETE LOSS OF ENGINE POWER. INSPECTION DISCLOSED A FRACTURED CRANKSHAFT. A METALLURGICAL EXAMINATION OF THE CRANKSHAFT REVEALED LADDER CRACKING AND A FATIGUE FRACTURE BETWEEN THE NUMBER 3 AND NUMBER 5 MAIN BEARING JOURNALS. THE CRANKSHAFT WAS A USED CRANKSHAFT WHICH WAS INSPECTED AND INSTALLED AS PART OF A 'ZERO TIME' OVERHAULED ENGINE. NO PREEXISTING METALLURGICAL ANOMALIES WERE DISCOVERED DURING THE POSTACCIDENT METALLURGICAL INSPECTION.

Probable cause

THE TOTAL LOSS OF ENGINE POWER DUE TO A FATIGUE-FRACTURED CRANKSHAFT.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI92LA094
Event ID
20001211X14089
Case number
CHI92LA094
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: 8508f7c570be251295b4e6c367fd8297c22715e4c19ddb16cd34fc26c75277bb; retrieved 2026-09-18T18:48:09.620Z.