FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR23FA275 · Cessna T310R

18 Jul 2023 · Santa Fe, NM, United States

Cessna T310R · Accident: loss of engine power (total) during initial climb

From Santa Fe Municipal Airport (SAF) to Santa Monica Municipal Airport (SMO)

Report a problem

Event

NTSB case
WPR23FA275
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
Unknown
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 T310R

Aircraft type
Cessna 310
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
N5251C
Operator
Unknown
Onboard fatalities
Unknown
Route
From Santa Fe Municipal Airport (SAF), Santa Fe, NMTo Santa Monica Municipal Airport (SMO), Santa Monica, CA
Aircraft age
About 45 years (built 1978)
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
Initial climb
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 engine power (total)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Aircraft › Aircraft power plant
  • 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

Shortly after takeoff in the multi-engine airplane, the pilot reported to the tower controller that he had an engine failure. The controller cleared the pilot to land on any runway, and the pilot stated that he was going to try to gain altitude before returning for landing. There were no other transmissions from the pilot. ADS-B data indicated that the airplane lifted off from the runway and generally maintained the runway heading. The airplane climbed to a maximum altitude of about 200 ft above ground level (agl) at a ground speed about 100 knots (kts). The airplane continued south for about 2.5 miles over a sparsely populated area without climbing. The airplane then began a descending, slowly decelerating left turn toward a frontage road and an interstate highway; however, it is possible that the pilot chose not to use either location as a forced landing site due to powerlines located immediately north of the frontage road and traffic on the interstate. The pilot continued the left turn and aligned the airplane with an alley located in a neighborhood. A witness stated that the airplane’s left wing dropped just before the airplane impacted a house, consistent with a loss of control in the final moments of the flight. Examination of the left engine revealed significant internal damage. Multiple fragments of engine components were found in the oil sump, including separated crankshaft counterweight components. Further examination revealed that the aft-facing crankshaft counterweight retaining rings were installed incorrectly, with the retaining ring ears facing away from the crankshaft centerline, some of them with the sharp edge incorrectly facing inward, and with incorrect spacing of the ring ear gap. This improper installation allowed two of the counterweights to separate, and one to partially separate, from the crankshaft, which resulted in the total loss of power to the left engine. Examination of the right engine revealed the same incorrect installation of the aft-facing counterweight retaining rings; however, the crankshaft counterweights remained intact. There were no other mechanical malfunctions or failures with the right engine that would have precluded normal operations. Examination of the airframe revealed extensive thermal damage, but no anomalies that would have precluded normal operation. The landing gear were found in the retracted position, and the position of the wing flaps could not be determined. A review of maintenance records revealed that all the counterweights from both engines were removed and reinstalled about 24 years before the accident in accordance with a mandatory service bulletin which, in part, called for the removal and reinstallation of all the counterweights. The removal criteria specifically called for removing and replacing the aft-facing retaining rings as part of the counterweight removal process. Records indicated that this was the last time the rings would have been removed/replaced. Based on the airplane’s estimated weight and balance and the atmospheric conditions present at the time of the accident, performance charts in the pilot operating handbook indicated that the airplane should have been able to climb at a rate of about 300 ft per minute with one engine inoperative, but obtaining this performance would have been dependent on the pilot establishing the proper airplane configuration and single-engine best rate of climb speed (Vyse). Examination of the airplane revealed that the landing gear was retracted and that the left propeller was feathered consistent with published single-engine inoperative procedures; however, ADS-B information indicated that the airplane’s ground speed was about 100 kts; the airplane’s published Vyse was 106 kts indicated airspeed. Additionally, the procedures stated that the airplane should be banked 5° into the operating engine, and the pilot was turning the airplane left (into the inoperative engine) before the accident occurred. Based on the available information, it is likely that the pilot did not maintain adequate airspeed while maneuvering following the loss of left engine power, which resulted in the airplane’s inability to climb and a subsequent loss of control and impact with terrain.

Probable cause

A total loss of left engine power as a result of improper installation of the aft-facing crankshaft counterweight retaining rings. Also causal was the pilot’s failure to maintain adequate airspeed following the loss of left engine power, which resulted in the airplane’s inability to climb and subsequent loss of control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR23FA275
Event ID
20230718192652
Case number
WPR23FA275
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: 983ab1eda38d65e566bd894b82798207c70002e012c178f1cc64a47457ee1059; retrieved 2026-09-15T08:03:06.238Z.