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

Cessna 421 accident near Tulsa, Oklahoma, July 11, 2010

On July 11, 2010 at about 3:05 am local time, a Cessna 421, registered N88DF, was substantially damaged in an accident during approach (VFR pattern final) near Tulsa, Oklahoma (Tulsa International Airport). It was a business flight under general aviation rules (Part 91). 3 people were killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot’s inadequate preflight fuel planning and management in-flight, which resulted in total loss of engine power due to fuel exhaustion. Contributing to the accident was the pilot’s use of performance-impairing medications.

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

What the record shows

Date
July 11, 2010 · about 3:05 am local time · cases in 2010
Place
Tulsa, Oklahoma · Tulsa International Airport · cases near this airport · map
Type
Accident
Injuries
3 people were killed.
Weather
visual conditions (good weather)
Aircraft
Cessna 421 A · all 421s on the register
Registration
N88DF · registry record · serial 421A0084
Damage
Substantial damage
Flight
Business flight · general aviation rules (Part 91)

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

During the 3.5-hour flight preceding the accident flight, the airplane used about 156 gallons of the 196 gallons of usable fuel. After landing, the airplane was topped off with 156 gallons of fuel for the return flight. During the preflight inspection, a line serviceman at the fixed based operator observed the right main fuel tank sump become stuck in the open position. He estimated 5 to 6 gallons of fuel were lost before the sump seal was regained, but the exact amount of fuel lost could not be determined. The lost fuel was not replaced before the airplane departed. Data from an onboard GPS unit indicate that the airplane flew the return leg at an altitude of about 4,500 feet mean sea level for about 4 hours. About 4 minutes after beginning the descent to the destination airport, the pilot requested to divert to a closer airport. The pilot was cleared for an approach to runway 18R at the new destination. While on approach to land, the pilot reported to the air traffic control tower controller, “we exhausted fuel.” The airplane descended and crashed into a forested area about 1/2 mile from the airport. Postaccident examination of the right and left propellers noted no leading edge impact damage or signatures indicative of rotation at the time of impact. Examination of the airplane wreckage and engines found no malfunctions or failures that would have precluded normal operation. The pilot did not report any problems with the airplane or its fuel state before announcing the fuel was exhausted. His acceptance of the approach to runway 18R resulted in the airplane flying at least 1 mile further than if he had requested to land on runway 18L instead. If the pilot had declared an emergency and made an immediate approach to the closest runway when he realized the exhausted fuel state, he likely would have reached the airport. Toxicological testing revealed cyclobenzaprine and diphenhydramine in the pilot’s system at or above therapeutic levels. Both medications carry warnings that use may impair mental and/or physical abilities required for activities such as driving or operating heavy machinery. The airplane would have used about 186 gallons of fuel on the 4-hour return flight if the engines burned fuel at the same rate as the previous flight. The fuel lost during the preflight inspection and the additional 30 minutes of flight time on the return leg reduced the airplane’s usable fuel available to complete the planned flight, and the pilot likely did not recognize the low fuel state before the fuel was exhausted due to impairment by the medications he was taking.

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. Miscellaneous/other during prior to flight
  2. Aircraft servicing event during prior to flight
  3. Fuel exhaustion during approach (VFR pattern final) defining event
  4. Loss of engine power (total) during approach (VFR pattern final)

The NTSB's findings

  • factor Personnel issues › Physical › Impairment/incapacitation › Prescription medication › Pilot
  • cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • cause Aircraft › Fluids/misc hardware › Fluids › Fuel › Fluid level other cases naming the fuel system

Pilot

  • Certificate: private
  • Ratings: multi-engine land; single-engine land
  • Flight time: 592 hours in all; 67 in this make and model
  • Last flight review: November 3, 2009
  • Medical certificate: Class 3 (with waivers/limitations)
  • Injury: fatal

Crew member

No details recorded.

The aircraft

  • Airframe total time: 640 hours
  • Last inspection: annual inspection, November 20, 2009
  • Maximum gross weight: 7,450 lb
  • Seats: 6
  • Landing gear: retractable
  • Engine 1: Continental GTSIO520 (piston); 0 hours total
  • Engine 2: Continental GTSIO520 (piston); 0 hours total
  • Fire on the ground

The flight

  • Departed from: PTK Pontiac MI at 11:03 pm
  • Destination: RVS Tulsa OK
  • Flight plan: none
  • Runway 18R, 6,101 ft by 150 ft
  • A second pilot was aboard

Weather at the time

  • Light: night
  • Wind: from 140° at 5 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 81°F (27°C), dew point 73°F (23°C)
  • Altimeter: 29.88 inHg
  • Observation at 2:53 am from TUL, 1 miles away

Injuries

FatalSeriousMinorNone
Flight crew2
Passengers1

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

14 documents, released by the NTSB on May 30, 2013. 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 Global Positioning System Device - Specialist's Factual Report PDF, 6 pages View Download
2 Global Positioning System Device - Attachment 1 - Tabular Data - Accident Flight - (Csv Format) data file Download
3 Global Positioning System Device - Attachment 2 - Tabular Data - Previous Flight - (Csv Format) data file Download
4 Engine Instrument(s) - Specialist's Factual Report PDF, 6 pages View Download
5 Witness Emails PDF, 3 pages View Download
6 Toxicological Report - Pilot PDF, 2 pages View Download
7 Toxicological Report - Pilot Rated Passenger PDF, 1 page View Download
8 Statement of Party Representatives to NTSB Investigation PDF, 3 pages View Download
9 Medical Factual PDF, 1 page View Download
10 Maps or Charts of Accident Area, Wreckage Diagrams PDF, 2 pages View Download
11 Photo 1 - Wreckage PDF, 1 page View Download
12 Photo 2 - Wreckage PDF, 1 page View Download
13 PHOTO-3 - Wreckage PDF, 1 page View Download
14 Airport Diagram PDF, 1 page View Download

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/CEN10FA382.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.