AAIB: Autopilot Error Caused Flybe Aircraft To Rapidly Lose Altitude | Aero-News Network
Aero-News Network
RSS icon RSS feed
podcast icon MP3 podcast
Subscribe Aero-News e-mail Newsletter Subscribe

Airborne Unlimited -- Most Recent Daily Episodes

Episode Date

Airborne-Monday

Airborne-Tuesday

Airborne-Wednesday Airborne-Thursday

Airborne-Friday

Airborne On YouTube

Airborne-Unlimited-04.29.24

Airborne-NextGen-04.30.24

Airborne-Unlimited-05.01.24 Airborne-AffordableFlyers--05.02.24

Airborne-Unlimited-05.03.24

Fri, Nov 09, 2018

AAIB: Autopilot Error Caused Flybe Aircraft To Rapidly Lose Altitude

Crew Corrected The Error, And Flight Continued Normally

A report released by the U.K. Air Accidents and Incidents Branch (AAIB) says that a autopilot error caused a Bombardier Q400 airplane with 44 people on board to begin a rapid descent shortly after takeoff from Belfast City Airport on January 11.

According to the report, after takeoff from Belfast City Airport, shortly after the acceleration altitude and at a height of 1,350 ft, the autopilot was engaged. The aircraft continued to climb but pitched nose-down and then descended rapidly, activating both the “don’t sink’ and “pull up” TAWS (EGPWS) warnings. The commander disconnected the autopilot and recovered the aircraft into the climb from a height of 928 ft.

At a height of about 1,300 ft agl, an EGPWS Mode32 “don’t sink” caution was activated. The commander responded almost immediately, disconnected the autopilot and applied nose-up pitch to arrest the rate of descent, which had reached a maximum of 4,300 ft/min. Engine power was also simultaneously reduced, with the airspeed having increased to 235 KIAS. The aircraft continued to descend for a few more seconds, during which a EGPWS “pull up” warning was triggered.

The aircraft then transitioned to a climb, having reached a minimum height of 928 ft agl and a maximum airspeed of 241 KIAS (VMO 3 below 8,000 ft amsl is 245 KIAS); the crew subsequently reported that they had become visual with the ground during the recovery.

The aircraft continued to Glasgow where it made an uneventful landing. After landing, the crew briefly discussed the incident, but neither were certain why the aircraft had descended when the autopilot had been initially engaged.

The report found that the incorrect autopilot ‘altitude’ mode was active when the autopilot was engaged causing the aircraft to descend toward a target altitude of 0 ft. As a result of this event, the operator has taken several safety actions including revisions to simulator training and amendments to the taxi checklist.  

(Source: AAIB. Image from file. Not incident airplane)

FMI: Report

Advertisement

More News

ANN's Daily Aero-Linx (05.02.24)

Aero Linx: Model Aeronautical Association of Australia MAAA clubs are about fun flying, camaraderie and community. For over 75 years, the MAAA has been Australia’s largest fl>[...]

ANN's Daily Aero-Term (05.02.24): Touchdown Zone Lighting

Touchdown Zone Lighting Two rows of transverse light bars located symmetrically about the runway centerline normally at 100 foot intervals. The basic system extends 3,000 feet alon>[...]

Aero-News: Quote of the Day (05.02.24)

“Discovery and innovation are central to our mission at Virgin Galactic. We’re excited to build on our successful record of facilitating scientific experiments in subor>[...]

ANN FAQ: Contributing To Aero-TV

How To Get A Story On Aero-TV News/Feature Programming How do I submit a story idea or lead to Aero-TV? If you would like to submit a story idea or lead, please contact Jim Campbel>[...]

NTSB Final Report: Cirrus Design Corp SR20

Student Pilot Reported That During Rotation, “All Of A Sudden The Back Of The Plane Kicked To The Right..." Analysis: The student pilot reported that during rotation, “>[...]

blog comments powered by Disqus



Advertisement

Advertisement

Podcasts

Advertisement

© 2007 - 2024 Web Development & Design by Pauli Systems, LC