NTSB CAROL · Event
Event CEN19FA161
Registry · N622MM
FAA Aircraft Registry record.
Make / Model
VAN'S AIRCRAFT RV-12IS
Year of manufacture
2025
Engine
ROTAX 912 IS (100 hp)
Seats / Engines
2 seats · 1 engine
Last airworthiness date
20251120
ADS-B equipped
Yes — Mode-S A81ECA
Registrant of record
GRAY PLANE LLC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot’s loss of airplane control during a descent to a diversion airport with only the left engine operating. Contributing to the accident was a malfunction of the right engine throttle, the cause of which could not be determined.
Factual narrative
HISTORY OF FLIGHTOn June 10, 2019, about 1020 central daylight time, a Cessna 425 airplane, N622MM, was destroyed when it was involved in an accident near Butler, Missouri. The private pilot sustained fatal injuries. The cross-country flight was conducted under the provisions of Title 14 Code of Federal Regulations Part 91. The flight originated about 0554 eastern daylight time from Vero Beach Municipal Airport, Vero Beach, Florida, and its planned destination was New Century Airport (IXD), Olathe, Kansas. After an uneventful 970-mile flight, the pilot initiated a descent to IXD and was in direct communication with air traffic control (ATC). About 1004 central daylight time (all times from this point forward are central daylight time), the pilot told the radar controller that he had a “major problem” and could not retard the right engine throttle. Shortly afterward, the controller instructed the pilot to change frequencies to another radar controller. At 1008:32, the controller told the pilot that he was observing the airplane climbing and descending and acknowledged that the pilot was having engine trouble. The pilot advised the controller that he was going to have to shut down the right engine while it was at full power. The controller then asked the pilot if the airplane could make IXD. The pilot responded that he could make the airport but that he might have to shut down the engine on final approach. At 1011:54, the pilot reported that he was operating the airplane with one engine. At 1013:40, the pilot requested the nearest airport, and the controller advised the pilot that the Butler Airport (BUM) was the nearest airport and was about 8 miles away. At 1015:32, the pilot stated that he would have to land on runway 18 at BUM; 36 seconds later, the pilot reported that he had the airport in sight. At 1017:45, the pilot advised the controller that he was trying to get the airplane under control. The controller then confirmed that the pilot had BUM in sight and cleared the airplane for a visual approach. Between 1018:53 and 1019:08, the pilot advised the controller that the airplane was “gonna go down” on the highway. No further transmissions were received from the pilot. Radar data showed that the airplane made a 360° right turn when the airplane was at an altitude of about 2,500 ft mean sea level, as shown in figures 1 and 2. The last radar data point was recorded when the airplane was at 1,300 ft mean sea level. Figure 1. Flight Path Figure 2. Flight Path Showing 360-degree Turn and Proximity to BUM. A witness who was traveling in her car on the highway reported that she saw the airplane. She stated that the airplane was low and slow but appeared to be in stable flight with both propellers spinning. She did not see any smoke coming from the airplane. She saw the airplane flying northeast to southwest before it suddenly descended nose first into the ground. The airplane impacted a gravel road adjacent to a 100-ft-tall grain silo, about 1-mile from the highway and about 3.3 miles from BUM. PERSONNEL INFORMATIONAccording to pilot records, he had completed recurrent ground and flight training in the Cessna 425 on April 4, 2019. WRECKAGE AND IMPACT INFORMATIONThe airplane initially impacted a gravel road with the right wing tip in a nose-down, right-wing-low attitude. The right engine/nacelle impacted the ground between the gravel road and a 100-ft-tall grain silo. The left wing struck a steel staircase on the exterior of the silo. The left and right main landing gear also contacted the silo. Rubber tire transfer marks were observed about 20 and 30 ft up the silo steel structure. A small fragment of airplane aluminum was found attached to the silo about 30 ft up. One of the left propeller blades contacted the silo about 15 ft up and left a black, white, and red paint smear on the silo surface. The nose of the airplane struck an air cycle machine at the base of the silo before as the airplane impacted the ground. The airplane then cartwheeled onto the left engine and came to rest inverted about 30 ft from the initial impact point, as shown in figure 3. Figure 3. Aerial View of Accident Site The left, right, and nose landing gear were found extended. The flaps were positioned about 10° nose down. Flight control continuity was established from the cockpit to all flight control surfaces. The fuel selector handles in the cockpit were found in cross-feed positions, with the left selector in the right main position and the right selector in the left main position. The right engine power control lever was found at the full forward position. The right engine propeller condition lever was found about 0.25 inch from minimum. The right engine fuel lever was found in the fuel cutoff position (off). The left engine power control lever was found at the full forward position. The left engine propeller condition lever was found about 0.50 inch back from maximum. The left engine fuel lever was found in the run position (on). The control linkages were impact damaged, and an examination of the available control linkages found no anomalies with the rigging. The left and right engines were examined during teardowns. No mechanical anomalies were found that could have prevented normal operation. The left and right engine fuel control units (FCU) were disassembled, and no pre-existing mechanical anomalies were found that could have prevented normal operation. Some contaminants were found in the Py air sections of both FCUs. According to the manufacturer, if an FCU’s Py bleed was partially restricted with debris, modulation of power could be altered. Examination of each FCU’s Py bleed found no restrictions or blockages. Examinations of the fuel pumps, propeller governors, and overspeed governors of both engines revealed no mechanical anomalies that could have prevented normal operation. ADDITIONAL INFORMATIONAccording to the Cessna 425 single-engine performance chart, the airplane could have maintained level flight with one engine inoperative if the landing gear and flaps were retracted and the inoperative engine’s propeller was feathered. The right engine propeller condition lever was not found in the feather detent position. MEDICAL AND PATHOLOGICAL INFORMATIONAccording to the autopsy report from the Office of the Jackson County Medical Examiner, Kansas City, Missouri, the pilot’s cause of death was multiple blunt force trauma. Toxicology testing performed by the Federal Aviation Administration Forensic Sciences Laboratory detected dextromethorphan (an over-the-counter cough medicine commonly marketed as Robitussin), its metabolite dextrorphan, rosuvastatin (a medication to control high cholesterol), and metoprolol (a medication to control high blood pressure) in the pilot’s blood and urine. Ramipril (a medication to control high blood pressure) and the over-the-counter pain and inflammation medications acetaminophen, salicylate (aspirin), and ibuprofen were detected only in the pilot’s urine. All of these medications are considered non-impairing. No ethanol was detected in the pilot’s blood. During a cross-country flight, the pilot initiated a descent to his intended destination. During the descent, the pilot informed air traffic control (ATC) that he could not retard power on the right engine. Later in the descent, the pilot decided to shut down the right engine. The pilot communicated his desire to land at the nearest airport to ATC, and ATC provided the pilot with the clearance to divert. Radar data showed the airplane in a steady descent toward the airport. When the airplane was at an altitude of about 2,500 ft mean sea level, the pilot contacted ATC and stated that he was trying to get the airplane under control; radar data showed the airplane in a 360° right turn at the time. The pilot contacted ATC again and stated that he was going to land on a highway. No further transmissions were received from the pilot. After the right turn, the airplane continued in a descent through 1,300 ft mean sea level, at which point radar contact was lost. A witness saw the airplane and stated that the airplane was low and slow but appeared to be in stable flight with both propellers spinning. She did not see any smoke coming from the airplane. She saw the airplane flying northeast to southwest when it suddenly descended nose first into the ground. The airplane impacted a gravel road adjacent to a 100-ft-tall grain silo about 1 mile from the highway and about 3.3 miles from the airport. Examination of the airframe flight controls, throttle quadrant rigging, and engines revealed no mechanical anomalies. The left and right engine fuel control units (FCU) were disassembled and showed no pre-existing mechanical anomalies that could have prevented normal operation. Some contaminants were found in the Py air sections of both FCUs. According to the manufacturer, if an FCU’s Py bleed was partially restricted with debris, modulation of power could be altered. However, each FCU’s Py bleed had no restrictions or blockages. Examination of the fuel pumps, propeller governors, and overspeed governors of both engines revealed no mechanical anomalies that could have prevented normal operation. According to the Cessna 425 single-engine performance chart, the airplane could have maintained level flight with one engine inoperative if the landing gear and flaps were retracted and the inoperative engine’s propeller was feathered. At the time of impact, the airplane’s landing gear was extended, the flaps were at 10° down, and the right engine propeller condition lever was about 0.25 inch from minimum and not in the feather detent position. The reason for the pilot’s reported problem with retarding the right engine’s throttle could not be determined. It is unknown why the pilot made a right turn into the inoperative engine toward the end of the descent, and the reason for the pilot’s loss of control could not be determined. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- — Aircraft-Aircraft power plant-Engine controls-Power lever-Malfunction
- — Personnel issues-Task performance-(general)-(general)-Pilot
- — Not determined-Not determined-(general)-(general)-Unknown/Not determined
- — Aircraft-Aircraft power plant-Engine controls-(general)-Unknown/Not determined
Verbatim from NTSB's published report. Source file
NTSB_2019_CEN19FA161.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (loss of control). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2025 · Journal article (JAAER)
A Scoping Review of Aviation Loss of Control Inflight Research
Loss of control – inflight (LOC-I) contributes to aircraft accidents at unacceptably high rates. Significant industry efforts and research have aimed to improve LOC-I prevention, detection, and recove…
- SKYbrary (Eurocontrol) 2024 · SKYbrary article
Loss of Control In-Flight (LOC-I) — SKYbrary Knowledge Base
SKYbrary comprehensive knowledge-base entry on Loss of Control In-Flight — definitions, contributing factors, accident case studies (Air France 447, Colgan 3407), and prevention strategies.
- NTSB Aircraft Accident Reports 2022 · Accident report
Loss of Control on Takeoff in Icing Conditions — Citation 560XL
Cessna Citation 560XL fatal takeoff icing accident, March 2018. Investigation of a Citation 560XL loss-of-control takeoff accident in icing conditions.
- Semantic Scholar 2021 · Article (Aviation)
ANALYSIS OF GENERAL AVIATION FIXED-WING AIRCRAFT ACCIDENTS INVOLVING INFLIGHT LOSS OF CONTROL USING A STATE-BASED APPROACH
Inflight loss of control (LOC-I) is a significant cause of General Aviation (GA) fixed-wing aircraft accidents. The United States National Transportation Safety Board’s database provides a rich source…
- NASA NTRS 2021 · Presentation
Use of Design of Experiments in Determining Neural Network Architectures for Loss of Control Detection
Abstract—We describe empirical methods for selecting a neural network architecture to implement belief state inference on generic commercial transport aircraft.
- NASA NTRS 2021 · Conference Paper
Use of Design of Experiments in Determining Neural Network Architectures for Loss of Control Detection
We describe empirical methods for selecting a neural network architecture to implement belief state inference on generic commercial transport aircraft.
Browse the full corpus — academia portal ↗