ASN Wikibase Occurrence # 162043
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Sunday 10 November 2013 |
| Time: | 15:46 |
| Type: |  Mitsubishi MU-2B-25 |
| Owner/operator: | Private |
| Registration: | N856JT |
| MSN: | 306 |
| Year of manufacture: | 1974 |
| Total airframe hrs: | 6581 hours |
| Engine model: | Honeywell TPE331-10AV-5 |
| Fatalities: | Fatalities: 1 / Occupants: 1 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | WNW of Owasso, OK -
 United States of America
|
| Phase: | Manoeuvring (airshow, firefighting, ag.ops.) |
| Nature: | Private |
| Departure airport: | Salina, KS (SLN) |
| Tulsa, OK (TUL) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
Radar and air traffic control communications indicated that the Mitsubishi MU-2B-25 was operating normally and flew a nominal flightpath from takeoff through the beginning of the approach until the airplane overshot the extended centerline of the landing runway, tracking to the east and left of course by about 0.2 nautical mile then briefly tracking back toward the centerline. The airplane then entered a 360-degree turn to the left, east of the centerline and at an altitude far below what would be expected for a nominal flightpath and intentional maneuvering flight given the airplane's distance from the airport, which was about 5 miles.
As the airplane was in its sustained left turn tracking away from the airport, the controller queried the pilot, who stated that he had a "control problem" and subsequently stated he had a "left engine shutdown." This was the last communication received from the pilot. Witnesses saw the airplane spiral toward the ground and disappear from view.
Examination of the wreckage revealed that the landing gear was in the extended position, the flaps were extended 20 degrees, and the left engine propeller blades were in the feathered position. Examination of the left engine showed the fuel shutoff valve was in the closed position, consistent with the engine being in an inoperative condition. As examined, the airplane was not configured in accordance with the airplane flight manual engine shutdown and single-engine landing procedures, which state that the airplane should remain in a clean configuration with flaps set to 5 degrees at the beginning of the final approach descent and the landing gear retracted until landing is assured. Thermal damage to the cockpit instrumentation precluded determining the preimpact position of fuel control and engine switches.
The investigation found that the airplane was properly certified, equipped, and maintained in accordance with federal regulations and that the recovered airplane components showed no evidence of any preimpact structural, engine, or system failures. The investigation also determined that the pilot was properly certificated and qualified in accordance with applicable federal regulations, including Special Federal Aviation Regulation (SFAR) No. 108, which is required for MU-2B pilots and adequate for the operation of MU-2B series airplanes. The pilot had recently completed the SFAR No. 108 training in Kansas and was returning to Tulsa. At the time of the accident, he had about 12 hours total time in the airplane make and model, and the flight was the first time he operated the airplane as a solo pilot. The investigation found no evidence indicating any preexisting medical or behavioral conditions that might have adversely affected the pilot's performance on the day of the accident.
Based on aircraft performance calculations, the airplane should have been flyable in a one-engine-inoperative condition; the day visual meteorological conditions at the time of the accident do not support a loss of control due to spatial disorientation. Therefore, the available evidence indicates that the pilot did not appropriately manage a one-engine-inoperative condition, leading to a loss of control from which he did not recover.
The airplane was not equipped, and was not required to be equipped, with any type of crash-resistant recorder. Although radar data and air traffic control voice communications were available during the investigation to determine the airplane's altitude and flightpath and estimate its motions (pitch, bank, yaw attitudes), the exact movements and trim state of the airplane are unknown, and other details of the airplane's performance (such as power settings) can only be estimated. In addition, because the airplane was not equipped with any type of recording device, the pilot's control and system inputs and other actions are unknown.
The lack of available data significantly increased the difficulty of determining the specific causes that led to this accident, and it was not possible to determine the reasons for the left engi
Probable Cause: The pilot's loss of airplane control during a known one-engine-inoperative condition. The reasons for the loss of control and engine shutdown could not be determined because the airplane was not equipped with a crash-resistant recorder and postaccident examination and testing did not reveal evidence of any malfunction that would have precluded normal operation.
Accident investigation:
 |
|
Sources:
NTSB
https://flightaware.com/live/flight/N856JT
FAA register: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=856JT
Location
Media:
Sad scene of plane accident near #owasso #oklahom #photojournalism pic.twitter.com/e1u4ASpfan
— mike simons (@mikesimonsphoto) November 10, 2013
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 11-Nov-2013 00:17 | Geno | Added |
| 11-Nov-2013 16:22 | harro | Updated [Embed code] |
| 12-Nov-2013 00:21 | Geno | Updated [Source, Embed code] |
| 12-Nov-2013 13:46 | skihard | Updated [Source] |
| 14-Nov-2013 16:25 | Alpine Flight | Updated [Time, Departure airport, Destination airport] |
| 06-Dec-2013 01:08 | Geno | Updated [Operator, Nature, Source] |
| 30-Oct-2016 18:19 | Anon. | Updated [Narrative] |
| 21-Dec-2016 19:28 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 29-Nov-2017 09:23 | ASN Update Bot | Updated [Operator, Other fatalities, Departure airport, Destination airport, Source, Embed code, Narrative] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation