20 Apr 2008: CESSNA C175A

20 Apr 2008: CESSNA C175A (N6868E) — Unknown operator

No fatalities • Groveland, CA, United States

Probable cause

A total loss of engine power due to fuel starvation as a result of a blocked fuel line that was improperly fabricated by the pilot. Also causal was the pilot's excessive ground speed during the taxi tests that resulted in an inadvertent takeoff.

— NTSB Determination

Accident narrative

On April 19, 2008, about 1855 Pacific daylight time, a Cessna Aircraft Company (Cessna) C175A Skylark, N6868E, experienced a reported loss of engine power and collided with transmission wires following a departure from Pine Mountain Lake Airport, Groveland, California. The pilot, who was the owner, was operating the airplane under the provisions of 14 CFR Part 91. The commercial pilot, the sole occupant, sustained serious injuries; the airplane sustained substantial damage. The local personal flight was originating from Groveland. Visual meteorological conditions prevailed, and a flight plan had not been filed.

In a written statement, the pilot reported that while conducting a high-speed taxi test, the airplane encountered a gust of wind and the airplane inadvertently became airborne. The engine experienced a loss of power and the airplane struck power lines.

An inspector from the Federal Aviation Administration (FAA) interviewed friends of the pilot who were based at Groveland. A friend stated that the pilot, who was a certificated airframe and powerplant mechanic, was conducting a series of high-speed taxi tests. The airplane's groundspeed became excessive and it encountered a gust of wind. The airplane unintentionally became airborne. The airplane continued to climb and it appeared as though the pilot was attempting to return back to the airport. After the airplane made a 90-degree turn, the engine experienced a loss of power momentarily. The engine powered up again and then quit. The airplane collided with a telephone pole and descended nose-low onto the road below.

The FAA inspector and representatives from both Cessna and Teledyne Continental Motors (TCM) conducted a post accident examination. The FAA inspector discovered that the pilot had just installed a recently purchased engine. As part of the installation he had fabricated and fitted a new fuel line just prior to the accident flight.

According to the FAA inspector, the engine and airframe examination disclosed no mechanical malfunctions or failures that would have precluded normal operation except the following. He noted that during the disassembly of the fuel line connecting the gascolator to carburetor he noticed a "flapper valve" at both end fittings; he thought this was the fuel line the pilot had recently fabricated. He stated that flapper valves can occur as a result of fittings being installed without using a mandrel, where the fitting cuts the inside of the hose creating a valve that obstructs fuel flow. The inspector opined that the flapper valve created enough of an obstruction to prevent fuel flow.

The FAA inspector added that the last annual inspection noted in the airframe logbook was on October 01, 2006, at a total time of 2,733.4 hours. No records were found for the engine or installation thereof. He further stated that the airplane had not been approved for return to service, nor did it have an airworthiness certificate.

A routine aviation weather report (METAR) generated by an Automated Surface Observation System (ASOS) at Merced Municipal Airport/Macready Field, Merced, California (located 38 nautical miles southwest from the accident site), indicated that about 2 minutes prior to the accident, winds were 260 degrees at 15 knots, gusting to 25 knots.

Contributing factors

  • cause Malfunction
  • cause Maintenance personnel
  • Effect on operation
  • cause Incorrect service/maintenance
  • cause Incorrect use/operation

Conditions

Weather
VMC, wind 260/13kt, 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.