FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX82FA236 · Cessna 182

26 Jun 1982 · TRINITY CENTER, CA, United States

Flying Country Club Cessna 182 · Accident: in flight encounter with weather en route

From an unrecorded airport to C · San Jose, CA

Report a problem

Event

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

Cessna 182

Aircraft type
Cessna 182
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
N759NE
Onboard fatalities
Unknown
Route
From not recordedTo C · San Jose, 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 › VFR flight into imc, continued

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

NTSB narrative

THE PLT CONTACTED THE REDDING, CA TOWER & STATED HE WAS ON TOP & 41 MI FROM THE REDDING VOR. HE THEN REPORTED HE WAS GOING INTO THE CLOUDS & REQUESTED RADAR SERVICE. HE THEN CONTACTED OAKLAND ARTCC WHO PROVIDED ASSISTANCE UNTIL THE PLT STATED HE HAD FOUND A HOLE & WAS GOING DOWN NEAR THE TRINITY CENTER ARPT. RADAR & RADIO CONTACT WERE LOST AS THE ACFT DESCENDED BELOW ARTCC COVERAGE. THE PLT OF ANOTHER ACFT WAS ASKED TO RELAY TRANSMISSIONS & REPORTED THAT THE C-182 WAS OVER THE LAKE LOOKING FOR THE RWY. AT 1812 THE OTHER PLT RELAYED THAT THE C-182 WAS GOING TO CLIMB BACK UP & THAT IT WAS "SQUIRRELY" DOWN THERE. THE ACFT CRASHED IN MOUNTAINOUS TERRAIN AT THE 6,500 FT ELEVATION OF A 7,000 FT PEAK. THE WX IN THE AREA WAS REPORTED AS HAZY & FOGGY WITH THE MOUNTAINS OSCURED.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record LAX82FA236
Event ID
20020917X03667
Case number
LAX82FA236
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 1982-06-27.
  • API snapshot SHA-256: ba54c6fc18610a3959536d30d2e7c575d24d6b7875f047201569044e0d4489e9; retrieved 2026-09-21T08:09:59.642Z.