FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN03FA068 · Cessna 310D

17 Apr 2003 · Provo, UT, United States

Advantage Aviation Cessna 310D · Accident: total loss of engine power (non-mechanical) on approach

From Provo Municipal Airport (PVU) to Provo Municipal Airport (PVU)

Report a problem

Event

NTSB case
DEN03FA068
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
3 · 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
General aviation
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 310D

Aircraft type
Cessna 310
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
N6861T
Onboard fatalities
Unknown
Route
From Provo Municipal Airport (PVU), Provo, UTTo Provo Municipal Airport (PVU), Provo, UT
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 91: General Aviation
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
Approach · VFR pattern downwind
First occurrenceThe 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
Total loss of engine power (non-mechanical)
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Fuel exhaustion; Stall/spin
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Dual student › Aircraft control, not maintained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane's main fuel tanks were full (100 gallons useable) when it departed on a 1.6 hour instructional flight. The auxiliary fuel tanks had been placarded inoperative. Visual inspection confirmed the tanks were half-full at the conclusion of the flight. The accident flight took off and was aloft for approximately 1.7 hours. It, too, was an instructional flight. According to a tape recording and transcript of radio communications, the instructor reported they would be entering a right downwind for runway one eight, flying a single engine pattern. Shortly thereafter, he called the pilot of an airplane that was in front on them and asked, "Can we get priority to the runway? We've got a difficulty." The consensus of 27 witnesses was that the airplane made a steep right turn from base leg to final approach, and then it descended vertically to the ground, exploded on impact, and burned. Measurements taken indicated the landing gear was retracted and the flaps were extended 5 degrees. It was noted that when the rudder was aligned with the vertical stabilizer, the rudder trim tab was fully deflected to the right. Measurement of the rudder actuator confirmed this observation (left rudder). The right aileron trim tab was deflected full up (aileron down, wing up). Measurement of the elevator trim tab actuator indicated the tab was 15 degrees down (elevator up). According to the Cessna Aircraft Company, this is about half of the total deflection range. Disassembly of the engines revealed no anomalies. Components and accessories were bench tested and found to operate satisfactorily within service limits. Disassembly of the propellers revealed neither propeller was feathered. The left propeller was at the low pitch stop, and the right propeller was just past this position (low power). According to the airplane's Climb Data and Cruise Performance Charts, each engine will consume between 14.9 and 26.6 gallons per hour (gph) at 7,500 feet msl and under standard atmospheric conditions, depending on power setting (manifold pressure and rpm). During climb between 5,000 and 7,500 feet msl, each engine will consume between 6.2 and 7.5 gph (depending on power setting). Airworthiness Directive 69-15-09, entitled "To Prevent Fuel Starvation During High Angle Descent," was issued to mandate compliance with Cessna Service Letter ME69-19, entitled "Minimum Fuel and Power Setting Placards." The service letter stated (in part), "Operation with less than five gallons of fuel in each main tank is prohibited. Useable fuel in each tank is 45 gallons. Maintain power within the green arc during descent."

Probable cause

failure of the student to maintain aircraft control. Contributing factors were the instructor's inattention to the fuel supply, fuel exhaustion, an inadvertent stall/spin during the turn from base leg to final approach. and the instructor's inadequate supervision of the flight.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DEN03FA068
Event ID
20030428X00586
Case number
DEN03FA068
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: e2ede2c7fd449ec66f143a54a1dd9f26a166d8be6d1796db5f2821fa2efb9896; retrieved 2026-09-20T19:18:00.088Z.