LAX89LA126 · Cessna 172
Buchanon Flying Club Cessna 172 · Accident: loss of engine power en route
From Buchanan Field (CCR) to an unrecorded destination
Event
- NTSB case
- LAX89LA126
- 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
- N51313
- Operator
- Buchanon Flying Club
- Onboard fatalities
- Unknown
- Route
- From Buchanan Field (CCR), Concord, CATo not recorded
- 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
- Loss of engine power
- 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
- Wire, transmission
- 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 › In-flight planning/decision, poor
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT OF A C172 FLEW INTO A TELEPHONE WIRE, LOST CONTROL OF THE AIRPLANE AND COLLIDED WITH THE TERRAIN WHILE EXECUTING A SIMULATED FORCED LANDING APPROACH TO A FIELD ABOUT 8 MILES WEST OF RIO VISTA, CA. THE PILOT STATED THAT HE WAS SHOWING HIS PASSENGERS SIMULATED FORCED LANDING APPROACH TO AN OPEN FIELD. WHILE IN A DESCENT, BOTH OF THE PILOTS AND THE PASSENGER SAW A TELEPHONE WIRE IN THEIR FLIGHT PATH (AT ABOUT 75 FEET ABOVE GROUND LEVEL). THE PRIVATE PILOT WAS UNABLE TO AVOID THE WIRE. THE AIRPLANE'S MAIN LANDING GEAR CLEARED THE WIRE BUT, THE RIGHT SIDE OF THE HORIZONTAL STABILIZER CAUGHT THE WIRE. THE PRIVATE PILOT LOST CONTROL OF THE AIRPLANE AND COLLIDED WITH THE TERRAIN. THERE WAS NO REPORTED MECHANICAL MALFUNCTION OR FAILURE TO THE AIRPLANE, PRIOR TO THE ACCIDENT.
Probable cause
THE IMPROPER PLANNING AND EXECUTION OF AN EMERGENCY (SIMULATED) MANEUVER BY THE PILOT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX89LA126
- Event ID
- 20001213X27919
- Case number
- LAX89LA126
- 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 1989-03-16.
- API snapshot SHA-256: 528ccd540f22a7c034cab258e76259750f610b59cd3d2ee9171ca4151a36a263; retrieved 2026-09-22T00:16:10.555Z.