Airbus A320-Family Wing Thrust Spigot Nuts: Three Corroded Parts, One Look for the Whole U.S. Fleet

An FAA proposal published October 8, 2026 would require repetitive general visual inspections of the wing thrust spigot area on every U.S. Airbus A318, A319, A320 and A321 after three in-service occurrences of severely corroded slotted nuts. The proposal is the system working. FLEX AI™ does not inspect a slotted nut and does not replace this proposal or any check in it.

Three slotted nuts on A320-family wings corroded badly enough to lose their grip on the part they were holding. Now nearly two thousand U.S. airplanes may get a recurring look at the same spot.

On October 8, 2026, the Federal Register published a Federal Aviation Administration notice of proposed rulemaking for all Airbus SAS Model A318, A319, A320 and A321 series airplanes. The part in question is a slotted nut at the wing thrust spigot, in the joint that ties the engine pylon to the wing. After three in-service occurrences of severe corrosion, the concern is that the spigot sleeve the nut retains could migrate or go missing entirely. Left unaddressed, the FAA says, that could result in degraded pylon and wing structure integrity.

This is a proposal, not a final rule. Comments are open until November 23, 2026. But the direction is clear, and it is worth looking at what it says about how the fleet learns.

What the proposal actually says

The notice (Federal Register Doc. 2026-20700, 91 FR 64318; Docket No. FAA-2026-11803; Project Identifier MCAI-2025-01392-T) would adopt EASA AD 2025-0185, dated August 26, 2025, by reference. EASA is the State of Design authority for Airbus, and under the bilateral agreement it notified the FAA of the unsafe condition. The FAA determined the condition is likely to exist or develop in other products of the same type design.

The manufacturer's service information describes three in-service occurrences of severely corroded slotted nuts that led to loss of the interfacing portion with the spigot sleeve. From those findings, a risk of complete migration of the spigot sleeve was identified, and it was determined that severe corrosion could occur on slotted nuts with part number D57250182200 at the wing thrust spigot of both wings.

The required actions, as described in the proposal, are straightforward:

The FAA estimates 1,987 airplanes of U.S. registry would be affected. Each inspection cycle is estimated at 2 work-hours, or $170 per airplane at $85 per hour, which comes to about $337,790 per inspection cycle across U.S. operators. The FAA notes it has no definitive data on which to base cost estimates for the on-condition repairs.

This is the system working. A few operators find something, and the whole fleet looks.

A small part in a load-bearing joint

The thrust spigot is not a glamorous component. It is part of how engine thrust and pylon loads are carried into the wing. A slotted nut at that joint is a small piece of hardware doing a structural job. When three of them corrode badly enough to lose their interface with the sleeve they retain, the response is exactly what it should be: look at every airplane that has one, keep looking on a repeating schedule, and stop putting that nut on new installations.

The numbers make the point. Two work-hours per airplane is a modest task. Multiply it by nearly two thousand airplanes and a repeating interval, and the fleet is spending real hangar time to answer one question: has this particular sleeve moved since the last time someone looked?

That is a reasonable question, and a visual inspection is a reasonable way to answer it today. The proposal does not need FLEX AI™ or any other technology to work. It needs operators to do the inspection and report what they find.

Corrosion does not keep a calendar

What the proposal also shows is the shape of how fleets learn about structure. A finding on a handful of airplanes becomes a fleet-wide rule, and the rule is a scheduled look.

Corrosion does not happen on that schedule. It builds in the life each airplane actually flew: every cycle, every wet ramp, every de-icing season, every month parked in humid air between inspections. Two A320s with the same part number at the same spigot can live very different lives. One shuttles short coastal sectors several times a day. Another flies longer, drier routes and sits overnight in a hangar. Both are on the same inspection interval once the rule is adopted.

By the time three findings become a proposal, that history has already been written into every airframe about to be inspected. The inspection tells you the condition at the moment someone looks. It does not tell you how the airplane lived between looks, or which airframes in a fleet have been living hardest.

That gap is not a criticism of the airworthiness system. It is the honest limit of a method built on intervals. The intervals are set conservatively for a reason: without continuous history, the schedule has to assume the worst plausible life for every airplane.

What reporting is really asking for

One detail in the proposal deserves attention. Operators would be required to report inspection results. Reporting is how a three-airplane finding becomes fleet knowledge. It is also a recognition that the fleet does not yet know enough about how often this condition develops, on which airplanes, and under what operating patterns.

Inspection reports are snapshots. Collected across a fleet, they help engineering decide whether an interval is right. What they cannot easily capture is the operating history behind each snapshot: the loads, cycles, environments and utilization that led one airplane to a finding and another to a clean result.

Where FLEX AI™ fits, and where it does not

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 proposal: FLEX AI™ does not inspect a slotted nut. It does not replace the general visual inspection, the repair instructions from Airbus, the reporting requirement, the parts installation prohibition, or any other part of this proposal or the final rule that may follow. 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 question for operators and OEMs

The A320 family is the backbone of narrowbody flying in the United States. A repetitive inspection across nearly two thousand airplanes is a fleet-scale commitment of hangar time and planning attention, even at two hours a look.

The useful question is not whether the inspection is necessary. It is. The useful question is this: when three airplanes teach the fleet something, what was the rest of the fleet already recording? If every airframe had been carrying a continuous structural history, the conversation after those three findings could start with more context about which airplanes have lived the hardest lives.

Comments on the proposal are open until November 23, 2026. However the final rule reads, the inspection will happen on a schedule. The structure will keep living between those inspections. Giving each airframe a record of that life is the next step, not as a replacement for the look, but as context for it.