ASN Wikibase Occurrence # 217646
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can
submit corrected information.
Date: | Thursday 11 January 2018 |
Time: | 16:32 LT |
Type: | de Havilland Canada DHC-8-402Q Dash 8 |
Owner/operator: | FlyBe |
Registration: | G-ECOE |
MSN: | 4212 |
Year of manufacture: | 2008 |
Engine model: | Pratt & Whitney Canada PW150A |
Fatalities: | Fatalities: 0 / Occupants: 48 |
Aircraft damage: | None |
Category: | Serious incident |
Location: | Belfast International Airport (BFS/EGAA) -
United Kingdom
|
Phase: | Initial climb |
Nature: | Passenger - Scheduled |
Departure airport: | Belfast City Airport, Belfast, Northern Ireland (BFS/EGAC) |
Destination airport: | Glasgow Airport, Glasgow, Scotland (GLA/EGPF) |
Investigating agency: | AAIB |
Confidence Rating: | Accident investigation report completed and information captured |
Narrative:A Flybe de Havilland Dash 8-400, registration G-ECOE performing flight BE-130 from Belfast City, Northern Ireland to Glasgow, Scotland, with 44 passengers and 4 crew, was in the initial climb out of Belfast City's runway 22 through about 1,350 feet AGL, the aircraft was already accelerating for cleaning up the flaps and had entered instrument meteorological conditions at 163 Knots IAS, when the autopilot began to gradually pitch the aircraft down at a rate of about 1.2 degrees/second.
The crew was reading the after takeoff checklist, the aircraft in the meantime changed the attitude from 10 degrees nose up to 8 degrees nose down and began to descent after reaching 1,500 feet AGL. At 1,300 feet AGL the EGPWS sounded "Don't sink!". The captain immediately disconnected the autopilot and pitched the aircraft up to arrest the sink rate that had already reached 4,300 feet per minute with the airspeed having increased to 235 Knots IAS.
The EGPWS sounded "PULL UP!", after reaching a minimum height of 928 feet AGL. The commander stabilized the aircraft at 200 Knots IAS and 8 degrees nose up in a steady climb while increasing engine power. At 1,900 feet AGL the commander engaged the autopilot again, the aircraft however began to immediate pitch down again and the captain disconnected the autopilot a second time. The captain selected the flight director to IAS mode which de-selected the ALT mode, and the remainder of the flight was uneventful.
The AAIB released their bulletin (see link #1) reporting: "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 AAIB concluded the causes of the serious incident were:
Prior to pushback, the crew had selected the FD modes without entering a target altitude. This caused one mode to default to alt instead of alt sel, which was not detected by the crew.
Due to the DES being carried out whilst backtracking the runway, there was reduced time available in which to complete all required checks which, when combined with a sense of urgency, led to the crew not seeing the incorrect FD modes displayed on the FMA.
During the line-up checks, the PF noticed that alt sel was not displayed on the FMA. When alt sel was selected, the crew did not confirm that ga, hdg, and alt sel were displayed on the PFD. Instead alt mode was active and displayed which led to a target altitude of 0 ft amsl being set, resulting in a descent when the autopilot was engaged. Timely warnings of the hazardous flight path were provided by the EGPWS, and prompt corrective action by the PF returned the aircraft to safe flight.
The AAIB analysed:
Despite this high level of activity, the ‘Line Up’ checks did cause the PF to identify that alt sel was not selected but he did not see that alt was active instead of ga. The PF was also expecting to pitch the aircraft to about 15º nose-up instead of the 10º nose-up that the FD bar would have indicated with ga mode selected. It is possible that this was a reason why he did not notice that the FD bars were showing about 0º pitch on the PFD.
If the hdg, alt sel and alt modes are selected on the ground, subsequently as the aircraft climbs after takeoff above the target altitude, the FD vertical guidance bar will progressively move to a nose-down pitch attitude. Upon engagement of the autopilot, the aircraft will pitch down to follow the FD vertical guidance bar to descend to the target altitude. For this incident this target altitude would have been set to about 0 ft amsl.
When the aircraft pitched down as the autopilot was engaged, neither pilot initially noticed the change in pitch attitude but the “don’t sink” and “pull up” EGPWS warnings alerted the crew to the situation. The PF reacted promptly in accordance with the trained sequence of actions and returned the aircraft to a safe flight path. During the event the aircraft lost about 500 ft in 18 seconds, with a maximum rate of descent of 4,300 ft/min and having reached a minimum height of 928 ft agl.
When the autopilot was re-engaged, the aircraft again pitched nose-down but this was identified by the crew. They engaged IAS mode which replaced the alt mode and with alt sel also selected the aircraft climbed and levelled at the cleared altitude of 3,000 ft.
Accident investigation:
|
| |
Investigating agency: | AAIB |
Report number: | EW/C2018/01/04 |
Status: | Investigation completed |
Duration: | |
Download report: | Final report |
|
Sources:
1. AAIB Final Report:
https://assets.publishing.service.gov.uk/media/5bc73322ed915d0b0349a662/DHC-8-402_Dash_8_G-ECOE_11-18.pdf 2.
https://siteapps.caa.co.uk/g-info/ 3.
https://www.9news.com.au/2018/11/09/11/16/flybe-plane-in-autopilot-error-plunges-to-the-ground 4.
https://www.dailyrecord.co.uk/news/uk-world-news/glasgow-bound-flybe-flight-horror-13554172 5.
https://www.belfasttelegraph.co.uk/news/northern-ireland/flight-out-of-belfast-nosedived-500ft-due-to-autopilot-setting-37504384.html 6.
https://www.bbc.co.uk/news/uk-46137445
History of this aircraft
Other occurrences involving this aircraft Media:
Revision history:
Date/time | Contributor | Updates |
11-Nov-2018 21:22 |
Dr.John Smith |
Added |
12-Nov-2018 20:14 |
harro |
Updated [Source, Embed code, Accident report, ] |
21-Nov-2022 05:21 |
Ron Averes |
Updated [Location, Departure airport, Destination airport] |
The Aviation Safety Network is an exclusive service provided by:
CONNECT WITH US:
©2024 Flight Safety Foundation