FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA04LA071 · Beech Be-300

14 Apr 2004 · Daytona Beach, FL, United States

Mass Bay Kustom Leasing/Michael Rezendes Beech Be-300 · Accident: total loss of engine power (non-mechanical) on approach

From Witham Field (SUA) to Spruce Creek Airport (7FL6)

Report a problem

Event

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

Beech Be-300

Aircraft type
Beechcraft BE-300
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
N301KS
Onboard fatalities
Unknown
Route
From Witham Field (SUA), Stuart, FLTo Spruce Creek Airport (7FL6), Daytona Beach, FL
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
Approach
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; Tree(s)
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

  • Pilot in command › Fuel management, inadequate

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

NTSB narrative

The pilot stated that he initiated a fuel transfer due to a fuel imbalance. To affect the fuel transfer, he said he "began crossfeed right to left." When the airplane was about 5 to 10 miles away from Spruce Creek Airport, the pilot said he began his descent from 12,500, and also executed a left turn to begin setting up to land, when suddenly, both engines ceased operating. When he leveled the wings both engines restarted due to auto-ignition. He said the fuel gages showed 300 to 350 lbs of fuel for the right tank, and 100 to 150 pounds on the left, so he decided to continue his approach to Spruce Creek Airport. As he approached Spruce Creek Airport, he again entered a left bank to prepare for a left base to runway 23, and while established in the left turn, both engines ceased operating a second time. He said he did not think he could reach the runway, and decided to make an landing on a taxiway. When the wings became level after the turn, he said both engines again restarted while in the vicinity of the beginning of the taxiway. As he was about to land, he said a car pulled out onto the taxiway, and stopped on the centerline, so he applied power to avoid the car. He said he climbed straight out, and when he made a climbing left turn, he said the engines ceased operating a third time, and the airplane descended towards a cluster of condos. With no runway or clear area in sight, the pilot said he guided the airplane to a retention pond. Follow-on/detailed examinations of the aircraft, engines, and propellers were conducted by an FAA Inspector, as well as technical representatives from Raytheon Aircraft Company, Pratt & Whitney Canada, and Hartzell Propeller Company, and no preaccident anomalies were noted with the airframe, flight controls, engines/accessories, or propellers. According to the FAA Inspector, and the technical representative from the airplane manufacturer, Raytheon Aircraft Company, the pilot was transferring fuel from the left fuel tank to the right fuel tank, and with the reduced amount of fuel in the left tank, as he performed left turns, the engine ceased operating. The Raytheon Aircraft Company representative stated that the Pilot Operating Handbook specifies the use of crossfeed for those times when the airplane is operating on a single engine.

Probable cause

The pilot's inadequate management of the airplane's fuel system, which resulted in fuel starvation, a loss of engine power, a forced landing, and damage to the airplane during the landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA04LA071
Event ID
20040421X00492
Case number
MIA04LA071
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2004-04-15.
  • API snapshot SHA-256: 1b7e30c57fa5c8ffe3fcb0b7856b8a5aa08c541e89574daf5a0d884334c4ab46; retrieved 2026-09-21T09:18:19.275Z.