FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX91FA333 · Piper PA 28-181

28 Jul 1991 · Sonora, CA, United States

West Valley Flying Club Piper PA 28-181 · Accident: loss of control in flight while maneuvering

From Palo Alto Airport (PAO) to Q82 · MARKLEEVILLE, CA

Report a problem

Event

NTSB case
LAX91FA333
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
3 · 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 28-181

Aircraft type
Piper PA-28
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
N82716
Onboard fatalities
Unknown
Route
From Palo Alto Airport (PAO), Palo Alto, CATo Q82 · MARKLEEVILLE, CA
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; Tree(s)
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

  • Aircraft performance, climb capability › Exceeded
  • Pilot in command(cfi) › Airspeed(vs), not maintained

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

NTSB narrative

A CERTIFICATED FLIGHT INSTRUCTOR AND TWO CERTIFICATED PRIVATE PILOTS WERE PARTICIPATING IN A MOUNTAIN FLYING TRAINING SEMINAR AS PART OF A THREE AIRPLANE FLIGHT. THE ACCIDENT AIRPLANE WAS OBSERVED FOLLOWING A HIGHWAY UP A CANYON TOWARDS A 9,600 FOOT MOUNTAIN PASS. THE AIRPLANE WAS OBSERVED ABOUT 200 FEET ABOVE THE GROUND, BELOW SURROUNDING CANYON WALLS. THE TERRAIN RISES RAPIDLY AT THE END OF THE CANYON. THE AIRPLANE WAS OBSERVED TO MAKE A LEFT TURN AWAY FROM HIGH TERRAIN, PULL UP INTO A NOSE HIGH ALTITUDE, AND DESCEND FROM VIEW. THE AIRPLANE WAS FOUND TO HAVE STRUCK A PINE TREE WITH THE RIGHT WINGTIP, STRIKE ANOTHER TREE, AND THEN COLLIDE WITH A LARGE ROCK OUTCROPPING AT ABOUT 9,000 FEET MEAN SEA LEVEL. AN INTENSE POST IMACCT FIRE CONSUMED ALMOST ALL OF THE AIRPLANE WITH THE EXCEPTION OF PORTIONS OF THE LEFT WING AND TAIL. THE DENSITY ALTITUDE WAS ABOUT 12,000 FEET.

Probable cause

FAILURE OF THE FLIGHT INSTRUCTOR/PILOT-IN-COMMAND TO ADEQUATELY SUPERVISE THE FLIGHT AND TO MAINTAIN ADEQUATE AIRSPEED BY EXCEEDING THE CLIMB PERFORMANCE OF THE AIRPLANE. CONTRIBUTING TO THE ACCIDENT WAS THE PILOT-IN-COMMAND'S INADEQUATE PLANNING AND HIS SELECTION OF AN IMPROPER ALTITUDE FOR FLIGHT INTO RISING TERRAIN DURING HIGH DENSITY ALTITUDE CONDITIONS.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX91FA333
Event ID
20001212X17576
Case number
LAX91FA333
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: 9f1d776ccf9e96ae9c900b63f9fe4b2084da07653e1469709dfe2b5058598b25; retrieved 2026-09-21T01:40:19.360Z.