FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA14LA179 · Cessna T210L

3 Apr 2014 · Clayton, AL, United States

Southern Aerial Images Cessna T210L · Accident: loss of engine power (total) en route

From Valdosta Regional Airport (VLD) to Tuscaloosa National Airport (TCL)

Report a problem

Event

NTSB case
ERA14LA179
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
0 · 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 T210L

Aircraft type
Cessna 210
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
N1631X
Onboard fatalities
Unknown
Route
From Valdosta Regional Airport (VLD), Valdosta, GATo Tuscaloosa National Airport (TCL), Tuscaloosa, AL
Aircraft age
About 39 years (built 1975)
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 · cruise
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 power plant
  • Personnel issues › Task performance

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

NTSB narrative

The pilot receiving instruction reported that, about 1 hour into the flight, the engine "clunked and shuddered" and then lost total power. The flight instructor assumed control of the airplane and maneuvered it toward a nearby airport, and the pilot receiving instruction initiated an unsuccessful restart of the engine. After determining that the airplane was not going to reach the airport, the flight instructor executed a forced landing to a road, which resulted in substantial damage to the wings and firewall.

Examination of the engine crankshaft revealed that it had fractured at the No. 2 main bearing journal; the fracture surface exhibited evidence consistent with fatigue crack propagation. The adjacent bearing materials had deformed and disintegrated. The failure of these components likely preceded the final fracture of the crankshaft. The bearing components from this section were generally too damaged to conclude the mode of failure. However, examination of the No. 6 bearing components and connecting rod bearing journal exhibited wear patterns and damage consistent with oil starvation; the oil starvation likely resulted from bearing movement, which can result from inadequate torque on the engine case through bolts. Although the torque values on the through bolts could not be determined, the failure of the engine's internal components and the oil starvation were consistent with the through bolts not being torqued properly. Further, the damage was also consistent with damage found on another airplane engine that had experienced a crankshaft failure and oil starvation, which was determined to had been caused by the engine through bolts not being properly torqued (NTSB accident number ERA14LA193). A review of maintenance records revealed that maintenance personnel had replaced the Nos. 2, 3, and 6 engine cylinders about 3 months before the accident. It is likely that maintenance personnel did not torque the through bolts in accordance with the manufacturer's specifications during this maintenance and that this led to the eventual fracture of the crankshaft.

Further, during postaccident engine examination, metal particles were found in the oil sump. The maintenance records indicated that the engine oil was changed the day before the accident. However, the entry did not indicate that the oil filter was dissected or that the filter element was examined. It is likely that maintenance personnel did not examine the oil filter after the oil change and that, if they had examined the oil filter element, they would have detected the metal particles, which would have indicated an impending failure of an internal engine component.

Probable cause

Maintenance personnel’s failure to properly torque the engine case through bolts, which resulted in the fatigue fracture of the crankshaft and subsequent total loss of engine power.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA14LA179
Event ID
20140403X84610
Case number
ERA14LA179
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. 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: 1e3d8d64e7d41aefaaff23be4adcc23b39177c35f9951bab1d69da3683947612; retrieved 2026-09-15T23:28:46.108Z.