FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN23LA117 · Luscombe 8A

20 Feb 2023 · Guthrie, OK, United States

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

Report a problem

Event

NTSB case
CEN23LA117
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
Event fatalities
Unknown
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 not recordedTo not recorded
Aircraft age
About 83 years (built 1940)
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
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 from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The student pilot reported that, while rolling out on landing, the airplane suddenly veered to the right causing the nose to turn to the left. The student pilot attempted to correct with opposite rudder; however, the airplane exited the left side of the runway, proceeded down a terrace, and nosed over, which resulted in substantial damage to the vertical stabilizer. The student pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. At the time of the accident, the student pilot was landing the airplane on runway 34 with wind from 300° at 6 knots.

Probable cause

The student pilot’s failure to maintain directional control during the landing roll.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN23LA117
Event ID
20230223106765
Case number
CEN23LA117
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, coordinates, cause areas. 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: 8a069b0426c4d51d14811406da893a9027e996855c16d57543335140950130aa; retrieved 2026-09-16T17:21:59.935Z.