FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR17FA155 · Evolution 19 Lancair Evolution

17 Jul 2017 · Mesa, AZ, United States

Evolution 19 Lancair Evolution · Accident: loss of control in flight on approach

From Phoenix Deer Valley Airport (DVT) to Falcon Field (FFZ)

Report a problem

Event

NTSB case
WPR17FA155
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
2 · 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

Evolution 19 Lancair Evolution

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
N571JM
Operator
Unknown
Onboard fatalities
Unknown
Route
From Phoenix Deer Valley Airport (DVT), Phoenix, AZTo Falcon Field (FFZ), Mesa, AZ
Aircraft age
About 6 years (built 2011)
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 control in flight
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 oper/perf/capability
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The private pilot departed on a cross-country flight in his recently purchased high-performance experimental amateur-built airplane. About 25 minutes after takeoff, the pilot informed an air traffic controller that he was experiencing electrical problems and requested to divert to the airport where his maintenance facility was located. The pilot further stated that his electrical system was not charging and that he expected he may lose radio communications due to the loss of electrical power. The pilot continued about 30 minutes to the diversion airport. Radar data revealed that, about 1 minute after being cleared for landing, the airplane's transponder stopped sending altitude information, consistent with electrical power decreasing below the 18 volts required to power the radio system. The pilot performed a low pass over the runway, presumably for the tower controller to confirm that the landing gear were extended; although the pilot was not in communication with the controller, the controller transmitted that the gear appeared to be down. The airplane continued on a close-in downwind leg and turned onto the base leg of the traffic pattern; witnesses saw it enter a steep left turn followed by a near-vertical descent consistent with an aerodynamic stall. Examination of the wreckage revealed no evidence of preimpact mechanical malfunction or failure that would have precluded normal operation; however, the electrical system was consumed by fire, precluding functional testing or examination of its components. The starter-generator drive shaft was fractured in overload, consistent with it turning at the time of impact.

The pilot had owned the airplane about 3 months, during which time he logged about 40 hours of flight experience in it, including transition training with a provider who specialized in the accident airplane make and model; however, the pilot's most recent experience was flying about 35 hours in his other airplane, which operated at much lower airspeeds. The transition between the airplanes may have contributed to the pilot's failure to identify that he had let the airspeed drop below stall speed during the landing approach.

The accident airplane had experienced electrical problems several days before the accident; however, the pilot's handling of that situation suggested a lack of familiarity with the airplane and its emergency procedures. During that event, he allowed the airplane to become slow at low altitude while troubleshooting, and he attempted to activate the emergency landing gear extension system, but instead pulled the parking brake handle. Despite the fact that the airplane's published generator failure checklist included recycling the generator switch, the pilot was only able to remedy the electrical problem after an individual at the maintenance facility instructed him via cell phone to recycle the generator switch, which he did. After restoring electrical power and landing without incident, the pilot admitted that he had forgotten to turn the generator switch on in the first place, an item that was included in the airplane's after-start procedures.

During the accident flight, the pilot displayed similar evidence of failure to follow the airplane's published emergency procedures, which, for a generator failure, included reducing the electrical load by turning off nonessential equipment and landing at the nearest suitable airport. Onboard photos of the instrument panel during the flight indicated that the air conditioner, a nonessential item, remained on after the pilot initially reported electrical problems to the air traffic controller. Additionally, the pilot chose to continue the flight for 30 minutes to his maintenance facility, overflying other airports at which he could have landed. (The emergency procedures noted that battery power would last about 30 minutes with all nonessential equipment off.) Finally, the pilot was likely distracted from his primary task of flying the airplane as he was text messaging the maintenance facility about 8 minutes before the accident and placing a phone call within the 3 minutes before the accident, which may have been an attempt to reach the tower controller to confirm the status of the landing gear.

Due to the postcrash fire, the origin of the electrical system failure could not be determined. Based on the available evidence, the accident is consistent with the pilot's failure to maintain airspeed while maneuvering for landing, which resulted in an exceedance of the airplane's critical angle of attack and an aerodynamic stall/spin.

Probable cause

The pilot's failure to maintain adequate airspeed while maneuvering for landing, which resulted in an exceedance of the airplane's critical angle of attack and a subsequent stall/spin. Contributing to the accident was the pilot's distraction due to a failure with the airplane's electrical system, failure to follow emergency procedures and to continue with a known electrical problem.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR17FA155
Event ID
20170717X15023
Case number
WPR17FA155
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, coordinates. 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: 1dd834cad2780394794307495beeefc30c14decb18cbdedb0f7f5fae9ef4f585; retrieved 2026-09-15T06:08:43.418Z.