FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN14LA263 · Aero Commander 200D

27 May 2014 · La Grange, TX, United States

Aero Commander 200D · Accident en route

From Chennault International Airport (CWF) to Gillespie County Airport (T82)

Report a problem

Event

NTSB case
CEN14LA263
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
Unknown
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

Aero Commander 200D

Aircraft type
Aero Commander 200
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
N200D
Operator
Unknown
Onboard fatalities
Unknown
Route
From Chennault International Airport (CWF), Lake Charles, LATo Gillespie County Airport (T82), Fredericksburg, TX
Aircraft age
About 47 years (built 1967)
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
Defining eventThe 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
Unknown or undetermined
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

  • Aircraft › Aircraft power plant

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot reported that, during cruise flight, the airplane's engine began to run roughly. He then observed no pressure on the oil pressure gauge, and smoke entered the cockpit. The pilot shut down the engine and attempted to glide the airplane to the nearest airport. However, the pilot determined that the airplane would not make the runway and subsequently performed a forced landing to a field. A postaccident on-scene examination revealed damage to the engine's crankcase consistent with oil starvation. The airplane was repaired and the engine disposed of before a thorough examination could be conducted. The reason for the oil starvation could not be determined.

Probable cause

The loss of engine power due to oil starvation for reasons that could not be determined based on the available evidence.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN14LA263
Event ID
20140529X14523
Case number
CEN14LA263
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 73e5d66585fadf109f2eb042c1bf97152992cd50d521dead49d6117b16325641; retrieved 2026-09-15T23:41:18.766Z.