CHI03LA292 · Luscombe 8A
Luscombe 8A · Accident: loss of control on ground/water during landing
From Blosser Municipal Airport (CNK) to Macon Fowler Memorial Airport (K89)
Event
- NTSB case
- CHI03LA292
- 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
Luscombe 8A
- Aircraft type
- Luscombe 8
- 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
- N25342
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Blosser Municipal Airport (CNK), Concordia, KSTo 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 · 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
- Pilot in command › Rudder, improper use of
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane sustained substantial damage when it departed off the right side of the runway during the landing rollout. The pilot stated he performed a three-point landing and after touchdown the airplane encountered a "crosswind gust." The pilot reported that the airplane "veered" to the left and he "over controlled" with right rudder input, resulting in the airplane departing the right side of the runway and traveling down an embankment. The pilot stated the airplane impacted a tree and spun 180 degrees before coming to a stop. The pilot reported there were no mechanical malfunctions or failures during the accident flight.
Probable cause
The pilot's improper use of the rudder, which resulted in directional control not being maintained during the landing. A factor to the accident was the crosswind gust.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI03LA292
- Event ID
- 20030904X01458
- Case number
- CHI03LA292
- 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: 5e34b055018af07ec5296d3e20551a57752c78b964c051f3915e229863231fba; retrieved 2026-09-22T08:41:05.010Z.