13.07.2015 Views

In-flight upset - 154 km west of Learmonth, WA, 7 October 2008,

In-flight upset - 154 km west of Learmonth, WA, 7 October 2008,

In-flight upset - 154 km west of Learmonth, WA, 7 October 2008,

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

ADIRU 1 affected the operation <strong>of</strong> autopilot 1 but it would not have affectedautopilot 2. After autopilot 1 disconnected, the captain engaged autopilot 2, but hedisconnected it shortly after.The crew made no further attempts to use autopilot 2, which was understandablegiven their decreasing level <strong>of</strong> trust in the aircraft’s systems. The use <strong>of</strong> manualcontrol also enabled the captain to more quickly respond to any furtherpitch-downs. Although re-engaging autopilot 2 would have reduced the captain’sworkload, it would not have prevented the pitch-down commands from the FCPCs.<strong>In</strong> addition, autopilot 2 would have automatically disconnected during each <strong>of</strong> thepitch-downs.5.5.6 Cabin communicationsFollowing the first <strong>upset</strong>, the <strong>flight</strong> crew promptly advised passengers and crew tobe seated and to fasten their seat belts, and they also repeated this message soonafter the second <strong>upset</strong>.<strong>In</strong>itially the <strong>flight</strong> crew were focused on evaluating and managing the problemswith the aircraft’s systems. They realised that the pitch-down was serious andwould have resulted in injuries, and did not need any additional information fromthe cabin at that stage. After the first <strong>of</strong>ficer returned to the <strong>flight</strong> deck they hadadditional information about the extent <strong>of</strong> injuries and damage, and decided todivert to <strong>Learmonth</strong>.Soon after deciding to divert, the <strong>flight</strong> crew requested further information from thecabin. Some <strong>of</strong> the initial information was provided by an <strong>of</strong>f-duty cabin servicesmanager (CSM) who contacted the <strong>flight</strong> deck directly. Ideally, communicationsfrom the cabin in this type <strong>of</strong> situation should occur through the on-duty cabinservices manager (where available), as this will enable the manager to integrate theinformation and minimise unnecessary distractions for the <strong>flight</strong> crew. <strong>In</strong> this case,the <strong>of</strong>f-duty CSM’s communications provided useful information to the <strong>flight</strong> crew.Overall, there was regular and effective communication between the <strong>flight</strong> deck andthe cabin, and within the cabin crew. The <strong>flight</strong> crew also regularly kept thepassengers informed <strong>of</strong> their situation.Some <strong>of</strong> the passengers and crew were seriously injured and needed medicalattention. The <strong>flight</strong> crew decided that they could not allow the cabin crew to leavetheir seats because <strong>of</strong> the risk <strong>of</strong> further injuries if another <strong>upset</strong> occurred. Given theuncertain situation they were experiencing, their rationale was justified. Divertingthe aircraft, and landing as soon as possible, was the safest way <strong>of</strong> getting medicalattention to those who were seriously injured.5.6 Final comments and lessons for new systemsThe investigation into the in-<strong>flight</strong> <strong>upset</strong> occurrence involving QPA on 7 <strong>October</strong><strong>2008</strong> was difficult and took an extensive amount <strong>of</strong> time. It covered a range <strong>of</strong>complicated issues, including some that had rarely been considered in depth byprevious aircraft accident investigations (such as system safety assessments andsingle event effects).Ultimately, the occurrence involved a design limitation in the <strong>flight</strong> control systemthat had not been previously identified by the aircraft manufacturer, and a failure- 210 -

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!