airBaltic Airbus A220 300 incident
Airbus A220 300 · Incident: powerplant system/component malfunction/failure en route
From Riga International Airport (EVRA) to Málaga-Costa del Sol Airport (LEMG)
Event
- NTSB case
- ENG20LA015
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Incident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- Airline
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Unknown
Airbus A220 300
- Aircraft type
- Airbus A220
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- YL-AAU
- Operator
- airBaltic
- Onboard fatalities
- Unknown
- Route
- From Riga International Airport (EVRA), RigaTo Málaga-Costa del Sol Airport (LEMG), Malaga
- Aircraft age
- About 1 year (built 2019)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Non-U.S., Commercial
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route · cruise
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Powerplant system/component malfunction/failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Cause areas
- Aircraft › Aircraft power plant
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
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.
Probable cause
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ENG20LA015
- Event ID
- 20200212X95117
- Case number
- ENG20LA015
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates, cause areas, damage. Values present in the bulk record are kept.
- The date is the UTC date the NTSB stores; the local time zone is not recorded, so the local date may differ by a day.
- API snapshot SHA-256: 9ad1b5b526d345115ecf56253bd75600084b5dd49b76343b6ce925e4063e945c; retrieved 2026-09-16T11:06:45.360Z.