LAX08LA128 · Cessna 175A
Cessna 175A · Accident: powerplant system/component malfunction/failure en route
From Rio Linda Airport (L36) to Willows Glenn County Airport (WLW)
Event
- NTSB case
- LAX08LA128
- 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 175A
- Aircraft type
- Cessna 175
- 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
- N7059E
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Rio Linda Airport (L36), Rio Linda, CATo Willows Glenn County Airport (WLW), Willows, 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 · cruise
- Defining eventThe 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
- Powerplant system/component malfunction/failure
- 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
- Substantial
Cause areas
- Aircraft › Aircraft power plant
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot and owner of the airplane reported that during cruise flight, the engine partially lost power followed by several backfires. The pilot was unable to maintain altitude at the reduced power setting, and initiated a forced landing to a gravel road. During the landing roll on the gravel road, the left and right wings struck trees located on the edge of the road, resulting in structural damage to both wings. The owner of the airplane reported that during disassembly of the engine, the number four cylinder exhibited "signs of detonation." The number four piston head was "eaten away" to the top ring land. No additional anomalies were noted with the engine. The underlying reason for the detonation was undetermined.
Probable cause
The partial loss of engine power due to detonation. Contributing to the accident was trees in the landing area.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX08LA128
- Event ID
- 20080508X00637
- Case number
- LAX08LA128
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 3daefe5935e6f3d007386b2aac141f75c3cac01d54be172bf00938fee7fc3858; retrieved 2026-09-15T09:38:15.730Z.