CHI98LA258 · Piper PA-28-181
Piper PA-28-181 · Accident: total loss of engine power (non-mechanical) on approach
From 3R3 · Austin, TX to Downtown Airport (3DW)
Event
- NTSB case
- CHI98LA258
- 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
Piper PA-28-181
- Aircraft type
- Piper PA-28
- 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
- N2953Y
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 3R3 · Austin, TXTo Downtown Airport (3DW), Springfield, MO
- 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
- Approach
- 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)
- 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
- Pilot in command › Fuel consumption calculations, inaccurate
- Pilot in command › Fuel supply, exceeded
- Pilot in command › Preflight planning/preparation, inadequate
Approximate · Estimated position: the centre of Springfield, MO, the place the record names. Not the accident site.
NTSB narrative
The pilot stated that while he was in contact with approach control, the engine quit suddenly, he switched tanks, and the engine restarted without hesitation. The pilot notified approach control of his fuel situation and approach control communicated to the pilot that he was flying directly over the airport. The pilot stated that he still did not have visual contact with the airport. The engine quit, for the second time, and the pilot executed a forced landing into a field. The pilot stated that he used 3 notches of flaps, tried to keep the wings level, and was aware of some trees that were at the beginning of the field he had selected. The aircraft came to rest on some railroad tracks. Post accident investigation showed that the pilot had been flying for at least 4 hours and 4 minutes at the time of the first engine failure. The fuel tanks were drained, with 1.5 pints of fuel being drained from each wing tank. There was no evidence of a fuel spill at the accident site and the fuel tanks were not compromised during the forced landing. There were no other anomalies found with the aircraft, flight controls, or engine.
Probable cause
the pilot in command's inadequate preflight planning/preparation and inaccurate fuel consumption calculations that caused the aircraft's fuel supply to be exceeded. Factors to the accident were the dark light condition and the rough/uneven terrain condition.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI98LA258
- Event ID
- 20001211X10510
- Case number
- CHI98LA258
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1998-07-17.
- API snapshot SHA-256: 4cea12b9b895a0eac3d5d44f2b6d64f82367f0925ba11dd0c098e88556d09cb5; retrieved 2026-09-22T17:26:24.856Z.