FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX83FA438 · Piper PA-32R-301

27 Jan 1983 · Redlands, CA, United States

Piper PA-32R-301 · Accident: in flight encounter with weather en route

From Tucson International Airport (TUS) to Sacramento International Airport (SMF)

Report a problem

Event

NTSB case
LAX83FA438
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
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
Unknown

Piper PA-32R-301

Aircraft type
Piper PA-32
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
N8139D
Operator
Unknown
Onboard fatalities
Unknown
Route
From Tucson International Airport (TUS), Tucson, AZTo Sacramento International Airport (SMF), Sacramento, 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
En route · cruise
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
In flight encounter with weather
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
Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
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 › Aircraft handling, not maintained
  • Pilot in command › In-flight planning/decision, improper
  • Pilot in command › Spatial disorientation
  • Pilot in command › VFR flight into imc, continued

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

NTSB narrative

AT 0638 PST, THE PLT RECEIVED A WX BRIEFING ON A FLT TO SACRAMENTO, CA, AND WAS ADVISED THAT VFR WAS NOT RECOMMENDED. AT 0800, HE RECEIVED ANOTHER BRIEFING & FILED A VFR FLT PLAN TO PALM SPRINGS, CA. DURING FLT, HE ADVISED PALM SPRINGS TOWER THAT IF HE COULD GET THRU THE WX, HE INTENDED TO CONTINUE ON TO SACRAMENTO. RADIO & RADAR CONTACT WERE LOST APRX 7 MI WEST OF THE ARPT AT 2500 FT MSL. WHEN THE ACFT DID NOT ARRIVE AT ITS DESTINATION, A SEARCH WAS BEGUN; HOWEVER, IT WAS NOT FOUND UNTIL 9/13/83. THE ACFT WAS FOUND BY HIKERS APRX 15 MI NORTHWEST OF REDLANDS , CA AT AN ELEVATION OF ABOUT 6600 FT. AN EXAM OF THE WRECKAGE REVEALED THAT THE ACFT HAD CRASHED IN AN INVERTED, NOSE DOWN ATTITUDE IN MOUNTAINOUS TERRAIN. MOUNTAIN TOPS IN THE AREA RANGED FROM 10,831 TO 11,502 FT MSL. CLOUD BASES WERE REPORTED AT 2700 FT. ACCORDING TO THE PLT'S LOG BOOK, HE HAD FLOWN 5 HRS IN 1974, 1.4 HRS IN 1982 & 11.7 HRS IN 1983. THE CFI THAT CHECKED HIM OUT IN THE ACFT NOTED THAT IFR FLT WAS NOT RCMDD TIL HE RECEIVED MORE DUAL INSTRUCTION.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record LAX83FA438
Event ID
20001214X42016
Case number
LAX83FA438
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: 937200e99930154e0109696c7c2246e521fffacfb0cf2d4b61145cf633685ff3; retrieved 2026-09-21T07:15:29.909Z.