Sequence of Events in the Cockpit on Asiana Flight 214

Re:Sequence of Events in the Cockpit on Asiana Flight 214 by JshWright on Saturday December 14, 2013 @10:34PM (#6908261)

The braindead decision (in my uninformed, armchair pilot opinion) was made when the controls were no longer physically linked. Once you have controls that can move independently of each other, none of the options for handling conflicting inputs makes sense to me...

Sum them?

Only take the most extreme of the two inputs (in any given direction)?

Only take the most recently seen input?

Averaging makes more sense than any of those, given the premise of "Control sticks that can move in different directions"

[ Parent | on HN ]

Re:Sequence of Events in the Cockpit on Asiana Flight 214 by StavrosK on Saturday December 14, 2013 @10:53PM (#6908302)

You're right, but I'd go with "the secondary control is ignored and clearly marked as such" ("ignored" light turns on or something). But yeah, if they aren't linked, there's not much you can do that will make sense.

[ Parent | on HN ]

Re:Sequence of Events in the Cockpit on Asiana Flight 214 by mikeash on Sunday December 15, 2013 @10:54AM (#6909757)

Nah, the right way to compute the final inputs in a case like this is, "This design is stupid and is going to get somebody killed. There is nothing I can do at this level to fix it. You must physically link the two controls."

[ Parent | on HN ]