FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX91LA067 · Piper PA 34-200T

6 Jan 1991 · Red Bluff, CA, United States

Shasta Livestock Piper PA 34-200T · Accident: in flight collision with terrain/water on approach

From Roberts Field (RDM) to an unrecorded destination

Report a problem

Event

NTSB case
LAX91LA067
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
0 · 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
Instrument Meteorological Cond

Piper PA 34-200T

Aircraft type
Piper PA-34
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
N66SL
Onboard fatalities
Unknown
Route
From Roberts Field (RDM), Redmond, ORTo 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
Approach · IFR final approach
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 collision with terrain/water
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

  • Pilot in command › Minimum descent altitude, exceeded

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

NTSB narrative

THE PILOT SAID THE FLIGHT WAS NORMAL UNTIL ESTABLISHED ON THE VOR APPROACH. AFTER THE AIRCRAFT COMPLETED THE PROCEDURE TURN AND WAS INBOUND TO THE VOR THE PILOT NOTICED THAT THE AIRCRAFT WAS DESCENDING THROUGH ABOUT 1,300 FEET MSL (1,000 FEET AGL) AND THAT THE DESCENT RATE WAS STABALIZED AND WAS SUFFICIENT TO MAKE THE CROSSING RESTRICTION AT THE VOR. THE PILOT STATED THAT SHE THEN SCANNED THE VOR NAVIGATION HEADS 'FOR A FEW SECONDS' TO CROSS CHECK THE AIRCRAFT POSITION ON THE APPROACH COURSE RADIAL. SHORTLY THEREAFTER, THE AIRCRAFT FLEW INTO LEVEL TERRAIN ABOUT 1.5 MILES SOUTH OF THE AIRPORT.

Probable cause

THE FAILURE OF THE PILOT IN COMMAND TO DETECT A DESCENT BELOW THE MINIMUM DESCENT ALTITUDE FOR THE APPROACH IN USE.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX91LA067
Event ID
20001212X16328
Case number
LAX91LA067
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1991-01-07.
  • API snapshot SHA-256: ee9c456d00608203039bc1d091d639c44c39eae2cf03d3c2e6fb840246411b0d; retrieved 2026-09-23T04:57:15.879Z.