WPR15LA262 · Graves Bryon S VANS RV-7A
Graves Bryon S VANS RV-7A · Accident: loss of engine power (partial) while maneuvering
From Byron Airport (C83) to Byron Airport (C83)
Event
- NTSB case
- WPR15LA262
- 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
Graves Bryon S VANS RV-7A
- Aircraft type
- Graves Bryon VANS RV-7A
- 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
- N507RV
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Byron Airport (C83), Byron, CATo Byron Airport (C83), Byron, CA
- Aircraft age
- About 6 years (built 2009)
- 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
- Maneuvering · aerobatics
- 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
- Substantial
Cause areas
- Aircraft › Aircraft power plant
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Shortly after takeoff, the private pilot began a series of aerobatic maneuvers in the experimental, amateur-built airplane. After executing two rolls, the engine began to run rough, and an instrument panel annunciator indicated that the ignition system had reverted to backup mode. Unable to maintain altitude, the pilot performed a forced landing to a field, where the airplane nosed over and sustained substantial damage.
The airplane's engine was equipped with a composite propeller and an FAA-certified ignition system, which used traditional magnetos combined with an electronic control module. The design was such that, should the electronic system fail or malfunction, the ignition system would revert to "backup" mode, operating on the traditional magnetos. Postaccident examination revealed that the steel magneto drive gear for the left magneto had broken off and fallen into the engine accessory case. Based on the damage signatures to the gear teeth and its shaft, it is most likely that a foreign object within the engine crankcase or accessory case moved into the path of the gear drivetrain during inverted flight, imparting a heavy side load on the gear and separating it from the magneto.
The system was designed to tolerate such a failure and revert to backup mode on the remaining magneto with only a minimal loss of engine power. However, postaccident examination revealed that the right magneto's internal contact point timing ("E" gap) was offset by about 16 degrees. This was likely the result of an improper adjustment during overhaul of the magneto, which was completed at a repair facility about 20 flight hours prior to the accident. This internal error would not have been visible to the pilot (builder), who followed the correct procedures to reinstall the magneto and synchronize it to the engine. Under this condition, the engine-to-magneto timing would have been correct, but the magneto's internal timing was wrong, resulting in a reduction of energy available for the spark plugs. This error would not have been a factor under normal operation, because the electronic ignition system did not use the magneto timing points.
The error should have been noticeable during the pre-takeoff engine magneto check, because the system reverted to backup mode as the ignition was switched from BOTH to either the LEFT or RIGHT magneto position. However, it is possible that engine and environmental variables, or operating conditions at the departure airport's elevation, were sufficient to mask the lower spark energy during ground run-up, but not in the more demanding environment of powered flight.
Probable cause
Improper overhaul of the right magneto, which eliminated system redundancy, and resulted in a loss of engine power when the left magneto failed during aerobatic flight maneuvers.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR15LA262
- Event ID
- 20150921X31115
- Case number
- WPR15LA262
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2015-09-21.
- API snapshot SHA-256: ec3b5c5b40c74d1e8ec0fe025f697fbdffa001c1f7430db25ecd5751b87dac12; retrieved 2026-09-16T02:47:37.975Z.