Hello AR33Zab,
Thanks for the BUSS information.
I could add the following to your post, from the general perspective of compliance to an engineering, or certification specification :
If the Stall Warning announcement in a Stall approach, or Stall situation is a required - it's a MUST - then the logical formula that is at the basis of the announcement MUST calculate and deliver a TRUE or FALSE result.
If it has an "UNDEFINED" result for a certain condition, than the functioning of the formula, and the Warning announcement corresponds to a SHOULD, not to the specified MUST, and thus it fails to follow or to deliver according to the specifications.
Why the formula failed - which the NCD or AoA zero is - matters in terms of explanation for its failure to comply with MUST, and as an element for considerations in fixing it, so it complies with the MUST.
airtren.
Originally Posted by
A33Zab
jcjeant:
The Stall Warning logic itself is not at fault here.
It's the 'reducing' AoA value to 0° when CAS <60Kts by the ADIRUs which stopped the warning.
(We know they have changed that, don't know if its a part of the optional BUSS mod or if it is a separate -mandatory- mod)
Anyway this will be a legal case, who's to blame?
and I think we already suspect who will be blamed (for operating outside specs) at the end.