Accident Details
Probable Cause and Findings
the pilot's failure to maintain adequate airspeed while attempting to land in gusty wind conditions leading to an inadvertent stall/mush, which resulted in a porpoise and subsequent loss of directional control.
Aircraft Information
Analysis
On May 31, 2000, at 1232 hours Pacific daylight time, an experimental Hilyard Dragonfly, N22EX, veered off the runway during landing at the General William J. Fox Airfield, Lancaster, California. The personal flight, operated under the provisions of 14 CFR Part 91, by the owner/builder, sustained substantial damage. The private pilot, the sole occupant, was not injured. Visual meteorological conditions prevailed and no fight plan was filed. The flight originated from the airport at 1130. The automated weather reporting station on the field recorded the winds from 240 degrees at 12 knots with gusts to 14 knots.
The pilot stated that he was accomplishing a series of high-speed runway taxi tests to verify operation of a new wheel/brake installation. A gust of wind caused the airplane to become airborne in ground effect and veer to the right of the centerline. Due to the insufficient runway length remaining, full power was added. The plane departed ground effect and climbed out. The pilot entered the traffic pattern and made a normal approach to land.
The pilot stated that during the approach for landing the airplane was struck by another gust of wind that reduced his airspeed. He said he was "too high and slow," rendering the canard pitch authority inadequate. The airplane stuck the runway with the canard tip mounted wheels, and the airplane porpoised down the runway three times. He added power after the first bounce to restore airspeed prior to the occurrence of the second bounce. After the second bounce, he reduced the airspeed. On the third bounce the airplane did not respond to rudder inputs, departed the runway, and came to rest on its nose between the runway and the taxiway.
Data Source
Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# LAX00LA210