Cessna 210 accident near Arbuckle, California, May 19, 2010
On May 19, 2010, a Cessna 210, registered N580TP, was substantially damaged in an accident during enroute (cruise) near Arbuckle, California (Colusa County Airport). It was a personal flight under general aviation rules (Part 91). 1 person had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
Insufficient clamping force to the connecting rod bolt, which resulted in looseness in the connecting rod bearing area that led to the fatigue fracture of the connecting rod and a subsequent loss of engine power.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- May 19, 2010
- Place
- Arbuckle, California · Colusa County Airport · map
- Type
- Accident
- Injuries
- 1 person had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 210 F · all 210s on the register
- Registration
- N580TP · no longer on the register · serial 21058810
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
During cruise flight, the pilot heard a loud “bang” and immediately observed oil coming from the engine cowling. The pilot subsequently initiated a forced landing and struck trees. A postaccident examination of the engine revealed two holes in the top of the crankcase between the Nos. 1 and 2 cylinders. The No. 2 connecting rod was visibly bent and no longer attached to the crankshaft. The end cap and a section of the yoke were separated and found outside of the engine case. The No. 2 cylinder piston, pin, connecting rod, and separated sections were sent to the National Transportation Safety Board’s materials laboratory for examination. A materials specialist determined that the damage to the connecting rod was a result of a high-cycle fatigue fracture. The fatigue in the location of the connecting rod would likely occur due to looseness in the connecting rod bearing area due to wear or damage to the bearing, small journal diameter, or insufficient clamping force from the connecting rod bolts. The bearing pieces did not show signs of significant wear and the journal diameter was not known. However, fretting was observed on the clamping surface of the connecting rod cap, which likely indicates that the connecting rod bolt had insufficient clamping force.
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
- Loss of engine power (total) during enroute (cruise) defining event
- Collision with terrain or object (not controlled flight into terrain) during emergency descent
The NTSB's findings
- cause Aircraft › Aircraft power plant › Engine (reciprocating) › Recip eng cyl section › Failure
- cause Aircraft › Aircraft power plant › Engine (reciprocating) › Recip eng cyl section › Fatigue/wear/corrosion
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 1,012 hours in all; 35 in this make and model; 35 in the last 90 days; 17 in the last 30 days; 1,012 as pilot in command
- Last flight review: April 3, 2010
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: minor injuries
The aircraft
- Airframe total time: 2,818 hours
- Last inspection: annual inspection, February 26, 2010; 33 hours since
- Maximum gross weight: 3,300 lb
- Seats: 4
- Landing gear: retractable
- Engine: Continental Motors IO-520 (piston); 0 hours total
The flight
- Departed from: O08 Colusa CA at 11:43 pm
- Destination: 32CL Knights Landing CA
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: from 130° at 5 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 79°F (26°C), dew point 30°F (-1°C)
- Altimeter: 29.95 inHg
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.