Basically it incorrectly got tied to the paid AOA indicator, which is where the confusion comes from, I think. This wasn't what the design intended, but due to a misunderstanding/miscommunication between Boeing and Collins on a related trouble report, it is what ended up being implemented. Collins actually found this bug some years ago, and informed Boeing, but it was requested that Collins hold off on a fix until a future anticipated firmware update or some such weak reasoning, and Boeing never informed its customers. This is documented in the Congressional report, I haven't really seen it discussed much elsewhere.
So, if you DON'T pay for the extra indicator, the AOA disagree light NEVER goes ON? YIKES! How could Collins just SIT on that malfunction??!!??
That seems like something they really NEEDED to report to the FAA pronto!
However, I strongly believe that this concept of 'update the 50 year old airframe on the same type certificate under relaxed rules and with minimal pilot training' is fundamentally flawed.
Yes, I understand how they got here, between pressure from SouthWest Airlines and just making incremental changes on a really successful product line, and wanting to just deliver a more fuel-efficient machine, quickly, to existing customers who were chomping at the bit for a lower fuel burn.
But, YES, you are right, that keeping adding more hacks to a 50 year-old design eventually needs to end!
There was a lot else going on at Boeing that was problematic, but this is where I think the regulators really need to step up and redesign their type certification scheme.
Well, they have got the MAX back into the air, with additional fixes on top of the MCAS fixes, and are probably going to crank out a bunch more of the MAX aircraft over the next few years. But, I suspect that there's going to be a LOT more scrutiny over ANYTHING Boeing comes up with next for certification. And, then, eventually, they will need to address the narrow body market, and I can't IMAGINE it well be another hack on the 737 carcass. But, I could be wrong.
Jon