IAD98LA055 · Cessna 177B
Cessna 177B · Accident: total loss of engine power (non-mechanical) en route
From Evansville Regional Airport (EVV) to Mid Ohio Valley Regional Airport (PKB)
Event
- NTSB case
- IAD98LA055
- 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 177B
- Aircraft type
- Cessna 177
- 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
- N904DS
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Evansville Regional Airport (EVV), Evansville, INTo Mid Ohio Valley Regional Airport (PKB), Parkersburg, WV
- 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
- Total loss of engine power (non-mechanical)
- 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 exhaustion
- 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 › Exhaustion
- Pilot in command › Aircraft preflight, inadequate
- Pilot in command › Fuel consumption calculations, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Two pilots departed without visually verifying the quantity of fuel in the fuel tanks. During climbout, the pilots noted the right fuel quantity indicator '...was all the way on 'E', the left read three-quarters.' The pilot selected the right tank position on the fuel selector and flew for 50 minutes. He said this satisfied his suspicion that the right fuel gauge was inaccurate. The pilot said he then flew from the left tank to balance the fuel load and ultimately switched the selector to 'Both.' While in cruise flight at 9,000 feet, after approximately 2 hours of flight time, the engine stopped producing power. During a subsequent forced landing on uneven terrain, the airplane nosed over. There was no evidence of fuel at the scene. After the accident, an FAA Inspector started and ran the engine on the airframe. After reviewing his records and fuel receipts, the co-pilot/owner stated the airplane operated to its fuel endurance.
Probable cause
the pilot's inadequate preflight inspection and the inadequate fuel consumption calculations, which resulted in fuel exhaustion, loss of engine power, and a forced landing. Uneven terrain in the forced landing area was a related factor.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD98LA055
- Event ID
- 20001211X10106
- Case number
- IAD98LA055
- 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: 3f4d8b6d30d78ae0d80faf001aa3d8a6d08ae3eb8fa9b17f3ef156bfe30c6d2b; retrieved 2026-09-22T17:48:44.859Z.