FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DFW05FA188 · Cessna 310Q

24 Jul 2005 · Ada, OK, United States

Cessna 310Q · Accident: loss of engine power during takeoff

From Ada Regional Airport (ADH) to Cushing Municipal Airport (CUH)

Report a problem

Event

NTSB case
DFW05FA188
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
3 · 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 310Q

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
N1971W
Operator
Unknown
Onboard fatalities
Unknown
Route
From Ada Regional Airport (ADH), Ada, OKTo Cushing Municipal Airport (CUH), Cushing, OK
Aircraft age
Not recorded
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
Takeoff
First occurrenceThe 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
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

  • Engine assembly, gear › Failure, total
  • Engine assembly, gear › Fatigue
  • Pilot in command › Aircraft control, not maintained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The 1,500-hour airline transport rated pilot had just departed a 6,305-foot-long runway when, based on a viewing of security camera footage, a puff of white smoke exiting the back of the right engine shortly after the airplane became airborne. The airplane then began a right turn and flew on a westerly heading at a low altitude before it disappeared behind a tree line. A witness saw the airplane as it was in a right turn toward the north. He thought the airplane was going to land on a closed highway, but the nose of the airplane dropped and the airplane cartwheeled on the grass median west of the road. Examination of the right engine revealed that the crankshaft gear had failed due to a fatigue fracture in one of the teeth. The fatigue emanated from the pressure face of the tooth and intersected another crack emanating from the non-pressure face of the tooth, thereby producing separation of the tooth from the rim. Near the origin, post-fracture damage prevented the ability to determine if the crack initiated in fatigue or if a crack propagated in overstress through the case and then continued propagating through the core in fatigue. Upon completion of the materials examination it was evident that the microstructure of the gear was inadequate and more research into the manufacturing process was required. A review of manufacturing records indicated that approximately 2,400 crankshaft gears were made from the same batch of material as the accident gears, and were heat-treated in two groups. A review of the heat treatment records confirmed that furnace temperatures during the hardening step in each heat-treating process were not high enough to fully austenitize the material. Furthermore, the quantity and orientation of gears loaded in the furnace were greater when compared to other jobs completed for TCM. In addition, initial data from a test load similar to that used in the heat-treating process from the accident serial number gear, indicated that under these conditions, the gears might not have been fully equilibrated at temperature during the hardening step. As a result, TCM manufactured several other gears at different hardnesses and conducted failure testing to see if they could reproduce a similar failure. Even though some of the hardness levels were well below TCM standards, they were unable to produce a similar failure. In addition, there was evidence to suggest that the gear teeth may have been exposed to an excessive load at some point during its operation. The cause of the gear tooth failure could not be determined.

Probable cause

The loss of engine power as a result of a fatigue fracture in one of the crankshaft gear teeth for undetermined reasons. Also causal was the pilot's failure to maintain control of the twin-engine airplane after the power loss, which resulted in an inadvertent stall and subsequent collision with terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DFW05FA188
Event ID
20050801X01121
Case number
DFW05FA188
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: fd9e56f1bb08ddd151506d9c466da91eade99e7b77a204e18cd463a1614e382b; retrieved 2026-09-20T17:58:06.568Z.