Hawker Beechcraft Corporation 390 accident near South Bend, IN

On March 17, 2013, a Hawker Beechcraft Corporation 390 (airplane) was involved in an accident near South Bend, IN. 2 people died. Damage to the aircraft: destroyed.

Date

March 17, 2013

Place

South Bend, IN

Aircraft

Hawker Beechcraft Corporation 390 · Airplane

Injuries

2 fatal, 2 serious, 0 minor

Damage

Destroyed

Position

41.696°N, 86.296°W

NTSB ID

20130317X85055

Official records · CEN13FA196

• Public docket: reports, statements and exhibits from the investigation

Air traffic control records

• FAA Air Traffic Control Accident Package Excerpts: Document (PDF), on ntsb.gov
• FAA Air Traffic Control Radar Data Plot: Document (PDF), on ntsb.gov
• FAA Air Traffic Control Radar Data Source Data File: Document (CSV), on ntsb.gov

NTSB summary

HISTORY OF FLIGHTOn March 17, 2013, at 1623 eastern daylight time, a Hawker Beechcraft model 390 (Premier IA) business jet, N26DK, serial number RB-226, collided with three residential structures following an aborted landing attempt on runway 9R located at the South Bend Airport (SBN), South Bend, Indiana. The private pilot and pilot-rated-passenger, who were occupying the cockpit seats, were fatally injured. An additional two passengers, who were seated in the cabin area, and one individual on the ground sustained serious injuries. The airplane was registered to 7700 Enterprises of Montana, LLC, and operated by Digicut Systems of Tulsa, Oklahoma, under the provisions of 14 Code of Federal Regulations Part 91 while on an instrument flight rules flight plan. Day visual meteorological conditions prevailed for the business flight that departed the Richard Lloyd Jones Jr. Airport (RVS), Tulsa, Oklahoma, at 1356 central daylight time. According to air traffic control (ATC) information, after departing RVS, the accident flight proceeded toward the intended destination while receiving normal ATC services. The flight was eventually cleared to a final cruise altitude of 41,000 feet (FL410). The cockpit voice recorder (CVR) contained about 31 minutes of cockpit conversation/audio and radio communications. At 1545:31, the beginning of the CVR recording, the pilot was discussing the airplane's fuel status and how much fuel would be required for the return flight. The pilot continued to explain and demonstrate various flight management system functions to the pilot-rated-passenger. At 1

Probable cause

The private pilot's inadequate response to the dual engine shutdown during cruise descent, including his failure to adhere to procedures, which ultimately resulted in his failure to maintain airplane control during a single-engine go-around. An additional cause was the pilot's decision to allow the unqualified pilot-rated passenger to manipulate the airplane controls, which directly resulted in th

More accidents in IN

• Pilatus PC-12, May 25, 2011
• Mitsubishi MU-2B-60, Sep 11, 1992
• Cessna 310N, Nov 20, 1984
• Cessna T303, Nov 14, 2006
• Cessna U206G, Apr 21, 2006

Browse: Indiana

See it on the map

Source: NTSB aviation accident database (US government, public domain). Findings may be preliminary or later revised by the NTSB. Not a complete global record.