FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ATL99FA046 · Aero Commander 560A

30 Jan 1999 · Belleview, FL, United States

Aero Commander 560A · Accident: loss of engine power on approach

From OX8 to an unrecorded destination

Report a problem

Event

NTSB case
ATL99FA046
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
2 · 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

Aero Commander 560A

Aircraft type
Aero Commander 560
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
N919VC
Operator
Unknown
Onboard fatalities
Unknown
Route
From OX8To 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
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
Loss of engine power
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
Destroyed

Cause areas

  • Fluid, fuel › Exhaustion

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

NTSB narrative

After takeoff, the flight climbed to 1500 feet and the pilot reduced the engine RPM to 3000. The pilot also reported that within seconds of reducing the engine RPM the left engine sputtered. The pilot turned on the fuel boost pump in an effort to restore full engine power. Immediately afterward, the right engine sputtered and lost power. The pilot turned on the right engine boost pump again in an effort to restore full power. Attempts by the pilot to restore normal engine operation failed. The pilot selected an area for an emergency landing. The pilot recalled that as he prepared for an emergency landing, the airplane would yaw right and left as the engines momentarily gain and lose power. The airplane collided with tops of several trees. The airplanes subsequently collided with a single family home adjacent to the lake. Examination of the airframe and engine assemblies failed to disclose a mechanical malfunction or a component failure. During the examination of the fuel system, approximately 2 1/2 pints of fuel were recovered. The pilot reported that he thought he had about 50 gallons of fuel when he departed.

Probable cause

The pilot's inadequate preflight planning of the fuel required for the flight that resulted in fuel exhaustion and the subsequent total loss of engine power to both engines.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL99FA046
Event ID
20001204X00008
Case number
ATL99FA046
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: 765f079ed00313d0ab9eda8ffdb3cc3b3f2d0f301d061edd0ba4fda0b6774c26; retrieved 2026-09-20T22:15:42.395Z.