A final FAA airworthiness directive, AD 2026-20-11, requires removal and replacement of a batch of low-pressure compressor blades on Rolls-Royce Trent 768-60, 772-60 and 772B-60 engines after a non-conforming repair left them outside the approved design. The directive is the system working. FLEX AI™ does not inspect engine blades and does not replace this AD or any check in it.
A batch of engine compressor blades went through a repair that left them outside the approved design. Nothing about those blades announced the problem on the wing. The risk was in their history. Now every one of them has to come out of service.
On October 13, 2026, the Federal Register published a final Federal Aviation Administration airworthiness directive, AD 2026-20-11, for all Rolls-Royce Deutschland Model RB211 Trent 768-60, 772-60 and 772B-60 engines. This is the Trent 700 family found on many Airbus A330s. The affected low-pressure compressor (LPC) blades are more prone to cracking. Left unaddressed, the FAA says, the condition could lead to multiple structural failures of the affected parts, with increased risk of an in-flight shutdown, an engine fire, or an uncontained release of high-energy debris. The rule takes effect November 17, 2026.
The fix is simple to state. What makes this directive worth reading is where the risk came from.
The final rule (Federal Register Doc. 2026-20869, 91 FR 64751; Docket No. FAA-2026-4648; Amendment 39-23484) follows a notice of proposed rulemaking published on June 1, 2026. The FAA received one comment, from the Air Line Pilots Association, International, which supported the proposal without change. The rule was adopted as proposed, apart from minor editorial changes and an update to the European reference.
The required work is defined in European Union Aviation Safety Agency AD 2025-0288R1, dated June 26, 2026, which the FAA rule incorporates by reference. In plain terms, operators must:
The FAA estimates the AD affects eight engines installed on airplanes of U.S. registry. Replacing the blades is estimated at 2 work-hours of labor plus $225,000 in parts, about $225,170 per engine, or roughly $1.8 million across U.S. operators.
This is not a new concern. EASA first flagged the batch in AD 2024-0130, dated July 8, 2024, which stated that the blades had been exposed in service to non-conforming repair procedures that resulted in a blade configuration deviating from the approved design. EASA later superseded that directive and expanded the list of affected parts. The FAA rule now brings the requirement to U.S.-registered engines.
The blades did not fail because of how they were built. Their risk traced back to what was done to them afterward.
Most people picture an engine directive as the response to a design problem or a manufacturing defect. This one is different. The blades were in service. They went through a repair. The repair did not match the approved design. From that point on, those specific blades carried a higher cracking risk than identical blades that had not been through the same procedure.
Two blades with the same part number can look the same on the shelf and in the engine. What separates them is history: which shop touched them, which procedure was used, and whether the result matched what the design allows. The directive works because that history was recorded well enough to identify the affected batch and pull it.
That is the part that stays with me. The fleet could act decisively because the records existed. The airworthiness system tracks what was done to a part very carefully, and in this case that care is exactly what made a clean, targeted fix possible.
Aviation is very good at one kind of history: the maintenance record. Part numbers, serial numbers, repairs, overhauls, the shop, the date, the procedure. When a problem is traced to a specific repair, that record is how the right parts get found and the wrong ones stay in service.
There is a second kind of history the system tracks far less of: what the structure around a part actually lives through between visits. The loads, the cycles, the environment, the routes, how hard a particular airframe is working compared with its sister ships. Most of that history is never written down. Between two scheduled checks, it is still happening. It is just not being recorded.
That gap is not a flaw in any directive. It is the honest limit of a method built on visits. Without a continuous record of how each airframe is living, the system leans on conservative intervals and on the records it does have. This directive is a reminder of how powerful a good history can be when it exists.
Nothing in this article is a criticism of how this directive came about. The process worked the way it is supposed to:
Engine shops, records teams and continuing airworthiness staff deserve credit for that traceability. It is the reason a risk hidden inside a repair could be found at all.
FLEX AI™ is built to collect and trend structural history while the aircraft is flying. The purpose is earlier visibility into how structure is actually living under real routes, loads and environments, so engineering, maintenance and operations teams have more context between required checks.
To be clear about this directive: FLEX AI™ does not inspect engine blades. It does not identify affected parts, and it does not replace the removal and replacement, or any other requirement, of AD 2026-20-11 or the EASA directive it references. Compliance stays with the operator's approved program and the applicable directives.
FLEX AI™ is structural health monitoring. It is not a camera system. The FAA STC for FLEX AI™ is in process and will be finished before the end of 2026. Until that work is complete, FLEX AI™ is not a substitute for required inspections, airworthiness directives, or approved maintenance programs. Platinum Eagle Aerospace is ISO 9001 certified, and AS9100 certification is in process.
The useful question is not whether this removal is necessary. It is. The useful question is broader: when a part's risk lives in its history, how does your program make sure that history gets read before the next shop visit?
The blades will come out on a schedule, and they should. The record of what was done to them made that possible. Giving the structure around them a record of what it lives through between visits is the next step, not as a replacement for any directive or check, but as context for it.