WPR15LA242 · Bartels Lancair Evolution
Bartels Lancair Evolution · Accident en route
From Phoenix Deer Valley Airport (DVT) to Hesperia Airport (L26)
Event
- NTSB case
- WPR15LA242
- 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
Bartels Lancair Evolution
- Aircraft type
- Bartels LANCAIR
- 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
- N427LE
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Phoenix Deer Valley Airport (DVT), Phoenix, AZTo Hesperia Airport (L26), Hesperia, CA
- Aircraft age
- About 6 years (built 2009)
- 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 · climb to 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
- Unknown or undetermined
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Not determined › Not determined
- Personnel issues › Physical
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The commercial pilot was working on the development and modification of hardware and software systems for the experimental airplane, which was being adapted for unmanned flight; however, the purpose of the flight was for personal reasons. The flight was delayed a day so the pilot could work on the airplane and perform unknown maintenance to restore functionality to the batteries, which had been drained.
After takeoff, the pilot contacted air traffic control, stating that he was at 18,100 ft and climbing to 21,000 ft. The controller responded that he was cleared to climb and maintain 25,000 ft, which was the altitude listed in the pilot's flight plan. About 4 minutes later, the pilot made his last radio transmission, which was a response to the controller's frequency change instructions. The pilot read back the new frequency correctly; he also made a slight stutter at the beginning of the transmission and double clicked the microphone. The controller checked to see if the pilot was on the frequency about 5 minutes later but did not receive a response. There were insufficient voice communications to determine if the pilot was experiencing hypoxia.
Radar data indicated that the airplane made a continuous climb until reaching 25,000 ft and tracked a jet route, passing over a series of waypoints, consistent with the autopilot controlling the airplane. After the controller did not receive a response from the pilot, two military jets intercepted the airplane. Despite trying to get the pilot's attention, they were unable to get a response from or see the pilot inside the cockpit. The airplane overflew the destination airport and eventually descended into the ocean after 4 hours 22 minutes in flight, which was likely when the engine lost power due to fuel exhaustion. The airplane's flight track and the pilot's lack of responsiveness are consistent with pilot incapacitation.
After impacting the water, the airplane floated for at least 42 minutes before it sank, which indicates that no catastrophic decompression event occurred because the airplane's pressure vessel was intact enough to not rapidly fill with water. The airplane eventually sank and was not recovered, which precluded any physical examination of the wreckage. Therefore, the configuration and status of the airplane's pressurization and oxygen systems could not be determined.
The pilot had received training in the airplane and would have known how the pressurization system operated. He had been in a hypobaric chamber and was likely familiar with the symptoms of hypoxia. He reportedly did not use any medications and was in good health. Because the pilot's body was not recovered, an autopsy and toxicology testing could not be conducted.
One of the military pilots who intercepted the airplane stated that, although he could not see anyone in the airplane, he saw what he believed to be a seatbelt shoulder harness fully forward and extremely tight. It is likely that the accident pilot was not visible because he was fully slumped over into the right seat or on the floor.
Probable cause
The pilot's incapacitation for reasons that could not be determined because the airplane was not recovered from the ocean.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR15LA242
- Event ID
- 20150814X91539
- Case number
- WPR15LA242
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2015-08-14.
- API snapshot SHA-256: 10c5b3c9e77fbb39884ea2914df4c7fbd9e0dbcd87ffaeec4f202d7ad5ebb33a; retrieved 2026-09-14T19:49:44.285Z.