4 Jan 2015: RAYTHEON AIRCRAFT COMPANY A36

4 Jan 2015: RAYTHEON AIRCRAFT COMPANY A36 (N349EA) — Unknown operator

No fatalities • Parker City, IN, United States

Probable cause

The pilot’s loss of airplane control while troubleshooting an engine issue in instrument meteorological conditions, which resulted in impact with trees and terrain.

— NTSB Determination

Accident narrative

On January 4, 2015, about 1603 eastern standard time, a Raytheon Aircraft Company A36 single-engine airplane, N349EA, was substantially damaged after impacting terrain while maneuvering near Parker City, Indiana. The private pilot, who was the sole occupant, sustained serious injuries. The airplane was registered to Black Gold Aviation, LLC, Norris City, Illinois, and operated by the pilot. Instrument meteorological conditions (IMC) prevailed at the time of the accident and an instrument flight rules (IFR) flight plan was filed for the 14 Code of Federal Regulations Part 91 personal flight. The airplane departed from the Carmi Municipal Airport (CUL), Carmi, Illinois, approximately 1400 central standard time, and was destined for the Delaware County Regional Airport (MIE), Muncie, Indiana.

According to the pilot, prior to the accident flight, he completed two practice instrument approaches at CUL, then obtained a weather briefing for a flight to MIE. The airplane departed CUL at 1345 central standard time, and prior to obtaining his IFR clearance, the pilot noted the autopilot would not engage so he returned to CUL. After landing, the pilot checked the circuit breaker and fuse for the autopilot with no problems noted. The pilot cycled the avionics master switch and the autopilot was then determined by the pilot to be functioning. The pilot then departed CUL at 1400 central standard time.

At 1549, air traffic control (ATC) instructed the pilot to descend at his discretion from 9,000 feet to 4,000 feet. While performing the descent checklist, the pilot switched fuel tanks at which time the engine lost power. The pilot stated he was certain the engine restarted and resulted in "putting me behind the airplane in performing my cockpit duties." The next thing the pilot remembered was ATC informing him he was flying in circles and losing altitude. The pilot felt he was in a spin and attempted to regain control of the airplane. The airplane broke out of the cloud layer and the pilot recalled it snowing with poor visibility. The pilot located a harvested cornfield and made the decision to land in the cornfield. The pilot does not recall why he decided to execute an off-airport landing. During the landing, the airplane impacted terrain and trees.

A witness, who was located near the accident site, reported he observed the airplane at a low altitude traveling at a high rate of speed heading in a northerly direction. The witness observed the airplane pitch nose up to almost vertical flight, and then turn to a west-southwest heading, before impacting the cornfield. The airplane impacted terrain, bounced, and impacted trees.

After reflecting on the accident flight, the pilot noted the following for reasons not to perform the flight:

"1. First long flight after annual and doing it in poor weather.

2. Limited flying time due to my end of year work schedule and airplane being in annual for two weeks.

3. The weather I had set myself a minimum of 1,000 feet for shooting approaches (If I recall correctly ceilings at MIE at time of briefing were 1,300, they had dropped I believe to 850 to 900 feet at time of arrival).

4. Autopilot malfunctioned on first departure; it had never done that before.

5. Should have left fuel tank selector alone, had not used that much fuel."

At 1553, the MIE automated surface observing system reported the wind from 270 degrees at 16 knots, gusting to 25 knots, visibility 3/4 mile, decreasing snow, mist, sky broken at 1,200 feet, ceiling overcast at 1,800 feet, temperature 0 degrees Celsius, dew point minus 2 degrees Celsius, and an altimeter setting of 30.02 inches of Mercury.

An examination of the airplane by two Federal Aviation Administration inspectors, and technical representatives from Textron Aviation and Continental Motors revealed the three propeller blades were twisted and bent aft. The forward fuselage was crushed upward and distorted. The flaps and landing gear appeared to be in the retracted position. No preaccident mechanical malfunctions or failures were noted with the airplane that would have precluded normal operation.

Contributing factors

  • cause Performance/control parameters — Not attained/maintained
  • cause Pilot
  • Effect on personnel
  • Effect on personnel

Conditions

Weather
IMC, wind 270/16kt, vis 1sm

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.