logoalt Hacker News

Reason077today at 7:55 AM6 repliesview on HN

The recalled aircraft include the latest A320neo model, some of which are basically brand new. Why would they be using flight computers from before 2002? Why is an old report from 2008, relating to a completely different aircraft type (A330), relevant to the A320 issue today?


Replies

RealityVoidtoday at 11:48 AM

The issue detailed in the linked report details why the spike happened in the first place on the ADIRU (produced by Northrop Gruman). The recalled controller is the ELAC that comes from Thales. The problem chain was that despite the ADIRU spiking up, the ELAC should not have taken the reactions it took. So they are fixing it in the ELAC.

t0mas88today at 9:02 AM

> Why would they be using flight computers from before 2002?

Because getting a new one certified is extremely expensive. And designing an aircraft with a new type certificate is unpopular with the airlines. Since pilots are locked into a single type at a time, a mixed fleet is less efficient.

Having a pilot switch type is very expensive, in the 50-100k per pilot range. And it comes with operational restrictions, you can't pair a newly trained (on type) captain with a newly trained first officer, so you need to manage all of this.

show 1 reply
LiamPowelltoday at 8:25 AM

> Why would they be using flight computers from before 2002?

Why would you assume they're not? I don't know about aircraft specifically, but there's plenty of hardware that uses components older than that. Microchip still makes 8051 clones 45 years after the 8051 was released.

show 1 reply
4ndrewltoday at 8:35 AM

The neo is not brand new - it's an incremental update to the 320. neo refers to New Engine Option

show 1 reply
Havoctoday at 8:16 AM

> Why would they be using flight computers from before 2002?

Guessing that using previously certified stuff is an advantage

RealityVoidtoday at 8:14 AM

Because the problem isn't just this. It's that the flight controller did not properly decide what to do when the data spiked because of this issue as well.