FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN00LA003 · Piper PA-12

2 Oct 1999 · Las Cruces, NM, United States

Piper PA-12 · Accident: loss of control on ground/water during landing

From El Paso International Airport (ELP) to Las Cruces International Airport (LRU)

Report a problem

Event

NTSB case
DEN00LA003
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
0
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

Piper PA-12

Aircraft type
Piper PA-12
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
N2493M
Operator
Unknown
Onboard fatalities
Unknown
Route
From El Paso International Airport (ELP), El Paso, TXTo Las Cruces International Airport (LRU)
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 › Ground loop/swerve, inadvertent

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

NTSB narrative

The pilot said that while on final approach to runway 26, engine power remained too high even though the throttle had been completely retarded. On the second approach, engine power was still too high even with the throttle closed. He initiated a second go around and when the airplane was 50 feet above the ground, the mixture control was slowly moved towards idle cutoff 'to decrease power.' The airplane touched down at high speed. Directional control was lost when the pilot became distracted, and the airplane ground looped to the right. The left wing buckled when it struck the runway, and the side loads tore off the left main landing gear and damaged the right main landing gear. It was later discovered that the clamp securing the throttle sleeve to the throttle housing had come loose, allowing the sleeve (not the cable) to move when the throttle control was operated.

Probable cause

The pilot's inadvertent ground loop/swerve during landing. A factor was his attention being diverted by a malfunctioning throttle control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DEN00LA003
Event ID
20001212X19940
Case number
DEN00LA003
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. 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: 8c49406162ad993cf47536045d7d320104335ae99ce042a7f0de43741f71a153; retrieved 2026-09-22T13:58:12.903Z.