FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN19FA161 · Cessna 425

10 Jun 2019 · Butler, MO, United States

Cessna 425 · Accident: powerplant system/component malfunction/failure en route

From Vero Beach Regional Airport (VRB) to New Century AirCenter Airport (IXD)

Report a problem

Event

NTSB case
CEN19FA161
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
1 · all aircraft and ground
Ground fatalities
0
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Cessna 425

Aircraft type
Cessna 425
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N622MM
Operator
Unknown
Onboard fatalities
Unknown
Route
From Vero Beach Regional Airport (VRB), Vero Beach, FLTo New Century AirCenter Airport (IXD), Olathe, KS
Aircraft age
About 35 years (built 1984)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route · descent
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Powerplant system/component malfunction/failure
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft power plant
  • Not determined › Not determined
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

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.

Probable cause

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN19FA161
Event ID
20190610X45525
Case number
CEN19FA161
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, cause areas. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 009fec8804c4d97820c15879503cf7b62cfaa02bcfc549ea2b05b63d551879f2; retrieved 2026-09-15T06:59:44.452Z.