FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN18LA287 · Cessna 210C

21 Jul 2018 · Blum, TX, United States

Cessna 210C · Accident: fuel related en route

From Granbury Regional Airport (GDJ) to Hilltop Lakes Airport (0TE4)

Report a problem

Event

NTSB case
CEN18LA287
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
Visual Meteorological Cond

Cessna 210C

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
N3611Y
Operator
Unknown
Onboard fatalities
Unknown
Route
From Granbury Regional Airport (GDJ), Granbury, TXTo Hilltop Lakes Airport (0TE4), Hilltop Lakes, TX
Aircraft age
About 56 years (built 1962)
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
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
Fuel related
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 › Fluids/miscellaneous hardware
  • Personnel issues › Action/decision

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 stated that she was about 20 minutes into a cross-country flight with the airplane at a cruise altitude of 3,500 ft mean sea level (msl) when the engine started to run roughly. The pilot suspected vapor lock because of the hot weather conditions and attempted to restore engine power. She switched the fuel selector positions from the right to the left fuel tank, but when the roughness worsened, she switched the selector back to the right tank. She selected the boost pump to LOW and then HIGH, and retarded throttle control, all of which had no effect on engine operation. The engine began to lose power rapidly and then quit; the propeller windmilled.

The pilot began an approach for a forced landing on a field with flaps at 30° and the landing gear retracted. She said that it would take her about 3 minutes to manually pump the landing gear down and that she did not have enough time to lower the landing gear due to the airplane's altitude. The landing on the field was "firm," and the airplane quickly slid to a stop and sustained substantial damage during the gear-up landing.

The airplane emergency checklist for a forced landing after a complete engine failure required extension of the landing gear if the landing surface is smooth and hard and does not mention the need to extend the landing gear using manual extension; the windmilling engine would provide power to the hydraulic pump to operate the flaps and also to extend the landing gear normally. Postaccident examination of the field showed that the surface was hard and in good condition to perform a landing; however, the pilot stated that she could not determine this when she was 2 miles from the field when she decided to land there.

The density altitude near the departure airport was about 3,500 ft msl, which would have required full rich fuel mixture at takeoff.

Postaccident examination of the airplane revealed that the left and right fuel tanks were each about half full, the throttle and propeller controls were in the full forward positions, and the mixture control was near the idle cutoff position. The pilot stated she did not remember advancing the mixture control to full rich when the engine roughness occurred and did not change the mixture control position after landing. Advancement of the mixture control to full rich would have increased fuel flow to mitigate restrictions to fuel flow, if present. There were no anomalies noted during the postaccident test run of the engine. Thus, it is likely that the pilot leaned the fuel mixture too much when the airplane reached cruise altitude, which resulted in the subsequent loss of engine power.

Probable cause

The pilot's excessive leaning of the fuel mixture, which resulted in a loss of engine power, and the pilot's failure to extend the landing gear in accordance with the airplane emergency checklist, which resulted in a gear-up landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN18LA287
Event ID
20180723X93813
Case number
CEN18LA287
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: 221923ea0ae32a80546433d27865678283f01066b932b70af3db8b31c579a5be; retrieved 2026-09-16T07:57:40.593Z.