FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI02LA101 · Beech C23

4 Apr 2002 · Kahoka, MO, United States

Beech C23 · Accident: in flight collision with terrain/water during landing

From Kahoka Municipal Airport (0H7) to Macon Fowler Memorial Airport (K89)

Report a problem

Event

NTSB case
CHI02LA101
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

Beech C23

Aircraft type
Beechcraft 23
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
N2258L
Operator
Unknown
Onboard fatalities
Unknown
Route
From Kahoka Municipal Airport (0H7), Kahoka, MOTo Macon Fowler Memorial Airport (K89), Macon, MO
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
Landing
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
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Soft field takeoff/procedure, improper

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

NTSB narrative

The airplane was destroyed on impact with terrain and postcrash fire during takeoff from a soft field with inoperative runway lights. The Airport Facility Directory listed the runway lighting for the airport as inoperative. Night visual meteorological conditions prevailed at the time of the accident. The pilot stated that the airplane lifted off at 65 knots approximately 1,500 feet down the 2,650 foot long runway. Takeoff performance data listed for the model of airplane indicates that the airplane has an approximate ground roll distance of 1,220 feet. The pilot described the flight controls as feeling mushy, a condition which is consistent with flight near stalling speed and high drag flight. He also stated that the airplane developed more airspeed and lift as it approached the end of the runway but the airplane seemed to not want to maintain flight so he chose to land the airplane. No mechanical malfunctions were noted.

Probable cause

The improper soft field takeoff/procedure by the pilot. Contributing factors were the night condition and the inadequate planning/decision by the pilot.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI02LA101
Event ID
20020409X00482
Case number
CHI02LA101
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 2002-04-05.
  • API snapshot SHA-256: d53c59d6ff3552f1b37e947004c18fa4ea950ebe71edc748cc72e4cf4efe1d91; retrieved 2026-09-21T19:45:10.392Z.