Aviation Crash Map

Cessna 525 N711BX

18 January 2016 · Cedar Fort, Utah, United States · Fatal

Summary

On 18 January 2016 at about 17:00 local time, a Cessna 525 registered N711BX was involved in an accident near Cedar Fort, Utah, United States. 2 people were on board and 2 died. The aircraft was destroyed. The NTSB has published a probable cause for this accident; it is quoted in full below.

The record

Date
at 17:00
Classification
Accident
Location
Cedar Fort, Utah, United States
Coordinates
40.3139, -112.0808
Aircraft
Cessna 525
Registration
N711BX
Category
Airplane
Year built
1999
Engines
2
Operator
Not recorded
Operating rule
Part 91: General Aviation
Purpose of flight
Personal
Phase of flight
Not recorded
Route
Salt Lake City → Tucson
Aircraft damage
Destroyed
Weather
VMC
Light
Day
NTSB number
WPR16FA054

People

2 people died.

On board Died Serious Minor Uninjured
2 2 0 0 0

Probable cause

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.

Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.

Read the full NTSB narrative

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.

Quoted verbatim from the NTSB record.

Other Cessna 525 accidents

Date Aircraft Location Operator Outcome Died
13 Oct 2016 Cessna 525
N518AR
Pawtucket, Rhode Island, United States - No injuries -
30 Dec 2016 Cessna 525
N614SB
Cleveland, Ohio, United States - Fatal 6
14 Mar 2016 Cessna 525
HB-VWM
Lugano, Switzerland Nomad Aviation AG No injuries -
3 May 2015 Cessna 525B
N784JS
Teterboro, New Jersey, United States Superior Air Charter LLC No injuries -
6 Nov 2015 Cessna 525
N525DY
Monroeville, Alabama, United States Execuflight LLC. No injuries -
27 Dec 2017 Cessna 525A
N525KT
Michigan City, Indiana, United States Integrated Flight Resources Inc Minor injuries -

All 69 records for this type

Other accidents in this area

Date Aircraft Location Operator Outcome Died
12 Dec 2016 Quest KODIAK 100
N772RT
Moab, Utah, United States Aerowest Aviation Fatal 1
18 Jul 2016 Diamond DA40 F
N419FP
Logan, Utah, United States Utah State University Fatal 1
2 Feb 2016 Cessna 210
N8340Z
Park Valley, Utah, United States - Minor injuries -
14 Sep 2016 Robinson R44 II
N46HF
Cedar City, Utah, United States Southern Utah University No injuries -
22 Jun 2016 Burkes BR-1
N677DB
Brigham City, Utah, United States - No injuries -
2 Aug 2016 Beechcraft C 99
N234AV
Spanish Fork, Utah, United States Ameriflight Inc No injuries -

All 170,864 records in United States