DEN91LA014 · Cessna T-210-M
Denver Air Center Cessna T-210-M · Accident: total loss of engine power (non-mechanical) en route
From Scottsdale Airport (SDL) to Rocky Mountain Metropolitan Airport (BJC)
Event
- NTSB case
- DEN91LA014
- 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
- 0 · all aircraft and ground
- Ground fatalities
- 0
- 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 T-210-M
- Aircraft type
- Cessna T-210
- 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
- N621BD
- Operator
- Denver Air Center
- Onboard fatalities
- Unknown
- Route
- From Scottsdale Airport (SDL), Scottsdale, AZTo Rocky Mountain Metropolitan Airport (BJC), Broomfield, CO
- 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
- En route · cruise
- 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
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Fluid, fuel › Exhaustion
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PRIVATE PILOT WAS FLYING FIVE PASSENGERS ON A ROUND TRIP CROSS COUNTRY FLIGHT. ACCORDING TO THE PASSENGERS, THEY PAID THE PILOT FOR THE FLIGHT. THE PILOT SAID HE TOOK OFF WITH WHAT HE ESTIMATED WAS 64 GALLONS OF FUEL. TWO HOURS AND TWENTY FIVE MINUTES LATER, HE REPORTED THAT THE PLANE WAS OUT OF FUEL, AND HE ATTEMPTED AN ENGINE OUT LANDING TO RUNWAY 33. THE PLANE LANDED 400 FEET SHORT OF THE RUNWAY, STRUCK A FENCE, SHEARED THE NOSE GEAR, AND NOSED OVER. THE PLANE CAME TO REST INVERTED 40 YARDS SHORT OF THE RUNWAY. BOTH WINGS, THE CABIN AND FUSELAGE WERE SUBSTANTIALLY DAMAGED. THE RESCUE PERSONNEL AND LAW OFFICERS ON THE SCENE REPORTED THE TANKS WERE EMPTY AND NO FUEL SPILL WAS FOUND AT THE ACCIDENT SCENE. THE INVESTIGATION FOUND NO FUEL IN THE ENGINE SYSTEM, AND COULD FIND NO EVIDENCE TO EXPLAIN ANY INCREASED FUEL USAGE.
Probable cause
THE PILOT MISJUDGED THE FUEL SUPPLY RESULTING IN FUEL EXHAUSTION.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN91LA014
- Event ID
- 20001212X24458
- Case number
- DEN91LA014
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1990-10-29.
- API snapshot SHA-256: 15c60278e50224b74480d65378c7e22c46e8c8e72b3a6a036c592f2524db9edf; retrieved 2026-09-21T23:42:37.598Z.