Submitted via IRC for Bytram
Airbus A350 software bug forces airlines to turn planes off and on every 149 hours
Some models of Airbus A350 airliners still need to be hard rebooted after exactly 149 hours, despite warnings from the EU Aviation Safety Agency (EASA) first issued two years ago.
In a mandatory airworthiness directive (AD) reissued earlier this week, EASA urged operators to turn their A350s off and on again to prevent "partial or total loss of some avionics systems or functions".
The revised AD, effective from tomorrow (26 July), exempts only those new A350-941s which have had modified software pre-loaded on the production line. For all other A350-941s, operators need to completely power the airliner down before it reaches 149 hours of continuous power-on time.
Concerningly, the original 2017 AD was brought about by "in-service events where a loss of communication occurred between some avionics systems and avionics network" (sic). The impact of the failures ranged from "redundancy loss" to "complete loss on a specific function hosted on common remote data concentrator and core processing input/output modules".
In layman's English, this means that prior to 2017, at least some A350s flying passengers were suffering unexplained failures of potentially flight-critical digital systems.
Not a power of two. I wonder why 149 hours?
(Score: 5, Touché) by isostatic on Friday July 26 2019, @09:02AM (2 children)
536,400 seconds, but what is the value in milliseconds?
If you can't multiply a number by 1,000 you have no business commenting on complex software
(Score: 0) by Anonymous Coward on Friday July 26 2019, @11:51AM (1 child)
But are binary milliseconds like in ram or decimal ones like storage marketing use to boost product size?
And after formatting those milliseconds how much time really you have left?
(Score: 0) by Anonymous Coward on Saturday July 27 2019, @07:00AM
Any proper wielded of the SI system knows to label those milbiseconds.