FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Flight Express Cessna 210L accident

8 Jun 2010 · Tampa, FL, United States

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

From Tampa International Airport (TPA) to Fort Lauderdale Executive Airport (FXE)

Report a problem

Event

NTSB case
ERA10LA307
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
Charter & commuter
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 210L

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
N2263S
Onboard fatalities
Unknown
Route
From Tampa International Airport (TPA), Tampa, FLTo Fort Lauderdale Executive Airport (FXE), Fort Lauderdale, FL
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 135: Air Taxi & Commuter
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 power plant

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

NTSB narrative

The airplane was climbing when the engine lost partial power. The pilot turned back toward the departure airport and the engine lost total power. During the subsequent forced landing, the airplane struck a fence, which resulted in substantial damage to the fuselage and left wing. Examination of the engine crankcase halves revealed fretting at the No. 2 main bearing saddle surfaces, which indicated insufficient clamping force during assembly due to inadequate torque on the bolts. The No. 2 main bearing was broken into pieces, which were observed in the oil sump. Examination of the crankshaft revealed a fatigue fracture that initiated in the fillet between the No. 2 main journal and the cheek at the aft end of the journal. The fatigue crack features observed in the No. 2 main bearing were secondary and were a result of high stresses on the bearing as it shifted. This most likely resulted from insufficient bearing crush due to insufficient clamping force on the crankcase saddle surfaces. According to the engine logbooks, a 100-hour maintenance inspection occurred 19.5 hours prior to the accident, which required a mechanic to verify that the crankcase bolts did not exhibit looseness.

Probable cause

The total loss of engine power due to inadequate torgue on the crankcase bolts. Contributing to the accident was the inadequate inspection performed 19.5 hours prior to the accident.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA10LA307
Event ID
20100609X51932
Case number
ERA10LA307
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2010-06-09.
  • API snapshot SHA-256: 1865bfabde4444067596225206783af5ca9db54e352dca7b27b1bdecf9d78066; retrieved 2026-09-15T14:25:54.123Z.