FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DFW07LA108 · Cessna A188A

11 May 2007 · Clinton, OK, United States

Cessna A188A · Accident: airframe, component or system failure while maneuvering

From Clinton Regional Airport (CLK) to an unrecorded destination

Report a problem

Event

NTSB case
DFW07LA108
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 A188A

Aircraft type
Cessna 188
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
N4413Q
Operator
Unknown
Onboard fatalities
Unknown
Route
From Clinton Regional Airport (CLK), Clinton, OKTo not recorded
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 137: Agricultural
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
Maneuvering · aerial application
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
Airframe, component or system failure
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

  • Exhaust system, stack › Failure
  • Fluid, fuel › Vapor lock

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

NTSB narrative

As the agricultural pilot was pulling up from a low level pass, he smelled something "like wires burning" and observed the engine's fuel pressure drop. The pilot selected the auxiliary fuel pump's "EMERGENCY" position and five to ten seconds later the engine lost partial power. Not able to maintain altitude, the pilot elected to land the airplane to a rolling wheat field. During landing, the airplane nosed over and came to rest in an inverted position. An examination of the airplane revealed that, prior to impact, the engine exhaust stack had separated from the muffler. Hot exhaust gasses, that are normally vented overboard, were directed to the airplanes firewall, resulting in thermal damaged to electrical wiring and a vapor condition in the fuel gascolator. The pilot attempted to purge the vapor to no avail. No other pre impact anomalies were noted with the engine or the fuel system that would have prevented normal operating power.

Probable cause

Separation of the exhaust stack and resulting vapor lock. A contributing factor was the none suitable terrain for the forced landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DFW07LA108
Event ID
20070517X00579
Case number
DFW07LA108
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: 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: 4a14b6d847c5098bef9dcb8c64b8b2e7c04446377e6b3a87cedbfb4be06076c4; retrieved 2026-09-21T08:48:56.167Z.