WPR18LA021 · Metcalfe Robert B VANS RV 6 UNDESIGNAT
Metcalfe Robert B VANS RV 6 UNDESIGNAT · Accident: loss of engine power (total) en route
From Fresno Chandler Executive Airport (FCH) to Fresno Chandler Executive Airport (FCH)
Event
- NTSB case
- WPR18LA021
- 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
Metcalfe Robert B VANS RV 6 UNDESIGNAT
- Aircraft type
- Metcalfe Robert VANS RV 6
- 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
- N88MV
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Fresno Chandler Executive Airport (FCH), Fresno, CATo Fresno Chandler Executive Airport (FCH), Fresno, CA
- Aircraft age
- About 17 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 · descent
- 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 (total)
- 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
- Aircraft › Aircraft systems
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that about 25 minutes into the local personal flight in the experimental amateur-built airplane, with all systems appearing to operate normally, he noticed that the batteries (located near his right foot) were getting hot and that the system voltage indicated about 15.5V, which was above the normal value of about 13V. Almost immediately thereafter, the engine lost total power. The pilot activated the bus manager emergency power switch and independently selected each of the two engine control units but was unable to restore engine power. He chose a rural road for a forced landing but changed his path to clear a truck on the road; the airplane impacted a vineyard on the side of the road, nosed over, and came to rest inverted.
The pilot had recently decided to change the carburetor and conventional magneto ignition systems to electronic versions for "performance and efficiency improvements." He purchased a kit that included an electronic fuel injection system and replaced the magnetos himself with a fully electronic ignition system.
After completing the installations, the pilot began testing the systems and engine operation. Two days before the accident flight, he conducted two flights of the airplane with the new systems; both flights were brief and uneventful.
Postaccident examination revealed no anomalies with the airplane fuel system or the engine itself. Because the engine was completely reliant on electricity for operation and control of the ignition and fuel injection, the cause of the engine power loss was likely due to a problem with the electrical system or supply. The only nonimpact-related anomaly discovered during the engine and airframe examination was that the swage/crimp of the terminal to the conductor of the primary alternator ground cable was loose, and the conductor and terminal bore evidence (black residue) of electrical arcing. The appearance was consistent with that residue having been caused by the looseness of the swage/crimp and as having been loose for an extended period before the accident. This looseness and arcing indicated that there were transient power interruptions. Such interruptions also create the potential for spurious electrical power variations, which could potentially interfere with the operation of the airplane's electrical or electronic systems, including the alternator, batteries, bus manager, and both the fuel injection and ignition systems.
Probable cause
The pilot’s failure to properly secure an alternator ground cable swage that led to problems with the electrical system and/or electronic engine controls, which resulted in a total loss of engine power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR18LA021
- Event ID
- 20171031X10251
- Case number
- WPR18LA021
- 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. 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: 698bd0d9b302a731b928c8a120dd69428d9da84ff73e4ab3c1dde4eebc931493; retrieved 2026-09-16T05:58:36.955Z.