FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI95LA336 · Cessna T210M

27 Sept 1995 · Dodge City, KS, United States

Cessna T210M · Accident: partial loss of engine power (non-mechanical) on approach

From Springfield Branson National Airport (SGF) to Dodge City Regional Airport (DDC)

Report a problem

Event

NTSB case
CHI95LA336
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
Instrument 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
N7660E
Operator
Unknown
Onboard fatalities
Unknown
Route
From Springfield Branson National Airport (SGF), Springfield, MOTo Dodge City Regional Airport (DDC), KS
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 · IFR initial approach
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
Partial loss of engine power (non-mechanical)
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

  • Pilot in command › Fuel boost pump selector position, improper use of
  • Pilot in command › Powerplant controls, improper use of

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

NTSB narrative

The pilot reported that after descending on the initial approach segment of the ILS approach, he pushed the throttle forward to add power and level off upon reaching the assigned altitude. The pilot stated that he did not receive an increase in engine power. He then turned the fuel boost pump ON, but no additional power was obtained. Losing altitude and airspeed, the pilot realized that the airplane was not going to be able to make it the airport, and a forced landing was made on a field. Postaccident examination revealed no mechanical abnormalities. The engine was successfully started and it ran to 1500 RPM. The pilot stated that he always turns the auxiliary fuel pump ON during all approaches. Normal Operating Procedures in the Pilot Operating Handbook recommends that the auxiliary fuel boost pump be in the OFF position during descent.

Probable cause

the pilot's improper use of the auxiliary fuel boost pump during descent which led to fuel flooding and loss of combustion.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI95LA336
Event ID
20001207X04472
Case number
CHI95LA336
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 1995-09-28.
  • API snapshot SHA-256: 25cb48d2e63a3d455d93ff3a42ff00797fdc51cab717f7cdbb97100e390b6f10; retrieved 2026-09-22T23:13:16.918Z.