26 Jun 2011: LEMOND FLY FISHER — DOUG SAPP LLC

26 Jun 2011: LEMOND FLY FISHER (N397JL) — DOUG SAPP LLC

No fatalities • West Glacier, MT, United States

Probable cause

A total loss of engine power during takeoff due to water contamination in the fuel system. Contributing to the accident was the pilot’s inadequate preflight inspection of the airplane.

— NTSB Determination

Accident narrative

On June 26, 2011, about 1003 mountain daylight time, an amateur built experimental Lemond Fly Fisher, N397JL, sustained substantial damage during a forced landing after takeoff from the Ryan Field Airport (2MT1), West Glacier, Montana. The airplane was registered to and operated by the pilot under the provisions of Title 14 Code of Federal Regulations Part 91. The private pilot and his one passenger sustained serious injuries. Visual meteorological conditions prevailed and no flight plan was filed for the personal flight. The cross-country flight was originating at the time of the accident with an intended destination of Omak, Washington.

The pilot reported to a Federal Aviation Administration (FAA) inspector that during his pre-flight inspection of the airplane, all three fuel drains were drained, and approximately one-quarter cup of fuel was obtained from each drain port, with no evidence of water noted. The pilot told the FAA inspector that during the pre-flight, the airplane was parked in an unusual attitude and that water could have possibly been trapped in a different area of the fuel tank. The pilot further reported that after conducting a 10 to 12 minute engine warm-up, he conducted a magneto check, noting all operations were normal and initiated takeoff. As the airplane passed approximately midpoint along the runway, he heard a small pop and looked at the engine RPM gauge, and saw no indication of a loss of power.

The pilot stated that as the airplane ascended through about 200 feet above ground level (agl) over the departure end of the runway, the engine quit running "like it [the engine] had a slug of water." The pilot initiated a forced landing to an adjacent field. Subsequently, the airplane struck trees and came to rest on its right side.

Examination of the airplane by the FAA inspector revealed that it came to rest near the departure end of the runway. The right wing was bent upwards about 90 degrees, and the left wing was bent and buckled throughout. The wreckage was recovered to a secure location for further examination.

On August 17, 2011, the engine was examined by the National Transportation Safety Board (NTSB) investigator-in-charge (IIC) and representatives from the FAA at the facilities of Arlin's Aviation, Belgrade, Montana. Examination of the recovered Lycoming O-320-E2D engine, serial number L-36982-27A, revealed it had been separated from the airframe by the wreckage recovery company to facilitate wreckage transportation. All engine accessories remained attached to the engine. The exhaust exhibited impact damage. The top spark plugs and rocker arm covers were removed, and the engine crankshaft was rotated by hand using the propeller. Rotational continuity was established throughout the engine and valve train. Thumb compression was noted on all cylinders. The carburetor remained attached to its mount; however, it exhibited impact related damage. The float bowl, floats, needle valve, and finger screen were separated and not located. The mixture and throttle control arms moved freely by hand from stop to stop. Examination of the engine revealed no mechanical anomalies that would have prevented normal operation.

Examination of the airframe fuel filter revealed that a small amount of clear liquid was within the filter bowl. The liquid was tested using water finding paste with positive results of water.

The electronic ignition system was removed from the airframe and engine for further testing. On November 17, 2011, the ignition system was examined at the facilities of Light Speed Engineering, Santa Paula, California, under the supervision of the IIC. The electronic ignition system and harness was functionally tested on a test bench with no anomalies noted.

Contributing factors

  • Fluid condition
  • Pilot

Conditions

Weather
VMC, wind 160/04kt, 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.