FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN93LA072 · Cessna 150M

1 Jul 1993 · HASWELL, CO, United States

Cessna 150M · Accident: airframe, component or system failure en route

From FTG · WATKINS, CO to La Junta Municipal Airport (LHX)

Report a problem

Event

NTSB case
DEN93LA072
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 150M

Aircraft type
Cessna 150
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
N704QR
Onboard fatalities
Unknown
Route
From FTG · WATKINS, COTo La Junta Municipal Airport (LHX), Lamar, 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
Airframe, component or system failure
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

  • Pilot in command › Aircraft control, not maintained

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

WHILE ON A STUDENT SOLO CROSS COUNTRY TRAINING FLIGHT, THE ALTERNATOR FAILED AND THE STUDENT FAILED TO RECOGNIZE THE FAILURE. THE LORAN, WHICH HE WAS USING FOR NAVIGATION, FAILED SO HE SWITCHED TO THE VOR. THAT ALSO FAILED AND HE THEN NOTICED HIS FUEL GAUGES WERE LOW AND THOUGHT HE WAS RUNNING OUT OF FUEL. THE STUDENT PILOT ATTEMPTED TO LAND ON A RURAL ROAD AND WENT OFF THE SIDE OF THE ROAD INTO A DITCH. THE FLIGHT DEPARTED WITH FULL FUEL WHICH PROVIDES APPROXIMATELY 4 HOURS AND 30 MINUTES ENDURANCE. THE ACTUAL DURATION OF THE FLIGHT WAS 1 HOUR AND 45 MINUTES.

Probable cause

FAILURE OF THE STUDENT PILOT TO MAINTAIN CONTROL OF THE AIRCRAFT DURING LANDING ROLL. FACTORS WERE: ALTERNATOR FAILURE, FAILURE OF THE STUDENT PILOT TO FOLLOW PROCEDURES AND DIRECTIVES, AND FAILURE OF THE STUDENT PILOT TO PERFORM FUEL CONSUMPTION CALCULATIONS.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DEN93LA072
Event ID
20001211X12886
Case number
DEN93LA072
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. 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: 0693969314e330a76dd92972cdc5783717d09410e3f07febfae9521d3df69c4c; retrieved 2026-09-23T01:55:05.649Z.