DEN04LA128 · Beech 95-B55
Beech 95-B55 · Accident: total loss of engine power (non-mechanical) en route
From Roosevelt Municipal Airport (74V) to GJT · Roosevelt, UT
Event
- NTSB case
- DEN04LA128
- 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
- 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
Beech 95-B55
- Aircraft type
- Beechcraft 55
- 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
- N120F
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Roosevelt Municipal Airport (74V), Roosevelt, UTTo GJT · Roosevelt, 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
- En route · climb to 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
- Tree(s)
- 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
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, the left engine began to run rough shortly after departing runway 07. He noticed a loss in indicated fuel pressure and within a few moments, the left engine lost power and then quit. The pilot made several unsuccessful attempts to restart the engine. The pilot attempted an immediate left turn to return to the airport. The 270-degree left turn resulted in a loss of altitude and improper line-up with runway 25. The pilot completed a 90-degree right turn as the airplane crossed the airport's access road. The airplane continued to descend as it struck several trees and impacted terrain southwest of the airport. The impact separated both engines and the nose and main landing gear assemblies from the fuselage. Approximately 3 feet of the outboard section of each wing was crushed upwards and aft. According to an FAA inspector, the mixture was in the full rich position and the fuel boost pumps were off. Although the airplane's right wing was compromised, there was visible fuel in the left wing.
Probable cause
the loss of engine power for undetermined reasons. A contributing factor was the lack of suitable terrain for a forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN04LA128
- Event ID
- 20040824X01274
- Case number
- DEN04LA128
- 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: 5947ec5246d3cb97fa1fdc46a863280f4d3ca83f7c3556ca3ba10680a7541ff8; retrieved 2026-09-21T19:09:41.190Z.