SEA03LA069 · Cessna 175B
Cessna 175B · Accident: loss of engine power en route
From Wellington, NV to Crater Lake-Klamath Regional Airport (LMT)
Event
- NTSB case
- SEA03LA069
- 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 175B
- 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
- N8159T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Wellington, NVTo Crater Lake-Klamath Regional Airport (LMT), Klamath Falls, OR
- 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
- 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
- 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
- Engine assembly, connecting rod cap › Separation
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that while in cruise flight the engine made a loud sound followed by a partial loss of engine power. Shortly thereafter, smoke started coming in the cockpit and the engine lost complete power. The pilot initiated a forced landing to a county road. During the landing roll, the left wing collided with a power pole. The airplane spun around, the nose gear collapsed and the airplane subsequently nosed over. During the engine inspection, a large hole was found in the crankcase between the number 1 and 2 cylinders. The number 1 connecting rod bearing journal was deeply scored, blue in color and dry. Portions of the number 1 main bearing insert could be observed between the number 1 crank cheek and the number 1 main bearing saddle. The numbers 1 and 2 crank cheeks were blue in color and dry. The number 1 connecting rod was in pieces. The connecting rod cap had a portion of one bolt still present in the cap. The fracture area of the bolt was necked down in diameter and the bolt was blue in color. A matching portion of a bolt with the nut attached was recovered and noted that the fracture area was also necked down in diameter. The pilot reported that the maintenance logbooks had been destroyed in a hangar fire. The pilot also reported that the aircraft had not been maintained in accordance with an annual inspection for some time, as he had not been flying the aircraft since about 1997, when the engine was top overhauled.
Probable cause
Separation of the connecting rod cap. Annual maintenance inspections which were disregarded by the owner/pilot was a factor.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA03LA069
- Event ID
- 20030425X00574
- Case number
- SEA03LA069
- 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, coordinates. 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: 22d5305dc54aad9e5f41a9673b810622774d390eea44ca98548de59949e7b319; retrieved 2026-09-21T19:30:23.480Z.