FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR22FA335 · Rutan VARIEZE

5 Sept 2022 · Columbia, CA, United States

Rutan VARIEZE · Accident: loss of engine power (total) on approach

Report a problem

Event

NTSB case
WPR22FA335
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
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

Rutan VARIEZE

Aircraft type
Rutan VARIEZE
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
N10EZ
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 29 years (built 1993)
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 pattern final
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

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot had been performing maintenance on the airplane and upgrading various systems. The accident flight was the first flight out of maintenance.

According to radar and ADS-B data, the airplane departed and the pilot executed several maneuvers before returning to the runway. The airplane then made a high-speed pass over the airport, reversed course, and approached the runway again. After a second high-speed pass over the runway, the airplane joined the traffic pattern for landing. As the airplane turned on final approach it was about 680 ft above ground level (agl) at an airspeed of about 70 knots. Over the next 24 seconds, it descended toward terrain at an airspeed of about 66 knots, coming to rest about 0.5 nautical miles (nm) from the runway.

A comparison of the airplane’s two approach paths revealed similar speeds and altitudes until the final approach., where the accident flight ADS-B data ends abruptly. At the last ADS-B return, the airplane would have been around 200 ft agl and there was a well-traveled road beneath the flight path.

Postaccident examinations revealed no definitive evidence of a failure with the flight control systems. The engine exhibited no evidence of preimpact catastrophic mechanical malfunction or failure, but the negligible damage to the propeller suggests that the engine was not operating at the time of impact. The close proximity of the accident site to the runway’s surface, additionally suggests that the airplane did not have adequate power to reach the runway.

The exact fuel quantity at impact could not be determined due to the airplane’s position at the accident site, though there was likely sufficient fuel.

During recent maintenance, the pilot modified the airplane to a dual-ignition system, replacing one of the magnetos with an electronic ignition system. The remaining magneto was improperly wired to the ignition, rendering it inoperable unless the keyed-ignition switch was set to the “BOTH” position. This would have made it impossible for the pilot to verify that both ignition systems were operable during the runup unless the electronic switch was activated and was operable, which could not be definitively determined. Disassembly of the magneto revealed fine carbon dust and a worn distributor brush, which could have impaired its performance.

The ignition key was found removed from the switch, which was in the OFF position, while the master switch was in the ON position. This suggests that the pilot was likely troubleshooting the ignition system before impact, as it is unlikely he would remove the key without turning off the master switch during an engine-out procedure.

The electronic ignition system wiring had two separations where the splices were not properly crimped, allowing the wires to come loose. It is unclear if these separations occurred during the impact. The electronic ignition switch was also found broken internally, with one disconnected wire, and therefore it is unknown if the electronic switch was ever operable. The wiring at the front of the airplane was stretched and hanging over a boulder, making it difficult to determine the damage to the wiring before impact.

If the electronic ignition wiring or switch had not been intact on the flight, the engine would have been operating solely on the magneto. If the pilot then turned the keyed ignition switch to the LEFT or RIGHT position, the magneto would have shut off, resulting in a total loss of power.

Probable cause

The pilot’s improper maintenance of the ignition system, which led to an ignition system failure and a loss of engine power.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR22FA335
Event ID
20220906105874
Case number
WPR22FA335
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: a0cbf66743314f9116f50ae6469801bba80e4f4d1453010903d22846eea8c44c; retrieved 2026-09-15T07:50:36.451Z.