15 Jun 2021: COVEY Tri Quickie

15 Jun 2021: COVEY Tri Quickie (N8054Y) — Unknown operator

1 fatality • Gila Bend, AZ, United States

Probable cause

The pilot’s exceedance of the airplane’s critical angle of attack during the takeoff initial climb, which resulted in an aerodynamic stall and loss of airplane control. Contributing to the accident was the reduced airplane performance due to high density altitude conditions.

— NTSB Determination

Accident narrative

On June 15, 2021, about 0820 mountain standard time, an experimental, amateur-built Tri-Quickie, N8054Y, was destroyed when it was involved in an accident near Gila Bend, Arizona. The pilot was seriously injured, and the pilot-rated passenger was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot had recently purchased the airplane and was flying it home to Texas from California. A friend of the pilot reported that he had told the pilot not to take a passenger with him on the trip until he had more experience in the airplane. According to the airport manager, the pilot and passenger arrived at the airport the evening before the accident and refueled the airplane that evening with 17.5 gallons of 100 low-lead aviation fuel. The pilot and passenger departed the following morning from runway 4 on the accident flight. A witness reported that he was working on his airplane when he saw two men perform a preflight and then board the accident airplane. The pilot started the engine and taxied the airplane to the runway hold short line where it sat for about 20 minutes with the engine running before the airplane departed. During the takeoff run, about a 1/3 of the way down the 5,200-ft-long runway, the witness observed a dirt cloud and surmised that the landing gear must have departed the runway surface. The airplane returned to the runway centerline and continued down the runway; about halfway down the runway, it appeared that the airplane was “yanked off the runway” and it “struggled” to gain altitude. The witness estimated that the airplane reached an altitude of about 50 ft when it made a left turn, stalled, and impacted the ground. The weight and balance information for the airplane was not located. Additionally, no performance specifications for the accident airplane were available. The closest weather reporting station to the accident airport was located 5 nautical miles southwest at Gila Bend Air Force Auxiliary Airport (GXF), Gila Bend, at an elevation of 883 ft mean sea level. The recorded weather conditions at 0758 included wind from 120° at 4 kts, temperature 93.2°F, dewpoint 42.8°F, and an altimeter setting of 29.81 inches of mercury. The calculated density altitude was 3,486 ft. At 0858, recorded weather conditions at GXF included wind from 280° at 3 kts, temperature 98.6°F, dew point 42.8°F, and altimeter setting of 29.81 inches of mercury. The calculated density altitude was 3,810 ft. The airplane came to rest about 200 ft west of runway 4, adjacent to the airport perimeter fence. The first identified points of impact were witness marks from the landing gear on the hard packed desert floor. The debris path continued an additional 140 ft before the airplane impacted a ditch and came to rest; a postcrash fire ensued. The airframe was mostly destroyed by the postcrash fire, exposing the inner hardware of the airplane. The main wreckage came to rest inverted with the wing and landing gear lying adjacent to the cockpit. Flight control cables were identified from the cockpit to each wing and the tail section. The engine separated from the airframe and was found near the main wreckage. The propeller hub remained attached to the engine crankshaft; however, all three propeller blades separated from the propeller hub. A visual examination of the engine revealed no holes in the crankcase. The engine had sustained thermal and impact damage to the accessory case and engine accessories. The crankshaft could not be rotated, and the engine was subsequently disassembled. Pooled molten metal was observed in the accessory case area. The cylinders and pistons displayed varying degrees of thermal damage. Examination of the airframe and engine did not reveal any anomalies that would have precluded normal operation.

Contributing factors

  • Capability exceeded
  • Airspeed — Not attained/maintained
  • Effect on equipment
  • Pilot
  • Pilot

Conditions

Weather
VMC, wind 120/04kt, vis 10sm

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.