PPRuNe Forums - View Single Post - Ethiopian airliner down in Africa
View Single Post
Old 23rd Mar 2019, 04:36
  #2383 (permalink)  
jimjim1
 
Join Date: Oct 2007
Location: Here
Posts: 963
Received 3 Likes on 2 Posts
Originally Posted by Alchad
For example, the ARINC 429 representation of AoA uses two's complement fraction binary notation (BNR). It is interesting to note that bit 26 represents 22.5 degrees which would be the bit "flipping" between the Captain and F/O AoA values
https://www.satcom.guru/2019/03/ethi...lion.html#more

The full post contains quite a few comments which I think will generate a few talking points.

From preliminary report.
"PRELIMINARY
KNKT.18.10.35.04"

Copy here for now -
http://www.flightradar24.com/blog/wp...ary-Report.pdf

- At least one AoA sensor was changed immediately before penultimate flight. Presumably there was a percieved AoA sensor issue.
"replaced angle of attack sensor"

- Captain side AoA sensor showed 22 degree error for entirity of penultimate flight.

- Captain side AoA sensor showed 22 degree error for entirity of crash flight.

Perhaps the AoA sensor was not faulty and the issue lay elsewhere and was not correctly repaired?

I like** the idea of an encoding error. (**like the idea as an explanation for the observed symptoms - I don't like it that there was a crash - added in the hope of deflecting the present preposterous pprune pedants)

I doubt very much it was a transmission/reception error on the BUS since that almost certainly has CRC error detection.

The sensor is an analog device and there will be an A to D converter at some stage.

A bad bit within the AD converter data path seems a distinct possibility.

Last edited by jimjim1; 23rd Mar 2019 at 09:27. Reason: fixed bad flightradar24 link
jimjim1 is offline