FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX02FA285 · Piper PA-18A-150

14 Sept 2002 · Tucson, AZ, United States

Piper PA-18A-150 · Accident: loss of control in flight while maneuvering

From Ryan Field (RYN) to an unrecorded destination

Report a problem

Event

NTSB case
LAX02FA285
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
2 · 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

Piper PA-18A-150

Aircraft type
Piper PA-18
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
N8980D
Operator
Unknown
Onboard fatalities
Unknown
Route
From Ryan Field (RYN), Tucson, AZTo not recorded
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
Maneuvering
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 in flight
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Stall/spin
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Airspeed, not maintained

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

NTSB narrative

The aircraft collided with flat desert terrain in a steep nose down attitude. No witnesses to the accident were identified. The airplane departed from it's home base airport at 0740 for a presumed local area flight and was reported overdue on the morning of the 15th when the passenger failed to return home. The FAA issued an ALNOT for the missing airplane and it was found by a search helicopter at 1641 that afternoon. Witnesses who knew the pilot stated that he liked to land in the open desert on "sand dunes" on the large sized tundra tires he had equipped the airplane with that were designed to be used on soft unimproved surfaces. Several entries in the pilot's personal flight logbook contained notes of "practice short and soft landings in dirt." Weather data showed that during the morning hours of the 14th the conditions remained clear with generally southerly winds at less than 10 knots. No unusual meteorological phenomena were reported during this time. The accident site is in flat desert terrain composed of firm sandy soil and populated by scrub type trees up to 10 feet tall. Examination of the trees surrounding the accident site revealed no evidence of disturbance to any upper branches or trunks. The airplane sustained extensive longitudinal crush and collapse of the fuselage back to within 3 feet of the horizontal stabilizers. Ground scar impressions were noted about 15 feet from the wreckage that dimensionally and geometrically resembled the nose of the airplane and the left wing tip. No other ground disturbances were observed in the vicinity. The engine was in a shallow crater formed in the impact sequence with the engine's longitudinal axis at a 30-degree angle to the horizontal. No pre-impact mechanical malfunctions or failures were found with any airframe system or the engine. About 1/2 mile southwest of the wreckage, a large flat clear area was noted with multiple tire tracks crossing the field. The tire tracks were dimensionally similar to the main gear tires on the airplane and were spaced about the wheel width of the PA-18 series airplanes. Two sets of tracks were found with a center track approximating the geometry and dimension of the airplane's tail wheel; these tracks started, went for a distance estimated about 500 feet, where they turned around and proceeded back the opposite way until they disappeared. Two additional tracks were observed without the center track trace; these tracks were shorter in length at about 200 feet. No footprints could be discerned around any of the tracks. Assuming that the tracks represent an airplane landing or taking off, the accident site was noted to be in a location consistent with the approximate traffic pattern distance from a typical 2,000-foot landing strip at either a base-to-final or crosswind-to-downwind turn point.

Probable cause

the pilot's failure to maintain an adequate airspeed while maneuvering at low altitude, which resulted in a stall spin.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX02FA285
Event ID
20020919X05181
Case number
LAX02FA285
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: 6a880a99cdb4c02abe83994a2a558f133e97f9db4d3f2f36a409b4f41dfab978; retrieved 2026-09-20T19:49:50.146Z.