FTW98LA069 · Cessna 172N
Cessna 172N · Accident: loss of engine power en route
From Stuttgart Municipal Airport / Carl Humphrey Field (SGT) to Tokeen Seaplane Base (TKI)
Event
- NTSB case
- FTW98LA069
- 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 172N
- 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
- N1371E
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Stuttgart Municipal Airport / Carl Humphrey Field (SGT), Stuttgart, ARTo Tokeen Seaplane Base (TKI)
- 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
- 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; 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
- Fluid, fuel › Exhaustion
- Pilot in command › In-flight planning/decision, inadequate
- Pilot in command › Refueling, not performed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
A total loss of engine power occurred during the final descent to the destination airport. Fluctuation of the fuel quantity gauges was reported by the pilot. The pilot planned the cruise flight at 75 percent power and leaned the mixture by using the EGT gauge. A passenger reported the aircraft 'ran out of fuel.' There was no evidence of fuel at the accident site. The company mechanic had informed the pilot that the engine would run lean and that fuel consumption for the airplane varied from 8 gph to 12 gph. The total cross country flight time was calculated at 5 hours and 11 to 19 minutes. According to the Pilot's Operating Handbook, the endurance at 75 percent cruise power is approximately 5 hrs 24 minutes. No pre-existing mechanical anomalies were found that would have precluded engine producing power. Testing of the fuel sending units revealed inaccuracy of the cockpit fuel gauge readings.
Probable cause
The pilot's inadequate in-flight/planning decision which resulted in continued flight until fuel exhaustion. Related factors were incorrect fuel gauge readings and trees.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW98LA069
- Event ID
- 20001208X09307
- Case number
- FTW98LA069
- 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: baa275ddf2e031cb592612f06f9e531ac4c646ce2b328873f52089a9f4a3b840; retrieved 2026-09-21T11:42:47.647Z.