FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN13CA411 · Luscombe 8

14 Jul 2013 · Rose Hill, KS, United States

Luscombe 8 · Accident: loss of control on ground during landing

From Cook Airfield (K50) to Cook Airfield (K50)

Report a problem

Event

NTSB case
CEN13CA411
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 8

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
N1837B
Onboard fatalities
Unknown
Route
From Cook Airfield (K50), Rose Hill, KSTo Cook Airfield (K50), Rose Hill, KS
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 · flare/touchdown
Defining eventThe 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
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

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

NTSB narrative

According to the pilot, he entered the traffic pattern for runway 17. The wind was favoring runway 19, a turf runway, but he thought the recent rains may have made the runway soft. As he landed the tailwheel airplane on runway 17, the wind switched from the south to the west. The airplane turned to the southwest; he added full left rudder and added power. He was unable to stop the turn and the airplane ground looped. Examination of the airplane revealed substantial damage to the right wing and fuselage. The pilot reported no mechanical anomalies that would have precluded normal operation.

Probable cause

The pilot's inadequate compensation for the crosswind, which resulted in a loss of directional control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN13CA411
Event ID
20130715X20927
Case number
CEN13CA411
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 6ac2cf662d35f21edff59ca7244dd3a71c590c9123263198c068a9c6f7b5293a; retrieved 2026-09-15T22:12:28.356Z.