23 Aug 2010: PIPER PA-30 — Thomas B Newman

23 Aug 2010: PIPER PA-30 (N8734Y) — Thomas B Newman

No fatalities • Douglas, GA, United States

Probable cause

A loss of engine power during takeoff due to fuel contamination. Contributing to the accident was the pilot's inadequate preflight inspection and inadequate maintenance of the fuel system.

— NTSB Determination

Accident narrative

On August 23, 2010, about 1320 eastern daylight time, a Piper PA-30, N8734Y, owned and operated by a private individual, was substantially damaged when it impacted terrain, during takeoff from Douglas Municipal Airport (DQH), Douglas, Georgia. The certificated airline transport pilot was seriously injured. Visual meteorological conditions prevailed and no flight plan had been filed for the local personal flight conducted under the provisions of Title 14 Code of Federal Regulations Part 91.

According to the owner, the airplane had been parked outside at DQH, and not flown for about 1 year. On July 7, 2010, an annual inspection was performed on the airplane, however, during a subsequent test-flight on July 25, the left engine "missed" and additional maintenance was performed, which included "flushing the fuel tanks and cleaning the fuel lines to each respective flow divider." On the date of the accident, the pilot intended to fly the airplane to Florida, where the owner planned to sell it.

According to the pilot, during the preflight inspection, he observed water in the airplane's main fuel tanks, and debris in the right wingtip fuel tank. During two subsequent ground-runs, both engines had periods of rough running operation and unidentifiable debris was observed in the fuel injectors. A third ground-run was conducted without any anomalies noted, and the pilot intended to conduct a test-flight in the airport traffic pattern.

After normal preflight checks, the pilot attempted to depart from runway 22, a 6,000-foot-long, 100-foot-wide, asphalt runway. During the takeoff roll, the right engine rpm exceeded redline on a digital rpm gauge. The pilot adjusted the engine power and continued with the takeoff. The airplane lifted off the runway and was accelerating in ground effect, when the left engine began to run rough. The pilot believed that there was insufficient runway remaining to land and stop on the runway. He attempted to climb; however, the airplane began to settle and slowly yaw to the left.

The airplane subsequently impacted trees, and came to rest about a 1/4-mile southwest of the airport. The airplane sustained substantial damage to both wings, the fuselage, and empennage.

The airplane was equipped with two Lycoming IO-360-C1C series engines. The position of the wreckage precluded examination at the accident site. Subsequent examination of the wreckage conducted by representatives of the airframe and engine manufacturers, under the supervision of a Federal Aviation Administration (FAA) inspector revealed the presence of water and corrosion in the fuel distribution system. Water was observed in both of the main fuel tank strainers and the left engine fuel injector. In addition, fuel that was drained from the airplane by recovery personnel contained water and unidentified debris. No additional anomalies were noted, which would have prevented normal engine operation.

According to fuel records, the airplane was "topped-off" with 30 gallons of 100-low-lead aviation gasoline on the morning of the accident. Three airplanes were refueled on the day prior to the accident, and one airplane was refueled after the accident airplane. The airport manager reported that he specifically contacted the owners and/or pilots of those airplanes, and they reported that they did not experience any fuel related problems.

The pilot reported 3,465 hours of total flight experience, which included 3,297 hours in rotorcraft, 141 hours in single-engine airplanes, and 22 hours in multiengine airplanes. The pilot had no previous experience in the same make and model as the accident airplane beyond the test flight that was performed in July, and the accident flight.

Contributing factors

  • cause Fluid condition
  • cause Pilot
  • cause Maintenance personnel
  • cause Maintenance personnel

Conditions

Weather
VMC, wind 080/05kt, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.