CESSNA 525 near Cleveland, OH — 2016-12-30
- Date
- 2016-12-30
- Location
- Cleveland, OH, USA
- Airport
- BKL
- Aircraft
- CESSNA 525
- Registration
- N614SB
- Category
- Airplane
- Highest injury
- Fatal
- Fatalities
- 6
- Phase of flight
- Initial climb
Probable cause
Controlled flight into terrain due to pilot spatial disorientation. Contributing to the accident was pilot fatigue, mode confusion related to the status of the autopilot, and negative learning transfer due to flight guidance panel and attitude indicator differences from the pilot's previous flight experience.
Contributing factors
Contributing to the accident was pilot fatigue, mode confusion related to the status of the autopilot, and negative learning transfer due to flight guidance panel and attitude indicator differences from the pilot's previous flight experience.
NTSB narrative
The airplane entered a right turn shortly after takeoff and proceeded out over a large lake. Dark night visual conditions prevailed at the airport; however, the airplane entered instrument conditions shortly after takeoff. The airplane climb rate exceeded 6,000 fpm during the initial climb and it subsequently continued through the assigned altitude of 2,000 ft mean sea level. The flight director provided alerts before the airplane reached the assigned altitude and again after it had passed through it. The bank angle increased to about 62 degrees and the pitch attitude decreased to about 15 degrees nose down, as the airplane continued through the assigned heading. The bank angle ultimately decreased to about 25 degrees. During the subsequent descent, the airspeed and descent rate reached about 300 knots and 6,000 fpm, respectively. The enhanced ground proximity warning system (EGPWS) provided both "bank angle" and "sink rate" alerts to the pilot, followed by seven "pull up" warnings. A postaccident examination of the recovered wreckage did not reveal any anomalies consistent with a preimpact failure or malfunction. It is likely that the pilot attempted to engage the autopilot after takeoff as he had been trained. However, based on the flight profile, the autopilot was not engaged. This implied that the pilot failed to confirm autopilot engagement via an indication on the primary flight display (PFD). The PFD annunciation was the only indication of autopilot engagement. Inadequate flight instrument scanning during this time of elevated workload resulted in the pilot allowing the airplane to climb through the assigned altitude, to develop an overly steep bank angle, to continue through the assigned heading, and to ultimately enter a rapid descent without effective corrective action. A belief that the autopilot was engaged may have contributed to his lack of attention. It is also possible that differences between the avionics panel layout on the accident airplane and the airplane he previously flew resulted in mode confusion and contributed to his failure to engage the autopilot. The lack of proximal feedback on the flight guidance panel might have contributed to his failure to notice that the autopilot was not engaged. The pilot likely experienced some level of spatial disorientation due to the dark night lighting conditions, the lack of visual references over the lake, and the encounter with instrument meteorological conditions. It is possible that once the pilot became disoriented, the negative learning transfer due to the differences between the attitude indicator display on the accident airplane and the airplane previously flown by the pilot may have hindered his ability to properly apply corrective control inputs. Available information indicated that the pilot had been awake for nearly 17 hours at the time of the accident. As a result, the pilot was likely fatigued which hindered his ability to manage the high workload environment, maintain an effective instrument scan, provide prompt and accurate control inputs, and to respond to multiple bank angle and descent rate warnings.
Analysis
- Primary failure mode
- Spatial disorientation
- First missed decision gate
- Pilot could have engaged autopilot after takeoff to maintain control.
NTSB coding
Evidence available
- CVR
- ATC audio
- ADS-B / radar
- Photos
- 35 docket documents
Docket documents35
- Transcript of Air Traffic Control Communicationsatc
- Cockpit Voice Recorder - Group Chairman's Factual Reportcvr
- Aircraft Performanceform
- Release of Aircraft Wreckage, NTSB Form 6120.15form
- Customer Service Personnel Statements - FBOinterview
- Statement of Party Representatives to NTSB Investigationinterview
- Statements from Pilots Regarding KBKLinterview
- Conversation Summary - Designated Pilot Examinerother
- Conversation Summary - Flight Instructorother
- Conversation Summary - OSU Airport Managerother
- Conversation Summary - Pilot's Colleagueother
- E-mail Correspondence - Williams Internationalother
- Excerpts from Textron Aviation Aircraft Operating Manualsother
- Maintenance Records - Airframeother
- Maintenance Records - Left Engineother
- Maintenance Records - Right Engineother
- Maintenance Records - Weight and Balanceother
- Pilot Logbooks - Excerptother
- Pilot Training Recordsother
- Summary of Airplane Examinationother
- Summary of Operational Factorsother
- Summary of Pilot's Flight Experienceother
- Weather Attachment 1other
- Weather Attachment 2other
- Weather Attachment 3other
- Weather Attachment 4other
- Weather Attachment 5other
- Weather Attachment 6other
- Weather Attachment 7other
- Accident Report Photosphotos
- ADS-B Dataradar
- Plot of ADS-B Position Dataradar
- FADEC Download Reportreport
- Maintenance Status Reportreport
- Weather Study Reportreport
Related mishaps
- CASSUTT IIIM
2026-07-05 · Odessa, TX
- PIPER PA-22-108
2026-06-05 · Westminster, MD
- TORRES RUBEN AVENTURA II
2025-11-15 · Culebrita Beach, PR
- CESSNA 152
2025-10-23 · St. Augustine, FL
- SCOTT VINCIN JUST ACFT HIGHLANDER
2025-07-13 · Mancos, CO
- Kyle Koncak Aventura II
2025-07-03 · DeLand, FL