FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI95LA122 · Cessna 188

8 Apr 1995 · Meade, KS, United States

Cessna 188 · Accident: in flight collision with terrain/water during an uncontrolled descent

Report a problem

Event

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

Cessna 188

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
N9849V
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo 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
Uncontrolled descent
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
In flight collision with terrain/water
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Stall/mush
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 › Airspeed(vlo), low

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

NTSB narrative

THE PILOT OF AN AERIAL APPLICATION AIRPLANE SAID HE ROTATED THE AIRPLANE AT 60 TO 65 MPH. HE SAID THE AIRPLANE ACCELERATED TO 85 MPH IN THE CLIMB. HE RETRACTED ONE NOTCH OF FLAPS AND NOTICED THE AIRPLANE STOPPED CLIMBING. HE SAID THE AIRPLANE BEGAN DESCENDING AT A FAST RATE. DURING THE DESCENT HE SAID THE AIRSPEED HAD DECELERATED TO 60 MPH WHILE THE THROTTLE AND PROPELLER CONTROLS WERE FULL IN. THE PILOT REPORTED THE HIGH DESCENT RATE CONTINUED UNTIL THE AIRPLANE COLLIDED WITH THE GROUND. THE ON-SCENE INVESTIGATION REVEALED NO PRE-IMPACT MECHANICAL ANOMALIES WITH THE ENGINE OR AIRFRAME. THE PILOT'S OPERATING HANDBOOK SHOWED THE LIFTOFF SPEED TO BE 65 MPH.

Probable cause

the pilot taking off the airplane at a low liftoff speed (Vlo). A factor associated with the accident was a stall/mush encountered by the pilot.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI95LA122
Event ID
20001207X03259
Case number
CHI95LA122
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. 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: a82ccf68481f2e3ff0dc52d60e3be78aabfebc91ae90cfeae9359566c3cdc8d0; retrieved 2026-09-21T22:21:15.822Z.