The U.S. aircraft register, updated daily
Accidents · NTSB CEN11LA101 · Final report

Beech 95-C55 accident near Claremore, Oklahoma, December 3, 2010

On December 3, 2010 at about 11:40 pm local time, a Beech 95-C55, registered N211DS, was substantially damaged in an accident during emergency descent near Claremore, Oklahoma (Claremore Regional Airport). It was a personal flight under general aviation rules (Part 91). 1 person was seriously injured and 1 person had minor injuries. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

A loss of engine power on both engines for undetermined reasons.

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

What the record shows

Date
December 3, 2010 · about 11:40 pm local time · cases in 2010
Place
Claremore, Oklahoma · Claremore Regional Airport · cases near this airport · map
Type
Accident
Injuries
1 person was seriously injured and 1 person had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Beech 95-C55 · all 95-C55s on the register
Registration
N211DS · registry record · serial TE-237
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

While in the traffic pattern at the destination airport, the pilot experienced a loss of engine power on the left engine followed by a loss of engine power on the right engine. The pilot reported that there was not enough airspeed or altitude to reach the airport so he performed an off-field landing resulting in substantial damage to the airplane. The pilot reported that he had encountered a loss of engine power on both engines on two previous occasions. Both events were preceded by the reduction of engine power under rich mixture conditions. An examination of the left and right engines, and right side fuel system revealed no anomalies. The left fuel tank and fuel system were damaged by the fire and could not be examined for continuity. Data recovered from the engine monitor illustrated a decrease in exhaust gas temperature on the right engine approximately one minute prior to the decrease of exhaust gas temperature on the left engine. The reason for the loss of engine power on both engines could not be determined.

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 approach (VFR pattern base)
  2. Loss of engine power (total) during emergency descent defining event

The NTSB's findings

  • cause Aircraft › Aircraft power plant › Power plant › (general) › Failure other cases naming the engine
  • cause Not determined › Not determined › (general) › (general) › Unknown/Not determined

Pilot

  • Certificate: private
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 404 hours in all; 298 in this make and model; 30 in the last 90 days; 11 in the last 30 days; 297 as pilot in command
  • Last flight review: November 13, 2010
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: serious injuries

The aircraft

  • Airframe total time: 4,820 hours
  • Last inspection: annual inspection, May 11, 2010
  • Maximum gross weight: 5,700 lb
  • Seats: 6
  • Landing gear: retractable
  • Engine 1: Cont Motor IO 520 C15B (piston); 0 hours total
  • Engine 2: Cont Motor IO 520 C15B (piston); 0 hours total
  • Fire on the ground

The flight

  • Departed from: KJSO Jacksonville TX at 10:10 pm
  • Destination: KGCM Clairmore OK
  • Flight plan: IFR

Weather at the time

  • Light: night
  • Wind: from 170° at 13 knots, gusting 17
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 61°F (16°C), dew point 32°F (0°C)
  • Altimeter: 30.04 inHg
  • Observation at 11:59 pm from KGCM

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

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

8 documents, released by the NTSB on June 15, 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.

#DocumentWhat it is
1 Engine Instrument(s) - Specialist's Factual Report PDF, 10 pages View Download
2 Engine Instrument(s) - Attachment 1 - Tabular Data - OPT-1 - (Csv Format) data file Download
3 Engine Instrument(s) - Attachment 2 - Tabular Data - Gem 1200 - (Csv Format) data file Download
4 Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 PDF, 10 pages View Download
5 Witness Statements PDF, 2 pages View Download
6 Record of Telephone Conversation PDF, 1 page View Download
7 Fuel Selector Valve Examination PDF, 5 pages View Download
8 Statement of Party Representatives to NTSB Investigation PDF, 3 pages View Download

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

Other NTSB records under N211DS the same tail number, which may have belonged to a different aircraft at the time

1985-02-09ATL85LA092 · accident near Charleston, SC · substantial damage · no injuries

Connections how this case links to the rest of the register

Aircraft
Place
Record

The whole map of how records connect · these connections as data: /graph/accident/CEN11LA101.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.