The U.S. aircraft register, updated daily
Accidents · NTSB WPR17FA065 · Final report

Cessna 172 accident near Panguitch, Utah, February 26, 2017

On February 26, 2017 at about 3:40 am local time, a 1966 Cessna 172, registered N3712F, was substantially damaged in an accident during enroute (cruise) near Panguitch, Utah. It was a personal flight under general aviation rules (Part 91). 3 people were killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's continued visual flight rules flight into instrument meteorological conditions, which resulted in controlled flight into terrain. Contributing to the accident were the pilot's inadequate preflight weather planning and his poor decision-making.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
February 26, 2017 · about 3:40 am local time
Place
Panguitch, Utah · map
Type
Accident
Injuries
3 people were killed.
Weather
visual conditions (good weather)
Aircraft
Cessna 172 H, built 1966 · all 172s on the register
Registration
N3712F · no longer on the register · serial 17255207
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The noninstrument-rated private pilot was making a 220-nautical mile (nm) cross-country flight under visual flight rules over mountainous terrain in dark night instrument meteorological conditions. Radar data revealed that the airplane was flying in a northwest direction, proceeding en route between 9,100 ft and 9,900 ft mean sea level (msl). The last radar return, which occurred about 1 hour after takeoff, showed that the airplane was about 80 nm northwest of the departure airport and about 3 nm southeast of the accident site. A short time later the airplane impacted remote, snow-covered, mountainous terrain on a southwest heading at an elevation of 7,350 ft. The changes in heading and altitude between the end of the radar data and the impact suggest that the pilot began maneuvering the airplane after radar contact was lost. A survey of the accident site revealed that the damage to the airplane and the linear debris path was consistent with controlled flight into terrain. All airplane components necessary for flight were accounted for at the accident site. Additionally, a post-accident examination of the airframe and engine did not reveal evidence of any mechanical anomalies that would have precluded normal operation. Weather surveillance radar revealed an area of snow showers over the accident site, and an infrared satellite image depicted a band of low stratiform clouds over the accident site with tops near 14,000 ft msl. The cloud bases were estimated at 8,700 ft msl.  A meteorological impact statement for the area warned of marginal visual flight rules to instrument flight rules conditions in snow showers. Dark nighttime conditions existed with no illumination of the moon at the time of the accident. The area surrounding the accident site was uninhabited, and there would have been no ground lighting visible to the pilot. It is likely that the airplane encountered instrument meteorological conditions (the band of clouds), and the pilot descended and turned to exit the cloud layer but was unable to establish visual contact with the ground before impacting terrain in the dark nighttime conditions. There was no record of the pilot getting an official weather briefing. If he had gotten a briefing, he would have been told "VFR not recommended" and this may have prevented the accident.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. VFR encounter with IMC during enroute (cruise) defining event
  2. Controlled flight into terrain or object (CFIT) during maneuvering

The NTSB's findings

  • cause Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Below VFR minima › Decision related to condition
  • cause Personnel issues › Action/decision › Info processing/decision › Identification/recognition › Pilot
  • cause Personnel issues › Action/decision › Action › Incorrect action selection › Pilot
  • cause Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Below VFR minima › Effect on operation
  • cause Environmental issues › Conditions/weather/phenomena › Light condition › Dark › Effect on operation
  • factor Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • factor Personnel issues › Task performance › Planning/preparation › Weather planning › Pilot
  • Environmental issues › Physical environment › Terrain › Mountainous/hilly terrain › Contributed to outcome

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 176.8 hours in all; 120 in this make and model; 6 in the last 90 days; 113 as pilot in command
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 7,372.6 hours
  • Last inspection: annual inspection, April 14, 2016; 133 hours since
  • Seats: 4
  • Landing gear: fixed
  • Engine: Continental Motors O-300-D (piston); 7,012 hours total

The flight

  • Departed from: PGA Page AZ at 2:18 am
  • Destination: U42 Salt Lake City UT
  • Flight plan: none

Weather at the time

  • Light: night, dark
  • Visibility: 10 statute miles
  • Sky: overcast at 4,800 ft; a few clouds at 3,900 ft
  • Temperature: 27°F (-3°C), dew point 21°F (-6°C)
  • Altimeter: 29.98 inHg
  • Observation at 3:59 am from U55, 11 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers2

Documents from the investigation the NTSB's docket: the evidence folder behind the report

8 documents, released by the NTSB on April 11, 2018. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.