Amateur-built THUNDER MUSTANG accident near Spanish Springs, Nevada, July 26, 2014
On July 26, 2014 at about 3:42 pm local time, a 2011 amateur-built THUNDER MUSTANG, registered N695HR, was destroyed in an accident during enroute (climb to cruise) near Spanish Springs, Nevada. It was a personal flight under general aviation rules (Part 91). 1 person had minor injuries; 1 other was unhurt. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
A complete loss of engine power during climb for reasons that could not be determined due to the severity of postcrash fire damage to the airplane.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 26, 2014 · about 3:42 pm local time
- Place
- Spanish Springs, Nevada · map
- Type
- Accident
- Injuries
- 1 person had minor injuries; 1 other was unhurt.
- Weather
- visual conditions (good weather)
- Aircraft
- Amateur-built THUNDER MUSTANG NO SERIES, built 2011
- Registration
- N695HR · no longer on the register · serial IITM026
- Damage
- Destroyed
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The builder/owner/pilot completed the kit-built composite airplane in 2011 and had flown it about 178 hours. The day before the accident, he made an uneventful flight from his home airport to another airport; the following morning, he and his passenger departed on a long cross-country flight. The pilot reported that the takeoff and initial climbout were normal, but as the airplane was climbing through an altitude of about 10,000 feet, the engine lost power suddenly and completely. The pilot described the engine failure as "immediate," without a gradual onset, or any prior symptoms. Although the propeller continued to windmill after the loss of power, the pilot was unable to effect a successful re-start and conducted a forced landing on a two-lane road. During the landing rollout, the airplane impacted a truck and a highway sign, resulting in substantial damage to the airplane, and a postaccident fire consumed a significant portion of the airplane. Although the airplane was equipped with multiple electronic devices, including two electronic engine control units (ECUs), that recorded data about the operation of the engine and airplane, fire damage precluded the recovery of any of that data. The custom V-12 engine was based on an automotive design and relied on the twin ECUs to control fuel injection and ignition. Each ECU was dedicated to a separate cylinder bank, and each was powered by an independent electrical system. As a result of this system architecture, the engine was completely dependent on electrical power to and proper functioning of both ECUs for normal operation. Loss of one ECU would have resulted in the engine running in a degraded mode on one bank of cylinders. The continued windmilling of the propeller subsequent to the power loss indicated that the engine maintained its mechanical integrity. This was confirmed by postaccident examination of the engine, which did not reveal evidence of any malfunctions or failures that would have resulted in the power loss. The lack of evidence of a mechanical failure combined with the rapidity and finality of the power loss suggested an underlying electrical problem or event that simultaneously disabled both ECUs. However, the damage to the airplane and destruction of electronic data due to the fire, precluded determination of the reason(s) for the engine power loss.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Loss of engine power (total) during enroute (climb to cruise) defining event
- Off-field or emergency landing during enroute (climb to cruise)
- Collision with terrain or object (not controlled flight into terrain) during landing (landing roll)
The NTSB's findings
- cause Not determined › Not determined › (general) › (general) › Unknown/Not determined
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 2,191 hours in all; 178 in this make and model; 71 in the last 90 days; 20 in the last 30 days; 2,133 as pilot in command
- Last flight review: May 14, 2014
- Medical certificate: Class 2 (with waivers/limitations)
- Seat: frt
- Injury: no injuries
The aircraft
- Airframe total time: 199 hours
- Last inspection: condition inspection, February 22, 2014; 41 hours since
- Maximum gross weight: 3,600 lb
- Seats: 2
- Landing gear: retractable
- Engine: Falconer V12 (piston); 213 hours total
- Fire on the ground
The flight
- Departed from: RTS Reno NV at 3:15 pm
- Destination: Rock Springs WY
- Flight plan: none
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: a few clouds
- Temperature: 66°F (19°C), dew point 37°F (3°C)
- Altimeter: 30.19 inHg
- Observation at 3:55 pm from RNO, 12 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.