FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI95LA111 · Baker LONG EZE

27 Mar 1995 · Salina, KS, United States

Baker LONG EZE · Accident: total loss of engine power (mechanical failure) en route

From Hampton Municipal Airport (HPT) to Dalhart Municipal Airport (DHT)

Report a problem

Event

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

Baker LONG EZE

Aircraft type
Baker LONG EZE
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
N3223P
Operator
Unknown
Onboard fatalities
Unknown
Route
From Hampton Municipal Airport (HPT), Hampton, IATo Dalhart Municipal Airport (DHT), Dalhart, TX
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, pump › Cracked

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

NTSB narrative

THE PILOT REPORTED HE FILLED BOTH FUEL TANKS PRIOR TO DEPARTURE. HE WAS CRUISING AT 800 FEET ABOVE GROUND LEVEL WHEN THE ENGINE LOST POWER. HE SWITCHED FUEL TANKS AND TURNED THE ELECTRIC FUEL BOOST PUMP ON. THE ENGINE STOPPED WINDMILLING. HE LOWERED THE NOSE GEAR AND ATTEMPTED TO RESTART THE ENGINE WITH THE STARTER TO NO AVAIL. THE PILOT INITIATED A FORCED LANDING TO A GRAVEL ROAD BUT HAD INSUFFICIENT ALTITUDE. HE LANDED SHORT OF THE ROAD IN A SOFT FIELD. THE NOSE GEAR COLLAPSED AND THE AIRPLANE NOSED OVER. INSPECTION OF THE WRECKAGE REVEALED THE DIAPHRAGM IN THE ENGINE DRIVEN FUEL PUMP WAS CRACKED. NO OTHER EVIDENCE OF A PRE-EXISTING MALFUNCTION WAS FOUND.

Probable cause

failure of the engine driven fuel pump. Factors associated with the accident were fuel starvation, insufficient altitude and soft terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI95LA111
Event ID
20001207X03102
Case number
CHI95LA111
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: a0caf5aa343ab0af48484f7cffc3506ef27513756d7c05e5482f71521c0f33dc; retrieved 2026-09-21T22:21:44.633Z.