20 May 2016: MICHAEL BURTON Calidus

20 May 2016: MICHAEL BURTON Calidus (N50NE) — Unknown operator

No fatalities • Fruitland, UT, United States

Probable cause

The pilot's improper judgment in conducting a flight in a gyroplane over mountainous terrain near its demonstrated maximum operating altitude and his subsequent failure to maintain adequate clearance with terrain during cruise flight in turbulent weather conditions.

— NTSB Determination

Accident narrative

HISTORY OF FLIGHTOn May 20, 2016, about 1100 mountain daylight time, an experimental amateur-built Michael Burton (AutoGyro GmbH) Calidus, N50NE, collided with mountainous terrain near Fruitland, Utah. The gyroplane was registered to the builder and operated by the pilot under the provisions of 14 Code of Federal Regulations (CFR) Part 91. The private pilot and passenger were seriously injured, and the gyroplane sustained substantial damage. The cross-country personal flight departed Duchesne Municipal Airport, Duchesne, Utah, about 1015, with a planned destination of Spanish Fork Airport-Springville-Woodhouse Field, Spanish Fork, Utah. Visual meteorological conditions prevailed, and no flight plan had been filed.

The pilot reported that they departed from Glenwood Springs Municipal Airport, Glenwood Springs, Colorado, earlier that morning and stopped at Duchesne for fuel. They then departed west towards Spanish Fork on a route over the Wasatch Mountain Range. As they approached the last ridge, about 200 ft above its peak, they encountered strong downdrafts and the gyroplane descended 500 ft and into a box canyon. Unable to out-climb the terrain, the pilot guided the gyroplane over a river at the base of the canyon until he could see a landing spot on the shore. As he approached the site and initiated the landing flare, the right wheel struck a boulder and the gyroplane rolled over, coming to rest in the river.

A witness, who was fishing in the river, called 911 after climbing to a peak where he was able to acquire cell phone reception. Due to the remoteness of the site, the pilot and passenger were not recovered until later in the afternoon.

The gyroplane came to rest within a canyon, at an elevation of about 7,300 ft mean sea level. The canyon walls rose about 1,000 ft above the accident site to the north and south. The projected route of flight would have required clearance over rugged 8,200 ft peaks, about 5 miles north of the 9,420 ft summit of Baldy Mountain.

About the time of the accident, a weather observation station located at Carbon County Regional Airport/Buck Davis Field, 37 miles south-southeast of the accident site and at an elevation of 5,957 ft, reported wind from 170 degrees at 20 knots gusting 25 knots. About the same time, at Provo Municipal Airport, 38 miles west at an elevation of 4,497 ft, wind was reported from 130 degrees at 15 knots, gusting to 22 knots.

The gyroplanes Pilot Operating Handbook specified a maximum demonstrated operating altitude of 10,000 ft. The pilot reported that the gyroplanes maximum gross weight was 1,256 pounds, and the that the weight at the time of the accident was 1,100 pounds.

The pilot stated that the gyroplane did not experience any mechanical malfunctions or failures, and that the accident could have been avoided if he had approached the mountain ridge at a higher altitude.

The Federal Aviation Administration Bioaeronautical Research Laboratory performed toxicology tests on a sample of blood that was collected from the pilot at 1546 on the day of the accident. Results identified 0.0111 ug/ml of tetrahydrocannabinol carboxylic acid (THC-COOH) in his blood. Tetrahydrocannabinol carboxylic acid (THC-COOH) is the primary metabolite of tetrahydrocannabinol (THC), the main psychoactive compound in marijuana. The report did not document the presence of THC. The reporting cutoff for THC was 0.001 ug/ml.

Contributing factors

  • cause Pilot
  • cause Altitude — Not attained/maintained
  • cause Attain/maintain not possible
  • cause Effect on operation
  • cause Effect on operation
  • Pilot

Conditions

Weather
VMC, wind 170/20kt, 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.