CEN19LA326 · Vans VANS RV-10
Vans VANS RV-10 · Accident: loss of engine power (partial) on approach
From Lancaster Airport (LNC) to Lancaster Airport (LNC)
Event
- NTSB case
- CEN19LA326
- 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
Vans VANS RV-10
- Aircraft type
- Vans RV-10
- 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
- N569JC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Lancaster Airport (LNC), Lancaster, TXTo Lancaster Airport (LNC), Lancaster, TX
- Aircraft age
- About 9 years (built 2010)
- 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
- Approach · VFR go-around
- 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
- Environmental issues › Physical environment
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Just after takeoff following a touch-and-go landing, the engine backfired and lost partial power. The pilot decided that he could not land on the remaining runway, so he continued to climb the airplane, raised the flaps, and increased airspeed. The manifold pressure continued to decrease despite the pilot’s application of full throttle, and the pilot attempted to return to the airport, but had insufficient altitude, and conducted a forced landing to a field. The nose landing gear sheared off, and the main landing gear collapsed. Both wings sustained substantial damage.
Examination of the engine and accessories revealed that the left magneto fired on only 3 of its 6 terminals. The airplane was equipped an electronic ignition system that was coupled to the magnetos. The system created multiple sparks over a longer duration and synchronized timing between the two magnetos. This synchronization was accomplished by using the left magneto as a trigger for the complete system. When the electronic ignition was operating, it relied solely on the left magneto points to fire both magnetos with an enhanced multi-spark. If the left magneto failed or deteriorated, then the complete ignition cycle would be compromised. The degraded functionality of the left magneto was likely the cause of the partial engine power loss.
Probable cause
A partial loss of engine power due to a faulty magneto/ignition system, which resulting in a forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN19LA326
- Event ID
- 20190923X91342
- Case number
- CEN19LA326
- 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, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2019-09-21.
- API snapshot SHA-256: 2223a7224e995519e47865471a5eb3e6a2ad130cc19058389e6591a7c253dc0c; retrieved 2026-09-16T10:12:15.376Z.