LAX97LA146 · Cessna 170B
Cessna 170B · Accident: total loss of engine power (mechanical failure) during initial climb
From an unrecorded airport to Eastern Sierra Regional Airport (BIH)
Event
- NTSB case
- LAX97LA146
- 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 170B
- Aircraft type
- Cessna 170
- 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
- N2294D
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Eastern Sierra Regional Airport (BIH), Bishop, 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
- Initial climb
- 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
- Total loss of engine power (mechanical 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
- Fuel starvation
- 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
- Fluid, fuel › Starvation
- Fuel system, selector/valve › Disconnected
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot departed with the fuel selector set to the 'both' tanks position. However, during the flight fuel appeared to have been mostly used from the right tank. To equalize the burn off, he repositioned the fuel selector to the left tank only position. Fuel continued to be consumed out of the right tank, and the engine quit when the right fuel tank gauge registered empty and the left tank gauge registered 3/4 full. The pilot made a forced landing on a road. Thereafter, the pilot examined his airplane and noted that the fuel selector handle was 'real loose.' The pilot manually siphoned between 12 and 15 gallons of fuel out of the left tank, poured it into the right tank, and took off. Several seconds into the initial climb, between 100 and 150 feet above ground level, all engine power was lost again. Unable to return to the road, the pilot made a forced landing on rough terrain. The fuel tank selector assembly was examined and its control shaft was found disconnected at its attachment to the fuel valve assembly.
Probable cause
Fuel starvation resulting from disconnection of the fuel selector valve. Factors which contributed to the accident were the pilot's intentional operation with known airplane deficiencies and the rough terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX97LA146
- Event ID
- 20001208X07746
- Case number
- LAX97LA146
- 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: a0fedc067a959ddc914032e9376680484515e2f6b8e752f8269eb4ec44c03aca; retrieved 2026-09-21T21:28:40.968Z.