Fuel exhaustion Accident Beechcraft B23 N7657R,
ASN logo
ASN Wikibase Occurrence # 292748
 
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Saturday 24 December 2005
Time:16:37 LT
Type:Silhouette image of generic BE23 model; specific model in this crash may look slightly different    
Beechcraft B23
Owner/operator:Private
Registration: N7657R
MSN: M-1261
Engine model:Lycoming O-360-A2G
Fatalities:Fatalities: 0 / Occupants: 2
Aircraft damage: Substantial
Category:Accident
Location:Palatka, Florida -   United States of America
Phase: Unknown
Nature:Private
Departure airport:Southern Pines-Pinehurst Airport, NC (SOP/KSOP)
Destination airport:Palatka, FL (28J)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
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.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: MIA06CA040
Status: Investigation completed
Duration: 3 months
Download report: Final report

Sources:

NTSB MIA06CA040

Revision history:

Date/timeContributorUpdates
09-Oct-2022 08:42 ASN Update Bot Added

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org