Airbus A220 incident near Bordeaux, Outside the U.S., February 12, 2020
On February 12, 2020 at about 9:00 am local time, a 2019 Airbus A220, registered YLAAU, was involved in an incident during enroute (cruise) near Bordeaux, Outside the U.S.. It was flown under non-U.S. commercial rules. No one was hurt; 154 people were on board or involved. The weather was conditions the NTSB did not record.
The NTSB's probable cause their words, unchanged
A No. 1 (left) engine low pressure compressor (LPC) stage 1 integrally bladed rotor (IBR) separation due to a high cycle fatigue crack (HCF) that originated at the runout of an airfoil leading edge root radius. The HCF crack developed because of a mechanically coupled LPC stage 3 and stage 1 IBR mode excitation and blade flutter response. The excitation was driven by an acoustic tone generated by turbulent airflow passing over the 2.5 bleed valve duct cavity while the engine was operating at high speeds in specific flight conditions. A primary contributor to the failure mode was an electronic engine control (EEC) software update that changed the LPC vane schedule and increased the likelihood of LPC stage 1 IBR blade flutter onset within the engine operating range.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- February 12, 2020 · about 9:00 am local time
- Place
- Bordeaux, France · map
- Type
- Incident
- Injuries
- No one was hurt; 154 people were on board or involved.
- Weather
- conditions the NTSB did not record
- Aircraft
- Airbus A220 300, built 2019
- Registration
- YLAAU · no longer on the register · serial 55064
- Damage
- Not recorded
- Flight
- Flight · non-U.S. commercial rules
The NTSB's narrative final · quoted from the NTSB record
The No. 1 engine low pressure compressor (LPC) stage 1 integrally bladed rotor (IBR) failure was caused by a stage 1 IBR high cycle fatigue crack that originated at the runout of an airfoil leading edge root radius. Multiple analytical methods, including two-dimensional (2D) computational fluid dynamics (CFD), acoustic testing, and instrumented flight testing identified a coupled LPC stage 3 and stage 1 IBR instability caused by an acoustic coincidence with the 2.5 bleed valve duct cavity. At high engine N1 speeds, the stage 3 IBR blade tips generate vortices/turbulent airflow and given the right conditions, the turbulent airflow can create an acoustic tone as it passes over the 2.5 bleed valve duct cavity, located immediately aft of the LPC stage 3 IBR (Figure 1). The acoustic tone drove a LPC stage 3 IBR blade 1st bending mode excitation that was then mechanically transferred through the LPC module and excited a LPC stage 1 IBR stiffwise bending mode that was present at the same approximate frequency. The resultant stresses on the LPC stage 1 IBR blades exceeded material limits and subsequently led to crack formation and eventual progression to overload failure. Figure 1- Engine LPC Diagram Identifying the IBR 3 / 2.5 Bleed Valve Acoustic Interaction Factors that contributed to the LPC stage 3 and stage 1 IBR acoustic coincidence and blade excitation within the engine operating range were: installation of electronic engine control (EEC) Software V2.11.7.2 and the low time rub in period on the LPC IBR blade tip clearances. EEC Software V2.11.7.2 changed the LPC inlet guide vane schedule to rotate the IGV’s in the closed direction at specific high power engine conditions to improve engine stall/surge margin. The revised vane schedule inadvertently created conditions that were favorable for generation of the 2.5 bleed valve duct cavity acoustic tone and IBR mode excitation. New engines have tighter clearances between the LPC IBR blade tips and the outer air seals. The reduced clearance created unsteady loading at the blade tip region and resulted in stronger acoustic coupling/flutter response. After a rub in period, the clearance increases, and the occurrence of flutter onset is reduced. There were three PW1524G-3 and one PW1521G-3 LPC stage 1 IBR separation events between July 25, 2019 and February 12, 2020 that occurred on multiple operators. The incident detailed in this investigation was the fourth PW1500G series LPC stage 1 IBR failure. The engine parameters at the time of each of the events and the resulting engine damage were consistent. Additional information about the failure mode and investigation process are available in the investigation dockets for the first two incidents, NTSB investigation numbers ENG19IA029 and ENG19IA034.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Powerplant sys/comp malf/fail during enroute (cruise) defining event
The NTSB's findings
- Aircraft › Aircraft power plant › Engine (turbine/turboprop) › Compressor section › Failure
- Aircraft › Aircraft power plant › Engine (turbine/turboprop) › Compressor section › Design
The aircraft
- Landing gear: retractable
- Engine 1: Pratt & Whitney PW1521G-3 (turbofan); 165 hours total
- Engine 2: Pratt & Whitney PW1521G-3 (turbofan); 0 hours total
The flight
- Departed from: EVRA Riga OF
- Destination: LEMG Malaga OF
- A second pilot was aboard
Weather at the time
- Light: daylight
- Temperature: 0°F (-18°C), dew point 0°F (-18°C)
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Cabi | 3 | |||
| Flight crew | 2 | |||
| Passengers | 149 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
2 documents, released by the NTSB on May 3, 2022. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Flight Data Recorder - Specialists' Factual Report | PDF, 26 pages | View Download |
| 2 | Flight Data Recorder - Attachment 4 (FDR Tabular Data for Event Flight) | data file | Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
