FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN23LA388 · Cessna 210B

30 Aug 2023 · Wichita, KS, United States

Skynavy Aviation Cessna 210B · Accident during initial climb

From an unrecorded airport to Tulsa, OK

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's injuries. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
CEN23LA388
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 210B

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
N9663X
Onboard fatalities
Unknown
Route
From not recordedTo Tulsa, OK
Aircraft age
About 61 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
Initial climb
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 flight instructor and private pilot receiving instruction reported that their first two attempts to depart were aborted due to engine roughness discovered during the engine run-ups, which was subsequently determined to be an ignition issue that was addressed by replacing a spark plug. After a satisfactory engine run-up check, they initiated the takeoff. During the initial climb, when the airplane reached about 150 ft above ground level (agl), the tower controller informed them that the airplane was trailing smoke. About that time, the engine lost all power, and the flight instructor executed a forced landing to a field where the airplane sustained substantial damage to both wings, fuselage, and left horizontal stabilizer. Postaccident examination revealed that the oil sump contained only 4 quarts of oil with a total oil capacity of 12 quarts. No evidence of an external oil leak was found. Examination of the top spark plugs found that the electrodes were dry, black, and sooty, indicating an overly rich fuel mixture. The airplane was equipped with a fuel flow transducer installed at the firewall, upstream of the engine driven-fuel pump and downstream of the electric fuel pump. According to the maintenance records, the transducer was installed in conjunction with an avionics upgrade and in accordance with a supplemental type certificate (STC). The installation manual associated with that STC stated that the placement of the transducer was at the discretion of the installer but that a common location was downstream of any electric boost pumps but upstream of the engine-driven fuel pump. However, the transducer manufacturer’s installation manual provided conflicting information, stating that the transducer must be installed after any fuel pumps and that installation upstream of any fuel pumps could result in vapor lock. Although a vapor lock condition would result in a lean mixture that could result in a loss of engine power, the spark plug indications and the in-flight smoke were not indicative of a lean mixture condition. Additionally, although vapor lock can result in hard starting, it generally does not manifest as a loss of power once the engine is operating. The oil sump contained less oil than specified for its minimum operating capacity. However, postaccident examinations found no evidence of oil leakage and no condition that would result in the engine burning oil. Further, the engine was not seized, and the spark plugs did not appear to be oil fouled. Thus, there was no evidence that the low oil level contributed to the loss of engine power. A fuel line fitting that extended from the engine-driven fuel pump to the mixture valve was loose and moved freely when slight finger pressure was applied. Blue staining was evident at the fitting location, potentially consistent with fuel leakage. The fuel injection mixture control valve screen contained substantial debris and fibers. However, postaccident testing of the fuel control unit (with the contaminated screen installed), fuel pump, and fuel flow sensor revealed no functional deficiencies. The loose fuel fitting could result in leakage of fuel and, in conjunction with the obstructed fuel filter, could result in a lean mixture. Under certain conditions, fuel leakage in an airplane can result in a fuel spray that may appear as a cloud of white fuel vapor, which could be mistaken for smoke. However, the investigation was not able to determine the amount of fuel leakage from the loose fitting, and, as stated previously, the spark plug indications were inconsistent with a lean fuel condition. The reason for the loss of power could not be determined.

Probable cause

Loss of engine power for reasons that could not be determined.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN23LA388
Event ID
20230830192968
Case number
CEN23LA388
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, cause areas. 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: 55b2d176bde7079ed7956899491973fde6bfde2f1ac453142f8d74d9272310dc; retrieved 2026-09-16T18:03:56.887Z.