18 Jul 2019: Cessna 550 No Series

18 Jul 2019: Cessna 550 No Series (N320JT) — Unknown operator

No fatalities • Mesquite, NV, United States

Probable cause

The pilot's operation of the airplane while intoxicated, which resulted in a loss of airplane control on landing.

— NTSB Determination

Accident narrative

On June 17, 2019, about 1844 Pacific daylight time, a Cessna 550 airplane, N320JT, was destroyed when it was involved in an accident at Mesquite Airport (67L), Mesquite, Nevada. The pilot, the sole occupant, had minor injuries. The airplane was operated under the provisions of Title 14 Code of Federal Regulations Part 91 as a ferry flight. Visual meteorological conditions prevailed, and an instrument flight rules (IFR) flight plan was filed for the cross-country flight. The flight departed Tri-Cities Airport (PSC), Pasco, Washington, about 1625 and had a filed destination of Henderson Executive Airport (HND), Las Vegas, Nevada. According to an ATC recording and radar data, the pilot was in contact with approach control and a radar track showed that the accident airplane was approaching the Las Vegas class B airspace from the northeast. The pilot's speech was slurred, and the controller repeatedly asked if the oxygen system on the airplane was working properly. As the airplane approached 67L from the northeast, the pilot stated he had the airport in sight and repeatedly requested a visual approach. The controller instructed the pilot to continue his flight to his destination of HND, which was another 85 miles past 67L in a southwest direction. As the controller attempted to maintain communications, the pilot dropped off radar shortly after passing 67L. According to the pilot, during his descent to HND, the right thrust reverser lever "felt weird," and the right thrust reverser warning light began to illuminate. He stated that he decided not to continue his flight into the "busy LAS [Las Vegas]-HND airspace." The pilot canceled his IFR flight plan with the approach controller and proceeded to 67L. He stated he continued his visual approach into 67L and upon landing, experienced a left yaw and opined that the left thrust reverser had fully deployed and the right one did not. After applying full right rudder, the airplane "ballooned" and soon after touched down "again" as the airplane continued to yaw to the left as it continued down the runway. The pilot stated that the airplane veered off the side of the runway and the landing gear then collapsed. He further stated that he attempted to extinguish the fire and was unsuccessful. A surveillance video at 67L captured the airplane as it was sliding across the runway shortly after landing. The main landing gear had collapsed prior to entering the video frame and a large fire and dark smoke followed the airplane as it slid down the runway. The airplane disappeared from view as it exited the runway near the departure end of the runway. Local authorities responded to the accident site where the pilot was located, and the airplane was engulfed in flames. The pilot was observed to be intoxicated and stated to the authorities that he had been drinking some vodka. The authorities asked about the amount of vodka he drank and the timeline of drinking it. The pilot stated that the vodka had burned in the fire and an accurate timeline was not given. After refusing a standard sobriety test, the pilot was placed under arrest for operating an aircraft under the influence of an intoxicating liquor. About 2 hours after the accident, a blood draw and a complete analysis of that blood was performed by the City of Henderson Police Department, Henderson, Nevada. The results were positive for ethanol at 0.288 g/dL±0.011 g/dL. The amount of ethanol found was consistent with a blood alcohol count (BAC) of .288. This level exceeded the FAA's allowable limit of .040 (Federal Aviation Regulation 14 CFR 91.17) while operating an aircraft. The onsite examination of the accident site revealed multiple impact marks about 2,517 ft down the 5,121 ft long runway surface. A debris field down the runway consisted of main landing gear components and a lower fuselage mounted antenna. The main wreckage came to rest about 50ft off the left side of the runway, near the departure end. The fuselage and wings were mostly consumed by postimpact fire, and the engines and empennage remained intact. The wreckage was relocated to a secure facility and an examination of the wreckage was not conducted.

Contributing factors

  • cause Pilot
  • cause Pilot

Conditions

Weather
VMC

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.