MIA03LA112 · Beech C23
Future Flight Beech C23 · Accident: total loss of engine power (non-mechanical) on approach
From Columbus Airport (KCSG) to Daytona Beach International Airport (KDAB)
Event
- NTSB case
- MIA03LA112
- 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 C23
- Aircraft type
- Beechcraft 23
- 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
- N18936
- Operator
- Future Flight
- Onboard fatalities
- Unknown
- Route
- From Columbus Airport (KCSG), Columbus, GATo Daytona Beach International Airport (KDAB), 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 · VFR pattern final
- 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 exhaustion
- 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
- Pilot in command › Aircraft preflight, inadequate
- Pilot in command › Refueling, not performed
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 the planned trip duration was between 2 hours 30 minutes and 2 hours 45 minutes. He originally planned to have 2 passengers on the flight but one of the passengers decided not to go. He and his wife arrived at the airport and the owner of the facility that rented the airplane to him asked him how much fuel was needed. A discussion with himself, the owner of the renting facility, and a certified flight instructor was held and it was agreed by all that a total of 40 gallons of fuel would be needed which included fuel for reserve. At 1710, the operator placed a fuel order with the only fuel facility on the airport. He performed his preflight inspection of the airplane at about 1740 hours which included a visual check of the fuel level in the fuel tanks. He estimated the total fuel capacity at the time of takeoff was 30 gallons. The engine was started at 1745, and taxied to runway 06. The flight departed and climbed to 7,500 feet where the flight proceeded direct to the destination (Daytona Beach International Airport). When the flight was just past Valdosta, he descended to 5,500 feet and remained at that altitude for a few minutes then descended to 3,000 feet to maintain VFR conditions. The flight continued and the pilot further stated that when over the St. Johns River just west of St. Augustine, he descended to 1,500 feet to maintain VFR conditions. When the flight was clear of weather he climbed to 2,500 feet and established radio contact with Daytona Beach Approach Control. The controller "gave us the go" for a left base to runway 7L at his destination airport when the flight was 7 miles away. At that time the engine lost power and he immediately switched to the left tank. During the flight he had repositioned the fuel selector every 30 minutes. The engine was operating so he elected to divert to Ormond Beach. The controller asked if there was a problem and he replied he needed to stop for fuel. The controller gave him a frequency change to the Ormond Beach UNICOM frequency, and there was no response to his radio calls. He turned close in on the base leg and while on final approach, the engine "cut out...." The propeller windmilled for a short time then stopped as the flight was clearing trees at the approach end of the runway. The airplane was landed in grass short of the runway resulting in collapse of the nose landing gear and subsequent nose over. He and the passenger (his wife) exited the airplane and walked to the airport for assistance. He further reported there was no mechanical failure or malfunction. According to a sergeant with the Ormond Beach Police Department who is familiar with aviation, the fuel tanks did not contain any fuel and there was no smell of fuel at the accident site or in the cabin. According to an FAA inspector who examined the airplane, both fuel gauges indicated empty with electrical power applied, and both fuel tanks were empty. The fuel selector was found positioned to the left fuel tank. No fuel was found in the gascolator. Examination of all engine controls and flight controls revealed no evidence of preimpact failure or malfunction. Examination of the propeller revealed 1 propeller blade was bent slightly at the tip. Damage to the airframe precluded an engine run. Examination of the engine revealed crankshaft and valve train continuity; no engine discrepancies were reported. According to the operator of the airplane, the airplane was last fueled on May 22, 2003, which brought the fuel level to the bottom of the tabs in each fuel tank (15 gallons a side). The engine was then operated for 24 minutes while on the ground; no flight was performed. He checked the fuel level in both fuel tanks earlier in the day of the accident date and reported that the fuel level in the left tank was below the bottom of the tab and the fuel level in the right fuel tank was at the bottom of the tab. He was aware that the accident pilot intended on flying the airplane and he asked the pilot how much fuel was needed for the trip. The reply was both sides to the slot which would give 20 gallons a side. He called the order in at 1710 hours. According to the fuel facility located on the airport, the fuel request was made but the flight departed before the airplane was fueled. Records provided by the owner indicate that at the time of the accident, the airplane had been operated for 2.7 hours since engine start. According to the Pilot's Operating Handbook and FAA Approved Airplane Flight Manual, when fuel touches the bottom of the tab it indicates 15 gallons of fuel, of which 13.7 gallons are usable.
Probable cause
The pilot's inadequate preflight and his failure to refuel the airplane before departure resulting in the total loss of engine power due to fuel exhaustion and a hard landing during the subsequent forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA03LA112
- Event ID
- 20030603X00761
- Case number
- MIA03LA112
- 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 2003-05-24.
- API snapshot SHA-256: cd0effbf1deb55cd9f422af3a5ae240b8d73c5a74da4144d8e72713dd7eac937; retrieved 2026-09-22T09:15:48.211Z.