LAX97LA064 · Cessna 172
Cessna 172 · Accident: on ground/water collision with object during landing
From L39 · Ramona, CA to L35
Event
- NTSB case
- LAX97LA064
- 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
- N1042G
- Operator
- Gary W. Buscombe · private individual
- Onboard fatalities
- Unknown
- Route
- From L39 · Ramona, CATo L35
- 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
- Landing · landing roll
- 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
- On ground/water collision with object
- 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 › Compensation for wind conditions, inadequate
- Pilot in command › Proper alignment, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that while approaching the Big Bear City Airport, he monitored the AWOS and understood the wind was from 250 degrees at 5 knots. He said that during final approach to land on runway 26, he was 'fighting to keep lined up,' and the windsock was 90 degrees to the runway. During the landing flare, a gust pushed the airplane off the runway, and the airplane collided with a light stanchion. The pilot additionally reported that the accident could have been prevented had he gone around or exercised 'better crosswind landing technique.' The Big Bear City Airport AWOS reported that the wind was from 360 degrees at 9 gusting 16 knots.
Probable cause
the pilot's inadequate compensation for the wind condition, and his failure to maintain alignment with the runway. The gusty crosswind was a related factor.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX97LA064
- Event ID
- 20001208X07085
- Case number
- LAX97LA064
- 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: 2d007f7f610e0026d5831fdf54e90e057a05987b61345d4a7df9ed78038a9662; retrieved 2026-09-22T20:42:19.209Z.