FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

BFO91FA053 · Beech B65

2 Jun 1991 · California, MD, United States

Fayard Enterprise Beech B65 · Accident: loss of engine power during initial climb

From 2W6 to an unrecorded destination

Report a problem

Event

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

Beech B65

Aircraft type
Beechcraft 65
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
N655KJ
Onboard fatalities
Unknown
Route
From 2W6To not recorded
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
Loss of engine power
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Reason for occurrence undetermined

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

NTSB narrative

THE PILOT REPORTED THAT SHORTLY AFTER TAKEOFF ON A PARACHUTE JUMPING FLT THE LEFT ENGINE LOST POWER, BUT A SECOND LATER POWER WAS RESTORED. SOON AFTERWARDS A TOTAL POWER LOSS OCCURRED. ACCORDING TO THE PILOT, THE PROPELLER STOPPED ROTATING AND DID NOT WINDMILL. HE DID NOT FEATHER THE LEFT PROPELLER. HE MADE A SHALLOW LEFT TURN TOWARD AN OPEN FIELD, WHILE TRYING TO RETURN TO THE AIRPORT. HE WAS UNABLE TO MAINTAIN ADEQUATE AIRSPEED OR ALTITUDE, AND IN ORDER TO MAINTAIN AIRCRAFT CONTROL, HE REDUCED POWER ON THE RIGHT ENGGINE. HE MADE A FORCED LANDING IN A WHEAT FIELD. THE AIRPLANE CAME TO A STOP AND ALL OCCUPANTS ESCAPED THE AIRPLANE BEFORE IT CAUGHT FIRE. THE EXAMINATION OF THE AIRPLANE DID NOT DISCLOSE EVIDENCE OF MECHANICAL MALFUNCTION.

Probable cause

THE LOSS OF POWER IN ONE ENGINE FOR UNDETERMINED REASONS.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record BFO91FA053
Event ID
20001212X17177
Case number
BFO91FA053
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: bddce7edc0f13caf7495ab19ebd8b7cd1da68b09e4cde9c348b3d50f79ec3f51; retrieved 2026-09-21T15:26:13.849Z.