Serious incident Airbus A320-214 (WL) G-EZWX,
ASN logo
ASN Wikibase Occurrence # 386487
 
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:Monday 28 November 2016
Time:13:03
Type:Silhouette image of generic A320 model; specific model in this crash may look slightly different    
Airbus A320-214 (WL)
Owner/operator:EasyJet
Registration: G-EZWX
MSN: 6192
Year of manufacture:2014
Engine model:CFMI CFM56-5B4/P
Fatalities:Fatalities: 0 / Occupants: 176
Aircraft damage: Minor, repaired
Category:Serious incident
Location:30 miles North West of Newcastle-upon-Tyne, Tyne & Wear (NCL/EGNT) -   United Kingdom
Phase: En route
Nature:Passenger - Scheduled
Departure airport:Edinburgh-Turnhouse Airport (EDI/EGPH)
Destination airport:Hamburg Airport, Fuhlsbüttel, Hamburg, Germany (HAM/EDDH
Investigating agency: AAIB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
An EasyJet Airbus A320-200, registration G-EZWX, performing flight U2-6931 from Edinburgh, Scotland to Hamburg (Germany) with 172 passengers and 6 crew, was climbing out of Edinburgh when the crew stopped the climb at FL250 about 30nm northwest of Newcastle-upon-Tyne, UK when the crew decided to divert to Newcastle reporting fumes in the cabin. The aircraft landed safely on Newcastle's runway 07 about 15 minutes later.

A replacement A320-200 registration G-EZWM reached Hamburg with a delay of 4 hours. The airline reported the aircraft diverted due to technical reasons.

The AAIB reported on Dec 8th 2016, that there was an electrical type smell in the cockpit shortly followed by wispy smoke during the climb out of Edinburgh. The occurrence was rated a serious incident and is being investigated by the AAIB.

On Sep 14th 2017 the AAIB released their bulletin releasing following conclusion:

=Static inverter failure=
The source of the smoke and fumes was traced to the cockpit additional electrical supply static inverter, which had overheated. The manufacturer of the static inverter isolated the fault to a component, capacitor C306, which had not received an individual quality screening prior to fitment. A batch of 2,058 static inverters were affected.

The incident on G-EZWX was the eleventh failure reported to the aircraft manufacturer which had resulted in the release of smoke and fumes into the cockpit. Of the eleven failures, at least seven had resulted in diversions.

The operator was not aware until after the incident that the manufacturer of the static inverter had published VSB 1830-25-37, nor that the aircraft manufacturer had previously communicated the problem with the static inverters in TFU 24.00.00.114.

This was because the operator was not registered to receive notifications of VSB’s from the manufacturer of the inverter and, like another large UK operator, did not routinely review TFUs.

Following a decision in September 2016, the aircraft manufacturer subsequently issued OIT 999.0096/16 to all operators on 15 December 2016 to “broaden awareness” that the reason for the failure of the static inverter had been identified and had been published to address this.

Both the aircraft manufacturer and the operator intend further safety action, in addition to that which has already been taken.

=Emergency interphone communications=
Initial communications between the Cabin Manager (CM) and co-pilot using the emergency interphone system failed to be established, as the co-pilot either inadvertently omitted to set up his audio control panel (ACP) to transmit on the cabin interphone channel or did not select the transmit button.

The CM was unable to hear the co-pilot and hung up his handset, which disconnected it from the emergency call. Communication was subsequently established with the CM about three minutes later when the co-pilot selected the forward interphone call option.

The investigation identified that neither information nor training was provided to crew on how to re-establish communications to the cockpit in the event that a cabin handset became disconnected from an emergency interphone call initiated from the cockpit.

Whilst an emergency call is in progress, it is not possible to initiate a call to the cockpit from a handset that has been disconnected. However, by selecting the emergency call button on the disconnected handset’s keypad, the handset is reconnected to the emergency call, allowing communications with the cockpit and other cabin crew who are also on the call. The CM was not aware of this feature, but had he been, communications may have been established more quickly. The emergency interphone system is infrequently used, and therefore it is important that crew have a good understanding of its operation in the event of an emergency.

Both the aircraft manufacturer and the operator intend to take safety action to address this issue.

The AAIB reported that the crew became aware of fumes and smoke in the cockpit when the aircraft climbed through FL230. Both crew donned their oxygen masks, at the same time the "Avionics Smoke" indication activated. The captain assumed duties as pilot flying and communication while the first officer performed the checklists. At about that time the cabin became aware of fumes, the captain announced "Attention, crew at all stations", which alerted cabin crew to a potential emergency. The captain transmitted a Mayday Call and had to repeat the call as ATC initially did not understand the call due to the use of the oxygen masks.

About a minute after the first officer, while working the checklist, had selected Avionics Extract and had set the Blower to OVRD the smoke and smell began to dissipate. The first officer then selected interphone emergency call function, a flight attendant picked up the phone but could not hear the first officer, the first officer however heard the flight attendant. At about the time the flight attendant hung up the interphone the AVIONICS SMOKE indication ceased.

The first officer again attempted to contact the cabin, this time using the interphone call function (rather than the emergency function). The flight attendant in the cabin picked up the hand set, pressed and released the EMER button, a two-way communication was now established about 3 minutes after the first attempt to contact the cabin.

The landing into Newcastle went without further incident, the engines were shut down. Emergency services inspected the aircraft, fumes were still noticed in the cockpit, the aircraft was electrically powered down as a precaution.

A static inverter providing additional electrical supply to the cockpit was identified as source of smoke and fumes, when it overheated.

Following a number of static inverter failures the aircraft manufacturer released information in form of "Technical Follow Up" (TFU), which does not require any follow up and therefore was not followed by the operator.

The AAIB analysed:
Smoke in the cockpit and the emergency use of oxygen by flight crews are considered to be safety issues by ICAO and, in Annex 13 Attachment C, cite them as possible examples of a Serious Incident. Following the G-EZWX event, the operator queried the aircraft manufacturer’s use of a TFU in this instance as it had concerns that the identified mechanism of the ‘capacitor failure due to overheating resulting in a smoke smell event should be classified as a safety issue and hence should have been clearly communicated to the operators.’ The failure of the static inverter on G-EZWX resulted in an unplanned diversion and the flight crew donning oxygen masks. As a consequence of the smoke and fumes released into the cockpit, this particular mode of failure of the static inverter has resulted in a total of seven aircraft diverting.

With respect to the communication problems over the Interphone the AAIB analysed:

'It was most likely that the reason the CM had been unable to hear the co-pilot was because the co-pilot had not set his ACP to transmit on the cabin attendant channel, or he had omitted to select the radio transmit switch on his ACP or sidestick whilst speaking into the oxygen mask microphone. This led to the CM hanging up his handset, which disconnected it from the emergency call. The CM was then able to make a passenger announcement from the forward handset'.

However, as the emergency interphone call was still active, it would not have been possible for the CM to have initiated an interphone call to either the cockpit or cabin crew at the rear of the aircraft, until the emergency call was cancelled. In the absence of any other action, this would have required the CM to wait for up to two minutes until the emergency call ‘timed out.’ Pressing the emergency call button on his handset would have reconnected the CM to the emergency call immediately; however, the CM was not aware that this was required as it was neither documented nor covered in training.

Three minutes after having initially tried to establish communications with the cabin crew, a button press in the cockpit accompanied by a single call chime was recorded on the CVR (Cockpit Voice Recorder). The CM removed his handset from its cradle and pressed and released the emergency call button on the keypad before speaking into it. Communications were then established between the CM and co-pilot. The single call chime, followed by communications being established with the CM indicates that the co-pilot had selected the forward attendant call button at this time. This call was prioritised over calls initiated from the cabin and it was therefore not necessary for the CM to have selected the emergency call function on his handset to connect the call.

=Damage to airframe=
Per the AAIB Report "Static inverter overheated". The aircraft was repaired and returned to service. The reported point where the diversion decision was made ("30 miles North West of Newcastle-upon-Tyne, Tyne & Wear") would put the aircraft over Rothbury, Northumberland

Accident investigation:
cover
  
Investigating agency: AAIB
Report number: EW/C2016/11/02
Status: Investigation completed
Duration: 8 months
Download report: Final report

Sources:

1. AAIB Final Report: https://assets.publishing.service.gov.uk/media/59afe620ed915d033a9fa810/Airbus_A320-214_G-EZWX_09-17.pdf
2. https://www.chroniclelive.co.uk/news/north-east-news/easyjet-flight-makes-emergency-landing-12243103
3. https://www.aeroinside.com/8653/easyjet-a320-near-newcastle-on-nov-28th-2016-fumes-and-smoke-in-cockpit
4. https://www.itv.com/news/tyne-tees/2017-09-14/easyjet-flight-makes-emergency-landing-at-newcastle-airport-due-to-cockpit-smoke
5. https://archive.news.stv.tv/east-central/1397726-smoke-in-cockpit-of-easyjet-flight-caused-by-known-fault.html
6. https://www.thenorthernecho.co.uk/news/15532988.smoke-cockpit-easyjet-flight-forced-flight-divert-newcastle-edinburgh/
7. https://www.bbc.com/news/uk-scotland-edinburgh-east-fife-38135625
8. https://planetradio.co.uk/greatest-hits/north-east/news/plane-makes-emergency-landing-newcastle/
9. https://www.chroniclelive.co.uk/news/north-east-news/easyjet-flight-newcastle-airport-emergency-13621481

History of this aircraft

This Airbus A320-214 was built in 2014, and delivered new to EasyJet at London-Luton Airport, registered as G-EZWX on 9 July 2014. The same aircraft was involved in an earlier incident on 27 July 2016 over Compiègne, France (see AAIB Report number: EW/G2016/07/25 and separate ASN entry)

Other occurrences involving this aircraft
27 July 2016 G-EZWX easyJet 0 over Compiègne non

Location

Media:

G-EZWX Airbus A320-214 G-EZWX on 21 January 2016

Revision history:

Date/timeContributorUpdates
10-Apr-2024 06:11 Dr. John Smith Added
10-Apr-2024 06:12 ASN Updated [Source, Accident report]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org