WPR12FA059 · Vans RV7 - A Donahoe
Vans RV7 - A Donahoe · Accident: loss of engine power (total) en route
From Glendale Municipal Airport (GEU) to Glendale Municipal Airport (GEU)
Event
- NTSB case
- WPR12FA059
- 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
Vans RV7 - A Donahoe
- Aircraft type
- Vans RV7
- 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
- N724WD
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Glendale Municipal Airport (GEU), Glendale, AZTo Glendale Municipal Airport (GEU), Glendale, AZ
- Aircraft age
- About 5 years (built 2006)
- 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 · cruise
- 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 power plant
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot, who was also the owner and builder, was flying his experimental amateur-built airplane powered by a converted automobile engine back to his home airport after a brief personal out-and-back flight. Light winds and daylight visual meteorological conditions prevailed. Radar and GPS data showed that the return portion of the flight followed an essentially straight track in the direction of the pilot's home airport at an altitude of about 1,500 feet above ground level with a groundspeed of about 100 knots. When the airplane was about 12 miles from the airport, the groundspeed decreased to about 60 knots over a period of about 25 seconds. The airplane then entered a descent of about 800 feet per minute, which it maintained for the next minute. Shortly after the start of that descent, the transponder was switched to the emergency code of 7700. About 25 seconds later, the pilot transmitted a "mayday" call to the approach controller. He stated that he had a problem, and several seconds later, transmitted that he was "going down." In the radio call, the pilot named the component that he thought was causing the problem, but the transmission quality prevented a positive determination of exactly what the pilot said. The descent rate then increased rapidly, and the airplane impacted terrain several seconds later.
The damage to the rudder stop, rudder, elevator trim tab link, and elevator trim tab was inconclusive as to whether it occurred in flight or on impact. Propeller damage indicated that the propeller was not rotating or was rotating with little engine power. However, no preimpact mechanical problems with the engine, propeller gearbox, or propeller were identified.
The reconstructed flight path was consistent with a significant deceleration at a near-constant altitude, followed by a descent to maintain flying speed, followed by a loss of control and/or aerodynamic stall at low altitude, from which the airplane did not recover. The airplane had slowed and started to descend when the pilot took the deliberate actions of squawking 7700 and transmitting a radio distress call. He attempted to describe the problem that he perceived. During that time, the data suggests that the airplane was still controllable and was under control. Shortly thereafter, as evidenced by the significantly increased descent rate and the pilot's transmission that he was going down, control was lost, and the airplane impacted the ground.
The limited propeller damage, coupled with the engine's dependence on electricity and its electronics for continued operation, suggest that the deceleration could have been a result of an engine power loss for electrical or electronic reasons that could not be determined during postaccident examination. The specific reason for the stall could not be determined; however, the pilot may have been distracted by the emergency or the radio calls. The investigation was unable to determine the accuracy of the airspeed indicator or stall speed values. Further, the airplane does have a limited natural stall warning and no stall warning system to alert the pilot to an impending stall, particularly if he was distracted.
Probable cause
An electrical or engine electronic problem, which resulted in a loss of engine power, followed by a low-altitude stall.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR12FA059
- Event ID
- 20111210X64849
- Case number
- WPR12FA059
- 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: 3bdc2bbd690eeaca135e47073af30f7b563dc3c25c8bd7f1a819ce97a480bcd4; retrieved 2026-09-13T22:04:01.620Z.