CHI07CA175 · Luscombe 8A
Luscombe 8A · Accident: loss of control on ground/water during landing
From Columbus Southwest Airport (04I) to London, OH
Event
- NTSB case
- CHI07CA175
- 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
- N45468
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Columbus Southwest Airport (04I), Columbus, OHTo London, OH
- 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 › Compensation for wind conditions, inadequate
- Pilot in command › Directional control, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot was landing the tailwheel aircraft on runway 27 (4,001 feet by 75 feet, asphalt) with a right-hand crosswind. The pilot stated that upon touchdown "contact came before alignment was complete" and the airplane turned to the right. The pilot reported that he "overcompensated and got into an oscillation" and the airplane ground looped. The airplane departed the right side of the runway and struck a taxiway sign. The pilot stated in his accident report that the accident could have been prevented by performing a go around. Wind conditions reported at an airport, located 15 nautical miles east of the accident site, were: 350 degrees at 8 knots.
Probable cause
The pilot's failure to maintain directional control of the airplane and the pilot's inadequate compensation for the crosswind which resulted in a ground loop and subsequent collision with a taxiway sign. Factors contributing to the accident include the crosswind and the taxiway sign.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI07CA175
- Event ID
- 20070712X00921
- Case number
- CHI07CA175
- 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: 8d05ab26841d9ac8a52a0c67c81bd349de13e96e29a457909468d72d92bcbd4f; retrieved 2026-09-21T18:29:04.878Z.