HAWKER BEECHCRAFT CORPORATION 390 near South Bend, IN — 2013-03-17
- Date
- 2013-03-17
- Location
- South Bend, IN, USA
- Airport
- SBN
- Aircraft
- HAWKER BEECHCRAFT CORPORATION 390
- Registration
- N26DK
- Category
- Airplane
- Highest injury
- Fatal
- Fatalities
- 2
- Phase of flight
- Approach
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 the inadvertent dual engine shutdown.
NTSB narrative
According to the cockpit voice recorder (CVR), during cruise flight, the unqualified pilot-rated passenger was manipulating the aircraft controls, including the engine controls, under the supervision and direction of the private pilot. After receiving a descent clearance to 3,000 feet mean sea level (msl), the pilot told the pilot-rated passenger to reduce engine power to maintain a target airspeed. The cockpit area microphone subsequently recorded the sound of both engines spooling down. The pilot recognized that the pilot-rated passenger had shutdown both engines after he retarded the engine throttles past the flight idle stops into the fuel cutoff position. Specifically, the pilot stated "you went back behind the stops and we lost power." According to air traffic control (ATC) radar track data, at the time of the dual engine shutdown, the airplane was located about 18 miles southwest of the destination airport and was descending through 6,700 feet msl. The pilot reported to the controller that the airplane had experienced a dual loss of engine power, declared an emergency, and requested radar vectors to the destination airport. As the flight approached the destination airport, the cockpit area microphone recorded a sound similar to an engine starter spooling up; however, engine power was not restored during the attempted restart. A review of the remaining CVR audio did not reveal any evidence of another attempt to restart an engine. The CVR stopped recording while the airplane was still airborne, with both engines still inoperative, while on an extended base leg to the runway. Subsequently, the controller told the pilot to go-around because the main landing gear was not extended. The accident airplane was then observed to climb and enter a right traffic pattern to make another landing approach. Witness accounts indicated that only the nose landing gear was extended during the second landing approach. The witnesses observed the airplane bounce several times on the runway before it ultimately entered a climbing right turn. The airplane was then observed to enter a nose low, rolling descent into a nearby residential community. The postaccident examinations and testing did not reveal any anomalies or failures that would have precluded normal operation of the airplane. Although the CVR did not record a successful engine restart, the pilot was able to initiate a go-around during the initial landing attempt, which implies that he was able to restart at least one engine during the initial approach. The investigation subsequently determined that only the left engine was operating at impact. Following an engine start, procedures require that the respective generator be reset to reestablish electrical power to the Essential Bus. If the Essential Bus had been restored, all aircraft systems would have operated normally. However, the battery toggle switch was observed in the Standby position at the accident site, which would have prevented the Essential Bus from receiving power regardless of whether the generator had been reset. As such, the airplane was likely operating on the Standby Bus, which would preclude the normal extension of the landing gear. However, the investigation determined that the landing gear alternate extension handle was partially extended. The observed position of the handle would have precluded the main landing gear from extending (only the nose landing gear would extend). The investigation determined that it is likely the pilot did not fully extend the handle to obtain a full landing gear deployment. Had he fully extended the landing gear, a successful single-engine landing could have been accomplished. In conclusion, the private pilot's decision to allow the unqualified pilot-rated passenger to manipulate the airplane controls directly resulted in the inadvertent dual engine shutdown during cruise descent. Additionally, the pilot's inadequate response to the emergency, including his failure to adhere to procedures, resulted in his inability to fully restore airplane systems and ultimately resulted in a loss of airplane control.
Analysis
- Primary failure mode
- Human factors
- First missed decision gate
- Pilot should have maintained power management to avoid engine failure.
NTSB coding
Evidence available
- CVR
- Video
- ADS-B / radar
- Photos
- 55 docket documents
Docket documentsshowing 50 of 55
- FAA Air Traffic Control Accident Package (Excerpts)atc
- FAA Air Traffic Control Radar Data, Plotatc
- FAA Air Traffic Control Radar Data, Source Data Fileatc
- Cockpit Voice Recorder 12 - Factual Report of Group Chairmancvr
- Certification of Party Coordinator Formsform
- FAA Airman Registry Information (James Steven Davis)form
- FAA Airman Registry Information (Wesley Bryan Caves)form
- NTSB Wreckage Release Formform
- Passenger Interview (Chris Evans)interview
- Passenger Interview (Chris Evans) Email Correspondenceinterview
- Witness Statementsinterview
- Affidavit Concerning Role of Pilot-Rated-Passenger on Accident Flight (James Steven Davis)other
- Airframe Maintenance Logbook (Excerpts)other
- Airport Diagram, South Bend Airportother
- Engine Maintenance Logbook, Left Engine (Excerpts)other
- Engine Maintenance Logbook, Right Engine (Excerpts)other
- FAA Airman Documentation (Wesley Bryan Caves)other
- FAA Airworthiness and Registration Info for Accident Airplaneother
- Pilot Flight History in Accident Airplane (Wesley Bryan Caves)other
- Pilot Historical Flight Time Summary (Wesley Bryan Caves)other
- Pilot Logbook (James Steven Davis)other
- Pilot Logbook (Wesley Bryan Caves)other
- Pilot Logbook Spreadsheet (Wesley Bryan Caves)other
- Pilot Training Records - The Jetstream Group (Wesley Bryan Caves)other
- Toxicological Test Results (James Steven Davis)other
- Toxicological Test Results (Wesley Bryan Caves)other
- Photo 01 – Accident Site Overviewphotos
- Photo 02 – Accident Site Overviewphotos
- Photo 03 – Accident Site Overviewphotos
- Photo 04 – Accident Site Overviewphotos
- Airplane Maintenance Status Reportreport
- Airworthiness Group Chairman Reportreport
- Airworthiness Group Chairman Report – Attachment 1report
- Airworthiness Group Chairman Report – Attachment 2report
- Airworthiness Group Chairman Report – Attachment 3report
- Airworthiness Group Chairman Report – Attachment 4report
- Airworthiness Group Chairman Report – Attachment 5report
- Airworthiness Group Chairman Report – Attachment 6report
- Airworthiness Group Chairman Report – Attachment 7report
- Airworthiness Group Chairman Report – Attachment 8report
- Airworthiness Group Chairman's Factual Report of Investigation - Addendum 1report
- Airworthiness Group Chairman's Factual Report of Investigation - Addendum 1 - Attachment 1report
- Electronic Devices Specialist's Factual Reportreport
- Electronic Devices Specialist's Factual Report – Attachment 1 (ForeFlight Flight History)report
- Electronic Devices Specialist's Factual Report – Attachment 2 (LogTen Pro Flight History)report
- Errata - Powerplants Factual Report of Investigationreport
- Powerplants Group Chairman Factual Reportreport
- Powerplants Group Chairman Factual Report – Attachment 1 (Engine Air Start Procedures)report
- Sound Spectrum Study Specialist's Factual Reportreport
- South Bend Police Department Incident Reportreport
Related mishaps
- PIPER PA46
2024-07-28 · Radisson, WI
- CESSNA 182A
2024-06-24 · Spokane Valley, WA
- PIPER PA22
2024-01-11 · Dalhart, TX
- LANCAIR IV
2023-11-17 · Perry, FL
- DIAMOND DA20
2023-08-23 · Fairfield, UT
- MOONEY AIRCRAFT CORP. M20K
2022-08-13 · Hanna City, IL · 2 fatalities