FTW96LA293 · Beech A23-19
Beech A23-19 · Accident: loss of engine power en route
From Pueblo Memorial Airport (PUB) to Hanksville Airport (HVE)
Event
- NTSB case
- FTW96LA293
- 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
Beech A23-19
- Aircraft type
- Beechcraft 23
- 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
- N5675S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Pueblo Memorial Airport (PUB), Pueblo, COTo Hanksville Airport (HVE), HANKSVILLE, 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 · 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
- Loss of engine power
- 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
The pilot crossed Salida Airport at 8,200 feet and approached Monarch Pass (elevation 11,312 feet) at 10,500 feet. The pilot said the engine 'popped twice' and power dropped 600-700 rpm from a setting of 2,450 rpm. The pilot attempted to land on U.S. Highway 50, but was forced to pull up and bank sharply due to an approaching vehicle. The airplane landed hard and collided with terrain. Postaccident functional testing of the engine resulted in full power being developed. The distance between Salida and Monarch Pass is 17.5 miles. Computed density altitude at Monarch Pass was 15,061 feet msl. According to the Beech Aircraft Company, at best rate of climb airspeed of 70 knots, the airplane would be capable of climbing 270 fpm and 50 fpm at 8,000 feet and 12,000 feet, respectively.
Probable cause
a reported power loss for reasons undetermined.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW96LA293
- Event ID
- 20001208X06215
- Case number
- FTW96LA293
- 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: cba0e2a4e82e8939437a27132c73acd7ec9ac2d30a96957f43eb3acacf6748d5; retrieved 2026-09-22T21:58:57.932Z.