Sure do. The program kicked in the thrust reversers because it thought
it had already landed. Faulty input or bad coding? Take your pick but
the problem was the inputs weren't properly validated and the program
jumped into a state that was obviously, to a human at least, wrong to
be in. A program should never be able to jump into wrong states out of
sequence like that. Just stupid!


I would tend to blame the hardware there. Traffic signal controllers have
conflict monitors which are separate devices which monitor the outputs to
the lights and in the event of greens in multiple directions will trip the
system offline and put it in 4 way flash.