LAX01LA193 · Cessna 177RG
Cessna 177RG · Accident: in flight collision with terrain/water on approach
From Borrego Valley Airport (L08) to 95L · Pauma Valley, CA
Event
- NTSB case
- LAX01LA193
- 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
- Unknown
- 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 177RG
- Aircraft type
- Cessna 177
- 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
- N8287G
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Borrego Valley Airport (L08), Borrego Springs, CATo 95L · Pauma Valley, 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
- Approach · VFR pattern downwind
- 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
- 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
- Substantial
Cause areas
- Pilot in command › Clearance, not maintained
- Pilot in command › VFR flight into imc, intentional
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The instrument-rated pilot stated that he was descending in visual flight rules conditions, and was on the extended downwind leg for landing at the destination airport. He intentionally flew into the top of what appeared to be an isolated, "puffy" cloud, expecting to be in the cloud only briefly and to see the runway again on the other side. The cloud was more expansive than he anticipated and the airplane continued to descend in the cloud for a period of time until the pilot saw vegetation on a mountainside a short distance in front of them. The pilot took evasive action and the airplane impacted upsloping mountainous terrain and slid to a stop through heavy sagebrush.
Probable cause
The pilot's intentional flight into instrument meteorological conditions and failure to maintain clearance from terrain during an approach for landing under visual flight rules.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX01LA193
- Event ID
- 20010530X01029
- Case number
- LAX01LA193
- 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: 610c234e6e58e6210cf4a63de01f9a0d43a741b3a344b674db4299c0e4004228; retrieved 2026-09-21T19:56:38.585Z.