FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR13FA010 · Piper PA-28-151

14 Oct 2012 · Marana, AZ, United States

Piper PA-28-151 · Accident: loss of control in flight en route

From Benson Municipal Airport/Paul Kerchum Field (E95) to Imperial County Airport (IPL)

Report a problem

Event

NTSB case
WPR13FA010
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
1 · 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-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
N151SV
Operator
Unknown
Onboard fatalities
Unknown
Route
From Benson Municipal Airport/Paul Kerchum Field (E95), Benson, AZTo Imperial County Airport (IPL), Imperial, CA
Aircraft age
About 38 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
En route · cruise
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
Loss of control in flight
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

  • Personnel issues › Psychological

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

NTSB narrative

During a night cross-country flight, the airplane collided in the unpopulated desert located in between the departure and destination airports. The non-instrument-rated pilot had amassed an estimated 185 hours of total flight experience, of which 7.3 hours were conducted in nighttime conditions. Although the pilot had made this trip twice before, those flights were not conducted in dark night conditions. For the first 30 minutes after departure, radar returns for the flight were uniformly spaced and at uniform altitudes, with the track was consistent with a route of flight toward the destination airport. About 4 minutes before the end of the data, radar returns indicate a period consistent with the airplane making a series of turns with fluctuations in altitude. The maneuvering and altitude variations were inconsistent with the intended route of flight, and along with the pilot's inexperience in night time conditions, he likely experienced the effects of spatial disorientation as the accident occurred in an area devoid of visual references. Ground scar analysis, impact signatures, and wreckage fragmentation patterns disclosed that the airplane impacted terrain in a slightly nose-low attitude with high forward velocity.

A review of the pilot's daily work activities revealed that he had not obtained his normal amount of rest before the accident and was likely fatigued; however, the effect the fatigue would have had on his operation of the airplane could not be determined. A postaccident examination of the airframe and engine revealed no evidence of a mechanical malfunction or failure that would have precluded normal operation.

Probable cause

The pilot’s flight in dark night conditions with no visual reference and his subsequent spatial disorientation.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR13FA010
Event ID
20121015X22823
Case number
WPR13FA010
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2012-10-15.
  • API snapshot SHA-256: 0ebd96b8009e47c5452cdaec39843bdb5476177f06ff0eea310d8dab23622240; retrieved 2026-09-14T15:46:03.247Z.