FTW83LA192 · Cessna 210K
Cessna 210K · Accident: total loss of engine power (non-mechanical) on approach
From Monroe Regional Airport (MLU) to San Marcos, TX
Event
- NTSB case
- FTW83LA192
- 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 210K
- 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
- N8234M
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Monroe Regional Airport (MLU), Monroe, LATo San Marcos, 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
- 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 (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
- Fuel starvation
- 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
- Fluid, fuel › Starvation
- Pilot in command › Fuel tank selector position, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
BEFORE TAKING OFF (AT 1740) ON HIS RETURN FLT, THE PLT GOT A WX BRIEFING & CHECKED THE NOTAMS, BUT DID NOT REFUEL THE ACFT. THERE WERE NO NOTAMS FOR THE SAN MARCOS ARPT. DURING ARRIVAL AT SAN MARCOS, TX, NO RWY LIGHTS WERE VISIBLE. THE PLT CIRCLED FOR 15 TO 20 MIN UNTIL HE VERIFIED THE RWY LIGHTS WERE INOP, THEN DIVERTED TO AUSTIN,TX. HE STATED THAT ON FINAL APCH TO LAND, THE ENG LOST POWER WITH THE L MAIN TANK INDICATING 1/3 FULL & THE R TANK 1/4 FULL. HE STATED HE SWITCHED FUEL TANKS BUT WAS UNABLE TO START THE ENG. DURING THE LANDING ONTO A BOULEVARD, THE NOSE LANDING GEAR COLLAPSED & THE R MAIN GEAR SEPARATED. A PASSING VEHICLE RAN OVER THE SEPARATED GEAR WHICH RUPTURED ITS FUEL TANK. THE PLT TOLD THE FBO THAT HE MADE THE APCH USING THE R TANK, THEN WHEN HE LOST POWER, HE SWITCHED TO THE L TANK & BACK TO THE R TANK. LATER, HE STATED HE MADE THE APCH USING THE L TANK. THE ARPT MANAGER AT SAN MARCOS SAID A NOTAM WAS CALLED IN ON 1/25/83 THAT THE RWY LIGHTS WOULD BE INOP INDEFINITELY, BUT NO RECORD OF THIS CALL WAS AVAILABLE.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record FTW83LA192
- Event ID
- 20001214X42685
- Case number
- FTW83LA192
- 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 1983-04-15.
- API snapshot SHA-256: bab5b3dc6c3fc6dc64613d7a9cb957354bfb2d4396bdc71f43c434e3522802f0; retrieved 2026-09-22T02:43:52.450Z.