WPR15LA254 · Raudenbush Ernie LANCAIR SUPER ES
Raudenbush Ernie LANCAIR SUPER ES · Accident: loss of engine power (partial) en route
From El Paso International Airport (ELP) to Glendale Municipal Airport (GEU)
Event
- NTSB case
- WPR15LA254
- 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
Raudenbush Ernie LANCAIR SUPER ES
- Aircraft type
- Raudenbush Ernie LANCAIR SUPER ES
- 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
- N74ES
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From El Paso International Airport (ELP), El Paso, TXTo Glendale Municipal Airport (GEU), Glendale, AZ
- Aircraft age
- About 15 years (built 2000)
- 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
- Defining eventThe 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 (partial)
- 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
- Not determined › Not determined
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
The commercial pilot stated that, about 1 hour into the cross-country personal flight, he observed a "slight" loss of engine power and "fluctuating" engine exhaust gas temperature indications. Shortly thereafter, the engine experienced a significant loss of power, and the pilot subsequently chose to perform a forced landing to a rocky plateau, during which the airplane sustained substantial damage. Following the pilot's egress, the airplane was consumed by a postimpact fire. The engine was examined and disassembled following the accident, and it displayed significant thermal damage. No anomalies were observed that would have precluded normal operation.
Probable cause
A partial loss of engine power for reasons that could not be determined because postaccident examination of the engine revealed no anomalies.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR15LA254
- Event ID
- 20150902X31943
- Case number
- WPR15LA254
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: cb519185958597f0a107a755f17f65038d78c1f5f4673b4cb930666d3ce30b07; retrieved 2026-09-16T02:44:31.104Z.