Accident Details
Probable Cause and Findings
the pilot's failure to ensure the aircraft was secured prior to attempting an engine start by handpropping.
Aircraft Information
Registered Owner (Historical)
Analysis
On December 7, 1994, at 1811 Pacific standard time, an unattended Piper PA-23, N2027P, collided with an airport fence and a tree after getting away from the pilot during a handprop start attempt at the Oxnard, California, airport. Visual meteorological conditions prevailed at the time and no flight plan was filed for the operation. The aircraft sustained substantial damage. The certificated commercial pilot was not injured. The flight was originating as the return portion of a flight from San Jose, to Oxnard, California.
In his written and oral statements, the pilot noted that during the flight to Oxnard he performed a long cruise descent with the engines at a very low power output. The pilot reported that he was unaware that the aircraft was equipped with generators as opposed to alternators, and that the engine speed he was using for the descent was below the speed required to keep the battery charged. The aircraft landed at Oxnard and the pilot deplaned his passenger after shutting down both engines. The pilot then attempted to start the engines and discovered that the battery charge was too low to crank the engines.
The pilot said that he set the brakes then started the right engine by handpropping. He then returned to the cockpit and attempted to use the right engine generator to help start the left engine. During the start attempt, the engine would not crank over enough to achieve a start. The pilot then retarded the right engine throttle to idle, made sure the brakes were set, then exited the aircraft to handprop the left engine. The engine started and went to a high power setting. Before the pilot could get back in the aircraft, it left the parking space and began turning in circles. After the third circle, the left wing hit a fence and a tree.
Data Source
Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# LAX95LA045