FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

BFO94LA053 · Piper PA-24- 260

28 Feb 1994 · Stow, MA, United States

Piper PA-24- 260 · Accident: total loss of engine power (non-mechanical) during initial climb

From an unrecorded airport to Minute Man Air Field (6B6)

Report a problem

Event

NTSB case
BFO94LA053
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-24- 260

Aircraft type
Piper PA-24
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
N9322P
Operator
Stumpf, Bernard · private individual
Onboard fatalities
Unknown
Route
From not recordedTo Minute Man Air Field (6B6)
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
Initial climb
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 starvation
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 › Starvation
  • Pilot in command › Checklist, not followed

Approximate · Estimated position: the centre of Stow, MA, the place the record names. Not the accident site.

NTSB narrative

THE PRIVATE PILOT AND A PASSENGER WERE TAKING OFF ON RUNWAY 3 DURING A DARK NIGHT WHEN THE ENGINE LOST POWER AT 100 FEET ABOVE THE GROUND. THE PILOT STATED THAT DUE TO INSUFFICIENT ALTITUDE HE WAS UNABLE TO RESTART THE ENGINE. THE AIRPLANE IMPACTED TREES IN A WOODED AREA. ACCORDING TO THE PILOT HE HAD FLOWN THE AIRPLANE EARLIER FOR ABOUT AN HOUR ON THE RIGHT AUXILIARY TANK. HE STATED THAT HE LANDED AND PICKED UP A PASSENGER. THE PILOT STATED THAT HE COMPLETED AN ABBREVIATED CHECKLIST WHICH INCLUDED CHECKING THE POSITION OF THE FUEL PUMP AND FUEL SELECTOR. HE STATED THAT HE THOUGHT THE FUEL SELECTOR WAS ON 'A MAIN TANK.' AN FAA AVIATION SAFETY INSPECTOR WHO EXAMINED THE AIRPLANE AFTER THE ACCIDENT FOUND THE FUEL SELECTOR ON THE RIGHT AUXILIARY FUEL TANK WHICH WAS EMPTY. THE PILOT REPORTED THAT THERE WAS NO MECHANICAL MALFUNCTION AND THE ACCIDENT COULD HAVE BEEN PREVENTED IF A MORE DELIBERATE CHECK OF THE STATUS OF THE FUEL SELECTOR WAS ACCOMPLISHED.

Probable cause

THE PILOT'S FAILURE TO FOLLOW THE CHECKLIST WHICH RESULTED IN FUEL STARVATION AND SUBSEQUENT LOSS OF ENGINE POWER. THE LACK OF SUITABLE TERRAIN TO COMPLETE A FORCED LANDING WAS A FACTOR.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record BFO94LA053
Event ID
20001206X00717
Case number
BFO94LA053
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: 0ae32a907c4e741d1b0be2f60bf8ca60c5053e069c16a537e82284e7beed72a0; retrieved 2026-09-23T01:18:07.238Z.