MIA06CA040 · Beech BE23
Beech BE23 · Accident: total loss of engine power (non-mechanical) en route
From Moore County Airport (KSOP) to Palatka Municipal - Lt. Kay Larkin Field (28J)
Event
- NTSB case
- MIA06CA040
- 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 BE23
- 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
- N7657R
- Operator
- Fitzhugh L. Shelton III · private individual
- Onboard fatalities
- Unknown
- Route
- From Moore County Airport (KSOP), Pinehurst, NCTo Palatka Municipal - Lt. Kay Larkin Field (28J), Palatka, 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
- En route · cruise
- 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; 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
- Substantial
Cause areas
- Pilot in command › In-flight planning/decision, 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 had planned a cross country flight from Chambersburg, Pennsylvania, to Ocala, Florida, with 2 fuel stops along the route. During the flight to the second fuel stop, the engine lost fuel pressure, and the airplane impacted trees during a forced landing on a road. Seven days before the accident flight, the airplane was topped off with fuel, and was flown in the area for about a 15 minute flight. The flight departed at about 0720, they landed at the first fuel stop at about 0920, and refueled the airplane with 20 gallons of fuel. He estimated that he had a total of 45 gallons of usable fuel on board for the flight to the second fuel stop. He stated that he would make a decision after 2 hours into the flight to determine if they would require a stop for fuel before reaching the second fuel stop, at a fuel consumption of 10 gallons per hour. He forecasted the flight to be 4 hours. Twenty minutes into the flight to the second fuel stop, they stopped at the Moore County Airport for a restroom stop, and departed at about 1130. During the engine run-up check for departure, he noted that he failed to reset the timer to monitor the fuel when he departed the first fuel stop. He reset the timer and made a mental note to include approximately 30 minutes extra when figuring the fuel status en route. At about 1530, about 12 miles from the second fuel stop, the pilot noted a loss of fuel pressure. He switched tanks, turned on the fuel pump, enriched the fuel mixture, and about 2 minutes later the fuel pressure was lost again. He advised Jacksonville Approach Control of his intentions to land on a road or in a field. A road was located and he glided the airplane to land. He noticed a gate along the landing path and maneuvered the airplane over the gate. As the airplane came back down, the left wing struck trees resulting in the airplane rotating counter clockwise before coming to a stop. He and the passenger exited the airplane, and called Flight Service to advise the authorities of what had happened. According to the passenger, they departed after 11:15 am from the Moore Airport that day. While en route, at about 3:00 pm, the engine sputtered as if it was running out of fuel. The pilot switched from the left fuel tank to the right fuel tank and mentioned that they had enough fuel for a four hour trip, and that the right tank would be more than enough to get them to the airport. He had been regularly switching tanks during the flight. A few minutes later the engine sputtered again. The pilot said "this can't be happening; we have enough fuel for 4 hours". The engine went on and off and then lost power. The pilot stated to the NTSB and the FAA that he had experienced fuel exhaustion, due to miscalculation of the fuel and there were no mechanical failures or malfunctions to the airplane or any of its systems prior to the accident.
Probable cause
The pilot's inadequate in-flight planning/decision which resulted in fuel exhaustion and the loss of engine power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA06CA040
- Event ID
- 20060113X00066
- Case number
- MIA06CA040
- 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, coordinates. 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: fc0dd004d19a9f5ca9615b2261adb6c62998b182476800e821159b2fac4acde6; retrieved 2026-09-22T05:11:21.580Z.