ERA11CA053 · Luscombe 8A
Luscombe 8A · Accident: loss of control on ground during landing
From Winchester Regional Airport (OKV) to Ingalls Field (HSP)
Event
- NTSB case
- ERA11CA053
- 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
- N71102
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Winchester Regional Airport (OKV), Winchester, VATo Ingalls Field (HSP), Hot Springs, VA
- 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
- 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 › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, he maneuvered the airplane into a slip configuration while on final approach in an effort to compensate for a crosswind. He landed on runway 25 with using a wheel-landing technique, where the main landing gear touchdown first and the tail gear follows during the landing roll. During the roll out, as the airplane slowed, a gust of wind struck its right side. The airplane began to veer to the right and the pilot attempted to regain directional control with full left rudder and opposing aileron. The airplane continued to veer to the right and flipped over, coming to rest inverted. As a result of the accident sequence, the airplane incurred damage to the left wing, fuselage, vertical stabilizer, and rudder. The pilot reported that there were no preimpact mechanical anomalies with the airplane. The wind reported at the airport about the time of the accident were from 310 degrees at 14, gusting to 19 knots.
Probable cause
The pilot's inadequate compensation for the crosswind during landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA11CA053
- Event ID
- 20101110X44157
- Case number
- ERA11CA053
- 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: 1c7a2392112b8d3a8c8bf4b8dd80fb3994ab5b74888bb48a62dbe5e7d51e1884; retrieved 2026-09-15T15:33:17.049Z.