LAX84FA002 · Cessna 182M
Cessna 182M · Accident: in flight encounter with weather en route
From Crater Lake-Klamath Regional Airport (LMT) to Salt Lake City International Airport (SLC)
Event
- NTSB case
- LAX84FA002
- 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
- Visual Meteorological Cond
Cessna 182M
- 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
- N92019
- Operator
- Micheal Wood
- Onboard fatalities
- Unknown
- Route
- From Crater Lake-Klamath Regional Airport (LMT), Klamath Falls, ORTo Salt Lake City International Airport (SLC), Salt Lake City, UT
- 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
- Stall
- 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 › Flight into known adverse weather, initiated
- Pilot in command › In-flight planning/decision, improper
- Pilot in command › Preflight planning/preparation, misjudged
- Pilot in command › Stall, uncontrolled
- Pilot in command › Weather evaluation, inattentive
- Wing › Ice
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT COLLIDED WITH THE TERRAIN IN A HIGH SPEED WINGS LEVEL DESCENT AT NIGHT AFTER ENCOUNTERING WEATHER AND ICING AT FLT LEVEL OF 13000 FT. THE PLT WAS IN CONTACT WITH SALT LAKE CENTER UNTIL 5 MINUTES BEFORE RADAR CONTACT WAS LOST AND GAVE NO INDICATION OF TROUBLE EXCEPT 'IN THE CLOUDS AND LIGHT ICE.' EARLIER HE HAD DESCRIBED ST ELMOS FIRE TO THE CENTER. HIS LAST CONTACT WAS A REQUEST FOR HIS NOTED GROUND SPEED FROM RADAR. IT WAS 120 KTS ACCORDING TO SALT LAKE ARTCC. DURING THE ON SITE EXAMINATION OF THE ACFT WRECKAGE FLT CONTROL CONTINUITY PRIOR TO IMPACT COULD NOT BE ESTABLISHED. THE COCKPIT SWITCHES/CONTROL POSITIONS WERE DESTROYED. THE ENGINE WAS DISASSEMBLED AND NO EVIDENCE WAS FOUND OF PRE-IMPACT FAILURE OR MALFUNCTION.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX84FA002
- Event ID
- 20001214X44862
- Case number
- LAX84FA002
- 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 1983-10-02.
- API snapshot SHA-256: 5b1b1fec43456c85dc0afff145b41c732fb5c769493fc4bfa2226b63b1b8b8c3; retrieved 2026-09-21T06:05:07.443Z.