Fatal Lancair Evolution Crash in Mesa, AZ: A Cautionary Tale

A high-performance, experimental Lancair Evolution aircraft took off from Phoenix Deer Valley Airport on July 17, 2017, on what was supposed to be a routine cross-country flight. However, just 25 minutes in, the pilot reported electrical issues, setting off a chain of events that would ultimately lead to a tragic crash near Falcon Field Airport in Mesa, Arizona. The accident claimed the lives of the private pilot and his passenger.

This incident highlights the dangers of aircraft system failures, the importance of emergency procedures, and how distraction and lack of experience can be deadly in high-performance aircraft.

The First Flight: A Warning That Was Ignored

The accident pilot, a 53-year-old private pilot with an instrument rating, had approximately 1,700 total flight hours, including 41 hours in the Lancair Evolution. He had purchased the aircraft just three months prior and completed transition training in it. However, most of his recent flight time had been in a much slower Aviat Husky A1-200, which likely contributed to his struggle with the high-speed Lancair Evolution.

Three days before the crash, Alan went to retrieve his aircraft from the maintenance facility at Falcon Field. While waiting for a mechanic to replace a landing gear microswitch, he sat in the cockpit with the radios on, draining the battery voltage to 22.5 volts.

After takeoff, Alan performed a low pass over the runway, then radioed that something was wrong with the landing gear. Instead of troubleshooting properly, he texted the maintenance facility mid-flight, a clear distraction. The facility owner, Heath, saw the aircraft flying dangerously slow, nearly stalling, and immediately called Alan, instructing him to increase power and climb to troubleshoot safely.

Alan accidentally pulled the parking brake instead of the emergency landing gear handle, worsening his confusion. Eventually, Heath asked Alan whether he had turned on the generator. Alan cycled the switch, and power was restored—revealing that he had simply forgotten to turn it on after engine start.

After this incident, Heath warned Alan that he needed to spend more time reviewing the aircraft systems before flying again. Unfortunately, Alan did not listen. Three days later, he took off on his final flight.

The Second Flight: A Preventable Crisis

On July 17, 2017, Alan and Krista took off from Deer Valley Airport (DVT) in Phoenix, Arizona, bound for Santa Ana, California. Almost immediately, Alan noticed low voltage warnings on his primary and multifunction displays (PFD/MFD), just like during his previous flight. Instead of turning around immediately, he continued west for 15 minutes before finally deciding to divert back to Falcon Field.

Alan did not declare an emergency, despite the clear signs of an impending electrical failure. He overflew multiple airports, including Luke Air Force Base (3 miles away) and Glendale Regional Airport (8 miles away), both of which could have provided a safe landing. Instead, he continued toward Falcon Field, adding unnecessary risk.

At 16:41 local time, Alan took a photo showing that the system voltage had dropped to 19.6 volts. His aircraft’s generator required at least 18 volts to operate, meaning he was minutes away from losing all electrical power.

Despite multiple warning signs, Alan never turned off non-essential systems like the air conditioning, which was still running even though the emergency checklist advised turning it off to conserve battery power.

The Final Approach: A Series of Critical Errors

At 16:49, as Alan entered the pattern at Falcon Field, his aircraft suffered a total electrical failure. The tower controller confirmed visually that the landing gear appeared down, but Alan was unable to acknowledge.

Then, in a shocking decision, he performed a go-around instead of landing.

This choice was fatal. His aircraft no longer had electrical power, meaning he would need to manually extend the gear and land without flaps. Alan entered the downwind leg again but flew it too close to the runway, likely forcing him to pull back harder in the turn to final—causing the aircraft to stall and enter a near-vertical descent.

Alan and Krista were killed instantly when the aircraft crashed into a golf course just moments away from the runway.

Video footage confirmed that just before impact, the aircraft was flying at about 83 knots, dangerously close to the stall speed of 76 knots (clean) or 61 knots (with landing flaps extended). The Lancair Evolution is a high-performance aircraft that requires precise speed management, especially in the traffic pattern.

Post-Crash Investigation: What Went Wrong?

Investigators found no evidence of pre-impact mechanical failure that would have prevented normal operation of the aircraft. However, due to a post-crash fire, the exact cause of the electrical system failure could not be determined.

The starter-generator drive shaft was found fractured in overload, meaning it was rotating at the time of impact, but the aircraft’s electrical system had already been depleted by then. The avionics and circuit breaker panel were destroyed by fire, making further analysis impossible.

Contributing Factors

1. Failure to Follow Emergency Procedures:
   • The generator failure checklist instructed the pilot to turn off nonessential equipment, but photos recovered from his phone showed that the air conditioning remained on long after he reported electrical issues.
   • Instead of landing at the nearest suitable airport, the pilot continued for 30 minutes toward his maintenance facility, draining the remaining battery power.
2. Distraction from Troubleshooting & Phone Use:
   • The pilot was text messaging his maintenance facility about the electrical issue 8 minutes before the crash.
   • 3 minutes before the crash, he made a phone call, possibly trying to reach air traffic control to confirm gear position.
   • These distractions likely contributed to his loss of situational awareness.
3. Lack of Experience with High-Performance Aircraft:
   • The pilot’s recent experience was primarily in a much slower Husky A1-200, which stalled at 48-55 knots—far lower than the Lancair Evolution’s 61-76 knot stall speed.
   • This transition may have caused him to misjudge the aircraft’s speed and handling characteristics, leading to the fatal stall.
4. Aerodynamic Stall Due to Slow Speed on Approach:
   • The aircraft’s final turn was too steep, with an airspeed of only 83 knots.
   • This was dangerously close to stall speed, especially in a turn where stall speed increases due to added load factor.
   • The low altitude left no room for recovery once the stall occurred.

Key Safety Lessons

1. Always Follow Emergency Procedures

Aircraft checklists exist for a reason. The generator failure checklist was clear: reduce electrical load, land at the nearest suitable airport. The pilot disregarded both. If he had landed sooner, this accident may have been avoided.

2. Prioritize Flying the Airplane

The pilot was distracted by texting and making a phone call while troubleshooting the electrical issue. Pilots must remember the “Aviate, Navigate, Communicate” principle—flying the airplane should always come first.

3. Know Your Aircraft’s Performance Limits

Transitioning between aircraft with significantly different speeds and handling characteristics requires time and practice. The Lancair Evolution is not forgiving at low speeds, and the pilot’s recent time in a much slower aircraft likely contributed to poor airspeed management.

4. Declare an Emergency

The pilot never declared an emergency despite experiencing a total electrical failure. Declaring an emergency would have given him priority handling and possibly better guidance from controllers.

5. Manage Energy on Approach

A tight, steep turn at low altitude is a common setup for an aerodynamic stall. A stabilized approach with proper airspeed control is critical, especially in high-performance aircraft.

Conclusion

The crash of the Lancair Evolution in Mesa, Arizona, was a tragic accident with multiple contributing factors. The pilot’s decision to continue flying with a known electrical issue, his failure to follow emergency procedures, distraction due to phone use, and poor airspeed management all played a role in the loss of control.

This accident serves as a reminder that emergency procedures must be followed to the letter, and pilots should always prioritize flying the airplane above all else. High-performance aircraft demand precision, discipline, and respect for their handling characteristics—and failing to manage these factors can have fatal consequences.