Cabin Crew Injury Following Abrupt Flight Level Correction

Casualties unknown • IE

A flight crew's manual intervention to correct an altitude error led to sudden g-forces, resulting in a broken ankle for a cabin crew member.

What happened

On 7 September 2012, an Airbus A320-214, registration EI-CVA, was performing a scheduled passenger flight from Milan to Dublin. While cruising at FL380 within the London Flight Information Region, the crew received Air Traffic Control (ATC) clearance to descend to FL340. However, the pilot flying had incorrectly set the altitude window to FL240.

As the aircraft descended, the pilot monitoring noticed the discrepancy and queried the clearance with ATC. During this period of confusion, the aircraft approached the intended level. In an attempt to arrest the descent and prevent an altitude excursion, the pilot disconnected the autopilot and applied a manual, abrupt pitch input using the side stick. This sudden maneuver caused vertical acceleration to spike to 1.7g. The resulting forces caused a cabin crew member in the aft galley to be thrown to the floor, resulting in a broken ankle.

The investigation

The AAIU examined flight data from the Digital Flight Data Recorder (DFDR) and cockpit communications from the Cockpit Voice Recorder (CVR). The investigation established that while the pilot monitoring had correctly read back the clearance to ATC, the information was not immediately recorded in the flight log. Furthermore, the investigation found that the pilot flying's manual control input was an instinctive reaction to the altitude error, but it was not the most appropriate method for leveling the aircraft.

Findings

  • The flight crew failed to effectively cross-check the descent clearance, allowing the incorrect altitude to remain set in the Flight Control Unit.
  • Communication between the pilots regarding the discrepancy was unclear, which delayed the recognition of the error.
  • An abrupt manual pitch input was used to level the aircraft instead of utilizing more appropriate autopilot or flight guidance settings.
  • The rapid change in g-forces during the maneuver directly caused the injury to the cabin crew member.

Probable cause

The primary cause of the injury was an abrupt manual pitch input used to arrest the aircraft's descent, which generated significant vertical acceleration.

Frequently asked questions

What happened in the null aircraft accident near IE?

A flight crew's manual intervention to correct an altitude error led to sudden g-forces, resulting in a broken ankle for a cabin crew member.

What aircraft was involved and where did it happen?

The accident on null involved a aircraft, registration EI-CVA, at IE.

What was the probable cause of the accident?

The primary cause of the injury was an abrupt manual pitch input used to arrest the aircraft's descent, which generated significant vertical acceleration.

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 40,000+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.