The U.S. aircraft register, updated daily · Carbon Free Flight by 2050
Accidents · NTSB WPR17FA074 · Final report

Quicksilver MXL II accident near Hesperia, California, March 7, 2017

On March 7, 2017 at about 6:18 pm local time, a 2017 Quicksilver MXL II, an amateur-built aircraft,, registered UNREG, was substantially damaged in an accident during takeoff near Hesperia, California (Hesperia airport). It was a flight test under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).

Preview. This page is not yet listed for search engines.

The NTSB's probable cause their words, unchanged

The pilot's failure to identify and correct his construction error of a critical structural component, which resulted in a loss of airplane control during takeoff. Contributing to the accident was the pilot's impairment due to his combined use of multiple medications and illicit drugs, which led to his improper decision to attempt the flight despite evidence indicating that the error had not been addressed.

Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.

What the record shows

Date
March 7, 2017 · about 6:18 pm local time
Place
Hesperia, California · Hesperia · map
Type
Accident
Injuries
1 person was killed.
Weather
visual conditions (good weather)
Aircraft
Quicksilver MXL II, built 2017, amateur-built · all MXL IIs on the register
Registration
UNREG · no longer on the register · serial NONE
Damage
Substantial damage
Flight
Flight test · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The pilot, who did not hold a pilot or medical certificate, had been performing multiple high-speed taxi tests in the experimental amateur-built airplane since he had completed construction of it about 2 months before the accident. During those tests, the airplane had been pulling to the left. About 1 month before the accident, the pilot performed the first flight test; however, shortly after getting airborne, the airplane rolled left, departed the runway, struck a hangar, and sustained substantial damage. He spent the next month repairing the damage sustained in that accident and performing more high-speed taxi tests. Onboard video footage revealed that, during the days leading up to the final accident, the pilot performed multiple high-speed taxi tests but was unable to maintain a straight track down the runway. On the day of the accident, he performed another erratic high-speed taxi test during which the airplane veered left and right, but, instead of stopping and attempting to determine the reason for the directional control problem, he turned the airplane around and departed in the opposite direction. Shortly after rotation, the airplane began to roll left. The pilot applied corrective control inputs (right aileron and rudder), and, although the control surfaces responded appropriately, the left turn continued. The airplane then rapidly rolled to a steep left bank, the nose dropped, and the airplane rolled over into a spin. The airplane struck the ground in a nose-down attitude, and the pilot was fatally injured. Postaccident examination revealed that a load-carrying structural member on the forward left side of the airframe had not been properly secured when the pilot constructed the airplane. The unsecured structural member created a differential load between the left and right wing supporting structures and flying wires. This differential load was further increased as the airplane departed the runway surface, which transferred the weight of the pilot from the landing gear to the unsecured structural member. The resultant imbalance likely caused the left wing to warp, creating aerodynamic forces that could not be overcome by the flight controls. Witness marks on the structural member indicated that the error had gone undetected since construction was completed, and it was most likely the reason for the loss of control during the first flight test about 1 month before the accident. The airplane had not been registered with the FAA and did not have an airworthiness certificate, which should have been done before a flight test. Therefore, it did not benefit from receiving an official inspection from an FAA representative, who may have caught the error. The toxicology findings indicated that the pilot had used substantial amounts of methamphetamine in combination with hydrocodone (an impairing opioid), diazepam (an impairing benzodiazepine), THC (the active compound in marijuana), gabapentin (an impairing anti-seizure medication), and possibly alcohol before attempting flight. It could not be determined if the pilot was in the "high" phase of use and feeling grandiose and euphoric, or if he was beginning to come down from his high and feeling dysphoric and agitated at the time he elected to attempt flight. In either case, it is very likely that the pilot's judgement and decision-making were impaired by his use of methamphetamine in combination with multiple other impairing substances and that his impairment contributed to his willingness to attempt a flight in the airplane without having identified and repaired the known control problem with the airplane

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

  1. Aircraft maintenance event during prior to flight
  2. Aircraft structural failure during takeoff defining event
  3. Loss of control in flight during initial climb
  4. Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent

The NTSB's findings

  • cause Aircraft › Aircraft structures › Fuselage › Frames (main fuselage) › Incorrect service/maintenance
  • cause Aircraft › Aircraft structures › Fuselage › Frames (main fuselage) › Inadequate inspection
  • factor Personnel issues › Physical › Impairment/incapacitation › Illicit drug › Pilot
  • factor Personnel issues › Physical › Impairment/incapacitation › Prescription medication › Pilot
  • factor Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • factor Personnel issues › Action/decision › Info processing/decision › Understanding/comprehension › Pilot

Pilot

  • Certificate: student
  • Flight time: 100 hours in all; 0.1 in this make and model
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: fatal

The aircraft

  • Last inspection: inspection type not recorded
  • Maximum gross weight: 725 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Rotax 582 (piston); 0 hours total

The flight

  • Departed from: L26 Hesperia CA at 6:17 pm
  • Destination: L26 Hesperia CA
  • Flight plan: none
  • Runway 03, 3,910 ft by 50 ft

Weather at the time

  • Light: daylight
  • Wind: from 030° at 4 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 50°F (10°C), dew point 23°F (-5°C)
  • Altimeter: 30.29 inHg
  • Observation at 6:15 pm from KVCV, 13 miles away

Injuries

FatalSeriousMinorNone
Flig1

Other NTSB records under UNREG the same tail number, which may have belonged to a different aircraft at the time

2026-07-07CEN26LA246 · accident near Hooker, OK · substantial damage · minor injuries
2026-02-28CEN26LA131 · accident near Van Burensburg, IL · substantial damage · no injuries
2025-10-13ERA26LA017 · accident near Gaffney, SC · substantial damage · serious injuries
2025-09-27CEN25LA397 · accident near Harvard, IL · substantial damage · no injuries
2025-09-12CEN25LA385 · accident near Rossville, IN · substantial damage · serious injuries
2025-07-07CEN25LA242 · incident near Ingram, TX · minor damage · no injuries
2025-06-18DCA25WA305 · accident near N/A · serious injuries
2025-05-01OPS25LA034 · incident near Washington, DC
2025-04-11CEN25LA155 · accident near Brady, TX · substantial damage · serious injuries
2025-01-30DCA25MA108 · accident near Washington, DC · destroyed · fatal

About this page

Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The docket at the NTSB holds the report as a PDF and the investigation's photographs and documents. This site never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number WPR17FA074.