FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR16LA017 · Luscombe 8A A

24 Oct 2015 · Prescott, AZ, United States

Luscombe 8A A · Accident: runway excursion during landing

From Gallup Municipal Airport (KGUP) to Prescott Regional Airport - Ernest A. Love Field (KPRC)

Report a problem

Event

NTSB case
WPR16LA017
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 A

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
N25100
Operator
Unknown
Onboard fatalities
Unknown
Route
From Gallup Municipal Airport (KGUP), Gallup, NMTo Prescott Regional Airport - Ernest A. Love Field (KPRC), Prescott, AZ
Aircraft age
About 76 years (built 1939)
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
Runway excursion
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 systems
  • 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 commercial pilot of the tailwheel-equipped airplane stated that, upon touching down in a three-point attitude, the airplane veered left. The pilot attempted to correct with rudder, but the airplane continued left and ground looped. Examination revealed that the tailwheel had rotated 180°, leaving its control chains crossed over one another. Under this condition, the tailwheel direction of movement would be opposite that commanded by the pilot. Further examination revealed that the tailwheel steering arms were bent upward, allowing the wheel to rotate past its travel stops and into the reversed condition. It is likely that, as the pilot initially lost control and the airplane began to ground loop, the wheel passed beyond its travel limits, causing the controls to become reversed, which made recovery unlikely.

Probable cause

The pilot's failure to maintain directional control during landing, and his inability to recover due to a malfunction of the tailwheel.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR16LA017
Event ID
20151025X53618
Case number
WPR16LA017
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. 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: ac689a00f9383768b13b2a74885ee2e9be815e7d50eca76c55c747a066fe50cb; retrieved 2026-09-16T02:55:14.439Z.