ERA23FA188 · Miller Glenn F RV-12
Miller Glenn F RV-12 · Accident: loss of engine power (partial) during initial climb
Event
- NTSB case
- ERA23FA188
- 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
- 1 · 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
Miller Glenn F RV-12
- Aircraft type
- Miller Glenn RV-12
- 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
- N543GM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 2 years (built 2021)
- 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
- Initial climb
- 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
- Aircraft › Aircraft power plant
- Aircraft › Fluids/miscellaneous hardware
- Environmental issues › Physical environment
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
Two commercial pilots departed for a local flight in the experimental amateur-built airplane that was undergoing Phase 1 flight testing. The purpose of the flight was to perform aerodynamic stall testing. Earlier in the day, the right-seat pilot had completed a solo flight. Upon returning to the airport, the left-seat pilot boarded the airplane and they taxied for takeoff. During the climb, about 400 ft above ground level, the airplane sustained an abrupt partial loss of engine power. The airplane immediately stopped climbing and the pilot entered a left turn, then turned left again to fly over a highway that paralleled the departure runway. The pilots attempted to troubleshoot the partial loss of engine power by adjusting the throttle and mixture, and by ensuring that both fuel pumps were on, but were unable to restore engine power. The airplane continued toward an overpass, under which a semi-truck was parked, and near which powerlines spanned across the highway. The pilots attempted to fly under the powerlines and over the overpass, but entered an extreme bank angle and impacted the overpass before coming to rest inverted below it. A post-crash fire ignited immediately. The right-seat pilot was pulled from the wreckage by motorists; the left-seat pilot was fatally injured. Examination of the engine found that the Nos. 1 and 2 cylinder spark plug electrode tips were obliterated. The Nos. 3 and 4 cylinder spark plug electrode tips remained intact, but were found blackened. There was no evidence that any of the spark plugs had sustained impact-related damage. A bench test of the spark plugs found that the Nos. 1 and 2 plugs would produce a spark at low compression, but would extinguish under the higher compression levels produced during normal engine operation. The Nos. 3 and 4 cylinder spark plugs produced normal spark at the bench test’s maximum compression. It is likely that the partial loss of engine power was due to the damaged Nos. 1 and 2 spark plug electrode tips. The owner/builder of the airplane stated that he used low-grade 87 octane automotive fuel with the engine in its first 9 hours of operation about two years before the accident. The engine manufacturer required that the engine be operated with at least 89 octane automotive fuel or higher grade. The manual and engine manufacturer further reported that using low grades of automotive fuel could result in engine detonation and/or catastrophic failure. The operations manual further stated that, when stored for 3 months or longer, the airplane should be stored with 100 low lead aviation fuel. The airplane owner reported that the airplane sat idle for nearly two years, during which occasional engine run-ups were performed, and that the fuel onboard during this time was automotive fuel with a fuel preservative/additive. Despite the surviving pilot reporting that he fueled the airplane with 93 octane automotive fuel for his recent flight activity and the accident flight, it is likely that the estimated first 9 hours of engine operation with the lower grade of fuel, and old automotive fuel, likely contributed to the degradation and ultimate failure of the Nos. 1 and 2 spark plug electrodes during the accident flight. Although the engine lacked other signatures of detonation, it is likely that the spark plug damage was due to detonation occurring at some point in the airplane’s 20 total hours of engine operation. There was no evidence that the spark plugs had been inspected or replaced during the required annual condition inspection seven months before the accident. According to the pilot’s operating handbook, the landing distance was 525 ft. During the pilots’ engine troubleshooting, they overflew more than 4,000 ft of a multilane highway with a wide grass median. Had either pilot decided to make an immediate precautionary off-airport landing either on the grass median or the highway, rather than continuing the engine troubleshooting at low altitude, the conflict with powerlines and the collision with the overpass likely could have been prevented. It is also likely that the partial loss of engine power, rather than a total loss of power, exacerbated the confusion and indecision by both pilots on whether an immediate precautionary landing should be made. The engine examination findings and testing of the spark plugs supported a scenario in which the engine likely would continue to run, but could not produce sufficient power to climb. Toxicology testing for the fatally injured left-seat pilot detected Carboxyhemoglobin at 15%, consistent with smoke inhalation after the accident, glucose, and acetaminophen. The testing was negative for ethanol.
Probable cause
The airplane owner/builder’s inappropriate use of a lower grade fuel than that required by the airplane and engine operations manual, which resulted in engine detonation and the degradation and eventual obliteration of the Nos. 1 and 2 cylinder spark plug electrode tips. Contributing to the outcome was the pilots’ decision to continue flight at low altitude following a partial loss of engine power instead of performing an immediate precautionary landing, which resulted in collision with an overpass and terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA23FA188
- Event ID
- 20230411107039
- Case number
- ERA23FA188
- 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, cause areas. 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: d7647d9892c2433db8ded025c4a660dac3403e80d0248d8f6e7410bfaaf1bdb4; retrieved 2026-09-15T07:58:43.367Z.