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

Cessna 525 accident near Cedar Fort, Utah, January 18, 2016

On January 18, 2016 at about 5:00 pm local time, a 1999 Cessna 525, registered N711BX, was destroyed in an accident during enroute (climb to cruise) near Cedar Fort, Utah. It was a personal flight under general aviation rules (Part 91). 2 people were killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's loss of control due to spatial disorientation while operating in instrument meteorological conditions, which resulted in an exceedance of the airplane's design stress limitations, and a subsequent in-flight breakup. Contributing to the accident was the pilot's reported inflight instrumentation anomaly, the origin of which could not be determined during the investigation.

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

What the record shows

Date
January 18, 2016 · about 5:00 pm local time
Place
Cedar Fort, Utah · map
Type
Accident
Injuries
2 people were killed.
Weather
visual conditions (good weather)
Aircraft
Cessna 525, built 1999 · all 525s on the register
Registration
N711BX · no longer on the register · serial 525-0299
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

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

The airline transport pilot and passenger departed on a cross-country flight in instrument meteorological conditions in the light business jet. About 1 minute after departure, air traffic control instructed the pilot to climb and maintain an altitude of 14,000 ft mean sea level (msl). About 3 minutes later, the pilot stated that the airplane's flight management system (FMS) had failed. Shortly thereafter, he requested a climb and stated that he was "trying to get to clear skies." Over the next several minutes, the controller provided the pilot with headings and altitudes to vector the airplane into visual meteorological conditions. During this time, and over the course of several transmissions, the pilot stated that he was "losing instruments," was hand-flying the airplane (likely indicating the autopilot was inoperative), and that he wanted to "get clear of the weather." Radar data indicated that, during the 10-minute flight, the airplane conducted a series of climbs and descents with large variations in airspeed. About 2 minutes before the loss of radar contact, the airplane entered a climbing right turn, reaching its highest altitude of about 21,000 ft, before it began a rapidly descending and tightening turn. Performance data revealed that, during this turn, the airplane entered a partially-inverted attitude, exceeded its design maneuvering speed, and reached a peak descent rate of about 36,000 ft per minute. Radar contact was lost at an altitude of about 16,000 ft msl, and the airplane subsequently experienced an inflight breakup. The wreckage was distributed over a debris path that measured about 3/4-mile long and about 1/3-mile wide.  Postaccident examination and testing of various flight instruments did not indicate what may have precipitated the inflight anomalies that the pilot reported prior to the loss of control. Additionally, all airframe structural fractures were consistent with ductile overload, and no evidence of any preexisting condition was noted with the airframe or either engine. The airplane was equipped with three different sources of attitude information, all three of which were powered by separate sources. It is unlikely that all three sources would fail simultaneously. In the event the pilot experienced a dual failure of attitude instrumentation on both the pilot and copilot sides, airplane control could have been maintained by reference to the standby attitude indicator. Further, the pilot would have been afforded heading information from the airplane's standby compass. Although the pilot did not specifically state to the controller the nature of the difficulties he was experiencing nor, could the investigation identify what, if any, anomalies the pilot may have observed of the airplane's flight instruments, the pilot clearly perceived the situation as one requiring an urgent ascent to visual conditions. As a single pilot operating without the assistance of an additional crewmember in a high-workload, high-stress environment, the pilot would have been particularly susceptible to distraction and, ultimately, a loss of airplane control due to spatial disorientation.

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. Unknown or undetermined during enroute (climb to cruise) defining event
  2. Loss of control in flight during enroute (climb to cruise)
  3. Aircraft structural failure during uncontrolled descent
  4. Part(s) separation from AC during uncontrolled descent
  5. Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent

The NTSB's findings

  • cause Personnel issues › Psychological › Perception/orientation/illusion › Spatial disorientation › Pilot
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Lateral/bank control › Not attained/maintained
  • cause Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › (general) › Effect on operation
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › (general) › Capability exceeded
  • factor Aircraft › Aircraft systems › Navigation system › Flt management computing sys › Malfunction
  • factor Not determined › Not determined › (general) › (general) › Unknown/Not determined

Pilot

  • Certificate: airline transport pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 3,334 hours in all; 1,588 in this make and model; 8.5 in the last 90 days; 7 in the last 30 days; 2,959 as pilot in command
  • Last flight review: August 8, 2015
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 2,304.4 hours
  • Last inspection: continuous airworthiness programme, January 4, 2016; 3 hours since
  • Maximum gross weight: 10,600 lb
  • Seats: 7
  • Landing gear: retractable
  • Engine 1: Williams International FJ 44 (turbojet); 2,260 hours total
  • Engine 2: Williams International FJ 44 (turbojet); 2,257 hours total
  • Not recorded

The flight

  • Departed from: SLC Salt Lake City UT at 4:30 pm
  • Destination: TUS Tucson AZ
  • Flight plan: IFR

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: broken clouds at 2,700 ft
  • Temperature: 37°F (3°C), dew point 34°F (1°C)
  • Altimeter: 30.06 inHg
  • Observation at 4:53 pm from SLC, 28 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

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

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

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.