FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI94LA096 · Piper PA-28-180

2 Mar 1994 · Lindsborg, KS, United States

Piper PA-28-180 · Accident: total loss of engine power (non-mechanical) en route

From Town & Country Airpark (F82) to Salina Municipal Airport (SLN)

Report a problem

Event

NTSB case
CHI94LA096
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-180

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
N3592R
Operator
Unknown
Onboard fatalities
Unknown
Route
From Town & Country Airpark (F82), Lubbock, TXTo Salina Municipal Airport (SLN), Salina, KS
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

  • Pilot in command › Refueling, not performed

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

THE AIRPLANE WAS IN CRUISE FLIGHT WHEN THE ENGINE LOST POWER. THE PILOT SWITCHED FUEL TANKS SEVERAL TIMES IN AN ATTEMPT TO REGAIN POWER. HE WAS UNABLE TO SUSTAIN ENGINE POWER AND RESORTED TO A FORCED LANDING ON A ROAD, WHERE THE WING STRUCK A SIGN. SUBSEQUENT INVESTIGATION REVEALED ONLY UNUSABLE FUEL REMAINING IN THE TANKS. THE PILOT STATED THAT HE THOUGHT THAT HE HAD FIVE HOURS OF FUEL ON BOARD THE AIRPLANE FOR THE INTENDED FLIGHT, BUT AFTER 4.4 HOURS ON THE HOBBS METER THE ENGINE BEGAN TO LOSE POWER FROM FUEL EXHAUSTION.

Probable cause

was the pilot-in-command's failure to refuel the airplane during the flight. Factors were fuel exhaustion, the sign, and the pilot-in-command's lack of total experience in type of airplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI94LA096
Event ID
20001206X00862
Case number
CHI94LA096
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: 16b592c6f47b3bda78dc9f83dafbe771aec9bb06a44cbf486dd33788f4f310b8; retrieved 2026-09-23T01:17:56.881Z.