Airlines across Asia, Europe, and the United States confirmed they had completed the emergency software retrofit ordered by Airbus and mandated by global aviation regulators. The fix followed last week’s incident involving a JetBlue A320, during which a suspected vulnerability to solar flares was linked — though not proven — to a sudden and brief loss of altitude.
Airbus said the vast majority of the roughly 6,000 A320-family aircraft covered by the safety alert had already been updated, leaving fewer than 100 jets still awaiting work. Some aircraft, however, require a more extensive intervention, prompting Colombia’s Avianca to pause bookings until December 8. JetBlue said it would cancel about 20 flights on Monday as it completed updates on its fleet.
Sources familiar with the internal discussions said the sweeping recall — one of the broadest in Airbus’s history — was triggered shortly after initial indications of a possible software issue emerged late last week. Shares in Airbus slipped 3% following the news, while Thales, supplier of the flight computers involved, dropped 2%. Analysts said the long-term financial impact appears limited.
Wide-Scale Recall During a Busy Travel Period
The emergency directive, issued Friday after talks with regulators, required airlines to install the fix before their next flight, effectively grounding many aircraft during a major travel period. Executives said the pace and scale of the recall were unprecedented.
Flyadeal CEO Steven Greenway described how airlines mobilised quickly: “The thing hit us about 9 p.m. Jeddah time and I was back in here about 9:30. I was actually quite surprised how quickly we got through it: there are always complexities,” he said.
One challenge highlighted by industry sources was Airbus’s limited real-time visibility into which software versions individual aircraft were running — a gap that created early confusion among operators. Finnair, for instance, faced delays as engineers verified whether its aircraft were affected.
Within 24 hours, engineers had narrowed down the specific jets requiring the fix. Several airlines later reduced their estimates of affected aircraft, and the expected three-hour repair time per plane proved shorter in many cases.
The update required reverting to an earlier version of the software controlling the aircraft’s nose-angle calculations. Engineers had to load the software via a data-loader device physically connected in the cockpit — a security precaution to prevent cyber intrusions. At least one airline encountered delays because it did not have enough data loaders to handle dozens of simultaneous updates.
Carriers such as easyJet and Wizz Air said they completed all required updates over the weekend without flight cancellations.
Older A320s Will Need Hardware Replacement
Not all aircraft can be fixed with software alone. Some of the older A320-family jets will require new flight computers, raising questions about timelines amid global semiconductor shortages. Thales emphasised that it was not responsible for the affected software. Analysts at Jefferies suggested hardware replacement costs would likely be limited.
A Shift in Industry Crisis Response
The rapid, transparent handling of the issue reflects broader changes in the aviation sector following the Boeing 737 MAX crisis. Airbus CEO Guillaume Faury issued a public apology — a rare move in an industry historically cautious about public messaging — signalling a more open approach as manufacturers face heightened regulatory and public scrutiny.
Public-relations experts say Airbus acted decisively with the lessons of Boeing in mind. “Boeing paid the reputational price for hesitation and opacity,” said Ronn Torossian of 5W Public Relations. “Airbus clearly wants to show a willingness to say, ‘We could have done better.’ That resonates with regulators, customers, and the flying public.”
With the vast majority of affected aircraft now restored to service, airlines and regulators will continue monitoring the small number of jets awaiting more extensive fixes — and the longer-term implications for safety oversight in a software-dependent aviation era.