FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI08CA005 · Piper PA-18-150

4 Oct 2007 · Hot Springs, AR, United States

Piper PA-18-150 · Accident: total loss of engine power (mechanical failure) en route

From Memorial Field Airport (HOT) to North Little Rock Municipal Airport (ORK)

Report a problem

Event

NTSB case
CHI08CA005
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

Piper PA-18-150

Aircraft type
Piper PA-18
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
N4157R
Operator
Unknown
Onboard fatalities
Unknown
Route
From Memorial Field Airport (HOT), Hot Springs, ARTo North Little Rock Municipal Airport (ORK), North Little Rock, AR
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 (mechanical failure)
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

  • Fuel system › Starvation/exhaustion
  • Pilot in command › Altitude, low
  • Pilot in command › Fuel consumption calculations, inadequate
  • Pilot in command › Unsuitable terrain or takeoff/landing/taxi area, improper

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane received substantial damage during a forced landing on a lake. The pilot reported a total loss of engine power while maneuvering over a lake at 300-500 feet above ground level. Post-accident examination revealed no fuel in the left fuel tank and a mixture of water and fuel in the right fuel tank. The fuel selector was selected to the left tank. There was no fuel found in the gascolator. The airplane rudder was "folded" over. The pilot reported minor injuries.

Probable cause

The total loss of engine power due to inadequate fuel consumption calculations by the pilot resulting in fuel starvation while maneuvering over a lake at too low altitude for a safe landing. An additional cause was the unsuitable terrain encountered during landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI08CA005
Event ID
20080103X00012
Case number
CHI08CA005
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: c3f8e64e1f0204f5193795f0df74aa96485cd02c9ce47ea8d41e1035fba85e32; retrieved 2026-09-21T18:22:47.643Z.