17 Mar 2024: HOLMES WILLIAM B AIR CREATION TWIN

17 Mar 2024: HOLMES WILLIAM B AIR CREATION TWIN (N4425L) — Unknown operator

1 fatality • Gila Bend, AZ, United States

Probable cause

The pilot’s loss of control and subsequent collision with a mesquite tree on approach to land.

— NTSB Determination

Accident narrative

HISTORY OF FLIGHTOn March 17, 2024, about 0942 mountain standard time, an experimental amateur-built light-sport weight-shift control Air Creation Twin, N4425L, was substantially damaged when it was involved in an accident near Gila Bend Municipal Airport (E63), Gila Bend, Arizona. The pilot sustained fatal injuries and the passenger sustained minor injuries. The aircraft was operated as a Title 14 Code of Federal Regulations Part 91 instructional flight. According to the passenger, who was seated in the front seat, he intended on purchasing the aircraft and received flight instruction from the pilot. He and the pilot had flown the weight-shift-control aircraft the day before the accident and planned a subsequent flight the next morning. Before departure, the pilot briefed the passenger that they would take off and fly in the local area, then return to the airport to practice touch-and-go takeoffs and landings. The pilot briefed that the passenger would fly the approach and that the pilot would perform the landing. After departing, they had flown around the local area for about 45 minutes to increase the passenger’s flight experience and understanding of the flight characteristics of a weight-shift control aircraft. The passenger stated that after the local flight, they returned to E63 and focused on takeoffs and landings on runway 04. During the second approach, the passenger heard the pilot state, “my airplane” and the passenger then relinquished the flight controls. The passenger reported hearing the engine spool up, stating that it “sounded strong.” The passenger recalled that the aircraft turned to the right and flew over the dirt area parallel to the right side of runway 04. The aircraft’s descent rate was arrested and continued to drift to the right, over brush and vegetation. The aircraft turned left, the approach speed was fast and while headed back to the runway, the delta wing struck a mesquite tree. The aircraft descended and impacted the ground near taxiway E. It came to rest on its right side, oriented on a northwesterly heading about 158 ft southeast of the runway 04 centerline. PERSONNEL INFORMATIONA review of the pilot’s logbook revealed that his last recorded flight was December 5, 2015, in the accident aircraft. The pilot received his private pilot certificate on February 21, 2015, and did not hold a flight instructor rating. The logbook was in the pilot’s flight bag, and no additional record of pilot experience was located. AIRCRAFT INFORMATIONThe weight-shift-control aircraft was stored in a mobile trailer. However, no aircraft maintenance records were found in the trailer, and there were no aircraft maintenance logbooks available to the investigation. METEOROLOGICAL INFORMATION. AIRPORT INFORMATIONThe weight-shift-control aircraft was stored in a mobile trailer. However, no aircraft maintenance records were found in the trailer, and there were no aircraft maintenance logbooks available to the investigation. WRECKAGE AND IMPACT INFORMATIONThe initial point of impact was a 10 ft mesquite tree located about 88 ft south of the main wreckage, and about 85 ft east of the runway 04 asphalt surface. The mesquite tree was largely intact and contained witness marks comprised of missing branches with 45° cut signatures. The height of the tree was about 10 ft, and the width was about the same. The initial witness mark began on the south side of the tree, about 7 ft in height and the signatures continued throughout the treetop from south to north. The mesquite tree was located perpendicular to and just before taxiway E. The main wreckage was found consistent with it having impacted the ground nose-down and coming to rest on its right side. The nose-gear and control pedals were found about 5 ft south of the main wreckage, consistent with the nosewheel impacting the ground first. The main wreckage consisted of the delta-wing, the engine, fuel cell and the carriage. Postaccident examination of the aircraft revealed that it had sustained substantial damage to the forward carriage keel frame and wing keel. The wing keel was fracture-separated at the hang point. The seat frame showed impact signatures on the right side and was fracture-separated from the carriage frame. The nosewheel was fracture-separated from the lower carriage frame. Flight control continuity was confirmed from the cockpit to delta wing. The left wing reflex cables, battens, pockets, and leading edge stiffeners were present and unremarkable except for the three inboard battens, which sustained damage consistent with impact. The right wing reflex cables, battens, pockets and leading edge stiffeners were present and unremarkable. The sail remained intact and unremarkable up to the inboard second batten pocket. The sail had forward, aft, and lateral tears near the aft section and a separated reflex cable. The damage was consistent with the inboard No. 2 batten separating from its pocket and the trailing edge of the sail. Three of the four propeller blades were fracture-separated about midspan. The fourth blade revealed tip damage with chordwise striations. The propeller hub remained intact and unremarkable. The right-side rear flying wire was attached to the right crossbar and right downtube. The wire was taut and wrapped twice around the flange, which did not rotate as expected. The fuel system remained intact and unremarkable; the fuel cell was about 1/3 full. The aircraft was equipped with a 2-cycle carbureted engine. Because the passenger indicated that the engine operated normally, and propeller signatures were consistent with engine operation at the time of impact, an examination of the engine was not completed. Postaccident examination of the aircraft revealed no evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation. MEDICAL AND PATHOLOGICAL INFORMATIONAn autopsy of the pilot was performed by the Maricopa County Medical Examiner, Phoenix, Arizona, which listed the cause of death as multiple blunt force injuries. Toxicology testing performed at the FAA Forensic Sciences Laboratory identified losartan, amlodipine, labetalol, homoamphetamine, and tadalafil in heart blood and liver tissue. Losartan is a prescription medication commonly used to treat high blood pressure. Amlodipine is a prescription medication that can be used to treat high blood pressure and certain types of coronary artery disease. Labetalol is a prescription medication that can be used to treat high blood pressure, especially as added therapy in people who do not respond adequately to combinations of other medications. Homoamphetamine is a chemical that has been identified as a metabolite or breakdown product of labetalol. Tadalafil is a prescription medication commonly used to treat erectile dysfunction, as a sexual enhancement aid, and to treat symptoms of an enlarged prostate. Losartan, amlodipine, and labetalol are not generally considered impairing. Tadalafil is not typically impairing, although the FAA states that pilots who use it on an as-needed basis should wait 24 hours after use, before flying, to monitor for side effects.

Contributing factors

  • Pilot
  • Effect on operation

Conditions

Weather
VMC, vis 9sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.