FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR22LA144 · Piper PA-28-151

19 Mar 2022 · Alpine, CA, United States

Piper PA-28-151 · Accident: collision with terrain/object (non-CFIT) while maneuvering

From Gillespie Field (SEE) to an unrecorded destination

Report a problem

Event

NTSB case
WPR22LA144
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

Piper PA-28-151

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
N42764
Onboard fatalities
Unknown
Route
From Gillespie Field (SEE), El Cajon, CATo not recorded
Aircraft age
About 48 years (built 1974)
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 · low-altitude flying
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
Collision with terrain/object (non-CFIT)
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 › Action/decision
  • Personnel issues › Psychological

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot reported that, he entered a valley and descended to an altitude of about 300 to 500 ft above the ground. As the pilot began a climb to clear an upcoming ridgeline, he realized that the airplane would not clear the terrain despite making S-turns and adjusting to best rate of climb airspeed. Subsequently, he initiated an emergency landing and the airplane impacted terrain in a level attitude, which substantially damaged the left wing and underside of the airplane. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

Probable cause

The pilot’s failure to maintain clearance from rising terrain while operating in a canyon, which resulted in an impact with terrain

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR22LA144
Event ID
20220406104898
Case number
WPR22LA144
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: 8a1c7d3d5751feb79c5998115832e862c506c4400be3ab36cbfce945f84a2055; retrieved 2026-09-16T15:06:31.827Z.