3 Dec 2016: ARION AIRCRAFT LLC LIGHTNING LS-1 NO SERIES

3 Dec 2016: ARION AIRCRAFT LLC LIGHTNING LS-1 NO SERIES (N218D) — Unknown operator

No fatalities • Goshen, IN, United States

Probable cause

A partial loss of engine power due to carburetor icing and the subsequent forced landing on a rough/soft field.

— NTSB Determination

Accident narrative

On December 3, 2016, about 0851 eastern standard time, an Arion Aircraft LLC, Lightning LS-1 airplane, N218D, impacted soft terrain during a forced landing following an inflight loss of engine power near Goshen, Indiana. The pilot and his passenger were uninjured. The airplane sustained substantial fuselage damage. The airplane was registered to and operated by the pilot under the provisions of 14 Code of Federal Regulations Part 91 as a personal flight. Day visual meteorological conditions prevailed for the flight, which did not operate on a flight plan. The flight originated from the Goshen Municipal Airport (GSH), near Goshen, Indiana, about 0840 and was destined for the Ankeny Regional Airport (IKV), near Ankeny, Iowa.According to the pilot, he contacted the flight service station for a weather briefing along his route of flight to IKV. He conducted a preflight inspection of the airplane. About 0825, the pilot loaded the airplane and started it to allow it to warm up. About 0830, the airplane was taxied to runway 27. The pilot performed flight checks that allowed the operating temperatures to continue to warm and he "ran the carburetor heat again just prior to departing." About 0835, he departed from the runway on a 270 heading. The climb to cruise at 2,000 feet was normal and he subsequently transitioned to cruise. About 9 to 10 nautical miles from GSH the engine started to run "rough" and the pilot applied carburetor heat. This did not improve engine performance, so he decided to return to GSH where he started to line up for a downwind for runway 27. The engine continued to sputter with carburetor heat applied. Engine "power was very poor" and the airplane was losing altitude rapidly. The pilot then thought that the airplane may be able to make runway 9. He subsequently realized the airplane was too low for that approach and with little power, the airplane would not be able to make the field where it would end up in the trees or fence short of runway 9. The pilot spotted a clear field that he could turn into and have an up wind landing. He called common traffic advisory frequency at GSH about 0852 and announce a mayday call that indicated where the airplane was landing. The pilot performed a soft field landing approach and slowed as much as possible heading back on 270 heading. He knew that the fields were recently tilled and would be very soft and muddy due to recent rains. The pilot attempted to fly just above the surface as long as possible and keeping the nose up. On landing the gear dug into the very soft plowed field and the airplane continued forward on its belly. The pilot indicated that it was a very short amount of time from when he "called in and actually landed the plane."

At 0853, the recorded weather at GSH was: Wind 260 degrees at 5 knots; visibility 10 statute miles; sky condition overcast clouds at 2,800 feet; temperature 1 degree C; dew point -3 degrees C; altimeter 30.33 inches of mercury.

The temperature and dew point spread were plotted on a carburetor icing probability chart. Their intersection was within the serious icing at any power setting envelope.

A Federal Aviation Administration Inspector conducted an on-scene investigation of the accident airplane. He established flight control continuity existed. He observed that the fuel filters, one for each tank, were mounted in the aircraft cabin under the seats. The filters appeared clean and contained a liquid consistent with 100 low lead aviation gasoline. Some engine components sustained impact damage and the engine could not be test run. However, no preimpact anomalies were detected.

Contributing factors

  • cause Contributed to outcome
  • Contributed to outcome

Conditions

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