FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR24FA112 · Holmes William B AIR CREATION TWIN

17 Mar 2024 · Gila Bend, AZ, United States

Holmes William B AIR CREATION TWIN · Accident: loss of control in flight on approach

Report a problem

Event

NTSB case
WPR24FA112
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

Holmes William B AIR CREATION TWIN

Category
Weight-Shift
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
N4425L
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 26 years (built 1998)
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
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Tree(s)
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

  • Environmental issues › Physical environment
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The non-pilot-rated passenger in the front seat reported that he was in the process of purchasing the weight-shift-control aircraft from the pilot seated in the rear seat. The pilot was providing the passenger with instruction to gain flight experience and to familiarize him with the flight characteristics of the aircraft. 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. The passenger reported that the flight was about 45 minutes and they had performed one touch-and-go. During the second approach, on the final leg of the airport traffic pattern, the passenger was on the controls, the pilot called out “my airplane” and took the flight controls. The aircraft drifted to the right of the runway centerline and overflew the unimproved desert surface that consisted of brush and mesquite trees. The pilot increased the engine power and maneuvered the aircraft to the left toward the runway. During the descending left turn back to the runway, the aircraft’s approach speed was fast, and the aircraft collided with a 10-ft tall mesquite tree, subsequently impacting the ground about 85 ft to the right of the runway surface. The passenger reported that the engine sounded strong, and there were no observable aircraft malfunctions before the collision with the tree. The nearest weather reporting facility, 5 miles from the accident site, recorded calm wind at the time of the accident. Postaccident examination of the aircraft revealed no anomalies with the airframe or engine that would have contributed to a loss of control.

Probable cause

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

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR24FA112
Event ID
20240317193945
Case number
WPR24FA112
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, cause areas. 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: 5ea7ba776e6633ebbc3c689c49153fe8afb3b702acde8f7199f9acee4837188f; retrieved 2026-09-15T08:11:45.849Z.