LAX85FVG02 · Cessna 172
Cessna 172 · Accident: in flight collision with object en route
From Fallon Municipal Airport (FLX) to Auburn Municipal Airport (AUN)
Event
- NTSB case
- LAX85FVG02
- 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
- Visual Meteorological Cond
Cessna 172
- Aircraft type
- Cessna 172
- 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
- N6167E
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Fallon Municipal Airport (FLX), Fallon, NVTo Auburn Municipal Airport (AUN), Auburn, 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 · descent
- 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 object
- 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
- Tree(s)
- 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
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT CRASHED INTO TREES DURING AN APPROACH TO LAND AFTER SUNSET. THE PLT STATED THAT HE WAS DESCENDING FROM 10,500 FT THRU 5000 FT WITH THE ARPT IN SIGHT AS WELL AS THE LIGHTS OF SACRAMENTO, CA. HE DOES NOT REMEMBER THE ACCIDENT BUT REMEMBERS HIS WIFE WAS ASLEEP AND THE DOG IN BACK TRIED TO GET UP FRONT, WHICH HE LATER THOUGHT UNUSUAL. THE FLT LASTED AN HOUR AND THE HEATER WAS ON DURING THE FLT BUT TESTS FOR CO2 DAYS LATER WERE INCONCLUSIVE. POST ACC EXAM OF THE ACFT EXHAUST SYSTEM SHOWED NO MALFUNCTION. THE CRASH SITE WAS AOBUT 2 MILES FROM THE ARPT. THE ACFT CRASHED INVERTED ABOUT 100 FT FROM THE FIRST TREE IMPACT POINT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX85FVG02
- Event ID
- 20001214X36224
- Case number
- LAX85FVG02
- 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 1985-04-07.
- API snapshot SHA-256: 4711912f1d5190281e82f3f3be4ccca8c0817f47118a69adf3ce2f5dfda40d21; retrieved 2026-09-21T17:19:33.181Z.