Originally Posted by
RatherBeFlying
This retired software developer is not impressed. Instead of RETARD, the voice prompt needs to be GO TO TOGA. This may require some sorting out of the flight mode determination logic.
Demanding a useful response from the pilot would reduce confusion and reduce the odds of making things worse where little time is available for analysis.
There's similarities with AF447 where the later stall warnings only came on when nose down was commanded. Here we have a landing annunciation come on during takeoff
Cockpits are the worst possible places for diagnosing software errors - or should we say poor specifications.
You make a good point about diagnosing errors, but remember, Airbus can't conceive of every possible failure. I don't think it's a matter of the plane being programmed to call RETARD in that situation (as good as that advice may be), as Airbus was simply able to explain WHY the call was generated at that time.
It's a bit over-engineered, and when things don't go exactly as planned, you can get some unusual results, as was the case with the RETARD callout on takeoff.