eFlight
Accidents · NTSB ERA10LA307 · Final report

Cessna 210L accident near Tampa, Florida, June 9, 2010

On June 9, 2010, a Cessna 210L, registered N2263S, was substantially damaged in an accident during initial climb near Tampa, Florida (Tampa International Airport). It was flown under charter and air-taxi rules (Part 135). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
June 9, 2010 · cases in 2010
Place
Tampa, Florida · Tampa International Airport · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 210L · all 210Ls on the register
Registration
N2263S · no longer on the register · serial 21061207
Damage
Substantial damage
Flight
Flight · charter and air-taxi rules (Part 135)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Loss of engine power (total) during initial climb defining event
  2. Off-field or emergency landing during emergency descent
  3. Collision with terrain or object (not controlled flight into terrain) during landing

The NTSB's findings

  • cause Aircraft › Aircraft power plant › Engine (reciprocating) › Recip eng cyl section › Fatigue/wear/corrosion other cases naming the engine
  • factor Personnel issues › Action/decision › Action › (general) › Maintenance personnel
  • factor Personnel issues › Task performance › Maintenance › Scheduled/routine maintenance › Maintenance personnel

Pilot

  • Certificate: flight instructor, commercial pilot
  • Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
  • Flight time: 1,300 hours in all; 10 in this make and model; 96 in the last 90 days; 28 in the last 30 days; 1,280 as pilot in command; 250 on instruments
  • Last flight review: June 3, 2010
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 13,710 hours
  • Last inspection: 100-hour inspection, May 27, 2010; 20 hours since
  • Maximum gross weight: 3,500 lb
  • Seats: 6
  • Landing gear: retractable
  • Engine: Cont Motor IO 520 SERIES (piston); 0 hours total
  • Operator: Flight Express INC

The flight

  • Departed from: TPA Tampa FL
  • Destination: FXE Fort Lauderdale FL
  • Flight plan: IFR

Weather at the time

  • Light: night
  • Wind: from 070° at 8 knots, gusting 18
  • Visibility: 10 statute miles
  • Sky: a few clouds at 6,000 ft
  • Temperature: 86°F (30°C), dew point 66°F (19°C)
  • Altimeter: 30.04 inHg

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

10 documents, released by the NTSB on October 25, 2011. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/ERA10LA307.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.

Aircraft

By kindModelsMakersEnginesFleetsWhat changed

Fly

Plan a flightAirportsLive mapRoutes and flightsFuels

Training and work

TrainingFlight schoolsGround schoolsPilot examinersMedical examinersJobs

Companies

DirectoryCharter operatorsFBOsRepair stationsClaim your listing

Safety and data

AccidentsRecords checkAnalyticsSAFxCHANGEThe graphAbout

Colours follow your device's light or dark setting.