20050816021169A

Accident · Destroyed

FAA accident report · Cessna 310R · Apopka, FL · August 16, 2005

Date
August 16, 2005 · 21:45 local
Place
Apopka, FL
Phase of flight
Normal Cruise
Operating rules
General operating rules (Part 91)
Damage
Destroyed
Aircraft
N2631E
NTSB investigation
NTSBATL05FA145
Reported as
Cessna 310R
Reported engine
Continental IO520*
People aboard
1
Fatal injuries
1
Pilot’s flight hours
600 total

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry by N-number and event date, checked against the reported make and model; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

(-23) Pilot had very limited experience in a Cessna 310 and only 20 hours of multiengine in a BE-70. Pilot's itinerary was departing Florida, flight to south carolina and then to north carolina to conduct business and the return to Florida. Fuel mismanagement could be an issue. Aircraft impacted trees and power poles, crashed and burned. Fuel system controls could not be identified after fire.

As the FAA filed it

(-23) PILOT HAD VERY LIMITED EXPERIENCE IN A CESSNA 310 AND ONLY 20 HOURS OF MULTIENGINE IN A BE-70. PILOT'S ITINERARY WAS DEPARTING FLORIDA, FLIGHT TO SOUTH CAROLINA AND THEN TO NORTH CAROLINA TO CONDUCT BUSINESS AND THE RETURN TO FLORIDA. FUEL MISMANAGEMENT COULD BE AN ISSUE. AIRCRAFT IMPACTED TREES AND POWER POLES, CRASHED AND BURNED. FUEL SYSTEM CONTROLS COULD NOT BE IDENTIFIED AFTER FIRE.

NTSB investigation

The NTSB’s investigation of this event, with its probable cause and findings. Matched to this report by N-number and date.

Other reports on N2631E · 1

Matched to the same aircraft by N-number and date.