2 Aug 2020: North American NAVION No Series

2 Aug 2020: North American NAVION No Series (N225HJ) — Unknown operator

2 fatalities • Cedar City, UT, United States

Probable cause

A total loss of engine power due to fuel exhaustion. Contributing to the accident was the pilot’s improper fuel planning and failure to see and avoid the communications tower support guy wire.

— NTSB Determination

Accident narrative

HISTORY OF FLIGHT

On August 2, 2020, about 0841 mountain daylight time, a North American Navion airplane, N225HJ, was substantially damaged when it was involved in an accident near Cedar City Regional Airport (CDC), Cedar City, Utah. The pilot and pilot-rated passenger were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

According to a friend of the pilot, the airplane was topped off with fuel at North Las Vegas Airport (VGT), Las Vegas, Nevada, on the day before the accident. The airplane’s main fuel tanks held 20 gallons each with a total of 39.5 gallons of usable fuel. Publicly available radar information indicated that the airplane departed VGT that day and flew two flights with a total time of about 1 hour 55 minutes. Radar data showed that, on the day of the accident, the airplane departed Strawberry Valley Estates Airport (UT24), Alton, Utah, about 0815; UT24 was about 30 miles (and about 20 minutes of flying time) from the last known point of contact from the previous day. After departure, the airplane flew southwest before turning north where it continued to track for the remaining portion of the flight captured by radar data. The airplane’s direction was consistent with a heading toward CDC.

As the airplane approached its destination, witnesses heard the pilot make a distress call. The pilot stated that the airplane was out of gas and that he was going to try to land in a field. Other witnesses observed the airplane descending and then impacting terrain. Shortly thereafter, a nearby communications tower collapsed.

WRECKAGE AND IMPACT INFORMATION

Local law enforcement and the Federal Aviation Administration responded to the accident site. Examination of the accident site revealed that all major components of the airplane were located at the site. A support guy wire from the tower was observed wrapped around the front of the airplane. There was no post impact fire.

The airplane came to rest inverted about 7 miles southwest from CDC and a few hundred feet from the collapsed tower. The wreckage site was on flat terrain at an elevation of about 5,475 ft. The outboard portion of the right wing separated and was found a few feet from the main wreckage. The right horizontal stabilizer and elevator remained attached but sustained impact damage. The front of the fuselage was also damaged. The main landing gear was extended, and the nose wheel had separated.

A review of information on the communication tower revealed that it was about 400 ft in height and constructed of steel. The tower had 5 sets of guy wires that were connected to it at different elevations. The first wire was at 80 ft, the second wire at 160 ft, the third wire at 240 ft, the fourth wire at 320 ft, and the highest wire at 380 ft. Each wire had a varying width between 5/16 to 9/16 of an inch, which increased in width the higher the elevation. There were 3 guy wires at each elevation.

Postaccident examination of the airframe and engine revealed no preimpact anomalies that would have precluded normal operation.

MEDICAL AND PATHOLOGICAL INFORMATION

The Office of the Medical Examiner, Utah Department of Health, Taylorville, Utah, conducted an autopsy on the pilot. His cause of death was blunt trauma. Toxicology testing performed by the Federal Aviation Administration Forensic Sciences Laboratory on the pilot’s liver specimen detected dextrorphan, which is a cough suppressant used in many cold medications and is generally considered not impairing.

Contributing factors

  • Fluid management
  • Pilot
  • Pilot
  • Effect on equipment

Conditions

Weather
VMC, 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.