CEN22FA011 · Beech 58TC
Beech 58TC · Accident: loss of control in flight en route
From Blake Field (AJZ) to Southwest Wyoming Regional Airport (RKS)
Event
- NTSB case
- CEN22FA011
- 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
Beech 58TC
- Aircraft type
- Beechcraft 58
- 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
- N6748V
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Blake Field (AJZ), Delta, COTo Southwest Wyoming Regional Airport (RKS), Rock Springs, WY
- Aircraft age
- About 41 years (built 1980)
- 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
- 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
- Loss of control in flight
- 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 oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot departed on a personal flight that was the first flight after completion of the airplane’s most recent annual inspection. Recorded air traffic control communications revealed that pilot had climbed through 11,000 ft for 14,000 ft. The flight track showed that, after the airplane reached 14,000 ft, it descended about 1,000 ft, climbed to 15,000 ft, and then descended rapidly toward terrain. The airplane impacted a rocky mountainside about 25 nautical miles north of the departure airport. The wreckage debris path was about 30 ft long and consisted mostly of paint chips, shards of windscreen, various small debris, and a large outboard section of the right wing that had separated on impact. The empennage was distorted to the left and remained partially attached to the rear fuselage. The bottom of the airplane exhibited impact damage and scoring from the rocky terrain. The left engine was mostly separated from the leftwing nacelle, and the right engine remained attached to the right-wing nacelle. All six propeller blades were relatively undamaged and did not exhibit leading-edge damage or scoring, which was consistent with minimal, if any, rotation during impact. The right engine compartment, propeller blades, and right-side nose compartment were covered in a layer of engine oil. The engine throttle levers were found near the idle position, and the mixture and propeller control levers were found near the forward position. The pilot’s seatbelt and shoulder harness were not latched during the accident and the pilot was ejected from the airplane. On the right engine, the oil line from the turbocharger wastegate control valve outlet to the inlet side of the turbo pressure controller was loose at the wastegate outlet end. Also on the right engine, the propeller governor had fractured near the mounting base and remained attached to the mounting pad, but three of the four mounting nuts were loose. According to a discrepancy in the maintenance records from the most recent annual inspection, oil was found around the right engine propeller governor. Although the corrective action noted in the maintenance records was to remove the left engine propeller governor and install a new gasket, the mechanics indicated that the reference to the left engine was likely an inadvertent error and that they actually replaced the gasket on the right engine. However, the right engine propeller governor was not properly reinstalled. It is also likely that the turbocharger oil line was not properly tightened. These loose connections likely resulted in a loss of oil during the flight, which led to a loss of engine power. The pilot likely experienced difficulty handling the airplane during the emergency and lost control of the airplane.
Probable cause
The maintenance personnel’s failure to properly tighten the turbocharger oil line and the right engine propeller governor, which resulted in a loss of engine power. Contributing to the accident was the loss of airplane control following the loss of engine power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN22FA011
- Event ID
- 20211011104079
- Case number
- CEN22FA011
- 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, coordinates, 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: 680b59b51c52fcbaba1f3a17540c77a131372bd4bb0133201e3e0524ef0c9468; retrieved 2026-09-15T07:35:17.331Z.