CHI99LA195 · Cessna 150G
Cessna 150G · Accident: loss of control on ground/water during landing
From Butler Memorial Airport (BUM) to Fort Scott Municipal Airport (FSK)
Event
- NTSB case
- CHI99LA195
- 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 150G
- Aircraft type
- Cessna 150
- 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
- N2263J
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Butler Memorial Airport (BUM), Butler, MOTo Fort Scott Municipal Airport (FSK)
- 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 · landing roll
- 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
- Loss of control on ground/water
- 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 › Directional control, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
On landing rollout the airplane veered to the left side of the runway. The pilot reported that the airplane departed the runway surface, the tires sunk into soft turf on the side of the runway, and the airplane nosed over coming to rest in an inverted position. Inspection of the runway surface revealed a single tire skid mark that initiated approximately 240 feet from the runway threshold, 10 feet left of the runway centerline, and followed a left curved path terminating approximately 465 feet from the runway threshold, 20 feet left of the runway edge. The tire skid mark was approximated 225 feet long. Inspection of the wreckage revealed no mechanical anomalies with the aircraft's control and the brake systems. Both main landing gear wheels were free moving and the brake system was exercised and operated without any anomalous behavior.
Probable cause
The pilot's failure to maintain directional control during the landing roll. A factor to the accident was the soft terrain condition.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI99LA195
- Event ID
- 20001212X18953
- Case number
- CHI99LA195
- 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: dd93626902f9fb60bc9b1adf4225f9bf761c5d60ff0bff378b941a052d6cd856; retrieved 2026-09-22T14:45:20.082Z.