5 Jul 2015: AVIAT AIRCRAFT INC A-1C-180 UNDESIGNAT

5 Jul 2015: AVIAT AIRCRAFT INC A-1C-180 UNDESIGNAT (N354BM) — Unknown operator

No fatalities • Cincinnati, OH, United States

Probable cause

The pilot’s inadequate preflight inspection and fuel planning, which resulted in a loss of engine power due to fuel exhaustion.

— NTSB Determination

Accident narrative

***This report was modified on February 20, 2020. Please see the docket for this accident to view the original report.***

On July 5, 2015, about 1740 eastern daylight time, an Aviat Aircraft Inc., A1C-180 Husky airplane, N354BM, was substantially damaged during a forced landing following a loss of engine power near Cincinnati, Ohio. The private pilot was not injured. The airplane was registered to and operated by the pilot under the provisions of Title 14 Code of Federal Regulations Part 91 as a personal flight. Visual meteorological conditions prevailed and a flight plan was not filed. The flight originated from the Clermont County Airport (I69), Batavia, Ohio, at 1730, and its destination was the Cincinnati Municipal Airport (LUK), Cincinnati, Ohio.

The pilot reported that after practicing stop and go short field landings at I69, the pilot departed for LUK. After departure, the pilot turned the airplane to the left, climbed to 1,800 ft mean sea level (about 950 ft above ground level), reduced power to 40% to 45% for slow flight, and activated the Lean-of-Peak assist feature of the JPI EDM930 Engine Instrument. As he leaned the mixture and watched for the first cylinder to reach peak exhaust gas temperature, a Fuel Flow Sensor malfunction indicator light appeared on the EDM930. The pilot subsequently enriched the mixture, but the sensor malfunction indication continued, and the engine lost power. After attempting engine restart procedures and applying carburetor heat, the engine did not respond, so the pilot set up for a forced landing to a golf course. During the landing roll, the right wing tip and right elevator struck a tree resulting in structural damage. The airplane came to rest upright and the pilot evacuated uninjured.

According to a Federal Aviation Administration inspector, examination of the engine and airframe at the accident site did not reveal any mechanical or fuel delivery problems. All engine controls were functioning properly and oil quantity was normal. Additionally, the fuel tanks were not damaged and there was no indication of fuel leaking at the accident site. The aircraft was equipped with two 26-gallon (25 usable) fuel tanks, one in each wing. According to the pilot, the aircraft burned about 10 gallons per hour and the last amount of fuel put on the aircraft was 13.4 gallons, the day before the accident. The aircraft accumulated about 3.1 hours of flight time since the refueling.

At the accident site, the JPI EDM930 system was powered up and the "fuel remaining" indicated 17.6 gallons. Per the EDM 930 pilot's guide, the pilot is required to perform a "first time set up" which includes calibrating the fuel flow transducer. This calibration has a direct input into how the EDM computes the aircraft's remaining fuel. This task was never accomplished, which provided the pilot with an erroneous "fuel remaining" indication. After the fuel was drained from the left wing, approximately 2 gallons were recovered from the tanks. The pilot reported that he did not physically check the wing tank fuel quantity tubes that were in the cockpit, or "dip" the fuel tanks to verify fuel quantity. Also, the pilot stated that he was "preoccupied" with trying to obtain the "rich to peak" fuel burn on the EDM930 while the engine began to lose power, and he may not have noticed the engine was losing power until it actually quit.

Contributing factors

  • cause Fluid management
  • cause Pilot
  • cause Fluid level
  • Contributed to outcome

Conditions

Weather
VMC, 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.